text:
Calibration fails for phospho-enriched TMT run

I'm trying to run calibration on a published phospho-enriched TMT dataset, and all but two of the files fail to calibrate. Has anyone else tried to run calibration on such a dataset or know why it's failing?

Posting them to \bison\share\Projects\MetaMorpheusPhosphoTmtU2OS

The search works great without the calibration, so no rush on this one. It's something to check out down the road.

Can you include a calibration toml and database? I need more info.

I'm adding the original database and the partial results to the folder. (I didn't let the run finish, so I could start running other things.) Thanks for looking into this!

I ran G-PTM-D before the calibration in this run because I knew calibration failed in the past... I was wondering if it was because there weren't enough phosphos annotated in the database for the phospho-enriched run. It turns out a similar number of files failed with or without GPTMD.
The GPTMD results are included in the folder.

It looks like the TMT mods don't have a chemical formula added. Calibration uses this information to calculate the accurate mass and discards the identification if it's not present. For this dataset, that means it has to have an N-terminal acetyl and no lysines, which is pretty rare. I'll try to add the chemical formulas for the TMT mods.

Maybe you can get something close. But, unfortunately, neither TMT nor any of the other so-called isobaric tags are truly isobaric at high resolution. They are isobaric enough to be selected together for fragmentation. But there still equal. We don't want them to be relatively miscalibrated becasue the spacing between the various diagnostic ions is the key for quant.

Thanks for finding that out, Zach, and good point, Michael.
I suppose we could calculate the chemical formula for each of the multiplex-labeled peptides, and then they would get aggregated by IsotopicDistribution based on the resolution. But we'd want to report the MS1 identification as one peptide, not an ambiguous ID between the multiplex-labeled peptides.

I talked with Rob about this and he suggested we supplant the chemical formula with an averagine model for TMT (and other cases). I'm trying this right now to see if the calibration improves your data or if it makes it worse.
I'm pretty sure the TMT labels are the exact same mass. There is no neucode difference.

you could be right. i might have mixed things up. best to double check for higher multplexing though. 11plex

Still working their magic with just 4 carbons and 1 nitrogen for TMT11

Hi Anthony,
Because the intact mass for all of these labels is identical, we can just add the chemical formula to tmt.txt (located in MetaMorpheus\EngineLayer\Mods\tmt.txt
I've attached an updated version here that you can use as a short term solution.
I've also opened a PR to update the file.
This is still going to be an issue for iTRAQ, since those masses do have the neutron-binding energy mass differences. We could use averagine to model the theoretical isotopic distribution, but we'll still be stuck with the issue of ensuring that all of the observed MS1 peaks are being assigned to the correct theoretical MS1 peaks.
This is a big undertaking, but will be important for the calibration of anything that uses these small mass differences (iTRAQ, DiLeu, neucode SILAC)
tmt.txt

PrecursorMassTolerance = "±34.6907 PPM"
ProductMassTolerance = "±5.1149 PPM"
Oof. Okay, that's not great. I'll look again.

This is bizzare. I was expecting it to shift the distribution 30 ppm, but it smeared it

Thanks for sharing the plots. That is bizarre!

authors: acesnik trishorts zrolfs

repo: smith-chem-wisc/MetaMorpheus


text:
Wasm-bindgen gets compiled even for non-wasm32 targets

I haven't figured out which dependency that is exactly, but something is leaking wasm-bindgen

cargo tree should show it.

cargo tree should show it.

Oh, cool, I didn't know takes current target into account.
As far as I understand, this makes it compile futures-timer with wasm-bindgen feature enabled:
[target.'cfg(target_arch = "wasm32")'.dependencies]
futures-timer = { version = "3.0", features = ["wasm-bindgen"] }

See https://github.com/rust-lang/cargo/issues/1197
The new feature resolver was stabilized recently, I actually believe it'll be possible to fix this with the next Rust release! Meanwhile, this could be worked-around with introducing wasm-bindgen feature to bevy_networking_turbulence, just like they do in every other crate.

Oh, cool, I didn't know takes current target into account.
As far as I understand, this makes it compile futures-timer with wasm-bindgen feature enabled:
[target.'cfg(target_arch = "wasm32")'.dependencies]
futures-timer = { version = "3.0", features = ["wasm-bindgen"] }

See https://github.com/rust-lang/cargo/issues/1197
The new feature resolver was stabilized recently, I actually believe it'll be possible to fix this with the next Rust release! Meanwhile, this could be worked-around with introducing wasm-bindgen feature to bevy_networking_turbulence, just like they do in every other crate.

I just checked cargo tree and wasm-bindgen is under dev-dependencies and not under dependencies. So IIUC this issue is solved.
[dev-dependencies]
├── bevy v0.4.0
│   └── bevy_internal v0.4.0
│ [...]
├── console_error_panic_hook v0.1.6
│   ├── cfg-if v0.1.10
│   └── wasm-bindgen v0.2.71
│       ├── cfg-if v1.0.0
│ [...]

Well, I'd like to avoid compiling wasm-bindgen even in the dev environment if possible. If I'm interested only in the UDP stack, for example, I'd like to avoid affecting my clean build time by WASM tools. It's even more noticeable in CI.

If you are not developing bevy_networking_turbulence itself, you are not compiling dev-dependencies. It is used only to build examples project.
If you have the library in your dependencies you are compiling library dependencies only, not dev-dependencies.

Oh, you're right. I also remember that wasm-bindgen was coming from futures-timer, but you've feature-gated it, so it's really good now. Thanks!

source: gharchive/issue

authors: mvlabat smokku

license: MIT

license_type: permissive

license_source: github-api


text:
'modal' is not recognized as the name of a cmdlet

unable to run: modal token new
Error:
modal : The term 'modal' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that
the path is correct and try again.

I'm getting the same issue

same here, after installing added object to path, restarted few times, tried from admin shell - nothing. Windows refuses to recognize "modal"

I have also added the path in the system variables. Same result, model not recognized

modal token new
modal: The term 'modal' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Same problem...

Try using wsl2 or the devcontainer if you are just wanting to get up and running. A lot of the tools in this ecosystem I feel aren't tested against windows necessarily so it's easier to just run in there.
That error is because powershell is expecting a module/command. You can try with & call operator before it, like & modal or if it's a python module be explicit by calling with python3 -m modal .... and see if that helps.
I definitely enjoy windows and macOS, but honestly it's less friction on some of these to just run in devcontainer/wsl2 as things should more clearly just "work".

Modal is still in early beta and we are only selectively giving access to users. You are on the waitlist and we will get back to you when there is capacity for more users.

I was able to resolve this issue by running the modal commands in a terminal outside of Visual Studio Code. The issue seems to only occur in the terminal within Visual Studio Code, but I am not sure why. However, the workaround is working well.

repo: smol-ai/developer


text:
Difference with airbnb/babel-plugin-inline-react-svg

One of my coworker did work with https://github.com/airbnb/babel-plugin-inline-react-svg in a distributed package.
I've told him to use svgr because it is now the default with create-react-app.
I would like to ask the same question as in #74 , how to deal when you are writing a distributed package?
What is the difference between this plugin and the babel plugin?
So far we didn't find a working way to import *.svg with webpack and rollup when it comes to distributed package.

SVGR doesn't have a Babel plugin because it doesn't not work in sync mode (Prettier, etc...). But it is plan to support this way too.

I think now I can get an explanation:
It is better to use babel-plugin-inline-react-svg because it will export your svg as a react component during transpilation. This way, your svg react won't depend of any plugin anymore.
What's the difference with this plugin?
This plugin work with webpack, the svg is converted to react using loaders, and after the production build, you won't need any plugin as well. This fits if you are in an application, not in a module.
What about modules?
rollup can be used to create modules, and svgr have a module for it. If you want to bundle your code with rollup, it is perfect, but if you want to transpile your lib with babel, and have an aside configuration for producing a bundle with rollup, this plugin doesn't fit.
We personally choose to use @svgr/webpack for all svg that are imported in application, and we use babel-plugin-inline-react-svg for svg important in modules.
We do not use @svgr/rollup only because it doesn't fit well with babel-plugin-inline-react-svg, but it would be nice if it could.

authors: kopax neoziro

repo: smooth-code/svgr


text:
Basic Programs / Python

@smv1999 i created hello world in python because we start in python just now so start from level 1 now i added some medium and hard level programs in python because of starting so thats why i added hello world

@smv1999 sir plss review it now i am deleted the hello world now this will merged it so afte next time i ahev to make good question in the repo

@smv1999 sir plss review it now i am deleted the hello world now this will merged it so afte next time i ahev to make good question in the repo

source: gharchive/pull-request


text:
Depth first execution.

Snakemake versions:

7.24.0 and 8.1.0

Is your feature request related to a problem? Please describe.
PROBLEM:  I have a pipeline with 2 rules. Download fastq and align. I want to process one sample at a time OR prioritize processing depth first. My pipeline keep processing them breadth first way. (download all fastqs, then starts aligning them). I have read few previously opened issue but i see no change.
Describe the solution you'd like
I am more worried I am doing something wrong but maybe depth prioritized option?
ATTEMPTS:
I tried multiple things before I wrote here.
I used following command to launch my workflow.
snakemake --snakefile test.snakemake2 --configfile test.yaml --cores 9   --resource mem_mb=200 --forceall -n --prioritize STARsolo_automatic
Per suggested in

priority didnt work. this
using the most updated snakemake didnt help (solver is ILP) this
resource allocation. I limited 200 total mem and gave 120 to download_fastq and 80 to alignment.
In both 7.24 and 8.10 both working solutions run the same so this solution is not working. Previous issue here

I would appreciate any help or guidance.
Thank you very much for developing and maintaining snakemake.
Best,
T.
snakefile
def get_results():
    out_list=[]
    for sample in config["samples"]:
        out_list.append(f"results/{config['project']}/{sample}/STAR/output/Velocyto/filtered")
    return out_list

def gather_all_fastqs(wildcards):
    out_list=[]
    for srr in config["samples"][wildcards.sample]:
        out_list.append(f"raw-data/{wildcards.project}/{wildcards.sample}/{srr}_1.fastq")
        out_list.append(f"raw-data/{wildcards.project}/{wildcards.sample}/{srr}_2.fastq")
    print(out_list)
    return out_list

rule all:
    input: get_results()

rule download_fastq:
    output:
        R1_fastq=temp("raw-data/{project}/{sample}/{SRR}_1.fastq"),
        R2_fastq=temp("raw-data/{project}/{sample}/{SRR}_2.fastq")
    threads:
        8
    resources:
        mem_mb=120
    log:
        "raw-data/{project}/{sample}/log.download.{SRR}"
    shell:
        """
        touch {output.R1_fastq}
        touch {output.R2_fastq}
        """

rule STARsolo_automatic:
    input:
        gather_all_fastqs,
        # y="raw-data/{project}/{sample}/fastq_check_done"
    output:
        directory("results/{project}/{sample}/STAR/output/Velocyto/filtered")
    log:
        "results/{project}/{sample}/log.STAR.txt"
    threads:
        8
    priority:
        50
    resources:
        mem_mb=80
    benchmark:
        "results/{project}/{sample}/benchmark.STAR.txt"
    shell:
        """
        mkdir -p {output}
        """

test.yaml
project: "testproject-001"
samples:
  GSM3148577_BC10_TUMOR1:
  - "SRR7191904"
  - "SRR7191905"
  sample2:
    - "SRR7191904"
  sample3:
    - "SRR7191904"
  sample4:
    - "SRR7191904"

Hi, you may try to set a disk storage limitation in snakemake?

Dear @dariober, Thank you very much for your suggestion. I think i am getting to the bottom of my problem.
snakemake --snakefile code/velo-db-utils/test.snakemake2 --jobs 1
When i execute it it runs like you suggested. Below you see me actually executing it and dry-running it. I remember trying the jobs 1 and was not getting what i wanted. I think the reason is, in execution it actually runs the way i wanted. However, in dry-run the order  is simply rule1 rule1 rule1 > rule2 rule2 rule2. Behaviour is same for v7.24 and v8.1. Then I have an ignorant questions, is there a way to i can see the order of the execution ? DAG does not show the order, I can see the dry-run but you see the problem below. I also dont see the jobid represent the execution order.
Dear @Hocnonsense , I previously played with disk_mb setting in the resources but got no help with that but maybe I was not paying attention to the order.
Thank you very much both of you.
Toy snakefile
samples=["a","b","c"]

rule all:
    input:
        expand("results/test/final_result_{data}",data=samples)

rule rule1:
    output:
        temp("results/test/int_result_{sample}")
    threads:
        8
    resources:
        disk_mb=100
    priority:
        1
    shell:
        """
        touch {output}
        sleep 5
        """

rule rule2:
    input:
        "results/test/int_result_{sample}"
    output:
        "results/test/final_result_{sample}"
    threads:
        8
    priority:
        50
    resources:
        disk_mb=100
    shell:
        """
        touch {output}
        sleep 5
        """

execution
$ snakemake --snakefile code/velo-db-utils/test.snakemake2 --jobs 1
Building DAG of jobs...
Using shell: /usr/bin/bash
Provided cores: 1 (use --cores to define parallelism)
Rules claiming more threads will be scaled down.
Job stats:
job      count    min threads    max threads
-----  -------  -------------  -------------
all          1              1              1
rule1        3              1              1
rule2        3              1              1
total        7              1              1

Select jobs to execute...

[Tue Jan  9 17:32:48 2024]
rule rule1:
    output: results/test/int_result_a
    jobid: 2
    reason: Missing output files: results/test/int_result_a
    wildcards: sample=a
    priority: 1
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:32:53 2024]
Finished job 2.
1 of 7 steps (14%) done
Select jobs to execute...

[Tue Jan  9 17:32:53 2024]
rule rule2:
    input: results/test/int_result_a
    output: results/test/final_result_a
    jobid: 1
    reason: Missing output files: results/test/final_result_a; Input files updated by another job: results/test/int_result_a
    wildcards: sample=a
    priority: 50
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:32:58 2024]
Finished job 1.
2 of 7 steps (29%) done
Removing temporary output results/test/int_result_a.
Select jobs to execute...

[Tue Jan  9 17:32:58 2024]
rule rule1:
    output: results/test/int_result_b
    jobid: 4
    reason: Missing output files: results/test/int_result_b
    wildcards: sample=b
    priority: 1
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:33:03 2024]
Finished job 4.
3 of 7 steps (43%) done
Select jobs to execute...

[Tue Jan  9 17:33:03 2024]
rule rule2:
    input: results/test/int_result_b
    output: results/test/final_result_b
    jobid: 3
    reason: Missing output files: results/test/final_result_b; Input files updated by another job: results/test/int_result_b
    wildcards: sample=b
    priority: 50
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:33:08 2024]
Finished job 3.
4 of 7 steps (57%) done
Removing temporary output results/test/int_result_b.
Select jobs to execute...

[Tue Jan  9 17:33:08 2024]
rule rule1:
    output: results/test/int_result_c
    jobid: 6
    reason: Missing output files: results/test/int_result_c
    wildcards: sample=c
    priority: 1
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:33:13 2024]
Finished job 6.
5 of 7 steps (71%) done
Select jobs to execute...

[Tue Jan  9 17:33:13 2024]
rule rule2:
    input: results/test/int_result_c
    output: results/test/final_result_c
    jobid: 5
    reason: Missing output files: results/test/final_result_c; Input files updated by another job: results/test/int_result_c
    wildcards: sample=c
    priority: 50
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:33:18 2024]
Finished job 5.
6 of 7 steps (86%) done
Removing temporary output results/test/int_result_c.
Select jobs to execute...

[Tue Jan  9 17:33:18 2024]
localrule all:
    input: results/test/final_result_a, results/test/final_result_b, results/test/final_result_c
    jobid: 0
    reason: Input files updated by another job: results/test/final_result_a, results/test/final_result_c, results/test/final_result_b
    resources: tmpdir=/tmp

[Tue Jan  9 17:33:18 2024]
Finished job 0.
7 of 7 steps (100%) done
Complete log: .snakemake/log/2024-01-09T173247.474301.snakemake.log

dry-run
(snakemake2023) $ cat snakeout
Building DAG of jobs...
Job stats:
job      count    min threads    max threads
-----  -------  -------------  -------------
all          1              1              1
rule1        3              1              1
rule2        3              1              1
total        7              1              1

[Tue Jan  9 17:35:53 2024]
rule rule1:
    output: results/test/int_result_b
    jobid: 4
    reason: Forced execution
    wildcards: sample=b
    priority: 1
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:35:53 2024]
rule rule1:
    output: results/test/int_result_c
    jobid: 6
    reason: Forced execution
    wildcards: sample=c
    priority: 1
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:35:53 2024]
rule rule1:
    output: results/test/int_result_a
    output: results/test/final_result_c
    jobid: 5
    reason: Input files updated by another job: results/test/int_result_c
    wildcards: sample=c
    priority: 50
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:35:53 2024]
rule rule2:
    input: results/test/int_result_a
    output: results/test/final_result_a
    jobid: 1
    reason: Input files updated by another job: results/test/int_result_a
    wildcards: sample=a
    priority: 50
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

[Tue Jan  9 17:35:53 2024]
rule rule2:
    input: results/test/int_result_b
    output: results/test/final_result_b
    jobid: 3
    reason: Input files updated by another job: results/test/int_result_b
    wildcards: sample=b
    priority: 50
    resources: tmpdir=/tmp, disk_mb=100, disk_mib=96

Would remove temporary output results/test/int_result_c
Would remove temporary output results/test/int_result_a
Would remove temporary output results/test/int_result_b

[Tue Jan  9 17:35:53 2024]
localrule all:
    input: results/test/final_result_a, results/test/final_result_b, results/test/final_result_c
    jobid: 0
    reason: Input files updated by another job: results/test/final_result_b, results/test/final_result_a, results/test/final_result_c
    resources: tmpdir=/tmp

Job stats:
job      count    min threads    max threads
-----  -------  -------------  -------------
all          1              1              1
rule1        3              1              1
rule2        3              1              1
total        7              1              1

Reasons:
    (check individual jobs above for details)
    forced:
        rule1
    input files updated by another job:
        all, rule2
    missing output files:
        rule1

This was a dry-run (flag -n). The order of jobs does not reflect the order of execution.

sorry for my last reply, the param disk_mb seems for cluster jobs. However, you can set priority of rule 2 ten times higher than rule 1, and once rule 1 for sample=a is done, rule 2 for sample=a is selected prior any other rule 1

My solution to this was to use input functions to create a "linear" DAG.
If you have a workflow of A->B->C and for e.g. sample_1 and sample_2 to process, you can write an input function for rule A that takes wildcards as args and:
If the sample is the first sample you want to process, returns None/Empty string
If the sample is not the first sample, returns the path to rule C's output for the previous sample. In this case the input function would return empty for sample_1, and it would return sample_1's rule C output. This will force the DAG to run A->B->C for sample1 before running A->B->C for sample2.

authors: Hocnonsense lculibrk mortunco

repo: snakemake/snakemake


text:
Disable of option is not working

Disable of selected option in multi select is not working in

@caseyjhol  : This issue still stand correct. How to disable an option from the select? Can we reopen please?
(@sourabh17aitr : found a workaround ?)

repo: snapappointments/bootstrap-select


text:
style: votes page horizontally scrollable on mobile

On mobile and on the page "votes" there isn't enough space to show the content for votes, we should make the table scrollable horizontally, similar than site like https://www.coingecko.com
The cells should have a minum width so it doesnt take extra line, (first cell dont need to be sticky like on coingecko).

Delegates and leaderboard use similar layout, what should happen to them? same as votes?

I had a blocker with sticky property on thead, will wait for this https://github.com/snapshot-labs/sx-monorepo/issues/145#issuecomment-2104404066

We currently hide some column in smaller screen.
I guess with this feature, we keep columns ?

I had a blocker with sticky property on thead, will wait for this #145 (comment)

Merged, so this can move on

sticky doesn't work here. we may have to remove the stickiness of this page. also, the vote % in the background for each will not be correct if we allow horizontal scrolling.

I bumped it to Medium as I think it will require quite a bit of work.

@bonustrack What's the decision here, following the issues raised by chaitu ?

sticky doesn't work here. we may have to remove the stickiness of this page. also, the vote % in the background for each will not be correct if we allow horizontal scrolling.

For the background with vote % if the page is larger than the screen we can make the bg sticky and base the % from the screen width (and not the whole page width). Does it make sense?

And we remove sticky?

For the sticky, I'm not sure what's blocking, we can use div if table is not working

Not an issue of table or div, sticky does not simply seem to work when inside overflow: scroll, it does not stick

There are two problems with this:

If we want sticky nature like below video, we won't able to make it horizontally scrollable
https://github.com/user-attachments/assets/30bc0a8f-663b-4070-b290-6720dbee1779

Not sure how we want to handle voting power in the background,

Here we have the same width as the screen, so if a user 50%, it will add a background of half the screen,
but if we allow horizontal scroll, it may go under the scroll

Need to figure out a solution to keep the first nav with "Overview, votes, discussion" sticky

Here is an example of the UX we want done with CSS using Claude
https://claude.site/artifacts/40c93fdf-5cec-4ed5-b845-232b40385d56

authors: ChaituVR Sekhmet bonustrack wa0x6e

repo: snapshot-labs/sx-monorepo


text:
feat: add support for oSnap

We should add support for oSnap in the UI. oSnap is an integration built by UMA on snapshot.org to execute transactions from Snapshot proposals. It uses UMA as an oracle to confirm onchain if a proposal pass. oSnap is a Safe module that works a bit like a Timelock contract, when a proposal pass, anyone can send a tx to start a challenge period, during the challenge period someone can challenge the proposal result and can stop execution using UMA resolution. You can learn more about it here: https://osnap.xyz
For this integration we need to allow space having oSnap to setup a proposal with execution. The execution is stored in the parameter "plugins" from the proposal. A space can have multiple oSnap Safe modules, on multiple chain. We should allow a proposal to have execution for multiple oSnap module / treasury.
Here is an example of space using oSnap: https://snapshot.org/#/cow.eth
Here is a proposal using oSnap execution: https://snapshot.org/#/cow.eth/proposal/0x7456f84721dbbe164b30324112accf976ff3be397b1957e68abe6953801a1f97
The execution should be visible on the proposal page, similar to how SX-EVM executions are displayed.
With this integration it should also be possible to initiate tx to be populated in a proposal from the treasury page with the send, stake, walletconnect or transfer action.

@bonustrack what features should be supported on SX-UI?

Creating proposal with execution on oSnap
Initiating execution by creating a bond.
Executing transaction.

Anything else?

@Sekhmet That's it yes. There are others features that we will have to add, but it can be done later on within another PRs, these features are:

Add the ability to import and export txs based on Safe format, see how it's done in Snapshot for import: https://x.com/UMAprotocol/status/1780977115652886750
Add ability to setup execution for a space that is not using oSnap (but having treasury setup)
Add support for SafeSnap (this is more complex cuz the format support multiple batch of txs per Safe).

One thing that I didn't mention here and that would require some design is to display the treasury address or execution strategy name within the execution section of the proposal.

@bonustrack I see that it's possible that there are multiple treasuries each having its own execution within single proposal with oSnap.
Should we work on this task first to make it possible to use it? https://github.com/snapshot-labs/sx-monorepo/issues/138
I assume it will be needed.

@Sekhmet I think so

I think it should define not only the network but also the address executing the txs (the treasury)

authors: Sekhmet bonustrack


text:
Support multiple response types in the same post

…if that’s not possible or awkward, document which will take priority if multiple are provided. For example, this post https://waterpigs.co.uk/notes/4gG89z/ is both a photo and an  event RSVP, but when POSSEing to facebook using Publish it was treated just as a photo. From this I can assume that presence of a u-photo takes priority over presence of u-in-reply to p-rsvp — where do other response types fit into this?

good point! at minimum, we should think through the order of precedence (and document it) more deliberately. rsvp should probably come before photo, for example. :P
do you know if there's any prior art or best practice documented anywhere for this yet? I'll go look on the wiki in a bit.

we're probably more likely to just document the order of precedence than to try to get multi posting right. beyond problems like atomicity, we don't necessarily know the user's intent. i can imagine someone else with the same post might be a bit surprised if bridgy posted the rsvp and also the photo, separately. (maybe no more surprised than us choosing one, though. not sure.)
@barnabywalters if you're interested in a more powerful and configurable posse tool, definitely check it @kylewm's https://silo.pub/ ! more background: https://snarfed.org/2015-11-29_keep-bridgy-publish-dumb , https://kylewm.com/2015/11/silo-pub-as-a-generic-micropub-to-silo-adapter

Sounds good to me, at the moment at least I’m very happy to continue using a “dumb” tool, provided I can understand exactly how it’s dumbness works :) So documenting the order of precedence would be great.

On 2016-03-16, at 16:20, Ryan Barrett notifications@github.com wrote:
we're probably more likely to just document the order of precedence than to try to get multi posting right. beyond problems like atomicity, we don't necessarily know the user's intent. i can imagine someone else with the same post might be a bit surprised if bridgy posted the rsvp and also the photo, separately. (maybe no more surprised than us choosing one, though. not sure.)
@barnabywalters https://github.com/barnabywalters if you're interested in a more powerful and configurable posse tool, definitely check it @kylewm https://github.com/kylewm's https://silo.pub/ https://silo.pub/ ! more background: https://snarfed.org/2015-11-29_keep-bridgy-publish-dumb https://snarfed.org/2015-11-29_keep-bridgy-publish-dumb , https://kylewm.com/2015/11/silo-pub-as-a-generic-micropub-to-silo-adapter https://kylewm.com/2015/11/silo-pub-as-a-generic-micropub-to-silo-adapter

i dug into this a bit more, and we actually interpreted this specific post as a note with photo instead of an RSVP because it has class="h-as-note", which overrides post type discovery (http://indiewebcamp.com/post-type-discovery).
h-as-* classes are evidently deprecated, so the fix is probably just to remove support for them and fully follow post type discovery. easy to document too. :P

authors: barnabywalters snarfed

repo: snarfed/bridgy


text:
add disabled to Fieldset

Hi @snehilvj
Can we include this small update in the next release?
@MichaelODeli has the docs PR ready to merge after this is released as well :tada:

Here is a sample app to give it a try

import dash_mantine_components as dmc
from dash import Dash, _dash_renderer, Input, Output
_dash_renderer._set_react_version("18.2.0")

app = Dash(external_stylesheets=dmc.styles.ALL)

component = dmc.Fieldset(
    children=[
        dmc.TextInput(label="Your name", placeholder="Your name"),
        dmc.TextInput(label="Email", placeholder="Email"),
        dmc.Group(
            [
                dmc.Button('Send')
            ],
            justify='flex-end'
        )
    ],
    legend="Personal information",
    disabled = True,
    m=20
)

app.layout = dmc.MantineProvider([
    component
])

if __name__ == "__main__":
    app.run(debug=True)

Whenever I try the fieldset - as part of a drawer element - the heading does now show up like shown in the documentation

@AnnMarieW @snehilvj  - just tagging as the issue is closed
Am I doing something stupid?

@sssaha What version are you using?  Can you please provide a complete minimal example that reproduces the issue?   Hard to tell what the problem is just from an image.

authors: AnnMarieW sssaha

repo: snehilvj/dash-mantine-components


text:
lalrpop exploration

I just read thru the lalrpop documentation and it seems worth investigating the readability & performance comparison to the current nom usage. This exploration task could just be done on its own branch and never merged and it would serve its purpose. But if it stumbles into some improvements, then it could be up for consideration.

I'll plan on taking some time to read the lalrpop docs. I'm definitely interested potential for value it would add to this project. Keep me posted on any details.

Just remembered this issue and something I'd bumped into trying to work with significant whitespace reading the Writing a custom lexer chapter in the lalrpop book. Looks like there's a way work around it (the point of that chapter) but it wasn't the way I'd hoped. I think it's a deal breaker for me, for now.

By default, LALRPOP generates a tokenizer that skips all whitespace -- including newlines. What we want is to capture whitespace characters and ignore the rest as comments, and LALRPOP does the opposite of that.

At the moment, LALRPOP doesn't allow you to configure the default tokenizer. In the future it will become quite flexible, but for now we have to write our own.

authors: CrockAgile shnewto snewt

repo: snewt/bnf

license: mit

license_source: bigquery


text:
放在template循环里报错_.addRef is not a function

使用代码：

报错：

如果单独拿出来不在v-for里循环就没有问题？ 这个要怎么处理？

不要把 <v-contextmenu ref="contextmenu"></v-contextmenu> 放在循环里，相同的 ref 只能存在一个。你可以把触发区域放在循环中，contextmenu 放在循环外面就好

@snokier  咨询一下，把菜单放到循环外面去了，那我要怎么区别是属于哪个层弹出的菜单呢？菜单的点击事件又怎么区别传递呢？

参考 #23 #34

authors: Kennersky snokier

repo: snokier/v-contextmenu


text:
Repeat inference experiments to obtain confidence interval of elapsed time

For the inference experiments, get following times for each pretrained models

Data Loading
Profiling
Forward passing

Repeat the inference experiments since time elapsed has discrepancy according to CPU cores utilized through time.
Suggested by @hihellohowareyou

Extension of issue #14
inference time(CUDA and CPU time)
FLOPS
number of hyperparams
number of layers


text:
Explicitly calling Exporter::import doesn't work

Explicitly calling Exporter::import doesn't work.  For example (from CGI::Carp):
Exporter::import($pkg,keys %routines);

Fixed in v1.027

repo: snoopyjc/pythonizer


text:
🛑 tools is down

In 2dd0712, tools (https://tools.snowdreams1006.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tools is back up in d14b45c.


text:
Pages for Group Basic Concepts

Task  -> Assignee

[ ] Basic Concepts ->
[ ] Project Structure ->
[ ] Astro Pages ->
[ ] Astro Components ->
[ ] Frontend Components (React, Svelte, Vue, and more) ->
[ ] Component Hydration ->
[ ] Layouts -> @ewatch
[ ] Styling -> @itskitto
[ ] Content (Markdown) -> @jgil-r
[ ] Data Fetching ->
[ ] Pagination ->
[ ] Collections ->
[ ] Build & Deploy ->

Layouts -> ewatch

I'll take the styling portion! I want to read more about it so it'll force me to sit down and digest the information on it 😁

Could I get assigned to Content (Markdown)?

Could I get assigned to Content (Markdown)?

Gotcha! Are you in the Discord btw? If so what's your username?

Could I get assigned to Content (Markdown)?

Gotcha! Are you in the Discord btw? If so what's your username?

Yes I am, chuy#5231

I'll take Component Hydration

@itskitto @FredKSchott I added a new page to this section URL Sanitization, not sure if the title is ideal or if it should be part of another group, please let me know your thoughts.
This came out of this PR: https://github.com/snowpackjs/astro-docs/pull/19#discussion_r657479290

After moving everything over from the Astro repo, we're in pretty good shape! Here's what I think is left to do:

Layouts
Pages
build & deploy

Getting close!!!

Done! All pages are now available! 🥳
Curious to hear what people would like to do next! Two steps that jump to mind are:

Edits: Give someone's page a read if you didn't write it yourself, and create a PR to help edit their work. Good chance to review that everything is correct as well, in case something has changed.
Copy these docs into the main astro repo: Now that the docs are complete, we should copy them back into the main astro repo so that any changes made in the main repo are easy to port onto here. (This came up on Discord, but once the site is ready we can move the entire thing into the main astro repo, so this is just a temporary copy step until that work is done).

authors: FredKSchott Hanawa02 ewatch itskitto jgil-r

repo: snowpackjs/astro-docs


text:
Remove SimpleEmitter (close #341)

For issue #341.
Removes SimpleEmitter, and combines AbstractEmitter and BatchEmitter into one class.
I kept the name BatchEmitter rather than changing it to Emitter for two reasons: the Emitter interface is already called Emitter; and to avoid a huge breaking change.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

authors: mscwilson snowplowcla

repo: snowplow/snowplow-java-tracker


text:
SPPayload's value is truncated to 6 digits precision

getPayload uses %g to format a double as a string, but %g defaults to 6 digits of precision:

The double argument is converted in style f or e (or F or E for G conversions).  The precision specifies the number of significant digits.  If the precision is missing, 6 digits are given; if the precision is zero, it is treated as 1.  Style e is used if the exponent from its conversion is less than -4 or greater than or equal to the precision.  Trailing zeros are removed from the fractional part of the result; a decimal point appears only if it is followed by at least one digit.

so we're losing 4 digits of precision in our millisecond timestamps, which is rounding them down to 10s.
NB this bug does not occur with the Android SDK.
I've made a PR that fixes this.

Closed on PR #299

authors: AlexBenny gchilds

repo: snowplow/snowplow-objc-tracker


text:
Replace Gitlab

I love Gitlab, but it is too complex and obscure, and is a huuuge system resources sink, especially when not actively in use.
Maybe we should replace it with something like Gitea + Drone IO or Travis CI or Circle CI (+ deployment tool if necessary) + Uptime Kuma + Prometheus & Grafana ?

Another possible option: OneDev

Closed by #39


text:
Exhibitor reverting to default config in case of network disconnect.

I've got 3 exhibitors on 3 nodes using a central config file on a network share. And everything runs fine. Except, during certain periods of high network traffic, the connection to the central config file is severed. Usually this doesn't matter, but on the rare occasion, exhibitor sees it can't reach the network file, and tries using its local default (I think). It keeps on trying to start zookeeper with the wrong settings until the exhibitor service is stopped and started. Is this expected behaviour? If so, what's the best way of ensuring exhibitor always uses the correct settings?

Exhibitor won't switch config modes. Can you provide an example?

Closing this for now, its been a long time and many new versions have came out since then.
You can re-open if you have further comments.

authors: Randgalt ashic xiaochuanyu

repo: soabase/exhibitor


text:
v1.5.6 pom.xml uses version 1.5.5

The stand-alone pom for tag v.1.5.6 references version 1.5.5 i.s.o. the updated v1.5.6 file.
Please update the v1.5.6 tag with the updated version number.
The same issue exists for the exhibitor-1.1.0 tag pom.xml which is referencing 1.5.6.

Hmm .. I'm not sure how to edit the content of a past version tag without destroying git history.
@Randgalt, any ideas?
Also, why is the latest version tag named exhibitor-1.1.0, I thought it would 1.5.7 or something?}

I've released a new version 1.6.0 and also updated the various pom files to reference this new version. Hopefully everything is correct this time.
Closing this issue for now, you can re-open by commenting.

authors: bassco xiaochuanyu


text:
Custom sql comparison between 2 data source

Usecase:
We have tables with incremental numeric primary key and I want to run comparison between src and destination based on max primary key.
Example,
Find the max_value :
 val max_id=s"select max(${pkey}) from ${sf_table}"

MSSQL:
select  * from   mssql_table  where ${pkey} <= ${max_id}
Snowflake:
select *  from   mssql_table  where ${pkey} <= ${max_id}
check in Snowflake:
row_count is same as MSSQL
Is it possible to achieve above condition in soda ?

SODA-1438

Reconciliation checks are a very powerful way to do schema/metric/row comparison across datasources and datasets and are part of our commercial Soda Library offering.

repo: sodadata/soda-core


text:
add _.isBigint

Description
Please provide a detailed description of the changes and the intent behind them :)
Checklist

[x] Changes are covered by tests if behavior has been changed or added
[x] Tests have 100% coverage
[x] If code changes were made, the version in package.json has been bumped (matching semver)
[x] If code changes were made, the yarn build command has been run and to update the cdn directory
[x] If code changes were made, the documentation (in the /docs directory) has been updated

Resolves
N/A

This is still targeting Radash. We can get it merged over at Radashi fork.

authors: aleclarson heathcliff-hu

repo: sodiray/radash


text:
复写Log4jLogger，适配多模块下static final修饰的Logger情况使用

每次调用日志打印 根据当前线程上下文类加载器动态获取Logger

麻烦再补充两点内容

在 log4j2 的 samples 里再补充个case
log4j2 的适配原理 补充下适配的原理

麻烦再补充两点内容

在 log4j2 的 samples 里再补充个case
log4j2 的适配原理 补充下适配的原理

已补充

repo: sofastack/sofa-serverless


text:
Error: Attempting to watch missing directory

After installing the add-on and running ember server, I get the following error.
The Broccoli Plugin: [Funnel] failed with:
Error: Attempting to watch missing directory: C:\Program Files\Git\ember-panels
node_modules\sl-ember-components\node_modules\sl-ember-components\app
at EventEmitter.Watcher_addWatchDir [as addWatchDir](C:Program FilesGite
mber-panelsnode_modulesember-clinode_modulesbroccoli-sane-watcherindex.js:9
0:11)
at C:\Program Files\Git\ember-panels\node_modules\ember-cli\node_modules\emb
er-cli-broccoli\lib\builder.js:95:35
at lib$rsvp$$internal$$tryCatch (C:\Program Files\Git\ember-panels\node_modu
les\ember-cli\node_modules\rsvp\dist\rsvp.js:1036:16)
at lib$rsvp$$internal$$invokeCallback (C:\Program Files\Git\ember-panels\nod
e_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:1048:17)
at C:\Program Files\Git\ember-panels\node_modules\ember-cli\node_modules\rsv
p\dist\rsvp.js:331:11
at lib$rsvp$asap$$flush (C:\Program Files\Git\ember-panels\node_modules\embe
r-cli\node_modules\rsvp\dist\rsvp.js:1198:9)
at _combinedTickCallback (node.js:370:9)
at process._tickCallback (node.js:401:11)
The broccoli plugin was instantiated at:
at Funnel.Plugin (C:\Program Files\Git\ember-panels\node_modules\sl-ember-co
mponents\node_modules\broccoli-funnel\node_modules\broccoli-plugin\index.js:7:31
)
at new Funnel (C:\Program Files\Git\ember-panels\node_modules\sl-ember-compo
nents\node_modules\broccoli-funnel\index.js:44:10)
at Class.module.exports.treeForVendor (C:\Program Files\Git\ember-panels\nod
e_modules\sl-ember-components\index.js:85:17)
at Class._treeFor (C:\Program Files\Git\ember-panels\node_modules\ember-cli
lib\models\addon.js:322:31)
at Class.treeFor (C:\Program Files\Git\ember-panels\node_modules\ember-cli\l
ib\models\addon.js:290:19)
at C:\Program Files\Git\ember-panels\node_modules\ember-cli\lib\broccoli\emb
er-app.js:446:20
at Array.map (native)
at EmberApp.addonTreesFor (C:\Program Files\Git\ember-panels\node_modules\em
ber-cli\lib\broccoli\ember-app.js:444:30)
at EmberApp._processedVendorTree (C:\Program Files\Git\ember-panels\node_mod
ules\ember-cli\lib\broccoli\ember-app.js:865:29)
at EmberApp._processedExternalTree (C:\Program Files\Git\ember-panels\node_m
odules\ember-cli\lib\broccoli\ember-app.js:895:21)

What version of Node are you running?

v5.7.1

Does running rm -rf node_modules && npm cache clean && npm install resolve the issue?

I ran the command but there was some errors during. Now when I run ember s, I get a different error:
Error: Could not require 'ember-cli-build.js': Cannot find module 'ember-cli/lib
/broccoli/ember-app'

same thing here, when I disabled check at index.js -> treeForVendor() (line 82)
var folder = ( Number( process.version.match( /^v(\d+)/ )[1] ) >= 5 ) ? this.name : '../';

so that the folder was '../', it worked.
ember-cli: 2.8.0-beta.1
node: 6.2.1
os: win32 x64

I have this issue too. I installed sl-ember-components at v0.12.3, cleared the npm cache, removed node_modules, and reinstalled everything, and it's giving me this error. I don't know why it's trying to watch this directory (node_modules/sl-ember-components/node_modules/sl-ember-components/app), because it doesn't make any sense for a package to have itself in node_modules anyway.

@jdhines i think this addon is abandoned, there were no major fixes for at least a year, in the end i just gave up and used ember-bootstrap + bunch of smaller addons.

@jdhines @vlascik This problem seems related to the same cause of https://github.com/softlayer/ember-cli-jsdoc/issues/19 and https://github.com/softlayer/ember-cli-jsdoc/issues/36.  I don't have time at the moment to test all of the iterations of the code but hope to get a fix in for this soon.
@jdhines This package does not have itself in node_modules, it is due to the problem described in the previously-listed issues.  watchman is not watching this directory for any changes, however it does access the directory in order to add LESS-generated CSS into the vendor tree of a consuming app to be imported in included().  More information about this can be found at https://github.com/softlayer/sl-ember-components#styling and https://github.com/softlayer/sl-ember-components/blob/master/index.js#L70-L77
@vlascik This project no longer has full-time development resources being dedicated to it.  Myself and @juwara0, who were the primary contributors no longer work at SoftLayer, and both SoftLayer and our present employer's focus have shifted away from this library.  I try and keep up with any bugs that are reported, such as making modifications last month to be able to support Ember 2.11.0+.  Both @juwara0 and myself remain very interested in the space and any efforts we contribute to it have been undertaken at https://github.com/ember-forge/ember-forge-ui, though you will notice even that project has not been able to be given full-time attention either.  If you, @jdhines, or others have interest in the promise of what https://github.com/ember-forge/ember-forge-ui can provide (of which a lot has already been written and the architecture proven out) please reach out and we can discuss collaboration.
Thank you for your interest in, and use of, this project.

I have been able to replicate this problem.
Serving an app when running

node: v7.8.0
ember-cli: v2.12.1
ember-cli-babel: v5.2.4
sl-ember-components: v0.12.3

there is no problem.  When I upgraded ember-cli-babel to v6.1.0 I encountered this error thougH
Error: Attempting to watch missing directory: /notmessenger/project/node_modules/sl-ember-components/node_modules/sl-ember-components/app
    at Watcher_addWatchDir [as addWatchDir] (/notmessenger/project/node_modules/ember-cli-broccoli-sane-watcher/index.js:142:11)
    at //notmessenger/project/node_modules/broccoli-builder/lib/builder.js:132:35
    at tryCatch (/notmessenger/project/node_modules/rsvp/dist/rsvp.js:539:12)
    at invokeCallback (/notmessenger/project/node_modules/rsvp/dist/rsvp.js:554:13)
    at /notmessenger/project/node_modules/rsvp/dist/rsvp.js:629:16
    at flush (/notmessenger/project/node_modules/rsvp/dist/rsvp.js:2414:5)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)

authors: georges49 jdhines notmessenger vlascik

repo: softlayer/sl-ember-components


text:
Single select configuration - onChange firing before unselect

When using a configuration with selectionLimit=1 and autoUnselect=true, the onChange function passed into the input ngModelChange is fired before the original value is unselected, so the optionsModel ends up with 2 elements in it.  The event is also not fired again when the unselect does occur.
This was found in v1.3.2.

Similar to #148, I'll test this as part of the fix

authors: chris--jones jeremiah-white


text:
async-http-client cannot detect proxy settings

HttpURLConnectionBackend works fine without any configuration.
But when I try to use async-http-client I get HTTP/1.1 407 Proxy Authentication Required
So I need to set
options = SttpBackendOptions.httpProxy()

manually
Could async-http-client work the same way as HttpURLConnectionBackend?

any update on this one?

repo: softwaremill/sttp


text:
play command (-p) doesn't work for multiple translation languages

If I have multiple languages as translation languages (tl) in my init.trans and try to translate a word with the -p option, the first one will be played, while for the second one I receive the following error:

gawk: /dev/fd/63:3481: fatal: expression for `>' redirection has null string value

Thanks for reporting. It seems this bug is specific to the Bing Translator engine -- please always attach the output of trans -V in the future so it's easier for me to look into the cause.

Sure, thanks again!
And thanks for the rapidity!

authors: freeasinbear soimort

repo: soimort/translate-shell

license: unlicense


text:
refactor: reconfig baseUrl in tsconfig file and import order

Configure base url...
refactor import part

please get latest and re-request if desired to merge into latest wallet updates

repo: solana-labs/dapp-scaffold


text:
Fix deposit instruction

Refactor tests for easier composibility
Add deposit instruction and test
Deposit JS test works again

absolutely, I'm building up a list of tests to add, using what's present currently in token as inspiration

repo: solana-labs/solana-program-library


text:
token-js: bump to 0.4.2 for release

Problem
Thanks to @qiweiii, the TokenGroup and TokenGroupMember extensions are now available in @solana/spl-token, but we need to publish a release with the new features!
Solution
Ship it!

git diff [] [] [--] […]
git diff [] --cached [--merge-base] [] [--] […]
git diff [] [--merge-base]  […]  [--] […]
git diff [] … [--] […]
git diff []
git diff [] --no-index [--]

authors: Eianaftyio buffalojoec


text:
Fix borsh library version

There was a new release of dao-xyz/borsh-ts with breaking changes. As we are about to abandon this library, I am only removing the caret from package.json to avoid downloading the newest version.

I am curious (as the maintainer of this lib) what the pain-points are with "@dao-xyz/borsh" library? I see you have extended the writer doing some specific things to convert to and from solidity, so you are not the "standard" user. I fully respect your decision, its more that I would appreciate to learn what could be improved so I could learn the shortcomings of the lib and improve as a dev

@marcus-pousette "abandon this library" refers to @solana/solidity, not @dao-xyz/borsh. I don't think we have an issue with @dao-xyz/borsh.

Aha I see! Thanks for the info.
Yes, the library does not support signed numbers yet. I see your implementation does some extra computation to get around the large signed integers, but I guess it is fine for your use case since you are perhaps not doing thousands of operations per second. I guess, for your custom implementation the most important thing is to test that bounds are handled correctly. I have planned for adding support for signed integers (and floats) in the future, but I have not prioritised that yet, but good to know that there is a need for it!

authors: LucasSte marcus-pousette seanyoung


text:
Can't edit Logo URI

I, can't update the logo URI for UXS token, as the auto merger always gives the error that,
Not eligible for automerge (click details for more information)
found removed line: - "logoURI":
I was changing the logo URI.

Thanks for the help, @keone  but the auto-merge test still failed with the same error,  that Logo URI was removed, attached is the image.
Link to the issue details

repo: solana-labs/token-list


text:
Automate token listing with a GitHub bot

I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary

Current way of manual approvals is a bottleneck, but PR reviews are necessary to ensure that others' data is not tampered with. A GitHub bot can automate this in a secure way:

Use Google Forms to accept token listing data
A webhook call is made to the GitHub bot when form is submitted. The bot has write permission to the repo. It writes adds a formatted object into solana.tokenlist.json. Since write format is fixed and the bot keys are hidden on a server, there's no scope of tampering.

    {
      "chainId": 101,
      "address": "CJR5HtmXzpCD8Ro28zyZyLjz1wtrCsu7bEwC4f8ZjRCD",
      "symbol": "GEKZ",
      "name": "Gekz Arena",
      "decimals": 9,
      "logoURI": "https://raw.githubusercontent.com/solana-labs/token-list/main/assets/mainnet/CJR5HtmXzpCD8Ro28zyZyLjz1wtrCsu7bEwC4f8ZjRCD/logo.png",
      "tags": [],
      "extensions": {
        "website": "https://www.gekzarena.com/",
        "twitter": "https://twitter.com/gekzarena",
        "discord": "https://discord.gg/Mh29ZdQCGC"
      }

+1

Cool idea

Solana is all about speed,,,,,
Automation leads to innovation, come on solana i want you to kill ETH faster!

Hey, everyone!
As a coding challenge, I got the opportunity to try my hands at this issue!
Functionality is exactly same as @secretshardul proposed.
If you want to check it out (and give much appreciated feedback 💙 ) please go to the following links:

Bot
Bot Repository
Form To Submit New Token

Currently If you go and fill the form and submit it, the bot will instantly add a new token to exogenesys/token-list
Here is one of the recent commit by the bot to add a token.
Problems yet to be tackled

The google form is connected to zapier which in turn makes POST requests. Zapier has a monthly limit of 100 triggers
The bot allows duplicate entries
Data validation can definitely be improved upon (feedback are welcomed!)
The bot is a nodejs app and is currently hosted on heroku, which make its servers (dynos) sleep after inactivity, so sometimes the bot may take 1-2 minutes to work
Google form is error-prone in submitting arrays and objects

Somebody else tested the bot by adding a token $PNT, here is the commit by the bot. Sharing since it can take a few minutes to reflect!

Any way you could help me add my coin

very helpful i hope my problem is solved

Hey @Cl3v4 @shikokusolanatoken This bot is not yet connected to the solana-labs/token-list repo -- so it won't help you

authors: CEO-NextMindCoin Cl3v4 SolGuy801 exogenesys secretshardul shikokusolanatoken stevenpollack


text:
Adding Armani Mendrek token

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

Appears that a new user requires manual merge.  Will await further instructions as we are not sure what else is required from us.


text:
add BRKTR token

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

BRKTR token

BRKTR token


text:
add guild saga gems token

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

ggem


text:
Populating componentsjs variables from env-vars

For creating component-instances, all config is currently refactored out to componentsjs config files. And there is provision for variables.
But there is no direct way to create and use new variables other than creating custom init/AppRunner.ts, as it takes only pre-defined variables through cli flags.
It will be truly extensible if AppRunner also parses env-vars and maps them to componentsjs-vars. The mapping can be defined in a component-instantiation-file itself at a standard/customizable path.
It also allows us to properly handle secrets through env-vars.

We have an older issue that's related to this: #158

Thanks for pointer @joachimvh .
I will be closing the isuue, and continue there.

authors: damooo joachimvh

repo: solid/community-server


text:
cannot read jsonld resource

https://timbl.com/timbl/Public/Test/Content-Type/application/ld-json/
On a server created in december the problem do not occur https://bourgeoa.bourgeoa.ga:8560/public/test.jsonld

What's the problem here? I tried the url at timbl.com and it seems to work properly for me:

@NoelDeMartin
This is the issue for example on : https://bourgeoa.solidcommunity.net:8443/public/test.jsonld
(you can try it, it is a public link)
Firefox and chrome on windows or linux give the same error. What browser are you using ?

I think there is something to deal with the mimetype of the files.
As I remember
application/json can be read by solidos
application/json+ld can not

@scenaristeur agreed. That is what need to be resolved.
We must found where and why the problem occurs.
Some server do not have the problem like https://Bourgeois.bourgeoa.ga:8560/public/test.jsonld and apparently @NoelDeMartin do not have the problem with the browser he is using.
Using node-fetch directly like with solid-ide solid-file-client there is no problem to PUT or GET. There is also no problem with the test-suite. Nor with rdflib.js unit tests, but these are unit tests.
I tried different version of rdflib and had no success.
@timbl thinks it may relate to missing async/await

Here is what get using Solid-Node-Client on https://bourgeoa.solidcommunity.net:8443/public/test.jsonld :
 get JSON-LD file :
    status 200
    content-type application/ld+json
    body {}

If I create my own json-ld file and use Solid-Node-Client to put it  with content-type application/ld_json, I can read fine and a get returns the JSON I sent in the put as the body.  What is the body of this test file?

I just checked with ide and  the contents of the file is a pair of empty curly braces.  Maybe try the same thing but with acutal JSON-LD content?  I use this to test with :
{
  "@context": "https://json-ld.org/contexts/person.jsonld",
  "@id": "http://dbpedia.org/resource/John_Lennon",
  "name": "John Lennon",
  "born": "1940-10-09",
  "spouse": "http://dbpedia.org/resource/Cynthia_Lennon"
}

I guess that is not the issue. This script succeeds and returns the expected JSON but in the databrowser  it shows fetch error with undefined status
const {SolidNodeClient} = require('solid-node-client');
const client = new SolidNodeClient();
const url="https://jeff-zucker.solidcommunity.net:8443/public/test.jsonld";
const jsonld=`
{
  "@context": "https://json-ld.org/contexts/person.jsonld",
  "@id": "http://dbpedia.org/resource/John_Lennon",
  "name": "John Lennon",
  "born": "1940-10-09",
  "spouse": "http://dbpedia.org/resource/Cynthia_Lennon"
}
`;
async function run(){
  await client.login(credentials);
  let r1 = await client.fetch(url,{
    method: "PUT",
    body: jsonld,
    headers: {"content-type":"application/ld+json"}
  });
  let r2 = await client.fetch(url);
  console.log("put JSON-LD file : ", r1.status)
  console.log("get JSON-LD file : ",r2.status,r2.headers.get('content-type'));
  console.log(await r2.text());
}
const credentials = {
    "idp": "https://solidcommunity.net:8443",
    "username": "jeff-zucker",
    "password": "...",
}
run()

Yes @jeff-zucker the problem only arise in datatBrowser
The console log is :

HTTP error: Status undefined (undefined) fetching https://bourgeoa.solidcommunity.net:8443/public/test.jsonld

The error is created in rdflib and while the fetchResponse exists, it seems that all or some keys are undefined..

The problem occurs in fetcher.ts line 1213 where nowOrWhenFetched checks the response from a fetch and looks for response.ok.  But jsonld returns an indexedFormula and has no ok property.  Removing the ok  in that line lets the jsonld be displayed.  So either we need to check here if the response is an indexedFormula or else we need jsonldHandler to return a Response object with an ok property.

Note : I believe @NoelDeMartin could read jsonld from timbl.com because it uses an older stack, not because he used a different browser.

see also https://github.com/solid/solid-panes/issues/254

Resolved by https://github.com/linkeddata/rdflib.js/pull/509/

authors: NoelDeMartin angelo-v bourgeoa jeff-zucker scenaristeur

repo: solid/solidos


text:
rdflib with LiveStore version added

solidos had a rdflib dependence. Not sure why but I changed it to include the LiveStore commit.

This is not correct nor relevant anymore


text:
fix catchError propagation

Summary
Opening this up just for the idea. I initially used a separate const ErrorHandled = Symbol() but changed to ERROR.
fixes https://github.com/solidjs/solid/issues/1895

IMO, catchError should work like one we have in the language. It should stop further execution inside the boundary. Everything outside should work as usual.
https://playground.solidjs.com/anonymous/a42cb5b3-37b9-4469-9b48-a5fc0d50937e
How did you test this change?
Added a narrowed down test for catchError though I'm not sure if there's any other edge cases.
pnpm test seems to pass including the one added.

Pull Request Test Coverage Report for Build 9997429348
Details

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 93.602%

Totals

Change from base Build 9751531446:
0.04%

Covered Lines:
4194

Relevant Lines:
4416

💛  - Coveralls

I'm going to link a conversation I had with Jin which lead to the last change in error behavior: https://dev.to/ninjin/comment/206d2
I'm not saying this doesn't uphold this but I want to review it in this context. I was thinking that moving towards lazy computation would mean we wouldn't want to error out everything but just things that depended on the broken stuff.. That being said we aren't there in current Solid so we have to make a decision.

authors: coveralls mdynnl ryansolid

repo: solidjs/solid


text:
upgrade to 21.05.2

this is only a upgrade from 0.31.6 to 21.05.2 like the last upgrade

Hey @sysreport,
thanks for your contribution. I'll let handle CI the rest and merge it if all goes green.

authors: solidnerd sysreport

repo: solidnerd/docker-bookstack


text:
Reconsider adding an address to the imported StockLocation

We're currently using Shopify's HQ as the default stock location address, but we'd probably better off not setting an address at all, making the behavior more simple and understandable.
@MinasMazar wdyt?

Hi @elia! This is no longer an issue since #39 has been merged 👍

authors: MinasMazar elia


text:
macOS 菜单栏汉化

菜单栏的汉化怎么是Windows那套风格草哈哈哈哈

这是你的个人设置的问题吧，改变一下主题看看，我这里最新的release是没问题的，下面是预览图：

抱歉我没说清楚，我的意思是macOS的菜单栏应该没有"(F)" "(E)"这些源自Windows的Alt快捷键提示才对吧

好像是，不过也没啥影响，晚会更新到最新的版本试试。

刚测试了最新版本的，也有这个问题，不过这个也不是我能搞定的，先关闭issue了。

repo: sollyu/AndroidStudioChineseLanguagePack


text:
Solo APIs. @tag-name=sa-k8s-1.28-bump

Bump to k8s 1.28
Updates the latest rate-limit protos as of 2023-12-05
Updates skv2 and adds the corresponding flags to mitigate breaking changes

Given the conversations we had around why this branch exists, and what alternatives we considered, I think it would be helpful if we persisted those findings somewhere for future developers to discover. I could see value in any of the following places:

Add a README to this branch in solo-apis
Create an issue that outlines the technical debt of this solution, and add it as a comment in the go.mod above the dependency in gloo
Add an entry to the gloo oss or enterprise devel/ folder
Some other better option I'm not thinking of

Added docs around this branch
https://github.com/solo-io/solo-apis/pull/1090

authors: davidjumani sam-heilbron

repo: solo-io/solo-apis


text:
🛑 server.h-24871.kz is down

In 7660f8f, server.h-24871.kz (185.121.81.43) was down:

HTTP code: 0
Response time: 0 ms

Resolved: server.h-24871.kz is back up in 297403a.


text:
Directory listing: give more characters to the name column

I am almost sure this is not the right repository for this enhancement request.
Please let me know if I have to move it to another GitHub project!

What are you trying to do?

At https://search.maven.org/artifact/io.netty/netty-tcnative-boringssl-static/2.0.34.Final/jar, at the top-right corner there is a Browse button that leads to https://repo1.maven.org/maven2/io/netty/netty-tcnative-boringssl-static/2.0.34.Final/
As you can see the file names are cut and it is hard to see their full names. I needed to see the possible classifiers.
It would be nice to give more room for the file name column.
If Apache HTTPD is the backend server then most probably IndexOptions NameWidth should be modified.

i would like to see this feature implemented. as user is mostly concerned about directly downloading jar if they want to come via UI based download

authors: ArjunDandagi martin-g


text:
令牌创建初始额度设置问题

例行检查

[x] 我已确认目前没有类似 issue
[x] 我已确认我已升级到最新版本
[x] 我已完整查看过项目 README，尤其是常见问题部分
[x] 我理解并愿意跟进此 issue，协助测试和提供反馈
[x] 我理解并认可上述内容，并理解项目维护者精力有限，不遵循规则的 issue 可能会被无视或直接关闭

问题描述
版本：v0.4.9-alpha.1
令牌创建初始额度设置为0，后面再把额度增加上，这时候会发现即使有额度，也还是用不了，一直提示额度已耗尽。
复现步骤
预期结果
相关截图

你是不是没有启用？

你是不是没有启用？

不，我又测试了一下，确实是有这个问题，编辑加额度后，启用了，然后使用还是会提示该令牌额度已用尽，然后状态会自动变为已耗尽，额度实际上是有的，再次启用也没法用

我又试了一次，还是没法复现。
方便的话发视频吧。

authors: Ackites songquanpeng

repo: songquanpeng/one-api


text:
stream 模式下，字符串的兼容性问题。

例行检查

[x] 我已确认目前没有类似 issue
[x] 我已确认我已升级到最新版本
[x] 我已完整查看过项目 README，尤其是常见问题部分
[x] 我理解并愿意跟进此 issue，协助测试和提供反馈
[x] 我理解并认可上述内容，并理解项目维护者精力有限，不遵循规则的 issue 可能会被无视或直接关闭

问题描述
对于 stream 响应的容错性不足，对于下图的 stream 响应似乎会报错：[SYS] 2023/07/12 - 15:58:34 | error unmarshalling stream response: invalid character 'd' after top-level value

复现步骤
预期结果
应该可以正常解析，没有 content 字段的内容直接忽略。
相关截图
如果没有的话，请删除此节。

我这边也能复现这个问题，不过为什么 delta 里面偶尔会出现没有 content 键的情况呢？

没有 content 也不应该反序列化错误才对

我还发现一种情况会返回 invalid character 'd' after top-level value 这个错误
就是上游渠道那边在下游传参是 stream: false 非流的时候，进行了流式返回，就也会有这个错误

官方的我都遇到过，只是再次请求又好了

实测没有 content 并不会导致序列化错误，问题出在其他地方。

我今天添加 ChatGLM2 支持的时候也发现了这个问题，目前应该已经解决，问题在于有些实现的分隔符不是两个换行，而是一个，就会导致解析出错，现在 One API 已经对此做了兼容处理。

我今天添加 ChatGLM2 支持的时候也发现了这个问题，目前应该已经解决，问题在于有些实现的分隔符不是两个换行，而是一个，就会导致解析出错，现在 One API 已经对此做了兼容处理。

是的。sse中，应该是先进行2个换行拆分，再进行1个换行。

目前的实现是直接用一个换行进行拆分，然后丢弃掉无效的部分。

目前的实现是直接用一个换行进行拆分，然后丢弃掉无效的部分。

感觉可能会埋坑。
标准sse中是包括event name和data。最好还是能完整解析，防止以后会出现event name的情况。
fastgpt 中是先对\n\n进行拆分，然后再对\n进行拆分，从中解析name和data进行完整转发。(name可以不存在)

如果 OpenAI 的返回体格式变了，那到时候再处理吧，现在应该是没什么问题的

authors: c121914yu mrhaoji songquanpeng


text:
[Thinkit] Add APIs

Build Results:
divya@e9e9b2e05579:/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
INFO: Analyzed 373 targets (0 packages loaded, 0 targets configured).
INFO: Found 373 targets...
INFO: Elapsed time: 0.524s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
Test Results:
divya@e9e9b2e05579:/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
INFO: Analyzed 373 targets (2 packages loaded, 103 targets configured).
INFO: Found 373 targets...
INFO: Elapsed time: 19.009s, Critical Path: 18.05s
INFO: 4 processes: 1 internal, 3 linux-sandbox.
INFO: Build completed successfully, 4 total actions
divya@e9e9b2e05579:/sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS --cache_test_results=no ...
INFO: Analyzed 373 targets (0 packages loaded, 26 targets configured).
INFO: Found 245 targets and 128 test targets...
INFO: Elapsed time: 66.236s, Critical Path: 16.40s
INFO: 133 processes: 140 linux-sandbox, 17 local.
INFO: Build completed successfully, 133 total actions
//gutil:collections_test                                                 PASSED in 0.5s
//gutil:io_test                                                          PASSED in 0.5s
//gutil:proto_matchers_test                                              PASSED in 0.7s
//gutil:proto_ordering_test                                              PASSED in 0.5s
//gutil:proto_test                                                       PASSED in 0.5s
//gutil:status_matchers_test                                             PASSED in 0.5s
//gutil:test_artifact_writer_test                                        PASSED in 0.6s
//gutil:testing_test                                                     PASSED in 0.5s
//gutil:version_test                                                     PASSED in 1.1s
//lib:basic_switch_test                                                  PASSED in 0.8s
//lib/gnmi:gnmi_helper_test                                              PASSED in 0.8s
//lib/gnoi:gnoi_helper_test                                              PASSED in 0.5s
//lib/utils:json_utils_test                                              PASSED in 0.0s
//lib/validator:validator_backend_test                                   PASSED in 0.5s
//p4_fuzzer:constraints_util_integration_test                            PASSED in 0.6s
//p4_fuzzer:fuzz_util_test                                               PASSED in 0.7s
//p4_fuzzer:fuzzer_showcase_test                                         PASSED in 0.9s
//p4_fuzzer:switch_state_test                                            PASSED in 0.6s
//p4_fuzzer:table_entry_key_test                                         PASSED in 0.1s
//p4_pdpi:built_ins_test                                                 PASSED in 0.5s
//p4_pdpi:entity_keys_test                                               PASSED in 0.6s
//p4_pdpi:ir_tools_test                                                  PASSED in 0.7s
//p4_pdpi:p4_runtime_matchers_test                                       PASSED in 0.6s
//p4_pdpi:reference_annotations_test                                     PASSED in 0.7s
//p4_pdpi:sequencing_util_test                                           PASSED in 0.6s
//p4_pdpi/netaddr:ipv4_address_and_network_address_test                  PASSED in 0.5s
//p4_pdpi/netaddr:ipv6_address_test                                      PASSED in 0.6s
//p4_pdpi/netaddr:mac_address_test                                       PASSED in 0.5s
//p4_pdpi/packetlib:packetlib_fuzzer_test                                PASSED in 16.3s
//p4_pdpi/packetlib:packetlib_matchers_test                              PASSED in 0.5s
//p4_pdpi/packetlib:packetlib_test                                       PASSED in 0.1s
//p4_pdpi/packetlib:packetlib_test_runner                                PASSED in 0.1s
//p4_pdpi/packetlib:packetlib_unit_test                                  PASSED in 1.7s
//p4_pdpi/string_encodings:bit_string_test                               PASSED in 0.5s
//p4_pdpi/string_encodings:byte_string_test                              PASSED in 0.5s
//p4_pdpi/string_encodings:decimal_string_test                           PASSED in 0.0s
//p4_pdpi/string_encodings:decimal_string_test_runner                    PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test                               PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test_runner                        PASSED in 0.0s
//p4_pdpi/string_encodings:readable_byte_string_test                     PASSED in 0.5s
//p4_pdpi/testing:helper_function_test                                   PASSED in 0.6s
//p4_pdpi/testing:info_test                                              PASSED in 0.1s
//p4_pdpi/testing:info_test_runner                                       PASSED in 0.1s
//p4_pdpi/testing:main_pd_test                                           PASSED in 0.0s
//p4_pdpi/testing:mock_p4_runtime_server_test                            PASSED in 1.6s
//p4_pdpi/testing:packet_io_test                                         PASSED in 0.2s
//p4_pdpi/testing:packet_io_test_runner                                  PASSED in 0.2s
//p4_pdpi/testing:rpc_test                                               PASSED in 0.1s
//p4_pdpi/testing:rpc_test_runner                                        PASSED in 0.1s
//p4_pdpi/testing:sequencing_test                                        PASSED in 0.1s
//p4_pdpi/testing:sequencing_test_runner                                 PASSED in 0.1s
//p4_pdpi/testing:sequencing_util_test                                   PASSED in 0.1s
//p4_pdpi/testing:sequencing_util_test_runner                            PASSED in 0.1s
//p4_pdpi/testing:table_entry_gunit_test                                 PASSED in 0.8s
//p4_pdpi/testing:table_entry_test                                       PASSED in 0.1s
//p4_pdpi/testing:table_entry_test_runner                                PASSED in 0.1s
//p4_pdpi/utils:annotation_parser_test                                   PASSED in 0.5s
//p4_pdpi/utils:ir_test                                                  PASSED in 0.6s
//p4rt_app/event_monitoring:app_state_db_port_table_event_test           PASSED in 1.0s
//p4rt_app/event_monitoring:app_state_db_send_to_ingress_port_table_event_test PASSED in 0.9s
//p4rt_app/event_monitoring:config_db_cpu_queue_table_event_test         PASSED in 1.0s
//p4rt_app/event_monitoring:config_db_node_cfg_table_event_test          PASSED in 0.9s
//p4rt_app/event_monitoring:config_db_port_table_event_test              PASSED in 0.9s
//p4rt_app/event_monitoring:debug_data_dump_events_test                  PASSED in 0.9s
//p4rt_app/event_monitoring:state_verification_events_test               PASSED in 1.0s
//p4rt_app/p4runtime:cpu_queue_translator_test                           PASSED in 0.6s
//p4rt_app/p4runtime:ir_translation_test                                 PASSED in 0.8s
//p4rt_app/p4runtime:p4info_verification_schema_test                     PASSED in 0.7s
//p4rt_app/p4runtime:p4info_verification_test                            PASSED in 0.9s
//p4rt_app/p4runtime:packetio_helpers_test                               PASSED in 1.0s
//p4rt_app/p4runtime:resource_utilization_test                           PASSED in 0.9s
//p4rt_app/sonic:app_db_acl_def_table_manager_test                       PASSED in 0.8s
//p4rt_app/sonic:app_db_manager_test                                     PASSED in 0.8s
//p4rt_app/sonic:app_db_to_pdpi_ir_translator_test                       PASSED in 0.8s
//p4rt_app/sonic:hashing_test                                            PASSED in 0.8s
//p4rt_app/sonic:packet_replication_entry_translation_test               PASSED in 0.7s
//p4rt_app/sonic:packetio_impl_test                                      PASSED in 0.6s
//p4rt_app/sonic:packetio_port_test                                      PASSED in 0.6s
//p4rt_app/sonic:response_handler_test                                   PASSED in 0.7s
//p4rt_app/sonic:state_verification_test                                 PASSED in 0.6s
//p4rt_app/sonic:vrf_entry_translation_test                              PASSED in 0.8s
//p4rt_app/sonic/adapters:fake_sonic_db_table_test                       PASSED in 0.1s
//p4rt_app/tests:acl_table_test                                          PASSED in 1.4s
//p4rt_app/tests:action_set_test                                         PASSED in 1.1s
//p4rt_app/tests:api_access_test                                         PASSED in 1.0s
//p4rt_app/tests:arbitration_test                                        PASSED in 1.1s
//p4rt_app/tests:cpu_queue_name_and_id_test                              PASSED in 1.6s
//p4rt_app/tests:debug_data_dump_test                                    PASSED in 1.0s
//p4rt_app/tests:fixed_l3_tables_test                                    PASSED in 2.6s
//p4rt_app/tests:forwarding_pipeline_config_test                         PASSED in 4.0s
//p4rt_app/tests:grpc_behavior_test                                      PASSED in 5.4s
//p4rt_app/tests:p4_constraints_test                                     PASSED in 1.2s
//p4rt_app/tests:p4_constraints_test_runner                              PASSED in 0.2s
//p4rt_app/tests:p4_programs_test                                        PASSED in 1.6s
//p4rt_app/tests:packetio_test                                           PASSED in 3.7s
//p4rt_app/tests:port_name_and_id_test                                   PASSED in 2.4s
//p4rt_app/tests:resource_limits_test                                    PASSED in 1.8s
//p4rt_app/tests:response_path_test                                      PASSED in 2.8s
//p4rt_app/tests:role_test                                               PASSED in 1.2s
//p4rt_app/tests:state_verification_test                                 PASSED in 1.8s
//p4rt_app/tests:vrf_table_test                                          PASSED in 1.6s
//p4rt_app/tests/lib:app_db_entry_builder_test                           PASSED in 0.0s
//p4rt_app/utils:event_data_tracker_test                                 PASSED in 0.0s
//p4rt_app/utils:table_utility_test                                      PASSED in 0.8s
//sai_p4/instantiations/google:clos_stage_test                           PASSED in 0.5s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test PASSED in 0.0s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test        PASSED in 0.0s
//sai_p4/instantiations/google:sai_p4info_fetcher_test                   PASSED in 0.7s
//sai_p4/instantiations/google:sai_p4info_test                           PASSED in 0.9s
//sai_p4/instantiations/google:sai_pd_proto_test                         PASSED in 0.0s
//sai_p4/instantiations/google:sai_pd_util_test                          PASSED in 0.7s
//sai_p4/instantiations/google:tor_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google:union_p4info_up_to_date_test              PASSED in 0.1s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test                PASSED in 0.2s
//sai_p4/instantiations/google/test_tools:table_entry_generator_helper_test PASSED in 1.7s
//sai_p4/instantiations/google/test_tools:test_entries_test              PASSED in 0.8s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 0.8s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.6s
//sai_p4/tools:packetio_tools_test                                       PASSED in 0.8s
//thinkit:bazel_test_environment_test                                    PASSED in 0.5s
//thinkit:mock_control_device_test                                       PASSED in 0.6s
//thinkit:mock_generic_testbed_test                                      PASSED in 0.7s
//thinkit:mock_mirror_testbed_test                                       PASSED in 0.7s
//thinkit:mock_ssh_client_test                                           PASSED in 0.0s
//thinkit:mock_switch_test                                               PASSED in 0.9s
//thinkit:mock_test_environment_test                                     PASSED in 0.1s
//thinkit:switch_test                                                    PASSED in 0.7s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 11.7s
Stats over 5 runs: max = 11.7s, min = 1.1s, avg = 7.6s, dev = 4.9s
Executed 128 out of 128 tests: 128 tests pass.
INFO: Build completed successfully, 133 total actions
divya@e9e9b2e05579:/sonic/src/sonic-p4rt/sonic-pins$
Keyword Check:
divya@eonms3vm12:~/new_code/sonic-buildimage/src/sonic-p4rt/sonic-pins$ ~/keyword_checks.sh .
Keyword check Passed.
Pins-commit ID: 613f4857c4282626927548015d907679f08987ce

@kishen, could you please review.

authors: bibhuprasad-hcl divyagayathri-hcl

repo: sonic-net/sonic-pins


text:
Null Safety

Is there a timeline on this getting migrated to null safety?

Hi @emmett-deen, We don't have a timeline for that yet, but our repo is open to receive contributions. It would be awesome if you can help us on that.

authors: emmett-deen maiconpeixinho

repo: sonikro/flutter-okta-sdk


text:
Create readme.md for SQL directory

hacktoberfest-2022
Created SQL folder with readme.md file.
Will add commands of SQL in the next PRs

You can follow me on github and give ⭐ to this repo.

authors: NamanManjkhola sonumahajan


text:
Question: What validations to perform before placing a market order?

I'm placing a market order (say XRPETH, 20, SELL) and sometimes I'm getting "Error happened while making order to Binance. Filter failure: LOT_SIZE", sometimes succeed.
So, is there any kind of checks to perform before placing a market order?

@betimd, there are a couple of ClientOrder extension methods available: IsValid() and Validate(). The former returns a bool result and the later throws an exception with a message. Both use the cached Symbol information to determine, among other things, if the ClientOrder.Quantity will pass the 'LOT_SIZE' filter for the symbol. The static asset/symbol information is only as recent as the latest build, but you can update them using Symbol.UpdateCacheAsync().

@sonvister is there any way to "format" quantity of a symbol before making order? Because if I'm having a market order TRXBTC, and I send say 1000.98 I get exception (LOT_SIZE). Thought, let me remove decimals and round a full number and it worked. But on the same time I cannot do this with BTC, while value of BTC I have say it's ~0.1982, so the former rounding doesn't work while it gives me 0. So, is there any way to have a proper qty for a pair?

@betimd, for that there are 3 extension methods on InclusiveRange or symbol.Quantity: GetUpperValidValue, GetValidValue, and GetLowerValidValue. The comments should help explain how each work if the names aren't enough. For more info, the source code is InclusiveRangeExtensions.cs.

@sonvister very helpful. Thnx a lot. What would be the best updating rate of symbol caches? In hours, days, weeks. I mean I want to have serialized locally and not ping Binance every time I check any amount of price if it's correct.

@betimd, I do not know what is best. I can say this data doesn't change very frequently and most of the changes are additional symbols. At a minimum, I would update when the application starts (as updates to this library will become less frequent). Serializing seems unnecessary, since I can't imagine a use case where an application is starting and stopping so frequently. Beyond that, I would again update if the 'LOT_SIZE' or similar filter failure occurs during order placement after validation passes. Also, some changes may not cause an error, but not give you the best result. So, a regular update should also occur which is application dependent. The exchange info rate limit weight is 1, so conceivably you could refresh the cache frequently.

authors: betimd sonvister

repo: sonvister/Binance


text:
FLW-890 Update Validators screen & Recommended flow

add option of "Select by yourself"
update navigation of "Select recommended"

Show "Recommended validators" with validators and their APY, and a button to continue to Confirm screen

add "Stake with your validators" text block and action cell

Codecov Report

Merging #277 (3ea6626) into develop (7920849) will increase coverage by 1.67%.
The diff coverage is 39.03%.

@@             Coverage Diff             @@
##           develop     #277      +/-   ##
===========================================
+ Coverage    31.43%   33.10%   +1.67%
===========================================
  Files          462      501      +39
  Lines        19656    22710    +3054
===========================================
+ Hits          6179     7519    +1340
- Misses       13477    15191    +1714

Impacted Files
Coverage Δ

...ataProvider/Sources/JsonSingleProviderSource.swift
0.00% <0.00%> (ø)

...DataProvider/Sources/WebSocketProviderSource.swift
0.00% <0.00%> (ø)

.../Subscription/SingleValueSubscriptionHandler.swift
10.00% <0.00%> (-1.12%)
:arrow_down:

...s/Common/Extension/Model/WalletAssetId+Chain.swift
0.00% <0.00%> (ø)

...e/CDTransactionHistoryItem+CoreDataDecodable.swift
0.00% <0.00%> (ø)

.../Common/Extension/UIKit/GradientButton+Style.swift
0.00% <0.00%> (ø)

...sion/Wallet/TransactionHistoryItem+Extrinsic.swift
0.00% <0.00%> (ø)

.../Common/Migration/NetworkConnectionsMigrator.swift
90.90% <ø> (ø)

...rless/Common/Network/JSONRPC/WebSocketEngine.swift
0.00% <0.00%> (ø)

...n/Network/WalletNetworkFacade+MinimalBalance.swift
0.00% <0.00%> (ø)

... and 148 more

authors: codecov-commenter stas-litvinov

repo: soramitsu/fearless-iOS


text:
Allow us to silence type alias related runtime errors

Problem
https://sorbet.run/#require 'sorbet-runtime'

module Contracts
  class Maybe
  end
end

class A
  extend T%3A%3ASig

  X %3D Contracts%3A%3AMaybe.new

  sig {returns(X)}
  def self.foo
  end
end

A.foo
I'd like to use failure overrides to prevent this from erroring in production when this code is executed.
Proposed solution
I'd like this to be caught by inline_type_error_handler

I don't think this should piggy back on inline_type_error_handler, but i'm fine either using something like sig_builder_error_handler or introducing a new error handler for T::Utils.coerce

More generally we might want to audit all uses of raise in sorbet-runtime and replace them with calls to T::Configuration error handlers, or ensure that if they're using raise that they're raising a specific exception class (i.e., no RuntimeError / raise "foo") and that that specific error class is rescued by calling a T::Configuration handler.

Is this another instance of the same issue?
I have the following issue which caused some production paths to be broken despite the runtime error overrides:
Incompatible return type in override of method `METHOD_NAME`:\n* Base: `String` (in #\u003cClass:BASE_CLASS\u003e at /var/www/app/services/path_to_base_class.rb:13)\n* Override: `NilClass` (in #\u003cClass:CHILD_CLASS\u003e at /var/www/app/services/path_to_child_class.rb:19)\n(The types must be covariant.)

authors: AlexEvanczuk jez

repo: sorbet/sorbet


text:
Don't overwrite sorbet/config file if one already exists

Motivation

This should help people to run srb init more aggressively.
Test plan

I confirmed that the test I wrote failed before my change:
https://buildkite.com/sorbet/sorbet/builds/4496#28512d46-e01e-432f-aa97-3e5a59b80f39/281-311

👍

authors: DarkDimius jez


text:
生成されたコメントDOMの後始末をする

このままだとブラウザが死んでしまう
comments.jsxのコメントアウトを外して調整でおk

done


text:
Load (human) chess play data

Hi, first of all thank you very much for your work on Pgx!
I'm opening this issue because I am hoping to be able to leverage Pgx's chess environment for a project on scaling laws in RL. As part of this project, I would like to load some large scale supervised learning data (obtained from various sources, including Lichess, CCRL and a few others) for supervised training of an AlphaZero-like model which will later continue training through AlphaZero-like self-play as you implemented in one of the examples.
I was wondering whether you have thoughts/advice/help when it comes to making that data (all in the form of PGN files) available for use with Pgx. Within the chess environment there are _from_fen and _to_fen, but according to this issue these are neither supposed to be exposed to the user nor well-tested. Further, the issue says that there are no plans for such a feature at the moment. For Go as far as I can tell there was interest in having such an option.
How would you recommend an user make an existing PGN file usable for supervised learning in a format compatible with Pgx's? If there are no plans for such a feature I would really appreciate any help/advice/general tips or resources. Thanks!

Something like OpenSpiel ParseSANMove would be really helpful.

Hi, sorry for the late response and thank you for the request!
Given your request, we added from_fen/to_fen to public (but experimental API).
So far, you can use them like
from pgx.experimental.chess import from_fen, to_fen

state = from_fen("k7/8/8/8/2N5/8/P7/7K w - - 0 1")
print(to_fen(state))

Note that they are still subject to (large) changes.
Please let me know if you find any bug or problem.
Currently, we only support fen format.
Does it enough for your use case?
We suppose you can convert other formats to fen format with some other libraries (but not sure).
You can use them by install pgx from latest main branch (2.1.0-rc0).
pip install git+ssh://git@github.com/sotetsuk/elf-opengo-jax.git

or
pip install git+https://github.com/sotetsuk/elf-opengo-jax.git

Thank you, this is a really useful addition. One aspect that is still missing (please correct me if I'm wrong) though is an efficient way to also parse the moves themselves, like OpenSpiel's ParseSANMove. Of course these can be obtained by e.g. checking all potential moves and checking which ones match the FEN of the successive state, but it would be helpful to have a dedicated method for that.

Hi! Thank you for your comment!
Yeah I agree that it's useful but so far we don't have a plan to implement it.
I'll keep this PR open and contributions are welcome.
Someone who want this feature may add it to experimental like from_fen and to_fen

repo: sotetsuk/pgx


text:
Multiple SMS for a share

If a share price has been increased more than the defined limit, each time the code runs SMS will be sent. This should be avoided.

Possible suggestions:

Send SMS uniquely for each time the share price crosses on the multiples of the defining_limit.

Plan to solve:

Set a flag and changed percentage if the share has been notified for the first time in a day.
Reset all the flags and percentages EOD.
Check the share's flag --> If set check if the price changed more than the set second_defining_limit.


text:
Uneven Footer Section

Description:
The footer sections do not have grid layout, the sections are unevenly placed
Image:

@soumita1234 please assign this issue to me under the label LGM-SOC