text:
Document clearly the reference frames that are used

🐞 Problem
(This came from user feedback)
We have been tackling several issues regarding reference frames lately (see #215, #222, #243, #245) and we are already thinking in integrating Orbit objects with reference frames (#257), but until we have that, it is not clear in the documentation what reference frames are used for propagation, orbit conversion and other operations. The only mention of a reference frame in the user guide concerns the results from ephemerides:
https://github.com/poliastro/poliastro/blob/v0.8.0/docs/source/user_guide.rst#where-are-the-planets-computing-ephemerides
We should document this very clearly.
🎯 Goal
For those users that care, be very explicit about what assumptions we make and which coordinate systems we use.
💡 Possible solutions
Start documenting. Also reference astropy.coordinates or the Florence notebook.
📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #<put issue number here>
Ask for a review in comments section of pull request
Celebrate your contribution to this project 🎉

I could add a question in a separate thread, but this question is directly applicable to this issue, so I guess it should go here.
Using the sample method returns a tuple containing time and a CartesianRepresentation, which is an astropy.coordinates class.  Plotting the XYZ coordinates contained in the CartesianRepresentation, it's obviously some sort of Earth-centered inertial frame.
On my end, I am looking to convert these coordinates to Earth-centered Earth-fixed (ECEF) coordinates so I can analyze satellite coverage.  This requires knowing which inertial frame the XYZ coordinates are coming from.
I see that additional documentation is a goal in this area, but do you happen to know which frame is being used here?  If you do, I would be happy to write up some simple documentation giving a description of the frame to help your efforts in this area.

Hi @MichaelRThompson! If it's centered on the Earth, ICRS is assumed. If the body is different, it would be a frame parallel to ICRS but with a different center. Does this help?

It does indeed.  Thanks for the help.  I'll see if I can get around to pitching in here and there on this module soon.

Today another person asked this very same thing in the mailing list:
https://groups.io/g/poliastro-dev/message/37
Now I'm convinced to urgently fix this before the next release.

Will take care of this as part of #344.

repo: poliastro/poliastro


text:
这个项目包括socket.io的服务器端吗？

这个项目包括socket.io的服务器端吗？

内置了一个简洁版的socket express

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
yo bower grunt-cli で えらる

npm install -g yo bower grunt-cli
/root/.nvm/versions/node/v4.1.1/bin/grunt -> /root/.nvm/versions/node/v4.1.1/lib/node_modules/grunt-cli/bin/grunt

> spawn-sync@1.0.13 postinstall /root/.nvm/versions/node/v4.1.1/lib/node_modules/yo/node_modules/cross-spawn/node_modules/spawn-sync
> node postinstall

sh: node: command not found
/root/.nvm/versions/node/v4.1.1/bin/bower -> /root/.nvm/versions/node/v4.1.1/lib/node_modules/bower/bin/bower
npm ERR! Linux 2.6.32-431.3.1.el6.x86_64
npm ERR! argv "/root/.nvm/versions/node/v4.1.1/bin/node" "/root/.nvm/versions/node/v4.1.1/bin/npm" "install" "-g" "yo" "bower" "grunt-cli"
npm ERR! node v4.1.1
npm ERR! npm  v2.14.4
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! spawn-sync@1.0.13 postinstall: `node postinstall`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the spawn-sync@1.0.13 postinstall script 'node postinstall'.
npm ERR! This is most likely a problem with the spawn-sync package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node postinstall
npm ERR! You can get their info via:
npm ERR!     npm owner ls spawn-sync
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /root/workspace/js/test-app/public/js/npm-debug.log

fix
https://github.com/ForbesLindesay/spawn-sync
 npm install spawn-sync --unsafe-perm

これ
https://github.com/Unitech/pm2/issues/1359
からのこれ
https://github.com/Unitech/pm2/issues/1359
‘npm config set unsafe-perm true‘
で解決した

Yeoman Doctor
Running sanity checks on your system
✔ Global configuration file is valid
✔ NODE_PATH matches the npm root
✔ Node.js version
✔ No .bowerrc file in home directory
✔ No .yo-rc.json file in home directory
✔ npm version

別件でyoで落ちるとき
vagrantでrootとか使ってると出るのかも
Error: EACCES: permission denied, mkdir '/root/.config'

fix
mkdir -p /root/.config/configstore/
chmod 777 /root/.config/configstore/

license: mit

license_source: bigquery


text:
Cannot Set EthereumPlugin's Network Key Using String

The following code does not compile:
const network = "rinkeby";

ethereumPlugin({
  networks: {
    `${network}`: {
      provider: ...
    }
  }
})

The solution to this is a nuance in JavaScript. String templates are expressions, and expressions cannot be property names. But we can make it work with the addition of an additional syntax element.
ECMA2015 introduced computed property names. To use string templates as property names, we just need to surround them in brackets and the client compiles as expected.
This is okay:
const stringTemplateNetwork = "stringTemplateNetwork";
expect({
  [`${stringTemplateNetwork}`]: {
    provider: ethereum,
  }
}).toStrictEqual({
  "stringTemplateNetwork": {
    provider: ethereum,
  }
})

And this console log:
console.log({
  [`${stringTemplateNetwork}`]: {
    provider: ethereum,
  }
});

Prints the following:
console.log
  { stringTemplateNetwork: { provider: 'http://localhost:8545' } }

authors: dOrgJelli krisbitney

repo: polywrap/monorepo


text:
remove old EBI ftp site warning

I think we can remove:
Warning: S. pombe files are no longer available from the old “pombase” FTP site within the EBI domain. If you have a link that contains ftp.ebi.ac.uk, please check these pages for a link using https://www.pombase.org/. Please contact the PomBase curators if you need help finding a file or directory.
and if people do get tot he EBI directory, this message is in the README:
PomBase is no longer hosted at EMBL-EBI. Please visit
https://ftp.pombase.org/. For release files please see
ftp://ftp.pombase.org

I moved the text to the bottom of the main datasets page, and deleted it from other pages.

repo: pombase/website


text:
Improve the look of the annotation tables (publication pages)

I saw this today and wondered if there bug that caused the gene to be on the wrong row.  Then I remembered that is how it looks on publication pages.  At some point I'd like to re-visited how we format these tables.

Ah OK, this is publication page?

Ah OK, this is publication page?

Yep.
Although I don't like how the genotype is sometimes on the same line as the term and sometimes not.  I think that's a different issue though.

I'm not keen on how the annotation tables look.  Here's how it looks if we take the box around the sections away:

I prefer that....

did you fix the publication pages?
https://www.pombase.org/reference/PMID:7681363

I haven't made any changes to any pages.

Hi @manulera
This is a low priority issue but if you have any ideas for how to improve how any of the pages look, it would be great to get your opinion.   Val and I have been looking at these pages for years so I don't think we are good at judging what's good and what's bad any more.  So please comment if you have any suggestions or ideas, or make new issues.  Thanks!

authors: ValWood kimrutherford


text:
[Feature] SurrealDB driver

A SurrealDB driver in addition to PostgreSQL and SQLite would be great!

Thanks for opening. Could you share a bit more about why you want this? What problem would SurrealDB solve, and for what use cases would you prefer it over Postgres?

Definitely!
Convenience in SurrealDB based projects
Probably the most obvious and immediate benefit would be that for projects already using SurrealDB (full disclosure, like the one I'm working on), having Ponder directly write to SurrealDB in a Ponder namespace would make things a lot simpler rather than having to query from the Ponder API -- as I'm sure you're aware, going Ponder --> SQL DB --> GQL API --> Backend API --> SurrealDB  is a lot less efficient than Ponder --> SurrealDB --> Backend API
More data relation models
SurrealDB is a multi-model database, meaning that on top of schemafull and schemaless relational data, it also allows for document data and most importantly for Ponder, graph related data, meaning that Ponder could eventually have a way to lay out indexed data on a graph-style database within Surreal on top of a more traditional relational layout
Live updates
SurrealDB makes it really easy to listen for live updates to the database without setting up complex systems like in Postgres
Indexing & searching
SurrealDB provides a really great out-of-the-box solution for indexing a database for full-text semantic search, meaning that a real time search engine could be built incredibly easily off of a single Ponder instance connected to SurrealDB rather than having to injest and reindex that data onto a search engine like ElasticSearch or MeiliSearch.
Inspection
SurrealDB has a very nice in-house tool called Surrealist, which makes viewing database models and data really simple and easy in both development and production. I've used visual tools for SQL-esque databases before and at least imo, they aren't as intuitive
REST API
Even though Ponder already provides a GraphQL API, ingesting it into Surreal would also allow for developers to build out a custom REST API directly within SurrealDB without having to write their own backend if they prefer REST over GraphQL.
Running
In both development and production, SurrealDB is far simpler to configure and run compared to Postgres -- not as simple as SQLite, but far closer to the capabilities of Postgres (which is pretty hard to get running, especially locally on a dev machine).

Thanks for the thorough response. We don't have any immediate plans to add more database drivers, but I'll move this to discussion and revisit down the road.

repo: ponder-sh/ponder


text:
Add heartbeat to telemetry service; improve telemetry flush handling

To avoid bugs and complications of getting the path for the script to run in detached process, I write it to tmp and call it there. Also can bump up heartbeat rate from 60sec to like 10min, depending on what you expect average runtime to be (forever?).
The bug preventing the flush from running was that the path was sometimes incorrect depending on how ponder was being called, and it was failing silently.

Two more things:

Should add "Fixes https://github.com/ponder-sh/ponder/issues/560" to the PR comment to get that sweet issue link
Should add a changeset, see guide here https://github.com/ponder-sh/ponder/issues/560

source: gharchive/pull-request


text:
Release 0.58.0

Target release is the end of November 2023.

Release is underway

repo: ponylang/ponyc


text:
Implement RFC #5

This PR implements  https://github.com/ponylang/rfcs/blob/master/text/0005-file-naming-guidelines.md
It should also be noted that an Int type has been created as type Int is (Signed | Unsigned) to match the Float type.

Looks great, thanks for taking care of this!
However, I wonder if Integer might be better than Int for the new type...  I don't feel super strongly about it so I will see what others from @ponylang/core @ponylang/committer say.

@jemc Integer exists as a trait, just like FloatingPoint is a trait and Float is a type declaration.

@Theodus - you're right - makes sense to me.  I'm going to merge this - I don't think it has any breaking changes.

I think there are some problems here
test.pony was renamed to main.pony, I'm not sure that is what we would want here.

@SeanTAllen what would you suggest?

test.pony is in my mind better. it captures "what this is" far better than "main.pony".
i think this is one case where the naming convention falls apart a bit. in any other case I think it works, however, not in the case of tests.

I think this is a good conversation for the sync call.

I understand the general idea of why it was done, but I think that test.pony is a better name because it is the tests and that better represents the intent.

test.pony is in my mind better. it captures "what this is" far better than "main.pony".

i think this is one case where the naming convention falls apart a bit. in any other case I think it works, however, not in the case of tests.

I'd argue that this is not a failure of the naming convention, but yet another case where applying rules consistently highlights a tension with the fact that tests in the standard library are compiled in the same package as the code they test. For another example of this, see #588.  For another example of this, see the builtin_test package, where including the tests in the same package builtin was seen as not only impractical, but impossible. For another example, see the fact that every single Pony application that uses a standard library package also has a dependency on ponytest, even applications that are not tests.
That is, the complaint here that foo/main.pony isn't a good conceptual description of the file that contains tests is the direct result of the fact that the Main of a given package is not the conceptual "main" executable actor for that package.  Most packages (those that are reusable libraries) should not really have a "main" conceptual actor, because a library is generally not executable, but those that do have a conceptual "main" (like top-level applications, or libraries that come with an accompanying command line tool) need their Main reserved for the actual application - forcing yet another special case where the tests must be in a subpackage.
All these tensions are not incidental, but the result of a real consistency problem in our test conventions.
See #625 for more discussion.

We strongly disagree. I think it's a good conversation for sync call.

authors: SeanTAllen Theodus jemc


text:
Ｗindows対応

WSL2があれば不要。

repo: pooza/tomato-shrieker


text:
How to use blacklist with space character?

If you're trying to remove all occurrences of 'hello world' using a sanitizor, how can you do it with the blacklist sanitizor (because 'hello world' has a space in it)?

Define a regex

authors: rightaway thetutlage

repo: poppinss/indicative


text:
Remove hypothesis code for generating random graphs.

This turned out to be more of a maintenance burden than a useful tool
for testing. Hypothesis is amazing, and it would be nice to have this,
but I'll leave it for someone else to resurrect if they're really
motivated.
Closes #360.

:100:

I agree it'd be nice, but coming up with a sensible model for random demographies is probably quite a tricky thing.

authors: grahamgower jeromekelleher

repo: popsim-consortium/demes-python

license: ISC


text:
Add support to change endpoint type

I would like to change old endpoints from "Docker" type to "Agent" type. I've prepared everything on the server (agent runs there), but I have no idea how to change the endpoint type in portainer.

Exactly the same problem.
Additional question.
I tried to add the existing Docker endpoint as Agent endpoint.
Now I have 2 identical endpoints : primary (Docker type) and docker-node1 (agent one).
If I remove primary endpoint.
a) do it do the job?
b) is it safe? I have some containers running, I hope they will not be stopped...

Just to continue...
I tried to remove primary endpoint.

the good thing... Globally it works. Containers continue to work.
the bad thing... at the same time, finally I think it's not a good idea.
The containers keep to work, but for example the stacks that were deployed on removed (primary) endpoint now are marked as "Limited" and we could not remove or retrieve them.
This is probably in link with #3023 issue.

I had also some strange networks trouble, not sure it was linked to remove endpoint operation, but there are some chances as it started pretty well after removing.
This problem was solved by completely restart docker-node1 and all containers.
So the bottom line, I think remove duplicated endpoints could be a work-around, but it's better to avoid it.

Currently changing an existing endpoint type is not possible, and as the user above pointed out stacks become 'limited' as the stack files in the Portainer DB reference the old endpoint. I have labelled this as a feature request accordingly.
@paulz1 Deleting an endpoint in Portainer won't effect docker resources such as containers as these are handled by docker, Portainer just manipulates them using docker commands :)

authors: hason itsconquest paulz1

repo: portainer/portainer

license: Zlib


text:
chore(deps): remove grunt-html2js and grunt-karma

fix #4764 CE-249

/azp run

authors: chiptus jfadelhaye


text:
Timeout when installing Fedora CoreOS on iPXE

Bug
Environment

Platform: bare-metal
OS: fedora-coreos
Release: 1.17.4
Terraform:

Terraform v0.12.24

provider.ct v0.4.0
provider.local v1.4.0
provider.matchbox v0.3.0
provider.null v2.1.2
provider.template v2.1.2
provider.tls v2.1.1

Problem
iPXE receives a timeout while attempting to download the Fedora CoreOS image.
Interestingly, my web browser has no problem downloading the same URL.
I compiled iPXE from source, and the only hint I have that it isn't working is that it hangs while (seemingly) reporting the certificate authority. It doesn't actually start downloading (like a percentage counter). Flatcar over HTTPS does not have the same issue.
Desired Behavior
iPXE Fedora CoreOS
Steps to Reproduce

Compile iPXE from latest source, enabling HTTPS, install on router, confirm booting from said iPXE image
terraform apply as per the docs for Fedora CoreOS on bare metal
Boot any machine, see it attempt to download correctly, and time out.

Reports for iPXE fetch problems can go to the upstream OS vendors.
At various points I've had issues with CoreOS Container Linux, Flatcar Linux, and Fedora CoreOS. They've all turned out to be either ephemeral upstream hosting issues or related to iPXE firmware -  test with debug enabled, check if its their root OSCP cert expiring again, etc.

I provisioned a Fedora CoreOS stable 31.20200310.3.0 cluster in the course of upgrading all clusters to Kubernetes v1.18.0. So I think the issue will turn out to be in your iPXE setup and I'll close this out.
If you can test out iPXE with debug still have issues, probably best to note the iPXE sha, compilation options, and Fedora CoreOS version to report to https://github.com/coreos/fedora-coreos-tracker

authors: barakmich dghubble

repo: poseidon/typhoon


text:
🛑 main is down

In f1ec834, main ($MAIN_API_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: main is back up in 009824a.

repo: positive-infinity/api-status


text:
How many specific localhosts instead of DNS servers?

Diving deeper into the server object and profiling how many are using localhost.

This has been answered - https://github.com/postman-open-technologies/knowledge-base/blob/main/R/oas_summary.md#how-often-do-apis-use-localhost-vs-domain-based-servers


text:
Update labs-overview.md

Modified the intro to remove a few redundancies.

@skatikia check this once? Minor changes. I'm unable to add reviewers.

repo: postmanlabs/labs-docs


text:
Extract name and path from definePage()

Currently, name and path defined through definePage() are not added to the types like it happens with the route block but it should be possible since they are extracted through the AST

any estimated time to fix on this? trying definePage today, but got error because it does not added to typed-router.d.ts

This turns out to be really tricky: got the extraction working but I still have a few bugs to fix. I recommend you to stick to the <route> block for the moment. Note that definePage only accepts literals values as so:
definePage({ name: 'must be literal' })

I need to ensure that having imports doesn't have a huge impact on performance

This turns out to be really tricky: got the extraction working but I still have a few bugs to fix. I recommend you to stick to the <route> block for the moment. Note that definePage only accepts literals values as so:
definePage({ name: 'must be literal' })

I need to ensure that having imports doesn't have a huge impact on performance

all right! thanks :D

any update on this? @posva

I haven't been able to work on this feature again yet

I haven't been able to work on this feature again yet

all right, i hope this been fixed soon since it's really better to wrote everything using definePage() function rather than route block

repo: posva/unplugin-vue-router


text:
Scheduler issue when coroutine waiting on list of triggers

There is a bug in the scheduler dealing with unpriming triggers correctly when a coroutine in waiting on a list of triggers, and one of those triggers fires, but other coroutine(s) are waiting on a non-fired trigger in the list.
The scenario is as follows:
Two coroutines exist, with coro_A waiting on a list of triggers [RisingEdge(sig1), RisingEdge(sig2)], and coro_B waiting on one of the triggers in coco_A's list RisingEdge(sig1).
If one of the other triggers in coro_A's list fires, RisingEdge(sig2), the scheduler does not unprime RisingEdge(sig1) because coro_B is waiting on it. This is correct behavior.
The bug is that the scheduler also does not update the list of coroutines that are waiting on the trigger RisingEdge(sig1). The scheduler should remove coro_A from this list, as it is no longer waiting on it.
This will cause coro_A to be called when RisingEdge(sig1) does happen in the future.
@cocotb.coroutine
def coro_A(dut):
    while True:
        yield [RisingEdge(dut.sig1), RisingEdge(dut.sig2)]

@cocotb.coroutine
def coro_B(dut):
    while True:
        yield RisingEdge(sig1)

@cocotb.test
def test1(dut):
    cocotb.fork(coro_A(dut))
    cocotb.fork(coro_B(dut))

    yield Timer(1)
    dut.sig2.value = '1'

This may be related to issue #839
I have a fix for this and will create a Pull Request.

@garmin-mjames: I don't really understand your test, so I can't tell if this is a duplicate of #839. Can you test this on master and see if it can be closed?

The test is designed for two coroutines to yield on the same trigger, but with one of the two coroutines also waiting on an additional trigger. The list of pending coroutines for the additional trigger was not being cleaned up correctly.
It is a duplicate of #839 because it is caused by the same issue in the scheduler.
Now that #870 is merged I'll test it.

I tested this on master and #870 fixed this.

authors: eric-wieser garmin-mjames

repo: potentialventures/cocotb


text:
WIP: parallel execution without Makefile - demo

A very unpolished demo for #696 that removes the need for Makefiles (for discussion).
Libraries are build using setuptools Extension.
Allow basic discovery by pytest (better integration TBD).
Better portability.
The use case would be to run pytest -n 16 which would discover all the test and run them in parallel/distributed using pytest-xdist.
Usage is to add somewhere in the test module (no Makefile needed):
def test_run():
    Run(sources=['../hdl/dff.v'], toplevel='dff')

and run pytest
Comments, suggestions help highly appreciated.

Work will continue as an external extension for now: https://github.com/themperek/cocotb-test


text:
Update kubernetes/master/golang/master build

This is an automated PR via build-bot

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

Needs approval from an approver in each of these files:

OWNERS

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


text:
Update kubernetes/master/golang/master build

This is an automated PR via build-bot

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

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


text:
Update 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:
can not findNearestPoly bug

the dungeon.obj
res= move.query.findNearestPoly(new float[]{1, 10, 19}, new float[]{1.0f, 1.0f, 1.0f},new QueryFilter());
System.out.println(res.getNearestRef());
get 0?

i am wrong


text:
Run Audio Tests in Linux against a dummy audio driver

I'm not so sure if we can do this in the current state of how we use SDL in osu!framework, but #4430 is failing when running audio tests. The only way to probably get these to run is to run them against a dummy driver which SDL already provides. SDL has a "dummy" driver which is enough to make a program using the library "think" there's a valid audio driver.

This isn't related to SDL - it's BASS not being able to initialise the no sound device for some reason.

repo: ppy/osu-framework


text:
Global plugins

It seems plugins are globally registered, so I'm wondering how I could get a filepond instance with image preview and one without working in the same script.

You can set allowImagePreview to false on the instance you don't want to have previews.

Ah, that works, thanks.

authors: LostKobrakai rikschennink

repo: pqina/filepond


text:
Question: building without a Developer ID?

According to its readme, Karabiner-VirtualHIDDevice can be built without a code signature from apple. Will you ever publish a version of Karabiner-DriverKit-VirtualHIDDevice that can be built without a signature?

No, we cannot do it.
Xcode requires Developer ID to build driver extension.

Does that mean that Karabiner-VirtualHIDDevice also can't be built without a Developer ID?

You can build Karabiner-VirtualHIDDevice without Developer ID.
But it uses kext and you cannot use kext since Big Sur (11.0).

license: Unlicense


text:
iohyve cpiso cannot handle file names with spaces

I ran this command:
sudo iohyve cpiso /zdata/ISOs/Windows\ 7\ SP1\ Ultimate\ x64\ en-us\ Nov2014\ Pre-Activated@Only\ By\ THE\ RAIN-=TEAM\ OS=-\{HKRG\}/Windows\ 7\ SP1\ Ultimate\ x64\ en-us\ Nov2014.iso

and got this error
[: /zdata/ISOs/Windows: unexpected operator
Copying Windows
7
SP1
Ultimate
x64
en-us
Nov2014
Pre-Activated@Only
By
THE
RAIN-=TEAM
Windows
7
SP1
Ultimate
x64
en-us
Nov2014.iso from /zdata/ISOs/Windows 7 SP1 Ultimate x64 en-us Nov2014 Pre-Activated@Only By THE RAIN-=TEAM OS=-{HKRG}/Windows 7 SP1 Ultimate x64 en-us Nov2014.iso...
too many arguments
usage:
        create [-pu] [-o property=value] ... <filesystem>
        create [-ps] [-b blocksize] [-o property=value] ... -V <size> <volume>

For the property list, run: zfs set|get

For the delegated permission list, run: zfs allow|unallow
cp: Nov2014.iso is not a directory

I guess that that's what I get for trying to figure out how to get everything set up properly with a pirated version of Windows before doing it for real with a properly licensed one. ;)
In all seriousness, it's clear that iohyve cpiso is not escaping the file name properly. At minimum, it doesn't handle spaces correctly, and I'd guess that characters that the shell treats specially would have problems as well. It wouldn't surprise me if other iohyve commands which take file names  (e.g. iohyve cpfw) have similar problems, but I haven't tested them.

This is a known issue in the way iohyve handles just about everything.
I really don't want to say something like "it's UNIX you shouldn't have file names with spaces anyway" but that's totally bad.
There is work to clean this kind of stuff up. Until now, I suggest something like mv "My Backdoored Copy Of Windows Uber Ultimate Cracked by +++====CYB3R_TEAM-420===+++.ISO" windows7.iso then use iohyve cpiso windows7.iso ;)

Closing this issue as it is now added to our roadmap.


text:
[Do Not Merge] NetStandard Upgrade: Update NuSpec & Raw NuGets

Should now install in just about every application

@onovotny can you validate my changes here.

Also, do you want dependency groups for Xamarin tvOS and watchOS?

I think this library itself is still actually a PCL which is really odd, I am going to change it over to .NET Standard 1.1 and then add tvos/watchos

Alright @onovotny I think this should be good now, I have created a new .NET Standard 1.1 project and added in the references needed.

I think that once Bitrise upgrades to the latest stable it will build up.

@jamesmontemagno if you're going that approach, you can just use the pack targets too -- dotnet pack. All of the info in the nuspec have equivalent properties in the csproj. The only reason to really split out the dependency groups as you have them would be to potentially minimize pain on people using packages.config with older project types.

I have been working on a new version of this that builds using .NET Core on Bitrise.
I'm making good progress! Let's switch to there.
https://github.com/praeclarum/sqlite-net/pull/561

authors: jamesmontemagno onovotny praeclarum

repo: praeclarum/sqlite-net


text:
Python 3 support

Currently an issue arises from requests_testadapter:
BytesIO.__init__(self, stream)
TypeError: 'str' does not support the buffer interface

We have worked around this in seed-stage-based-messaging tests by encoding it:
adapter = RecordingAdapter(json.dumps(response).encode('utf-8'))

This would also require an updated importing of url_parse:
try:
    from urllib.parse import urlparse
except ImportError:
    from urlparse import urlparse

@gsvr Which bits of the go-http-api code does this refer to?

@hodgestar go_http/tests/test_metrics.py, for example https://github.com/praekelt/go-http-api/blob/develop/go_http/tests/test_metrics.py#L95

Could you open a pull request to add Python 3 to Travis and then we can review and sort out issues there?

@hodgestar done as requested

We will also need to update the fakes module from the go-contacts-api package.

Noting that http://python-future.org/compatible_idioms.html is a good palce to start for this work (and depending on the future module is probably sensible).

authors: gsvr hodgestar imsickofmaps

repo: praekelt/go-http-api


text:
Add use spin to uneearth problems and solutions

@dcmoore
Heres the addition of "Use SPIN To Unearth Problems and Solutions". Hopefully its in the right direction :)
I wasn't entirely sure what to put for nuance, introspective questions, or how to improve. So I left them blank for now.
Let me know what else I can do to help with adding the practice!

@miketabb33 I made some changes to the copy to make it more beginner friendly. Any thoughts?

@dcmoore I think this looks good and ready to merge. Thoughts?

@dcmoore poke

repo: pragmint/open-practices


text:
Can it be used to pre-train a BART model?

Hi~
I want to find a method to pretrain a BART model with my own corpus. The pretrain method can add noise to the input and reconstruct the input, just as BART pre-training model did. But I couldn't find a specific way to pre-train the BART model, but came across this mBART pre-training method. Can it be used to pre-train the BART model?
Looking forward to your reply.

mBART and BART use the same technique. Except that the former uses monoolingual corpora for multiple languages and Bart  uses monoolingual corpora for a single language. So yes, you can do this using my toolkit. All you do is specify the corpus for a single language.

repo: prajdabre/yanmtt


text:
Do Calendar and Periodic Notes plugins need to be disabled?

Do the Calendar and Periodic Notes plugins need to be disabled for this plugin to work?
Or can they coexist?

This plugin is a completely separate entity from the built-in daily notes plugin, on top of which I believe the Calendar and Periodic Notes plugins operate. They don't need to be disabled per se, but they will only operate on the core plugin and not this plugin, so they won't be of any use. I have updated the Readme to better reflect that.
Co-existing with the core plugin will require perpetual synchronisation between it's files and the single file provided by this plugin, which I don't think would be ideal. Instead, I might look into implementing some kind of one time import/export to switch between the two systems.

authors: jcesguerram pranavmangal


text:
[GSSoC'23] Change the UI of repository web page

Describe the bug
In the repository web page link of the image or GIF of the header is not working.
Expected behavior
there should be a proper image or GIF.
Screenshots (optional)

in the screen upper most part there is the header
Additional context (optional )
i have already solve this problem and after solving it will look some thing like this

Please assign this issue to me under GSSoC'23

@pranjay-poddar I have made the PR. Please review it.

Please assign this issue to me under GSSoC'23. This is my first open source contribution for  I want to make some changes in the UI

@karananu This issue is closed.

repo: pranjay-poddar/Dev-Geeks


text:
Weight Conversion program in python

Describe the project you want to add with tech stack
Tkinter is a standard GUI library that comes with Python. In this program, we'll provide options for converting weight from one unit to another (e.g., kilograms to pounds, pounds to kilograms).
Expected behavior

Screenshots (optional)

Additional context (optional )

@MohitGupta121 @TusharKesarwani @pranjay-poddar can you please assign it to me


text:
Open-box animation added

Title and Issue number

I have added the project .Can it be merged now?
Close #4795

Checklist:

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

@MohitGupta121 ,@TusharKesarwani Please review my PR.


text:
Max list at 460

For some reason, running list while querying against a parent ID (listing all files in that directory) even with a -m for max return value only returns 460 file entries... anything lower than 460 works properly, but nothing seems to work past it.

This is apparently a pretty common thing in a lot of gdrive programs. I wrote a python script as a workaround to pull all the file ids in a directory and pass that to this program; the issue appears to come from not fully polling all the pages of results when calling list()

Was fixed some time ago.

authors: batteryshark prasmussen

repo: prasmussen/gdrive


text:
🛑 ChatGPT Beyond 2021 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: ChatGPT Beyond 2021 is back up in 95a7347 after 8 minutes.

repo: prateekralhan/status


text:
🛑 ChatGPT + DALL-E is down

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

HTTP code: 0
Response time: 0 ms

Resolved: ChatGPT + DALL-E is back up in b0f0a29 after 7 minutes.


text:
🛑 ChatGPT Beyond 2021 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: ChatGPT Beyond 2021 is back up in de3a445 after 11 minutes.


text:
Additionally accept fullnames in the lists given to inbox.mark_read() and inbox.mark_unread()

I've come across a usecase where I want to mark messages as read, but I only have the fullname and not the praw.models.Message instance. Unfortunately inbox.mark_read() takes a lost of Message/Comments instances but doesn't allow fullnames to be in the list. I don't see a reason why that shouldn't work.
Describe the solution you'd like
In addition to Comment/Message instances, allow fullnames (str) in the lists given to inbox.mark_read() and inbox.mark_unread() functions
like this:
diff -Naur praw/models/inbox.py ../praw/models/inbox.py
--- praw/models/inbox.py	2021-02-24 03:49:04.000000000 +0100
+++ ../praw/models/inbox.py	2021-06-01 09:41:43.736733862 +0200
@@ -81,12 +81,12 @@
         )

     def mark_read(
-        self, items: List[Union["praw.models.Comment", "praw.models.Message"]]
+        self, items: List[Union["praw.models.Comment", "praw.models.Message", "str"]]
     ):
-        """Mark Comments or Messages as read.
+        """Mark Comments or Messages (given as object or fullname) as read.

         :param items: A list containing instances of :class:`.Comment` and/or
-            :class:`.Message` to be be marked as read relative to the authorized user's
+            :class:`.Message` and/or :class:`str` to be be marked as read relative to the authorized user's
             inbox.

         Requests are batched at 25 items (reddit limit).
@@ -109,7 +109,7 @@

         """
         while items:
-            data = {"id": ",".join(x.fullname for x in items[:25])}
+            data = {"id": ",".join(x if isinstance(x, str) else x.fullname for x in items[:25])}
             self._reddit.post(API_PATH["read_message"], data=data)
             items = items[25:]

Describe alternatives you've considered
I've considered pulling the Message objects from inbox, but that would introduce delay and network traffic for no good reason.
Additional context
none

Have you considered stripping the prefix off:

ids = [fullname[3:] for fullname in full names]

I may be wrong, but I think that API call wants fullnames. Why would I want to strip the prefixes?

I was meaning to use the stripped fullnames to construct Message objects like this:
reddit.inbox.mark_read([reddit.inbox.message(fullname[3:]) for fullname in fullnames])

I don't understand what exactly you're trying to do. Do you want to .mark_read() based on usernames(str)? Because you could just:
for commentID in reddit.inbox.unread():
    thisComment = comment(id=comment)
    if thisComment.author.name() == myAuthor:
         reddit.inbox.mark_read(thisComment)

authors: Demmenie LilSpazJoekp molecular

repo: praw-dev/praw


text:
Possibly flesh out prerender fetch patch with ok, status, etc.

Just ran into this on www, we check response.ok but the patched fetch here only provides { text, json} in the response.
There are of course workarounds, and we probably can't / wouldn't want to mock out everything, but it might be worth considering the following:

adding some static ok: true, status: 200 etc. props to the return object
calling readFile ahead of time, properly returning 404's, etc.

Tbf, only really going to be an issue seen in existing projects.

FYI: These days there is the Response constructor, so we should be able to do new Response(content, init) which has all the properties. So instead of stubbing a response we could construct a real one ourselves.

Yup, that's what I was thinking with the second option if that wasn't clear.

authors: marvinhagemeister rschristian

repo: preactjs/preset-vite


text:
Fix rendering bug; Declare support for TCFv2 for Sharethrough bidder

Hi, Prebid team, please note that this PR combines an update and a bug fix.
Update

Sharethrough bid adapter supports TCFv2, this change updates Sharethrough documentation

Bug fix

This PR includes a bug fix of another bidder's markdown file (selectmediavideo.md). Incorrect markdown syntax is causing incorrect rendering, and as a result, the Sharethrough section in the Bidders section of the website is inaccessible.
See the current broken behavior deployed live: https://prebid.org/dev-docs/bidders.html#sharethrough (note the anchor tag #sharethrough is not working yet other anchor tags work; then notice the syntax error addressed in commit https://github.com/sharethrough/prebid.github.io/commit/ecd703ff11487dbe5a67c53feefe957e1ddcc126 of this PR).

Please let me know if you would like me to separate out the commits -- the broken documentation on prebid.org was flagged to us by a publisher.

I'm not sure this is going to fix the formatting -- will address it in a separate PR if it doesn't.

Did fix it.

Thanks for the quick review @bretg !

authors: bretg madma


text:
removed cookieSyncDelay from config

Removed cookieSyncDelay from config since we have more configuration options now with the userSync object.
Documents https://github.com/prebid/Prebid.js/issues/3061.

thanks for this @thewizarodofoz -- but since we can't merge it until 2.0 -- API change, I think we want to add the deprecation now and remove it later.

Yes I thought a deprecation notice is more suitable, but then I saw that cookieSyncDelay is actually not being used anywhere in the master branch (except for in the config object itself).
The user sync module is using the new syncDelay param. So unless I am missing something, I think leaving cookieSyncDelay is actually misleading.

@bretg FYI: https://github.com/prebid/Prebid.js/pull/3142#issuecomment-427854451

Ok.

authors: bretg thewizarodofoz


text:
Add resizable button and scroll richtext

Title
Add resizable button and scroll Richtext and textarea fields
Type of Change

[x] New feature
[ ] Bug fix
[ ] Documentation update
[ ] Example update
[ ] Refactoring
[ ] Hotfix
[ ] Security patch
[ ] UI/UX improvement

Issue
#348
Screenshots

Impact
No Impact

Thanks for this!
Looks good, except for one little thing. Even though the resizing feature show up, it doesn't seem to work when I try to expand the size of the text box.

authors: cregourd ogoldberg

repo: premieroctet/next-admin


text:
Pass blocked request resource list from outside. so the resources need to be blocked is configuarable

With my pull request to phantom: https://github.com/sgentle/phantomjs-node/pull/229
Passing a variable to onResourceRequested can be done now.
See this note in phantom:

onResourceRequested takes a function that executes in the scope of phantom which has access to request.abort(), request.changeUrl(url), and request.setHeader(key,value). The second argument is the callback which can execute in the scope of your code, with access to just the requestData. This function can apply extra arguments which can be passed into the first function e.g.

page.onResourceRequested(
function(requestData, request, arg1, arg2) { request.abort(); },
function(requestData) { console.log(requestData.url) },
arg1, arg2
);

So I create a json file which include all resources need to be blocked, then pass it into `onResourceRequest`.

Thanks! This would be nice to get rid of the duplication of that array.
How is requestData.aborted shared between the two?

:+1:

You did a trick on the fn function to make request accessable. The request is special and cannot be touched out side onResourceRequest, but others are just normal objects. I test on them, they do share between x and cb.

Looks good. Thanks @msk86 !
I also made it so you can pass in blockedResources in the server.js file like:
var prerender = require('prerender');

var server = prerender({
    blockedResources: [ 'google.com' ]
});

server.start();

repo: prerender/prerender


text:
🛑 Beta is down

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

HTTP code: 400
Response time: 633 ms

Resolved: Beta is back up in 9eb75b7.

repo: presquelabs/upptime


text:
🛑 Beta is down

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

HTTP code: 400
Response time: 599 ms

Resolved: Beta is back up in 38f5244.


text:
JWT role claim

Hello,
I couldn't find any reference in the docs nor the issues about using the JWT claims.
Can I use the role claim from an JWT token as the pg role for the session ? (à la postgrest)
Thanks

this library looks awesome! I really want to use prest, however, I'm in the same boat as @tbmale .... just looking for some docs on how to use this.
Are there any examples out there for integrating a JWT system?
Here is how I've done it and would like to:
issuing and storing tokens/sessions
The way I typically do it, is I've actually implemented a table with my own tokens, and a function for validating and issuing tokens to users. The table is private, and never exposed to public. The function will check against a users email/password to issue a token.
authenticating requests
Then when client sends requests, token is pulled off to be authenticated, before every request, and then sets some settings using set_config, which changes role and gives some meta-data that my policies use for RLS:
select set_config('role', 'app_user', true);
select set_config('jwt.claims.role_id', '681f005b-f897-467f-86de-8f4e59bfb12f', true);

write SQL using this information in procedures and policies
Now in using RLS and policies, you can use this information:
CREATE POLICY can_do_something ON some_table
  FOR UPDATE
  USING (
    current_setting('jwt.claims.role_id')::uuid = sender_id
  );

@avelino @joelmdesouza

We are working on the implementation of standard authentication, can be followed here https://github.com/prest/prest/issues/276

cc @tiaguinho

implementation of authentication endpoint completed, we will be grateful for your feedback
view more: https://docs.postgres.rest/query-statements/#auth-auth---post

authors: avelino pyramation tbmale

repo: prest/prest


text:
Selecting only partition column causes table scan in parquet-hive

select min(datehour) from foo; will cause a full table scan on a table foo partitioned by datehour. Instead the query should only scan the hive table metadata.

@billonahill I think you meant to open this issue in facebook/presto rather than prestodb/presto-admin :)

You should this issue in facebook/presto

Ugh. Thanks! :)

authors: billonahill cawallin rschlussel

repo: prestodb/presto-admin


text:
Separate Alluxio related documentation

Since we are adding caching docs as a separate document . the Alluxio docs should sit side by side with it and not be in the main Hive connector docs. We plan to pull that long document apart even more in the future but this is necessary now since we have built in caching support.
Related to https://github.com/prestosql/presto/pull/4227

Can you rebase?

Rebased .. somehow that pulled in the contributing guideline changes.. should I reissue PR from a new branch?

I think GitHub is just confused.

authors: electrum mosabua

repo: prestosql/presto


text:
is there a way to override all configuration?

Hi
I was integrating eslint-config-prettier into a project, and ran into this issue:
Here is our current .eslintrc config (simpified)
module.exports = {
...
extends: [
    ...some rules
    'prettier'
    ],

rules: {
    ...overrideEslintRules,
    }
}

if, to say, we're overriding an indent rule in overrideEslintRules to [2, 4, { SwitchCase: 1 }], that would mean eslint-config-prettier 's disabling of indent does not work anymore
The question is, is there any way to still override all of it with eslint-config-prettier ? Cause in rules we have so much rules that are often overlap with prettier, and disabling them manually renders eslint-config-prettier unnecessary.
Thanks.

Hi!
Removing stuff from rules that is unnecessary or conflicts with Prettier is the way to go. Personally I’ve done exactly that in many projects, so that I ended up not needing eslint-config-prettier at all. I just run the CLI helper tool sometimes to check that I don’t have any conflicts.

makes sense, thanks

authors: lydell xblurx

repo: prettier/eslint-config-prettier


text:
chore: bump dependencies - yaml v2

close #279

Are you still planning on doing this?

authors: JounQin nzakas

repo: prettier/yaml-unist-parser


text:
chore: updated the publishing documentation

an update to the publishing documentation.  Once I figure out a more precise reason for using the  npm run prepare script i will add it in.

Codecov Report

Merging #464 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #464   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          43     43
  Lines         398    398
=====================================
  Hits          398    398

Continue to review full report at Codecov.

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

LGTM

Resolves #451

Ping/ @broox9, any chance we can collaborate more to move this publish guide forward?

authors: BeniCheni bertya broox9 codecov-io

repo: pricelinelabs/design-system


text:
Fix typo in create_triples.py

Signed-off-by: Ikko Eltociear Ashimine eltociear@gmail.com
Pull Request
What does this PR do?
unqiue -> unique

Fixed as part of PR #439

authors: eltociear franzmpub

repo: primeqa/primeqa


text:
[Tests] Ensure that axe calls are made on open state of the component

Hi! I noticed that in the component snapshot tests, axe scans are made on the default state of the component.
For example, in ActionMenu, the scan axe call is made like so:
        test('axe @aat', async ({page}) => {
          await visit(page, {
            id: 'components-actionmenu-examples--groups-and-descriptions',
            globals: {
              colorScheme: theme,
            },
          })
          await expect(page).toHaveNoViolations({
            rules: {
              'aria-required-children': {
                enabled: false,
              },
            },
          })
        })

Axe is being called on the closed state of the menu - Example snapshot, which does not provide as much value because we're essentially running an axe scan on a button, rather than on the menu markup that is only visible open activating the toggle.
Instead (or in addition to what we currently have), I believe we would want the axe scans to happen on the open state of the menu. I observed this in other "popover" type components like Dialog as well.
We should update these tests to have the axe scan run on the open state.
Stretch: It would be great if we could have some kind of automated check that ensures that we have axe scan coverage on the open state of components.

@khiga8 sounds great! Wanted to ask you, for the stretch goal is there anything that you all have found helpful for this in other projects like PVC or in github/github?

That's a great question @joshblack! I am not sure the same setup would translate to Primer React, but happy to share what I've observed about setups in other projects.
I've noticed that e2e tests in Primer React are reserved for auto-generated visual regression tests and axe scans tests. It sounds like this is because (as you've noted before), it is possible to write very robust React unit tests that test component behaviors. Since you can test most interactions (e.g. keyboard behavior) with unit tests, it isn't really worth testing these in e2e tests.
If I recall correctly, it's not possible to test JS behaviors with Rails unit tests. In PVC, in order to test (any kind of JS) interactions, e2e browser tests need to be written. Browser tests in PVC are written (manually, not auto-generated) with the intent of testing interactions because unit tests are limited. The tests have been set up in a way where whenever interactions are made (e.g. a click call), an axe scan is automatically called. This expands coverage of axe to different states. It doesn't seem like this same setup would make sense in Primer React though and would require a significant change.
If we want to work with the existing setup, I wonder if a starting point could be to modify the script/generate-e2e-tests.js script. I wonder if if we could have this script cross check the component markup (somehow?), and if it is role="dialog", role="combobox", role="menu" (or any markup that "pops over"), the auto-generated tests would include the following:
Pseudo:
      test('axe @aat' on open state, async ({page}) => {
        await visit(page, {
          id: '${story.id}',
          globals: {
            colorScheme: theme
          }
        })
        // Remove this after addressing TODO
        expect(false).toBeTruthy();
        // TODO: We want the axe scan to run on the open state of the component. Please replace this with a call to open the component!
        await expect(page).toHaveNoViolations()
      })

Basically, try to call attention to the fact that there should be test coverage on the open state by noting it in the test and having it auto-fail.
Curious what you think of this approach to start with, or if you have any other ideas!

repo: primer/react


text:
fix flask dependency issues

Reference Issues/PRs

Fixes #196
What does this implement/fix? Explain your changes.

Fixes dependency for sweb.eval.x86_64.pallets__flask-4045:latest

Ok, I reproduced this and the change works well!
Thanks!

authors: carlosejimenez wistuba

repo: princeton-nlp/SWE-bench


text:
Examples for providing a more complicated database model > application model mapping

In my opinion, the current suggestions for mapping the database models to the application models only allows for the most simplistic mapping use cases.
However, in the event that you need to also map to child/referenced entities, there is no documentation around this.
I was able to put together a solution in typescript that may be helpful for others looking to implement something similar.
Fundamentally, I expose a singleton that provides the mapping to and from the prisma model and supports full nesting with some good code reuse.
import { company, user } from "@prisma/client";
import { UserEntity } from "../../entities/user/user.entity";
import { CompanyEntity } from "../../entities/company/company.entity";
import { convertStatusEnum } from "../../enums/status.enum";
import { Mapper } from "../entity-mapper.interface";
import { UserMapper } from "../user/user.mapper";

const CompanyMapper: Mapper<CompanyEntity, company> = {
    fromPrisma(dbo: company & {
        users?: user[],
        parent?: company,
        created_by?: user,
        updated_by?: user,
    }): CompanyEntity {
        if (!dbo) return null;
        const entity = new CompanyEntity();
        entity.id = dbo.id;
        entity.version = dbo.version;

        if (dbo.parent) entity.parent = CompanyMapper.fromPrisma(dbo.parent);
        else if (dbo.parentId) entity.parent = new CompanyEntity(dbo.parentId);

        entity.status = convertStatusEnum(dbo.status);
        entity.name = dbo.name;
        entity.website = dbo.website;
        entity.about = dbo.about;

        entity.created_at = dbo.created_at;
        if  (dbo.created_by) entity.created_by = UserMapper.fromPrisma(dbo.created_by);
        else if (dbo.createdById) entity.created_by = new UserEntity(dbo.createdById);
        entity.updated_at = dbo.updated_at;
        if (dbo.updated_by) entity.updated_by = UserMapper.fromPrisma(dbo.updated_by);
        else if (dbo.updatedById) entity.updated_by = new UserEntity(dbo.updatedById);

        if (dbo.users) entity.users = dbo.users.map(UserMapper.fromPrisma);

        return entity;
    },

   // simplified as I don't want child dependencies to be automatically inserted by prisma
    toPrisma(entity: CompanyEntity): company {
        if (!entity) return null;

        return {
          id: entity.id,
          version: entity.version,
          parentId: entity.parent?.id,
          status: entity.status,
          name: entity.name,
          about: entity.about,
          website: entity.website,
          created_at: entity.created_at,
          createdById: entity.created_by?.id,
          updated_at: entity.updated_at,
          updatedById: entity.updated_by?.id
        }
    }
}
export { CompanyMapper };

Then my repository looks something like this:
import { Injectable } from "@nestjs/common";
import { Prisma, PrismaClient } from "@prisma/client";
import { UserEntity } from "../../entities/user/user.entity";
import { CompanyEntity } from "../../entities/company/company.entity";
import { PrismaService } from "../prisma.service";
import { CompanyMapper } from "./company.mapper";

@Injectable()
export class CompanyRepository {
    private db: Prisma.companyDelegate<Prisma.PrismaClientOptions>;
    private db_history: Prisma.company_historyDelegate<Prisma.PrismaClientOptions>;
    constructor(prisma: PrismaService | PrismaClient) {
        this.db = prisma.company;
        this.db_history = prisma.company_history;
    }

    async create(entity: CompanyEntity, by?: UserEntity) {
        entity.version = 0;
        entity.created_at = entity.updated_at = new Date();
        entity.created_by = entity.updated_by = by;

        const dbo = await this.db.create({
            data: CompanyMapper.toPrisma(entity)
        });

        await this.db_history.create({
            data: dbo
        });

        return CompanyMapper.fromPrisma(dbo);
    }

    async update(entity: CompanyEntity, by?: UserEntity) {
        entity.version++;
        entity.updated_at = new Date();
        entity.updated_by = by;
        const dbo = await this.db.update({
            where: {
                id: entity.id,
            },
            data: CompanyMapper.toPrisma(entity)
        });
        await this.db_history.create({
            data: dbo
        });

        return CompanyMapper.fromPrisma(dbo);
    }

    async findById(id: number) {
        const dbo = await this.db.findFirst({
            where: { id: id }
        });

        return CompanyMapper.fromPrisma(dbo);
    }

    async findByIdAndVersion(id: number, version: number) {
        const dbo = await this.db_history.findFirst({
            where: { id: id, version: version }
        });

        return CompanyMapper.fromPrisma(dbo);
    }

    async findOne(args: Prisma.companyFindFirstArgs) {
        const dbo = await this.db.findFirst(args);

        return CompanyMapper.fromPrisma(dbo);
    }

    async findOneHistory(args: Prisma.company_historyFindFirstArgs) {
        const dbo = await this.db_history.findFirst(args);

        return CompanyMapper.fromPrisma(dbo);
    }

    async find(args: Prisma.companyFindManyArgs) {
        const dbos = await this.db.findMany(args);

        return dbos.map(CompanyMapper.fromPrisma);
    }

    async findHistory(args: Prisma.company_historyFindManyArgs) {
        const dbos = await this.db_history.findMany(args);

        return dbos.map(CompanyMapper.fromPrisma);
    }

    /**
     * WARNING: This performs a HARD delete which may cause a foreign key constraint problem
     * @param id
     */
    async delete(id: number) {
        await this.db.delete({
            where: {
                id: id
            }
        });

        await this.db_history.deleteMany({
            where: {
                id: id
            }
        });
    }
}

Nice, had a client request Prisma but after looking into it- it does indeed have trivial ORM restrictions you wouldn't think would be there.
There are some libraries from other developers in the communities but they're not being maintained.
I like this approach- separation of concerns and no massive Schema file.

repo: prisma/docs


text:
Implement a warning system for data model validations

Now we only warn through the language server. We should have a system in place, that would output warnings in a similar way as we do with errors. Yellow instead of red highlight, and not stopping the execution when having only warnings.
Open questions:

When to warn, always when evaluating a data model
Do we warn about things such as deprecated features in the cli additionally
Is it ok to be noisy?
And if we're not noisy, can we reach the users with deprecation warnings

Warnings emitted from engines are now supported :)

This should have been closed by https://github.com/prisma/prisma-engines/pull/2468 if I understand correctly. This should definitely be used more, however.

authors: Druue pimeys

repo: prisma/language-tools


text:
Stop exporting a token named prisma

Problem
My codebase contains a singleton PrismaClient named prisma. We import and use this object to access all the data, as you'd expect.
Somewhere along the way @prisma/client also started exporting a variable named prisma. As far as I can tell, it doesn't provide any utility.
However, autocomplete-import systems that like of VS Code now default to importing the useless token from @prisma/client rather than the prisma singleton. This is regularly annoying, and I can't imagine we're the only one's dealing with it.
Suggested solution
Don't export a token named prisma from @prisma/client.
Alternatives
Alternately, we could rename our singleton to db or prismaClient or something without a namespace conflict, they just don't feel as elegant.

We're having the same problem while following the Turborepo + Prisma guide, but also trying to export a shared prisma client, named prisma.
In other words, we can't do:
export * from '@prisma/client';

in our packages/database/index.ts.
If we also want to do
export const prisma = new PrismaClient()

authors: defrex javiercr

repo: prisma/prisma


text:
Improve error messages for missing system dependencies

Stems from https://github.com/prisma/prisma/issues/18832#issuecomment-1620822480
The linked issue seems to be due to the fact that the Linux distribution on Namecheap doesn't have libc or musl installed.  However the error message is confusing and should let the user know about that. This is an enhacement and as such is addressed separately.
cc @aqrln as he might have input on the issue

The error in the linked issue is not due to glibc not being installed but due to it being too old. We require at least glibc 2.17 (the oldest supported by Rust, we can't possibly compile for an older version), and the error implies that whatever version is installed is at most 2.13 or older (since a symbol introduced in 2.14 wasn't found).
We can certainly improve this error message.

Hi @janpio, I'd love to take on this issue.

authors: aqrln goisleandro miguelff


text:
Add time zone conversion for timestamps

Problem
Currently, it's not possible to convert a timestamp to another time zone like in this PostgreSQL example:
select example_date at time zone 'Europe/Brussels' from example_table
Suggested solution
I was thinking of something like the example below but this requires a select option so there might be a better workaround.
const posts = await prisma.post.findMany({
  where: {
    author: { email: 'bob@prisma.io' },
    title: { startsWith: 'Hello' },
  },
  select: {
     createdAt: { timeZone: 'Europe/Brussels' }
  }
})

I agree with her. We need to use like this. I'm having trouble now

any update?

any updates?

This would be great. Im currently converting all dates by mapping all the records after the query.

Anything ?

any updates? this would be great, fr

hopeless ..

Any updates ?
The entire world (I mean people others than UTC) is begging you :)

any update?

This needs to be added, it would make my life 100x simpler.

So sad that this issue has been around for so long.

We all need this update :(

Any updates?

Any updates?

Hello any updates ?

authors: DarkestSeconds LoriKarikari LucasMSCaetano MaxiSanchez600 NathanPo TheRealSmeddy ekufrin henriquezolini isaacsaless mardev60 palatkalog pclokcer rod2ik soutowhs xphys yogasw


text:
Error formatting for connection limit error

Problem
Originally suggested by @janpio. There are two lines before the actual error from the database
Invalid \`prisma.queryRaw()\` invocation:

Error in connector: Error querying the database: db error: FATAL: sorry, too many clients already

https://github.com/prisma/prisma/blob/5c1039d08545c3bbf41eaad6189a63fc0d2ed518/src/packages/client/src/__tests__/integration/errors/connection-limit/__snapshots__/test.ts.snap
Is that expected?
Suggested solution
A single blank line should be enough.
Additional context
This might break some snapshot tests etc out there and in that sense, this is a breaking change.

Seems to be generally accepted or have been fixed along the way.

authors: divyenduz janpio


text:
Consider renaming connect/disconnect to link/unlink

Problem
Right now the terms connect and disconnect are overloaded in the Prisma client
Connect

prisma.$connect: connect to a database
nested connect: connect a relation

Disconnect

prisma.$disconnect: disconnect to a database
nested disconnect: disconnect a relation

Suggested solution

Deprecate nested connect and disconnect, replace them with link and unlink.
const user = await prisma.profile.create({
  data: {
    bio: 'Hello World',
    user: {
-     connect: { email: 'alice@prisma.io' },
+     link: { email: 'alice@prisma.io' },
    },
  },
})

There would be a period of deprecation and the codemod would be updated to help with the transition.
Alternatives
Do nothing. Decide that it's not that confusing. I'd love to hear what you think 🙂

I agree we should change this. The Go client already uses Link and Unlink and I think it's a lot clearer at what it does.

authors: matthewmueller steebchen


text:
Prisma.upsert() should support the value of null in where condition.

Bug description
Prisma supports creating the nullable value for the table, but not support the null value in where condition of upsert() method.
How to reproduce
I wrote a simple reproducible example - https://github.com/xuqingkuang/prisma-null-foreignkey
Please follow the README.
Expected behavior
upsert() accepts a null input as an option value.
Environment & setup

OS: CentOS 8
Database: MySQL and Sqlite
Node.js version: v14.15.4
Prisma version:

❯ npx prisma -v
Environment variables loaded from .env
prisma               : 2.20.1
@prisma/client       : 2.20.1
Current platform     : rhel-openssl-1.1.x
Query Engine         : query-engine 60ba6551f29b17d7d6ce479e5733c70d9c00860e (at node_modules/@prisma/engines/query-engine-rhel-openssl-1.1.x)
Migration Engine     : migration-engine-cli 60ba6551f29b17d7d6ce479e5733c70d9c00860e (at node_modules/@prisma/engines/migration-engine-rhel-openssl-1.1.x)
Introspection Engine : introspection-core 60ba6551f29b17d7d6ce479e5733c70d9c00860e (at node_modules/@prisma/engines/introspection-engine-rhel-openssl-1.1.x)
Format Binary        : prisma-fmt 60ba6551f29b17d7d6ce479e5733c70d9c00860e (at node_modules/@prisma/engines/prisma-fmt-rhel-openssl-1.1.x)
Default Engines Hash : 60ba6551f29b17d7d6ce479e5733c70d9c00860e
Studio               : 0.365.0

Hey @xuqingkuang thanks for the detailed reproduction. This is working as designed, but we may want to revisit the design. It's a bit of a larger topic unfortunately.
For now, you may need to use $queryRaw or a 2-3 queries in your application for now. We'll have a closer look though.

Hey @xuqingkuang thanks for the detailed reproduction. This is working as designed, but we may want to revisit the design. It's a bit of a larger topic unfortunately.
For now, you may need to use $queryRaw or a 2-3 queries in your application for now. We'll have a closer look though.

Sure, I use a 0 instead of null and dropped the foreign key for a workaround, but still looking forward to the issue will be fixed.

That is entirely by design. Prisma has 2 core query concepts: Operate on a list of records or operate on a single record. Upsert falls into the single record category with the semantics being: "Find a single record and if that record exists, update it with the provided data, else create it with the provided data". We categorize it strictly like that because a narrow definition allows us to implement queries without considering a larger class of edge cases that introduce uncertain behavior into Prisma.
So, to implement upsert we need to pin exactly one record in the database. IDs and uniques are the to do that in Prisma, any other (non-unique) condition would potentially result in a list of records and it is not clear which record to update (or update all, which breaks the semantics of the operation). Sidenote: "The first one" is also not acceptable because without an explicit ordering, there's no guarantee that the first one is always the first one, among other edge cases.
Now the question is why we allow @@unique on nullable fields - that's an SQL tradeoff we made so far. Your unique index in SQL is (in most cases) not really "unique" as we'd intuitively understand it, because you can totally have two identical titles with NULL as the authorId in the row (because in SQL, NULL != NULL, that's why). However, the construct is so common  that we had to include it, but as the interface requires you to find exactly one, we must require the input field and can't accept null values, which is why there's a deviation.
We may consider loosening restrictions in the future, but we will only do so after careful consideration when we are absolutely sure we understand all the use cases and problems it introduces.

@ahathaway are you able to workaround this issue using the method @xuqingkuang described?

Can reproduce with provided repo.
Using our internal dev version 4.4.0-dev.25 the error changes for ========== Prisma.upsert with null error: ==========
Full logs:
> prisma-null-foreignkey@1.0.0 start /Users/j42/Repros/prisma-null-foreignkey
> ts-node ./src/index.ts

========== One books should exist  ==========
[
  {
    id: 1,
    title: 'The Old Man and the Sea',
    authorId: null,
    author: null
  }
]
========== Two books should exist  ==========
[
  {
    id: 1,
    title: 'The Old Man and the Sea',
    authorId: null,
    author: null
  },
  { id: 2, title: 'A Farewell to Arms', authorId: null, author: null }
]
========== Prisma.upsert with null error: ==========
PrismaClientKnownRequestError

Invalid `prismaClient.book.upsert()` invocation in
/Users/j42/Repros/prisma-null-foreignkey/src/index.ts:53:31

  50 {
  51   const title = "For Whom the Bell Tolls";
  52   try {
→ 53     await prismaClient.book.upsert(
Missing a required value at `Mutation.upsertOneBook.where.BookWhereUniqueInput.title_authorId.BookTitleAuthorIdCompoundUniqueInput.authorId`
Error:
Invalid `prismaClient.book.upsert()` invocation in
/Users/j42/Repros/prisma-null-foreignkey/src/index.ts:53:31

  50 {
  51   const title = "For Whom the Bell Tolls";
  52   try {
→ 53     await prismaClient.book.upsert(
Missing a required value at `Mutation.upsertOneBook.where.BookWhereUniqueInput.title_authorId.BookTitleAuthorIdCompoundUniqueInput.authorId`
    at RequestHandler.handleRequestError (/Users/j42/Repros/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:30850:13)
    at RequestHandler.request (/Users/j42/Repros/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:30833:12)
    at PrismaClient._request (/Users/j42/Repros/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:31805:16)
========== Prisma.upsert with non-exists foreign got foreign key constraint error ==========
PrismaClientKnownRequestError

Invalid `prismaClient.book.upsert()` invocation in
/Users/j42/Repros/prisma-null-foreignkey/src/index.ts:80:31

  77 {
  78   try {
  79     const title = "For Whom the Bell Tolls";
→ 80     await prismaClient.book.upsert(
Foreign key constraint failed on the field: `foreign key`
Error:
Invalid `prismaClient.book.upsert()` invocation in
/Users/j42/Repros/prisma-null-foreignkey/src/index.ts:80:31

  77 {
  78   try {
  79     const title = "For Whom the Bell Tolls";
→ 80     await prismaClient.book.upsert(
Foreign key constraint failed on the field: `foreign key`
    at RequestHandler.handleRequestError (/Users/j42/Repros/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:30850:13)
    at RequestHandler.request (/Users/j42/Repros/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:30833:12)
    at PrismaClient._request (/Users/j42/Repros/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:31805:16)

Before
========== Prisma.upsert with null error: ==========
PrismaClientValidationError

Invalid `prisma.book.upsert()` invocation:

{
  where: {
    title_authorId: {
      title: 'For Whom the Bell Tolls',
      authorId: null
                ~~~~
    }
  },
  update: {},
  create: {
    title: 'For Whom the Bell Tolls',
    authorId: null
  }
}

Argument authorId: Got invalid value null on prisma.upsertOneBook. Provided null, expected Int.

Error:
Invalid `prisma.book.upsert()` invocation:

{
  where: {
    title_authorId: {
      title: 'For Whom the Bell Tolls',
      authorId: null
                ~~~~
    }
  },
  update: {},
  create: {
    title: 'For Whom the Bell Tolls',
    authorId: null
  }
}

Argument authorId: Got invalid value null on prisma.upsertOneBook. Provided null, expected Int.

    at Document.validate (/home/xqkuang/github/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:32548:19)
    at NewPrismaClient._executeRequest (/home/xqkuang/github/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:34481:17)
    at /home/xqkuang/github/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:34416:52
    at AsyncResource.runInAsyncScope (async_hooks.js:197:9)
    at NewPrismaClient._request (/home/xqkuang/github/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:34416:25)
    at Object.then (/home/xqkuang/github/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:34536:39)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

After
========== Prisma.upsert with null error: ==========
PrismaClientKnownRequestError

Invalid `prismaClient.book.upsert()` invocation in
/Users/j42/Repros/prisma-null-foreignkey/src/index.ts:53:31

  50 {
  51   const title = "For Whom the Bell Tolls";
  52   try {
→ 53     await prismaClient.book.upsert(
Missing a required value at `Mutation.upsertOneBook.where.BookWhereUniqueInput.title_authorId.BookTitleAuthorIdCompoundUniqueInput.authorId`
Error:
Invalid `prismaClient.book.upsert()` invocation in
/Users/j42/Repros/prisma-null-foreignkey/src/index.ts:53:31

  50 {
  51   const title = "For Whom the Bell Tolls";
  52   try {
→ 53     await prismaClient.book.upsert(
Missing a required value at `Mutation.upsertOneBook.where.BookWhereUniqueInput.title_authorId.BookTitleAuthorIdCompoundUniqueInput.authorId`
    at RequestHandler.handleRequestError (/Users/j42/Repros/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:30850:13)
    at RequestHandler.request (/Users/j42/Repros/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:30833:12)
    at PrismaClient._request (/Users/j42/Repros/prisma-null-foreignkey/node_modules/@prisma/client/runtime/index.js:31805:16)

Type Error

I want to find records that don't have field.
In mongodb, there is $exists operator which is { field: { $exists: <boolean> } }.
but in prisma, { fieldName: { equals: null } } does not find records don't have field.
but { fieldName: { not: null } } condition find records have field.

Hello,
I have a use case with a unique constraint on 3 columns, one of which is nullable.
With the unique constraint, I still have only one record where the first two columns have specific values and the third one is null.
I'd like to be able to upsert into my table with:
where:
   {
       firstColumn_secondColumn_thirdColumn: {
           firstColumn: "value",
           secondColumn: "value",
           thirdColumn: null,
       }
   }

Is there a way to do this?
Thanks you.

@MarieMinasyan could you open a discussion here?
Because this issue is closed for a long time now.

authors: Jolg42 MarieMinasyan dpetrick heyask matthewmueller xuqingkuang


text:
tests: Rename uuid.test.ts to uuid-coercion.test.ts

Test gave false impression of testing uuid, but really tests something related to coercion from uuid to strong.

Looks like it's about making sure that what goes into String[] doesn't blow up during validation because of a uuid, so actually testing the runtime validation for String[]

Replaced by https://github.com/prisma/prisma/pull/17969


text:
temp: Only for engine search in 'this.config.datamodelPath'

Test what happens when we only search in this.config.datamodelPath

[ci test all]

Closing to clean up the open PRs list.


text:
Handle empty dates

Currently when adding a date field to a template and calling a document that doesnt yet have that date filled out the SDK raises an error because it cant convert an empty string or nil to a Date/Time.
It will still raise an error for malformed dates.
This fixes it by returning an empty text fragment (so calling .value) still works.
I thought about a few other approaches but this seems to have the lowest impact. Open to feedback

Btw looks like these same tests that failed are failing in master

What are your thoughts on this @faresd ?

@zjwhitehead thanks for your contribution and apologies for the massive delay in responding. While it works it feels slightly icky that we would return a Prismic::Fragments::Text instance when we are expecting a Prismic::Fragments::Date instance. I think it would be better if we adjust Prismic::Fragments::Date#to_html to simply do an early return with an empty string ('') if the value is nil.

authors: alistairholt zjwhitehead

repo: prismicio-community/ruby-kit


text:
Fix continuous integration

See here.

Node.js CI: Some jobs were not successful

It looks like the continuous integration is failing. We first need to solve #365, #375, #377. Then we can take on this issue.

Now that the Mocha tests in issue #375 have been merged in main. The continuous integration should now be working. See example #387 for a PR that passes checks.

authors: SebastianZimmeck sophieeng

repo: privacy-tech-lab/gpc-optmeowt


text:
Custom KV server

Will custom K/V servers that adhere to requirements and are verified be an option in the future? Or will there only be the official Google build and controlled implementation?

Hi @dynamix , could you elaborate a bit on your concerns behind the question? e.g., are you interested in for example more flexibility of the request processing logic, resource savings or better ownership of running servers in private data centers, less stringent visibility requirements of the server code, or something else?
We have just published another explainer of the K/V server user defined functions to talk about the feature to provide more customization in the processing logic. I wonder if that'd be of interest to you.

authors: dynamix peiwenhu

repo: privacysandbox/fledge-key-value-service


text:
nitvm: Basic blocks generation and SSA-algorithm

This PR introduces a SSA-algorithm implementation in the nitvm.
First, basic blocks are generated. A basic block is a sequence of instructions without a jump inside.
In this version, basic blocks are generated from the AST and so they contain only the first instruction and the last one.
Then, SSA-algorithm (Single-Static Assignment) is implemented. In SSA algorithm, variables are renamed to have only one assignment per variable.
Each time an assignment is made, a new version of a variable is made.
Some variables (phi-functions) have several assignment and so, several dependances.
The basic block generation and SSA are computed for each method in a lazy way in the nitvm.
The main objective of SSA is to give the dependances for each variable (this will be used in further PR).
This module also collect all object-mechanisms sites during the visit of methods.

Not familiar with the algo, but I can't see anything that particularly suprised me here, :shipit: !

Nice. I have to reread the datastructure and the algo throughout.

Reroll with all your remarks.
I made a module ssa in src/ and the vm use it. It should be reusable.

authors: R4PaSs jpages privat

repo: privat/nit


text:
code: cleanup some docunits

They where detected since #1332 is merged

Ignore failed tests. Jenkins is drunk!

+1

+1

authors: BlackMinou privat xymus


text:
Not JSON Serializable

Madam while running train.py from Deep-Learning/depth_estimation/ i received the following error
TypeError: 'Not JSON Serializable' while doing tf.keras.Model.save
after completing one epoch
On line:
basemodel.save(runPath + '/model.h5')
Using
Keras 2.4.4,
Tensorflow 1.13.1
Ubantu 18
Can you help?

I wanted to write the same but I found your issue first, Did you figure anything out?
If yes, can you pls share

女士，从 Deep-Learning/depth_estimation/ 运行 train.py 时，我收到以下错误 TypeError: 'Not JSON Serializable' while doing tf.keras.Model.save
完成一个纪元后
在线： basemodel.save(runPath + '/model.h5') 使用 Keras 2.4.4， Tensorflow 1.13.1 Ubantu 18
你能帮我吗？

Have you solved the error?

repo: priya-dwivedi/Deep-Learning


text:
Use the right core inside the debugger.

Currently much of the debugger code just uses core(0), but with #565 merged it should actually use the situationally correct core.
@Dirbaio @noppej @diondokter

debugger

The current debugger.rs and debug_adapter.rs code will use the user requested core (command line or DAP Client configuration option via launch.json). At the time of implementing this, there was no multi core, so we could not test this. I agree that after merging (or maybe just before) we should do some multi-core testing with the debugger. I have a dual-core STM32H7 board available so I am happy to own that.
In addition to selecting the correct core, we should look at implementing the CTI (cross trigger interface) settings that allow cross core debugging behaviours.  I suspect this is non-trivial, but it will be a valuable capability.

authors: Yatekii noppej

repo: probe-rs/probe-rs


text:
Add probe-rs config

Let's see what it takes to add some global probe-rs config :) Currently the only possibility is to configure probe aliasses, but in the future I imagine we can dump a lot of the environment variable options here as well.

Example config file:
default_device = "esp32c6"

[[devices]]
alias = "esp32c6"
selector = "303a:1001:40:4C:CA:4E:0B:08"

[[devices]]
alias = "esp32"
selector = "0403:6010"

Example probe-rs list output:
The following debug probes were found:
[0]: Dual RS232-HS -- 0403:6010: (FTDI) (alias: esp32)
[1]: ESP JTAG -- 303a:1001:40:4C:CA:4E:0B:08 (EspJtag) (alias: esp32c6)

The name device is a bit confusing for me here. If I have an external debugger like a J-Link, which is connected to a board, it feels a bit weird to describe it as a device.  Maybe it could be called alias, or favourite?
device also adds to the already somewhat unclear terms chip and target.

I don't know what would be best, I wouldn't even be against extending --probe to support named aliases. In code, alias would probably work well enough. In config, I'm not sure - we might end up adding quite a bit more to them - that would lead me toward preset, maybe?

Right now, the CLI takes --parameter-set foo, and the config uses default_parameter_set and parameter_sets. A bit verbose, but probably obvious enough?
There are use cases that make me want to add an extends = "parent_parameter_set" field and code to resolve those. The main use case would be to deduplicate hypothetical future "host/token" field pairs that would configure a remote connection, into a single parameter set.

authors: Tiwalun bugadani


text:
Idea - add check to /ProcessHacker/plugin.c::260 for prevent crash in to legacy OS then "FirewallMonitorPlugin.dll" is exists.

Idea - add check If OsVersion() <= 6.3 Then PH_STRINGREF_INIT(L"FirewallMonitorPlugin.dll") End to /ProcessHacker/plugin.c::260 for prevent crash in to legacy OS then "FirewallMonitorPlugin.dll" is exists.
Example:
    static PH_STRINGREF PhpPluginBlocklist[] =
    {
        PH_STRINGREF_INIT(L"CommonUtil.dll"),
        PH_STRINGREF_INIT(L"ExtraPlugins.dll"),
        PH_STRINGREF_INIT(L"NetAdapters.dll"),
        PH_STRINGREF_INIT(L"SbieSupport.dll"),
        PH_STRINGREF_INIT(L"HexPidPlugin.dll"),
       If OsVersion() <= 6.3 Then PH_STRINGREF_INIT(L"FirewallMonitorPlugin.dll") End
    };

Source - forum.ru-board.com users bug-report's in summary:
If some legacy system PH is carashed at startup if "FirewallMonitorPlugin.dll" is exists.

prevent crash in to legacy OS

The plugin supports Windows 7... The problem is you're using an older version of the plugin API and need to recompile the plugin for the latest nightly build.
You could always use the plugins with the stable build instead which would also solve the issue.

I try fix in to my toolkit and commited modifed FirewallMonitorPlugin source. And wait users callback (in to latest revision I added only VERSION_INFO in to .rc).

authors: VictorVG dmex

repo: processhacker/processhacker


text:
Fixed issue #5934 - Typo in web page

Fixed the required typo in Korean reference page
Fixes #5934
Changes: - Fixed a typo as requested
From - mode 상수: (선택 사항) 호를 그리는 방식들로, CHORD, PIEC, OPEN 중 선택 가능
To - mode 상수: (선택 사항) 호를 그리는 방식들로, CHORD, PIE, OPEN 중 선택 가능

Thank you @shivanshsharma13 for working on it.  I am inviting the Korean Translation stewards to review this pull request @yinhwa, @almchung, @jhongover9000, @sssueing, @GeryGeryGery, @sosunnyproject. Thanks!

Thank you @shivanshsharma13 for fixing this! Just merged in :)

Thank you @shivanshsharma13, @almchung  and @yinhwa
Just added @shivanshsharma13  to the p5.js contributors list. 🎉

authors: Qianqianye shivanshsharma13 yinhwa


text:
Users upload files

This commit implements the /invoke endpoint to output JSON and graph images from input data

I rebased commits from other branches to align and it made a lot of duplicates, I think I need to cleanup before opening the PR... any help is appreciated. The relevant commit is https://github.com/production-optimiser/production-optimiser/pull/16/commits/b8740d486c3c38e7cb00edae3fa2d082641ce3fa

Resolved conflict but it seems to have messed up the formatting

lgmt, refactoring is definitely needed in the next spring or 2 max

maybe wait with merge for other PRs to go into develop first, since you had a lot of changes and we dont have tests to not break something

@Theanko1412 I'm opening another branch, wait for that PR to merge it into develop


text:
Integrate Enigma Data Marketplace

Since Enigma Data Marketplace is now out, we can integrate new datasets into our app.

Closing issue to focus on free datasets

repo: produvia/kryptos


text:
Bootcamp

Add Cygwin

merging