text:
InternetExplorer does not support array.find()

CodeSandbox demo
https://codesandbox.io/s/popper-2-playground-hgjuz
Steps to reproduce the problem

Open example in InternetExplorer

What is the expected behavior?
Popperjs works in InternetExplorer as well
What went wrong?
InternetExplorer does not support array.find() method. In 3 places this not supported is used.

https://popper.js.org/docs/v2/browser-support/#ie11

authors: FezVrasta bsever

repo: popperjs/popper-core


text:
Add shard compatibility to mergeSTR

Main changes (similar to changes to merge_str_prep.py):

Add a 'numshards' parameter to specify number of shards to loop over.
Push mergeSTR into a loop over each shard so that mergeSTR runs on all samples on each shard separately.

Remaining lint conflicts relate to a different file in the repo, so have been ignored.

source: gharchive/pull-request

repo: populationgenomics/sv-workflows

license: MIT

license_type: permissive

license_source: github-api


text:
Compose File Version 3.8 not working with Docker Swarm

Bug description
The compose file Version 3.8 is not working with Docker Swarm. If a create a stack and insert a compose file with version 3.8 i get the following error: "Failure: unsupported Compose file version: 3.8"

If I use verion 3.7 or less it works as expected but I cannot use deploy features like max_replicas_per_node.
Expected behavior
That it works with the latest version of compose files.
Portainer Logs
2021/01/10 16:50:48 http error: unsupported Compose file version: 3.8
 (err=unsupported Compose file version: 3.8
) (code=500)

Technical details:

Portainer version: 2.0.1 (also 2.0.0)
Docker version (managed by Portainer): 20.10.0
Kubernetes version (managed by Portainer): Not in use. Docker swarm is in use.
Platform (windows/linux): Linux: Ubuntu 20.04.1 LTS
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker stack deploy --compose-file docker-compose.yml portainer (look down for the docker-compose.yml)
Browser: Firefox 84.0.2 (64-Bit) on Windows 10

Additional context
Portainer is started with: docker stack deploy --compose-file docker-compose.yml portainer
docker-compose.yml of portainer:
version: '3.2'

services:
  agent:
    image: portainer/agent
    environment:
      # REQUIRED: Should be equal to the service name prefixed by "tasks." when
      # deployed inside an overlay network
      AGENT_CLUSTER_ADDR: tasks.agent
      # AGENT_PORT: 9001
      # LOG_LEVEL: debug
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /var/lib/docker/volumes:/var/lib/docker/volumes
    networks:
      - agent_network
    deploy:
      mode: global
      placement:
        constraints: [node.platform.os == linux]

  portainer:
    image: portainer/portainer-ce
    command: -H tcp://tasks.agent:9001 --tlsskipverify
    ports:
      - "9000:9000"
      - "8000:8000"
    volumes:
      - portainer_data:/data
    networks:
      - agent_network
    deploy:
      mode: replicated
      replicas: 1
      placement:
        constraints: [node.role == manager]

networks:
  agent_network:
    driver: overlay

volumes:
  portainer_data:

It can't work since portainer currently only supports docker-compose ≤2 (it is using libcompose, not docker-compose),
It also mentioned in the "create stack" section of your panel:
This stack will be deployed using the equivalent of docker-compose. Only Compose file format version 2 is supported at the moment.
The 2.1 release will fully support docker-compose. It will reportedly be released later this month. However, since it was also supposed to be released in December, I wouldn't count on it.
see #3750.

It can't work since portainer currently only supports docker-compose ≤2 (it is using libcompose, not docker-compose),
It also mentioned in the "create stack" section of your panel:
This stack will be deployed using the equivalent of docker-compose. Only Compose file format version 2 is supported at the moment.
The 2.1 release will fully support docker-compose. It will reportedly be released later this month. However, since it was also supposed to be released in December, I wouldn't count on it.
see #3750.

Actually, this problem is because we are currently bundling an older version of the Docker Binary that doesn't support v3.8 in Swarm. I am currently finishing my testing of this PR which should bring that functionality by the end of the month with our 2.1 release.
Since there is already an issue tracking the change needed for support of v3.8, i'll close this as a duplicate of https://github.com/portainer/portainer/issues/3206

Actually, this problem is because we are currently bundling an older version of the Docker Binary that doesn't support v3.8 in Swarm. I am currently finishing my testing of this PR which should bring that functionality by the end of the month with our 2.1 release.
Since there is already an issue tracking the change needed for support of v3.8, i'll close this as a duplicate of https://github.com/portainer/portainer/issues/3206

source: gharchive/issue

authors: itsconquest maxschloegl mygrexit

repo: portainer/portainer

license: Zlib


text:
not able to use portainer: panic: runtime error: invalid memory address or nil pointer dereference

I am not able to install portainer in my environment.
I tried it with portainer-ce:latest and portainer:latest
Both pulls worked, but while starting both generates the same error and trying to restart endless.
The user which used to run was root and docker-user. I tried both without difference in result.
The users have write rights on the path which was used for run (docker -user and -group).
For each try I cleaned the data folders completely
I tried it with and without cert-files in the local-certs folders.
I tried also to restart the server, with same result.
I would be happy, if someone can help me to solve this
log:
....
2021-07-12T11:27:46.139988937+02:00 	/home/vsts/work/1/s/api/cmd/portainer/main.go:351 +0xd0
2021-07-12T11:27:46.139991525+02:00 main.main()
2021-07-12T11:27:46.139994122+02:00 	/home/vsts/work/1/s/api/cmd/portainer/main.go:501 +0x86
2021-07-12T11:27:51.606766266+02:00 2021/07/12 09:27:51 Migrating database from version 0 to 30.
2021-07-12T11:27:51.608977272+02:00 panic: runtime error: invalid memory address or nil pointer dereference
2021-07-12T11:27:51.608996662+02:00 [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x11a7d1a]
2021-07-12T11:27:51.608999429+02:00
2021-07-12T11:27:51.609001747+02:00 goroutine 1 [running]:
2021-07-12T11:27:51.611272124+02:00 github.com/boltdb/bolt.(*Bucket).Cursor(...)
2021-07-12T11:27:51.611278997+02:00 	/tmp/go/pkg/mod/github.com/boltdb/bolt@v1.3.1/bucket.go:91
2021-07-12T11:27:51.612349434+02:00 github.com/portainer/portainer/api/bolt/migrator.(*Migrator).retrieveLegacyResourceControls.func1(0xc0000a7b20, 0xc0000a7a00, 0xc0000a7b20)
2021-07-12T11:27:51.612360518+02:00 	/home/vsts/work/1/s/api/bolt/migrator/migrate_dbversion1.go:66 +0xaa
.....

I use an ubuntu server  5.4.0-77-generic #86-Ubuntu SMP  x86_64 x86_64 x86_64 GNU/Linux
Run-command which i used:
docker run -d --privileged -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock --restart always --log-driver=local --log-opt max-size=10m --log-opt max-file=5 --name=rie_portainer -v /home/mypath/data:/data -v /home/mypath/local-certs:/certs portainer/portainer-ce:latest --ssl --sslcert /certs/portainer.crt --sslkey /certs/portainer.key
Docker info:
Client:
Context:    default
Debug Mode: false
Server:
Containers: 10
Running: 0
Paused: 0
Stopped: 10
Images: 8
Server Version: 20.10.2
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version:
runc version:
init version:
Security Options:
seccomp
Profile: default
Kernel Version: 5.4.0-77-generic
Operating System: Ubuntu 20.04.2 LTS
OSType: linux
Architecture: x86_64

I startet with root. after I recognized that this did not work, I tried the same with an other user assigned to group docker.
Both with same negative result

Additional information:
I tried for playing around to run the same with a missing folder on host.
docker run -d --privileged -p 8000:8000 -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock --restart always --log-driver=local --log-opt max-size=10m --log-opt max-file=5 --name=rie_portainer -v /home/riedocker/newPath/data:/data -v /home/riedocker/newPath/local-certs:/certs portainer/portainer-ce:latest --ssl --sslcert /certs/portainer.crt --sslkey /certs/portainer.key
The path /home/riedocker/ exists but the subfolder newPath did not exist.
The result was positive , because the error which I mentioned did not apear.
In the logs are only:
DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process] 2021-07-13T16:10:10.997412729+02:00 2021/07/13 14:10:10 Http server exited: open /certs/portainer.crt: no such file or directory 2021-07-13T16:10:12.003528377+02:00 2021/07/13 14:10:12 failed opening store: timeout
The new generated Folder "newPath" was generated with root rights:
drwxr-xr-x 4 root      root      4096 Jul 13 16:09 newPath
The Folder which I used before and got the error is a mounted folder.
The mount was done with:   davfs rw,auto,user,uid=1001,gid=1009,_netdev	0	0
The rights are: drwxr-xr-x  4 riedocker riedocker
The UID:GID of the mount are related to the user&group riedocker

Hi
kindly verify the crt file. probably could try generating once
openssl genrsa -out portainer.key 2048
openssl ecparam -genkey -name secp384r1 -out portainer.key
openssl req -new -x509 -sha256 -key portainer.key -out portainer.crt -days 3650
please do verification of certificate with openssl x509 -noout -text -in .
also this link could help in validating the certificate creation
https://jamielinux.com/docs/openssl-certificate-authority/create-the-intermediate-pair.html

Hello @srebala
Thank you for your help.
I did the same also without ssl and cert tags. just to see if the container works.
But the result was the same.

Hi
kindly check the getfacl  for the /certs/ directory on host, need to selinux acl for this

@schwabenheinz you are utterly correct, the issue will have been to do with permissions of the existing on-host directories - and in allowing Docker to create them on start, the dir and files have been given the permissions that Portainer is expecting.
I think this issue should be improved, by adding more details logging before the code gets to the migration - testing and reporting if the ownership / access permissions are sufficient - so the user has the knowledge how to remediate.

in some ways, this is related to https://github.com/portainer/portainer/issues/5623
we need to check existance, permissions and ownerships, and bubble up anything that is not right in a way that is relevant to the user - so not only in the log, but also in the webUI (and in a non-timebound expiring way)

I was able to get it working when creating the "portainer" mount folder with root (sudo) instead of creating it with my normal user.

authors: SvenDowideit schwabenheinz srebala thiagottss


text:
Multiple custom app templates

Is your feature request related to a problem? Please describe.
Adding new app templates requiring combining of multiple app templates as suggested here: https://docs.portainer.io/advanced/app-templates/build
or as it is done here: https://github.com/ntv-one/portainer
Describe the solution you'd like
A solution like the one of TrueNas Scale to have multiple app templates available and treat them separately allows to have more flexibility and simplifies the custom app templates creation.
Describe alternatives you've considered
The one above is the only solution that came in my mind right now.
Additional context
None for now.

#1616 Multiple External Templates
https://www.technorabilia.com/portainer-tools-merge-and-host-app-template-definitions/

@gamegine Thanks! Nice solution. It would still be nice to have it on portainer tho, wouldn't it?

Sorry I just saw you linked an issue. So I will close this as duplicated of #1616

authors: UnconventionalMindset gamegine


text:
Portainer Title headlines

Hi!
I would like to ask if you can add a feature like a text box to put a Title that shows somewhere on the upper side of the screen.
My team needs to connect to several Portainers at the same time.
It is useful to identify each one and give them a title.
Thanks!

You can customize the logo for your Portainer Server instance - would this potentially solve the problem for you?

It works like a charm,
but it has another bug.
If you change between differente Portainers, the logo doesn't change,
even with CRTL+F5 to completelly refresh on Chrome!
This could lead to a disaster!
I need to delete all cookies and temp files on Chrome, or open an
anonyous window =(
----- Mensagem de James Carppe @.***> ---------
Data: Wed, 14 Dec 2022 14:42:12 -0800
De: James Carppe @.***>
Assunto: Re: [portainer/portainer] Portainer Title headlines (Issue #8194)
Para: portainer/portainer @.***>
Cc: toxic9 @.>, Author @.>

You can customize the logo[1] for your Portainer Server instance -
would this potentially solve the problem for you?
—
Reply to this email directly, view it on GitHub[2], or unsubscribe[3].
You are receiving this because you authored the thread.Message ID:
@.***>

----- Fim da mensagem de James Carppe @.***> -----
Ligações:
[1] https://docs.portainer.io/admin/settings#use-custom-logo
[2] https://github.com/portainer/portainer/issues/8194#issuecomment-1352318119
[3]
https://github.com/notifications/unsubscribe-auth/AIGODWA5HNJJP7MCW6DTOJLWNJEMJANCNFSM6AAAAAAS5RUIPU


text:
Fix(db): needs encryption migration function fixed EE-2414

Resolves EE-2414
The logic didn't take into account a new database and made a bad assumption
I've also added a go test for it.

nice - love the tests

authors: SvenDowideit hookenz


text:
Do not show "waiting" message for several seconds

At simple AI settings, the whole waiting takes just 1-2 seconds; in this case the "Waiting..." message across the board just distracts.
The message should appear after, for example, 3 seconds of waiting.

Requires non-blocking UI.

repo: portnov/hcheckers


text:
[PA-769] Filter using namespace label and perform backup and schedule backup

What this PR does / why we need it:
In this PR, created couple of namespaces with namespace labels taking backup in below manner

Backup one namespace.
Backup multiple namespace.
Backup one namespace through schedule
Backup multiple namespace through schedule.
restore the backups

Which issue(s) this PR fixes (optional)
Closes #
https://portworx.atlassian.net/browse/PA-769
Jenkins -
https://jenkins.pwx.dev.purestorage.com/job/Users/job/Sumit/job/Custom-Pipelines/job/px-backup-on-demand-system-test-byoc/1067/console
Special notes for your reviewer:

Updated the new Jenkins run
https://jenkins.pwx.dev.purestorage.com/job/Users/job/Sumit/job/Custom-Pipelines/job/px-backup-on-demand-system-test-byoc/1067/console

repo: portworx/torpedo


text:
[AWIBOF-7047] modified flush command handling.

code changes:
Allow duplicated flush command if pos use journal disabled configuration.

Web으로 conflict 수정하다가 꼬여서 다시 살렸습니다.

repo: poseidonos/poseidonos


text:
Selection sometimes fails for DataFrames with integer named columns and a function selector

Will clean up a bit, but was triggered by this code:
from great_tables import GT, countrypops

# Get vectors of 2-letter country codes for each region of Oceania
countries = {
    "Australasia": ["AU", "NZ"],
    "Melanesia":  ["NC", "PG", "SB", "VU"],
    "Micronesia": ["FM", "GU", "KI", "MH", "MP", "NR", "PW"],
    "Polynesia": ["PF", "WS", "TO", "TV"],
}

# a dictionary mapping region to country (e.g. AU -> Australasia)
region_to_country = {
    region: country
    for country, regions in countries.items()
    for region in regions
}

keep_rows = (
    countrypops.country_code_2.isin(list(region_to_country))
    & countrypops.year.isin([2000, 2010, 2020])
)

# Create a gt table based on a preprocessed `countrypops`
wide_pops = (countrypops[keep_rows]
    .assign(region = lambda D: D.country_code_2.map(region_to_country))
    .pivot_table(index = ["country_name", "region"], columns = "year", values = "population")
    .reset_index()
    .sort_values(2020, ascending = False)
)

(
    GT(wide_pops, rowname_col = "country_name", groupname_col = "region")
    .tab_header(title ="Populations of Oceania's Countries in 2000, 2010, and 2020")
    .tab_spanner(
        label = "Total Population",
        columns = lambda colname: True
    )
    .fmt_integer()
)

Essentially, tab_spanner correctly selects columns using the lambda, but then it passes those columns to cols_move. However, because some of the cols it selected are integers (e.g. 2000), cols_move interprets these as column positions :/

Fixed by https://github.com/posit-dev/great-tables/pull/127. Example works but issues warning by design.

authors: machow rich-iannone

repo: posit-dev/great-tables


text:
Add Python dependency interrogation technique

Implement a strategy to interrogate the requirements.txt file for bundles that have one. Some initial thoughts:

Create an abstraction on the archive written by bundle. download.
Add a method to that abstraction that allows the user to inspect the requirements.txt file.

archive = bundle.download('archive.tar.gz')
'dash' in archive.requirements_txt
>>> True

Relates to #304

This might even be superseded by #304 yeah?

Most likely, yes. Depends on what we want to do with backwards compatibility with prior Connect versions.

And, depending on the shape of the API, we might have different information from requirements.txt that is relevant

Closing as not planned since the functionality was added in https://github.com/posit-dev/posit-sdk-py/issues/304

authors: jonkeane tdstein

repo: posit-dev/posit-sdk-py


text:
Cannot open the external Shiny webpage.

Hello, this is my first time using the VS Code Shiny extension, and I've encountered a problem. When I use it, the Shiny preview window that automatically pops up in VS Code does not navigate to the URL. I can manually enter it and it works, but I'd like to know how to make it navigate automatically. Is there something wrong with my settings?

Sorry to hear that @Jxuanrui. Is there anything printed in the terminal window opened by the extension (it's named "Shiny")?

Yes, I tried switching to another computer and then used R to start Shiny. The same issue occurred: a URL appeared in the terminal, and I could access the Shiny interface by copying the URL into the browser. However, the VSCode extension does not automatically redirect to the Shiny interface.

Thanks @Jxuanrui. Does your app take a long time to start normally? The error message in the bottom right is shown when it takes longer than 10s to start the app. From the state shown in your screenshot, you should be able to click "Keep waiting", at which point the preview will open immediately because the app has already started. Alternatively, you could dismiss the error message and Ctrl + Click on the URL in the terminal to open the preview.

Alright, maybe there are still some errors in my software settings. Thank you for your suggestion.

authors: Jxuanrui gadenbuie

repo: posit-dev/shiny-vscode


text:
Use the Roboto package instead of bundling the font

This PR proposes a change to the CTAN font package for the Roboto font, eliminating the requirement to maintain it. For end users this results in a removal of the requirement to maintain a font directory making the package easier to use.
I've opted to leave the \fontdir command in place to not break the build for existing users who might use it for other custom fonts.

No worries!
I have rebased on the current master. CI jobs seems to be waiting for an approval from a maintainer since it considers me a first time contributor.

Thanks! Yep, which I did before, but the problem was that the actual rendering job (i.e. the closest thing to a 'test') wasn't set to run on PRs, so I fixed that on master but needed the rebase for CI on your branch to pick it up.

authors: OJFord bol


text:
🛑 PowBot SDN is down

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

HTTP code: 502
Response time: 607 ms

Resolved: PowBot SDN is back up in 0694939.

repo: powbot/status


text:
AMD instances

Amazon announced new AMD based instances https://aws.amazon.com/blogs/aws/new-lower-cost-amd-powered-ec2-instances/
Thanks!

Closed by #389
And hopefully T3a will also work.

license: mit

license_source: bigquery


text:
Handle wrapping behavior

#151 removes wrapping behavior from witness generation, because it is not a requirement in the halo2 backend due to extra rows needed for eg. blinding factors.
On the flip side, it is a requirement in eSTARK, so even though witness generation is currently fine according to pilcom, it could fail if a witness does not satisfy the wrapping constraint.
One idea would be to toggle wrapping in the executor depending on which backend is to be used, but this breaks the clear separation.
This was moved to an issue as it was not clear at the time how to deal with it, and witness generation did not rely on the wrapping behavior in the existing state machines.

Some more notes: We might already use wrapping to compute the values for the first row, for example if we have an identity of the form x' = x + 1, then it will actually be evaluated as x = x[-1] + 1.
We should analyze the PIL to check if it depends on wrapping or not (substitute fixed columns and see if next references are still there).
In my opinion, the cleanest solution would be to change the asm->pil generator to not rely on wrapping and report if there are "free" rows.
If pil is specified by the user, the system should warn that it is not compatible with halo2 and could even offer to introduce additional columns and factors to fix it (as we currently do).

Is this fine now? @Schaeff @chriseth

I think we are still just ignoring the problem and thus introducing nondeterminism with halo2.

I don't think so. In halo2 we explicitly add 2 selector columns, enable_cur and enable_next, that guard the used rows and the used rows - 1, respectively. I wouldn't say this introduces nondeterminism. This would be true only for machines that rely on the cyclic behavior, which I don't think we have.

This is sound now in Halo2.

authors: Schaeff chriseth leonardoalt

repo: powdr-org/powdr


text:
[DO NOT MERGE] Release 2.18 - Migration Customizations

This is a PR to track the changes made to the 2.18 release branch to support converting our existing clusters to Kubespray.

Is this intended to form a todo list of things we'll shoot to align with upstream after we're using kubespray consistently, or do we expect to contribute these changes upstream?

authors: benlangfeld djtaylor

repo: powerhome/kubespray


text:
tests: Complete the method lists

[x] Add methods that do not return a Vector2
[x] Use Vector2.convert directly, rather than a lambda, so it has a human-meaningful name.

PS: The CI failure was caused by a mypy issue, so I added a type: ignore annotation as a workaround.

repo: ppb/ppb-vector


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:
apriltag in gazebo

april tag properly visible in gazebo
Controller is ready. camera needs to be set up.

launch files are separate right now. original world is as is.


text:
Drag and Drop reorder possible, but not seeing documentation for it.

When I use the image preview plugin I can drag and drop the order of the images in filepond. However, I am unable to find documentation on this features.
I'm using file pond for users to upload images to a gallery and the order of the gallery needs to be saved.
How do I save these images in the order the user sets in filepond using drag and drop reordering? (I'm using Laravel and Livewire)

Hello, Brentscholl! Look at this screencast here:
https://laravel-livewire.com/screencasts/s8-dragging-list
At the end there is a function that works with sorting. But the problem, as it seems to me, is not in changing the order of files when dragging, but in the order of transferring files from the client to the server. Each time, the server accepts files in a different order, even during the initial save. I also try to set up this bundle and so far it turns out poorly. If you can figure it out, please let me know.

Not sure if this is correct, but it seems to work
I added this to FilePond.setOptions()
FilePond.setOptions({
                allowMultiple: true,
                allowReorder: true,
                server: {
                    process: (fieldName, file, metadata, load, error, progress, abort, transfer, options) => {
                        @this.upload('images', file, load, error, progress)
                    },
                    revert: (filename, load) => {
                        @this.removeUpload('images', filename, load)
                    },
                },

                // Added this ----------------------------------------
                onreorderfiles(files, origin, target){
                    @this.set('images', null);
                    files.forEach(function(file) {
                        @this.upload('images', file.file);
                    });
                },
            });

This removes the previous uploaded images and reuploads with the new order.

Closed because inactive.

Hey @brentscholl, would you mind sharing your server side code for Livewire component using Pond? ;)

authors: bersyatina brentscholl flexchar rikschennink

repo: pqina/filepond


text:
Proposal: Add shock tube species profiles as an experiment type

PyKED/ChemKED version
v0.1.5
Code sample
...
experiment-type: Species profile
apparatus:
    kind: shock tube
    institution: Stanford University
    facility: stainless steel shock tube
    inner-diameter: &diam
        value: 15.2
        units: cm
common-properties:
    pressure: &pres
        - 1.672 atm
        - uncertainty-type: relative
          uncertainty: 0.02
    temperature: &temp
        - 1182 K
        - uncertainty-type: relative
          uncertainty: 0.01
    composition: &comp
      kind: mole-fraction
      species:
        - species-name: H2O2
          amount:
            - 0.002046 #can one specify it in ppm by giving ppm as units?
            - uncertainty-type: relative
              uncertainty: 0.05
        - species-name: H2O
          amount:
            - 0.001113
            - uncertainty-type: relative
              uncertainty: 0.05
        - species-name: O2
          amount:
            - 0.000556
            - uncertainty-type: relative
              uncertainty: 0.05
        - species-name: Ar
          amount:
            - 0.996285 #can balance be specified here instead of a value?
            - uncertainty-type: relative
              uncertainty: 0.05
    time-shift: &timeshift
      - 0 s
      - uncertainty-type: absolute
        uncertainty: 0.01 ms
    assumptions: &assumptions
        thermal-boundary: adiabatic #vs. isothermal
        mechanical-boundary: constant pressure #vs. constant volume
        equation-of-state: ideal gas
datapoints: #is it necessary to include the temperature: *temp stuff for each item even though it's common?
    - csvfile: 'hong_pci2013_oh.csv'
      targets:
        - name: OH
          type: mole fraction # vs. concentration or absorbance
          species: OH
          absolute-uncertainty: 1E-6
          relative-uncertainty: .05
    - csvfile: 'hong_pci2013_h2o.csv'
      targets:
        - name: H2O
          type: mole fraction
          species: H2O
          absolute-uncertanity: 1E-6
          relative-uncertainty: .05
    - csvfile: 'hong_pci2013_abs227nm.csv'
      targets:
        - name: 'abs_227nm'
          type: absorbance
          wavelength:
            value: 227
            units: nm
          absorbing_species:
            - species: H2O2
              cross-section:
                value: 1.40E+05
                units: 'cm^2 mol^-2'
                relative-uncertainty: .1
            - species: HO2
              cross-section:
                value: 1.27E+06
                units: 'cm^2 mol^-1'
                relative-uncertainty: .1
          path_length: *diam
          absolute-uncertainty: .01

Proposed by Mike Burke's group at Columbia. Mildly edited by Bryan for clarity.

To start, we don't need the ' ' around strings, like in the csvfile and units fields

This is excellent! A few thoughts:

ppm is not really necessary as a unit, just use E-06
The time-shift field looks fine, but it should be specified in each datapoint
I'm not sure about the assumptions field. How often are each of the options used? What is the utility of providing this?
Yes, it is necessary to explicitly include each required option in a data point. Therefore, each data point needs a temperature, composition, and pressure. See https://github.com/pr-omethe-us/PyKED/issues/59
Rather than having a csv file with the data, it would IMO be better to have 3 YAML files, one for each data set. That will reduce the problems YAML has dealing with tables. You can check out the RCM example for a case where a two-column table is used, https://github.com/pr-omethe-us/PyKED/blob/master/pyked/tests/testfile_rcm.yaml With that file in mind, I'd propose the following schema for a single target:

datapoints:
  - temperature: *temperature
    composition: *composition
    pressure: *pressure
    time-shift: *timeshift
    species-history:
      time:
        units: s
        column: 0
      target:
        name: OH  # This is more or less arbitrary, for user convenience
        type:
          - mole fraction  # or concentration or absorbance, need a field for units of concentration
          - uncertainty-type: relative
            uncertainty: 0.1
        column: 1
      values:
        - ...

Absolute uncertainty and relative uncertainty are mutually exclusive, I think...
For absorbance, maybe something like this:

datapoints:
  - temperature: *temperature
    composition: *composition
    pressure: *pressure
    time-shift: *timeshift
    species-history:
      time:
        units: s
        column: 0
      target:
        name: abs_227nm  # This is more or less arbitrary, for user convenience
        type:
          - absorbance
          - wavelength:
             - 227 nm
             - uncertainty-type: relative
                uncertainty: 0.1
          - path-length:
              - 0.1 m
              - uncertainty-type: relative
                uncertainty: 0.1
          - absorbing_species:
              - species-name: H2O2
                 cross-section:
                   - 0.1E5 cm2/mol
                   - uncertainty-type: relative
                      uncertainty: 0.1
              - species-name: OH
                 cross-section:
                   - 0.2E5 cm2/mol
                   - uncertainty-type: relative
                      uncertainty: 0.1
        column: 1
      values:
        - ...

I don't think the diameter should go in the apparatus field. We're trying to come up with an alternate file format for apparatuses, something that would store the details of each device and give it a unique identifier.

OK, lots to think about here!

I agree that each file should only contain a single dataset or series—it's ok if there are multiple ChemKED files from a single paper, for example.

Regarding assumptions, I am also wary of putting something specific to a way of modeling (at least I assume that's what that is for) in a file that is meant to encode the measurement itself.
That said, if this sort of information is similar to (e.g.) pre-ignition pressure rise in a shock tube, or compression volume trace or post-compression heat loss in an RCM, then I think it should be included.  However, I don't think that is the case.

Email from Mike Burke to Bryan:

Hi Bryan,
Thanks for your comments.  Some followups below to continue the dialogue...
1 Good point, agreed.
2,4 It might be worth pointing out there's one key aspect of this type of multi-species experiment that I suspect would to to differences in how one would treat it compared to a series of ignition delay times -- each of the species time profiles are measured in a single experiment rather than multiple experiments.  As a result, the time-shift (2), as well as the initial pressure, temperature, and composition (4) should be identical -- such that I would see value in listing them among common-properties only and not in the datapoints section because they would be redundant and because it would avoid someone making a mistake by entering different initial values for different datapoints.
3 Yeah, I'm not sure I even like the 'assumptions' field so much anyway -- I have the same philosophical objections to the assumptions block within our proposed shock tube file.  The tricky thing with this Hong experiment that we're emulating in this YAML file is that there is a driver insert in the shock tube such that the authors suggest that it is nearly constant pressure rather than the more conventional constant volume assumption used for shock tube (based on their pressure traces).  So in that regard, it is similar to the pressure trace that might in other experiments be used to model boundary layer effects or heat loss, or in the present case lack thereof.
5 Similar to 2,4, all of the species time profiles correspond to a single experiment not just a single paper, and have all the same common properties like initial temperature, pressure, composition, etc.  In that case, does it still make sense to have 3 different YAML files to represent it?  My students initially suggested csv files such that tables with titles for each column could be viewed very easily and read in similarly easily using pandas dataframes.  In many species profile experiments, there could be tables consisting of many dozens of rows (i.e. species) rather than just a few.  Another advantage of this format would be that it is a very common way that people right now represent their data in supplemental material for papers.  Thoughts?
6 I would see value in having both relative and absolute uncertainties for species time profiles for example, where one could account for "calibration" type uncertainties (which perhaps might be relative) and one could account for signal-to-noise/detection limit type uncertainties (which perhaps might be absolute).  At different points along the time profile, the relative uncertainties may take on different values on an absolute basis.
8 Ah, I see.  I could see some value in doing that.  I suppose you're planning on having an apparatus YAML format which describes an apparatus that could be identified by name or tag only within the experiment YAML file.  I should mention that the shock tube diameter is a necessary component to predicting the absorption signal through a Beer's Law analysis.

Mike,
Thanks for the quick response! Some further clarifications:

such that I would see value in listing them among common-properties only and not in the datapoints section because they would be redundant and because it would avoid someone making a mistake by entering different initial values for different datapoints.

Even values listed in the common-properties section still have to be entered into every data point, with the minor difference that they can be added by reference, for instance, the following is the preferred method:
common-properties:
  temperature: &temp
    - value
  pressure: &pres
    - value
datapoints:
  - temperature: *temp
    pressure: *pres
    ...
  - temperature: *temp
    pressure: *pres
    ...

This is an intentional design decision on our part. We felt there were two likely scenarios:

Properties in the common-properties block get autofilled for missing properties in each data point
Properties in the common-properties block are manually filled in each data point

In general, our philosophy is "explicit is better than implicit"; therefore, we chose the second scenario. We feel that the danger of someone forgetting to add a required value and having it implicitly filled from the common-properties with the wrong value is greater than the work required to add the property to each datapoint. Note, though, that even in the second scenario, the user is not required to type the value more than once, so we gain the advantages of reducing the risk of typos, while also forcing the user to think about what they're doing.

Yeah, I'm not sure I even like the 'assumptions' field so much anyway

I can see one important use case, which is specifying constant pressure vs. constant volume, as you mention. There are also some butanol experiments that use what Ron's group calls CRV (constrained reactor volume, I think) that they model as constant p-h rather than the typical constant u-v. We do have a keyword for the pressure rise that's sometimes specified in the constant volume shock tube experiments. Maybe this could be a part of the apparatus block? constant volume shock tube vs. crv shock tube vs. rcm or something?

In that case, does it still make sense to have 3 different YAML files to represent it?

We think the answer to this question is yes. Obviously there is some concern for typos, since there are a bunch of shared properties for the single experiment. I think the solution to this is to specify the common properties once and use a script to write multiple files. We're already sort of planning to have converter scripts from internal data formats to the standard format, so this would fit into that pretty neatly.
Another option that we've (I've) considered is putting a binary file encoded as a string into the data file, something like
data: !!binary base64-string

See here also: http://yaml.org/type/binary.html This is something that Kyle and I haven't come to consensus on yet though.

At different points along the time profile, the relative uncertainties may take on different values on an absolute basis.

If we can define how the relative uncertainty and absolute uncertainty combine, then that would be fine, I suppose, although I think my preference would be for the person writing the YAML file to just write out the absolute uncertainty for a single point in time.

I should mention that the shock tube diameter is a necessary component to predicting the absorption signal through a Beer's Law analysis.

Yes, I think the diameter should be a required property if the absorbance is specified, except the diameter (really, path length, right, since there can be multiple reflections?) should be specified in each   data point, or in the common properties section and then referenced in each data point.

Like @tsikes , I am also interested in developing a format for laser-schlieren data, but I think keeping the required fields to a minimum is best with the additional experimental descriptions being optional.
Maybe I'm missing something, but I think for the reflected shock experiment types, simulations should be performed by specifying the post-shock conditions T5, P5) that are present at time zero and then the time history of the observable - either a species profile as in laser absorption or H-ARAS.
For an observed density gradient in laser schlieren, we need the Mach number or shock speed (since we can easily calculate the Mach number), so I would propose specifying the initial temperature and pressure (P1, T1) and the observed shock speed and the calculated density gradient from the facility - attached is a sample of what I think a laser-schlieren ChemKED file could look like.
I know this means the thermo data, gas refractivities, etc. as used in the calculation of the density gradient are baked-in and not necessarily determinable from the data format, but I think this is something that would be added as optional fields versus trying to provide the raw signals and process those in PyKED. I do also think that alternatively specifying the incident shock conditions (T2, P2) might be more convenient for someone just looking at the data, but that processing the data by doing the ideal shock calculations first is "better".
LS_iBN_017.yaml.txt

authors: bryanwweber kyleniemeyer mefuller

repo: pr-omethe-us/PyKED


text:
Mural V2 não carrega na rede da UFFS

Foi reportado que não é possível acessar o Mural na rede na UFFS.
É necessário verificar, pois, a plataforma foi criada com o principal objetivo de atender as demandas na universidade.

Ticket aberto ao TI: https://ati.uffs.edu.br/customer.pl?Action=CustomerTicketZoom;TicketNumber=2022030332000085

vi que essa issue ainda ta aberta e aqui em Erechim funciona agora, o TI arrumou td... não sei como ta no resto

repo: practice-uffs/mural


text:
Narração de Material LGPD

Essa issue tem por objetivo a narração do seguinte material:
"Você conhece a Lei Geral de Proteção de Dados?
A Lei Geral de Proteção de Dados é a Lei nº 13.709, de 14 de agosto de 2018, que dispõe sobre o tratamento de dados pessoais, nos meios físicos e digitais.
Seu objetivo principal é proteger os direitos fundamentais de liberdade, privacidade e o livre desenvolvimento da personalidade da pessoa física.
Para você compreender melhor a LGPD, vamos destacar quatro conceitos relacionados à proteção de dados:
Dado pessoal: é a informação relacionada à pessoa física identificada ou identificável, como RG, CPF etc.
Dado pessoal sensível: é um dado que revela a origem racial ou étnica, convicção religiosa, opinião política, filiação a sindicato ou a organização de caráter religioso, filosófico ou político, dado referente à saúde ou à vida sexual, dado genético ou biométrico, quando vinculado a uma pessoa física.
Dado anonimizado: é o dado que não possibilita a identificação do titular, considerando a utilização de meios técnicos razoáveis e disponíveis na ocasião de seu tratamento.
Tratamento dos dados pessoais: são todos os processos realizados com o dado pessoal, como a operação de coleta, produção, recepção, classificação, utilização, acesso, reprodução, transmissão, distribuição, processamento, arquivamento, armazenamento, eliminação, controle da informação, modificação, comunicação, transferência e difusão ou extração.
A LGPD, em seu artigo 6º, traz dez princípios para o tratamento de dados pessoais:
• Os princípios da finalidade, adequação e necessidade estão relacionados com a utilização dos dados para um propósito específico e legítimo, além de restringir a coleta apenas aos dados que precisam ser utilizados.
Portanto, não se deve coletar dados sem explicar ao titular para que ele será utilizado, fazer o uso do dado para outra finalidade e nem coletar um dado que não será utilizado.
• Os princípios da transparência e livre acesso garantem, ao titular dos dados, a consulta de forma livre, gratuita e facilitada sobre o uso de seus dados, inclusive com a indicação do prazo de utilização. Além disso, o repasse de dados para terceiros será possível, apenas, se previamente informado e autorizado pelo titular.
• A qualidade dos dados é o princípio que assegura aos titulares o acesso a informações confiáveis, para que possam exercer, da melhor forma possível, a decisão sobre os seus dados coletados, tratados e compartilhados.
• Os princípios da segurança e prevenção estão relacionados à responsabilidade das organizações de adotar medidas técnicas e administrativas para garantir a proteção dos dados, prevenindo acessos indevidos, perdas ou danos.
• Os dados pessoais não podem ser usados para discriminar ou promover abusos contra os seus proprietários; e a instituição deve atuar com responsabilidade, apresentando provas e evidências de que medidas e procedimentos foram tomados para promover a proteção dos dados pessoais, garantias essas especificada nos princípios da não discriminação e responsabilização e prestação de contas.
Essas são algumas informações básicas para entender o funcionamento e a importância da Lei Geral de Proteção de Dados."

Criei as pastas dessa issue no Google Drive:

 Pasta da issue
🔽 Entrada
🔼 Saída

App Audacity para realizar edição, caso seja necessário

A narração já está na pasta de entrada

Vamos aguardar para ver se o solicitante não vai pedir nenhuma alteração antes de fechar a issue

Solicitação realizada pelo e-mail para regravar apenas alguns trechos, sem a necessidade de juntar com a parte que já foi gravada.

repo: practice-uffs/programa


text:
Atualizações nos templates das lives

Atualizar as informações dos tamplates das lives.

https://drive.google.com/drive/folders/1LRy2S1MXQVLZdWucMjl7WpWKCOGKDo_A

atualizados. o ccomputador do datacenter já está com os templates novos. agora preciso atualizar o computador da sala do caimi


text:
Not Finding Violations

@packocz  - I must be missing something, I just don't know what. Each time I run the scan, it always comes back clean. But when I scan it using SFCA directly, violations are found. Not sure why. My simple test is to take a very poorly coded class, format the file, commit, and then run the scan.
name: Automated Quality Gate
on:
    workflow_dispatch:
    pull_request:
        types: [labeled]
        branches: [main]
jobs:
    review:
        name: ReviewSource
        runs-on: ubuntu-latest
        if: ${{ github.event.label.name == 'review' }}
        steps:
            - name: Code Review
              uses: pragmatic-bear/sfdx-code-review-action@v0.5.1
              with:
                  pmdconfig: level-1-class-ruleset.xml
                  github_token: ${{ secrets.GITHUB_TOKEN }}

I also tried removing the pmdconfig option, as maybe my ruleset wasn't being found. But the result was still the same.

Hi @lukeb-tph
can you share the log from your action? Or a link to the repo if it's public.
It's hard to see what could be wrong without more info
Thanks

Hi @lukeb-tph
can you share the log from your action? Or a link to the repo if it's public.
It's hard to see what could be wrong without more info
Thanks

Thank you Aleš! Yes, here is the downloaded Log Archive.
logs_24.zip

I don't see anything obvious there @lukeb-tph.
When you run the scanner directly (I assume this is locally) are you doing the same git diff to limit the scope of the scan? Are there really changed files in the PR?

@packocz, l added another messy file to the PR and the command looks good, it returns force-app/main/default/classes/AgentLeadCleanUpBatch.cls,force-app/main/default/classes/TS_GenerateDocumentCtrl.cls
I reran the scan, and still no violations.

@lukeb-tph this is super hard to find without access to your repo.
To be safe I re-set my test PR to the bare min (similar to your setting) and it seems to work fine: https://github.com/packocz/investment-tracker-app/pull/36/

hey @lukeb-tph  can you pls try version 0.5.2? Not sure if it was the issue but I did find a issue :-)

@packocz, worth a shot! well, still a clean scan it seems. Could it be something about my repo and how it is set up? Maybe there is a missing permission or something?

@packocz - what level of access would you need to look deeper?

Hey I don't think I could see much more than you are telling me already without full access. That's prob a way we don't want to go.
Good news is I poured through the logs again and found that our problem is definitely the Git Diff. Can you share a screenshot of the PR at the Code Changes tab showing some of the Classes you expect to find violations on?
Something like this:

Feel free to find me on LinkedIn or Twitter for a DM if you don't want to share that here.
You can see @line 2203 in the log you sent me that it comes back empty (there should be a list of files to analyse after the colon).
2023-12-05T14:27:02.7016318Z   DIFF_LIST:
Similarly the output should actually appear also @line 539 in your log
2023-12-05T14:26:18.5993551Z

@packocz - ah, ok! Sure, I think this code is fairly innocuous. Is this what you were asking for?

@lukeb-tph I wonder if Git Diff could (sometimes) ignore formatting (or whitespace) changes only? Not likely, does not sound right.
I have absolutely no idea what's going wrong here :-/

@packocz - strange. well thanks for going the extra mile. I'll close this ticket. All the best!

Don't give up please :-)
try to create a PR where you change some more code (maybe add some System.debug() statements). I would be very interested to find out what caused this.

Ok @packocz, you have inspired me lol. I'll keep at it.

Yo @lukeb-tph did you manage to crack this one?

Hey Ales, I ended up getting the one by Mitch Spano to work, and then lost track of time. I'll try again next week, just for fun, maybe there was just a ghost in the machine. Thanks for following up dude

Negative. Still not finding the violations. Not sure what it is, but I really appreciate the help and follow up. All the best

authors: alesremta-ext43767 lukeb-tph packocz

repo: pragmatic-bear/sfdx-code-review-action


text:
Added Tilting Maze Game

Title and Issue number

This PR closes issue number #1558
Close #1558

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

Inactive

repo: pranjay-poddar/Dev-Geeks


text:
how can we store trends from test to test

Hi we currently uses allure and report-portal for test trends, but they are standalone servers,
I like to use pytest-html-reporter if it can store trends somewhere.
All my tests run in containers, so I have no place to store it unless I create a redis share or a web rest api share.
Any ideas

Store the html file external.

repo: prashanth-sams/pytest-html-reporter


text:
How to use linear-progress with determinate state?

I tried just passing progress as a number between [0, 1], as the MDC docs say to do, but it always renders the progress bar completely full
JSX:
<LinearProgress progress="0.5" />

<LinearProgress ref={pbar=>{this.pbar=pbar}} />
this.pbar.MDComponent. setProgress(0.5)

but yeah, probably we should make this a prop

This code:
componentDidMount = () => {
    console.log(this.pbar);
    this.pbar.MDComponent.setProgress(".2");
};

results in this:

my bad its
this.pbar.MDComponent.progress=0.5

which also makes it way easier to be implemented as a prop

Awesome!
I think progress is defaulting to 1 as well, which on initial load causes an animation from full bar down to whatever your desired initial progress is.
Maybe set this initial progress to 0 instead?

not really sure if initial progress falls under PMC or mdc-web

Are there any plans to make progress a prop?

it is there... sorry the doc says its values are true/false but actually its from 0 to 1
progress={0..1}

authors: mellogarrett prateekbh

repo: prateekbh/preact-material-components


text:
🛑 Prateek Ralhan-Resume is down

In 0370791, Prateek Ralhan-Resume (https://prateek-online-resume-render.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Prateek Ralhan-Resume is back up in cd70a60 after 11 minutes.

repo: prateekralhan/status


text:
🛑 Natural Language <2> SQL Query is down

In 5874b57, Natural Language <2> SQL Query (https://natural-language-2-sql-queries.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Natural Language <2> SQL Query is back up in ed3430e after 12 minutes.


text:
Update AUTHORS.rst (Re-trying of #1155)

This is another PR similar to #1155 but re-trying with the current master branch.

Just a tip, you can rebase your branch next time off the latest master.
git checkout master
git pull
git checkout patch-1
git rebase master
git push --force

If you get conflicts that you aren't sure how to resolve, you can do git rebase --abort, and if all else fails, you can get reset --hard origin/patch-1 to force your branch to be in sync with what is on github.
There's very likely a more concise way to do that, but that's the explicit way.

authors: PokestarFan bboe

repo: praw-dev/praw


text:
Bundle mainnet genesis state

Pairs with https://github.com/penumbra-zone/web/pull/1706

closing https://github.com/prax-wallet/web/pull/163 in favor of this.

@TalDerei feel free to take this over as it pairs with your other work

Looking at the rust code here https://github.com/penumbra-zone/web/blob/main/packages/wasm/crate/src/view_server.rs#L116 , isn't the compact block passed into wasm as a binary-proto-encoded byte array? in that case, wouldn't it be best to store the compact block in that format to avoid serialization overhead, and which would also be smaller to include in the extension manifest?

@TalDerei feel free to take this over as it pairs with your other work

thanks taking over PR 👍

Looking at the rust code here https://github.com/penumbra-zone/web/blob/main/packages/wasm/crate/src/view_server.rs#L116 , isn't the compact block passed into wasm as a binary-proto-encoded byte array? in that case, wouldn't it be best to store the compact block in that format to avoid serialization overhead, and which would also be smaller to include in the extension manifest?

In theory, storing the compact block object in a binary-proto-encoded byte array format should be more efficient in terms of both serialization and space cost.
In terms of serialization, we'll still need to perform a deserialization operation, CompactBlock.fromBinary(new Uint8Array(binaryData)), since the block processor processes and perform checks on the in-memory compact block object before converting it to the binary-proto-encoded byte array that wasm consumes. However, deserializing from binary is more efficient than deserializing from JSON.
In terms of space, the compact block object for the genesis block is ~10 MB, while its JSON representation is ~18 MB. Surprisingly, when serialized to a binary-proto-encoded byte array using compactBlock.toBinary() and saved to a binary file, it takes up ~150 MB.

I'm not sure where those numbers are coming from. The genesis compact block is 8035648 bytes. See https://github.com/penumbra-zone/penumbra/pull/4824 for code to generate the data

I'm not sure where those numbers are coming from. The genesis compact block is 8035648 bytes. See penumbra-zone/penumbra#4824 for code to generate the data

strange blowup, I was simply logging the binary representation of the compact block and manually saving to a file.

Tested this out locally and things are working for me. @TalDerei after publishing the latest packages in penumbra-zone and pulling them in here, think you can merge.
In general, it's nice this saves the 8mb download. However, for a full sync the user will still have to download another +60mb. Connectrpc downloads all of those in parallel to the block sync logic. That said, it's not really noticed on my machine as the CPU/IO tasks are the bottleneck and those downloaded blocks are just waiting to be processed.

That said, it's not really noticed on my machine as the CPU/IO tasks are the bottleneck and those downloaded blocks are just waiting to be processed.

echoing the same sentiment on M3 pro

authors: TalDerei grod220 hdevalence

repo: prax-wallet/web


text:
Changing ammo types?

I've tinkered around with the bindings for hours, both the default and custom for Index controllers. How the heck do you change ammo types in RE2? Default in RB but as far as I can see that's not even an assignable binding. I was able to map the D-Pad to the right touchpad, so at least there's a shortcut for switching guns on the fly with just a flick but I HAVE to be able to change grenade round types.
What's funny is in the inventory menu there are also bumper bindings for changing submenus (files, map, inventory) and THOSE work by clicking in on the upper portion of the touch pad.
I also can't figure out how to bring up the pause menu. The only way to do it is to click the System menu, I guess I could assign systembutton to something, but the binding menu freezes up after opening and closing it a few times. Probably just a software problem with valve, not much we can do about it other than have solid bindings already as the default.

Fixed in de7a6745c68bb35730712c41acc05b59344becac
It's unbound by default. You'll need to change it in SteamVR.

Would I be able to patch this into my game somehow, or would I have to wait until the next release?

Thank you so much, works great I can't wait to play through some more!

authors: bfinz praydog

repo: praydog/REFramework


text:
Ensure all examples are updated to use 1.0-compatible APIs

This includes:

All JSFiddle examples linked from the 'Examples' page
Everything under Prebid.org/examples (which currently 404s, but pages can be accessed directly)

As part of this work, we may also want to consider whether all of these examples are worth maintaining.

I believe this is addressed by #577 thanks to the inimitable @jsnellbaker !

The work to clean out under Prebid.org/examples will be tracked in https://github.com/prebid/prebid.github.io/issues/602


text:
OneVideo Adaptor : CCPA support

adding CCPA support in docs , changes are already merged : https://github.com/prebid/Prebid.js/pull/4571

@bretg review pls

Confirmed part of 3.1

authors: DeepthiNeeladri bretg


text:
lockr AIM

Providing recommended tweaks to the documentation for lockr AIM. Appreciate you working with us.
🏷 Type of documentation

[x] new feature

📋 Checklist

[x] Related pull requests in prebid.js or server are linked -> https://github.com/prebid/Prebid.js/pull/11159

@KEPlockr can you take a look at Bret's comments?

We are working on comprehensive edits based on Bret's comments.
On Fri, May 10, 2024 at 5:56 AM, Muki Seiler @.***>
wrote:

@KEPlockr https://github.com/KEPlockr can you take a look at Bret's
comments?
—
Reply to this email directly, view it on GitHub
https://github.com/prebid/prebid.github.io/pull/5278#issuecomment-2104315352,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARZLKJY7UY2G33KOQJFZ2IDZBSKWXAVCNFSM6AAAAABGVJ5USCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBUGMYTKMZVGI
.
You are receiving this because you were mentioned.Message ID: <
@.***>


text:
Allow DataFrame.sort_values by a single column name

according to the documentation, by= can be a str or a list of str

Thanks!

authors: melentye thomkeh


text:
Check if socket is resource before reading

Per your request, here is the PR for checking if the socket is a resource prior to reading.

This can't hurt and won't impact performance that much.

This is a dumb question but I already have 2.02 in my composer.lock and I can't seem to get this file change down. Do you need to bump to 2.03 so I will get the change?

Do you need to bump to 2.03 so I will get the change?

Yes, a new release needs to be done for it to appear.
Note: you can try out releases before they are done by using 2.0-dev as version (at your own risk)

Wouldn't it be dev-main?

Thanks. Do you know when your next release is planned? We would like to get this fix into production as soon as we can. We have other packages that reply on predis that we moved to “^2.0” in composer from 1.1.
From: Markus Podar @.>
Date: Monday, September 19, 2022 at 1:48 AM
To: predis/predis @.>
Cc: streamingsystems @.>, Author @.>
Subject: Re: [predis/predis] Check if socket is resource before reading (PR #802)
Do you need to bump to 2.03 so I will get the change?
Yes, a new release needs to be done for it to appear.
Note: you can try out releases before they are done by using 2.0-dev as versionhttps://github.com/predis/predis/blob/42c33a406f1fc8f63dc91a2cc32a5fd832659ec6/composer.json#L47 (at your own risk)
—
Reply to this email directly, view it on GitHubhttps://github.com/predis/predis/pull/802#issuecomment-1250630678, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOI5PRLKG2HNSWJ2BPSXHITV7AECNANCNFSM6AAAAAAQPTTMOU.
You are receiving this because you authored the thread.Message ID: @.***>

@streamingsystems: Tagged v2.0.3 just now.

authors: mfn streamingsystems tillkruss

repo: predis/predis


text:
feat: Implement more functions for pixi add --pypi

This pr adds:
pixi add --pypi "boltons @ https://files.pythonhosted.org/packages/46/35/e50d4a115f93e2a3fbf52438435bb2efcf14c11d4fcd6bdcd77a6fc399c9/boltons-24.0.0-py3-none-any.whl"
pixi add --pypi "exchangelib @ git+https://github.com/ecederstrand/exchangelib"
pixi add --pypi "project @ file:///absolute/path/to/project"

TODO:

[ ] Editable flag
[ ] Remove unwraps
[ ] Improve UX of the path style. (now seems to need absolute path, but this is not pixi like)

Would be nice:

[ ] Git branch
[ ] Git tag
[ ] Be able to only specify the source without the name (remove boltons @)

Did you try this? As the problem when I tried this was in the parsing of the url itself.

thanks for taking this over! :)

authors: ruben-arts wolfv

repo: prefix-dev/pixi


text:
Add Cursor.LastPage to retreive newer entries

I'm not sure if I understood pagination correctly and I have to admit that this is my first Go project, but at least this works for me and keeps downloading the newest entries.

Most people use web sockets to get the latest info. I've added a PrevPage method to navigate back and forth between pages. Technically you can get the last page, by storing the before header from the initial request and keep polling it till the before header is different/not empty. This is much less efficient than using websockets though

authors: BeckmaR preichenberger

repo: preichenberger/go-gdax


text:
Running vimux on a server without admin privileges

I am attempting to run vimux's commands in a tmux session on a server for which I am not an administrator. For example, when executing the following within vim:
:call VimuxRunCommand('ls')
I receive the following errors:
Error detected while processing function VimuxRunCommand..VimuxSendKeys.._VimuxTmux:
E484: Can't open file /tmp/vzyU75B/16
Error detected while processing function function VimuxRunCommand..VimuxSendText..VimuxSendKeys.._VimuxTmux:
E484: Can't open file /tmp/vzyU75B/17
Error detected while processing function VimuxRunCommand..VimuxSendKeys.._VimuxTmux:
E484: Can't open file /tmp/vzyU75B/18
Naively, I'm guessing that I'm getting these errors because of some user permissions that I lack. Is this correct, and if so, is there a way around this? Thanks.

Got the same issue even in sudo.

nevermind, i completely didn't get that you would need to run vim in a tmux session.

@briandepasquale Are you running vim inside or outside tmux?

Inside (I think). My comment is from a while back and I can't remember what I was doing...

Are you by chance running VIM from some containerized packaging such as Snap or Flatpack?

No

authors: alerque briandepasquale lionel75013

repo: preservim/vimux


text:
🛑 Beta is down

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

HTTP code: 400
Response time: 643 ms

Resolved: Beta is back up in aa667f0.

repo: presquelabs/upptime


text:
🛑 Beta is down

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

HTTP code: 400
Response time: 661 ms

Resolved: Beta is back up in b8e8d11.


text:
unit testing without postgres dependency (mock)

Discussed in https://github.com/prest/prest/discussions/562

Originally posted by avelino June 23, 2021
The postgres adapter depends on the postgreSQL (database) server to run (go test), i.e. it was developed with integration testing.
Integration testing is necessary, but it raises the barrier for new members to contribute, i.e. for a person to make any contribution he needs to learn to configure the development environment and only then contribute. I think it's great to have people immersed in the project, but this is not the reality of open source projects that people contribute in their spare time (usually without pay)
I don't think it is necessary to "remove" the integration test but put it in its place:

unit test that does not depend on external services (e.g. PostgreSQL) running with go test ...., so our people were able to run the tests locally (on their machines)
Integration test: run only on CI (GitHub Actions or Travis CI) on pull request - doesn't necessarily have to be written with go test

What would be the best option to write postgres adapter mock?
Ref:

[x] #510
[x] #555
[x] #558
[x] #472
… as we see above we have several issues related to this subject - sad

Is this still open?

Is this still open?

@vmesel yep, we need to rewrite the tests with unit tests in mind, this simplifies the way to run the tests for the incoming contributors
Leave the integration test (e2e) as we do for the build process (in the pipeline, even so we need to think if it is necessary)

authors: avelino vmesel

repo: prest/prest


text:
single TupleDomain constraint for multiple splits

In case the constraint is large sending the constraint (TupleDomain) per split is wasteful (for the case the constraint is the same per split).
In our connector we have relatively large number of small splits and we've stumbled upon the use case of querying for 10K string keywords in a single query we hacked/fixed it by adding the constraint to TaskSource and then infest it to all its splits.
Does it makes sense? Is this approach acceptable? Would it be more clean to add another kind of connectorHandle per taskSource?

The information is contained in the TableHandle associated with the TableScanNode. What we might need to do is change the PageSourceProvider API to take the TableHandle in addition to the Split. That way, anything that's common for the whole query doesn't need to be included in every split (only what's relevant to a split).
This is going to be important to support pushdown of complex operations and whole subplans into connectors. We certainly don't want connectors to have to embed a copy of the subplan in every split! (relates to https://github.com/prestosql/presto/wiki/Pushdown-of-complex-operations)

authors: kabunchi martint

repo: prestosql/presto


text:
Fix - Add default timeout to XMLHttpRequest

This proposed change is to fix a bug when using Pretender with React Native in Android. If the Pretender request is passthrough and synchronous, Pretender does not assign a timeout to the xhr request variable. When the request is dispatched and reaches native code, it errors out:
Attempt to invoke virtual method 'double java.lang.Double.doubleValue()' on a null object reference

This is due to the Android native library expecting a numeric timeout value.
NativeNetworkingAndroid.js Code
  +sendRequest: (
    method: string,
    url: string,
    requestId: number,
    headers: Array<Header>,
    data: Object,
    responseType: string,
    useIncrementalUpdates: boolean,
    timeout: number,
    withCredentials: boolean,
  ) => void;

NetworkingModule.java Code
@Override
  public void sendRequest(
      String method,
      String url,
      double requestIdAsDouble,
      ReadableArray headers,
      ReadableMap data,
      String responseType,
      boolean useIncrementalUpdates,
      double timeoutAsDouble,
      boolean withCredentials) {

To Dos:

Update tests in passthrough_test.js since now we are always adding a timeout, and this test will fail.

Not sure who I should mention, but based on the contributor list and organization:
@bantic @xg-wang @mike-north @trek

This looks fine. I think if you can fix the failing test to say assert.equal(xhr.timeout, 0); it would pass.
That said tho, I'm confused by the fact timeout could be null/undefined here, because if the default is 0 when the xhr is created, i.e.,
let xhr = new XMLHttpRequest()
console.log(xhr.timeout)  // prints 0

Do you know in your case is there code that deletes the timeout?
Also sync xhr are not allowed to set timeout in a document environment per MDN

Timeout shouldn't be used for synchronous XMLHttpRequests requests used in a document environment or it will throw an InvalidAccessError exception.

The following code will throw (https://codepen.io/xg-wang/pen/BaRmXOR)
const xhr = new XMLHttpRequest();
xhr.open('GET', '/server', false);
xhr.timeout = 0; // pen.js:5 Uncaught DOMException: Failed to set the 'timeout' property on 'XMLHttpRequest': Timeouts cannot be set for synchronous requests made from a document.
xhr.send(null);

No, I'm not changing the request directly nor indirectly. The package being used by node does not behave like the example you posted though.

According to the source, this is the package Pretender is utilizing: xmlhttprequest-ssl

@bombillazo ah that ponyfill is not spec compatible, looks like repo does not have issue section, not sure if we can submit a bug report to xmlhttprequest-ssl.
I commented on your commit https://github.com/hecdemi/pretender/commit/51a93c95b328a1d233015b25faefc1c910057663#commitcomment-53987232. We can add a compatibility check here but I'd want to add more context to the change.

https://www.npmjs.com/package/pretender/v/3.4.4

This PR appears to have created a new bug:
Error: Failed to set the 'timeout' property on 'XMLHttpRequest': Timeouts cannot be set for synchronous requests made from a document.
    at createPassthrough (webpack://__ember_auto_import__/./node_modules/pretender/dist/pretender.es.js?:1453:17)
    at FakeRequest.passthrough (webpack://__ember_auto_import__/./node_modules/pretender/dist/pretender.es.js?:1493:15)
    at FakeRequest.send (webpack://__ember_auto_import__/./node_modules/pretender/dist/pretender.es.js?:1482:12)
    at takeScreenshot (http://localhost:7357/assets/test-support.js:23526:9)
    at http://localhost:7357/assets/test-support.js:23565:37
    at invokeCallback (http://localhost:7357/assets/vendor.js:71723:17)
    at publish (http://localhost:7357/assets/vendor.js:71706:9)
    at http://localhost:7357/assets/vendor.js:66030:9
    at invoke (http://localhost:7357/assets/vendor.js:64236:16)
    at Queue.flush (http://localhost:7357/assets/vendor.js:64127:13)"

We may need to revisit this bugfix and find a way to solve the original problem without introducing this regression for scenarios where pretender was previously working.

From the discussion, the root cause is the spec incompatible polyfill depedency is utilizing for node XMLHttpRequests. The docs do disclaim there are missing features.
I am no longer using the library which depended on Pretender, but my solution pre-PR merge was to use patch-package to keep my changes. So we could revert this while a more robust solution is implemented.

authors: bombillazo elwayman02 xg-wang

repo: pretenderjs/pretender


text:
Not working with eslint

Hello, I'm using eslint v7.2.0. Everything was working fine until I ran a few updates which updated VSCode and some other programs. I've configured eslintrc to work with prettier, but when saving the file, prettier formats it in a different way (eslint config allows 2 spaces for tabs whereas prettier includes 4 spaces per tab). Below is my eslintrc.js
Any solutions on how to fix this and make eslint work with prettier?
module.exports = { 	env: { 		browser: true, 		es2020: true, 	}, 	extends: ['plugin:react/recommended', 'plugin:prettier/recommended'], 	parserOptions: { 		ecmaFeatures: { 			jsx: true, 		}, 		ecmaVersion: 11, 		sourceType: 'module', 	}, 	plugins: ['react'], 	rules: { 		quotes: [2, 'single', { avoidEscape: true }], 		'react/jsx-filename-extension': [1, { extensions: ['.js', '.jsx'] }], 		'prettier/prettier': 'error', 	}, };
Edit: In VSCode, the following is the error thrown after running eslint filename.js

Hi!
Your config looks good other than the quotes rule which you should remove.
To troubleshoot things like this, it’s the easiest to first take VSCode out of the question. Focus on getting it working on the command line.
Try to make a minimal repo that reproduces the issue. Many times, you’ll find the issue while doing so! Remove stuff until it doesn’t happen anymore. Then you should find what’s wrong! If not, push your minimal repo to github and I can take a look at it.
When it’s working from the command line it’s time to start trying in VSCode again.

Thank you for the response lydell. I did the whole thing all over again, and it seems that .prettierrc file was missing. I really didn't bother about it much as there was only one rule in that which was { "singleQuote": true}. But adding this file and this single rule surprisingly fixed the issue. Now eslint and prettier are going along well.

Ah, makes sense. Prettier defaults singleQuote to false (which means double quotes), so if you want single quotes you need to configure that in Prettier. (Also using the quotes rule in ESLint provides nothing but potential conflicts, though.)

authors: lydell prashanthwagle

repo: prettier/eslint-config-prettier


text:
[PRIMAUK-3642]: Stonehenge - update for Telepoison updates

As per the commit, updates the version of Telepoison used
https://prima-assicurazioni-spa.myjetbrains.com/youtrack/issue/PRIMAUK-3642

~> 1.0.0 already includes 1.0.1, and I don't see a reason to force library users to update if it's not necessary. Updating the mix.lock file in stonehenge to teleplug 1.0.1 should be enough to make all other libraries also use teleplug 1.0.1
https://github.com/primait/stonehenge/blob/c3238c28e09248ed30718c1fd8d0e840c403cee3/mix.lock#L166

I agree that libraries shouldn't necessarily bump the minimum version, so I'd leave ~> 1.0 here
Stonehenge can then safely use all the 1.0.1 versions because they are supported by the ~> 1.0 clause

Sorry chaps - it's the minor version that should have been updated, so 1.1.0 - do this make a difference?

I don't think we need to do this, there's no reason to force people to use a 1.1.x min version

authors: MaeIsBad cpiemontese michael-a-grammar


text:
this is a test

this is a test

Sorry on the wrong project

repo: primefaces/primeng-sass-theme


text:
Release tracking

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@primer/react-brand@0.33.0
Minor Changes

#575 89d6590 Thanks @rezrah! - New pagination component generally available
<Pagination pageCount={15} currentPage={5} />

:link: Read the documentation for more examples

#574 95f15ba Thanks @rezrah! - New breadcrumbs component generally available
<Breadcrumbs>
  <Breadcrumbs.Item href="/">Resources</Breadcrumbs.Item>
  <Breadcrumbs.Item href="/copilot">GitHub Copilot</Breadcrumbs.Item>
  <Breadcrumbs.Item href="/copilot/chat" selected>
    Chat
  </Breadcrumbs.Item>
</Breadcrumbs>

:link: Read the documentation for more examples

#555 3980daa Thanks @rezrah! - Added new IDE component
Example:
<IDE alternativeText="description of the IDE, including any animations for users of assistive technologies">
  <IDE.Editor />
  <IDE.Chat />
</IDE>

🔗 See the documentation for more examples

Patch Changes

#568 40a129d Thanks @rezrah! - Added support for optional Button and sub menu's in SubNav component.
Also added fullWidth prop to optionally remove the default component padding.
<SubNav>
  <SubNav.Heading href="#">Heading</SubNav.Heading>
  <SubNav.Link href="#">Link</SubNav.Link>
  <SubNav.Link href="#">Link</SubNav.Link>
  <SubNav.Link href="#">Link</SubNav.Link>
  <SubNav.Link href="#" aria-current="page">
    Link
    <SubNav.SubMenu>
      <SubNav.Link href="#">Link feature one</SubNav.Link>
      <SubNav.Link href="#">Link feature two</SubNav.Link>
      <SubNav.Link href="#">Link feature three</SubNav.Link>
      <SubNav.Link href="#">Link feature four</SubNav.Link>
    </SubNav.SubMenu>
  </SubNav.Link>
  <SubNav.Link href="#">Link</SubNav.Link>
  <SubNav.Link href="#">Link</SubNav.Link>
  <SubNav.Action href="#" variant="secondary">
    Optional CTA
  </SubNav.Action>
</SubNav>

#566 eaeb50e Thanks @joshfarrant! - Adjusted block padding of small button controls from 12px to 8px.
This change affects all small size Button and ActionMenu instances.

#575 89d6590 Thanks @rezrah! - Added none optiona to arrowDirection prop of Link component. This value removes the arrow entirely.
<Link arrowDirection="none" {...rest} />

#573 e76c92b Thanks @joshfarrant! - Add trailingComponent prop to Hero

@primer/brand-primitives@0.33.0
Patch Changes

#566 eaeb50e Thanks @joshfarrant! - Adjusted block padding of small button controls from 12px to 8px.
This change affects all small size Button and ActionMenu instances.

@primer/brand-storybook@0.33.0
@primer/brand-e2e@0.33.0
@primer/brand-fonts@0.33.0
@primer/brand-config@0.33.0

Smoke test: 23/04/24
❌  Subnav changes

internal paddings require overriding

❌  IDE changes

CSP issues with file extension icons

Text sizes being overridden by dotcom

✅  Pagination
✅  Button updates

Smoke test: 25/04/24
All aforementioned issues resolved through #580
✅  Subnav changes - fullWidth prop added to remove internal padding
✅  IDE component - tabIcons prop provided for CSP compliance
✅  Pagination
✅  Button updates
Result:

Release good to go 🚀

authors: primer-css rezrah

repo: primer/brand


text:
24px - Repo fork

https://www.figma.com/file/2rjsQp42uKvzPXzLZIqOeA/Octicons-v2-Source?node-id=786%3A916

We have this icon already. Closing this issue

authors: ashygee edokoa


text:
Support plan for Next.js ？

Is there a plan for Primer Design System components to support Next.js?
Using client-side components on Next.js has become quite painful.

Hi @meiyingqishi 👋 We support Next.js and you can also access our internal example of Next.js to see how we set up the project and utilize Primer React components there. I'm going to go ahead and close this issue but please report back if you are having any specific issues with compatibility of our components with Next.js.

Thank you for your response.  @broccolinisoup

The example you provided is from a Next.js pages project. The current mainstream approach is using Next.js app projects, and the situation has changed. Components are now defaulting to server-side components, while the Primer Design System components are client-side components. When the implementation of a component involves the use of React's client-side APIs, such as hooks like useState, it will result in runtime errors (Server Error
Error: createContext only works in Client Components. Add the "use client" directive at the top of the file to use it. Read more: https://nextjs.org/docs/messages/context-in-server-component).

The solution is to create a separate file and add 'use client' at the beginning of the file. Then, import this file in the page.tsx where it is used. However, creating a file like this for each component can become tedious and cumbersome.

I have reviewed the official documentation for the Primer Design System and did not find such a description or solution. My question is, do you have any plans to default to adding 'use client' in the component code files in the future? This would help alleviate many potential issues when using the components in the future.

Hi @meiyingqishi 👋 Sorry when I read the issue, it didn't occur to me that you are talking about the new app router and React Server Components! I appreciate you provided details. I am chatting about this with my team to see how we can support it. I'll re-open the issue and rename it to "Support for Next.js app router" and you can subscribe to this issue to get updates on the support. Thanks for bringing it up and raising the issue.

Hi @meiyingqishi, we have another issue opened that dives deeper into the server components, feel free to have a read.
We also have a draft PR that addresses the issue you mentioned here.

Hi there! 👋 Just wanted to follow up on this now that: https://github.com/primer/react/pull/4128 is merged and available in v36.6.0
Components should be directly usable from @primer/react without requiring 'use client' marker on the page or in components that call it when using app router with Next.js.
Going to close this out but feel free to leave a comment or provide any feedback if this is not working as expected!

Thank you! It worked.

Create and initialize the front-end project in terminal (pnpm): pn create primer-app;
Navigate to the directory: cd primer-app;
Add dependencies: pn add @primer/react @primer/css @primer/octicons-react styled-components@^5;
Import the project into vs code：code .;
Modify layout.tsx:

import {
  BaseStyles,
  ThemeProvider,
} from "@primer/react";

export default function RootLayout({
  children,
}: Readonly<{
  children: React.ReactNode;
}>) {
  return (
    <html lang="en">
      <body>
        <ThemeProvider>
          <BaseStyles>{children}</BaseStyles>
        </ThemeProvider>
      </body>
    </html>
  );
}

Modify page.tsx:

import {
  Button,
} from "@primer/react";

export default function Home() {
  return (
    <main>
      <Button>Hello Button</Button>
    </main>
  );
}

Run in vs code terminal: pn dev;
View in browser: http://localhost:3000.

@meiyingqishi That doesn't solve the SSR problem. You get CSS-in-JS where the styling is injected at runtime, on the client.
You actually get pretty far with:
import StyledComponentsRegistry from "@/lib/registry";

export default function RootLayout({
  children,
}: Readonly<{
  children: React.ReactNode;
}>) {
  return (
    <html lang="en">
      <body>
        <StyledComponentsRegistry>
          <ThemeProvider>
            <BaseStyles>
              <Inner>{children}</Inner>
            </BaseStyles>
          </ThemeProvider>
        </StyledComponentsRegistry>
      </body>
    </html>
  );
}

It works. But I get very strange warnings in development mode that I don't understand.

Hi there, @peterbe! We have an App Router example over at: https://github.com/primer/react/tree/main/examples/app-router if it's helpful (there is one change that needs to happen from https://github.com/primer/react/pull/4307)
Would love to hear any feedback you have for that example and if it works or doesn't work for your use-case. I believe it should handle the SSR case for styles using the guide from Next.js but let me know if there are any issues!

Hi there, @peterbe! We have an App Router example over at: https://github.com/primer/react/tree/main/examples/app-router if it's helpful (there is one change that needs to happen from #4307)

Yay!
Now I can't even remember how I stumbled into https://github.com/primer/react/tree/main/examples/nextjs in the first place. Perhaps by a Google search??

Would love to hear any feedback you have for that example and if it works or doesn't work for your use-case. I believe it should handle the SSR case for styles using the guide from Next.js but let me know if there are any issues!

I got things working. SSR and all. Used your draft from https://github.com/primer/react/pull/4307 and not a warning or error in sight.
What tripped me up, and can be seen in my screenshot above, was that the link on https://primer.style/react/getting-started#static-css-rendering to styled-components made me think I had to use styled-components@6 when it's styled-components@5 that is a must.

Hi there, @peterbe .
Yes, I also encountered some difficulties before and discovered this issue. That's why I added styled-components@^5 in the dependencies. I'm sorry for not making it very clear in my previous response.

Hi @joshblack ,
I accidentally tried the primer design system again and found there's still an issue. When using individual components like Button, there are no problems. However, errors occur when using composite components (involving child components, using a period), for example:
<ActionList>
    <ActionList.Item>Copy link</ActionList.Item>
    <ActionList.Item>Quote reply</ActionList.Item>
    <ActionList.Item>Edit comment</ActionList.Item>
</ActionList>

The issue lies with the ActionList.Item here. I've encountered this problem while using other components (such as react-bootstrap) as well. Their solution is to add additional components (for example: ActionListItem).

authors: broccolinisoup joshblack meiyingqishi peterbe

repo: primer/react


text:
Add interaction tests for pagelayout sticky

Add a couple of interactive tests
To test this, check PageLayout/interactions.stories

This is great. Thank you for setting this up, @pksjce! A couple of questions:

Do these interaction tests run during CI? Specifically, will CI fail if we accidentally break an interaction?
When I run this locally, is this what we expect the interaction tab to look like?

I kinda messed up this branch badly. So I'll close this PR and open a new one.
@colebemis - Thanks!

Yes they run on CI. On CI, playwright runs these "storybook tests". Will mention it in the new PR.
The interactions for this test don't seem to be very expressive on the addon. There's also the problem that scrollIntoView does not come under any of the "actions" that this addon recognises. As mentioned in this https://storybook.js.org/addons/@storybook/addon-interactions at the very end, its

calls to userEvent., fireEvent, findBy, waitFor* and expect
that get shown in the step by step debugger.

However, I have some hope that this is being improved. In storybook 7.0.0 versions, there's improvements like this https://github.com/storybookjs/storybook/pull/18555 , which help us have more expressive data in that addon. I feel that the addon is still new and not so mature yet.

authors: colebemis pksjce


text:
Loss Function Question

I was looking at loss.py. What is the goal of line 27: flow_loss += .01 * i_weight * (i_loss).mean(). If you include this term, shouldn't it include the valid mask so that it's flow_loss += .01 * i_weight * (valid * i_loss).mean()?

the intuition behind this is to encourage the model to output 0 disparity when there is no gt, e.g., in the background, at least it helps visually. I am not sure how this could affect quantitative evaluation.

authors: mazeyu tom-bu

repo: princeton-vl/CER-MVS


text:
How to use the Output

Thank you for this great work. Stuck at a point that how can I store or use or call the output , so that I can publish it .
Kindly help me out , Thank you in advance

@pradyumnakulkarni87 Have you figured it out?

repo: princeton-vl/DROID-SLAM


text:
似乎是使用不了了？

尝试录制了一下斗鱼和twitch，都提示如下
“The stream is not available now.
Retry after 10 seconds...
”
是不是脚本已经失效了？
我尝试录制的都是正在直播的

请参考 https://github.com/streamlink/streamlink/issues/2328

Closing due to long period of inactivity. Feel free to reopen it if you still encounter this issue with the latest version! :)

authors: Kafuziroh gitby2018 printempw

repo: printempw/live-stream-recorder


text:
Format on saves failure

Using the latest formatter (v2.8.0) on MacOS, I always get an error when trying to format the document.
If I call the rust formatter manually I get:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 9, kind: Other, message: "Bad file descriptor" }', libs/datamodel/core/src/ast/reformat/reformatter.rs:88:38
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Internal discussion that might have some more information: https://prisma-company.slack.com/archives/CBJCQF95M/p1601920056000500

Hi @Sytten! Are you still having that issue with 2.8.2?
From what you are describing, it seems like you are not using the extension, is this correct?
The error you received when trying out the binary manually hints that you may have missing permissions to read the file in the first place (Err value: Os { code: 9, kind: Other, message: "Bad file descriptor" }`). What binary were you using, the one from the extension in the extensions folder or the one from inside your Prisma project?

I am going to give it a try next week.
I am using the extension, but then I tried to do it manually with the binary in the node modules.
Interesting that it would miss permissions I will check that as well. I can open and save the file no problem so I didn't think that it might be a problem.

So more details, I got some logs out of the developper console:
 ERR No application in the Launch Services database matches the input criteria.: Error: No application in the Launch Services database matches the input criteria.

This is printed every time I try to save the file. This might be related to https://github.com/prisma/language-tools/issues/604

Since #604 is fixed, are you still getting this error?

Yes last time I checked, let me try again.

Seems to be fixed

authors: Sytten carmenberndt janpio

repo: prisma/language-tools


text:
d1 support

I'm working on getting CloudFflare d1 support for Prisma with Nuxt Hub, I've created this issue to help track my progress, so far this version of server/utils/prisma.ts is working for me.
import { PrismaD1 } from '@prisma/adapter-d1'
import { PrismaClient } from '@prisma/client'
import type { D1Database } from '@nuxthub/core'
import type { EventHandlerRequest, H3Event } from 'h3'
import models from '../models/index'

export function useDB(event: H3Event<EventHandlerRequest>): D1Database {
  return event.context.cloudflare.env.DB as D1Database
}

let prismaClient: PrismaClient
export function usePrisma(event: H3Event<EventHandlerRequest>) {
  if (!prismaClient) {
    const adapter = new PrismaD1(useDB(event))
    prismaClient = new PrismaClient({ adapter })
  }
  return prismaClient
}

My current challenge is how to run local migrations:

Cannot use npx prisma migrate because it doesn't harness the d1 driver
Cannot use wrangler because it goes after the .sqlite files in .wrangler and not .data

Any suggestions/tips/etc would be appreciated, I'll update this issue as I progress

bump
i like prisma, but switching to nuxt/nuxthub currently
would like to see prisma integrated with D1 too 👍

hmmm...
nuxthub says this is implemented on prisma's side, and they are currently reviewing the docs for nuxt
https://volta.net/nuxt-hub/core/issues/38
I found this on cloudflare, but doesn't seem related to nuxt
https://developers.cloudflare.com/d1/tutorials/d1-and-prisma-orm

hmmm...
nuxthub says this is implemented on prisma's side, and they are currently reviewing the docs for nuxt
https://volta.net/nuxt-hub/core/issues/38
I found this on cloudflare, but doesn't seem related to nuxt
https://developers.cloudflare.com/d1/tutorials/d1-and-prisma-orm

I have this working on this repo https://github.com/fumeapp/bio
I plan to hopefully contribute to those docs, one major change I had to make is to stop using the prisma nuxt module

BTW a full working version of nuxt+prisma+hub+d1 can be found here https://github.com/fumeapp/bio
One tip: remove the prisma nuxt module

BTW a full working version of nuxt+prisma+hub+d1 can be found here https://github.com/fumeapp/bio
Please note that until this gets in the module, I had to remove it.

Tnx, will have a look 👍

authors: acidjazz robert-hoffmann

repo: prisma/nuxt-prisma


text:
Regenerating Photon causes API in development to crash

With a postinstall hook, prisma generate runs on all yarn add operations, this causes an API in development with hot reload to fail for a few moments when the generation is happening as it cleans the node_modules up.
Related issue: https://github.com/prisma/photonjs/issues/88
More on this context:

I was using ts-node-dev at the time and it totally crashed (had to re-run.)
Now switched to Babel + Nodemon, the same thing happens and I have to re-run.

A potential solution to this could be to generate photon into a temporary directory and then swapping that in the main directory atomically using symlink.
Problems with this approach (not-exhaustive):

Might not work on windows
Might not be registered as a change by editors (for auto-completion etc)

Reproduction: https://github.com/divyendu-test/photonjs-234
GIF of reproduction: https://divyendu.s3-eu-west-1.amazonaws.com/photonjs-234-2.gif
The solution I proposed earlier won't work as this is happening while yarn pruning and not prisma2 generate.

This has been fixed by introducing the facade package 🎉

authors: divyenduz momakes timsuchanek

repo: prisma/photonjs


text:
Consider adding a helper method to return a slice of raw models

If I have a case like
user, err := db.Client.User.FindMany(
    db.User.Name.Contains(query),
).Exec(ctx)

How do I convert []db.UserModel to []db.RawUser?
We could add automatically generated helper methods to convert between these slices. These could even be types of custom slice types (type UserSlice []User) so we can define a method on that type – but this may have unintended side effects.
As suggested by @tarrencev, we could also introduce a chain method which would return that type:
user, err := db.Client.User.FindMany(
	db.User.ID.Equals(id),
).Raw().Exec(ctx)

Or even (by @matthewmueller):
user, err := db.Client.User.FindMany(
	db.User.ID.Equals(id),
).Raw(ctx)

let's also consider renaming Raw since it's an entirely different concept than Raw queries. This is more like getting the POJO (plain old javascript object), in our case POGS (plain old javascript struct/slice).
Some possibilities:

Inner
Output

Not in love with either, if you have any ideas please let us know!

I think Inner is probably a good choice for now. At least better than Raw, which may be confused with unrelated raw queries.

Sounds good.

Would love to land this soon :)

Would love to land this soon :)

A common use case for this is to use it with incompatible libraries such as gqlgen. I'll build this feature soon to have a temporary fits-all solution, however ideally we will make it compatible with gqlgen directly which is tracked in #371.

A common use case for this is to use it with incompatible libraries such as gqlgen. I'll build this feature soon to have a temporary fits-all solution, however ideally we will make it compatible with gqlgen directly which is tracked in #371.

I need to make a final decision on syntax.
WDYT about this:
user, err := db.Client.User.FindMany(
	db.User.ID.Equals(id),
).ExecInternal(ctx)

// or

user, err := db.Client.User.FindMany(
	db.User.ID.Equals(id),
).InternalExec(ctx)

Right now the struct is called "Internal", which is why this method would be called InternalX as well.
Now that I think about this method, internal sounds kinda weird, "inner" would probably make more sense. However if we would change the name it would be a breaking change for users depending on the internal structs.

I need to make a final decision on syntax.
WDYT about this:
user, err := db.Client.User.FindMany(
	db.User.ID.Equals(id),
).ExecInternal(ctx)

// or

user, err := db.Client.User.FindMany(
	db.User.ID.Equals(id),
).InternalExec(ctx)

Right now the struct is called "Internal", which is why this method would be called InternalX as well.
Now that I think about this method, internal sounds kinda weird, "inner" would probably make more sense. However if we would change the name it would be a breaking change for users depending on the internal structs.

FWIW, Internal makes me think I'm doing something I shouldn't be doing. Calling some internal Prisma Client method. Your call though.

Now that I think about this method, internal sounds kinda weird, "inner" would probably make more sense. However if we would change the name it would be a breaking change for users depending on the internal structs.

Deprecate & alias?

FWIW, Internal makes me think I'm doing something I shouldn't be doing. Calling some internal Prisma Client method. Your call though.

Now that I think about this method, internal sounds kinda weird, "inner" would probably make more sense. However if we would change the name it would be a breaking change for users depending on the internal structs.

Deprecate & alias?

Yeah exactly. I don't remember why I chose this wording back then :(
I think it may be worth deprecating Internal and renaming to Inner; that should be fairly simple to do in the generator templates.

Yeah exactly. I don't remember why I chose this wording back then :(
I think it may be worth deprecating Internal and renaming to Inner; that should be fairly simple to do in the generator templates.

authors: matthewmueller steebchen tarrencev

repo: prisma/prisma-client-go


text:
[Feedback] Introspection of embedded documents / composite types in MongoDB

Summary
Introspection of embedded documents in MongoDB is available as a preview feature.
To use it, simply run
npx prisma db pull --force

Note: we use the --force flag here as re-introspection is not supported with MongoDB. Just omit that if you run it only once.

against a MongoDB database and all embedded documents will be analyzed and added to the Prisma schema via type {}. The level of depth can be controlled or switched off via the option parameter:
--composite-type-depth=-1  // Inspect infinite levels of nesting (new default since 3.10.0)
--composite-type-depth=0   // Disable introspection of composite types (default from 3.4 to 3.9 included)
--composite-type-depth=N   // Inspect N levels of nesting

Please use this issue to report any feedback.

Thanks for this feature. It seems to work fine. The prisma cli seems to be confused with ports.
datasource db {
  provider = "mongodb"
  url      = "mongodb://testReadOnlyUser:****@db-rs-11:27017,db-rs-12:27017,db-rs-13:27017,db-rs-14:27017,db-rs-15:27017/default_default?replicaSet=dbMongoDB&maxPoolSize=1000"
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["mongoDb"]
}

gives
Error: invalid port number in database URL
Using this without the ports works fine
mongodb://testReadOnlyUser:****@db-rs-11,db-rs-12,db-rs-13,db-rs-14,db-rs-15/default_default?replicaSet=dbMongoDB&maxPoolSize=1000

Thanks @Hitabis, can you open a standalone issue on this please? Thanks.

Note that the default just changed with 3.10.0 and the default depth is infinite.

Closing as Introspection of embedded documents is in GA

authors: Hitabis Jolg42 floelhoeffel janpio

repo: prisma/prisma