text:
[Snyk] Upgrade async from 3.2.4 to 3.2.5

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade async from 3.2.4 to 3.2.5.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2023-11-03.

Release notes

Package name: async

3.2.5 - 2023-11-03Version 3.2.5

3.2.4 - 2022-06-07Version 3.2.4

    from async GitHub release notes

Commit messages

Package name: async

87e94e6 Version 3.2.5
44ed0fb Update built files
af02a3d work around compiler quirk
3c7a711 path to config file
91fd894 requireConfigFile: false
0412f8d Ensure error objects are propagated without modification (#1920)
ab3c56a Update .eslintrc.json to use es2021
8610499 Run lint on node 20
ffd4cfb Run coverage on node 20
253f5dc Update Node version matrix in CI
21ab441 Bump eslint from 8.35.0 to 8.52.0 (#1922)
54f5c72 Bump @ babel/core from 7.21.0 to 7.23.2 (#1923)
37ebc0f Bump rollup from 2.79.1 to 4.2.0 (#1921)
dc37005 Bump @ babel/eslint-parser from 7.19.1 to 7.22.15 (#1917)
7d001c4 Bump chai from 4.3.7 to 4.3.10 (#1915)
2219459 Bump karma from 6.4.1 to 6.4.2 (#1910)
9b3412f Bump yargs from 17.7.1 to 17.7.2 (#1909)
aa647c0 Bump semver from 7.3.8 to 7.5.4 (#1906)
ef05de9 Bump fs-extra from 10.1.0 to 11.1.1 (#1905)
8121840 chore: updated babel/core to @ babel/core (#1900)
0864852 Bump eslint from 8.20.0 to 8.21.0 (#1857)
8bc0e6d Bump @ babel/eslint-parser from 7.18.2 to 7.18.9 (#1858)
99922c0 Bump rollup from 2.75.7 to 2.77.2 (#1855)
d0b0051 Bump jsdoc from 3.6.10 to 3.6.11 (#1856)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Handled in https://github.com/polarityio/hyas-insight/pull/12

authors: CitadelOfBlairs sarus

repo: polarityio/hyas-insight


text:
Installation issues: patching needed?

We had trouble getting the MRIQC toolbox to work at our cluster computers. We figured it out, and here is what we did. First of all, we could only get it to work with Python 3. Furthermore, it seems that some dependencies are missing when installing MRIQC via pip, and some packages need to be updated in order to make it work. Here's what we did to get the toolbox working in an anaconda environment:
module load anaconda3/4.3.0
conda create -n mriqc python=3 numpy pip
source activate mriqc
pip install setuptools
pip install --upgrade https://github.com/nipy/nipype/archive/master.zip
pip install duecredit
pip install --upgrade https://github.com/poldracklab/niworkflows/archive/master.zip

Hi @jooweg, thanks for this information. Could you provide some information about your unsuccessful settings, so that we can:

Find out why stable settings didn't work
Write your experience in the documentation

Thanks!

Hi @jooweg. Have you considered asking your admins to install Singularity (http://singularity.lbl.gov/)? It would make installing MRIQC, FMRIPREP, and other BIDS Apps with their corresponding dependencies trivial.

Thanks for the replies! In the meantime, the problem has solved itself: setting up a new environment does work with the stable settings now, also using Python 2 (we replicated the initial problem and now it also works on all separate user accounts)! I guess a patch was issued for one of the libraries?
And thanks for the tip @chrisfilo, we're going to look into Singularity.

Good to hear that. We definitely advice using containers to avoid installation issues.
BTW, please note that as of MRIQC 0.9.4, Python 2 is not supported anymore.
Feel free to reopen if there is something else for us to comment on or fix.

source: gharchive/issue

authors: chrisfilo jooweg oesteban

repo: poldracklab/mriqc

license_type: permissive

license_source: bigquery


text:
Rewrite tool to generate deprecated signatures for Java 9

Java 9 does no longer has a rt.jar. Because of this we have to rewrite the deprecated methods generator. As we cannot use the Java 9 compile (we need compatibility with Java 5), the generating class will be made abstract (DeprecatedGen) and there will be 2 dynamic implementations (using Groovy as scripting engine). Groovy is lazy with compiling, so we can use both approaches and only use Java 9, if needed.

I committed this to master branch.

source: gharchive/pull-request

repo: policeman-tools/forbidden-apis


text:
HW 3

Простая сортировка - https://www.e-olymp.com/ru/submissions/5833114
Хитрая сортировка - https://www.e-olymp.com/ru/submissions/5823707
Сортировка пузырьком - https://www.e-olymp.com/ru/submissions/5820015
k-тая порядковая статистика - https://www.e-olymp.com/ru/submissions/5826846
Сортировка слиянием - https://www.e-olymp.com/ru/submissions/5833266

Принято полностью.

license_source: github-api


text:
Implement I2C API

This pull request implements a basic I2C API. It currently has some limitations that are documented in the comments.
@csagonero Please take look when you get a chance and let me know what you think.

I've pushed another commit that adds a basic usage example for the MPU-9250.

Thanks for the review!
A small clarification:

Sorry you had to dig in the official documentation, but your guess about the alternate function seems good to me :)

That comment you refer to applies to all the following code up to the next blank line. The alternate functions were relatively obvious, I think, but the low_speed and open_drain stuff less so. That stuff was covered nowhere in the official documentation, as far as I could tell.


text:
Freeze stream when resume from sleep on Oculus Go

Thanks for your nice app.
It's freeze problem on 2.3.0 when Oculus Go is going sleep, I wear it and click volume button(developer mode), then it stop stream and freeze. When I play VRChat, head tracking is fine but video streaming is freeze.  Reconnection by manual operation can recover this, but I everytime do that.
I try to "adb logcat", I found those line.

6477 7161 D ALVR Native: NAL Queue is too large. Discard. Size=10 Limit=10

It found every frame was Started. Then I roll up log and I find "Start new frame"s without discard message at 11 times. The first is forward:

07-30 14:16:04.242  6477  8695 V FrameTracking: [Frame 172938] Start new frame. frameByteSize=47399 fecPercentage=5 m_totalDataShards=18 m_totalParityShards=1 m_totalShards=19 m_shardPackets=2 m_blockSize=2732
07-30 14:16:04.244  6477  8699 V FrameTracking: [Frame 172963] Sending tracking info.
07-30 14:16:04.246  6477  8695 V FrameTracking: [Frame 172938] Frame was successfully recovered by FEC.
07-30 14:16:04.247  6477  8709 V FrameTracking: [Frame 172938] Got NAL Type=1 Length=47399 QueueSize=0
07-30 14:16:04.247  6477  8709 V FrameTracking: [Frame 172938] Feed P-Frame. Size=47399 PresentationTime=17705013779
07-30 14:16:04.247  6477  8709 V FrameTracking: [Frame 172938] Wait next input buffer.
07-30 14:16:04.251  6477  8705 I VrApi   : FPS=75,Prd=0ms,Tear=0,Early=0,Stale=62,VSnc=1,Lat=0,Fov=0,CPU2/GPU=3/3,1286/401MHz,OC=F,TA=F/F/0,SP=N/N/N,Mem=1804MHz,Free=1308MB,PSM=0,PLS=0,Temp=28.2C/25.0C,TW=2.15ms,App=0.35ms
07-30 14:16:04.258  6477  8699 V FrameTracking: [Frame 172964] Sending tracking info.
07-30 14:16:04.272  6477  8699 V FrameTracking: [Frame 172965] Sending tracking info.
07-30 14:16:04.286  6477  8699 V FrameTracking: [Frame 172966] Sending tracking info.
07-30 14:16:04.300  6477  8699 V FrameTracking: [Frame 172967] Sending tracking info.
07-30 14:16:04.314  6477  8699 V FrameTracking: [Frame 172968] Sending tracking info.
07-30 14:16:04.319  6477  8707 I UtilPoller: GPU Util 0.140510 / CPU Util 0.583333 (avg 0.478121)
07-30 14:16:04.328  6477  8699 V FrameTracking: [Frame 172969] Sending tracking info.
07-30 14:16:04.341  6477  8699 V FrameTracking: [Frame 172970] Sending tracking info.
07-30 14:16:04.345   569  8723 D NuPlayerDriver: notifyListener_l(0xf0e2aa80), (2, 0, 0), loop setting(0, 0)
07-30 14:16:04.347   569  1426 D NuPlayerDriver: reset(0xf0e2aa80) at state 6
07-30 14:16:04.347   569  1426 D NuPlayerDriver: notifyListener_l(0xf0e2aa80), (8, 0, 0), loop setting(0, 0)
07-30 14:16:04.355  6477  8699 V FrameTracking: [Frame 172971] Sending tracking info.
07-30 14:16:04.355   569  8723 W AMessage: failed to post message as target looper for handler 0 is gone.
07-30 14:16:04.357   569  8723 D NuPlayerDriver: notifyResetComplete(0xf0e2aa80)
07-30 14:16:04.369  6477  8699 V FrameTracking: [Frame 172972] Sending tracking info.
07-30 14:16:04.383  6477  8699 V FrameTracking: [Frame 172973] Sending tracking info.
07-30 14:16:04.397  6477  8699 V FrameTracking: [Frame 172974] Sending tracking info.
07-30 14:16:04.411  6477  8699 V FrameTracking: [Frame 172975] Sending tracking info.
07-30 14:16:04.425  6477  8699 V FrameTracking: [Frame 172976] Sending tracking info.
07-30 14:16:04.427  6477  8695 V FrameTracking: [Frame 172954] Start new frame. frameByteSize=62837 fecPercentage=5 m_totalDataShards=16 m_totalParityShards=1 m_totalShards=17 m_shardPackets=3 m_blockSize=4098
...

Thank you for reporting.
I found that similar issue is caused on my device.
I will fix it.

I hope to solve this problem at next update.

It's still happen on 2.3.1.

authors: polygraphene southws

repo: polygraphene/ALVR

license: MIT


text:
Headset not found - Oculus Quest for ALVR

I've read through a lot of threads at this point, but I can't seem to find an answer. I'm using the Oculus Quest for your new ALVR release.
I've installed adb and command prompt lists my headset if I put in the command "adb devices"
I've installed SteamVR but it says "headset not detected" with (108) in brackets.
I've loaded ALVR.apk in my adb folder and once I open the program under "unknown sources" it says "Press CONNECT button on ALVR server"
but my headset doesn't show.
I should mention that my ALVR is installed C:\ALVR\driver
My adb is installed under C:\adb
and SteamVR C:\Program Files (x86)\Steam\steamapps\common\SteamVR

Does the Server see the device? Is it just the client software on the Quest having the issue?

This is how it looks, even while in the ALVR application in the oculus quest

Try temporarily disabling windows firewall. Usually these issues are due to the firewall not allowing ALVR through.
if it works with the firewall off then ill pass you some additional info to help you out.

I've turned off the firewall too before I posted here. didn't work :(

I added firewall script on alpha5.
Please try installer version of alpha5. It will automatically add firewall settings.

Make sure you not running some VPN. Also check, what your Quest is connected to your local WiFi and same network as your PC.

Great news, I downloaded the .exe and not the portable version. Now it says "Server is alive!" but It still doesn't recognize the headset

okay so I have to uninstall my previous ALVR version from my headset.
how?

You don't need to uninstall.
You should re-install by adb install -r (apk path)

ok I re-installed the ALVR to the alpha 5 version, going to try now

it still doesn't show the headset :/

there are no error messages, nothing that pops up.
Not sure what it can be

Confirm that ping command properly works.

how should the results look, my headset is supposed to be disconnected from my pc. right?

with and without having it plugged in

with and without it being plugged in

Is the 192.168.1.165 IP address of PC?
ping seemed to fail.
You should check your headset and PC are connected under same router.
And please tell the result of:

ipconfig command
adb shell ip a command

what part of ipconfig do you want to see?

Thank you. PC and headset are under same subnet. It seems right settings.
ping from PC side fails too?
Please try ping 192.168.1.39

this.. doesn't seem too good :(

I should say my firewall is still inactive, I've turned it off a while ago.
if you want me to turn it on or try something along the lines there I can

Hmm...
If you can't get ping work, you should check router configuration.
You may need to disable "privacy separator" feature.

I'll have to see what I can do about that, I've had some issues with router stuff in the past :/

I can't really access the router at the moment, however, I should be in not too long. I'll update this in a little bit once I've tried to change the "privacy separator" feature on my router.
Thank you for the help so far. Hopefully this will be the only thing I need before it's fixed

Hi Guys. im having the exact same problem, im at work so tried to set this up on their wifi but alvr just doesnt see my quest. so i set my phone up as a wifi hotspot and connected my laptop and quest to that. still doesnt find it :/    please let me know if you come up with anything to try

I think l actually had to have the Quest on my head before it could find my headset. Trigger the sensor to keep the display on maybe.

Yer I did try that.  No use. So I tried riftcat... That searches then straight away pops up is thisquest your device. But when I say yes it says connecting for about 30 seconds then goes back to searching. So for some reason they can connect. Maybe it is firewalls so I'll try in a few weeks when I go home

I'll try riftcat before I come to any conclusions. If that doesn't work... I'll just have to wait for future updates, maybe a patch will come along :P

I can't really access the router at the moment, however, I should be in not too long. I'll update this in a little bit once I've tried to change the "privacy separator" feature on my router.
Thank you for the help so far. Hopefully this will be the only thing I need before it's fixed

I wonder if this is an issue with "client isolation" features on your wifi network(s).  That could easily prevent access between your PC and the Quest.  You should have both devices on a network that does not have this enabled.

I'm having the same issue, ALVR just doesn't recognize my quest. could it be a headset specific issue?

It's most likely your antivirus. I have comodo and until I added alvr as an exception to that it wouldn't find it. Works fine now.

I had the same problem.
Not sure how to explain that (mediocre english =.=) but what router do you use?
I "kinda" use two routers. The one i got from my provider and another WLAN-router which i bought to boost my wlan to 5ghz, which is recommended if you want to stream from pc to quest.
So when i first connected my wlan router to the providers router i got the same problem of alvr not recognizing my quest anymore.
But then i made my wlan router an "ip client" and now it works.
Polygraphenes comment earlier about having pc and quest connected to the same router kinda helped me out here. So maybe this helps you as well?
I hope you understand what im tried to explain ^^"
Greetings

I doubt it as i had these issues and i fixed them all bz turning off all my
antivirus software
On Sun, 16 Jun 2019, 07:04 tuesday8877, notifications@github.com wrote:

I'm having the same issue, ALVR just doesn't recognize my quest. could it
be a headset specific issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/polygraphene/ALVR/issues/363?email_source=notifications&email_token=AMHEXJ4AV6BPMEZGPALUDY3P2XJU7A5CNFSM4HRZD2U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXZF72Q#issuecomment-502423530,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMHEXJ6EZJGYI43ZC5DBWGTP2XJU7ANCNFSM4HRZD2UQ
.

Can confirm that allowing it through my firewall did work

If you are installing the Alpha programs and it is not working for you,  Maybe try the stable / regular versions

Also change the codec that might work for you

Hi @polygraphene
I am also facing a similar kind of issue.
I am able to ping from the PC to the Oculus Quest device but somehow ping from device to PC fails. The device and PC both are connected on the same network. Also when I try to ping to the gateway from the device then it works but fails with the PC. so don't know what's happening.
Can you please give some input on it.
Thanking you in advance...!!!
Thanks
Ronak

It's most likely your antivirus. I have comodo and until I added alvr as an exception to that it wouldn't find it. Works fine now.

Hi @bwadejs, could you please give a short tutorial, which settings you made in Comodo? I tried a lot, but the headset is still not found. Would be great! Thanks 🙏

we are having the same issue. Is the riftcat a good alternative?

we are having the same issue. Is the riftcat a good alternative?

Riftcat is worth a go, yes. But I have the connection problem on ALVR beta too and the last stable version works fine. Try that one.

I had the same problem, and it looks like it is an issue with the firewall. It also doesnt work with FW deactivated. But i found an easy Workaround:

Go to the last release in the old main repo https://github.com/polygraphene/ALVR/ and install alvr with the setup.exe. The Setup does the corret FW-Changes.

Download the newest release and extract the zip to the same installation directory like the setup and overwrite the files and install the matching apk on th quest

Now start with the new version and it works. hopefully ;-)

I am getting the same results. I tried what you said @Fizelche, but it didn't work for me. I turned my firewall off as well, just in case. It says I am connected but it says server is down and then disconnects altogether. Any other ideas?

I found the reason, why it doesnt work on my first trys. Windows prevents to launch apps with special FW-requierements from desktop(maybe complete user directory). I moved the unziped copy to any other direction and it asks for firewall permissions at launch. When FW-Rule is applied, it works fine.

I found another possible blocker. ALVR was deactivatet in steamvr. To change this property: Open SteamVR-> Klick on the BurgerMenu -> Settings -> Start/Stop -> Manage Add-Ons -> activate alvr_server -> try to start again


text:
Bug when transferring a phenotype annotation with GIs

@ValWood @kimrutherford
I cannot reproduce the bug in the test server because I don't have the transfer option there, but to reproduce:

Create a double mutant phenotype annotation linked to a single phenotype annotation. In my case

Then transfer the annotation (accidentally) to single mutant phenotypes. These phenotypes can no longer be deleted since they have associated GIs. However, these cannot be deleted.

This copies the previous GIs, now associated with the wrong genotypes:

This also happens if you transfer a phenotype annotation to a double mutant genotype (but in this case it can be deleted). The GI is incorrect.
https://user-images.githubusercontent.com/22526102/202496001-4d6fb650-0c4f-4df4-a024-68d29dec4d5d.mov
@kimrutherford I think I need you to delete these three phenotype annotations and/ or their associated GIs in the canto database so I can remove them from the session.

I guess for now we should not allow to transfer annotations with GIs.

Sorry this is a canto issue. Moved to canto repo at https://github.com/pombase/canto/issues/2666

repo: pombase/fypo


text:
Update InterPro

There has been an InterPro release since our last update.  The release was in November and we last updated in September.
https://www.ebi.ac.uk/interpro/release_notes/
This should be an easy update.

The new InterPro release will go in tonight.  I've had a look and there are no surprises in the XML file, it's just slightly bigger.  All ID types are the same.  I'll check the load in the morning before updating the main site.

All looks good.

we'll do  a news item, just because we can

closing because the newsitem should be on website tracker

authors: ValWood kimrutherford

repo: pombase/pombase-chado


text:
Advances query builder actions, allow other slims

Here, we will need to call this  slim bottom BP slim
and add "disease slim" and CC and MF slim once available

Perhaps the button for open a small menu with the different slims?  That would avoid clutter in the interface.

Perhaps the button for open a small menu with the different slims? That would avoid clutter in the interface.

good plan!

I've added a small menu on the results pages for slimming with BP, CC or disease.  Let me know what changes you'd like.  The MF slim will appear there once it's added to the configuration file.
http://desktop.kmr.nz:4242/results/from/id/8e3b36f2-9790-4c90-aceb-fd6e61d81927

Nice. This is very cool. It's very useful that you can see immediately how one disease list intersects with all of the other disease lists.
Or  a process  list with diseases.
Or a disease with components
I'm quite excited about this!

Done!  Now on the main server.

Closed by accident - needs an announcement.

queued here https://github.com/pombase/website/issues/1535

repo: pombase/website


text:
search result subset selection limit

What's the current limit on how long a search result list can be for the "Select subset" feature to be active?
When it was added (#601) the limit was 500, but from some searches I was just playing with for the documentation, it seems to be a bit higher now -- I've narrowed it down to 668 < x < 1408 ;)
I'd like to put the actual number in the documentation.

Thank you too :)


text:
Couldn't make it work from a markdown code block.

I'm testing out this extension along with a Dockerized instance of  Kroki. I have setup two containers on the same bridged network, thus they can see each other:

one container running kroki (I'm using the docker-compose.yml available on Kroki's site, which pulls up all the other auxiliary services)
a second container, with Node and other goodies, which I use as a workspace

Despite having configured this extension's settings with the URL of the Kroki container, along with a "kroki-" prefix, while working inside VSCode and attached to the workspace container, nothing happens when I for instance add a "kroki-blockdialog" code block to a markdown file:
blockdiag {
  blockdiag -> generates -> "block-diagrams";
  blockdiag -> is -> "very easy!";

  blockdiag [color = "greenyellow"];
  "block-diagrams" [color = "pink"];
  "very easy!" [color = "orange"];
}

Issuing a simple GET request against the Kroki container from the workspace container's terminal (via curl) works without issues.
Any ideas what could be the issue here? Is it possible to debug the extension to see if something is breaking?

Same Problem to ne.

@mpenna As far as I know, you shouldn't say "blockdiag" again when we are talking about Markdown:
That is original structurizr format
blockdiag {
  blockdiag -> generates -> "block-diagrams";
  blockdiag -> is -> "very easy!";

  blockdiag [color = "greenyellow"];
  "block-diagrams" [color = "pink"];
  "very easy!" [color = "orange"];
}

And that is the format of embedded kroki structurizr:

```kroki-blockdiag
{
  blockdiag -> generates -> "block-diagrams";
  blockdiag -> is -> "very easy!";

  blockdiag [color = "greenyellow"];
  "block-diagrams" [color = "pink"];
  "very easy!" [color = "orange"];
}
```

@mpenna @albbino did you test the suggestion ? Closing it for now, I'll reopen if the issue is not resolved

authors: acmnu albbino mpenna pomdtr

repo: pomdtr/vscode-markdown-kroki


text:
Add Pony examples link to home page

Some folks want to come and see some "real" Pony code. Here's a link.

Thanks! :)

authors: SeanTAllen mfelsche


text:
Applying global styles.

Is there a recommended approach in bss for applying styles to the body or as top level wildcards?

Yeah, b.css() - https://github.com/porsager/bss/blob/master/README.md#css 😊
Eg
b.css({
  body: `margin 0`
})

Wow great, can't believe I missed that.  😂👍
On Wed., 26 Sep. 2018, 15:35 Rasmus Porsager, notifications@github.com
wrote:

Yeah, b.css() - https://github.com/porsager/bss/blob/master/README.md#css
😊
Eg
b.css({
body: margin 0
})
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/porsager/bss/issues/29#issuecomment-424590576, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfo9EvYRvgp-vGp8JosU15LGGg3T7Ilks5uexIjgaJpZM4W5vCw
.

authors: JAForbes porsager

repo: porsager/bss

license: WTFPL


text:
Error: failed to send transaction: Transaction simulation failed

When i run liquidator with docker-compose, an error occurs：Transaction simulation failed: Attempt to debit an account but found no record of a prior credit.

Environment:
Ubuntu 20.04 LTS
Docker version 20.10.7, build 20.10.7-0ubuntu5~20.04.2
docker-compose version 1.25.0

ubuntu@VM-0-6-ubuntu:~/liquidator$ sudo docker-compose up --build
Building portfinance-liquidator
Step 1/10 : FROM node:alpine3.14 as builder
 ---> e32df7d6c22c
Step 2/10 : RUN mkdir -p /app
 ---> Using cache
 ---> 5f63fb1cb88d
Step 3/10 : WORKDIR /app
 ---> Using cache
 ---> 5227e5285054
Step 4/10 : COPY . ./
 ---> Using cache
 ---> 3a1ea6662597
Step 5/10 : RUN yarn install
 ---> Using cache
 ---> 6dc2439e1f06

Step 6/10 : FROM node:alpine3.14
 ---> e32df7d6c22c
Step 7/10 : USER node
 ---> Using cache
 ---> 44c68d5db061
Step 8/10 : COPY --from=builder /app /app
 ---> Using cache
 ---> fd23197b6c1c
Step 9/10 : WORKDIR /app
 ---> Using cache
 ---> fa8e9d4ece75
Step 10/10 : ENTRYPOINT [ "yarn", "liquidator" ]
 ---> Using cache
 ---> b92b9f275610

Successfully built b92b9f275610
Successfully tagged portfinance-liquidator:latest
Starting liquidator_portfinance-liquidator_1 ... done
Attaching to liquidator_portfinance-liquidator_1
portfinance-liquidator_1  | yarn run v1.22.17
portfinance-liquidator_1  | $ ts-node src/partial.ts
portfinance-liquidator_1  | Port liquidator launched on cluster=https://solana-api.projectserum.com
portfinance-liquidator_1  | Creating token account for PoRTjZMPXb9T7dyU7tpLEZRQj7e6ssfAE62j2oQuc6y
portfinance-liquidator_1  | Transaction simulation failed: Attempt to debit an account but found no record of a prior credit.
portfinance-liquidator_1  |
portfinance-liquidator_1  |
portfinance-liquidator_1  | /app/node_modules/@solana/web3.js/src/connection.ts:3575
portfinance-liquidator_1  |       throw new SendTransactionError(
portfinance-liquidator_1  |             ^
portfinance-liquidator_1  | Error: failed to send transaction: Transaction simulation failed: Attempt to debit an account but found no record of a prior credit.
portfinance-liquidator_1  |     at Connection.sendEncodedTransaction (/app/node_modules/@solana/web3.js/src/connection.ts:3575:13)
portfinance-liquidator_1  |     at processTicksAndRejections (node:internal/process/task_queues:96:5)
portfinance-liquidator_1  |     at Connection.sendRawTransaction (/app/node_modules/@solana/web3.js/src/connection.ts:3535:20)
portfinance-liquidator_1  |     at Object.sendAndConfirmRawTransaction (/app/node_modules/@solana/web3.js/src/util/send-and-confirm-raw-transaction.ts:27:21)
portfinance-liquidator_1  |     at sendTransaction (/app/src/utils.ts:188:12)
portfinance-liquidator_1  |     at Object.createAssociatedTokenAccount (/app/src/utils.ts:141:3)
portfinance-liquidator_1  |     at prepareTokenAccounts (/app/src/partial.ts:134:29)
portfinance-liquidator_1  |     at runLiquidator (/app/src/partial.ts:73:19)
portfinance-liquidator_1  | error Command failed with exit code 1.
portfinance-liquidator_1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hey @JiaxingZhao , thanks for filing this issue. I think this is likely caused by the id.json file that you provided is incorrect or doesn't have SOL in it. Can you let me know the publicKey that you have been using when running liquidators?

authors: JiaxingZhao leonardgee

repo: port-finance/liquidator


text:
feat(compose-plugin): update the way client config is loaded

This PR updates the way the Docker client config is loaded in the Compose plugin implementation as the --config flag is now unsupported.
docker compose version
Docker Compose version v2.2.3

docker --config /tmp/.docker compose ls
unknown flag: --config

DOCKER_CONFIG=/tmp/.docker docker compose ls
... displaying stacks ...

Not to be merged yet, but can be merged when we decide to bump up the version of the Compose plugin embedded in Portainer.

We use this method now in compose v2 plugin so this PR is no longer needed.

authors: deviantony hookenz

repo: portainer/docker-compose-wrapper


text:
Edge Groups - remove ability to add non-swarm endpoints to an edge group

Right now, the "edge compute" features leverage the Docker Swarm API to deploy stack files; if the edge endpoint is NOT running swarm, the edge stack deployment will sit pending forever (even if you try to deploy a v2 compose file)
We should introduce a filter to the edge groups page, which does not display edge agents that are not running Swarm. This will stop users creating an environment that will ultimately fail.

@deviantony How do you do the difference between edge swarm and edge non swarm endpoint ? Is there a route to call ? EndpointTypes is : 4 (EdgeAgentOnDockerEnvironment). There is nothing to differentiates swarm and non swarm inside endpoint object.

cc @chiptus can you help Alice on that one?

Sure, I'll reach her on slack

We have a boolean, that is available only when a snapshot is available. Inside Endpoint.Snapshots[].Swarm.
@deviantony what should we do with endpoints that didn't get a snapshot yet?

@Xuorg @chiptus putting this one in stand-by again as we need to find a way to support agents without snapshots.
I'll plan to discuss that one, maybe we can enhance the agent poll request to send the platform information (Docker standalone, Docker Swarm, Kubernetes...)

Closed in favor of https://github.com/portainer/portainer/issues/4648

authors: Xuorg chiptus deviantony ncresswell

repo: portainer/portainer

license: Zlib


text:
feat(home): show cpu and ram for non local endpoints EE-2077

feat(home): show cpu and ram for non local endpoints EE-2077

Result after this change:


text:
http: use requests to handle redirects

Raw use of httplib does not respect the 3xx status codes which may
result in 200 at the end. Use requests to handle any redirects and loop
detection.

Looking again, it wasn't so much. Addresses #193.

Obsolete, has been resolved without pulling requests.

authors: mathstuf posativ

repo: posativ/isso

license: mit


text:
Update Kubernetes from v1.12.3 to v1.13.0

Update Kubernetes from v1.12.3 to v1.13.0

https://github.com/poseidon/terraform-render-bootkube/pull/94

Testing

[x] v1.13.0-beta.1
[x] v1.13.0-rc.2
[x] v1.13.0

Can't run CNCF validation, its not published yet.
Back-off pulling image "gcr.io/heptio-images/sonobuoy:v0.13.0"

repo: poseidon/typhoon


text:
🛑 ma is down

In 9661f09, ma ($MA_API_URL) was down:

HTTP code: 404
Response time: 170 ms

Resolved: ma is back up in 68579b4.

repo: positive-infinity/api-status


text:
PATCH tests

Sorry :(

Good catch, I should have caught that! Thanks... Let me figure out why tests aren't running on circle.

Closing, commits are now in #23. Thanks!

authors: alexfreska possibilities

repo: possibilities/micro-cors


text:
$instagram->getAccount() no longer working

Data returned from $instagram->getAccount() is no longer of the expected format.
Use $instagram->getAccountInfo() instead and it seems to work as it did before.

Is there a more proper way to do that
I mean usinbg the 'https://www.instagram.com/{username}' and get data from it
instead of
'https://www.instagram.com/{}/?__a=1&__d=dis'
direct call with parameters might cause blocks.

Is there a more proper way to do that I mean usinbg the 'https://www.instagram.com/{username}' and get data from it instead of 'https://www.instagram.com/{}/?__a=1&__d=dis'
direct call with parameters might cause blocks.

Thanks - I will give it another try , any recommendations for best use ?

If you just need to retrieve public IG profile info , and last 12 posts, check https://github.com/skmachine/instagram-php-scraper - it does not require your IG auth details and uses cloud proxies to access public data (requires subscription). Note that this new package won't help if you need to extract followers or emails (as these endpoints require authentication).

authors: instasck jhob101 skmachine

repo: postaddictme/instagram-php-scraper


text:
Lint CSS code with stylelint (as part of the boilerplate)?

The boilerplate issue mentions adding structured CSS.
Do you want me to submit a PR that adds linting to each component's CSS, using stylelint and the stylelint-config-standard? Although the config won't help enforce the use of CSS Modules, it will catch little coding mistakes like accidental shorthand overrides and invalid hex colours.
As an aside, it's awesome to see stylelint get a mention in the early mock-up designs! :)

Yeah sure, sgtm!

Good idea

authors: MoOx jeddy3 mxstbr


text:
adjust postlight insights custom selectors

This PR addresses this issue by adjusting the selectors in Postlight.com's custom selector. I had to expand the main content's selector and then exclude a few elements from within it. That way the hero image gets pulled in as part of the content and can be displayed by the Reader.
Note that the Parser does successfully select the hero image and emit it to the Reader as the lead_image_url, but that the Reader does not make use of that field for anything. So there might be a bigger design/product question to explore there. This is a reasonable fix in the meantime.

What's up with CI on this project? It failed on my last PR too...

(I'm not authorized to merge, BTW.)

Yeah, something went wrong with the CircleCI config. I opened an issue to track it; doesn't seem related to your work specifically. I will merge!

authors: austinmbrown johnholdun

repo: postlight/parser


text:
How can I 'ignore everything except' a set of links

In the Examples section, I've got the 'Do not spider certain links' operation to work.
In my case 'Spidr.site('http://www.parkers.co.uk/', :ignore_links => [/vans/])
Correctly displays all URLs except those starting with /vans/.
However, I really need to also 'ignore' all links EXCEPT for /vans/, so that ONLY /vans/ urls are displayed.
Is this possible?
There are too many possibilities to just add to the list of 'ignore_links', I really need to 'ignore everything except' for /vans/.
thanks!

newbie here - but think using "links" instead of "ignore_links" will do it for you

Hi robfuller
thanks for the reply, but the issue I'm having is that I want to ignore many different sets of links, way too many to individually 'ignore_links' them.
So rather than list them all (50+) using the 'ignore links' command, I'm trying to find an equivalent of a 'ignore all links except'.

Maybe I am not understanding:
url = "http://www.hartehanks.com/about-harte-hanks"
opts = {
:links => [/about-harte-hanks/]
}
Spidr.start_at(url,opts ) do |spider|
spider.every_page { |page|
puts page.url.inspect
}
end
Output:
#<URI::HTTP http://www.hartehanks.com/about-harte-hanks>
#<URI::HTTP http://www.hartehanks.com/about-harte-hanks/leadership>
#<URI::HTTP http://www.hartehanks.com/about-harte-hanks/digital>
#<URI::HTTP http://www.hartehanks.com/about-harte-hanks/community-service>
Where ever you start does need to be in the links list, otherwise there is nothing to scan.

Oh, so I ended up implementing the accept/reject filters kind of weird. https://github.com/postmodern/spidr/blob/00f0ff1864d56bad1352aa43a925bc645f777351/lib/spidr/rules.rb#L41-L47
To solve your immediate problem, I would do something like:
Spidr.site("http://www.parkers.co.uk/vans/") do |agent|
  agent.ignore_urls_like do |url|
    !url.path.start_with?('/vans/')
  end
end

Ideally, it should be possible to to specify links: [%r{^/vans/}], ignore_links: [/./] together. Will probably add that to the spidr 1.0 road map.

authors: DHarls17 postmodern robfuller

repo: postmodern/spidr


text:
🛑 PowBot SDN is down

In ef588db, PowBot SDN (https://api.powbot.org/products) was down:

HTTP code: 502
Response time: 423 ms

Resolved: PowBot SDN is back up in 5a5f19f after 9 minutes.

repo: powbot/status


text:
Block machine witness generation: allow for multiple passes per row

The Poseidon block machine performs many steps of computation in a given row. That currently isn't supported; the witness generation just does once pass over the identities for each row.
With this PR, things work similar to the main state machine: For each row, over all identities until no further progress was made.
The approach I went for is to implement a custom "iterator" that yields steps and receives a message whether or not any progress was made. Perhaps it can be used in the main state machine in the future!
In order to prevent infinite loops, I needed to make the notion of what is a progress stricter (e.g., if the given cell already had a value, that doesn't count as progress). That should also make the ProcessingSequenceCache more effective.

@chriseth The way the ProcessingSequenceCache is used right now is that a sequence (for a given assignment pattern) is only cached if all results could be computed. But usually, the first time the block machine is invoked, that's not the case.
I think the cache could just remember that it wasn't able to complete the query and could return an empty sequence in that case. Do you agree? Should I implement that here?

I'm not sure we should do that. The fact that we were not able to complete the lookup could be also be related to the actual values. I have the feeling that this can be better fixed at the outside: If a lookup returns "could not complete", then the lookups should be invoked in a different order.
I'm mainly worried about the fact that the lookup could work for different input values (instead of a different set of known columns).

I'm mainly worried about the fact that the lookup could work for different input values (instead of a different set of known columns).

I agree. For example, a constraint input * output = 0 would determine the output for input != 0, but not for any other input. This is a general problem of the cache though (it can cache sequences that only work on some inputs, i.e., return false positives).
However, if we assume that the lookup columns can be partitioned into input and output columns (in the sense that input columns should be derived by the main machine and output columns can always be derived by the block machine if all inputs are set), then I think caching that no output could be derived for a given set of input columns should be fine, right? Even if it could potentially be derived for different values, the fact that it can't be derived for some values means that the main SM should have figured out more values before calling the block machine. And I think this assumption should hold in all practical cases?
I think this discussion might be out of scope for this PR though :)

@chriseth As discussed, I fixed that duplicate constraints are generated, which let me get rid of the deduplication!
This is done by:

Mutating left to keep track of current assignments, as discussed.
Also keeping track of range constraints of outer polynomials (which were previously ignored). This is a bit weird, because the main state machine might already have range constraints (which the block machine doesn't know about), but I think in the interest of keeping this PR small(ish) it should be sufficient.

To check performance, I ran test_keccak test both on main and this branch:
RUST_LOG=info PILCOM=$(pwd)/pilcom cargo test -r --all keccak -- --include-ignored --nocapture
In both cases, the witness generation took 46s (with 1s resolution from the log timestamps).

authors: chriseth georgwiese

repo: powdr-org/powdr


text:
fix: Ensuring that useQuery's isFetching becomes true after query changes

An issue was found where if the query or parameters change for useQuery, there would be single render cycle where isFetching was false before it became true.
For example:
1. isFetching: false // query changed but the variable is still false
2. isFetching: true // state has been updated
3. isFetching: false // query has finished re-executing

This fix ensures that isFetching is correctly set to true as soon as the hook executes due to a query change.
1. isFetching: true // query change causes hook to execute, compare current query to new query -
track with internal `shouldFetch` variable.
2. isFetching: true // state has been updated
3. isFetching: false // query has finished re-executing

In our case, we had multiple renders with isFetching being incorrectly false in combination with the old stale data, probably due to us having multiple useQuery hooks firing and re-rendering things.
I have tested @Chriztiaan's changes locally, and the latest version in this PR resolves the issue for us.

authors: Chriztiaan fooware

repo: powersync-ja/powersync-js


text:
Update kubernetes/master/golang/master build

This is an automated PR via build-bot

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ltccci
To complete the pull request process, please assign  after the PR has been reviewed.
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
Update kubernetes/master/golang/master build

This is an automated PR via build-bot

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ltccci
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
Update golang/master build

This is an automated PR via build-bot

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ltccci
To complete the pull request process, please assign  after the PR has been reviewed.
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
请大佬添加支持gotify推送

谢谢

已经加上了，还没进行测试，等待下一版发布
https://github.com/pppscn/SmsForwarder/commit/ec726ca8d2c097451f9f0fd05d18b0ea6ae1351c

authors: pppscn spysir

repo: pppscn/SmsForwarder


text:
Normalize line endings to LF

We probably want to do this. Unfortunately it's going to rewrite a lot of files, but kind of unavoidable.

Switches to applying line endings on checkout.
Uses CRLF for c# files for now, although this if likely not needed if users set autocrlf correctly.

Should have no effect on existing PRs (have already tested a merge).
References: https://help.github.com/articles/dealing-with-line-endings/ and https://github.com/boogie-org/boogie/issues/15

Lets do this

authors: peppy smoogipoo

repo: ppy/osu-framework


text:
Add support for AWS SDK v2

Adds a use_v2_sdk field to DynamoMessageOptions that generates AWS SDK v2-compatible MarshalDynamo, MarshalDynamoItem, MarshalDynamoDBAttributeValue, UnmarshalDynamo, UnmarshalDynamoItem, and UnmarshalDynamoDBAttributeValue methods when true.

merged into #21

authors: ennyjfrick pquerna

repo: pquerna/protoc-gen-dynamo


text:
مشکل در لود صفحات

تو تغییرات جدید لینک زیر صفحه سفید نشون میده
https://pullrequest.ir/گفته-های-آرش-خانگلدی-از-اسپاتیفای
و من همجا همین لینک رو شیر دادم که باعث میشه نشه دیدش

بهداد جان پول ریکوئست درحال انتقال به پلتفرم ویرگول هست. دامنه الان روی محتوای منتقل شده به ویرگول لود میشه.
متاسفانه ناچارا آدرس ها تغییر کردن یکم و این مطلب آدرس جدیدش اینه:
https://pullrequest.ir/گفتههای-آرش-خانگلدی-از-اسپاتیفای-sravc7z452ti
داریم روی روشی کار میکنیم که آدرس های قبلی رو بتونیم به مطلب جدید ریدایرکت کنیم.
در همین راستا اگر یوزرنیم خودت در ویرگول رو بهم بدی من مطلب رو به اسم خودت میتونم منتشر کنم.

فکر میکنید چقدر طول بکشه؟
اگر این روش زمان‌بر هست برم و لینک‌هارو تغییر بدم
رو ویرگول هنوز حساب ندارم

فکر میکنم یکی دو روزی طول بکشه چون مشکل فنی هست. به نظرم تغییر آدرس ها روش سریعتریه.

بعد این لینک جدید ممکنه بعدا از کار بی‌افته؟

نه. این لینک جدید همیشه سرپا خواهد بود.

@behdad.222
حساب من در ویرگول

@behdad222 مطلبتون با اکانت خودتون توی آدرس جدید منتشر شد.
https://pullrequest.ir/گفتههای-آرش-خانگلدی-از-اسپاتیفای-sravc7z452ti

repo: pr-techblog/pr-techblog


text:
Build-ability for arm64 platform

It would be extremely helpful to be able to build on arm64/aarch64 docker platform to enable local native use on Apple Silicon and other arm64 platforms without requiring rosetta2 or qemu emulation.

Implementation started.


text:
cardHeight prop not working

Describe the bug
I am adding cardHeight property to the Chrono component but nothing changes with the cards
To Reproduce
Steps to reproduce the behavior:

Add "cardHeight" to Chromo component

Expected behavior
From what I understand, the cardHeight property makes all cards have a certain minimum height. For example if I set it 1000, then all cards will have a minimum of 1000 pixels in height. However, in my case, the cards have the minimum height they need based on the text they occupy not the value I give.
Screenshots
https://imgur.com/a/PHGelk4
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: PC
OS: Windows 10
Browser: Firefox
Version: 1.8.4

I managed a workaround by adding to the cardsubtitle prop a div component instead which consists of text + multiple  to achieved the desired height

I managed a workaround by adding to the cardsubtitle prop a div component instead which consists of text + multiple  to achieved the desired height

@moaazassali this is been fixed with 1.8.5. update the lib and you should be able to set the height.

@moaazassali this is been fixed with 1.8.5. update the lib and you should be able to set the height.

authors: moaazassali prabhuignoto

repo: prabhuignoto/react-chrono


text:
clearing console logs

console.log has been cleared. Can you please review it

Changes merged.

repo: practicalit/ethelp-front


text:
Spacejam fails with "there is no route for the path: /local"

When I try running node_modules/spacejam/bin/spacejam test --driver-package=practicalmeteor:mocha-console-runner --loglevel debug, I get the following error: phantomjs: There is no route for the path: /local
Full output:
node_modules/spacejam/bin/spacejam test            --driver-package=practicalmeteor:mocha-console-runner --loglevel debug
Spacejam.constructor()
CLI.constructor()
CLI.exec()
command: test
CLI.exec() options: { 'driver-package': 'practicalmeteor:mocha-console-runner',
  loglevel: 'debug',
  packages: [],
  command: 'test' }
Spacejam.testPackages() { 'driver-package': 'practicalmeteor:mocha-console-runner',
  loglevel: 'debug',
  packages: [],
  command: 'test' }
{ 'phantomjs-script': 'phantomjs-test-in-console.js',
  'phantomjs-options': '--load-images=no --ssl-protocol=TLSv1',
  'driver-package': 'practicalmeteor:mocha-console-runner',
  loglevel: 'debug',
  packages: [],
  command: 'test' }
Meteor.runTestCommand() { '0': 'test',
  '1':
   { 'phantomjs-script': 'phantomjs-test-in-console.js',
     'phantomjs-options': '--load-images=no --ssl-protocol=TLSv1',
     'driver-package': 'practicalmeteor:mocha-console-runner',
     loglevel: 'debug',
     packages: [],
     command: 'test' } }
meteor options: { dir: '.',
  port: 4096,
  packages: [],
  'driver-package': 'practicalmeteor:mocha-console-runner',
  'meteor-ready-text': '=> App running at:',
  'meteor-error-text': 'Waiting for file change.',
  'phantomjs-script': 'phantomjs-test-in-console.js',
  'phantomjs-options': '--load-images=no --ssl-protocol=TLSv1',
  loglevel: 'debug',
  command: 'test' }
meteor cwd=/Users/noah/Projects/my-app/app
Meteor.getTestArgs() { dir: '.',
  port: 4096,
  packages: [],
  'driver-package': 'practicalmeteor:mocha-console-runner',
  'meteor-ready-text': '=> App running at:',
  'meteor-error-text': 'Waiting for file change.',
  'phantomjs-script': 'phantomjs-test-in-console.js',
  'phantomjs-options': '--load-images=no --ssl-protocol=TLSv1',
  loglevel: 'debug',
  command: 'test' }
meteor args= [ 'test',
  '--driver-package',
  'practicalmeteor:mocha-console-runner',
  '--port',
  4096 ]
ChildProcess.constructor()
ChildProcess.spawn() meteor [ 'test',
  '--driver-package',
  'practicalmeteor:mocha-console-runner',
  '--port',
  4096 ]
spacejam: spawning meteor
[[[[[ Tests ]]]]]

=> Started proxy.
=> Started MongoDB.
MeteorMongodb.constructor() { '0': 55741 }
MeteorMongodb.findAllChildren() {}
@meteorPid 55741
spacejam: meteor mongodb is ready
Found meteor mongod child with pid:  55760
I20160720-08:50:12.450(-7)? info: Initialized testing logger
I20160720-08:50:14.226(-7)? info: Initialized logger
I20160720-08:50:14.841(-7)? Kadira: completed instrumenting the app
I20160720-08:50:14.851(-7)? Cannot connect to Rollbar API as the following environment variables are not available: [ ROLLBAR_SERVER_ACCESS_TOKEN ]
=> Started your app.

=> App running at: http://localhost:4096/
spacejam: meteor is ready
Spacejam.runPhantom()
Phantomjs.run() { '0': 'http://localhost:4096/local',
  '1': '--load-images=no --ssl-protocol=TLSv1',
  '2': 'phantomjs-test-in-console.js',
  '3': undefined,
  '4': undefined,
  '5': false }
script=/Users/noah/Projects/my-app/app/node_modules/spacejam/lib/phantomjs-test-in-console.js
spawnArgs: [ '--load-images=no',
  '--ssl-protocol=TLSv1',
  'phantomjs-test-in-console.js' ]
spawnOptions: { cwd: '/Users/noah/Projects/my-app/app/node_modules/spacejam/lib',
  detached: false,
  env:
   { TERM_SESSION_ID: 'w0t0p1:6D33DA9C-73AE-4520-B9AF-A263F8896836',
     SSH_AUTH_SOCK: '/private/tmp/com.apple.launchd.JC8o9ezxw5/Listeners',
     Apple_PubSub_Socket_Render: '/private/tmp/com.apple.launchd.PYSVfq9IQE/Render',
     COLORFGBG: '7;0',
     ITERM_PROFILE: 'Default',
     XPC_FLAGS: '0x0',
     LANG: 'en_US.UTF-8',
     PWD: '/Users/noah/Projects/my-app/app',
     SHELL: '/bin/zsh',
     SECURITYSESSIONID: '186a7',
     TERM_PROGRAM_VERSION: '3.0.4',
     TERM_PROGRAM: 'iTerm.app',
     PATH: '/Users/noah/.nvm/versions/node/v4.2.2/bin:/Users/noah/.rbenv/shims:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/sm/bin:/Users/noah/bin:/Applications/mysql-5.5.27/client',
     COMMAND_MODE: 'unix2003',
     TERM: 'xterm',
     HOME: '/Users/noah',
     TMPDIR: '/var/folders/p4/466pgnmx7sd_2qwwwl2vc33m0000gn/T/',
     USER: 'noah',
     XPC_SERVICE_NAME: '0',
     LOGNAME: 'noah',
     ITERM_SESSION_ID: 'w0t0p1:6D33DA9C-73AE-4520-B9AF-A263F8896836',
     __CF_USER_TEXT_ENCODING: '0x1F5:0x0:0x0',
     SHLVL: '1',
     OLDPWD: '/Users/noah/Projects/my-app/app',
     JAVA_HOME: '/usr',
     NVM_DIR: '/Users/noah/.nvm',
     NVM_NODEJS_ORG_MIRROR: 'https://nodejs.org/dist',
     NVM_IOJS_ORG_MIRROR: 'https://iojs.org/dist',
     MANPATH: '/Users/noah/.nvm/versions/node/v4.2.2/share/man:/usr/local/share/man:/usr/share/man:/Applications/mysql-5.5.27/man:/Applications/Xcode.app/Contents/Developer/usr/share/man:/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/share/man',
     NVM_PATH: '/Users/noah/.nvm/versions/node/v4.2.2/lib/node',
     NVM_BIN: '/Users/noah/.nvm/versions/node/v4.2.2/bin',
     MARKPATH: '/Users/noah/.marks',
     PAGER: 'less',
     LESS: '-R',
     LC_CTYPE: 'en_US.UTF-8',
     LSCOLORS: 'Gxfxcxdxbxegedabagacad',
     DOCKER_HOST: 'tcp://:2376',
     DOCKER_CERT_PATH: '/Users/noah/.docker/machine/machines/dinghy',
     export: '',
     DOCKER_TLS_VERIFY: '1',
     DOCKER_MACHINE_NAME: 'dinghy',
     _: '/Users/noah/Projects/my-app/app/node_modules/spacejam/bin/spacejam',
     ROOT_URL: 'http://localhost:4096/local' } }
ChildProcess.constructor()
ChildProcess.spawn() phantomjs [ '--load-images=no',
  '--ssl-protocol=TLSv1',
  'phantomjs-test-in-console.js' ]
spacejam: spawning phantomjs

phantomjs: Running tests at http://localhost:4096/local using test-in-console
phantomjs: There is no route for the path: /local
    http://localhost:4096/packages/dispatch_mocha-phantomjs.js?hash=c9d8b77a2be80f5c71341225eac2fea43a33dc93: 214

ChildProcess.process.on 'exit': @command=phantomjs @killed=false code=6 signal=null
spacejam: phantomjs exited with code: 6
Meteor.kill() {} @childProcess?= true @mongodb?= true
ChildProcess.kill() signal=SIGTERM @command=meteor @killed=false
spacejam: killing meteor
MeteorMongodb.kill() killed= false
Spacejam.done() { '0': 6 }
Spacejam.done() @meteor?=true
Meteor.hasMongodb()
MeteorMongodb.hasMongodb()
Spacejam.done() @waitForMeteorMongodbKillDone=true
Spacejam.done() waiting for mongodb to exit before calling done
ChildProcess.process.on 'exit': @command=meteor @killed=true code=null signal=SIGTERM
spacejam: meteor killed with signal: SIGTERM
Spacejam.meteor.on 'exit': { '0': null, '1': 'SIGTERM' }
Spacejam.onMeteorMongodbKillDone() 6
spacejam: Unhandled error in meteor client side code. Exiting.
ChildProcess.process.on 'exit': @command=meteor @killed=true code=6
ChildProcess.kill() signal=SIGTERM @command=meteor @killed=true
MeteorMongodb.process.on 'exit': code=6
MeteorMongodb.kill() killed= true
ChildProcess.process.on 'exit': @command=phantomjs @killed=true code=6
ChildProcess.kill() signal=SIGTERM @command=phantomjs @killed=true

Can you tell us what is the content of your .meteor/packages & .meteor/versions & .meteor/release ?
I think it's related to dispatch:mocha-phantomjs, maybe you can't get them alonside.
http://localhost:4096/packages/dispatch_mocha-phantomjs.js
If that doesn't help, can you check if you have the same error with meteor test --driver-package=practicalmeteor:mocha, on your browser console ?

.meteor/packages
# Meteor packages used by this project, one per line.
# Check this file (and the other files in this directory) into your repository.
#
# 'meteor add' and 'meteor remove' will edit this file for you,
# but you can also edit it by hand.

meteor-base             # Packages every Meteor app needs to have
mobile-experience       # Packages for a great mobile UX
mongo                   # The database Meteor supports right now
session                 # Client-side reactive dictionary for your app
jquery                  # Helpful client-side library
tracker                 # Meteor's client-side reactive programming library

es5-shim                # ECMAScript 5 compatibility for older browsers.
ecmascript              # Enable ECMAScript2015+ syntax in app code

sanjo:jasmine@1.0.1
twbs:bootstrap
promise

http
peerlibrary:xml2js
blaze-html-templates
aldeed:collection2
accounts-password
dburles:collection-helpers
matb33:collection-hooks
kadira:flow-router
kadira:blaze-layout
meteorhacks:fast-render
fortawesome:fontawesome
alanning:roles
aldeed:autoform
check
arillo:flow-router-helpers
testing
percolate:synced-cron
brentjanderson:winston-client
saucecode:rollbar
kadira:debug
meteorhacks:kadira
mdg:validated-method
tunifight:loggedin-mixin
yogiben:autoform-modals
jcbernack:reactive-aggregate
percolate:migrations
msavin:mongol
lookback:emails
meteorhacks:aggregate
zimme:active-route
useraccounts:bootstrap
useraccounts:flow-routing
u2622:persistent-session
standard-minifier-css
standard-minifier-js
xolvio:cleaner
practicalmeteor:chai
practicalmeteor:mocha
dispatch:mocha-phantomjs
dburles:factory
practicalmeteor:sinon
lmieulet:meteor-coverage
practicalmeteor:mocha-console-runner

.meteor/versions
accounts-base@1.2.8
accounts-password@1.1.13
alanning:roles@1.2.15
aldeed:autoform@5.8.1
aldeed:collection2@2.9.1
aldeed:collection2-core@1.1.1
aldeed:schema-deny@1.0.1
aldeed:schema-index@1.0.1
aldeed:simple-schema@1.5.3
allow-deny@1.0.5
amplify@1.0.0
arillo:flow-router-helpers@0.5.2
autoupdate@1.2.11
babel-compiler@6.8.5
babel-runtime@0.1.9_1
base64@1.0.9
binary-heap@1.0.9
blaze@2.1.8
blaze-html-templates@1.0.4
blaze-tools@1.0.9
boilerplate-generator@1.0.9
brentjanderson:winston-client@0.2.1
caching-compiler@1.0.6
caching-html-compiler@1.0.6
callback-hook@1.0.9
check@1.2.3
chuangbo:cookie@1.1.0
coffeescript@1.1.4
dburles:collection-helpers@1.0.4
dburles:factory@1.0.0
dburles:mongo-collection-instances@0.3.4
ddp@1.2.5
ddp-client@1.2.9
ddp-common@1.2.6
ddp-rate-limiter@1.0.5
ddp-server@1.2.10
deps@1.0.12
diff-sequence@1.0.6
dispatch:mocha-phantomjs@0.1.7
dispatch:phantomjs-tests@0.0.5
ecmascript@0.4.8
ecmascript-runtime@0.2.12
ejson@1.0.12
email@1.0.16
es5-shim@4.5.13
fastclick@1.0.12
fortawesome:fontawesome@4.5.0
geojson-utils@1.0.9
hot-code-push@1.0.4
html-tools@1.0.10
htmljs@1.0.10
http@1.1.8
id-map@1.0.8
infinitedg:winston@0.7.3
jcbernack:reactive-aggregate@0.6.0
jquery@1.11.9
kadira:blaze-layout@2.3.0
kadira:debug@3.2.2
kadira:flow-router@2.12.1
kadira:runtime-dev@0.0.1
lai:collection-extensions@0.1.4
launch-screen@1.0.12
less@2.6.5
livedata@1.0.18
lmieulet:meteor-coverage@0.8.1
localstorage@1.0.11
logging@1.0.14
lookback:emails@0.7.4
matb33:collection-hooks@0.8.1
mdg:validated-method@1.1.0
mdg:validation-error@0.2.0
meteor@1.1.16
meteor-base@1.0.4
meteorhacks:aggregate@1.3.0
meteorhacks:collection-utils@1.2.0
meteorhacks:fast-render@2.14.0
meteorhacks:inject-data@2.0.0
meteorhacks:kadira@2.30.0
meteorhacks:meteorx@1.4.1
meteorhacks:picker@1.0.3
meteorhacks:ssr@2.2.0
meteortoys:toykit@2.2.1
minifier-css@1.1.13
minifier-js@1.1.13
minimongo@1.0.17
mobile-experience@1.0.4
mobile-status-bar@1.0.12
modules@0.6.5
modules-runtime@0.6.5
momentjs:moment@2.13.1
mongo@1.1.9_1
mongo-id@1.0.5
mongo-livedata@1.0.12
mpowaga:string-template@0.1.0
msavin:mongol@1.6.2
npm-bcrypt@0.8.6_3
npm-mongo@1.4.45
observe-sequence@1.0.12
ordered-dict@1.0.8
peerlibrary:blocking@0.5.2
peerlibrary:xml2js@0.4.8_1
percolate:migrations@0.9.8
percolate:synced-cron@1.3.2
practicalmeteor:chai@2.1.0_1
practicalmeteor:loglevel@1.2.0_2
practicalmeteor:mocha@2.4.5_6
practicalmeteor:mocha-console-runner@0.2.1
practicalmeteor:mocha-core@1.0.1
practicalmeteor:sinon@1.14.1_2
promise@0.7.3
raix:eventemitter@0.1.3
raix:handlebar-helpers@0.2.5
random@1.0.10
rate-limit@1.0.5
reactive-dict@1.1.8
reactive-var@1.0.10
reload@1.1.10
retry@1.0.8
routepolicy@1.0.11
sacha:juice@0.1.4
sanjo:jasmine@1.0.1
saucecode:rollbar@0.5.8
service-configuration@1.0.10
session@1.1.6
sha@1.0.8
softwarerero:accounts-t9n@1.3.4
spacebars@1.0.12
spacebars-compiler@1.0.12
srp@1.0.9
standard-minifier-css@1.0.8
standard-minifier-js@1.0.8
stevezhu:lodash@3.10.1
templating@1.1.14
templating-tools@1.0.4
testing@0.1.0
tmeasday:test-reporter-helpers@0.2.1
tracker@1.0.15
tunifight:loggedin-mixin@0.1.0
twbs:bootstrap@3.3.6
u2622:persistent-session@0.4.4
ui@1.0.11
underscore@1.0.9
url@1.0.10
useraccounts:bootstrap@1.14.2
useraccounts:core@1.14.2
useraccounts:flow-routing@1.14.2
velocity:reports@1.0.0
webapp@1.2.11
webapp-hashing@1.0.9
xolvio:cleaner@0.3.1
yogiben:autoform-modals@0.3.8
zimme:active-route@2.3.2

.meteor/release
METEOR@1.3.5.1

meteor test --driver-package=practicalmeteor:mocha works just fine
[[[[[ Tests ]]]]]

=> Started proxy.
=> Started MongoDB.
I20160724-21:55:29.280(-7)? info: Initialized testing logger
I20160724-21:55:31.372(-7)? info: Initialized logger
I20160724-21:55:32.019(-7)? Kadira: completed instrumenting the app
I20160724-21:55:32.028(-7)? Cannot connect to Rollbar API as the following environment variables are not available: [ ROLLBAR_SERVER_ACCESS_TOKEN ]
=> Started your app.

=> App running at: http://localhost:3000/
I20160724-21:56:35.695(-7)? info: Initialized logger
I20160724-21:56:35.910(-7)? MochaRunner.runServerTests: Starting server side tests with run id yaDcGkv2cMgWTiX9F

(it runs my tests just fine)

Related to https://github.com/serut/meteor-coverage-app-exemple/issues/1

authors: noahsw serut

repo: practicalmeteor/spacejam


text:
Manual da con-design

Precisamos detalhar o passo a passo dos trabalhos desenvolvidos dentro da equipe, além de contribuir com dicas e informações relevantes quanto aos métodos, programas e sites que utilizamos.
Todos devem contribuir na criação, @minieradka @lucasfrarao.
O registro será adicionado em um grande manual de funcionamento de todas as equipes, que está sendo criado na issue #671.
Estão convidadas @morgana-mo @anacarolinamorigi a contribuírem também, já que estão auxiliando a equipe e acompanhando alguns processos.

Criei as pastas dessa issue no Google Drive:

 Pasta da issue
🔽 Entrada
🔼 Saída

dei uma boa editada no arquivo acredito que o que já está escrito não necessite alterações, apenas a revisão gramatical feita pela con-con. Falta agora adicionar mais informações  de uns alguns  tópicos restantes (são poucos como diagramação como organizar uma paleta de cores e tipografia, símbolos e elementos visuais e assim já vai estar bem completo

Gurias, estava olhando essa issue, vocês necessitam da revisão da @practice-uffs/con-conteudo ?

Gurias, estava olhando essa issue, vocês necessitam da revisão da @practice-uffs/con-conteudo ?

Acredito que sim, mas ainda não finalizamos o texto.

Gurias, estava olhando essa issue, vocês necessitam da revisão da @practice-uffs/con-conteudo ?

Acredito que sim, mas ainda não finalizamos o texto.

Ah, perfeito! Assim que for finalizado, só marcar então. Ficamos no aguardo :)

@minieradka arrasou nas informações adicionadas no manual!!!!
Dei uma boa organizada, falta adicionar algumas informações ainda, quanto ao tamanho sugerido para alguns arquivos e também a experiências em relação ao mural v2.

Oi pessoal! Fiz a leitura do manual e gostei bastante! Acredito que esteja bem explicado e aborda questões bem pertinentes sobre o trabalho da equipe. Fiz pontuações e sugestões ao longo do documento que está no drive. Mas em geral achei ótimo! A leitura do manual já deu uma refrescada na minha memória e sei que vai ajudar ainda mais novos membros! :D

Boa noite!!
Primeiramente gostaria de pedir desculpas pela demora para fazer a análise do manual. Como falei na reunião, estou no final do semestre aqui no campus PF e (pra piorar kkk) apresento meu TCC na próxima semana, por isso estou bem apurado.
Achei o manual bem bom e bem explicativo, acrescentei alguns apontamentos e fiz algumas correções bobas por questão de TOC. Acredito que mais coisa precisará ser alteradas após a ativação do V2 do Mural, mas como ainda não sabemos ao certo como tudo isso funcionará na prática, acredito que é vantajoso fazermos essas alterações e acréscimos somente após o período de adaptação ao novo Mural.

Queria agradecer mais uma vez pelas contribuições que vocês fizeram para o nosso manual, está ficando muito bom!! Vocês arrasaram!
@luizdameda, você sugeriu que explicássemos sobre o Canva, poderia escrever um pouco sobre? Depois que concluir estará disponível para a revisão de texto.

Queria agradecer mais uma vez pelas contribuições que vocês fizeram para o nosso manual, está ficando muito bom!! Vocês arrasaram!
@luizdameda, você sugeriu que explicássemos sobre o Canva, poderia escrever um pouco sobre? Depois que concluir estará disponível para a revisão de texto.

Claro, posso sim!!!! Até a próxima reunião já deixo isso pronto

Acrescentei informações a respeito do Canva. Peço que deem uma lida e vejam se está ok. Talvez eu tenha me empolgado e escrito um pouco demais porque amo o programa kkk

Ficou muito bom Luiz!!! Muito obrigada pela contribuição.
Agora podemos encaminhar para a revisão de texto, alguém da @practice-uffs/con poderia adicionar o nosso manual para a fila de revisões de vocês? Ficamos no aguardo da finalização da revisão para encerrar a issue.

Ficou muito bom Luiz!!! Muito obrigada pela contribuição.
Agora podemos encaminhar para a revisão de texto, alguém da @practice-uffs/con poderia adicionar o nosso manual para a fila de revisões de vocês? Ficamos no aguardo da finalização da revisão para encerrar a issue.

Perfeito, Tay! Como combinado, as revisões ficarão para início do ano, para que possamos focar nas atividades da AURA. Eu mesma farei a revisão :)

Boa noite pessoal da @practice-uffs/con-design. Na última reunião da equipe con-conteúdo conversei com a @GessicaZanon e disse que estava curiosa para ler o manual de vocês. Comecei a ler e acabei por revisar também. Já deixei algumas contribuições e dúvidas em comentários no arquivo, mas ainda não terminei a revisão.
Logo que terminar eu aviso aqui.

Boa tarde, pessoal da @practice-uffs/con-design .
Finalizei a revisão do manual. Gostaria de parabenizar pela organização e explicação das ferramentas e processos. Está muito legal.
Deixei sugestões para algumas partes que pensei poderem ficar mais claras, e outras que não sei se compreendi direito. Por isso, já aviso que podem entrar em contato caso tenham qualquer dúvida.
Tem algumas partes em que comentei como seria interessante se fossem passados materiais sobre o tema, ou algum link para pesquisas preliminares, como no caso da tipografia. Também acho interessante linkar os materiais dos layouts padrões que vocês desenvolveram. Está tudo comentado no manual.
Uma coisa que mudou bastante foram as palavras estrangeiras (em inglês), que coloquei em itálico. Posso passar a lista das que observei, caso queiram.
Eu não revisei nomes de plugins e ferramentas, pois não sou muito familiarizada com o Figma.
Pelo que testei, todos os links estão funcionando.
Reforçando, qualquer dúvida, estou à disposição.

Boa tarde, pessoal da @practice-uffs/con-design . Finalizei a revisão do manual. Gostaria de parabenizar pela organização e explicação das ferramentas e processos. Está muito legal. Deixei sugestões para algumas partes que pensei poderem ficar mais claras, e outras que não sei se compreendi direito. Por isso, já aviso que podem entrar em contato caso tenham qualquer dúvida.
Tem algumas partes em que comentei como seria interessante se fossem passados materiais sobre o tema, ou algum link para pesquisas preliminares, como no caso da tipografia. Também acho interessante linkar os materiais dos layouts padrões que vocês desenvolveram. Está tudo comentado no manual.
Uma coisa que mudou bastante foram as palavras estrangeiras (em inglês), que coloquei em itálico. Posso passar a lista das que observei, caso queiram.
Eu não revisei nomes de plugins e ferramentas, pois não sou muito familiarizada com o Figma. Pelo que testei, todos os links estão funcionando.
Reforçando, qualquer dúvida, estou à disposição.

Obrigada Eweline pela revisão, alterações realizadas!

authors: Eweline GessicaZanon PracticeUFFSBot TaynaraCh kamila-rosa luizdameda minieradka

repo: practice-uffs/programa


text:
Regenerate PO files

@saeedmb8 | @miltontony  Please review

👍

repo: praekelt/molo-iogt


text:
Looking for maintainers

As evidenced by the growing number of issues and PRs on this project, I've not been able to keep up with growing and maintaining this library. I'm quite occupied with other projects at the moment and do not see myself freeing up to work on this library in the foreseeable future.
Instead of letting it languish, I was hoping if someone would be interested in maintaining this library and working with the community. You'll be added as a project collaborator and will have full freedom to take the library in any direction that you want.
If any of this sounds interesting, drop me an email (which is on my profile) and we can take this forward.
Thanks for showing interest!

Hi Prakhar,
I will try to maintain this library and will help with coding. Please let me know what are expected from me so that I can understand the role better.

Hi Prakhar,
I'm interested in maintaining react-tags. I sent you an email.

@dehlen Is there something you are waiting for in particular? :)

Just an update: Daniel (mrdannael) has volunteered to be a maintainer of this library going forward! Thank you very much Daniel! 🎉

@prakhar1989  why not merge this project with https://github.com/olahol/react-tagsinput


text:
Footer 37

Adding responsive footer Issue  #37

Close #37

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

can we also add a new file with code included in it?

repo: pranjay-poddar/Dev-Geeks


text:
Added Bank Management System [GSSOC'23]

Title and Issue number
Bank Management System
Issue #3190
Close #3190
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md

@pranjay-poddar @MohitGupta121 Please review and merge it.
And add the gssoc23 label and level label.

@MohitGupta121 @TusharKesarwani  Please review and merge it.
And add the gssoc23 label and level label.


text:
Frontend Project "Task manager" 'Add task' Button Design

Title and Issue number
Frontend Project "Task manager" 'Add task' Button Design
Close #3415
Output
Before

After

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md

@MohitGupta121 Kindly review this pr.


text:
🛑 ChatGPT + DALL-E is down

In 139ffaf, 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 92ee5e3 after 6 minutes.

repo: prateekralhan/status


text:
GPS work ?

I saw in your photos the connector of GPS.
But work GPS with your firmware ?

Not yet.

authors: pratikPhadte skimans


text:
Minor improvements to Rules

Few documentation touchups

Thanks! 🎆

authors: PythonCoderAS bboe

repo: praw-dev/praw


text:
createNuxtPersistedState SSR states empty (not working)

Describe the bug
The states are only restored from cookie at the client side.
Anything that is rendered on server side like,
any code that runs  on created hook or earlier doesn't have the states available
You can see it if you console.log it.
This means, middleware and plugins store will return an empty state on page load as well.
Reproduction
Install @pinia/nuxt 0.2.0 together with pinia 2.0.15
Tested with pinia-plugin-persisted: 1.6.3 and 2.1.0
with 2.1.0 i get the following error

System Info
System:
    OS: macOS 12.3
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 20.51 GB / 64.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.7.0 - /usr/local/bin/node
    Yarn: 3.2.1 - /usr/local/bin/yarn
    npm: 8.15.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 104.0.5112.79
    Firefox: 103.0
    Safari: 15.4

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible of the bug.

May I send a pull request that fixes this issue?
Also, this might be addressed a little bit as well https://github.com/prazdevs/pinia-plugin-persistedstate/issues/84
I placed an option to store multiple cookies to increase the 4096 bytes limit. But due note that if a lot of huge cookies are placed in the header that it will still throw an error that header is too big.
Lastly, I used https://github.com/microcipcip/cookie-universal/tree/master/packages/cookie-universal-nuxt
to persist the changes to the cookie in the client side when changes were made during SSR.

Can you provide a repo or a stackblitz to reproduce the error ?

Hello @prazdevs I'll create a PR so you can see how I fixed it on my end.
Give me a moment

Hello @prazdevs
Here's how it should look.
This is my plugin

This should be nuxt.mjs

it's just throwing some errors now because of optional chaining.

Hello @prazdevs Please check https://github.com/prazdevs/pinia-plugin-persistedstate/pull/99
Though i still have a minor issue.
Do you have discord?

Hello @prazdevs Please check #99
Though i still have a minor issue. Do you have discord?

I'm kinda busy with tons of stuff atm but i do have discord at PraZ#4184

No worries @prazdevs
Well my question is,
I'm using this as my current nuxt plugin setup

Everything works fine. Also, I can access everything at nuxt midldleware too.
Serverside changes to cookie is being reflected to client side cookie as well.
Now, I just tried editing the node_modules file dist/nuxt.mjs
Refactored my this to work as a plugin.
Everything is working except, I can't access it inside a middleware.
Please refer to my PR and see if it's the same with you since in the PR i edited the nuxt.ts and not the mjs file.

There is one problem tho, is that i do want to enforce the "0 external dependency" policy on the plugin/repo. Leaving the choice of external libs to the user. However what could be worked on are helpers to integrate these external libs into the plugin. If that makes sense

@prazdevs I understand where you're coming from. The only problem is that useCookie by nuxt doesn't work properly across server to client cookie management.
This only works properly on client only setup.

@prazdevs Now I know why in nuxt.mjs everything is not accessible inside a middleware

I just console log trying to cookie get inside the nuxt plugin which registered pinia persisted state and inside the node_modules/pinia-persistedstate/dist/nuxt.mjs
As you can see, nuxt.mjs doesn't get called in server side
nuxt.mjs calls the createPersistedState in this case.
However, if i use createPersistedState directly in the nuxt plugin like so

You'll see that getItem is also being called in server side, which restores the state and makes everything available in a middleware or any server side script

If the issue is from the nuxt-cookie, maybe we should see if there's an issue in their repo and look for a fix over there ? or at least be sure it is meant to behave taht way

@prazdevs  it's a different issue not related to nuxt cookie

v3 is now release with available nuxt module as well! docs are also deployed 🚀
closing this for now, if still having issues, feel free to reopen

repo: prazdevs/pinia-plugin-persistedstate


text:
Confusing error message when specifying two contradictory specs

This example is obvious but it can get more complicated quickly:
$ cargo r -- "requests>2.2" "requests<2.1"
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/rip 'requests>2.2' 'requests<2.1'`
  × Could not solve for the requested requirements:
  │ The following packages are incompatible
  │ |-- requests < 2.1 can be installed with any of the following options:
  │     |-- requests 2.0.1
  │     |-- requests 2.0.0
  │ |-- requests > 2.2 cannot be installed because there are no viable options:
  │     |-- requests 2.2.1 | 2.3.0 | 2.4.0 | 2.4.1 | 2.4.2 | 2.4.3 | 2.5.0 | 2.5.1 | 2.5.2 | 2.5.3 | 2.6.0 | 2.6.1 | 2.6.2 | 2.7.0 | 2.8.0 | 2.8.1 | 2.9.0 | 2.9.1 | 2.9.2 | 2.10.0 | 2.11.0 | 2.11.1 | 2.12.0 | 2.12.1 | 2.12.2 | 2.12.3 | 2.12.4 | 2.12.5 | 2.13.0 | 2.14.0 | 2.14.1 | 2.14.2 | 2.15.1 | 2.16.0 | 2.16.1
  │ | 2.16.2 | 2.16.3 | 2.16.4 | 2.16.5 | 2.17.0 | 2.17.1 | 2.17.2 | 2.17.3 | 2.18.0 | 2.18.1 | 2.18.2 | 2.18.3 | 2.18.4 | 2.19.0 | 2.19.1 | 2.20.0 | 2.20.1 | 2.21.0 | 2.22.0 | 2.23.0 | 2.24.0 | 2.25.0 | 2.25.1 | 2.26.0 | 2.27.0 | 2.27.1 | 2.28.0 | 2.28.1 | 2.28.2 | 2.29.0 | 2.30.0 | 2.31.0, which conflicts with
  │ the versions reported above.
  │

It appears to be saying that "2.3.0" is not compatible with the spec "requests > 2.2". Which is ofcourse incorrect.
Also would it be possible to put a check in before going out to the index to see if two top level requirements are mutually incompatible?

Thanks for testing! I appreciate it! We'll take a look!

So actually the error message is correct, but it is a bit hard to wrap your head around, I agree :)
So it's saying basically:
requests < 2.1 can be installed with: 2.0.1, 2.0.0
requests > 2.2 can be installed with: 2.2.1 up to 2.31.0, but these conflict with the versions reported in the previous VersionSet

authors: baszalmstra notatallshaw tdejager

repo: prefix-dev/rip


text:
🛑 Beta is down

In 1eb04cf, Beta (https://beta.presquelabs.com) was down:

HTTP code: 400
Response time: 636 ms

Resolved: Beta is back up in 644f926.

repo: presquelabs/upptime


text:
Fix incorrect result for IS DISTINCT FROM optimization

Expressions like "x IS DISTINCT FROM null" get incorrectly
constant-folded to false. The result depends on what value x takes.

@findepi, @sopel39. I changed the approach a bit. I separated the handling of "IS DISTINCT FROM" from the rest so that it's easier to reason about and applied the suggestions from @findepi above. Can you re-review?

repo: prestosql/presto


text:
Dialog changes

Let's make the Dialog component a bit more flexible with content. Right now, it always renders a grey header at the top of the component - I propose we make that optional or a sub component of Dialog, so that teams who have a bit of a different look can still use Dialog

To avoid a breaking change, we could do something like having a prop called noHeader - but I'm also not opposed to shipping a breaking change for this one either

Closed by #736

authors: BinaryMuse emplums

repo: primer/components


text:
bug: arbiter bind should generate bindings for contract dependencies

Description
arbiter bind will only generate bindings for contracts inside the contracts directory.
Steps to reproduce

arbiter init test-project && cd test-project
forge install primitivefinance/portfolio (this will create a submodule in the lib directory)
arbiter bind

Expected Behavior
The portfolio bindings are generated in src/bindings.
What actually happens
Bindings are only generated for the std-*.sol and Counter.sol contracts, but not for lib/portfolio.

As an add-on, I think it would be nice to specify which specific contracts you want to have bindings generated for (if you want). Having extraneous contracts is a bit of a headache sometimes. We could do this with some type of config file or even add it to a Foundry.toml.

authors: Autoparallel kinrezC

repo: primitivefinance/arbiter


text:
fix: failing tests

Problem
Tests seem to be failing, we need to fix them.

Steps to reproduce
See the README badge.
Expected behavior
Should be green not red!

Closed by rerunning test action. kek


text:
"GraphQL Playground" is damaged and can't be opened.

This issue pertains to the following package(s):

[x] GraphQL Playground - Electron App

1.8.5 release on macOS comes through as "damaged". I've tried twice to download it.

I had similar issues when I download the zip file too  (see screenshot), at first didn't even see the dmg file only the zipped one. Must be some issues with the default extractor on mac

i 've tried the .zip app(from www.electronjs.org) and faced to the issues above, then finding issue here, then i 've tred the .dmg one  now but it still not working but only showing a empty black app screen.

For me the solution was the ZIP version but only unzipped using macOS "Archive Utility"

authors: cdll kepi0809 lunelson

repo: prisma-labs/graphql-playground


text:
Production ready examples

Hey
Would anyone be interested in helping out adding some build scripts for the examples? I noticed they mostly use ts-node-dev which isn’t ideal for deployment.

Would anyone be interested in helping out adding some build scripts for the examples? I noticed they mostly use ts-node-dev which isn’t ideal for deployment.

Yes, I think we should definitely add/link to more examples of real world apps. One thing I wanted to point out, is that node -r ts-node/register/transpile-only app.ts is actually a fairly reasonable option depending on your environment and needs, it eliminates the confusion of the build step and the potential of things falling out of sync in development, which can be confusing to debug.
Obviously, YMMV but this is how how all of our Node apps are currently running at Cypress.io (after things are properly type-checked in CI prior to deploy) and it hasn't been an issue, aside from a slightly inflated memory footprint at startup, but overall the overhead of transpiling on the fly has appeared to be negligible.

Use a dictionary to store information about a person you know. Store their first name, last name, age, and the city in which they live. You should have keys such as first_name, last_name, age, and city. Print each piece of information stored in your dictionary. Add a new key value pair about qualification then update the qualification value to high academic level then delete it.
plz HOW CAN MAKE A PROGRAM

authors: hassanshk866 notrab tgriesser

repo: prisma-labs/nexus


text:
feat(automate release)

via PAT https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token

Fixes https://github.com/prisma-labs/vscode-graphql/issues/45

repo: prisma-labs/vscode-graphql


text:
Upsert should allow where clause with only undefined

Bug description
Currently when using upsert, you have to specify at least one argument in the where clause. This is problematic when creating an upsert interface since the id might be undefined/null. This requires us to do something like:
where: { id: id || '' },

Otherwise it throws something like:
Argument where of type MyModelWhereUniqueInput needs at least one argument. Available args are listed in green.

How to reproduce

Take any model
Try to upsert with an undefined id
Failure

Expected behavior
Prisma should treat this case as a create case instead of throwing an error. This would be closer to the expected behaviour. It would be even better to accept null too (currently only undefined is accepted).

Thanks @Sytten for creating this issue. We definitely agree that this is unwieldy.
We're planning to allow undefined in there, but not null. Null has special meaning in many cases, so while it doesn't affect where specifically, it's better to separate them out explicitly.

Thanks @Sytten and thanks @matthewmueller for the answer.
We indeed discussed this internally and in general undefined should be possible, as well as a non-existent value, if it makes sense in the api.
Let's understand what upsert does, to see, if it also would make sense here.
Upsert performs the following steps:

Look up the unique row provided through where - the same as findOne does
If it exists, do an update
If it doesn't exist, do a create

The first lookup step can't be performed, if the element can't even be looked up.
And this lookup is the crucial element of upsert.
If we don't look for anything before creating, we can just use create instead.

I agree with the idea. Still I think it is useful to allow the case where you cannot lookup to go directly to step 3. The general principle of an upsert is: update if possible, create otherwise.
So a typical usecase that I have now seen in two different codebase is a GraphQL mutation like saveObject that takes an optional id field. So this translate to id?: string | null. So I can understand not wanting to allow null but at least if I can do id | undefined that would still be an improvement.

@Sytten wondering if an upsert doesn't make sense in this case. Would you be able to do this instead?
if (id) {
  return prisma.user.update({data})
} else {
  return prisma.user.create({data})
}

Most likely yes, but when you have many of them the upsert syntax is nicer. I don't really see the point of an upsert otherwise. It is really rare that one would know a database ID but not know if it exists or not. Maybe in the case of a composite key?

@Sytten the case of knowing a database ID and not sure if it exists is for sure very rare.
A typical use-case is rather, that you have a different unique identifier like an email, then upsert makes more sense.

Closing this issue since there's are no plans to improve this right now.
That being said, I absolutely do agree with @Sytten that one of the major use cases of upsert is when you may or may not have an ID, you don't want application code to differentiate between these cases and you just want the database client to do the right thing.

Running into this issue now, where we either update a unique token if provided or create one if undefined. Would be nice to have this all wrapped in a single upsert, but the current state is blocking it. Processing undefined variables into the create procedure would be rather nice in these sort of cases.

authors: PHILLIPS71 Sytten matthewmueller timsuchanek

repo: prisma/prisma-client-js


text:
Invalid prisma.superAdmin.findOne() invocation in

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v10.16.3

OS
darwin

Prisma
2.5.1

Logs
  prisma-client { engineConfig:
  prisma-client    { cwd: '/Users/maxbigbudget/Work/Projects/akaboxi-graphql/prisma',
  prisma-client      enableDebugLogs: false,
  prisma-client      enableEngineDebugMode: undefined,
  prisma-client      datamodelPath:
  prisma-client       '/Users/maxbigbudget/Work/Projects/akaboxi-graphql/node_modules/.prisma/client/schema.prisma',
  prisma-client      prismaPath: undefined,
  prisma-client      engineEndpoint: undefined,
  prisma-client      generator:
  prisma-client       { name: 'prisma',
  prisma-client         provider: 'prisma-client-js',
  prisma-client         output:
  prisma-client          '/Users/maxbigbudget/Work/Projects/akaboxi-graphql/node_modules/@prisma/client',
  prisma-client         binaryTargets: [Array],
  prisma-client         previewFeatures: [Array],
  prisma-client         config: {} },
  prisma-client      showColors: false,
  prisma-client      logLevel: undefined,
  prisma-client      logQueries: undefined,
  prisma-client      flags: [],
  prisma-client      clientVersion: '2.5.1',
  prisma-client      enableExperimental: [ 'connectOrCreate', 'transaction' ],
  prisma-client      useUds: undefined } }
  plusX Execution per

Hello! Can you please provide a minimal reproduction for the above crash? Unfortunately the automatically collected information in the issue does not give us much to go with here - we will need a bit more information. What were you doing? Can you share the code and schema that was active?

Ping @Maxondria

Ping @Maxondria

I am going to close this as its been 3 months now and there is no activity here.
Please reply if you want us to take another look.

I am going to close this as its been 3 months now and there is no activity here.
Please reply if you want us to take another look.

authors: Maxondria pantharshit00 timsuchanek


text:
Array equals is order sensitive

Bug description
Using equals over an array of strings should not care about the order (the documentation doesn't suggest order as being relevant) but only about the content.
https://www.prisma.io/docs/orm/reference/prisma-client-reference#equals-1
How to reproduce
const records = await this.prisma.cars.findMany({
  where: {
    colors: {
      equals: ['blue', 'red'],
    },
  },
});

Only works if the record colors value is actually ['blue', 'red'] but it does not work for ['red', 'blue'].
Expected behavior
No response
Prisma information
model Cars {
  id     String   @id @default(uuid()) @db.Uuid
  colors String[] @db.Text
}

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: 18.17.0

Prisma Version
5.8.0

The docs say "The list matches the given value exactly.", and for lists "exactly" also includes the order of its items. Is that surprising? Should we add a "Remark" in the docs about this?

It would be most useful if it ignored the order or at least being able to opt out of verifying the order.

Wouldn't that be hasEvery then?

Every value exists in the list.

and

... returns all Post records where the tags list includes at least "databases" and "typescript":
const posts = await prisma.post.findMany({
  where: {
    tags: {
      hasEvery: ['databases', 'typescript'],
    },
  },
})

hasEvery checks whether is a subset, not really equality:

equals: ['blue', 'red'] should work with ['red', 'blue']
hasEvery: ['blue', 'red'] also works for ['blue', 'red', 'yellow']

Right now you could probably achieve this by combining multiple has with AND, but that of course is much less convenient than being able to provide just a list to compare.
I think you want to open a feature request issue then. It seems you wan a "equals without order" or "hasEvery that checks that exactly for these values". Maybe hasExactly or something similar could be a name, but that is probably also too strict and would possibly imply a check of the order as well.

Hi @btecu, equality implies order sensitivity for array. We should however improve our docs to highlight that, and add examples using arrays (currently we only show strings here).

authors: btecu janpio jkomyno

repo: prisma/prisma


text:
[MongoDB] Introspection does not work with MongoDB Atlas Serverless clusters: Error in connector: Error querying the database: An invalid argument was provided: loadBalanced is not supported

When trying to run prisma db pull on a connection string for a MongoDB Atlas Serverless cluster/database, it does not work yet:
λ npx prisma db pull
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db"

Introspecting based on datasource defined in prisma\schema.prisma …

Error: Error in connector: Error querying the database: An invalid argument was provided: loadBalanced is not supported

Reproduction is easy:

Create MongoDB Atlas Serverless cluster at https://cloud.mongodb.com/
Create new folder and cd into it
npm init -y
npm install prisma @prisma/client
npx prisma init --datasource-provider mongodb
Add connection string from Atlas to .env file
npx prisma db pull
Observe error message above

Tested with Prisma CLI 3.2.1

The error message loadBalanced is not supported points to this code in the MongoDB Rust driver we are using:
        // Disallow use of load-balanced configurations in non-test code.
        // TODO RUST-653 Remove this when load balancer work is ready for release.
        if !cfg!(test) && self.load_balanced.is_some() {
            return Err(ErrorKind::InvalidArgument {
                message: "loadBalanced is not supported".to_string(),
            }
            .into());
        }

https://github.com/mongodb/mongo-rust-driver/blob/5a0192cf1ba11d9e44c453e14f90d32231689166/src/client/options/mod.rs#L1152-L1159
Issue referenced there is https://jira.mongodb.org/projects/RUST/issues/RUST-653?filter=allopenissues
So seems Atlas Serverless (with MongoDB 5) is using loadBalanced somehow that their driver does not support yet.

There is an update on the JIRA issue: https://jira.mongodb.org/browse/RUST-653?focusedCommentId=4132461&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-4132461
Seems this was added to the driver: https://github.com/mongodb/mongo-rust-driver/pull/495
No release of the driver since then though.

Fixed on latest dev (~ 3.5.0-dev.14). Will be released with 3.5.0.

authors: dpetrick janpio


text:
docs: improve limitations document

Match the current implementation as described in the release notes: https://github.com/prisma/prisma2/releases/tag/2.0.0-preview019
I also adjusted the style of all items to match the Prisma Schema formatting with separation of definitions by two spaces: https://github.com/prisma/prisma2/blob/5c2ba10744fa719372047fe955717c03ff919a33/docs/prisma-schema-file.md#field-definitions-are-aligned-into-columns-separated-by-2-or-more-spaces
Unfortunately this is not reflected in the Preview tab. But maybe GitHub will change this sometime.

Thanks a lot for catching this @RafaelKr 🙌

authors: RafaelKr nikolasburk


text:
Unable to put footer text on same line as page number

Hello,
I am trying to write a document and, on the footer, would like to have the page number (in the middle) and the current data on the left hand side. I have this request but is putting date on one line and page number on other line. Any help is much appreciated:
      const footerString = `

          ${new Date().toISOString()}

        `;
    const fileBuffer = await HTMLtoDOCX('', null, {
      font: "Helvetica",
      footer: true,
      pageNumber: true,
    }, footerString);

Note: page number is automatically added to the first span, not sure how but it works.

i got same issue...

@privateOmega Could you please help us understand what is going on here? This is a kind of blocker issue for us. Thanks.

@andyrewwer @lignar-fazmin @ansal-exp Sorry guys that I didnt notice this issue for this long, unfortunately the way that page numbers are inserted is, it is inserted as last element into first paragraph tag (or its equivalent).
const footerString =
${new Date().toISOString()} |
;
This should put the date and page number into the same line as you guys hoped for I believe, unfortunately I am not in a position to commit time into this project at present.

Hi guys!
Excuse me... Could they solve it? I have the same problem.

authors: KariNabor andyrewwer ansal-exp lignar-fazmin privateOmega

repo: privateOmega/html-to-docx


text:
Read a .env file by default

Precheck

[X] I searched existing issues before opening this one to avoid duplicates
[X] I understand tsx aims for TypeScript parity and will not support arbitrary Node.js enhancements
[X] This request cannot be made to Node.js directly, and is specific to tsx
[X] I understand this form is not for addressing a bug or seeking help

Feature request
Load .env file directly so you can do one-off tasks like seeding the database.
Motivations
I wanted to do simple database cleanup using a script like seed/delete.ts but process.env.DATABASE_PATH came undefined.
The db variable uses that in another file.
I was confused for a whole day thinking something wrong with my SQLite Database or the ORM I was using as I got this error:

SqliteError: no such table: user

seed/delete.ts
import { BetterSQLite3Database } from 'drizzle-orm/better-sqlite3'

import { db } from '@/app/db/index'
import { sessionTable, userTable } from '@/app/db/drizzle.schema'

console.log(process.env.DATABASE_PATH)

const cleanupDatabase = (db: BetterSQLite3Database<Record<string, never>>) => {
  try {
    const user = db.delete(userTable)
    const session = db.delete(sessionTable)
    console.log({ user, session })
  } catch (err) {
    console.error('Something went wrong...')
    console.error(err)
  }
}

const main = () => {
  console.log('🧨 Started deleting the database...\n')
  cleanupDatabase(db)
  console.log('\n🧨 Done deleting the database successfully...')
}

main()

Alternatives
Using dotenv
Additional context
Node.js 20 does have --env-file support & would love this in here.
I know I ticked that box above but I feel like I'm not the only one who uses .tsx for tasks like this.
Contributions

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

Damn, I found the answer after reading some docs for like 1 minute:
"db:delete": "node --import tsx --env-file .env ./seed/delete.ts",

repo: privatenumber/tsx


text:
[style]:  Changing the the Text and give text typing effect

What's the style idea?
add text typing effect
Add screenshots

Record

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

@priyankarpal

if we add the type effect it will change our UI

authors: PatilHarshh priyankarpal

repo: priyankarpal/ProjectsHut


text:
Bug if code block is not closed

Even if the code block wasn't closed, I expected there would be a code block as long as it opened.

but ... Unfortunately, it is exposed only in pure text.
Can this bug be solved?

Can't we just close the code block, since that's how it is supposed to work?

@anshgoyalevil -- this is a serious issue if you are streaming a response and progressively rendering it via <Markdown>.  While a code block is not yet terminated, it gets rendered directly as HTML in the DOM, breaking things (and probably potentially executing JS?).
Surely this should be considered a bug and should be fixed.

authors: anshgoyalevil hzoou markedwards

repo: probablyup/markdown-to-jsx