text:
Is it possible to configure :arglists formatting or disable it completely?

Hi @kkinnear!
First of all, thank you for such a great tool — zprint is a beast (in a good sense)! I've never felt closer to solving the Clojure's most infamous "unsolvable" formatting problem. And now, with the advent of zprint, I am confident that this is possible.
Although I still notice a few wrinkles here and there. The one that bothers me the most deals with functions' attr-maps, in particular :arglists quoted forms.
My config (which is searched, found and otherwise works):
{:width       120
 :style       [:justified
               :multi-lhs-hang
               :respect-nl
               :require-pair
               :sort-require
               :extend-nl
               :rod-no-ma-nl]
 :fn-map      {"->"    [:noarg1-body
                        {:list               {:indent-only?   true
                                              :constant-pair? false}
                         :next-inner-restore [[:list :indent-only?]
                                              [:list :constant-pair?]]}]
               ;; https://github.com/kkinnear/zprint/issues/329
               "assoc" [:guided-body
                        {:guide [:element :mark 1 :element-best :newline :align 1 :element-pair-*]}]}
 :fn-type-map {:arg1 [:hang {}]}
 :map         {:indent  0
               :justify {:max-variance 40}
               :comma?  false}
 :binding     {:indent   0
               :justify? false}
 :pair        {:indent 0}
 :vector      {:wrap-after-multi? false
               :no-wrap-after     #{"&"}}
 :list        {:wrap-after-multi? false
               :no-wrap-after     #{"&"}
               :indent-only-style :input-hang}
 :set         {:wrap-after-multi? false}
 :comment     {:wrap? false}}

I've omitted :quote in my config intentionally.
What I have before running zprint:
(defn my-fn-1
  "..."
  {:arglists '([obj mapping-fn]
               [obj mapping-fn {:keys [tempid entity-spec apply-tx-fn]
                                :as   opts}])}
  ...)

(defn my-fn-2
  "..."
  {:arglists '([client db-name & {:keys [db-actions migrations-dir]
                                  :as   options}])}
  ...)

This is what I expect to stay intact, since in both cases max line length is much smaller than 120.
In other words, I need all arglist vectors:

wrap only if there is no more free space on the line
regardless of their elements' content (symbols, maps)

What I end up after running zprint:
(defn my-fn-1
  "..."
  {:arglists '([obj mapping-fn]
               [obj mapping-fn
                {:keys [tempid entity-spec apply-tx-fn]
                 :as   opts}])}
  ...)

(defn my-fn-2
  "..."
  {:arglists '([client db-name &
                {:keys [db-actions migrations-dir]
                 :as   options}])}
  ...)

Issues:

it wraps the line whenever there is a destructuring map, before the map
it seems like :no-wrap-after config option is completely ignored

I tried my best to figure things out on my own, but now I'm kinda stuck.
Is there a way to configure this somehow? Is there something I am missing?

Sorry to take so long to respond.  I did a quick try on this a week ago, to no particular avail, and have been away from my desk for a while.  What I have seen is that the inserted newline after mapping-fn in the first example seems to be triggered by the newline prior to the :as.  If there is no newline prior to the :as, it puts the entire rest of that argilst vector on one line.  I am just starting to try to figure out why this is happening and what to do about it.  This is what I am getting without using all of your configuration (not that I don't appreciate your sending me the whole configuration, that will be very helpful).  Anyway, thanks for your patience.  I will let you know what I come up with, hopefully soon.

Sure, there is no rush. It's nice to know that this behavior is as confusing to you, the author, as it is to me. 😅

Interesting question, for sure.  This exposed a problem with :no-wrap-after (where it only worked in very limited situations) that I have fixed for 1.3.0, but that obviously isn't going to do you much good.  The good news is that I think that I have a solution to the larger problem so that the :no-wrap-after issue won't really be much of an issue for you.
One note -- while testing this I have enabled :map {:force-nl? true} for maps inside of :arglists, because I got really tired of trying to create test cases with the newlines in the right places.  I would suggest that you might want to keep things that way, and not rely on your own newlines to put the map keys on separate lines.  The :force-nl? true in :map will do that for you.  Of course, once something is formatted, then there are newlines already in there, but that's what you get with :respect-nl, so I guess you are used to it.
Anyway, using a guide, I seem to be able to get what I think you are looking for. I have some tests that include parameters after the map in an argilist so that we can see what they do, since you have configuration about :wrap-after-multi? false.
Here is the configuration used by these tests:
{:binding {:indent 0, :justify? false},
 :comment {:wrap? false},
 :fn-map
   {"->" [:noarg1-body {:list {:constant-pair? false, :indent-only? true},
           :next-inner-restore
             [[:list :indent-only?] [:list :constant-pair?]]}],
    "assoc"
      [:guided-body {:guide
          [:element :mark 1 :element-best :newline :align 1 :element-pair-*]}]},
 :fn-type-map {:arg1 [:hang {}]},
 :list {:indent-only-style :input-hang,
        :no-wrap-after #{"&"},
        :wrap-after-multi? false},
 :map {:comma? false,
       :indent 0,
       :justify {:max-variance 40},
       :key-value-options
         {:arglists {:vector {:option-fn (fn
                                           ([] "wrap-arglists")
                                           ([opts n exprs]
                                            {:guide [:element-*]
                                             :map {:force-nl? true}
                                             :vector {:hang? true,
                                                      :wrap-multi? true}}))}}}},
 :pair {:indent 0},
 :set {:wrap-after-multi? false},
 :style [:respect-nl],
 :vector {:no-wrap-after #{"&"}, :wrap-after-multi? false},
 :width 120}

The only new thing is the value of :key-value-options in :map.  This causes this options map to only be used when formatting the values of the specified keys.  Some examples:
projects/zprint % ./zprintma-1.2.9  <cljfiles/i341a.clj
(defn my-fn-1
  "..."
  {:arglists '([obj mapping-fn]
               [obj mapping-fn {:keys [tempid entity-spec apply-tx-fn]
                                :as opts}])}
  ...)

(defn my-fn-2
  "..."
  {:arglists '([client db-name & {:keys [db-actions migrations-dir]
                                  :as options}])}
  ...)

projects/zprint % more cljfiles/i341r.clj
(defn my-fn-3
  "..."
  {:arglists '([client db-name & {:keys [db-actions migrations-dir] :as options} more args {:keys [stuff bother] :as keystuff} are here])}
                                  ...)

projects/zprint % ./zprintma-1.2.9  <cljfiles/i341r.clj
(defn my-fn-3
  "..."
  {:arglists '([client db-name & {:keys [db-actions migrations-dir]
                                  :as options}
                more args {:keys [stuff bother]
                           :as keystuff}
                are here])}
  ...)

I think this does largely what you are looking for.  If you get weird things with :no-wrap-after, let me know, and I'll see if it is something that I've fixed for 1.3.0.  More importantly, if this isn't what you were looking for, please let me know!  I have spent a good while trying to figure out how to get what you want.  It turns out that getting a multi-line thing (e.g., your maps) on the end of a line with other non-multi-line things isn't something that zprint will do.  I have used the guide to force that behavior.  It might be that I should try to implement that for regular zprint formatting, but nobody has ever asked for it before, so it hasn't come up.  That said, I can see why you like it.  Anyway, please let me know if this isn't what you wanted or you are unable to make your zprint do this.  Thanks!

In thinking more about this, I was completely mistaken about the :no-wrap-after issues and their cropping up in the formatting of your :arglists.  At least if you use the guide I supplied.  The :no-wrap-after capability only works in the code that normally wraps things.  The guides all use entirely different code where it would be really hard to predict if the next thing will fit on the line, and so there is no attempt to support :no-wrap-after in guides.  I don't think it will impact you, since you have a :width 120, but if it does I might be able figure out something.  Perhaps I could merge the :no-wrap-after thing with the next element on the line when processing a guide and then they would be processed together, and wrap or not together.  Anyway, see how what I gave you works before we worry about that.

authors: kkinnear marksto

repo: kkinnear/zprint


text:
Community styles for cond->

In the default styles, cond-> is formatted with :arg1-pair-body https://github.com/kkinnear/zprint/blob/ccfc04f1af44546095326e4e4d1acce641bffede/src/zprint/config.cljc#L295, in the :community styles :none-body https://github.com/kkinnear/zprint/blob/ccfc04f1af44546095326e4e4d1acce641bffede/src/zprint/config.cljc#L526 is used.
According to the style-guide (https://github.com/bbatsov/clojure-style-guide#body-indentation), I think :arg1-pair-body would be more appropriate for the :community styles as well.
Not a big deal, since we can just revert it back to the default setting, but wanted to ask for the intention here.

Available in 0.4.8.

source: gharchive/issue

authors: kkinnear kommen

license: mit

license_type: permissive

license_source: bigquery


text:
fix: fixed foundry version to a working one

Latest foundry nightly is bugged with WETH9. Fix the version to the latest working one.

As said in comments
This is only a temporary fix waiting on https://github.com/foundry-rs/foundry/issues/9349 to be resolved

source: gharchive/pull-request

authors: enitrat obatirou

repo: kkrt-labs/kakarot

license: MIT

license_source: github-api


text:
Fixed to work with PureScript 0.12

There seemed to be a few small breaking changes with PureScript 0.12.
I noticed in my application that used purescript-linear-algebra it wouldn't compile with the latest version of PureScript.
This is a fix to allow it to work with 0.12.

Thank you for the patch!
I will release new version today

authors: klangner logiclogue

repo: klangner/purescript-linear-algebra


text:
Gitolite integration with GitList

This pull request allows integration with Gitolite. It contains a fix for full relative path of nested repositories (based on #536 with my comments) which is critical for this. Since there is a chance that a user doesn't have access to any repository, I added catching NoRepositoryException to all Controllers so a user sees nice error message (not RuntimeException or a blank page).
To get list of accessible repos you have to write 2 simple scripts (see below). The first one gitolite-wrapper.sh is called from GitList itself and it calls the second one gitolite-perms.sh via sudo as gitolite user (so the web server user doesn't have ability to call gitolite command via sudo).
I included scripts in this PR.
Requirements

You have to setup a web server to perform authentification and pass username in $_SERVER['PHP_AUTH_USER'].
Usernames must correspond to those in gitolite.
You have to allow web server user to call gitolite-perms.sh via sudo as gitolite user and permit passing env variable GL_USER.

I hope this helps.

Can you please adapt your code to the PSR-2 standard?

@klaussilveira: I have adapted the code to PSR-2 and I also included wrapper scripts. If you merge this I will write a wiki how to setup this.

When do you paln to integrate this feature in the master ?

@Hologos as described in #739 I'm quite not sure if your changes should be in GitList, as the core of GitList should be minimalistic and only support the common needed features. In addition I don't prefer any sudo calls in webserver scripts, as they may be exploited easily, if the user didn't setup the environment carefully.
However, I'd love to hear your feedback in #739.

Is there somebody who can merge? The latest commit was on Aug 2017.

authors: Hologos alehaa klaussilveira welljsjs ycollet

repo: klaussilveira/gitlist


text:
fix: update rpc spec klay_nodeAddress and klay_resend

fix: update rpc spec klay_nodeAddress and klay_resend

LGTM

repo: klaytn/OpenSDK


text:
Request answers to some doubts about running the code process

Hello, excuse me. I would like to ask you a few questions.
First question: Running Python train_ When flow.py -- category car | chair | airplane, do I need to choose one of the car | chair | airplane options? Because I see in the code that one of the options is selected, rather than selecting all three at the same time.
Second question: train_ Flow.py, sample_ Flow.py, train_ Reflow. py, train_ Do I need to finish running the previous program before running the next program for these four programs?
Finally, may I ask if the train code needs to run 20000epoch, 10000epoch, 10000epoch, and 10000epoch respectively? I am running at a particularly slow speed, so I would like to ask if it is necessary to run so many epochs?
Looking forward to your reply and wishing you success in your work!

Thanks for being interested in our project.
For the first question, by default, you can choose one or just leave it blank. You can also make it a list to train all the classed in the list.
Second, yes, they are depend on the previous checkpoint so you need to run them one by one.
Final question, no, you can run it for a shorter epochs, for example 500-1000, I remember it is enough to see some reasonable results. 20000 is just for marching other works and getting a best number during evaluation.

Hello, after running 100epoch, I will generate the epoch_ Add 99.pth to sample_ When running 'parser. add_argument (' -- model ', default='./output/train_flow/2023-08-28-08-01-24/epoch_99. pth ', help=' path to model (to continue training) 'in flow.py, an error occurred as follows: What is the reason for this?
(wxpy38) wangxin@wangxin-IdeaCentre-GeekPro-17IAB:~/1_code/cvpr2023_PSF$ python sample_flow.py
Directory missing : ./data/ShapeNetCore.v2.PC15k/02691156/train
Traceback (most recent call last):
File "sample_flow.py", line 699, in
main()
File "sample_flow.py", line 618, in main
train_dataset, _ = get_dataset(opt.dataroot, opt.npoints, opt.category)
File "sample_flow.py", line 420, in get_dataset
tr_dataset = ShapeNet15kPointClouds(root_dir=dataroot,
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 250, in init
super(ShapeNet15kPointClouds, self).init(
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 100, in init
self.all_points = np.concatenate(self.all_points)  # (N, 15000, 3)
File "<array_function internals>", line 200, in concatenate
ValueError: need at least one array to concatenate

Hello, thank you for your enthusiastic answer earlier. After running the program 'train_flow. py' to the 99th epoch, my program stopped due to 'out of memory' and generated the weight 'epoch_99. pth'. Then, I added 'epoch_99. pth' to 'sample_flow. py' to train and run the program, but the following error occurred: What is the reason for this?
(wxpy38) wangxin@wangxin-IdeaCentre-GeekPro-17IAB:~/1_code/cvpr2023_PSF$ python sample_flow.py
Directory missing : ./data/ShapeNetCore.v2.PC15k/02691156/train
Traceback (most recent call last):
File "sample_flow.py", line 699, in
main()
File "sample_flow.py", line 618, in main
train_dataset, _ = get_dataset(opt.dataroot, opt.npoints, opt.category)
File "sample_flow.py", line 420, in get_dataset
tr_dataset = ShapeNet15kPointClouds(root_dir=dataroot,
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 250, in init
super(ShapeNet15kPointClouds, self).init(
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 100, in init
self.all_points = np.concatenate(self.all_points) # (N, 15000, 3)
File "<array_function internals>", line 200, in concatenate
ValueError: need at least one array to concatenate

Hi, I think this mainly because the data directory is set in a wrong way. Like the error message said: Directory missing : ./data/ShapeNetCore.v2.PC15k/02691156/train
in fact, sample step does not need a data input, but I reuse some of the code, so please at least set a valid dataset directory( maybe same as train_flow) then it should be ok.

I initially forgot to change the location of the dataset, but after correcting the dataset path in 'sample_flow. py', I still reported the same error as before. Can you guide me?
(wxpy38) wangxin@wangxin-IdeaCentre-GeekPro-17IAB:~/1_code/cvpr2023_PSF$ python sample_flow.py
Directory missing : ./datasets/ShapeNetCore.v2.PC15k/ShapeNetCore.v2.PC15k/02691156/train
Traceback (most recent call last):
File "sample_flow.py", line 699, in
main()
File "sample_flow.py", line 618, in main
train_dataset, _ = get_dataset(opt.dataroot, opt.npoints, opt.category)
File "sample_flow.py", line 420, in get_dataset
tr_dataset = ShapeNet15kPointClouds(root_dir=dataroot,
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 250, in init
super(ShapeNet15kPointClouds, self).init(
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 100, in init
self.all_points = np.concatenate(self.all_points)  # (N, 15000, 3)
File "<array_function internals>", line 200, in concatenate
ValueError: need at least one array to concatenate

I still see the error message
Directory missing : ./datasets/ShapeNetCore.v2.PC15k/ShapeNetCore.v2.PC15k/02691156/train.
could you have a double check for this directory?

authors: klightz wangxin-fighting

repo: klightz/PSF


text:
fix: close cache file

Standard checks

Unit tests: Any special considerations?
Docs: Do we need to update any docs, internal or public?
Backwards compatibility: Will this break existing apps? If so, what would be the extra work required to keep them working?

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

authors: CLAassistant testwill

repo: klothoplatform/klotho


text:
Error when trying to get the performance benchmarking of MySQL 8.0.28 community edition on Windows 11

Describe the Issue (Bug/Feature)
Bug: When the example command ./build/install/sbk/bin/sbk -class mysql  -size 100 -writers 1 -seconds 60 (as described in https://github.com/kmgowda/SBK/blob/master/driver-mysql/README.md) is executed in Git Bash in the root directory of this project or if the command  ./build/install/sbk/bin/sbk -class jdbc  -driver com.mysql.jdbc.Driver -url jdbc:mysql://localhost:3306/social -user root -password root  -table kmg_2 -size 100 -writers 1 -seconds 60(as described in https://github.com/kmgowda/SBK/blob/master/driver-jdbc/README.md#jdbc-with-mysql) is executed in the root directory of this project, an error due to main class caused by ClassNotFoundException occurs.
To Reproduce
Steps to reproduce the behavior:

Run the command ./build/install/sbk/bin/sbk -class mysql  -size 100 -writers 1 -seconds 60  in the root directory of this project or run the command ./build/install/sbk/bin/sbk -class jdbc  -driver com.mysql.jdbc.Driver -url jdbc:mysql://localhost:3306/social -user root -password root  -table kmg_2 -size 100 -writers 1 -seconds 60 in the root directory of this project.
See error.

Expected behavior
The expected behavior is that the performance benchmarking results of MySQL should be displayed.
Additional context

The error says:
Error: Could not find or load main class io.sbk.main.SbkMain
Caused by: java.lang.ClassNotFoundException: io.sbk.main.SbkMain

The same error occurs when running the command ./build/install/sbk-mysql/bin/sbk-mysql -class mysql  -size 100 -writers 1 -seconds 60  in the driver-mysql directory of this project or running the command ./build/install/sbk-jdbc/bin/sbk-jdbc -class jdbc  -driver com.mysql.jdbc.Driver -url jdbc:mysql://localhost:3306/social -user root -password root  -table kmg_2 -size 100 -writers 1 -seconds 60 in the driver-jdbc directory of this project.

My system information is attached below:

OS Name: Microsoft Windows 11 Home Single Language
Version: 10.0.22000 Build 22000

@sushnag22 This bug is not reproducible ; I am able to run file system benchmarking on windows 11

@sushnag22 see the results on windows 11: https://github.com/kmgowda/SBK/issues/316#issuecomment-1072441755

I'll recheck it and let you know sir.

Yes sir, It's working. I tried using command prompt and it's working fine, I'm not sure why it didn't work on the other day when I was using git bash.

repo: kmgowda/SBK


text:
packet.toBuffer() undefined is not a function

I can't get example/services.js to work on node v0.11.14.
$ node examples/service.js
xxx/node_modules/mdns-js/lib/advertisement.js:15
var buf = packet.toBuffer();
^
TypeError: undefined is not a function
at Object.internal.sendDNSPacket (xxx/node_modules/mdns-js/lib/advertisement.js:15:20)
at internal.probeAndAdvertise (xxx/node_modules/mdns-js/lib/advertisement.js:196:16)
at Advertisement.start (xxx/node_modules/mdns-js/lib/advertisement.js:258:30)
at Object. (xxx/node_modules/mdns-js/examples/service.js:10:9)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:124:16)

I don't get it under v0.12 but a lot of other things have happened in the meantime.
I will close this issue in a couple of days if I don't see it again or get more feedback.
Thanks.

@kmpm I'm no longer using this module so can't confirm. Thanks for looking into it.

authors: kmpm siboulet

repo: kmpm/node-mdns-js


text:
v4.0.0

https://github.com/kmyk/online-judge-verify-helper/pull/127 replace oj-verify bundle subcommand with oj-bundle command
https://github.com/kmyk/online-judge-verify-helper/pull/126 make .verify-helper/.gitignore
https://github.com/kmyk/online-judge-verify-helper/pull/125 add python_requires='>=3.6'

雑に merge ボタン押したけどだめやんけ

反省して branch protection の設定をしています。許して

branch protection すると auto push が動かないぽい？

repo: kmyk/online-judge-verify-helper


text:
Use the new knative-sandbox/reconciler-test framework

Changes

:broom: Use the new reconciler-test framework for e2e tests.
:wastebasket: Drop rigging.

/kind cleanup
Release Note

NONE

/lgtm
/approve

repo: knative-sandbox/discovery


text:
chore: update manifest.yamls

Changes

:bug: In a couple of cases, the invoke parameter was missing.
:bug: There was an outdated use of a typescript buildpack in the typescript/cloudevent templates.

Signed-off-by: Lance Ball lball@redhat.com
/kind bug
Release Note
Fixes missing `cloudevent` invocation format for Node.js, SpringBoot and Rust CloudEvent templates

@lance were are the TS changes?

/hold

@matejvasek here: https://github.com/knative-sandbox/kn-plugin-func/pull/846/commits/462696f07a68787d9e139fca5ef73b9d7c2eec5c

fixup: I should set VSCode to autosave on focus change

I learned obsessively press CTRL+S everywhere :smile:

/unhold

/lgtm

authors: lance matejvasek

repo: knative-sandbox/kn-plugin-func


text:
Add validation to controller for Task CRD

Expected Behavior
When someone creates a Task in a k8s cluster (e.g. with kubectl apply, the controller should make sure every field is valid.
This should include verifying as many fields as possible, e.g. verifying connectivity with any endpoints, if there are any references, verifying that those actually exist in the system, etc.
Task is defined here: https://github.com/knative/build-pipeline/blob/master/pkg/apis/pipeline/v1beta1/task_types.go
Any additional fields included should cause a failure (e.g. if a typo is made when defining a known field).
Actual Behavior
Some basic validation is applied, e.g. that required fields are present and that fields are in the correct format (e.g. string vs. int), but that's it.
Steps to Reproduce the Problem

Deploy the Pipeline CRDs to your k8s cluster
Create an instance that has invalid fields, e.g. a malformed URL or a typo in one of the fields.
Apply the instance with kubectl apply -f and notice that the controller does not complain

Additional Info
Blocked by #19

/assign @dlorenc
@dlorenc btw you should also take a look at #83 before you get started, where @pivotal-nader-ziada is adding skeleton webhooks

Closing this for now. We can always add more validation, but we have the basics.

authors: bobcatfish dlorenc

repo: knative/build-pipeline


text:
Format markdown

Produced via: prettier --write --prose-wrap=always $(find -name '*.md' | grep -v vendor | grep -v .github)

/close
Already taken care in https://github.com/knative/build-pipeline/pull/349
cc @mattmoor we should update the bot to open a new PR only if there is not a existing one :angel:

authors: mattmoor-sockpuppet vdemeester


text:
Remove kafka src channel

Fixes #

Proposed Changes

Release Note

Docs

/lgtm
/hold for another approval

/unhold

authors: matzew pierDipi slinkydeveloper

repo: knative/eventing-contrib


text:
fix misspelling functionallity -> functionality

Changes

/kind

Fixes #

Release Note

Docs

/retest

/ok-to-test

/lgtm
/approve

authors: Abirdcfly chizhg julz

repo: knative/hack


text:
Track the Contour release branch.

Also adds Contour to the set of things we bump in our upgrades.

/lgtm

authors: andrew-su mattmoor

repo: knative/net-contour


text:
[master] Auto-update dependencies

Produced via:
./hack/update-deps.sh --upgrade && ./hack/update-codegen.sh
/assign n3wscott vagababov
/cc n3wscott vagababov

/lgm

/lgtm

authors: antoineco mattmoor

repo: knative/pkg


text:
Freezes Entire Ubuntu Server

Overview
I have a Typescript NestJS application that uses

"@nestjs/core": "^9.0.0"
"knex": "^2.4.2"
"nest-knexjs": "^0.0.13"
"pg": "^8.10.0"

I have two different Ubuntu 20.04.3 servers both running PostgreSQL 13.
I can run select queries with no problem--such as
  public async getStudios(): Promise<string[]> {
    const studios: Array<{ id: string }> = await this.knex
      .select("id")
      .from<{ id: string }>("yoga.studio");
    return studios.map((studio: { id: string }) => studio.id);
  }

However, when attempting to do an insert--such as
public async create(scraperId: string): Promise<string> {
    return this.knex
      .table("public.scrape_run")
      .insert({ scraper_id: scraperId })
      .returning<string>("id");
  }

Knex Debug
{
  method: 'insert',
  options: {},
  timeout: false,
  cancelOnTimeout: false,
  bindings: [ '2e8ff241-a7d3-48a5-9d50-03d538d6078a' ],
  __knexQueryUid: 'aOE0bBVyq-vSc3dlcbneh',
  sql: 'insert into "public"."scrape_run" ("scraper_id") values (?) returning "id"',
  returning: 'id'
}

The entire Ubuntu server freezes.

Postgres becomes completely unresponsive
htop's uptime freezes and becomes completely unresponsive.
Can't ssh into the machine.

The only thing in postgres logs i have
2023-04-06 21:59:50.079 UTC [985] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-04-06 21:59:50.080 UTC [985] LOG:  listening on IPv6 address "::", port 5432
2023-04-06 21:59:50.084 UTC [985] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-04-06 21:59:50.115 UTC [1031] LOG:  database system was interrupted; last known up at 2023-04-06 21:55:16 UTC
2023-04-06 21:59:50.207 UTC [1031] LOG:  database system was not properly shut down; automatic recovery in progress
2023-04-06 21:59:50.212 UTC [1031] LOG:  redo starts at 9D/AEF03FE0
2023-04-06 21:59:50.212 UTC [1031] LOG:  invalid record length at 9D/AEF04030: wanted 24, got 0
2023-04-06 21:59:50.212 UTC [1031] LOG:  redo done at 9D/AEF03FE0
2023-04-06 21:59:50.628 UTC [985] LOG:  database system is ready to accept connections

My Knex config
export default function knexConfig(): DynamicModule {
  return KnexModule.forRoot({
    config: {
      client: "pg",
      useNullAsDefault: true,
      pool: {
        min: 1,
        max: 1
      },
      debug: true,
      connection: {
        host: dbConfig.host,
        port: dbConfig.port,
        database: dbConfig.database,
        user: dbConfig.username,
        password: dbConfig.password
      }
    }
  });
}

Resolution: https://kb.vmware.com/s/article/2151480

repo: knex/knex


text:
How to change server on the fly

Hi,
In all the sample applications the PubSubClient is created and set up outside the setup function. However, in my application I need to be able to disconnect from it and connect to another server at will.
I would expect a global variable to hold the PubSubClient, then modify its properties on the fly.
Is it possible to do this? Keep in mind i'm rather new to c/c++.
thanks in advance for any pointers.

Never mind, I figured it out. For those interested in the same:
I can create the object globally like this:
WiFiClient wclient; PubSubClient PSclient(wclient);
Then I can use:
PSclient.disconnect(); and PSclient.set_server(mqttServer, mqttPort);

repo: knolleary/pubsubclient


text:
Connect to multiple mqtt servers?

I am connected to cloudmqtt server and everything works great. Can I also connect to a local server? I did not see an example for that

What do you mean by 'local'?
If it has an IP address, you can connect to it. Doesn't matter where it is physically as long as you can get to its IP address.

Thanks for the reply.
I’d like to send messages from the esp32 to a server on my “local” lan as
well as to a server on the Internet.
I suppose I could  send everything to the local server and then forward
those messages to the internet server.
On Tue, Jul 2, 2019 at 10:11 knolleary notifications@github.com wrote:

What do you mean by 'local'?
If it has an IP address, you can connect to it. Doesn't matter where it is
physically as long as you can get to its IP address.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/knolleary/pubsubclient/issues/636?email_source=notifications&email_token=AHZMZRUBLODWK4DQH6HOSVTP5NHZFA5CNFSM4H4XNLQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZBG6KI#issuecomment-507670313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHZMZRT345BZWYR5WPSUEGDP5NHZFANCNFSM4H4XNLQQ
.

Create two PubSubClient instances and two WiFiClients. Do not share a WiFiClient instance between multiple PubSubClients.

authors: finnishcolumbia gazialankus knolleary


text:
[Proposal] Merge Xchange project with bitrich-info project

Hello,
i would like to propose the merge of those 2 projects. Bitrich-info is a very good project which i believe it is a must for every developer that wants real-time prices and response time. That merge will create a huge amount of value for everyone. Right now most of us, that we use this library on our projects, have a major issue with rate limits. This will help us eliminate most of them just by using websockets instead of the classic REST calls, as every exchange suggest to do if the offer such. What do you think?

Did you know that Bitrich-info originally started as XChange code? XChange used to support streaming as well, but we peeled out the streaming part to form Bitrich-info because it was just way too much to maintain in one project. Plus the streaming dependencies were not at all robust back then, and it was a real headache.

Thanks for the response @timmolter . I didn't know that. Do you believe that now it is much simpler with the dependencies? Is the project more mature now? Thanks

I honestly do not know because I haven't been following that project. From a quick look however it looks waaaay more advanced now than it was before and many more exchanges are supported.  I started doing monthly XChange releases specifically for the bitrich-info project meaning the two projects are very closely coupled. It looks like they are looking for a maintainer right now, which might be something you'd be interested in.

@timmolter i have already talked with today maintainers about becoming one, but because i don't have the experience or the knowledge they have, i am not ready for it yet. It is a shame that bitrich project don't have the maintainers it deserves. That is why i propose a merge. More people will work for the same project and PRs will be merge much faster.

Merging the two projects won't change much in the matter how much work is being devoted to them. Most ppl contribute only the modules / features they use. That said refactoring done to xchange-core would be easier to keep in sync with streams.
If an eventual merge was supposed to happen I think streaming features should still be kept in a separate module. For example you would have xchange-binance and xchange-binance-stream. This is because they usually have additional dependencies like websockets that may be undesired by people that don't need streams - and lots of use cases don't need them.

The thing that will change is how fast the PR will be merge.This is the pain in the ass, on the bitrich-info project. If we merge the projects this will change. I totally agree with your second point, i also was thinking something like this, definitely separate modules. So what do you thing?

I can do all the work of merging.

Have you had PRs there that aren't getting any attention?
I personally cannot dedicate any time to reviewing streaming PRs or anything related to the streaming API.

@walec51 or anyone here, are you willing to review streaming PRs? Right now on bitrich project there are only 2 persons (i am not sure) which review and merge. I can review them, but i cannot merge them because i don't have the privilege.

Have you had PRs there that aren't getting any attention?
I personally cannot dedicate any time to reviewing streaming PRs or anything related to the streaming API.

There are many PRs which will hang there for days. I totally understand that you don't have that extra time to do it. At least there will not be any version issues with the merge.  I am more than happy to review streaming PRs, although i am not expert or very good. I am dedicating a lot of my time on these 2 projects, so i will definitely be a reviewer.

I don't use streaming currently in my projects so no, I will not review streaming PRs.
I'm against merging projects until someone that actively maintains bitrich comes here personally and says that he thinks that merging is a good idea and that he will continue maintaining  that code after the merge.
@makarid if you want to be that person then please gain some experience first by contributing to the bitrich project in its current form.

I don't use streaming currently in my projects so no, I will not review streaming PRs.
I'm against merging projects until someone that actively maintains bitrich comes here personally and says that he thinks that merging is a good idea and that he will continue maintaining that code after the merge.
@makarid if you want to be that person then please gain some experience first by contributing to the bitrich project in its current form. After some time of working together they should give you contributor status.

@badgerwithagun what do you thing about the merging? Will you continue to contribute to the bitrich project if we make the merge?

Merging the two projects would make a huge difference to me and others, I'm sure.  I can't be the only one that has to maintain synchronised forks of both libraries to keep a production app stable. There are some differences in project structure which would need to be fixed to get the streaming project ready for a merge, but that's all achievable if someone has the time.
I would continue to review & merge PRs after a merge, but like most contributors to the xchange-stream project, I don't use all exchanges.  I won't be able to review BitMex PRs, for example (which covers most of the long, outstanding unreviewed PRs).
I certainly can't guarantee long-term support (who can? Including @timmolter, I'm sure!), but have no plans to stop my involvement in the near future.  However, to split hairs: I'm not a maintainer; I'm just a collaborator.  @dozd is the only (semi) active maintainer.
Broadly: I'm in favour of it, but the challenge xchange-stream has is a lack of committed maintainers, and that won't be immediately solved by merging projects (at least immediately - I suspect more people would get involved pretty quickly if streaming were more obviously available).

Thank you @badgerwithagun for your input.I would love to be a maintainer when i am fit. So @timmolter and @walec51 what do think?

I remember when Xchange library supported streaming and also when and why they dropped it. Their implementation was not good mainly due to bad design choices as well as bad technologies for the streaming implementation. When I started the implementation of the streaming interfaces, usage of rxjava was a crucial point to make it as simple as possible and solved a lot of bad choices from the past.
But as I am in favor of a loosely coupled architecture I think these two libraries benefits from their separation. Modular approach is much more easier to maintain for a long term. Maybe I don't see that but what would be the benefits of merging them together? If you need the basics, use Xchange. If you need streaming, add Xchange-stream on top of it. Big all-in-one libraries are obsolete.
The bad thing is that I'm not using any of these two libraries anymore and I don't have a time (and energy) to maintain xhcnage-stream just without any of my need. But I do not think that merging with Xchange will solve this problem. But maybe I am wrong.
Anyway, if there will be an opinion that these two libraries should be merged, I'm happy to assist you if needed.

@dozd the main issue with bitrich project is the luck of maintainers as you correctly told us. I have a lot of code in my local branch which i cannot merge because of that. But the biggest pain in the ass is the versioning issue. Bitrich project depend on Xchange but cannot keep up with the versioning of Xchange. Without Xchange bitrich cannot exists and that is way it is crucial to have always the latest version of Xchange on bitrich project.This is not what is happening now. For example, lets say that i want to fix an issue on Bitrich library. After searching on the code i found a solution, but this solution needs to add a feature on Xchange library first. So i make the PR to Xchange and they merge. But because bitrich doesn't use the latest version on Xchange,i cannot use the new feature. I need to wait for the new release in order to see the new Xchange feature on Bitrich library. This is at minimum frustration. I believe that the merge will at least fix that issue and maybe will attract more devs on streaming version. There are developers from exchanges that support Xchange with new implementation from their APIs but don't do it for bitrich because of that.

xchange-stream suffers from a lack of attention.  People find XChange, it does what they need, done.  If streaming were a more first-class citizen, more people might use it. More users means more interest, more eyes on the problem, more PRs, more collaborators, more predictable release cycle.  I don't see any element of this that stands as a benefit for the XChange project though; it's purely to the benefit of xchange-stream.  I wouldn't try and pretend otherwise!
I fully understand if others want to maintain the separation, but for the sake of argument if nothing else, I will try and make an architectural case.
In principle, @dozd is absolutely right; smaller, focused libraries are the "right" way to work, but it's important to apply appropriate domain-driven-design if you're going to enforce modularity, and having worked in parallel on both XChange and xchange-stream, it feels to me that "not streaming" and "streaming" are not the bounded contexts; the exchanges are.
It would make more sense to me if there were:

A clear "core xchange api"
A clear "core streaming api" which builds on the core API
Exchange A (implements core and streaming API)
Exchange B (implements only core API)
Exchange C...

In an ideal world, each would be a standalone project (for the very reasons @dozd describes - and because each exchange implementation is likely to have completely different userbases).
However, of course, XChange and xchange-stream are both monorepos covering all the different supported exchanges - the reason being that it allows the API to remain loose because developers can change it at any time by updating all the exchange implementations at the same time.  To move away from this to individual projects would mean being much more careful with API design and rollout and probably slow down a lot of people.
One could argue that in a mature project that would be the right thing to do anyway; by splitting out the exchange implementations it would force the core project to apply better, more sustainable API designs - but I don't think this is the kind of project in which such rigour is realistic. It survives on lots of small, disconnected, ad-hoc enhancements, not longer-running design projects.
So - the monorepo has enormous benefit in practice for most people - and I think for those of us that use xchange-stream, that benefit would be double if it covered both libraries.  In practice, xchange-stream is regularly broken by XChange API changes and this is every bit as much of a pain as it would be if XChange Exchange A and XChange Exchange B were in separate projects from the XChange core.  They would benefit from being in one library for the same reason.
Anyway, I fully understand either way, but that's the best case I can make.

Thank you all for taking part in this discussion.
After reading it I came to the conclusion that there are only two small benefits to merging:

one could propose changes / fixes to xchange-core and streaming functionality in one PR
streaming functionality would get more attention from xchanges users

This will not solve the problem of lack of maintainers because if someone really needs streaming (to the point he would be willing to contribute to make it work) then he will have no problem finding out that Bitrich-info exists and creating a PR there. The only inconvenience is that if some changes in xchange-core are required then he has to have two PRs instead of one.
Secondly I still oppose creating modules suggested by @badgerwithagun that will force me to import streaming dependencies for a given exchange. Modules do not only separate business domains, they are also technical artefacts. If I don't use streaming then I don't want to be forced to import RxJava and other libraries to integrate with Binance for example.
If this merge was supposed to happen then proper dependencies should look like this:

If this type of module separation was to be kept then I'm personally neither in favour nor against of this merge. This is simply because my use cased do not require it, I just don't want it to get in my way ;)

@walec51 I was not talking about modules/JARs; I was talking about projects. Absolutely the modules WITHIN the project should be as you describe. My point was that there is a good reason that Binance is in the same project as the API: they often change together. The same logic applies to the streaming API and the streaming implementations: they often change at the same time as the XChange API.

Thank you all for the inputs. Can we vote in order to see how many we are in favor and against?
I am in favor of a merge.

Just one question. Why you don't want to use websockets in order to get realtime market data? It is blazing fast and you solve the rate limit problem also. I really cannot understand that.

As @walec51 pointed out it's critical that users don't need to import streaming libs if using the polling API. His proposed module separation makes this a non issue though.
I think if xchange-stream was actually actively developed and maintained and synced with xchange regularly, this merger wouldn't be necessary, but a @dozd said he doesn't have the time and energy to dedicate to it. The issue is less of a technical one and more of a practical one. Therefore a merge would definitely benefit those users who really want to use the xchange-stream project as a critical part of their projects because changes will get merged faster and smoother. So for the benefit of those users (which I personally am not) this merger does make sense. Therefore my vote is to do the merge.
I would hesitate to vote "yes" if @dozd would be upset but it seems he's ok with a merge:

Anyway, if there will be an opinion that these two libraries should be merged, I'm happy to assist you if needed.

If we decide yes, I'm quite happy to do a bunch of the work needed. I'd need @dozd's help to get a bunch of laggard PRs pushed through first and a final release done and would aim to conduct the merge in a series of smaller PRs to make it manageable.
I think it'll be important to work on maintaining reversibility throughout and being disciplined enough to resist the urge to do any refactoring whatsoever.

@makarid many of us don't you web sockets because getting data via a request - response method is much easier and less error prone then caching data from a stream. For example if I getOrderbook after a placeOrder I know this order book reflects it state after my orders ware matched. If I have a cache asynchronously build from a stream I have no way of telling did the events representing my order get applied already or nor.

@walec51 method is much easier and less error prone - that's because you have probably not seen my stream implementation with rxJava :-).
@timmolter You know, if the merge makes a better open source project, that's the whole reason of the contribution to open source. No reason to be upset. Our apache 2 is compatible with your MIT so everything's OK.
@badgerwithagun i have zero to minus one time because of a work on this game... so I hope it will OK. But I will surely find some spare (from minus one to minus two there is some nice negative space here)

Hi @timmolter & @walec51. We're slowly working towards cleaning up xchange-stream for the merge. The current plan is:

Clear outstanding pull requests
Clear compiler warnings
Add coveo-fmt and format the code to match XChange
Rename the Maven modules to fit the naming patterns discussed above
Create merge PR

The merge PR will be too big to usefully review in one go. Are we happy to get it merged and go incrementally from there?

I'm strongly in favor of merging the two projects since I use both streaming and REST calls, and syncing XChange and XChange-stream versions is painful.
For me streaming is really helping, for the both fresh data but and for the API calls restrictions we have on a lot of exchanges. Some exchanges give much higher api private calls limits for like placing orders with websocket: for example bitfinex which give close to infinite place/cancel limit, and only allows something like 1/sec with rest, not the exact numbers, but the difference is huge. All of the exchanges strongly encourage users to use the streaming api too.

@cymp have no fear; that seems to be the general conclusion too.  It will happen.  If you'd like to help, clearing compiler warnings on xchange-stream would be very welcome!

BTW: try to research how to do the "merge" of these projects correctly in terms of git. It would be very beneficial not to loose the commit history for the future development.
Doing it through the regular pull request by copying the files would delete this valuable info. You surely know the situation: "Why this line of code is here?" I'll check the blame lines. Ah, it was just committed with the another thousands of lines :).

@dozd indeed. I was thinking on this yesterday!

sounds good!

I just saw this thread, and tend to agree with a merge, as I too often have to make changes in both XChange and XStream, and managing the dependencies is painful and thawrt with risks.  My only concern is that XChange feels slower paced, concentrating on breadth of exchanges over depth of functionality, but working with one snapshot must be better than having two,

One other thing to note: I feel that due to the nature of REST calls, and their rate limits, XChange is much less concerned about GC, and for me that is a problem since I subscribe to multiple exchanges and feeds simultaneously.

I've made a provisionary/experimental PR #3436 which is a draft attempt at merging the two projects. It's been marked at DO NOT MERGE because the green light has not been fully given by all involved parties, so this is a draft of what one possible future might look like available to brave souls who wish to test the two projects building and testing together.
There remain a few open PR's in XChange-stream which should still be merged, and I would love to see some discussion regarding the merge choices made, so as to better inform what an actual merge would look like in the future when both projects are ready.

Not sure if this is relevant, but is the streaming part of this project still looking for maintainers? If so what is the general process to bring someone on as such?

I'd be happy to take on a maintainer for the streaming part.

FYI, I just added @badgerwithagun

@timmolter sounds good, I want to go through a few more reviews maybe some that are more invasive and if you guys are comfortable with that I would like to become one.

also I figure this thread can be closed right?

authors: TSavo badgerwithagun cymp dozd earce makarid mdvx timmolter walec51

repo: knowm/XChange


text:
Multiple chart style in one chart?

Is it possible to draw an OHLC chart and a line chart into the same chart area?

@timmolter
Same as issue #250 feature.
PR #430 has been implemented.

repo: knowm/XChart


text:
Adding unit test for input actions.

Adding unit test for input actions.

Coverage decreased (-0.4%) to 60.789% when pulling 6aa1e205725171988449faa0d7938dfde339f21e on ranch:test/input into 320373de1a444785ac91a1df0afa67dbc810ac7c on knq:master.

Coverage increased (+0.2%) to 61.446% when pulling ca1ae9b64049d59e28975d02f2b7957cf55cb879 on ranch:test/input into 320373de1a444785ac91a1df0afa67dbc810ac7c on knq:master.

Coverage increased (+0.2%) to 61.446% when pulling ca1ae9b64049d59e28975d02f2b7957cf55cb879 on ranch:test/input into 320373de1a444785ac91a1df0afa67dbc810ac7c on knq:master.

Coverage increased (+0.4%) to 61.665% when pulling 3a264ed3ff581574df8613efd10d34981f2bc34d on ranch:test/input into 320373de1a444785ac91a1df0afa67dbc810ac7c on knq:master.

authors: coveralls ranch

repo: knq/chromedp


text:
build failed

=== BUILD TARGET flutter_google_ad_manager OF PROJECT Pods WITH CONFIGURATION Release ===
/Users/fun/Documents/flutter/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_google_ad_manager-0.9.0/ios/Classes/FlutterGoogleAdManagerPlugin.m:2:9: fatal error:
'flutter_google_ad_manager/flutter_google_ad_manager-Swift.h' file not found
#import <flutter_google_ad_manager/flutter_google_ad_manager-Swift.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
=== BUILD TARGET flutter_google_ad_manager OF PROJECT Pods WITH CONFIGURATION Release ===
error: the following command failed with exit code 1 but produced no further output
CompileC
/Users/fun/Library/Developer/Xcode/DerivedData/Runner-dwjxktxyzlqgxkcekrcauicmhtfl/Build/Intermediates.noindex/Pods.build/Release-iphoneos/flutter_google_ad_manager.build/Obje
cts-normal/arm64/FlutterGoogleAdManagerPlugin.o
/Users/fun/Documents/flutter/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_google_ad_manager-0.9.0/ios/Classes/FlutterGoogleAdManagerPlugin.m normal arm64 objective-c
com.apple.compilers.llvm.clang.1_0.compiler
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.2.1, on Mac OS X 10.14.3 18D109, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
✗ Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[!] iOS toolchain - develop for iOS devices (Xcode 10.3)
✗ libimobiledevice and ideviceinstaller are not installed. To install with Brew, run:
brew update
brew install --HEAD usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice
brew install ideviceinstaller
✗ ios-deploy out of date (1.9.4 is required). To upgrade with Brew:
brew upgrade ios-deploy
[✓] Android Studio (version 3.2)
[✓] VS Code (version 1.37.0)
[✓] Connected device (1 available)
! Doctor found issues in 2 categories.

rm -rf ios
flutter create -i swift .


text:
Return error 400 instead of 500 on invalid path part

Current behaviour:
curl corp.short.cm/%AF returns 500 Internal Server Error
Expected:
curl corp.short.cm/%AF returns 400 Invalid request
I'm running a link shortener service and user put different combinations in path part, some of them are valid, some of them - not. This case I sent is a client error and there is no need to raise an exception here

Sorry, wrong module

repo: koajs/koa


text:
fix: include the source in the packages

This has several benefits:

Allows directly importing the source files, that could resolve the issues with server-side rendering with various build systems
Can result in more optimized code as the source file is directly built by the build tool (better tree shaking or more modern syntax)
Compatibility with new package registries such as JSR that prefer TypeScript over JavaScript
In security conscious environments, the source files can be checked against GitHub and then used directly.

The import map change allows importing the source files. The top-level source entry is for some bundlers like Parcel that prefer the source files over the built files.

Thanks for the PR!

repo: kobaltedev/kobalte


text:
Fix Continuous Delivery GitHub Action

[ ] I added a CHANGELOG entry for this change.
[ ] I adjusted the corresponding documentation for this change.
[ ] I adjusted the values.yaml file and the documentation for all values.

Codecov Report

Merging #278 (b289021) into main (20acf81) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #278   +/-   ##
=======================================
  Coverage   42.68%   42.68%
=======================================
  Files          93       93
  Lines        7926     7926
=======================================
  Hits         3383     3383
  Misses       4506     4506
  Partials       37       37

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 20acf81...b289021. Read the comment docs.

Codecov Report

Merging #278 (b289021) into main (20acf81) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #278   +/-   ##
=======================================
  Coverage   42.68%   42.68%
=======================================
  Files          93       93
  Lines        7926     7926
=======================================
  Hits         3383     3383
  Misses       4506     4506
  Partials       37       37

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 20acf81...b289021. Read the comment docs.

authors: codecov-commenter ricoberger

repo: kobsio/kobs


text:
Annoying warning on Transfer

Every time I load transfer with an address like https://kodadot.xyz/transfer/?target=HcEvTkvAPYEEGEndFV9sMmS3P83jdtwhwZq37GfdzA3mLrL it this pops up
Probably it would be a harder one.

@yangwao I'll do this

I haven't seen it while

Looks like it was closed by https://github.com/kodadot/nft-gallery/pull/1263

authors: prachi00 vikiival yangwao

repo: kodadot/nft-gallery


text:
Having beta channel / contextual deployments for KodaDot

Think about how we can achieve have a beta channel where we can test some new features and have them battle-tested till they hit mainstream exposure.
Thinking aloud about the switch button which by default is off and once enabled, we can start enabling features.

having json, where you can enable/disable accessibility for new features for mainstream users
probably will be always on for beta?
having a survey, where can collect feedback probably, feedback channel on discord, is good but it could be messy, probably direct people straight to the github, but non-tech savvy having some tally form?
have a beta-testers audience
have proper way to have great and rich reports about bugs, critical

First feature we can start testing out with #753

Can we set some specific ENV variables per branch?

Apparently there is context env https://stackoverflow.com/questions/49720743/branch-specific-environment-variables-on-netlify
ref

https://docs.netlify.com/configure-builds/environment-variables/
https://www.netlify.com/blog/2020/05/21/localize-your-environment-variables-by-context-with-build-plugins/
https://docs.netlify.com/site-deploys/overview/#deploy-contexts

recall plugin which can set env based on branch prefix i.e.
in theory it might works 😄

Installed https://github.com/cball/netlify-plugin-contextual-env#readme

Regarding feature toggling, you might want to check launchdarkly

Memo, we have https://beta.kodadot.xyz meanwhile

authors: rhaicode vikiival yangwao


text:
fix: attach fall through attributes to teleport component

Thank you for your contribution to the Koda - Generative Art Marketplace.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

(please remove design and QA checks below if not needed)
Needs QA check

@kodadot/qa-guild please review

Context

[x] Closes #9661
[ ] Requires deployment <worker/stick/speck>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality

Optional

[ ] I've tested it at </ahp/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at Koda Ecosystem Telegram?

Screenshot 📸

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

@Jarsen136

@vikiival what are the next steps for claiming the bounty? Thanks!

pay 10 usd

Thank you @vikiival ! This is my first bounty. I hope to contribute more to the project 😄

pay 10 usd

😍 Perfect, I’ve sent the payout
💵 $10 @ 6.19 USD/DOT ~ 1.616 $DOT
🧗 12b5bwwugf3CgWy58MPYQAX9wazLX1S71ghgZ4YPb6g4qbEP
🔗 0x99d28db3f8e396dd4252f1f7eeed2be096c3a65318f688a058514542dec2c06b
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

authors: AnmolBansalDEV vikiival


text:
Creative minting with GPT-3

:truck: correct name for basic number input
:art: updated layout of simple mint
:zap: smart wrapper over Auth component
:zap: Labeled text is here <3
:tada: creative mint is here
:zap: creative mint is available under /creative
:construction: GPT3 API WIP
:tada: gpt-3 is here credits to @petersopko
:zap: tweaked loading for Labeled text
:zap: tweaked loading state for gpt
:zap: creative minting is available in the navbar

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[x] Feature
[x] Refactoring

What's new?

[ ] PR closes #<issue_number>
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[ ] My contribution builds clean without any errors or warnings
[ ] I've merged recent default branch -- main and I've no conflicts
[ ] I've tried to respect high code quality standards
[ ] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[ ] Fill up your KSM address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

https://deploy-preview-3080--koda-nuxt.netlify.app/rmrk/creative/

YOLO ?

authors: vikiival yangwao


text:
feat: add tooltip for expiration on offer table

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[x] Feature
[ ] Refactoring

What's new?

[x] PR closes #3639
[ ] Requires deployment <rubick/magick_issue>
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

https://user-images.githubusercontent.com/11361147/182155614-6b082128-24ab-4dd3-b708-d66c4ce2eff1.mov

@petersopko for now, I kind of hide the tooltip of the expiration date.

just one thing I've noticed, we're not showing timezone here (utc) so can we add that as well, please? I've checked how is it done in: https://deploy-preview-3642--koda-nuxt.netlify.app/sales and that looks more informative to me

Thank you for your contribution to the KodaDot NFT gallery. 👇 _ Let's make a quick check before the contribution.
PR type
* [ ]  Bugfix

* [x]  Feature

* [ ]  Refactoring

What's new?
* [x]  PR closes [expiration time detail tooltip #3639](https://github.com/kodadot/nft-gallery/issues/3639)

* [ ]  Requires deployment <rubick/magick_issue>

* [ ]  <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:
* [x]  My contribution builds **clean without any errors or warnings**

* [x]  I've merged recent default branch -- **main** and I've no conflicts

* [x]  I've tried to respect high code quality standards

* [x]  I've didn't break any original functionality

* [x]  I've posted a screenshot of demonstrated change in this PR

Optional
* [ ]  I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>

* [ ]  I've tested PR on mobile and everything seems works

* [ ]  I found edge cases

* [ ]  I've written some unit tests 🧪

Had issue bounty label?
* [x]  Fill up your KSM address: [Payout](https://beta.kodadot.xyz/transfer?target=DaWoVNNhBTdqJ5iPN3UcaLeamkPpJeGWdrs8LhvX9TQbadc)

Community participation
* [x]  [Are you at KodaDot Discord?](https://discord.gg/35hzy2dXXh)

Screenshot
* [x]  My fix has changed **something** on UI; a screenshot is best to understand changes for others.

Screen.Recording.2022-08-01.at.9.11.46.PM.mov

Hi, could you please load the screen recording again? It's not working, and it would be helpful to see it.

@KngZhi
https://deploy-preview-3641--koda-nuxt.netlify.app/bsx/gallery/10000001-0
here
it says expiration is 2 months, on hover it says November which would be like 3 months?

this is 2 months 30 days. @prachi00

pay 75 usd

😍 Perfect, I’ve sent the payout
💵 $75 @ 60.73 USD/KSM ~ 1.235 $KSM
🧗 HgpGWWmqrw8t6viwSy6LPcTVr2SuVPKWW5ArdNp2xCJY2U4
🔗 0x018b8eb9d61eadd0aad84edc676b2218cdb19ac1871af898ae4a7a8cf6ca84c5
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

authors: DeluneClaire KngZhi petersopko prachi00 yangwao


text:
🔧 MyOffer & OffersUserTable

ref #6726

@prury Notification pulse button is out of scope, the feature hasn't been implemented yet

showing Price(unit) here for me

@kodadot/code-review-guild any idea why I can't fetch chainSymbol on first load? (comes from useAssetsStore().fetchAssetList()) it work after HMR
For now I've hardcoded KSM value until I find a workaround

Changing this line of code could fix this issue. Please also check other places that use it.
// composables/useChain.ts
  const { symbol } = assets(tokenId.value)

Change to
// composables/useChain.ts
  const symbol = computed(() => assets(tokenId.value).symbol)

Changing this line of code could fix this issue. Please also check other places that use it.

Thanks it does work!

authors: Jarsen136 prury roiLeo


text:
fix: free mint stuck on the first step

PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context
free mint would get stuck on the first step after adding your email and pressing confirm
it wouldn't move to the next step (confirm email)
Needs QA check

@kodadot/qa-guild please review

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Screenshot 📸

[x] My fix has changed something on UI;

https://github.com/kodadot/nft-gallery/assets/44554284/f07666ad-0a83-438d-8e83-4f70dc848223
https://github.com/kodadot/nft-gallery/assets/44554284/1f6a0902-801e-4e45-8fae-a3533bd9edce

free mints will be somehow reused with farcaster so no need to check this one for now
great work @hassnian
Thanks!
pay 30 usd

😍 Perfect, I’ve sent the payout
💵 $30 @ 9.55 USD/DOT ~ 3.141 $DOT
🧗 16faLfsywwNATaEfbH2ah75dn6ZmctQWpMS5G4KFhbmj5hnD
🔗 0x1a0cd3a22b937a8ac1480de2c1e6dcee828abace10161143b6db7a6914129bf1
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

authors: hassnian yangwao


text:
Image repo.

Please don't use this issue. This is just an image repository of altair.

repo: kodefluence/altair


text:
The version "latest" couldn't be reached, there are no registered migrations.

Hello, I have a problem with migrations. When I trying to do migration I have an error. Also, migrations directory is empty.
/opt/app # php bin/console doctrine:migrations:migrate

 WARNING! You are about to execute a database migration that could result in schema changes and data loss. Are you sure you wish to continue? (yes/no) [yes]:
 > yes

 [ERROR] The version "latest" couldn't be reached, there are no registered migrations.

How I can resolve it?

Hello, are you using the 1.1.5 version ? The issue should be solved in this version.

Hello,
Have you been able to make it work ?

authors: GhOsTMZ benjaminjonard

repo: koillection/koillection


text:
PserverSRO Getötet

installation wont work
http://www.bilder-upload.eu/show.php?file=a8636d-1458603375.png

tested and works for me, can you post your composer.json?

{   "name": "kokspflanze/pserverCMS",   "description": "CMS for pServer",   "keywords": [     "framework",     "zf2",     "twig"   ],   "homepage": "https://github.com/kokspflanze/pserverCMSFull",   "require": {     "zendframework/Zend-developer-tools": "dev-master",     "kokspflanze/p-server-cms": "~0.1",     "zf-commons/zfc-twig": "dev-master",     "mabuzagu/pdo-dblib-module": "dev-master"   } }
im using debian 8

change it to that
{
  "name": "kokspflanze/pserverCMS",
  "description": "CMS for pServer",
  "keywords": [
    "framework",
    "zf2",
    "twig"
  ],
  "homepage": "https://github.com/kokspflanze/pserverCMSFull",
  "require": {
    "zendframework/Zend-developer-tools": "dev-master",
    "kokspflanze/p-server-cms": "~0.1",
    "zf-commons/zfc-twig": "dev-master",
    "mabuzagu/pdo-dblib-module": "dev-master",
    "kokspflanze/p-server-sro": "^0.3.0"
  }
}

than run php composer.phar update again

ok thx for help. now the modul is installed... but how to activate the features? i mean that u can see the job rankings and unstuck chars....?
i allready did the all steps shown in the instruction

but still wont show me job ranking on webpage

is there anything more to do?
Best regards

its a rights problem.
you have to add
https://github.com/kokspflanze/PServerSRO/blob/master/config/module.config.php#L9-L65
to this part
https://github.com/kokspflanze/pserverCMSFull/blob/master/config/autoload/bjyauthorize.global.php#L43-L194
see also https://github.com/bjyoungblood/BjyAuthorize/blob/master/docs/simple-example.md

i did what you said but it isnt working for me

i did what you said but it isnt working for me

i will create a guide for it,next days

i will create a guide for it,next days

@great4ever @crayon1337 was so nice and created a little guide https://github.com/kokspflanze/PServerSRO/pull/4/files
i will add some styles and check if smth is missing, than there should be a good basic guide for everyone =)

authors: Sybtek great4ever kokspflanze

repo: kokspflanze/PServerSRO


text:
Download by python

add download_data.py
more checks, should works on all platforms (i hope)

After this PR, i can switch on the data downloading in action, if we resolve the problem of downloading WPP2022_Demographic_Indicators_Medium.zip and pend-gdis-1960-2018-disasterlocations.csv

repo: koldunovn/climsight


text:
Fix/tidy README

Seems like you have to access the derivation via the build attribute now rather than the binary attribute
Fix one typo ("runnin" -> "running")
Remove trailing spaces (none were double-spaces for line breaks)

Thank you very much, @TMVector !

authors: TMVector kolloch


text:
READY FOR REVIEW - Quick fix for #5. Experimental support for Python 3.x.

You'll probably want to look this over carefully. I think most of the changes are pretty straightforward, but this PR includes an explicit assumption that input files are UTF-8 (or a subset). This may have been an implicit requirement already.
(tagging #5)

:+1:

@kolypto Any chance we can get this merged, or a similar PR?

@posita Could you maybe add Python 3.5 to the tox file too?

@zoidbergwill, done. Apologies for the delay.

Python 3 is support is now here. Thank you for your contribution!

authors: alissonmuller kolypto posita zoidbergwill


text:
Smart nonces

Contributor offers to license certain software (a “Contribution” or multiple
“Contributions”) to sewer, and sewer agrees to accept said Contributions,
under the terms of the MIT License.
Contributor understands and agrees that sewer shall have the irrevocable and perpetual right to make
and distribute copies of any Contribution, as well as to create and distribute collective works and
derivative works of any Contribution, under the MIT License.
What(What have you changed?)

Includes my minimal unittest.mock (also a separate PR because it's just a Good Idea).
Reapplies the requests wrapper and the nonce harvester built on top of that.
Adds an inelegant, but trivial, hack to the wrapper implementation that allows the existing mocked tests to pass.  (at least they pass locally for me).

Why(Why did you change it?)
To allow the wrappers to be merged - the nonce harvester is nice, but it only affects efficiency and saves many connections to the ACME endpoint.

The code will be back according to the New Plan sketched out in #152 - this had gotten a number of things stuck to it along the way.

repo: komuw/sewer


text:
static frame longer

What needs occurred
Show static frame longer
Check list

[ ] Code styles confirmed
[ ] Test confirmed

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (8a19302) 94.62% compared to head (d9d0bdd) 94.51%.

Files
Patch %
Lines

AnimatedWordCloud/Utils/Config.py
87.50%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##              dev      #64      +/-   ##
==========================================
- Coverage   94.62%   94.51%   -0.12%
==========================================
  Files          27       27
  Lines         633      656      +23
==========================================
+ Hits          599      620      +21
- Misses         34       36       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

In the beginning, the timestamp is "to_2012_to_2012". This is weird.

true

Enabled to configure the first time stamp

Enabled to configure the first time stamp

I prefer to 2012 to * to 2012.

OK


text:
check and fix possible dependencies security vulnerability

I got mail from GitHub to check our lib dependencies:
https://github.com/konfetti-app/konfetti-backend/network/dependencies

fixed in c4882fd7d1cb2f45460bf6232cf0aaa4c3e441ce

authors: piezzo rootzoll

repo: konfetti-app/konfetti-backend


text:
e2e: fix missing error forward

Signed-off-by: Francesco Ilario filario@redhat.com

/retest

/retest

Closed in favor of #194

repo: konflux-workspaces/workspaces


text:
#35 Change toolbar color in my schedule page.

Implemented #35

Awesome! I'll check it :+1:

LGTM! Many thanks!

authors: dkajiwara konifar


text:
merge from konsum-frontend-svelte

package.json

chore(deps): add ^10.6.2 remove ^10.6.0 (devDependencies.npm-pkgbuild)

:tada: This PR is included in version 1.31.18 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.31.18
GitHub release

Your semantic-release bot :package::rocket:

repo: konsumation/konsum-frontend-svelte


text:
bump dependencies

Applied mkpr on package.json
/tmp/mkpr.sh

:tada: This PR is included in version 6.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
v6.1.0
GitHub release

Your semantic-release bot :package::rocket:

repo: konsumation/konsum


text:
Ubuntu 14.04 Vagrant issue

Hi,
When trying to run the  kontena master vagrant create command on Ubuntu 14.04 by following the quick start guide, Vagrant always fails to initialize with:
$ kontena master vagrant create
Creating Vagrant machine kontena-master-white-shadow-98 ... \Vagrant failed to initialize at a very early stage:
Vagrant is attempting to interface with the UI in a way that requires
a TTY. Most actions in Vagrant that require a TTY have configuration
switches to disable this requirement. Please do that or run Vagrant
with TTY.
done
Waiting for Kontena-master-white-shadow-98 to start...
This is using Virtualbox 4.3 from the Virtualbox repos, Ruby 2.2.3 via rbenv (the Ruby portion of this: https://gorails.com/setup/ubuntu/14.04), and I've tried with Vagrant from both the Ubuntu repository and via the Vagrant package (1.7.4). Vagrant does work on it's own, but kontena still can't create the master via Vagrant.

I managed to get it working by running the vagrant init command again. If I write up a step by step for Ubuntu 14.04 where should that go? Thanks!

Hi,
Good to hear you've got your problem solved. It would be great to have a step by step guide, we could publish it for example on our blog. Would that be okay?

Sure, the master appears okay and they can be created and destroyed but when I spin up nodes they won't connect to the master so I probably need to review the steps at least once or people will end up with happily running masters but no nodes to connect to! ;-)
Is there an official list of versions of Virtualbox, Ruby, and Vagrant that are recommended? Thanks!

I don't think there is really an official list for those.. for Ruby >= 2.0 version should be good. Virtualbox 4.3 and 5.0 seems to work fine.

let's document some working combinations as this has been discussed in Gitter also:
https://gitter.im/kontena/kontena?at=5768511b4227fdc92298edfa

authors: Knoxvillain jakolehm jnummelin nevalla

repo: kontena/kontena


text:
Configuration for migrations with environment variables

Question
My migrations work with --configFile. But environment variables like DATA_OPS_ENVIRONMENT_ID=xxx and DATA_OPS_API_KEY=xxx don't seem to work. I prefer environment variables because it makes switching environments easier.
The documentation in the READ.ME about this seems to be cut off.
I can't find anything with DATA_OPS in the source of this repository
Is this already implemented?

Hi @Freekbron,
Thank you for submitting the issue. Unfortunately, I am not able to reproduce the issue with the latest version of data-ops. (I used a call like this DATA_OPS_API_KEY=*** DATA_OPS_ENVIRONMENT_ID=*** npx @kontent-ai/data-ops@latest export) What shell are you using to call data-ops? The example we have in the README.md file works in bash but does not have to work in other shells. Please, make sure that the environment variables you define are accessible to the data-ops process.
Regarding our code, the functionality is provided by the yargs library. You can find it used here.
Another thing to mention is that environment variables are only accepted when you run data-ops using the CLI. If you are using the TS/JS API, environment variables are not accepted.

@Freekbron the migrations-boilarplate is using the CLI. It definitely should work with environment variables. Just make sure that the variables are reaching the data-ops process. (e.g. if you set them like this 'runMigrations': 'DATA_OPS_API_KEY=*** tsc && data-ops ...', they will not be accessible to data-ops) The shell environment can also influence this. You can use a package like cross-env to make sure the variables are properly defined on whatever operating system you use.
Can you share the command you use to call data-ops?

@JiriLojda currently I'm using this:
"migrate:all": "tsc && data-ops migrations run --configFile ./migrationsParams.json --all",

So I need to make my own script where I pass my .env variables right?

@Freekbron If you want to pass environment variables from a .env file to a CLI command you'll need to use a tool to do that. For example with dotenv-cli you can call data ops like this tsc && dotenv -- data-ops migrations run --all.

That works, thanks for helping out!

authors: Freekbron JiriLojda

repo: kontent-ai/data-ops


text:
Implement Search for Client

Maybe it's best to use Postgres search for this. Demo: http://www.mathisonian.com/weblog/postgres-full-text-search-with-sequelizejs .

Related: https://stackoverflow.com/questions/9321225/using-dynamic-search-parameters-with-sequelize-js .

repo: koodilehto/koodilehto-crm-backend


text:
[Secure] IDOR Vulnerability report #135

📌 개요

close #135

💻 작업사항

걸어주신 이슈 작업 마쳤습니다.
PR review 해주시면 merge 하겠습니다.
다른 Secure issue도 open 해주세요.

✅ 변경로직

테스트하고 답변드리려고 했다보니 늦어서 죄송합니다. 실제 서비스에서 동적 테스트 마쳤고 해당 문제가 해결된 것을 확인했습니다. 수고하셨습니다.

authors: jeongahn younganswer


text:
Updating versions

Issue
https://github.com/kool-dev/kool/issues/418

:warning: Break Change
TBD

Description
Updating the docker-compose and base alpine image; the image is used on CI, would be important to test this before merging; but in case of problems one can always fix a past image while we work fixing moving forward, so I am OK adding this regardless of testing on CI.

Notes

OK alpine has a critical vulnerability in the latest image; we can hold on this PR while we get a patch in the official image possibly.
CVE-2022-28391  -  https://gitlab.alpinelinux.org/alpine/aports/-/issues/13661

Well actually it seems like 1.16 is not stable at; probably 1.15 is already patched; we can stick to that one.

repo: kool-dev/kool


text:
koord-descheduler: check pod ready when migrating

Ⅰ. Describe what this PR does
fix: https://github.com/koordinator-sh/koordinator/issues/1022

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm

/approve

authors: hormes lucming

repo: koordinator-sh/koordinator


text:
koordlet: supply cpushare inject logic in runtimehooks protocols

Signed-off-by: wangjianyu zmsjianyu@gmail.com
Ⅰ. Describe what this PR does
this pr supplies cpushare inject logic in runtimehooks protocols
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm


text:
TEST: feat(docker): support arm64 for image

This is a pull request to check the behavior when merging into the master branch.

publishに失敗したのとタグつけ忘れてたので別プルリクエストでリトライ😇
https://github.com/korosuke613/secretlint/actions/runs/2089568057/attempts/1


text:
[🔥優先🔥] 株価四本値をDynamoDBに保存する。(メイン for 毎日)

Link #213

このコミット以降、エラーが発生するようになったため、リバーとした。

To: #274

repo: koshikita-volleyball/turnip


text:
pod convert policy code cleanup in main

What type of PR is this?
/kind cleanup

What does this PR do?

pod convert policy code cleanup in main.
Which issue(s) does this PR fix?

Fixes #
Special notes for your reviewer:

@duanmengkk
Does this PR introduce a user-facing change?

NONE

/lgtm
/approve

repo: kosmos-io/kosmos


text:
Render CastingExpression as "cast" function in PostgreSQL dialect

Can the CastingExpression be rendered in PostgreSQL thusly?
    override fun <T : Any> visitCasting(expr: CastingExpression<T>): CastingExpression<T> {
        write("cast(")
        super.visit(expr.expression)
        removeLastBlank()
        write(" as ")
        write(expr.sqlType.typeName)
        write(") ")
        return expr
    }

Or is this not the intention of this expression?

CastingExpression was originally design just to make Kotlin's type checking happy, and it doesn't influence the generated SQL.
Assuming we want to join two tables together, in which one has an int id and the other has a long id:
object T1 : Table<Nothing>("t1") {
    val id by int("id")
}

object T2 : Table<Nothing>("t2") {
    val id by long("id")
}

We might write code like this:
database.from(T1).leftJoin(T2, on = T1.id eq T2.id)

Then the compiler complains that the types of these two ids are not matched. We have to modifiy it as follows:
database.from(T1).leftJoin(T2, on = T1.id.toLong() eq T2.id)

Just a trick.

I just read the document of PostgreSQL's cast function. It will be greate to actually generates a cast function in SQL.

Hello,
any update on this one?
I'd be interested in this function too :)

authors: arustleund d35h vincentlauvlwj

repo: kotlin-orm/ktorm


text:
Always try to demangle

Fixes #24
If frame is not inline at adress_space line 385 and resolve_symbol returns None we won't try to demangle the symbol.
This moves the demangle code so it always tries to demangled the symbol from name.
May not be the best way to do this so feel free to close!
Tests pass, and the resulting flamegraph is cleaner.
For reference here's how I've capture and generate the flamegraph:
./nperf record -F 997 -p 1234 -o datafile
./nperf flamegraph datafile -d /usr/lib/debug/ > flame.svg
Also the symbols are available at the correct path on /usr/lib/debug, so I'm not sure exactly why resolve_symbols would fail ?
nm /usr/lib/debug/tmp/mybin | wc -l
37587
But looks like, it reported it loaded only 69 symbols?
[2022-08-31T17:18:03Z DEBUG nperf_core::data_reader] New binary: "/tmp/mybin"
[2022-08-31T17:18:03Z DEBUG nwind::debug_info_index] Requested debug info for '/tmp/mybin'; debuglink = Some("mybin"), build_id = None
[2022-08-31T17:18:03Z DEBUG nwind::debug_info_index] Debug info lookup result: bin = Some("/usr/lib/debug/tmp/mybin"), dbg = None
[2022-08-31T17:18:03Z DEBUG nwind::symbols] Loaded 69 symbols for '/tmp/mybin' (0 normal, 69 dynamic) in 0ms
Curious to see why build_id is none there as well, as the file does have a build-id
file /tmp/mybin
/tmp/mybin: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /tmp/.elf, for GNU/Linux 3.2.0, BuildID[sha1]=f5ba86caa2c7a6c8efed8efa44869bd268e740ec, stripped

Can you share the source code for your test program and your exact compiler invocation that you use to compile it?

authors: koute thiagovice

repo: koute/not-perf


text:
Handle regexes with null-bytes

This patch brings back a fix in the original cRegex2Dfa module that I missed: we need to include the length of the regex so we don't terminate the string at the first null-byte.

Thanks for this. I committed some unit tests to master that test this NULL byte issue. So, it was easier to just merge this PR manually: https://github.com/kpdyer/regex2dfa/commit/81aa05b6dd9d3aef8232b55ac6c0ca7cff88c2b0.


text:
iPad Mini 3

'already jailbroken' but cydia don't install

Have you tried rebooting then re-running the yalu app?

Yes, and same. @MattCowley

I presume you calculated the offsets yourself?

No.. @MattCowley

No. Nor do I see them in the project (I may be wrong). It's not on the supported device list so I'd just wait till it is supported.

Yes,  the offsets maybe wrong. I will wait for any change.. thanks. @MattCowley

Can you mark this as closed please :)

Wait if someone has the solution @MattCowley

https://github.com/kpwn/yalu102/issues/64

authors: MattCowley Mila432 xNako

license: WTFPL


text:
Force allowedParentDomains value entry in the name of web security awareness

Zoid is an awesome library from usability and security standpoint. But, it needs to rethink default values.
HTML5 Window.postMessage() API has two important attributes viz. target and origin from security standpoint. Security concern: https://securingtomorrow.mcafee.com/business/security-risks-arise-insecure-implementations-html5-postmessageapi/
origin equivalent (from listener's perspective) is visible in Zoid component's definition, but target equivalent isn't visible at all. I wanted to use Zoid for private communications and so I had to hunt down allowedParentDomains from API docs. This isn't at the top of API docs page and what's worse is that the default value is *. None of demo and examples mention it. This is begging users to expose their private Zoid component to the malicious sites which can embed it to retrieve sensitive information using callbacks.
In the name of web security awareness, I request you to remove default value of allowedParentDomains and force users to enter its value in the beginning (put everything in the demo and examples).

Definitely open to discussing this.
That said: the default use-case for zoid is intended to be components which are built for sharing / public consumption, with 'internal' components being the special case.
At the very least, we should make the default policy more prominent in the docs, though.

authors: SachinShekhar bluepnume

repo: krakenjs/zoid