question about the difference in using MACS for single-end or paired-end data

HI,tao:
I notice that multiple ChIP-seq data were single-end and reads length was 50bp, and use MACS for peak calling.
1、 I am confused that for paired-end ChIP-seq data, does MACS also suitable？ Furthermore, for single-end and paired-end ChIP-seq data, does the parameter have difference?
2、how long the reads length is perfect for MACS to perform peak calling?  50bp? 150bp? 250bp?
does the reads length can influence the result?

MACS2 will work with paired-end reads. Rather than specifying -f BAM, use -f BAMPE. In the case of paired-end reads, MACS2 will ignore the estimated fragment length (via strand cross correlation) and use the fragment length of each mated pair.

As far as I know, there is no preference in read length for peak calling per se. It is important to remember that your reads may only represent a small fraction of your actual DNA fragment. That is, a 50 bp read (from sequencing) does not mean you had DNA fragments that are 50 bp long in your sample. You only "read" 50 bp of a potentially larger DNA fragment. Peak calling is necessary because the position of your read (which represents the ends of your DNA fragments) to the reference genome does not necessarily reflect the position of the DNA fragment your read came from (which you actually want). Hope that makes sense.


[Event Request] Page 232 "Apply Customer Entries" - protected var

Please move the following variable OK to protected var in Page 232 "Apply Customer Entries"
    protected var
<...>
        //>><< New variable
        OK: Boolean;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 12340.


feat(output): Output as JSON for consumption with jq

Summary
I really want a CLI tool that outputs the whole JWT as JSON, yours seemed the easiest to modify, and it's also very easy to install ⭐ .
I thought considered adding a --json argument for this output format but wondered first if maybe you'd just prefer this be the default? Happy with either, just really want a tool that outputs JSON for the whole payload so I can extract values with jq. 👌
Preflight checklist

[x] Code formatted with rustfmt
[x] Relevant tests added
[x] Any new documentation added

Howdy @shousper thanks for the PR! I like this idea, but I think I'd like it to be behind a --json, -j flag, since the output now adds some helpful output for validity and any errors. If you could also add some tests that would be great. Thanks!

@mike-engel Done mate, cheers! :)

@shousper merged and released! If you have it installed with homebrew, you can update to the latest version now with brew update; brew upgrade mike-engel/jwt-cli/jwt-cli. If you're on linux or windows, binaries are available on the downloads page. Thanks again!


url, path & header being passed to called feature

Description
In Karate version 1.2.0.RC2, a bug seems to have been introduced where Karate now passes url and header (not sure if any other things as well) from a calling feature to a called feature. I've tested this with doing * def blah = call read('some.feature'), and also having an afterScenario block that does karate.call('some.feature'); both ways exhibit this bug.
The bug doesn't happen in v1.2.0.RC1 .
I can see in the Karate README that variables get passed through automatically (tbh, that feels a bit iffy to me, I thought programming languages generally completely separate called function's scope from their parent except for explicitly passed through inputs. It would be nice if we could choose to disable this feature when we didn't want it. But that's separate to this issue). But the Karate README also says https://github.com/karatelabs/karate/blob/3b4de72abf93431d8c9fc9301d806c6b931df004/README.md?plain=1#L3444
myproject.zip contains a demo of this bug (try setting the karate version to 1.2.0.RC1 & 1.2.0.RC2 to see the difference).
This bug means that e.g. if a scenario fails and an afterScenario block runs, that afterScenario block could end up making REST API calls with incorrect additional headers. Even doing * configure headers = null doesn't seem to protect against this bug, as headers set by doing * headers foo = "bar" don't seem to be able to unset in this or any other way AFAICT.

@ismail-s going to take time to get to this. maybe you can contribute ;)

We have experienced a similar issue just today where the "path" setting is accumulated/concatenated as well across feature boundaries.
I understand that path segments are expected to be concatenated; however, with 1.1.0, I was able to use different paths in a called feature, where in 1.1.0 I am not. The snippets below are not a valid "test", but show the changed (breaking) behaviour when looking at the accessed urls.
Sample:
main.feature:
`Feature: Main
Background:
* url "http://httpbin.org/get"
* path '/main/feature'
* call read("sub.feature")
Scenario: Caller
Given method get
`
sub.feature:
`
Feature: Sub
Background: Called
Given url "http://httpbin.org/get"
And path '/sub/feature'
Scenario:
When method get
`
Feel free to redirect me to a different issue.
Thanks :)

all: fixed. it would be great if you can validate latest develop solves this. so the only case where the http-builder can "retain state" is from the Background

1.3.0 released

I've never had an issue with the way Karate functioned in this respect, other than having to occassionally set headers to null in the few cases where I don't want them passed.
I don't think we should be too rigid in the application of certain rules, if the current functionality reduces code duplication.  We all use base classes right?
Not saying this change should be reverted, just that there is more than one way of viewing this, as with most coding solutions ;)

@adrian-85 noted. maybe a future direction is to give users an explicit http object, which you can pass into called features. but I resist trying to make karate look like a "normal" programming language. we have gotten feedback from so many non-programmers that they love karate for keeping things simple and just reducing cognitive load. programmers tend to forget the fact that tests need to live on for years, and be maintainable in the long run, by folks new to the team, domain, etc etc.
I'm fully aware that programmers once in while will drive-by and say that things "feel a bit iffy" and whatnot, but I'll only take them seriously if they come up with constructive suggestions or best-case contribute code.
personally, I like the fact that karate encourages you to keep your "main flow" in a single feature - by making it "harder" to do "re-use" like some of the examples in this thread. I think this has worked out well to offset the urge to "re-use" and apply "design patterns" by inexperienced folks (with the best of intentions no doubt). my favorite example is this: https://stackoverflow.com/a/54126724/143475

all I'm willing to acknowledge that url should be NOT reset ever, even when calling a feature. you can always force it by hard-coding. when I though about it, this was the original intent and it got lost in discussion and refactoring, my bad.
posted some thoughts here, do comment if you have a PoV: https://github.com/karatelabs/karate/issues/2202#issuecomment-1338690477


Dusktreader/free mouse scroll from manager

Only the latest commit should be considered as there is a different pull request for the group button commit.
This commit allows a mouse scroll event to pass over the ControllerMaster if there are no bound mouse scroll handlers. This was necessary for allowing other parts of my application to process the mouse wheel events even when the pyglet-gui components were active

Hi @dusktreader. Thank you for your PRs. They have been merged into the master.

Only the latest commit should be considered as there is a different pull request for the group button commit.

FYI, If you don't want this to happen, you should branch from the master for each new PR. This way each commit is associated with a different PR. In any case, I accepted both.


Disable fast jumping of items when issues disabled

Feature Description
Disable fast jumping of items when issues disabled .
If the project has Issues turned off, the # tag will link to a page that does not exist.

Screenshots
No response

Maybe it should display the original repository's issue? from #25364

Maybe it should display the original repository's issue? from #25364

Different git implementations may have different URL formats, and it may be possible to provide a template for users to fill in.

Could add a "Source Forge Type" to mirrors, that can be set to Gitea, Github, etc, which would then be mapped to a issue link.

Gitea and Github use user/repo/issues/id
GitLab uses user/repo/-/issues/id

Still, we shouldn't show such popups for repos that are not the current gitea instance because the popup relies on an API that can only work on the current instance.


Reduce reliance on PyPi for building formulas?

Hey!
This project is exactly what I need, but unfortunately I am setting up a private homebrew repo, and I plan on having the install managed though the GitPrivateStrategyThing, and I'm not publishing the packages at the moment. Having the resources list is super helpful, but I can't seem to generate the formula, even with a template, without publishing the package. Would it be possible to have a private-repo mode for those of us not trying to publish to a registry?
Thanks, looking forward to using this!

I'm just starting to investigate this plugin, I think I agree with comment above. Here is my use-case:

poetry managed python CLI application
deploy for macOS via homebrew
source code or binaries hosted on github releases page
not using pypi at all

I ended up just using PEX to build a binary, but would still be interested in some sort of cacheable install for Pypi dependencies.


Dataset link 404 error

It seems that your dataset has been removed or changed.

Yup, broken link.


Admin Delete User

Required admin function: ability to delete a user from the database when given an email

Added Admin.listUsers while I was at it.


Add OpenComputers API

Please add OpenComputers API.
It's another mod which adds computers to minecraft.
It's much better at perfomance (native runtime for Lua) and at some other features.
https://github.com/MightyPirates/OpenComputers

Translation: Please add support for the OpenComputers API and add all the functions that you made available for ComputerCraft. I recommend using the prefabricated Driver and ManagedEnvironment for easy implementation, and if you prefer the ComputerCraft way of registering methods, implement ManagedPeripheral on the ManagedEnvironment.
Furthermore, it's recommended to implement NamedBlock on the ManagedEnvironment and setting the priority so that the name of the environment with the highest priority gets chosen for display.

Hey @Vexatos, thanks for the more in-depth explanation.
After doing a bit of research, would it be alright if I just implemented SimpleComponent and ManagedPeripheral in classes I also implement IPeripheral in, and just have the OC methods call the CC ones?  I want to try and do this with as efficiently as I can.

@aidancbrady That would work as well and would not require registering any driver. But there is a drawback: OC will propagate its network across all connected Environments (SimpleComponent being one). Depending of the CPU tier in your Computer, there is a certain maximum amount of components that may be connected at once. Meaning if you, for instance, implement SimpleComponent on your cables, every single Cable and all machines connected to those cables and all cables connected to them etc. would become part of the network and ultimately crash the computer due to the exceeded component limit. By registering a driver, You force the player to place an Adapter block from OC adjacent to the block they want to interface with. This means that only the one block the player wants to interface with gets added to the network and thus the component count. This issue occured with PneumaticCraft until it got changed to the Driver-based system.

Note that you could still easily implement your methods in your TileEntity just like you want to and then just call tile.whateverthemethodiscalled() from the ManagedEnvironment.

In that case, what's the easiest way I can build on my already-existent CC integration by means of drivers?  For my machines, right now I implement IPeripheral in the base machine class and take care of several common methods there, and then take care of the more specific methods (getMethodNames()/callMethod()) in functionality base classes (TileEntityElectricMachine for Enrichment Chambers/etc, TileEntityAdvancedElectricMachine for Osmium Compressors/etc).  I currently just pass getInventoryName() as the peripheral name and everything works alright.  Is something like this possible with the driver system?

@aidancbrady it is. When implementing NamedBlock, you need to implement preferredName which you can just call tile.getInventoryName() in. For the methods in ManagedPeripheral, you could also just, as I said, directly relay them to their according methods in the TileEntity. See here and here for the stuff needed. Just mind that you won't need to use @Callback methods when you instead implement MagagedPeripheral.

So it doesn't matter if I don't return the highest-level class in getTileEntityClass(), then?

Exactly. You can just return a superclass there and it will call createEnvironment everytime it finds a TileEntity with that superclass.

Oh, perfect. Thanks so much.

Then you cast the TE to that superclass and give it to the environment, and your Environment now has the tile it can relay all the methods to.

By the way, OC does have a maven repo.

Oh, another note: Convention for OpenComputers has component names lowercase and separated by underscores, so for instance geolyzer or tape_drive. It would be nice if your blocks adopt this convention.

.toLowerCase().replace(" ", "_") should do it

toLowerCase(Locale.ENGLISH) :neckbeard:

Done!


Python: Django

Description :
What is Django?
Note :

Changes should be made inside the Python/ directory & Python branch.
Issue only for GWOC'21 contributors.
Issue will be assigned on a first come first serve basis, 1 Issue  ==  1 PR.
In the PR, keep this issue's title as your PR's title.

Must Follow : Contributing Guidelines & Code of Conduct before start Contributing.

@adityabisoi I would like to work with this issue.

/assign

I would like to work with this issue, please assign me this issue.
Batch - 1
Dhruti Gandhi

@queenish001 Is the mentor of this issue. Please reach out to her for your queries.

@adityabisoi I am working on this issue . I will do The PR till tomorrow . I am reading some useful stuffs

@adityabisoi I am working on this issue . I will do The PR till tomorrow . I am reading some useful stuffs

Okay
Just a reminder that the deadline is 5 days, so make sure you do it before that :)

Ok i will do in time @queenish001

@queenish001 give me some time please atleast 2-3 days

Please get it done by 3 Oct. You will be unassigned after that.

@adityabisoi is this issue open for audio ??
if yes then I would like to work in this as audio contribution. Kindly assign it to me
thank you !!

@adityabisoi
sir, can I contribute on this issue through video.
Thanks!


Move get record data logic to record stack association data

This moves the logic for getting associated record data into the
record stack AssociationData class. This simplifies tests and is
setup for factory configs not copying factories from associated
factory configs.
This moves the logic for getting associated record data, either
from a preset value, from the lookup or by building a new record,
into the AssociationData class. This has the benefit of
simplifying the RecordStack logic and isolating the conditionals
for getting record data. The RecordStack tests no longer need to
test each scenario at a high level and can simply assumed that
they will always get record data from the AssociationData. The
AssociationData can more easily test just the conditional logic
without having to worry about all of the other logic that record
stacks are doing.
This sets up factory configs not copying factories because
association datas are no longer built with a factory config. This
allows an association data to be built by the initial record stack
which has one factory config but not use that factory config when
building getting record data. For example, if a record stack is
built for a model that has deeply nested associations preset then
it will build RecordData for all of the preset values and
AssociationData for all of their associations. To not copy
factories the deeply nested associations (that weren't preset)
need to be built with a different factory config than the original
record stacks. By not building the association datas with a
factory config they no longer store the initial record stacks
factory even though it built them. They can instead be passed a
different factory config as they are walked and their associations
are built.
This also changes the AssociationData to build a RecordData
for its preset record. This is a small optimization because now the
association data will use the same record data instances as the
lookup so less record data instances will be built. Previously, the
lookup would build its own record data when it was added to the
lookup and the preset value would build a new record data when its
association was walked.
@kellyredding - Ready for review. This is part of an effort to optimize factory configs and record stacks more and simplify adding a feature to force walk associations.

@jcredding in commit msg "...not use that factory config when building getting record data."??

@jcredding yeah, it makes sense at a high level.  I like the overall goals 👎


Limit GC cutoff to disk_consistent_lsn

Why?
Limiting the cutoff to disk_consistent_lsn feels right intuitively, but I can't actually put my finger on what exactly would happen. What is the bad thing that can happen without this? Can you add a test case?

GC removes old version beyond GC horizon if new version exists.
But if this new version is beyond disk_consistent_lsn, i.e. is not  flushed to the disk, then we can loose it in case of abnormal pageserver termination.

GC removes old version beyond GC horizon if new version exists. But if this new version is beyond disk_consistent_lsn, i.e. is not flushed to the disk, then we can loose it in case of abnormal pageserver termination.

True. To prevent that, this check is in the wrong place. You should be checking that the new image layer that supersedes the layer being removed is not newer than disk_consistent_lsn. I.e. somewhere around here:

            // 3. Is there a later on-disk layer for this relation?
            if !l.is_dropped() && !layers.newer_image_layer_exists(l.get_seg_tag(), l.get_end_lsn())
            {
                ...

GC removes old version beyond GC horizon if new version exists. But if this new version is beyond disk_consistent_lsn, i.e. is not flushed to the disk, then we can loose it in case of abnormal pageserver termination.

True. To prevent that, this check is in the wrong place. You should be checking that the new image layer that supersedes the layer being removed is not newer than disk_consistent_lsn. I.e. somewhere around here:

            // 3. Is there a later on-disk layer for this relation?
            if !l.is_dropped() && !layers.newer_image_layer_exists(l.get_seg_tag(), l.get_end_lsn())
            {
                ...

Yeh, you are right.
I take in my mind my own GC implementation which deletes version of it has successor greater than GC cutoff. So in my case adjusting cutoff boundary with disk_consistent_lsn will work.
I committed the fix you have proposed.

Sorry, I still do not have idea how to create test without introducing special hooks in our code to model this situation.
But the problem seems to be obvious: checkpointer creates new image layers, them are inserted in layer map and so GC can remove previous layers. But disk_consistent_lsn is adjusted only at the end of checkpoint_internal.
If pageserver is crashed somewhere in the middle, then all this new layers will be renamed to *.old because them are beyond disk_consistent_lsn. But previous layers are also dropped by GC! So we missed pages...
I have made yet another attempt to fix it.

Sorry, I still do not have idea how to create test without introducing special hooks in our code to model this situation.

Yeah, I think this warrants adding some special hooks for testing. We haven't done that before, but I'm sure this isn't the only thing that will need it. I'd suggest creating a rust unit test for this, like the ones we have in repository.rs, by inserting something like this to the right place in checkpoint_internal:
        if cfg!(test) {
            if test_sleep_before_writing_metadata {
                std::thread::sleep(std::time::Duration::from_secs(10));
            }
        }

Sorry, I still do not have idea how to create test without introducing special hooks in our code to model this situation.

Yeah, I think this warrants adding some special hooks for testing. We haven't done that before, but I'm sure this isn't the only thing that will need it. I'd suggest creating a rust unit test for this, like the ones we have in repository.rs, by inserting something like this to the right place in checkpoint_internal:
        if cfg!(test) {
            if test_sleep_before_writing_metadata {
                std::thread::sleep(std::time::Duration::from_secs(10));
            }
        }

I wonder if we want to have more generic mechanism for simulation of failures (fault injection).
Not only before writing metadata and not only in  checkpoint_internal, but in arbitrary place in pageserver we can add something like this:
     inject_fault("before_writing_metadata");

and in some configuration file or somewhere else we can specify for example:

skip counter: how much times this call should be completed normally before simulating failure.
defer timeout: how much time should be passed before this hook is armed.

May be also we can somehow control this hooks in runtime: enabling/disabling them. Not sure what is the most convenient way for it: send signal to force reloading of config file? ...
We have almost no tests for checking recovery and consistency. And fault injection can be really useful for it. Writing unit tests which should "manually" initialize database, populate it with data, then trigger some actions (like checkpoint or GC) seems to be really dreary task.

Replaced with #1128


Fix Route 53 POST APIs

This should fix #765 .
The root cause is split into two parts;

In Route 53, no operation has "payload" parameter but some API actually
requires payload. In that case, the payload should include members whose
"location" parameter is missing.
XML element name of each list element was wrong

I confirmed that ChangeResourceRecordSets works in simple cases at least.

Thanks for the pull request.  This looks good at a quick skim.  I'm in between sessions at a conference right now, but I should be able to give this a serious review tonight or tomorrow.

I'm planning the next pull request to fix rest-xml APIs. I think it should use xml::EventWriter instead of format! and naive string concatenations.
https://github.com/eagletmt/rusoto/compare/fix-route53-post-api...eagletmt:xml-writer

Looks great, thanks!


Lagarto mishandles naked ampersands in attributes and text

Lagarto renders the following:
<tag src="http://example.com/example.jpg?child=1&parent=2">Peanut Butter & Jelly</tag>

as
<tag src="http://example.com/example.jpg?child=1?ent=2">Peanut Butter  Jelly</tag>

instead of
<tag src="http://example.com/example.jpg?child=1&parent=2">Peanut Butter & Jelly</tag>

Hey @fuwjax! Thank you for submitting this issue, I am totally ashamed, since src is quite common attribute...but somehow it gets overlooked.
Thanx for the fix, it's great - and the tests! Awesome!
Enjoy!


CldVideoPlayer styles are not applying to player component

"next-cloudinary": "^4.16.3",

import { CldVideoPlayer } from 'next-cloudinary';
Hello, why dont work styles fro player? I did't find answer in documentation

Hello @colbyfayock @demptd13, I'm also facing this issuing. What stylesheet do we import to make it function properly in the app router? Are there any other alternative solutions?

thanks for the bump, ive been a bit slow to solve this as ive been wanting ot solve this in a way that doesn't require external imports for styles, but it seems that i need to do that
now to do this, im going to need migrate to importing the npm package as there are complexities with downloading the CSS file and stashing it from the CDN which it currently write from, particularly making sure i get all the assets included in the CSS
i have a WIP for that here, which i'll work on wrapping up and get shipped

update: im going to just download the assets from the CDN for now in order to avoid a bigger change that i feel isn't quite ready to go out (the node module)
will be merging this in on Monday unless any issues come up: https://github.com/colbyfayock/next-cloudinary/pull/265
feedback welcome

@demptd13 @victorcodess with this release, you can now import the player stylesheet from the next-cloudinary package which should make the player work properly in the App Router
import 'next-cloudinary/dist/cld-video-player.css';

https://next.cloudinary.dev/cldvideoplayer/basic-usage
please let me know if you experience any issues!

Hi there, thank you for your hard work!  When importing the css file I'm getting an error
Module not found: Package path ./dist/cld-video-player.css is not exported from package

hey @coderdix24 what version are you using?

@coderdix24 I am experiencing the same thing.
@colbyfayock I am currently on "next-cloudinary": "^5.13.0",

@coderdix24 @sethburtonhall created a new issue: https://github.com/colbyfayock/next-cloudinary/issues/382
the issue was that I started creating a foundation for subpath imports and in doing so, missed adding the export for the CSS file
version 5.14.1
testing in my own fresh nextjs project seems to be working, but please let me know if you're noticing issues still

@coderdix24 @sethburtonhall created a new issue: #382
the issue was that I started creating a foundation for subpath imports and in doing so, missed adding the export for the CSS file
version 5.14.1
testing in my own fresh nextjs project seems to be working, but please let me know if you're noticing issues still

Thanks! ya i ended up making the change in my local copy I should have done a PR (still haven't after all these years, i think Im' nervous lol)
Appreciate you man

Everything is now working as expected. Thanks @colbyfayock!!

@coderdix24 @sethburtonhall created a new issue: #382
the issue was that I started creating a foundation for subpath imports and in doing so, missed adding the export for the CSS file
version 5.14.1
testing in my own fresh nextjs project seems to be working, but please let me know if you're noticing issues still

Everything is now working as expected. Thanks @colbyfayock!!


Exponential Search Using C#

🚀 Feature
Exponential search allows you to look at a sorted, unbounded list for a specific input value (the search "key"). The algorithm is divided into two stages. The first stage establishes a range in which the search key will be found if it were in the set. This selection is then subjected to a binary search in the second level.
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
Strengthen the search Algorithms in C#
Pitch
exponential search is an algorithm, for searching sorted, unbounded /infinite lists.

/assign


Improve handling of different Go versions, address compile failure in Go 1.10.4+

What does this pull request do?
@wadey Thanks for your work on #34. This pull request builds on that work and fixes #40.
Yesterday's release of Go 1.10.4 and Go 1.11 brought another related breakage (see  golang/go#24161). The specific compiler error is cannot use nil as type _Ctype_CFAllocatorRef. This requires passing C.CFAllocatorRef(0) instead of nil to a few functions that we use.
In this pull request, I also made an effort to minimize the amount of code we need to maintain across different Go versions, replacing wrap_deprecated.go with a few new (smaller) files for different Go versions.
The fix that worked for Go 1.10.4 or better didn't work as expected in Go 1.10.3 (see https://travis-ci.org/fsnotify/fsevents/jobs/420640270). Declaring the C.CFAllocatorRef(0) constant in the same file works in all 1.10.x versions, but when I extract that constant to a different file (go_1_10_after.go) it continues to work on Go 1.10.4+ but fails in 1.10.3.
To get 1.10.x versions prior to 1.10.4 working, I had to extract larger amounts of code into Go version specific files.  (all of GetDeviceUUID, a new MakeCFString and CopyCFString functions). It's truly odd, but it is working now.
Please take a look and let me know if it's okay for me to merge this.
Where should the reviewer start?
go_1_10_after.go
How should this be manually tested?
go test should suffice but certainly feel free to test in a tool that uses this if you have one.

So this is related to a change in Go 1.10.4 and Go 1.11 released yesterday.
Go 1.10.3 expects the previous behaviour. Possibly related to https://github.com/golang/go/issues/24161

Codecov Report

Merging #41 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #41   +/-   ##
=======================================
  Coverage   71.18%   71.18%
=======================================
  Files           3        3
  Lines         288      288
=======================================
  Hits          205      205
  Misses         61       61
  Partials       22       22

Impacted Files
Coverage Δ

wrap.go
70.07% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

C.CFAllocatorRef(0) works with Go 1.10.3 as well as 1.10.4+

@havoc-io Thanks for the tip. Indeed kCFAllocatorDefault would make more sense.

@havoc-io How does this look now? I've pushed 2 new commits based on your feedback.

Other than squashing some commits, are there any other changes needed before merging this?


oid-info: Drop Build Signer Digest requirement from MUST -> SHOULD

Summary

It was pointed out that CI providers may not be able to meet the Build Signer Digest requirement if they've been using server-assigned UUIDs to identify CI jobs rather than a user-verifiable digest.
Everyone seems to be in agreement that this is something CI providers SHOULD strive for so that users have a means of detecting misbehavior by the CI system, but this is not necessarily something we may want to gate acceptance on, since it would require work to implement and include.
As a result, dropping this down from MUST to SHOULD.
/cc @haydentherapper @kommendorkapten @feelepxyz @asraa @laurentsimon @aladh @marshall007 for any additional feedback
Release Note

Dropped Build Signer Digest OID requirement from MUST to SHOULD.
Documentation

✅

Build Signer Digest requirement if they've been using server-assigned UUIDs to identify CI runs rather than a user-verifiable digest

a run is different from a signer. The "Build Signer Digest", iiuc, identifier the builder, not the run. GHA also use some sort of UUID to identify runs (RUN_ID, RUN_ATTEMPT, etc). If the code requesting an OIDC token is in source code repo, then there is a digest associated with it.
I'm certainly mis-understanding something :-)

Build Signer Digest requirement if they've been using server-assigned UUIDs to identify CI runs rather than a user-verifiable digest
a run is different from a signer. The "Build Signer Digest", iiuc, identifies the builder, not the run. GHA also uses some sort of UUID to identify runs (RUN_ID, RUN_ATTEMPT, etc). If the code requesting an OIDC token is in source code repo, then there is a digest associated with it.
I'm certainly mis-understanding something :-)

You're right- this should be s/runs/jobs (I'll update this).
We anticipate this looking like:

Field
GitHub
GitLab

Build Signer URI
Job Workflow Ref
Job ID

Build Signer Digest
Job Workflow SHA
- (there is no current equivalent)

Build Config URI
Workflow Ref
Pipeline Ref

Build Config SHA
Workflow SHA
Pipeline SHA

Run Invocation URI
Run ID + Run Attempt
Pipeline ID

Just one more question, the Job ID is stable across multiple invocations, right? It's just that when a new job is created, it gets an UUID?

@wlynch for GitLab, what are you adding in the Subject Alternative Name URI? For GitHub Actions, Builder Signer URI and Subject Alternative Name URI are set to the same value. It's also expected this is what you want to write policies against when verifying trusted cert identities.
Can you write stable-ish policies against the Job ID or does it change between each job?

@wlynch for GitLab, what are you adding in the Subject Alternative Name URI? For GitHub Actions, Builder Signer URI and Subject Alternative Name URI are set to the same value. It's also expected this is what you want to write policies against when verifying trusted cert identities.
Can you write stable-ish policies against the Job ID or does it change between each job?

It's an opaque id that changes per job. There's no way today to reliably ID a job with a known name because of the flexibility in how jobs can be referenced/layered.
The plan for the SAN is to use https://gitlab.com/org/repo@ref, since as of now you can only have a single config per repo. AFAIK Builder Signer URI == SAN is not a strict requirement, though I think it makes sense to always use the most-specific stable identifier.

Can you also update the text of 1.9 then, since it includes Build Signer URI is also included in the Subject Alternative Name?

Done.

Just one more question, the Job ID is stable across multiple invocations, right? It's just that when a new job is created, it gets an UUID?

Yes. A job retry results in a new job with a new UID.

@haydentherapper, seems like this should be good to merge?


fix(telemetry): Add segment telemetry back to apps

copilot:all

Current dependencies on/for this PR:

main

PR #3592   👈

This comment was auto-generated by Graphite.


Remove excessive login requests.

Explicit login against mujin controller is not necessary since March 2016.

sure~~~


Add firebase authentication to login and signup forms

I'm going to create a firebase project with my own google account for dev rn and add the integration to react

I'm going to create a firebase project with my own google account for dev rn and add the integration to react


Fix setup script file creation

Problem
The setup script is currently incomplete/broken.
First, per #213, it does not generate the tursted-membership-validator-membership-change.json, without which the chain will not start.
Second, when we merged #283, we changed the type of an address from a public key to a public key hash (see this line in the diff). However, we did not change the setup script accordingly, and it still generates a public key in validators.json.
Solution
Generating the trusted-membership-validator-change.json is very simple - I just copied the code for validators.json and made a slight modification.
Since sidecli self returns both the public key and the key hash, we can simply modify the setup script to use the key hash in the right place.
Related

#213
#283

@d4hines I believe this can be closed if #288 is the one to be merged.


Refactor keybindings to support different modes

You should be able to have a seperate set of bindings for list view and message view.

Could be a bit cleaner, but this is done


Add includes to Config.

This PR implement a includes in transforms.
includes and transforms can be empty. Files list in includes are related to current yaml file.
This design is compatible.
Example:
# some_device.yaml
includes:
  - peripheral_a.yaml
transforms:
  - ...

# peripheral_a.yaml
transforms:
  - ...

This is helpful for managing multiple devices.


Resolution by file order instead of alphabetical order

Description
When Paket has no way to determine package weight, it defaults to alphabetical order. I would like it to resolve by the order the packages are written in the paket.dependencies file.
Is there a way to do this?
If not, would you welcome a PR that implements it (using a paket.dependencies flag)?
Repro steps
I have a paket.dependencies file that requires two packages Xylophone (not real) and Kafunk (real). The file does not lock a version on either.
nuget Xylophone
nuget Kafunk

The Kafunk library has versions 0.1.8 and 0.1.9.
The Xylophone library has two release (1.0 and 2.0) that depend on Kafunk like so:
v2 : nuget Kafunk =0.1.8
v1 : nuget Kafunk >=0.0.1
Expected behavior
What I would like is to resolve by file order. Xylophone is first in the file, so resolve to 2.0, then resolve Kafunk, which would give 0.1.8
Actual behavior
Paket will try to resolve dependencies in alphabetical order. It starts with Kafunk, gets the latest (0.1.9), then looks for the version of Xylophone that supports 0.1.9. This resolves to Xylophone version 1.0. Like so:
Kafunk (0.1.9)
Xylophone (1.0)

Known workarounds
Lock the version of Kafunk to the version used in the preferred Xylophone.
nuget Xylophone
nuget Kafunk =0.1.8

The problem with this as a solution is that users of Xylophone and Kafunk need to know that not only is there a resolution issue, but they need to manually update the Kafunk version to match the latest Xylophone version.

After thinking about it: I think I would accept a pr which changes this
behavior
Am 14.11.2017 23:37 schrieb "Troy Kershaw"<EMAIL_ADDRESS>
Description
When Paket has no way to determine package weight, it defaults to
alphabetical order. I would like it to resolve by the order the packages
are written in the paket.dependencies file.
Is there a way to do this?
If not, would you welcome a PR that implements it (using a
paket.dependencies flag)?
Repro steps
I have a paket.dependencies file that requires two packages Xylophone
(not real) and Kafunk (real). The file does not lock a version on either.
nuget Xylophone
nuget Kafunk
The Kafunk library has versions 0.1.8 and 0.1.9.
The Xylophone library has two release (1.0 and 2.0) that depend on Kafunk
like so:
v2 : nuget Kafunk =0.1.8
v1 : nuget Kafunk >=0.0.1
Expected behavior
What I would like is to resolve by file order. Xylophone is first in the
file, so resolve to 2.0, then resolve Kafunk, which would give 0.1.8
Actual behavior
Paket will try to resolve dependencies in alphabetical order. It starts
with Kafunk, gets the latest (0.1.9), then looks for the version of
Xylophone that supports 0.1.9. This resolves to Xylophone version 1.0.
Like so:
Kafunk (0.1.9)
Xylophone (1.0)
Known workarounds
Lock the version of Kafunk to the version used in the preferred Xylophone.
nuget Xylophone
nuget Kafunk =0.1.8
The problem with this as a solution is that users of Xylophone and Kafunk
need to know that not only is there a resolution issue, but they need to
manually update the Kafunk version to match the latest Xylophone version.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/2898, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNGETXfifw5IczRfKNmpgFLajXedoks5s2hYcgaJpZM4QeG2v
.

Thanks Steffen, I'll get a PR together and we can discuss from there.

So what I think you would need to do: look at packagerequirement and add a
new field Position. Then add to the CompareTo implementation. Fix all
compiler issues. Done.
Am 15.11.2017 14:15 schrieb "Troy Kershaw"<EMAIL_ADDRESS>
Thanks Steffen, I'll get a PR together and we can discuss from there.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/2898#issuecomment-344588795,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNCCl9-G1A2JatzuQF7b83UUkg-XBks5s2uPjgaJpZM4QeG2v
.

Thanks, that's a great help. Would you like this to replace the comparison by name, or should I feature flag it?

The alphabetical was only a tie breaker anyway. I like to be able to break
it manually
Am 15.11.2017 14:54 schrieb "Troy Kershaw"<EMAIL_ADDRESS>Thanks, that's a great help. Would you like this to replace the comparison
by name, or should I feature flag it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/2898#issuecomment-344598761,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNIkIW6ryFuJcF6vxAaYF_nj6zMnvks5s2u0IgaJpZM4QeG2v
.

I built that as part of conflict resolution fixes. Release under way

Thanks Steffen, your change was much cleaner than mine was turning out to be :)
I enjoyed going through the code and seeing how it all works under the hood.


feat(checks_loader): discard unneeded cloudwatch checks

Description
This pull request includes updates to the load_checks_to_execute method in prowler/lib/check/checks_loader.py to enhance the filtering of checks to execute. The changes ensure that specific checks are excluded if they are not explicitly listed in the check_list.
Key changes include:

Added logic to exclude the cloudwatch_log_group_no_secrets_in_logs check from the checks to execute if it is not present in the check_list.
Added logic to exclude the cloudwatch_log_group_no_critical_pii_in_logs check from the checks to execute if it is not present in the check_list.

Checklist

Are there new checks included in this PR? Yes / No

If so, do we need to update permissions for the provider? Please review this carefully.

[x] Review if the code is being covered by tests.
[x] Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
[x] Review if backport is needed.

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This is working as expected, there is nothing to do.


Implement BranchNotFoundException

Rather than an unspecific RuntimeException :)

And make all exceptions that get thrown to implement the ExceptionInterface of the project.


Code style and typos on all files

Cleaned all files before big tracking PR!

Hello @EmmaRenauld! Thanks for opening this PR.

In the file tests/test_batch_sampler_iter.py:

Line 112:31: E241 multiple spaces after ','

Do see the PEP 8 -- Style Guide for Python Code


GTK+3: Dialog does not disappear

When using NFD from SDL, I noticed that the dialog never disappears after clicking Cancel or OK. It freezes and control is returned to the application as expected, but still remains in the foreground of the application. I can then call the window to the background and continue work. On the next call, the window appears as expected, but predictably shows the same behavior.
I would expect that the dialog disappears and focus is returned to the previous window.

That's just not happening for me over here.  I have NFD_SaveDialog() successfully disappearing in a program that hands its window management and event loop over to SDL.  I am linking against SDL 2.0.1 and libGTK-3 as ships with Ubuntu 14.04 (and Linux Mint 17).
I need advice on how to reproduce this or a pared down program that demonstrates the problem.

I'm running this in Ubuntu 12.10 with latest SDL from https://hg.libsdl.org/SDL and GTK+ 3.6.0.
Based on a hunch I just tried the obvious and called WaitForCleanup() right after gtk_widget_destroy(dialog), and that fixed the problem. You might want to do the same.

I'm experiencing the exact same issue running arch linux with sdl 1.2.15 and GTK+ 3.14.7. Using the fix described above fixes the problem for me.

I'm going to integrate the change as described as soon as I have time to test it.  I use NFD with SDL and it hasn't happened, but I don't want this to waste any more developer time.

Okay, I can't repro this bug, but I am going to fix it.  Can you confirm the solution is:
gtk_widget_destroy(dialog);

WaitForCleanup();
+WaitForCleanup();

return result;

}

Yes, that fixes the problem for me. The same happens with the open multiple dialog.

Since I can't repro this over here, if you could pull my fix and test it, I would appreciate that.

Nope, the dialog stays after calling and becomes unresponsive after selecting a file and clicking open. This only happens to the open and open multiple dialog though, the save dialog works fine. I believe the order of the function calls makes the difference. Putting waitForCleanup(2) after gtk_widget_destroy() fixes the problem, resp. doesn't introduce it in the first place in the save dialog.

Okay, I now understand.  Our previous conversation was not granular enough about the issue.  Proper fix coming up.

Fixed to that specification. Would appreciate a test and confirm.

Yup, that does it. All three dialogs disappear beautifully. Thanks!

Thanks for helping drain the native file dialog swamp!


Removing unwanted XML tag names.

Hello everyone,
In my native app I'm fetching XML data with axios. I can successfully change data to json with xml-js but the json data in this form.
{
  "SOAP-ENV:Envelope" : {
     "SOAP-ENV:Body": {
       "ns:anotherTitle": ...
    }
  }
}

I want to remove SOAP-ENV and ns: for better json structure. How can I achieve this?
Thanks for your help.

You can pass special function to the elementNameFn option to do custom work on the xml element name.
Something like this might solve your problem (not tested):
var convert = require('xml-js');
var xml = '<SOAP-ENV:Envelope>Hi</SOAP-ENV:Envelope>';
var options = {ignoreComment: true, elementNameFn: function(val) {return val.replace('SOAP-ENV:','').replace('ns:','');};
// or simpler:
// var options = {ignoreComment: true, elementNameFn: val => val.replace('SOAP-ENV:','').replace('ns:','')};
var result = convert.xml2js(xml, options); // or convert.xml2json(xml, options)
console.log(result);

You can find more info here  Options for Custom Processing Functions

@nashwaan Thanks for your contribution. It's exactly the same how I want it.


adds type definitions to simple_casper.v.py local variables

While playing around with Casper, I found that the file simple_casper.v.py didn't compile with the latest version of vyper (which is so cool by the way!). I went through and added all the necessary type definitions, which was the majority of the compilation errors. There was one other case where there was an error from a duplicate variable name declaration.

@karlfloersch @vbuterin I turned 26 today, and spent a few hours hacking. I ended up with this and #40 , my first attempts at contributing to Ethereum. I hope it helps, and thanks for Ethereum.

This one handled in #44. This PR should be closed.
@karlfloersch @ChihChengLiang

@djrtwo yep, looks good.


Fixing links in README and RULES files

The links in the main README file for the other languages are broken (#1002). Updating the links in all the README and RULES files to the absolute path.

The content of the files is used to generate/update the website. I don't feel confident with this change.
@helloitsjoe you should check [standard-www](https://github.com/standard/standard-www) against your PR and make sure that the pages are correctly created and linked

Good catch. The README links generate correctly, but for some reason the various rules.html files are pointing to the /docs/RULES.md paths. I'll take a look at this tonight!

@ematipico Hello! I just submitted this PR over at standard-www: standard-www PR#19. I was hoping I could fix this bug without affecting another repo, but I couldn't see a way. If you see another way to do this, just let me know!


Use custom desktop names in Task View

This is good tool to organize work when working on many projects in parallel.
It would be much more helpful if you could switch to correct task from the Task View (shown after pressing Win-Tab). This view, however, displays default generic desktop names (Desktop 1, Desktop 2), which is not very helpful.

Hi @msevcenko,
Windows does not actually let you rename the desktops the way you are asking for: the names you can assign in the script are only used by the script itself (in the popups and in the hover text).
You might want to follow #55 to stay updated on this.
Closing this as it is a duplicate of #55.

Hi, ok thanks for the info.


Multi-AZ deployments fail to render template for spec.index

This bug was encountered while deploying KubeCF 0.2.0 with CF-Operator v2.0.0-0.g0142d1e9
When multi_az is enabled, the pods are created with affinity rules for failure-domain.beta.kubernetes.io/zone=z1 where the nodes in aws have similar labels to failure-domain.beta.kubernetes.io/zone=us-west-2a . I tested changing the underlying cf_deployment manifest to point at the aws az values and this successfully gets the pods scheduled in k8s.
However, once the pods are scheduled, they all go into crashloopbackoff state during init containers. The failing init container in question is template-render and the only associated logs are
2020/02/06 22:12:40 no job instance found for spec index '4'
(The index changes depending on pod queried i.e. kubecf-uaa-z0-0 = 0, kubecf-uaa-z1-0 = 2, kubecf-uaa-z3-0 = 4, etc).
It is also worth noting that the number of pods created initially do not correspond to the number of instances specified, but seems to be #AZ * #Instances
The values used for the KubeCF chart were as follows deployed to an EKS cluster created with eksctl
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-23T14:21:54Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.9-eks-c0eccc", GitCommit:"c0eccca51d7500bb03b2f163dd8d534ffeb2f7a2", GitTreeState:"clean", BuildDate:"2019-12-22T23:14:11Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

system_domain: system.eks.example-domain.com

kube:
    service_cluster_ip_range: <IP_ADDRESS>/16
    pod_cluster_ip_range: <IP_ADDRESS>/16

multi_az: true
high_availability: true

features:
    eirini:
        enabled: true
    autoscaler:
        enabled: false

Attached are statefulset, and pod yaml outputs for further debugging.
get-pods.yml.txt
kubecf-uaa-z1.yml.txt

I added two blockers to this bug in tracker:

https://www.pivotaltracker.com/story/show/169727962
https://www.pivotaltracker.com/story/show/171304400

Hi David, Sorry for the delay.
The issue should be fixed by #843 . I tested it on kind with multiple nodes. Re-open the issue if you still face an issue.


How to distinguish a file from a directory using Filer HTTP API?

I'm trying to figure out how to do so.
Files and directories look the same at first glance.
I'm using a call like this:
curl -H "Accept: application/json" "http://localhost:8888/javascript/?pretty=y"
Thanks.

the files and directories have different mode value. The first bit indicate it is a directory.


Making Modals not under the color editor

Bug: Modals are under color editor
Reproduce:

Open Color editor
Open a modal such a convert

Merged to development branch. Will make it into the next update/release, thanks!


Version 0.2.0 introduces breaking change due to version upgrade

Hi @p1c2u
Version 0.2.0 introduces a breaking change due to the upgrade of the lower bound for the jsonschema dependency.
You can see this downstream in these packages:

https://github.com/p1c2u/openapi-spec-validator/issues/135
https://github.com/zalando/connexion/issues/1430

Restricting the version range of a dependency should be done as a major version update. The iter_errors change (#25) and accompanying version range restriction also should not have been needed yet for jsonschema 4.0.0, as it only provides a deprecation warning for future versions. The current approach leads to a very narrow range of compatibility with jsonschema and other dependent packages.
My proposal would be to release a patch version 0.2.1 reverting #25 and fixing the upper version of jsonschema to 5.0.0. When jsonschema 5.0.0 is released and the old behavior of iter_errors removed, #25 can be applied again, and the version range updated to support both 4.X.X and 5.X.X versions.

Hi @RobbeSneyders
that was my intention to follow new interface of jsonschema 4.x-5.x with version 0.2.x and let 0.1.x support jsonschema 3.x.
I didn't change to version 1.x because the project is not mature enough for this, instead I changed the left-most non-zero digit to follow Caret versioning

Fair point on increasing the minor version while still on 0.X.X, dependents should probably define boundaries on the minor version at this stage. It might be good to note though that caret versioning seems poetry specific, and not completely aligned with semantic versioning which is what most people will expect.
I still think my proposal is valid though. At this point the iter_errors change is unnecessary and limits the compatibility of open-schema-validator with both jsonschema and other packages depending on it.

Hi @p1c2u,

I didn't change to version 1.x because the project is not mature enough for this, instead I changed the left-most non-zero digit to follow Caret versioning

Do you consider versions 0.x to be ready for production? (and more generaly openapi-core ?

@gberaudo 1.x is planned to be stable for production, 0.x is marked as beta and you can expect issues.
@RobbeSneyders I think you're right we dropped support for jsonschema3 too early. I made dependency matrix for various versions

OAS
3.0
3.0
3.1

python
2.7+
3.7+
3.7+

jsonschema
2.x
3.x-4.x
4.x+

openapi-schema-validator
0.1.x
0.2.x
0.3.x

openapi-spec-validator
0.3.x
0.4.x
0.5.x

openapi-core
0.14.x
0.15.x
0.16.x

Thanks @p1c2u, that matrix provides a great overview.
Does that mean you want to release a patch version 0.2.1 reverting #25, as proposed?

@RobbeSneyders
Yes I will do that.

Thank you for your help. Patch version 0.2.1 released hence closing.


Move migration to pre-test step

... so that we've definitely done an npm install first

Should fix the failing test @ https://github.com/dylanpyle/node-api-boilerplate/pull/4 , maybe!


Update sql-data-warehouse-get-started-connect-query.md

Updating next steps

Hi @lodipalm, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@barbkess
Please review and approve here, thanks.

Ross, please approve.


Bump node sass to v3.4.1

From https://github.com/sass/node-sass/releases/tag/v3.4.0
This release has the latest LibSass 3.3.0 release which brings with it
major feature parity Ruby Sass*, massive speed improvements and MUCH
MORE!
I also saw a speed improvement.

Thanks @alexBaizeau!

Released as v0.7.0. :)


liblua not found

Okay, enough with the "funny" stuff, time for an actual issue.
./Bussin.Napture.LINUX: error while loading shared libraries: liblua.so.5.4: cannot open shared object file: No such file or directory

I already have lua5.4, liblua5.4-dev and liblua5.4-0 installed. Do i have to install something else as well?

google doesn't seem to help too :(

Duplicate of #21 i guess? Or should the issue be moved here?

the latest version of gtk4 for ubuntu is 4.12 while rust requires at least 4.13:
> PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags gtk4 gtk4 >= 4.13

i'll try updating the system and we'll see if it helps

it broke my system

it broke my system

oh, that's sad
guess i won't try that then

@Jajoo2 Actually I was able to fix the broken packages using an installation USB, it probably won't break anything for you though.

Also, compiling the browser works now. Closing the issue.


Feature_Request:Add Favicon to Website(Enhancement)

Is your feature request related to a problem? Please describe.
The current version of the website is missing a favicon, which is a small but essential visual element that appears in the browser tab.
Steps to Reproduce
Open the website in a browser.
Observe the absence of a favicon in the browser tab.
Describe the solution you'd like
This enhancement aims to improve user experience and brand recognition by adding a distinctive favicon to the website.
Describe alternatives you've considered

alternate solution is current.
Demo Video/Screenshot (Ma

ndatory )
Are you contributing under any open-source program ?
Yes,Under JWOC.

@apu52 assign this issue to me under JWOC.

@apu52 i need your help in finalising the fav-icon for the Project.


populating EC2 instance-id when launching node via Karpenter

Tell us about your request
What do you want us to build?
Node cleaning mechanism of EC2 instances that are in Not Ready state.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
Not Ready nodes need to be cleaned to avoid waste of compute. EC2 cli aws ec2 terminate-instances requires instance-id as parameters. Karpenter does not populate the instance-id like eksctl does alpha.eksctl.io/instance-id so it requires an extra step of mapping the node name PrivateDnsName with and instance id via aws ec2 describe-instances|jq -r '.Reservations[].Instances[] | [.PrivateDnsName, .InstanceId]| @tsv' which makes it complicated.
Are you currently working around this issue?
How are you currently solving this problem?
#!/bin/bash
aws ec2 describe-instances|jq -r '.Reservations[].Instances[] | [.PrivateDnsName, .InstanceId]| @tsv'> /tmp/private-dns-instanceid

#grap not ready instances for hours
kubectl get no | grep NotReady| awk '{print $1,$4}'| egrep '.*h'| awk '{print $1}'> /tmp/private-dns-not-ready
not_ready_inst=`cat /tmp/private-dns-not-ready`

for i in $not_ready_inst
do
  inst_id=`grep $i /tmp/private-dns-instanceid | awk '{print $2}'`
  aws ec2 terminate-instances --instance-ids $inst_id --no-cli-pager
done

Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

i'm open minded to adding this tag.

Wouldn't you be able to use spec.providerID? It should immediatly be populated with something like aws:///<AZ>/<instance ID>

I wrote this project to enrich labels/annotations with other node metadata as well -- might help you replace the bash script in the mean time.
https://github.com/bdwyertech/aws-node-labeler

This is brilliant! I just add it so got my node labeled. I am ok to close it but wanted to know first if the Karpenter gods wants to add it as default.

We do want to add it! I'm on vacation for a bit, but PRs welcome!


Spanish translation files added

Spanish files added.

Hola Luciano!
Thank you for taking the time to translate all the required files into Spanish! Que genial! Reviewing now 👍🏻

@luc881 has added the five requested Spanish translated files for the following:

[x] README
[x]  CODE_OF_CONDUCT
[x]  CONTRIBUTION-GUIDELINES.md
[x]  LICENSE
[x] about.md

This pull request is for the issue #28 and is now closed and completed. Thank you, Luciano. Excelente trabajo! Merging the feature branch of spanish-translation into the main branch. Muchismo Gracias!


An error occurred while retrieving information for the 'IF_ChatPrompt' node. Traceback (most recent call last):

Yes you missed the Step 3. Move the IF_AI folder from the ComfyUI-IF_AI_tools to inside the root input ComfyUI/input/IF_AI so for you it will be D:\AI\ComfyUI\input\IF_AI

thanks~


sweep: add support for multiple fee preferences to UtxoSweeper

In this PR, we introduce support for arbitrary client fee preferences when accepting input sweep requests. This is possible with the addition of fee rate buckets. Fee rate buckets are buckets that contain inputs with similar fee rates within a specific range, e.g., 1-10 sat/vbyte, 11-20 sat/vbyte, etc. Having these buckets allows us to batch and sweep inputs from different clients with similar fee rates within a single transaction, allowing us to save on chain fees. Implementing these fee rate buckets also lays down the groundwork required for being able to bump the fee rates for particular inputs.
We also get rid of the UtxoSweeper's default fee preference. Any clients using it to sweep inputs specify the same default fee preference to not change their behavior. Each of these can be fine-tuned later on given their use cases.

PTAL @joostjager.

PTAL @joostjager @Roasbeef.

Pushed a new version that removes re-evaluating fee rates for inputs with confirmation targets.

PTAL @Roasbeef @joostjager @halseth.


? operator has incompatible types with try_map and parse_with

this works in 0.11
#[derive(BinRead,)]
#[br(little)]
pub struct Meta {
    /// ID
    pub id: [u8; 6],
    /// Serial number
    #[br(pad_before = 1, parse_with = binrw::helpers::until_eof, try_map = String::from_utf8)]
    pub serial_number: String,
}

it seems to no longer work in 0.13, giving me
error[E0308]: `?` operator has incompatible types
  --> src/lib.rs:11:10
   |
11 | #[derive(BinRead)]
   |          ^^^^^^^ expected `Vec<u8>`, found `String`
   |
   = note: `?` operator cannot convert from `std::string::String` to `Vec<u8>`
   = note: expected struct `Vec<u8>`
              found struct `std::string::String`
note: return type inferred to be `Vec<u8>` here
  --> src/lib.rs:11:10
   |
11 | #[derive(BinRead)]
   |          ^^^^^^^
   = note: this error originates in the derive macro `BinRead` (in Nightly builds, run with -Z macro-backtrace for more info)
help: call `Into::into` on this expression to convert `std::string::String` into `Vec<u8>`
   |
11 | #[derive(BinRead.into())]
   |                 +++++++

For more information about this error, try `rustc --explain E0308`.

Thanks for your report! This issue should be fixed in 0.13.2.


mcrypt is deprecated from php 7.1

And removed in php 7.2 (https://wiki.php.net/rfc/mcrypt-viking-funeral)
Do you have plan to move to OpenSSL?

Hello, @slimus .
Thank you for the question.
As reveals the investigation (done in task OIS-104):

mcrypt functionality not used in Oro code. The only thing is that we have incorrectly named class and service within Security bundle Oro\Bundle\SecurityBundle\Encoder\Mcrypt which in fact uses openssl

To solve this confusion has been created the improvement task BAP-16232 (information for the Oro Community support developers).
Thank you one more time for your contribution to the quality of Oro applications!

And one small thing: you have requirement from ext-mcrypt (https://github.com/oroinc/platform/blob/master/composer.json#L20)
Thank you!

Hi @slimus
Thank you, we will discuss this with the team.

Let's use #782 to track status of mcrypt extension.


Docker image latest-15.1.1 pulling latest-17.0.0

Current Behavior
When I use the docker image to deploy keycloak configs, it warns be of keycloak version mismatch:
2022-03-09 20:09:33.764  INFO 1 --- [           main] d.a.k.config.KeycloakConfigApplication   : Starting KeycloakConfigApplication v4.8.0 using Java 17.0.2 on 938ca3ea9bc1 with PID 1 (/app/keycloak-config-cli.jar started by nobody in /)
2022-03-09 20:09:33.770  INFO 1 --- [           main] d.a.k.config.KeycloakConfigApplication   : No active profile set, falling back to 1 default profile: "default"
2022-03-09 20:09:35.556  INFO 1 --- [           main] d.a.k.config.KeycloakConfigApplication   : Started KeycloakConfigApplication in 3.435 seconds (JVM running for 4.535)
2022-03-09 20:09:37.595  INFO 1 --- [           main] d.a.k.c.provider.KeycloakImportProvider  : 2 configuration files found.
2022-03-09 20:09:37.601  INFO 1 --- [           main] d.a.k.c.provider.KeycloakImportProvider  : Loading file '/config/00-REDACTED.json'
2022-03-09 20:09:38.038  INFO 1 --- [           main] d.a.k.c.provider.KeycloakImportProvider  : Loading file '/config/01-master.json'
2022-03-09 20:09:38.049  INFO 1 --- [           main] d.a.k.config.KeycloakConfigRunner        : Importing file '/config/00-REDACTED.json'
2022-03-09 20:09:38.058  INFO 1 --- [           main] d.a.k.config.provider.KeycloakProvider   : Wait 600 seconds until https://staging.auth.REDACTED.com/auth is available ...
2022-03-09 20:09:39.186  WARN 1 --- [           main] d.a.k.config.provider.KeycloakProvider   : Local keycloak-config-cli (4.8.0-17.0.0) and remote Keycloak (15.1.1) may not compatible.
2022-03-09 20:09:47.897  INFO 1 --- [           main] d.a.k.config.KeycloakConfigRunner        : Importing file '/config/01-master.json'
2022-03-09 20:09:51.490  INFO 1 --- [           main] d.a.k.config.KeycloakConfigRunner        : keycloak-config-cli running in 00:13.900.

On staging it runs without issues, but on production the procedure caused the cluster to panic with an internal server error:
2022-03-09 19:28:43.021  INFO 1 --- [           main] d.a.k.config.KeycloakConfigApplication   : Starting KeycloakConfigApplication v4.8.0 using Java 17.0.2 on 6168b978f449 with PID 1 (/app/keycloak-config-cli.jar started by nobody in /)
2022-03-09 19:28:43.028  INFO 1 --- [           main] d.a.k.config.KeycloakConfigApplication   : No active profile set, falling back to 1 default profile: "default"
2022-03-09 19:28:44.671  INFO 1 --- [           main] d.a.k.config.KeycloakConfigApplication   : Started KeycloakConfigApplication in 3.298 seconds (JVM running for 4.357)
2022-03-09 19:28:47.153  INFO 1 --- [           main] d.a.k.c.provider.KeycloakImportProvider  : 2 configuration files found.
2022-03-09 19:28:47.158  INFO 1 --- [           main] d.a.k.c.provider.KeycloakImportProvider  : Loading file '/config/00-REDACTED.json'
2022-03-09 19:28:47.509  INFO 1 --- [           main] d.a.k.c.provider.KeycloakImportProvider  : Loading file '/config/01-master.json'
2022-03-09 19:28:47.514  INFO 1 --- [           main] d.a.k.config.KeycloakConfigRunner        : Importing file '/config/00-REDACTED.json'
2022-03-09 19:28:47.521  INFO 1 --- [           main] d.a.k.config.provider.KeycloakProvider   : Wait 600 seconds until https://production.auth.REDACTED.com/auth is available ...
2022-03-09 19:28:48.621  WARN 1 --- [           main] d.a.k.config.provider.KeycloakProvider   : Local keycloak-config-cli (4.8.0-17.0.0) and remote Keycloak (15.1.1) may not compatible.
2022-03-09 19:28:50.854 ERROR 1 --- [           main] d.a.k.config.KeycloakConfigRunner        : HTTP 500 Internal Server Error
2022-03-09 19:28:50.855  INFO 1 --- [           main] d.a.k.config.KeycloakConfigRunner        : keycloak-config-cli running in 00:03.706.

Both latest-15.1.1 and v4.8.0-15.1.1 have the same digest hashes, so I expect them both to be the wrong keycloak-config-cli versions.
Downgrading to docker tag v4.7.0-15.1.1 solves the issue.
Expected Behavior
Tag latest-15.1.1 to be compatible with keycloak 15.1.1.
Steps To Reproduce
- Use the tag latest-15.1.1
- try to deploy configs to keycloak 15.1.1
- Downgrade the tag to version v4.7.0-15.1.1 and the issue is gone.

Environment

Keycloak Version: 15.1.1
keycloak-config-cli Version: latest-15.1.1
Java Version: 17.0.2

Anything else?
No response

Thanks for reporting this. Should be fixed in 4.8.1 now.


Detect mismatched SSL versions

TESTING NOT READY FOR REVIEW
With this change the unit tests will fail if we manage to compile the library and libcurl against incompatible version of the SSL library.  The typical case is having libcurl compiled against OpenSSL/1.0.2 but compiling the google cloud storage library against OpenSSL/1.1.0, but other combinations are possible and also bad ideas (e.g. OpenSSL with LibreSSL and google cloud storage with OpenSSL).
The problems is that soon we will need to setup global configuration in the SSL library used by libcurl, specifically, the locking strategy so we can use libcurl with multiple threads.  That is not possible if we are configuring a different global state than the state used by libcurl.

This change is

I am going to fix this in a different way. Closing this PR.


Operation not permitted (os error 1)

Bug description
Trying to run even the simplest query results in an error: Operation not permitted (os error 1)
How to reproduce
My code:
import { PrismaClient } from '@prisma/client';

const client = new PrismaClient({ log: ['query', 'info', 'warn'] });

export const initDb = async () => {
  console.log(await client.$queryRaw`SELECT 1=1;`);
};

initDb();

Expected behavior
Prisma information
DEBUG="*" node app.js
  prisma-client {
  prisma-client   engineConfig: {
  prisma-client     cwd: '/usr/home/……/myproject/apps/api/prisma',
  prisma-client     enableDebugLogs: false,
  prisma-client     enableEngineDebugMode: undefined,
  prisma-client     datamodelPath: '/usr/home/……/myproject/node_modules/.prisma/client/schema.prisma',
  prisma-client     prismaPath: undefined,
  prisma-client     engineEndpoint: undefined,
  prisma-client     generator: {
  prisma-client       name: 'client',
  prisma-client       provider: 'prisma-client-js',
  prisma-client       output: '/usr/home/……/myproject/node_modules/@prisma/client',
  prisma-client       binaryTargets: [],
  prisma-client       previewFeatures: [],
  prisma-client       config: {}
  prisma-client     },
  prisma-client     showColors: false,
  prisma-client     logLevel: 'info',
  prisma-client     logQueries: true,
  prisma-client     flags: [],
  prisma-client     clientVersion: '2.10.0',
  prisma-client     enableExperimental: [],
  prisma-client     useUds: undefined
  prisma-client   }
  prisma-client } +0ms
  plusX Execution permissions of /home/……/prisma-engines/target/release/query-engine are fine +0ms
  engine port: undefined +0ms
  prisma-client prisma.queryRaw(SELECT 1=1;, []) +2s
  prisma-client Prisma Client call: +0ms
  prisma-client Prisma Client call: +20ms
  prisma-client prisma.queryRaw({
  prisma-client   query: 'SELECT 1=1;',
  prisma-client   parameters: {
  prisma-client     values: '[]',
  prisma-client     __prismaRawParamaters__: true
  prisma-client   }
  prisma-client }) +2ms
  prisma-client Generated request: +0ms
  prisma-client mutation {
  prisma-client   queryRaw(
  prisma-client     query: "SELECT 1=1;"
  prisma-client     parameters: "[]"
  prisma-client   )
  prisma-client }
  prisma-client  +0ms
  engine {
  engine   cwd: '/usr/home/……/myproject/apps/api/prisma'
  engine } +52ms
  plusX Execution permissions of /home/……/prisma-engines/target/release/query-engine are fine +53ms
  engine { flags: [ '--enable-raw-queries' ] } +0ms
  engine port: 16893 +3ms
  engine data Oct 29 18:37:48.965 TRACE query_engine::exec_loader: Loading Postgres connector... +22ms
  engine SyntaxError: Unexpected token  in JSON at position 0
  engine     at JSON.parse (<anonymous>)
  engine     at LineStream.<anonymous> (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:9439:33)
  engine     at LineStream.emit (events.js:311:20)
  engine     at addChunk (_stream_readable.js:294:12)
  engine     at readableAddChunk (_stream_readable.js:275:11)
  engine     at LineStream.Readable.push (_stream_readable.js:209:10)
  engine     at LineStream.Transform.push (_stream_transform.js:152:32)
  engine     at LineStream._pushBuffer (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4670:19)
  engine     at LineStream._transform (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4664:10)
  engine     at LineStream.Transform._read (_stream_transform.js:191:10) Oct 29 18:37:48.965 TRACE query_engine::exec_loader: Loading Postgres connector... +1ms
  engine data Oct 29 18:37:48.966  INFO quaint::pooled: Starting a postgresql pool with 25 connections. +1ms
  engine SyntaxError: Unexpected token  in JSON at position 0
  engine     at JSON.parse (<anonymous>)
  engine     at LineStream.<anonymous> (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:9439:33)
  engine     at LineStream.emit (events.js:311:20)
  engine     at addChunk (_stream_readable.js:294:12)
  engine     at readableAddChunk (_stream_readable.js:275:11)
  engine     at LineStream.Readable.push (_stream_readable.js:209:10)
  engine     at LineStream.Transform.push (_stream_transform.js:152:32)
  engine     at LineStream._pushBuffer (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4670:19)
  engine     at LineStream._transform (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4664:10)
  engine     at LineStream.Transform._read (_stream_transform.js:191:10) Oct 29 18:37:48.966  INFO quaint::pooled: Starting a postgresql pool with 25 connections. +0ms
  engine data Oct 29 18:37:48.966 TRACE query_engine::exec_loader: Loaded Postgres connector. +1ms
  engine SyntaxError: Unexpected token  in JSON at position 0
  engine     at JSON.parse (<anonymous>)
  engine     at LineStream.<anonymous> (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:9439:33)
  engine     at LineStream.emit (events.js:311:20)
  engine     at addChunk (_stream_readable.js:294:12)
  engine     at readableAddChunk (_stream_readable.js:275:11)
  engine     at LineStream.Readable.push (_stream_readable.js:209:10)
  engine     at LineStream.Transform.push (_stream_transform.js:152:32)
  engine     at LineStream._pushBuffer (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4670:19)
  engine     at LineStream._transform (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4664:10)
  engine     at LineStream.Transform._read (_stream_transform.js:191:10) Oct 29 18:37:48.966 TRACE query_engine::exec_loader: Loaded Postgres connector. +0ms
  engine data Oct 29 18:37:48.987 DEBUG quaint::pooled::manager: Acquired database connection. +18ms
  engine SyntaxError: Unexpected token  in JSON at position 0
  engine     at JSON.parse (<anonymous>)
  engine     at LineStream.<anonymous> (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:9439:33)
  engine     at LineStream.emit (events.js:311:20)
  engine     at addChunk (_stream_readable.js:294:12)
  engine     at readableAddChunk (_stream_readable.js:275:11)
  engine     at LineStream.Readable.push (_stream_readable.js:209:10)
  engine     at LineStream.Transform.push (_stream_transform.js:152:32)
  engine     at LineStream._pushBuffer (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4670:19)
  engine     at LineStream._transform (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4664:10)
  engine     at LineStream.Transform._read (_stream_transform.js:191:10) Oct 29 18:37:48.987 DEBUG quaint::pooled::manager: Acquired database connection. +0ms
  engine data Oct 29 18:37:48.987  INFO query_engine::server: Started http server +1ms
  engine SyntaxError: Unexpected token  in JSON at position 0
  engine     at JSON.parse (<anonymous>)
  engine     at LineStream.<anonymous> (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:9439:33)
  engine     at LineStream.emit (events.js:311:20)
  engine     at addChunk (_stream_readable.js:294:12)
  engine     at readableAddChunk (_stream_readable.js:275:11)
  engine     at LineStream.Readable.push (_stream_readable.js:209:10)
  engine     at LineStream.Transform.push (_stream_transform.js:152:32)
  engine     at LineStream._pushBuffer (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4670:19)
  engine     at LineStream._transform (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4664:10)
  engine     at LineStream.Transform._read (_stream_transform.js:191:10) Oct 29 18:37:48.987  INFO query_engine::server: Started http server +0ms
  engine data Oct 29 18:37:48.987  INFO query_engine: Encountered error during initialization: +0ms
  engine SyntaxError: Unexpected token  in JSON at position 0
  engine     at JSON.parse (<anonymous>)
  engine     at LineStream.<anonymous> (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:9439:33)
  engine     at LineStream.emit (events.js:311:20)
  engine     at addChunk (_stream_readable.js:294:12)
  engine     at readableAddChunk (_stream_readable.js:275:11)
  engine     at LineStream.Readable.push (_stream_readable.js:209:10)
  engine     at LineStream.Transform.push (_stream_transform.js:152:32)
  engine     at LineStream._pushBuffer (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4670:19)
  engine     at LineStream._transform (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4664:10)
  engine     at LineStream.Transform._read (_stream_transform.js:191:10) Oct 29 18:37:48.987  INFO query_engine: Encountered error during initialization: +0ms
  engine stderr {"is_panic":false,"message":"Operation not permitted (os error 1)","backtrace":"   0: <unknown>\n   1: <unknown>\n   2: <unknown>\n   3: <unknown>\n   4: <unknown>\n   5: <unknown>\n   6: <unknown>\n   7: <unknown>\n   8: <unknown>\n   9: <unknown>\n  10: <unknown>\n  11: <unknown>\n  12: <unknown>\n  13: <unknown>\n  14: <unknown>\n  15: <unknown>\n  16: <unknown>\n  17: <unknown>\n"} +1ms
  engine {
  engine   is_panic: false,
  engine   message: 'Operation not permitted (os error 1)',
  engine   backtrace: '   0: <unknown>\n' +
  engine     '   1: <unknown>\n' +
  engine     '   2: <unknown>\n' +
  engine     '   3: <unknown>\n' +
  engine     '   4: <unknown>\n' +
  engine     '   5: <unknown>\n' +
  engine     '   6: <unknown>\n' +
  engine     '   7: <unknown>\n' +
  engine     '   8: <unknown>\n' +
  engine     '   9: <unknown>\n' +
  engine     '  10: <unknown>\n' +
  engine     '  11: <unknown>\n' +
  engine     '  12: <unknown>\n' +
  engine     '  13: <unknown>\n' +
  engine     '  14: <unknown>\n' +
  engine     '  15: <unknown>\n' +
  engine     '  16: <unknown>\n' +
  engine     '  17: <unknown>\n'
  engine } +1ms
  prisma-client Error: Operation not permitted (os error 1)
  prisma-client     at LineStream.<anonymous> (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:9424:31)
  prisma-client     at LineStream.emit (events.js:311:20)
  prisma-client     at addChunk (_stream_readable.js:294:12)
  prisma-client     at readableAddChunk (_stream_readable.js:275:11)
  prisma-client     at LineStream.Readable.push (_stream_readable.js:209:10)
  prisma-client     at LineStream.Transform.push (_stream_transform.js:152:32)
  prisma-client     at LineStream._pushBuffer (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4670:19)
  prisma-client     at LineStream._transform (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:4664:10)
  prisma-client     at LineStream.Transform._read (_stream_transform.js:191:10)
  prisma-client     at LineStream.Transform._write (_stream_transform.js:179:12) +51ms
PrismaClientInitializationError2:
Invalid `prisma.queryRaw()` invocation:

  Operation not permitted (os error 1)
    at PrismaClientFetcher.request (/usr/home/……/myproject/node_modules/@prisma/client/runtime/index.js:15782:15)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  clientVersion: '2.10.0'
}

Environment & setup

OS: FreeBSD 11
Database: PostgreSQL
Node.js version: 12.16.1
Prisma version:

@prisma/cli          : 2.10.0
@prisma/client       : 2.10.0
Current platform     : freebsd11
Query Engine         : query-engine eefa9e6e5a4d42803ffc12e2d8131858b5181f65 (at ../../../../../../../../home/……/prisma-engines/target/release/query-engine, resolved by PRISMA_QUERY_ENGINE_BINARY)
Migration Engine     : migration-engine-cli 6fafbb461b7e0c140280a7794ed19a4f7035f577 (at ../../../../../../../../home/……/prisma-engines/target/release/migration-engine, resolved by PRISMA_MIGRATION_ENGINE_BINARY)
Introspection Engine : introspection-core 6fafbb461b7e0c140280a7794ed19a4f7035f577 (at ../../../../../../../../home/……/prisma-engines/target/release/introspection-engine, resolved by PRISMA_INTROSPECTION_ENGINE_BINARY)
Format Binary        : prisma-fmt 6fafbb461b7e0c140280a7794ed19a4f7035f577 (at ../../../../../../../../home/……/prisma-engines/target/release/prisma-fmt, resolved by PRISMA_FMT_BINARY)
Studio               : 0.304.0

I figured that if I hardcode getFreePort() to always return the same port which I manually opened, the Operation not permitted error is gone.
However, Prisma hangs indefinitely on the very first query I try to make. No additional output is available.

I figured this is because prisma-engines have to be run with RUST_LOG_FORMAT=json instead of devel (which is the default in .envrc file.

@mmiszy
Try using the UDS mode (Unix domain sockets). That won't open the port in the first place.
const client = new PrismaClient({ __internal: { useUds: true }});

We plan to make this the default in the near future.

Thank you, that solves it.
Sorry, I wasn't sure which repo is the right one to open issues.

It is alright, we usually transfer issues to appropriate place so no need to open things twice in the future :)


BUG: content_type field CustomContentTypeField is limited to empty queryset

When CUSTOM_CONTENT_TYPES is defined, queryset passed here: https://github.com/kunitoki/django-custard/blob/master/custard/builder.py#L94 returns empty queryset.
It causes the choices in admin form is empty.
P.S.
When 0.10 version will be released?

Coverage remained the same at 95.76% when pulling ba7ee640742b5f2dd8c1cb84fe42891402fdd7ce on quamilek:bugfix/empty-content-type-list into 37a659cc254ff222f862aea542749c002aa2d42a on kunitoki:master.

thanx for reporting!


chore: Added zipy.ai for analytics

Description
Adds zippy.ai for analytics
Type of change

New analytics tool

How Has This Been Tested?

Manual

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
No changes to code coverage between the base branch and the head branch

/ok-to-test sha=2e583af


record_accessor: Make code simple and bit faster

Signed-off-by: Masahiro Nakagawa<EMAIL_ADDRESS>Which issue(s) this PR fixes:
None
What this PR does / why we need it:
Make record_accessor code simple by moving call_index to default implementation.
New implementation is bit faster.
Warming up --------------------------------------
                base   317.029k i/100ms
                test   327.406k i/100ms
Calculating -------------------------------------
                base     10.600M (± 6.1%) i/s -     52.944M in   5.019043s
                test     10.797M (± 4.2%) i/s -     54.022M in   5.013882s

Docs Changes:
No need
Release Note:
Same as title.

Ah, I forgot to paste the code.
require 'benchmark/ips'

class Base
  def initialize
    @keys = 'k'
    mcall = method(:call_index)
    singleton_class.module_eval do
      define_method(:call, mcall)
    end
  end

  def call(r)
  end

  def call_dig(r)
    r.dig(*@keys)
  end

  def call_index(r)
    r[@keys]
  end
end

class Test
  def initialize
    @keys = 'k'
  end

  def call(r)
    r[@keys]
  end

  def call_dig(r)
    r.dig(*@keys)
  end
end

record = {'k' => 'foo'}
base = Base.new
test = Test.new

Benchmark.ips do |x|
  x.report "base" do
    base.call(record)
  end

  x.report "test" do
    test.call(record)
  end
end

I see. made it faster when using a default implementation 👍


node-sass fails with node v12

Consider upgrading node-sass to 4.12 because it's not longer compatible with recent node versions.
Description
I bumped into this error when building with CircleCI PHP default image (uses node v12)
yarn command fails:

Here's supported versions:
https://www.npmjs.com/package/node-sass
I made the change in package.json and v.12 works fine.
Steps to reproduce
sudo service docker start
docker pull circleci/php:7.3-node-browsers
docker run -it circleci/php:7.3-node-browsers /bin/bash
git clone git@github.com:roots/sage.git && cd sage
yarn

https://github.com/roots/sage/pull/2416


Proposal: custom tokens

I want to propose an extra section in kuma.config customTokens
colors: {
   ...
},
customTokens: {
   transforms: {
      scaleUp: "scaleY(1.5)"
   }
}

So you can use them in your CSS like
css`
  transform: t("trasforms.scaleUp")
`

What do you think?

How about just write the custom token fields in the top level of theme configuration?


Property 'HMRClient' doesn't exist

Environment

Windows 11
"react": "18.2.0",
"react-native": "0.73.4"
targeting Android platform
"@callstack/repack": "^3.7.0",
"webpack": "^5.90.1"
"terser-webpack-plugin": "^5.3.10",

Description
Running into this issue on my windows local environment. Any help would be appreciated
Run steps:

run react-native webpack-start --host <IP_ADDRESS> --webpackConfig ./webpack.config.mjs in it's own terminal
run react-native run-android --no-packager in it's own terminal

App installs and presents following error on the emulated device

Reproducible Demo
##Webpack Config
`import path from 'path';
import TerserPlugin from 'terser-webpack-plugin';
import * as Repack from '@callstack/repack';
/**

More documentation, installation, usage, motivation and differences with Metro is available at:
https://github.com/callstack/repack/blob/main/README.md

The API documentation for the functions and plugins used in this file is available at:
https://re-pack.netlify.app/
*/

/**

Webpack configuration.
You can also export a static object or a function returning a Promise.

@param env Environment options passed from either Webpack CLI or React Native CLI

       when running with `react-native start/bundle`.

*/
export default (env) => {
const {
mode = 'development',
context = Repack.getDirname(import.meta.url),
entry = './index.js',
platform = process.env.PLATFORM,
minimize = mode === 'production',
devServer = undefined,
bundleFilename = undefined,
sourceMapFilename = undefined,
assetsPath = undefined,
reactNativePath = new URL('./node_modules/react-native', import.meta.url)
.pathname,
} = env;
const dirname = Repack.getDirname(import.meta.url);
if (!platform) {
throw new Error('Missing platform');
}
/**

Using Module Federation might require disabling hmr.
Uncomment below to set devServer.hmr to false.

Keep in mind that devServer object is not available
when running webpack-bundle command. Be sure
to check its value to avoid accessing undefined value,
otherwise an error might occur.
*/
// if (devServer) {
//   devServer.hmr = false;
// }

/**

Depending on your Babel configuration you might want to keep it.
If you don't use env in your Babel config, you can remove it.

Keep in mind that if you remove it you should set BABEL_ENV or NODE_ENV
to development or production. Otherwise your production code might be compiled with
in development mode by Babel.
*/
process.env.BABEL_ENV = mode;

return {
mode,
/**
* This should be always false, since the Source Map configuration is done
* by SourceMapDevToolPlugin.
/
devtool: false,
context,
/*
* getInitializationEntries will return necessary entries with setup and initialization code.
* If you don't want to use Hot Module Replacement, set hmr option to false. By default,
* HMR will be enabled in development mode.
/
entry: [
...Repack.getInitializationEntries(reactNativePath, {
hmr: devServer && devServer.hmr,
}),
entry,
],
resolve: {
/*
* getResolveOptions returns additional resolution configuration for React Native.
* If it's removed, you won't be able to use <file>.<platform>.<ext> (eg: file.ios.js)
* convention and some 3rd-party libraries that specify react-native field
* in their package.json might not work correctly.
*/
...Repack.getResolveOptions(platform),
  /**
   * Uncomment this to ensure all `react-native*` imports will resolve to the same React Native
   * dependency. You might need it when using workspaces/monorepos or unconventional project
   * structure. For simple/typical project you won't need it.
   */
  // alias: {
  //   'react-native': reactNativePath,
  // },
},
/**
 * Configures output.
 * It's recommended to leave it as it is unless you know what you're doing.
 * By default Webpack will emit files into the directory specified under `path`. In order for the
 * React Native app use them when bundling the `.ipa`/`.apk`, they need to be copied over with
 * `Repack.OutputPlugin`, which is configured by default inside `Repack.RepackPlugin`.
 */
output: {
  clean: true,
  hashFunction: 'xxhash64',
  path: path.resolve(dirname, 'build/generated', platform),
  filename: 'index.bundle',
  chunkFilename: '[name].chunk.bundle',
  publicPath: Repack.getPublicPath({ platform, devServer }),
},
/**
 * Configures optimization of the built bundle.
 */
optimization: {
  /** Enables minification based on values passed from React Native CLI or from fallback. */
  minimize,
  /** Configure minimizer to process the bundle. */
  minimizer: [
    new TerserPlugin({
      test: /\.(js)?bundle(\?.*)?$/i,
      /**
       * Prevents emitting text file with comments, licenses etc.
       * If you want to gather in-file licenses, feel free to remove this line or configure it
       * differently.
       */
      extractComments: false,
      terserOptions: {
        format: {
          comments: false,
        },
      },
    }),
  ],
  chunkIds: 'named',
},
module: {
  /**
   * This rule will process all React Native related dependencies with Babel.
   * If you have a 3rd-party dependency that you need to transpile, you can add it to the
   * `include` list.
   *
   * You can also enable persistent caching with `cacheDirectory` - please refer to:
   * https://github.com/babel/babel-loader#options
   */
  rules: [
    {
      test: /\.[jt]sx?$/,
      include: [
        /node_modules(.*[/\\])+react\//,
        /node_modules(.*[/\\])+react-native/,
        /node_modules(.*[/\\])+@react-native/,
        /node_modules(.*[/\\])+@react-navigation/,
        /node_modules(.*[/\\])+@react-native-community/,
        /node_modules(.*[/\\])+expo/,
        /node_modules(.*[/\\])+pretty-format/,
        /node_modules(.*[/\\])+metro/,
        /node_modules(.*[/\\])+abort-controller/,
        /node_modules(.*[/\\])+@callstack\/repack/,
      ],
      use: 'babel-loader',
    },
    /**
     * Here you can adjust loader that will process your files.
     *
     * You can also enable persistent caching with `cacheDirectory` - please refer to:
     * https://github.com/babel/babel-loader#options
     */
    {
      test: /\.[jt]sx?$/,
      exclude: /node_modules/,
      use: {
        loader: 'babel-loader',
        options: {
          /** Add React Refresh transform only when HMR is enabled. */
          plugins:
            devServer && devServer.hmr
              ? ['module:react-refresh/babel']
              : undefined,
        },
      },
    },
    /**
     * This loader handles all static assets (images, video, audio and others), so that you can
     * use (reference) them inside your application.
     *
     * If you wan to handle specific asset type manually, filter out the extension
     * from `ASSET_EXTENSIONS`, for example:
     * ```
     * Repack.ASSET_EXTENSIONS.filter((ext) => ext !== 'svg')
     * ```
     */
    {
      test: Repack.getAssetExtensionsRegExp(Repack.ASSET_EXTENSIONS),
      use: {
        loader: '@callstack/repack/assets-loader',
        options: {
          platform,
          devServerEnabled: Boolean(devServer),
          /**
           * Defines which assets are scalable - which assets can have
           * scale suffixes: `@1x`, `@2x` and so on.
           * By default all images are scalable.
           */
          scalableAssetExtensions: Repack.SCALABLE_ASSETS,
        },
      },
    },
  ],
},
plugins: [
  /**
   * Configure other required and additional plugins to make the bundle
   * work in React Native and provide good development experience with
   * sensible defaults.
   *
   * `Repack.RepackPlugin` provides some degree of customization, but if you
   * need more control, you can replace `Repack.RepackPlugin` with plugins
   * from `Repack.plugins`.
   */
  new Repack.RepackPlugin({
    context,
    mode,
    platform,
    devServer,
    output: {
      bundleFilename,
      sourceMapFilename,
      assetsPath,
    },
  }),
],

};
};
`

Sorry, but I resolved it by disabling HMR -_-,
In the ‘webpack.config.mjs’ file, replace:
hmr: devServer && devServer.hmr, -> hmr: false

hi @mikeFromUDig
I don't have access to a Windows machine atm, but I have an idea what might be happening, can you try doing the following:
In webpack.config please replace
entry: [
  ...Repack.getInitializationEntries(reactNativePath, {
    hmr: devServer && devServer.hmr,
  }),
  entry,
],

with
entry: [
  ...Repack.getInitializationEntries(reactNativePath, {
    hmr: false,
  }),
  path.resolve('@callstack/repack/modules/WebpackHMRClient.js'),
  entry,
],

Please see if that works. The path to WebpackHMRClient might need some adjusting though.

hi @mikeFromUDig
I don't have access to a Windows machine atm, but I have an idea what might be happening, can you try doing the following:
In webpack.config please replace
entry: [
  ...Repack.getInitializationEntries(reactNativePath, {
    hmr: devServer && devServer.hmr,
  }),
  entry,
],

with
entry: [
  ...Repack.getInitializationEntries(reactNativePath, {
    hmr: false,
  }),
  path.resolve('@callstack/repack/modules/WebpackHMRClient.js'),
  entry,
],

Please see if that works. The path to WebpackHMRClient might need some adjusting though.

this doesn't work for me

@mikeFromUDig @vinhmdev @peterbd found the root issue.
to resolve the error in question please adjust the path of @callstack/repack inside of module.rules in webpack.config.mjs like this:
diff --git a/templates/webpack.config.mjs b/templates/webpack.config.mjs
index 18313be..e702a00 100644
--- a/templates/webpack.config.mjs
+++ b/templates/webpack.config.mjs
@@ -159,7 +159,7 @@ export default (env) => {
             /node_modules(.*[/\\])+pretty-format/,
             /node_modules(.*[/\\])+metro/,
             /node_modules(.*[/\\])+abort-controller/,
-            /node_modules(.*[/\\])+@callstack\/repack/,
+            /node_modules(.*[/\\])+@callstack[/\\]repack/,
           ],
           use: 'babel-loader',
         },


force hard limits for words count in textareas

wipe 10% of allowance in certain textareas

 [QAE16IMP]: change the word counts to be hard word counts from soft word counts


fix bugs around nested mounting

When using Mounts to nest routes any more than a single level deep, schema generation ignores all levels before the last and general routing completely blows up . This resolves those issues.
example:
app.mount('/api/', app=Router(routes=[
    Mount('/v1/', app=Router(routes=[
        Mount('/check/', app=Router(routes=[
            Route('/', EligibilityEndpoint, app.router, methods=['GET']),
            Route('/bulk/', BulkEligibilityEndpoint, app.router, methods=['POST']),
        ])),
        Mount('/membership/', app=Router(routes=[
            Route('/purchase/', MembershipPurchaseEndpoint, app.router, methods=['POST']),
        ])),
    ])),
]))

It seems that black formatting is failing, could you fix it?

Hi @perdy I know the author of this PR and we discussed it. It looks like you are using black as a linter. It is intended to be used as a code formatter instead; in other words, actually letting black make the changes it suggests.
In this case black is reporting that the issue is the use of single quotes on three lines. It would be easy enough to fix manually, but letting black handle that automatically upon merge to master is even easier. To wit: #34. If you can merge that PR and re-trigger this one's CI pipeline, it should pass. Also please check out my other open PR. Thanks! :)