text:
[Bug]: DrizzleSQLiteAdapter type error breaks build

Package
@lucia-auth/session-drizzle
Describe the bug
Not sure which exactly package started to cause the issue, since I had none before, but after I removed lock file, the error appeared:

const adapter = new DrizzleSQLiteAdapter(db, session, user) // here's on session

---

import { drizzle } from "drizzle-orm/libsql"
import { createClient } from "@libsql/client"
import * as schema from "@/lib/db/schema"

export const client = createClient({
  url: process.env.TURSO_CONNECTION_URL!,
  authToken: process.env.TURSO_AUTH_TOKEN!
})

export const db = drizzle(client, {
  schema
})

---

export const session = sqliteTable("session", {
  id: text("id").notNull().primaryKey(),
  userId: text("user_id")
    .notNull()
    .references(() => user.id, {
      onDelete: "cascade"
    }),
  expiresAt: integer("expires_at").notNull(),
  authenticated: integer("authenticated", { mode: "boolean" })
})

Argument of type 'SQLiteTableWithColumns<{ name: "session"; schema: undefined; columns: { id: SQLiteColumn<{ name: "id"; tableName: "session"; dataType: "string"; columnType: "SQLiteText"; data: string; driverParam: string; notNull: true; hasDefault: false; enumValues: [...]; baseColumn: never; }, object>; userId: SQLiteColumn<...>; ...' is not assignable to parameter of type 'SQLiteSessionTable'.
  Type 'SQLiteTableWithColumns<{ name: "session"; schema: undefined; columns: { id: SQLiteColumn<{ name: "id"; tableName: "session"; dataType: "string"; columnType: "SQLiteText"; data: string; driverParam: string; notNull: true; hasDefault: false; enumValues: [...]; baseColumn: never; }, object>; userId: SQLiteColumn<...>; ...' is not assignable to type 'SQLiteTable<{ dialect: any; columns: { id: SQLiteColumn<{ dataType: any; notNull: true; enumValues: any; tableName: any; columnType: any; data: string; driverParam: any; hasDefault: false; name: any; isPrimaryKey: any; isAutoincrement: any; hasRuntimeDefault: any; generated: any; }, object>; expiresAt: SQLiteColumn<...'.
    The types of '_.config.columns.id' are incompatible between these types.
      Type 'SQLiteColumn<{ name: "id"; tableName: "session"; dataType: "string"; columnType: "SQLiteText"; data: string; driverParam: string; notNull: true; hasDefault: false; enumValues: [string, ...string[]]; baseColumn: never; }, object>' is not assignable to type 'SQLiteColumn<{ dataType: any; notNull: true; enumValues: any; tableName: any; columnType: any; data: string; driverParam: any; hasDefault: false; name: any; isPrimaryKey: any; isAutoincrement: any; hasRuntimeDefault: any; generated: any; }, object>'.
        Type '{ name: "id"; tableName: "session"; dataType: "string"; columnType: "SQLiteText"; data: string; driverParam: string; notNull: true; hasDefault: false; enumValues: [string, ...string[]]; baseColumn: never; }' is missing the following properties from type '{ dataType: any; notNull: true; enumValues: any; tableName: any; columnType: any; data: string; driverParam: any; hasDefault: false; name: any; isPrimaryKey: any; isAutoincrement: any; hasRuntimeDefault: any; generated: any; }': isPrimaryKey, isAutoincrement, hasRuntimeDefault, generatedts(2345)

I have no idea what is happening here, and how to fix it. Tried to lock older versions, still error.
Using next, drizzle, turso/libsql

This is probably because you're using an older version of Drizzle, and that's unfortunately what happens when we built stuff on top off pre-1.0 libraries. It's only a type issue right?

@pilcrowOnPaper here I managed to find my older lock file version and reinstalled deps, now it works. Drizzle version changed from 0.31.2 to 0.31.4. Not sure if it was causing the issue (didn't found anything breaking in  their Changelog). here's a diff
dependencies:
- @lucia-auth/adapter-drizzle 1.1.0
+ @lucia-auth/adapter-drizzle 1.0.7
- arctic 1.9.2
+ arctic 1.9.1
- drizzle-orm 0.31.4
+ drizzle-orm 0.31.2
- posthog-js 1.155.4
+ posthog-js 1.139.5
- posthog-node 4.1.0
+ posthog-node 4.0.1
- react 18.3.1
+ react 18.2.0
- react-dom 18.3.1
+ react-dom 18.2.0
- resend 3.5.0
+ resend 3.4.0

devDependencies:
- @types/node 20.14.15
+ @types/node 20.12.2
- @types/react 18.3.3
+ @types/react 18.2.73
- @types/react-dom 18.3.0
+ @types/react-dom 18.2.23
- autoprefixer 10.4.20
+ autoprefixer 10.4.19
- clsx 2.1.1
+ clsx 2.1.0
- esbuild-register 3.6.0
+ esbuild-register 3.5.0
- postcss 8.4.41
+ postcss 8.4.38
- tailwindcss 3.4.10
+ tailwindcss 3.4.3
- typescript 5.5.4
+ typescript 5.4.3

Same problem here after upgrading @lucia-auth/adapter-drizzle" from ^1.0.7 to ^1.1.0. All others packages stay the same version, Drizzle included.
Downgrading back to ^1.0.7 fixes the type error for session table.

I should probably reopen this, so @pilcrowOnPaper could decide on closing by himself.

Probably related as downgrading from 1.1.0 to 1.0.7 also fixes this for the Postgres Drizzle adapter: https://github.com/lucia-auth/lucia/issues/1462#issuecomment-2312606043. It seems like these extra keys in the type definitions of the columns of *SessionTable and *UserTable are the cause of the TypeScript error:
isPrimaryKey: any;
isAutoincrement: any;
hasRuntimeDefault: any;
generated: any;

This is the base type for columns in
// drizzle pg-core types

export declare abstract class PgColumn<T extends ColumnBaseConfig<ColumnDataType, string> = ColumnBaseConfig<ColumnDataType, string>, TRuntimeConfig extends object = {}, TTypeConfig extends object = {}> extends Column<T, TRuntimeConfig, TTypeConfig & {
    dialect: 'pg';
}> {
    readonly table: PgTable;
    static readonly [entityKind]: string;
    constructor(table: PgTable, config: ColumnBuilderRuntimeConfig<T['data'], TRuntimeConfig>);
}

// drizzle types

export declare const entityKind: unique symbol;

export interface ColumnBuilderBaseConfig<TDataType extends ColumnDataType, TColumnType extends string> {
    name: string;
    dataType: TDataType;
    columnType: TColumnType;
    data: unknown;
    driverParam: unknown;
    enumValues: string[] | undefined;
}

export interface ColumnBaseConfig<TDataType extends ColumnDataType, TColumnType extends string> extends ColumnBuilderBaseConfig<TDataType, TColumnType> {
    tableName: string;
    notNull: boolean;
    hasDefault: boolean;
}

export declare abstract class Column<T extends ColumnBaseConfig<ColumnDataType, string> = ColumnBaseConfig<ColumnDataType, string>, TRuntimeConfig extends object = object, TTypeConfig extends object = object> implements DriverValueMapper<T['data'], T['driverParam']>, SQLWrapper {
    readonly table: Table;
    static readonly [entityKind]: string;
    readonly _: ColumnTypeConfig<T, TTypeConfig>;
    readonly name: string;
    readonly primary: boolean;
    readonly notNull: boolean;
    readonly default: T['data'] | SQL | undefined;
    readonly defaultFn: (() => T['data'] | SQL) | undefined;
    readonly onUpdateFn: (() => T['data'] | SQL) | undefined;
    readonly hasDefault: boolean;
    readonly isUnique: boolean;
    readonly uniqueName: string | undefined;
    readonly uniqueType: string | undefined;
    readonly dataType: T['dataType'];
    readonly columnType: T['columnType'];
    readonly enumValues: T['enumValues'];
    protected config: ColumnRuntimeConfig<T['data'], TRuntimeConfig>;
    constructor(table: Table, config: ColumnRuntimeConfig<T['data'], TRuntimeConfig>);
    abstract getSQLType(): string;
    mapFromDriverValue(value: unknown): unknown;
    mapToDriverValue(value: unknown): unknown;
}

And the type definition for the adapter is
PgColumn<{
  dataType: any;
  notNull: true;
  enumValues: any;
  tableName: any;
  columnType: any;
  data: string;
  driverParam: any;
  hasDefault: false;
  name: any;
  isPrimaryKey: any;
  isAutoincrement: any;
  hasRuntimeDefault: any;
  generated: any;
}, object>;

So yep it's just some extra fields that don't exist on T which should extend ColumnBaseConfig and ColumnBuilderBaseConfig.
Looking at the constraints in @lucia-auth/adapter-drizzle it's specifying "drizzle-orm": ">= 0.29 <1" and my version is at 0.31.2. I'm guessing one of the 0.3x.x releases changed they types around a bit.

export const session = sqliteTable("session", {
id: text("id").primaryKey(),
userId: text("user_id")
.notNull()
.references(() => user.id, {
onDelete: "cascade"
}),
expiresAt: integer("expires_at").notNull(),
authenticated: integer("authenticated", { mode: "boolean" })
})
i fixed this by removing notNull() from id, (with latest drizzle-orm and latest adapter

authors: bdrtsky iekilinc jxh0414com pilcrowOnPaper redbaron76 richardvanbergen

repo: lucia-auth/lucia


text:
Links to original tf code - fyi

After reading deepmind blog post I was looking forward to downloading model but no luck. Looking forward to your implementation.
You may be aware of this post and link but if not this is the coder's original tf implementation. Hope it helps.
Copy of comment to original model request:
https://github.com/huggingface/transformers/issues/4688
Interested in model weights too but currently not available. Author does mention releasing tf code here:
https://news.ycombinator.com/item?id=22290227
Requires tf 1.15+ and deepmind/sonnet ver 1.36. Link to python script here:
https://github.com/deepmind/sonnet/blob/cd5b5fa48e15e4d020f744968f5209949ebe750f/sonnet/python/modules/nets/transformer.py#L915
Have tried running as-is but doesn't appear to have options for training on custom data as per the paper and available data sets.

@GenTxt it should be fairly straightforward to implement! i'll get it done, and leave it to someone else with more resources to train and share a model
i'll be adding a bunch of features I learned from building other types of transformers to further enhance it as well

@GenTxt This is almost ready! Do you plan on training this on any text corpus? Perhaps pg19?

@GenTxt https://github.com/huggingface/nlp/pull/306 Once this is merged, it should be easy to start training

@GenTxt works great on enwik8 now, you should totally try this! are you a coder? or do you need this simplified even more?

Hi Phil:
Thanks for the updates. Currently running the ewik8 train.py on my home
machine and terminal output looks good.
Have a few questions:

Where is reference to 100000 epochs or iterations in train.py?

e.g.
training loss: 2.4765 | aux_loss: 0.9664
training:   0%|                         | 70/100000 [05:45<129:44:50,
4.67s/it]training loss: 2.4784 | aux_loss: 0.0000
training loss: 2.4343 | aux_loss: 0.0000

Does it save the model/weights at the end of 100000?

How to use a simple text file e.g. corpus.txt (1 sentence per line)
instead of ewik8.gz ?

Can 'train.py' be modified as separate generation script for saved model
above?

How to modify for using a multi-line input text file as start tokens?

prime = torch.ones(1, 1).cuda() # assume 1 is start token OR input.txt
Not a coder but I can make basic modifications to scripts. Would like to
see pg19 model but don't have the $ resources to train.
Thanks
On Sat, Jul 4, 2020 at 2:26 PM Phil Wang notifications@github.com wrote:

@GenTxt https://github.com/GenTxt works great on enwik8 now, you should
totally try this! are you a coder? or do you need this simplified even more?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lucidrains/compressive-transformer-pytorch/issues/1#issuecomment-653797356,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFMAWPPPZJFKI6SP4EHLUE3RZ5X5LANCNFSM4OKBSFNQ
.

Where is reference to 100000 epochs or iterations in train.py?

it's actually iterations, not epochs

Does it save the model/weights at the end of 100000?

nope, but that can be easily added!

How to use a simple text file e.g. corpus.txt (1 sentence per line)
instead of ewik8.gz ?

that will take some work to setup, specifically you will have to write your own Dataset class. let me think about how to abstract this away though!

Can 'train.py' be modified as separate generation script for saved model above?

ahh yeah kind of, let me think about how to abstract this away as well. I'm thinking about something kind of like my stylegan2-pytorch repository, a commandline tool that lets you train, resume training, and generate easily

How to modify for using a multi-line input text file as start tokens?

yea, that will take some coding

Would like to see pg19 model but don't have the $ resources to train.

i'll setup training for PG19 soon-ish, and perhaps there will be some generous, curious person out there who will train it for us lol

I have some experience pre-training BERT style models on custom subsets of PG, and access to lots of academic GPU time. Not to mention generous, and curious :D
@lucidrains would you like to collaborate on pre-training a Compressive Transformer?

@lucidrains Hey Phil,
Great work with getting the implementation out in such a short amount of time.
I was trying to replicate the results of the paper and ran into a few issues.
I was trying to find how to calculate the final BPC score but could not find it as part of the current repository. Is that something you plan to add in the near future or open to a contribution from my side about the same?
There are also other smaller improvements which I believe can help make the repository better. Please let me know what you think about them

I did not find save model code anywhere - Adding that would be great

Making use of multiple GPUs for faster training - as of now I think only 1 GPU is being used and extending it to use multiple GPUs would help in making the training faster

source: gharchive/issue

authors: DarrenAbramson GenTxt RajeshDM lucidrains

license: MIT

license_type: permissive

license_source: github-api


text:
Support to  Analytic-DPM and DPM-Solver

Hi Phil, thanks again for the great job!
Recently, Analytic-DPM and DPM-Solver, proposed optimal analytical solutions and better sampling methods, respectively.
Would you mind considering adding them to this repo?
Best regards

@lhaippp hey thanks Li! hmm, are you sure dpm-solver works? if it does work, wouldn't stable diffusion be using it?

@lhaippp famous last words
the majority of papers don't live up to their lofty claims

@lhaippp ok, you find a couple researchers or deep learning practitioners that can give good testimonies and i'll look into it

@lhaippp i'm in touch with the people behind stable diffusion, and none of them told me about dpm solver, and usually they are on top of things

@lhaippp verifying is a good idea :) most papers do not end up working as advertised, or has some catch

@lhaippp hey Li, i actually heard from someone i trust that dpm solver
will look into it this week

@lucidrains hi Phil, that's awesome! Look forward

I've got an implementation of DPM-Solver++ in combo with Elucidated Diffusion working with this repo. If interested I can make a pull-request

@Mut1nyJD omg, that would be amazing! so dpm-solver++ is working for you then?

@Mut1nyJD i'm confused, how could dpm-solver++ be compatible with elucidated sampling?

@Mut1nyJD omg, that would be amazing! so dpm-solver++ is working for you then?

Yeah it works at least on the model I've trained.  Katherine Crowson made it compatible with Elucidated sampling what she calls k-diffusion (k for Karras).
I will clean it up and submit a pull request.

@Mut1nyJD thanks for relaying this! ugh, i'm missing out not being on discord

@lucidrains
No problem you're welcome! It is hard to keep up with all the developments.
What I am personal curious is would be the addition of flash attention do you think that would work? And would it have any benefit to linear attention that is mostly used right now
And the other one is Self-Attention-Guidance (https://github.com/PnDong/Self-Attention-Guidance)

@Mut1nyJD yup, flash attention will be better than linear attention, although you will still face quadratic compute price
without reading the paper, is self attention guidance for better binding to text?

@lucidrains Yeah but should be still faster than full attention? Is your flash attention mature enough to try?
Well I guess you could also use the cross attention I am sure they are working on that but this paper/implementation is primarily about the general self attention layers so as far as I understood it is for unsupervised and maybe class supervised diffusion

@Mut1nyJD yup, under certain conditions it is faster
my flash attention repository is using cosine similarity, and unfortunately Robin had some failed experiments trying it out, i can't recommend it until more validation is done. good news is that flash attention will eventually be offered in pytorch! it will probably mature by v2.1
oh! 🤦 yes i got confused
just scanned the diagrams of the paper and i like it! thank you for mentioning it, may try it out when i find time

@Mut1nyJD what would happen if self attention guidance were applied to a language model?

@lucidrains

my flash attention repository is using cosine similarity, and unfortunately Robin had some failed experiments using it, so i can't recommend it until more validation is done. good news is that flash attention will eventually be offered in pytorch!

Ok thank you for the feedback. I will have a look at the official pytorch implementation. Although I due tend to be back a version from current main release 😄

oh! 🤦 yes i got confused
just scanned the diagrams of the paper and i like it! thank you for mentioning it, may try it out when i find time

Yeah looks like an interesting not too expansive improvement. That's great I will try my best as well to decipher it let you know if I got something if you haven't beaten me by then 😄

closing because of https://github.com/lucidrains/denoising-diffusion-pytorch/pull/148

authors: Mut1nyJD lhaippp lucidrains

repo: lucidrains/denoising-diffusion-pytorch


text:
AssertionError: if using tf gamma, only sequence length of 1536 allowed for now

@lucidrains I think this is not getting set properly. As per the doc it says from_pretrained should set the use_tf_gamma. Then the pre trained model should be able to accept seqlength of 196_608 ? or am I missing something ?
import torch
import polars as pl
from torch import nn
from enformer_pytorch import from_pretrained,GenomeIntervalDataset
from enformer_pytorch.finetune import HeadAdapterWrapper

enformer = from_pretrained('EleutherAI/enformer-official-rough')

enformer(seq) #seq of length 196_680

get the AssertionError with above

hmm, I'm getting a similar error:
AssertionError: if using tf gamma, only sequence length of 1536 allowed for now

@jerome-f – how did you fix this?

nevermind ... I had to add use_tf_gamma = False to the from_pretrained() function!

authors: abearab jerome-f

repo: lucidrains/enformer-pytorch


text:
Support hive2.2 ？

HI， for some reason i have to compile hive2.2 from github source codes,  I have did it ,  Now i want to use hive-solr t process my datas,  Is this support hive2.2 ? thans for your help.

Hive 2 is not expected to be supported until sometime this Summer.

authors: ctargett jhkkhtd

repo: lucidworks/hive-solr


text:
添加一个竖屏模式吧

预期行为
下方的导航栏添加一个竖屏刷
点进去就可以像抖音一样刷视频了
功能描述
像抖音一样刷视频
补充说明
什么双击点赞等等都想要

想要竖屏模式为什么不去用官方客户端呢，多少人放弃官方客户端就是因为强加的竖屏模式和抖音like UI，居然还有人想要抖音样式的，绝

那不是B站

那你为什么不直接用官版呢？


text:
Error enabling plugin LuckPerms

logs
https://gist.github.com/mat41997/20306c6f58a260295a9cce566e7e63c3
BungeeCord
https://github.com/HexagonMC/BungeeCord/releases
config
https://gist.github.com/mat41997/ab48920584fa29ce808125c2f7ee32f8
plugins
http://i.imgur.com/Hwz1DkA.png

You're not using the BungeeCord version of the plugin.

repo: lucko/LuckPerms


text:
gtags-cscope job failed on Neovim

Describe the bug
Open a c file with neovim, got this error:

Steps to reproduce

Open a file under root marker (gutentags_project_root)
view error messages, show above

Share your setup

What OS and version of Vim are you using?
Windows10, Neovim 0.4-434
What version of ctags, gtags, or whatever do you have installed?
gtags: 6.6.3; ctags: universal ctags 6fd7f3e9
Are you using g:gutentags_cache_dir?
let g:gutentags_cache_dir = expand('./.tags')

Post the logs

Run :let g:gutentags_trace = 1.
Reproduce the bug.
Run :messages and show the messages that Gutentags posted.
Look for the tags.log file that Gutentags' script left behind, and post its contents.
I can not find the tags.log.

Additional context
Add any other context about the problem here.

Hi!
I can't reproduce the bug so far... and I'm wondering why you have all those garbage characters in the job output. Could you try running gtags by hand in the same way Gutentags does?
If you check those messages you'll see it runs gtags --incremental "C:\Users\ryan\.cache\tags\D--cJSON-" from the D:\cJSON directory.

I'm not sure what's the "same way Gutentags does"? Run gtags and global in shell is OK. It works well on gvim with same configs. so, i think it's relative to Neovim.

The "same way Gutentags does" was about manually running that command line I took from your screenshot: gtags --incremental "C:\Users\ryan\.cache\tags\D--cJSON-"
It looks like when you run it from Neovim, gtags is somehow running into invalid input -- you can see that amidst all the weird garbage characters it's also raising UnexpectedToken errors and such... as such, the gtags process exits with an error code, and Gutentags reports it to you. I have no idea why it would be different in Neovim... if running the above command line by hand doesn't reproduce the errors, then maybe there's some other issue, like maybe Neovim runs with a different environment that makes Gutentags run an unexpected version of gtags, or using an unexpected encoding, or something...

Can u prinr ur configuration? I should konw how it is.

manual run the cmd gen the G* files in ~/.config/tags successfully.
however in neovim it gens files with 0kb.
    8 " change focus to quickfix window after search (optional).
    7 let g:gutentags_plus_switch = 1
    6 let g:gutentags_define_advanced_commands = 1
    5
    4 let g:gutentags_exclude_filetypes = ['l']
    3 let $GTAGSLABEL = 'native-pygments'
    2 "let $GTAGSLABEL = 'pygments'
    1 "let $GTAGSLABEL = 'native'
  172 let $GTAGSCONF = '/usr/local/share/gtags/gtags.conf'
    1
    2 let g:gutentags_project_root = ['.root', '.svn', '.git', '.hg', '.project']
    3
    4
    5
    6 let g:gutentags_ctags_tagfile = '.tags'
    7
    8
    9 let g:gutentags_modules = ['gtags_cscope']
   10 "let g:gutentags_modules = []
   11 "if executable('ctags')
   12 "¦  let g:gutentags_modules += ['ctags']
   13 "endif
   14 "if executable('gtags-cscope') && executable('gtags')
   15 "¦  let g:gutentags_modules += ['gtags_cscope']
   16 "endif
   17
   18
   19 let g:gutentags_cache_dir = expand('~/.cache/tags')
   20

authors: SurpassAll ilovin ludovicchabant xaljer

repo: ludovicchabant/vim-gutentags

license: mit

license_source: bigquery


text:
feat: split implementation in two classes

[BREAKING CHANGES] QvaPayClient was divided into two classes: AsyncQvaPayClient and SyncQvaPayClient. Both classes have the same methods and properties, with the difference that the methods in AsyncQvaPayClient are asynchronous and in SyncQvaPayClient are synchronous.
The _sync folders were generated automatically executing the command unasync qvapay tests.
The code that is added in the _async folders is automatically transformed.
So every time to make a change you must run the command unasync qvapay tests to regenerate the folders _sync with the synchronous version of the implementation.
Improve tests implementation and add pre-commit system to ensure format and style.

@leynier sorry for the delay, I didn't see any notification related to this. Checking it now.

source: gharchive/pull-request

authors: leynier lugodev

repo: lugodev/qvapay-python


text:
new release on pypi

We should make a release to be uploaded on pypi

[x] update documentation (see #74)
[x] add requirements into pyproject.toml
[ ] add versions also to requirements.txt?
[ ] update installation instructions for colab
[x] code formatted with black
[ ] decide which version (major/minor/patch) to release? 0.3.1 or 0.4.0 or 1.0.0alpha?

closed by #80

repo: luigibonati/mlcolvar


text:
Update redis-commands version to 1.5.0

Please update redis-commands version to 1.5.0, which correctly supports redis streams

Hello @luin ,
could you update also npm ? Or it's on purpose ?

Thanks

v4.10.0 has been released under latest tag.

authors: borsucok fas3r luin

repo: luin/ioredis


text:
Update Gods.py

Added new god Tiamat

Thanks! <3


text:
getting Error : Wrong type: Marked object is wrong type (boolean)

while running the transistor dataset example using command :
transistors --stg-temp-min --stg-temp-max --polarity --ce-v-max --parse --first-time --max-docs 500 --parallel 4 --conn-string="postgresql://:@:/transistors"
I am getting error for each step. Below is the error message while the process is still running.
Can someone explain it why this is happening. I have followed all installation steps as it is.
OS: Ubuntu18
Python Version: 3.6.1
Error --
/softwares/anaconda3/lib/python3.6/site-packages/spacy/data/en
You can now load the model via spacy.load('en')
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 119/119 [01:53<00:00,  1.15s/it]
 81%|██████████████████████████████████████████████████████████████████████████████████████████████████████████▌                        | 61/75 [01:04<00:11,  1.23it/s]Syntax Error: Marked object is wrong type (boolean)
Syntax Error: Marked object is wrong type (boolean)
100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 75/75 [01:15<00:00,  1.62it/s]
  0%|                                                                                | 0/500 [00:00<?, ?it/s]Syntax Error: Expected the default config, but wasn't able to find it, or it isn't a Dictionary
Syntax Error: Expected the default config, but wasn't able to find it, or it isn't a Dictionary
Syntax Error: Expected the default config, but wasn't able to find it, or it isn't a Dictionary
Syntax Error: Expected the default config, but wasn't able to find it, or it isn't a Dictionary
Syntax Error: Expected the default config, but wasn't able to find it, or it isn't a Dictionary
Syntax Error: Expected the default config, but wasn't able to find it, or it isn't a Dictionary
Syntax Error: Expected the default config, but wasn't able to find it, or it isn't a Dictionary
Syntax Error: Expected the default config, but wasn't able to find it, or it isn't a Dictionary
 27%|██████████████████████████████████▌                                                                                | 134/500 [02:59<05:17,  1.15it/s]Internal Error: xref num 0 not found but needed, try to reconstruct<0a>
Syntax Error: font resource is not a dictionary
Syntax Error: Failed to parse XRef entry [70].
Syntax Error: Failed to parse XRef entry [71].
Syntax Error: Failed to parse XRef entry [72].
Syntax Error: Failed to parse XRef entry [73].
Syntax Error: Failed to parse XRef entry [74].
Syntax Error: Failed to parse XRef entry [75].
Syntax Error: Failed to parse XRef entry [76].
Syntax Error: Failed to parse XRef entry [77].
Syntax Error: Failed to parse XRef entry [78].
Syntax Error: Failed to parse XRef entry [79].
Syntax Error: Failed to parse XRef entry [80].
Syntax Error: Failed to parse XRef entry [81].
Syntax Error: Failed to parse XRef entry [82].
Syntax Error: Failed to parse XRef entry [83].
Syntax Error: Failed to parse XRef entry [84].
Syntax Error: Failed to parse XRef entry [85].
Syntax Error: Failed to parse XRef entry [86].
Syntax Error: Failed to parse XRef entry [87].
Syntax Error: Failed to parse XRef entry [88].
Syntax Error: Failed to parse XRef entry [89].
Syntax Error: Failed to parse XRef entry [90].
Syntax Error: Failed to parse XRef entry [91].
Syntax Error: Failed to parse XRef entry [92].
Syntax Error: Failed to parse XRef entry [93].
Syntax Error: Failed to parse XRef entry [94].
Syntax Error: Failed to parse XRef entry [95].
Syntax Error: Failed to parse XRef entry [96].
Syntax Error: Failed to parse XRef entry [97].
Syntax Error: Failed to parse XRef entry [98].
Syntax Error: Failed to parse XRef entry [99].
Syntax Error: Failed to parse XRef entry [100].
Syntax Error: Failed to parse XRef entry [101].
Syntax Error: Failed to parse XRef entry [102].
Syntax Error: Failed to parse XRef entry [103].
Syntax Error: Failed to parse XRef entry [104].
Syntax Error: Failed to parse XRef entry [105].
Syntax Error: Failed to parse XRef entry [106].
Syntax Error: Failed to parse XRef entry [107].
Syntax Error: Failed to parse XRef entry [108].
Syntax Error: Failed to parse XRef entry [109].
Syntax Error: Failed to parse XRef entry [110].
Syntax Error: Failed to parse XRef entry [111].
Syntax Error: Failed to parse XRef entry [112].
Syntax Error: Failed to parse XRef entry [113].
Syntax Error: Failed to parse XRef entry [114].
Syntax Error: Failed to parse XRef entry [115].
Syntax Error: Failed to parse XRef entry [116].
Syntax Error: Failed to parse XRef entry [117].
Syntax Error: Failed to parse XRef entry [118].
Syntax Error: Failed to parse XRef entry [119].
Syntax Error: Failed to parse XRef entry [120].
Syntax Error: Failed to parse XRef entry [121].
Syntax Error: Failed to parse XRef entry [122].
Syntax Error: Failed to parse XRef entry [123].
Syntax Error: Failed to parse XRef entry [124].
Syntax Error: Failed to parse XRef entry [125].
Syntax Error: Failed to parse XRef entry [126].
Syntax Error: Failed to parse XRef entry [127].
Syntax Error: Failed to parse XRef entry [128].
Syntax Error: Failed to parse XRef entry [129].
Syntax Error: Failed to parse XRef entry [130].
Syntax Error: Failed to parse XRef entry [131].
Syntax Error: Failed to parse XRef entry [132].
Syntax Error: Failed to parse XRef entry [133].
Syntax Error: Failed to parse XRef entry [134].
Syntax Error: Failed to parse XRef entry [135].
Syntax Error: Failed to parse XRef entry [136].
Syntax Error: Failed to parse XRef entry [137].
Syntax Error: Failed to parse XRef entry [138].
Syntax Error: Failed to parse XRef entry [139].
Syntax Error: Failed to parse XRef entry [140].
Syntax Error: Failed to parse XRef entry [141].
Syntax Error: Failed to parse XRef entry [142].
Syntax Error: Failed to parse XRef entry [143].
Syntax Error: Failed to parse XRef entry [144].
Syntax Error: Failed to parse XRef entry [145].
Syntax Error: Failed to parse XRef entry [146].
Syntax Error: Failed to parse XRef entry [147].
Syntax Error: Failed to parse XRef entry [148].
Syntax Error: Failed to parse XRef entry [149].
Syntax Error: Failed to parse XRef entry [150].
Syntax Error: Failed to parse XRef entry [151].
Syntax Error: Failed to parse XRef entry [152].
Syntax Error: Failed to parse XRef entry [153].
Syntax Error: Failed to parse XRef entry [154].
Syntax Error: Failed to parse XRef entry [155].
Syntax Error: Failed to parse XRef entry [156].
Syntax Error: Failed to parse XRef entry [157].
Syntax Error: Failed to parse XRef entry [158].
Syntax Error: Failed to parse XRef entry [159].
Syntax Error: Failed to parse XRef entry [160].
Syntax Error: Failed to parse XRef entry [161].
Syntax Error: Failed to parse XRef entry [162].
Syntax Error: Failed to parse XRef entry [163].
Syntax Error: Failed to parse XRef entry [164].
Syntax Error: Failed to parse XRef entry [165].
Syntax Error: Failed to parse XRef entry [166].
Syntax Error: Failed to parse XRef entry [167].
Syntax Error: Failed to parse XRef entry [168].
Syntax Error: Failed to parse XRef entry [169].
Syntax Error: Failed to parse XRef entry [170].
Syntax Error: Failed to parse XRef entry [171].
Syntax Error: Failed to parse XRef entry [172].
Syntax Error: Failed to parse XRef entry [173].
Syntax Error: Failed to parse XRef entry [174].
Syntax Error: Failed to parse XRef entry [175].
Syntax Error: Failed to parse XRef entry [176].
Syntax Error: Failed to parse XRef entry [177].
Syntax Error: Failed to parse XRef entry [178].
Syntax Error: Failed to parse XRef entry [179].
Syntax Error: Failed to parse XRef entry [180].
Syntax Error: Failed to parse XRef entry [181].
Syntax Error: Failed to parse XRef entry [182].
Syntax Error: Failed to parse XRef entry [183].
Syntax Error: Failed to parse XRef entry [184].
Syntax Error: Failed to parse XRef entry [185].
Syntax Error: Failed to parse XRef entry [186].
Syntax Error: Failed to parse XRef entry [187].
Syntax Error: Failed to parse XRef entry [188].
Syntax Error: Failed to parse XRef entry [189].
Syntax Error: Failed to parse XRef entry [190].
Syntax Error: Failed to parse XRef entry [191].
Syntax Error: Failed to parse XRef entry [192].
Syntax Error: Failed to parse XRef entry [193].
Syntax Error: Failed to parse XRef entry [194].
Syntax Error: Failed to parse XRef entry [195].
Syntax Error: Failed to parse XRef entry [196].
Syntax Error: Failed to parse XRef entry [197].
Syntax Error: Failed to parse XRef entry [198].
Syntax Error: Failed to parse XRef entry [199].
Syntax Error: Failed to parse XRef entry [200].
Syntax Error: Failed to parse XRef entry [201].
Syntax Error: Failed to parse XRef entry [202].
Syntax Error: Failed to parse XRef entry [203].
Syntax Error: Failed to parse XRef entry [204].
Syntax Error: Failed to parse XRef entry [205].
Syntax Error: Failed to parse XRef entry [206].
Syntax Error: Failed to parse XRef entry [207].
Syntax Error: Failed to parse XRef entry [208].
Syntax Error: Failed to parse XRef entry [209].
Syntax Error: Failed to parse XRef entry [210].
Syntax Error: Failed to parse XRef entry [211].
Syntax Error: Failed to parse XRef entry [212].
Syntax Error: Failed to parse XRef entry [213].
Syntax Error: Failed to parse XRef entry [214].
Syntax Error: Failed to parse XRef entry [215].
Syntax Error: Failed to parse XRef entry [216].
Syntax Error: Failed to parse XRef entry [217].
Syntax Error: Failed to parse XRef entry [218].
Syntax Error: Failed to parse XRef entry [219].
Syntax Error: Failed to parse XRef entry [220].
Syntax Error: Failed to parse XRef entry [221].
Syntax Error: Failed to parse XRef entry [222].
Syntax Error: Failed to parse XRef entry [223].
Syntax Error: Failed to parse XRef entry [224].
Syntax Error: Failed to parse XRef entry [225].
Syntax Error: Failed to parse XRef entry [226].
Syntax Error: Failed to parse XRef entry [227].
Syntax Error: Failed to parse XRef entry [228].
Syntax Error: Failed to parse XRef entry [229].
Syntax Error: Failed to parse XRef entry [230].
Syntax Error: Failed to parse XRef entry [231].
Syntax Error: Failed to parse XRef entry [232].
Syntax Error: Failed to parse XRef entry [233].
Syntax Error: Failed to parse XRef entry [234].
Syntax Error: Failed to parse XRef entry [235].
Syntax Error: Failed to parse XRef entry [236].
Syntax Error: Failed to parse XRef entry [237].
Syntax Error: Failed to parse XRef entry [238].
Syntax Error: Failed to parse XRef entry [239].
Syntax Error: Failed to parse XRef entry [240].
Syntax Error: Failed to parse XRef entry [241].
Syntax Error: Failed to parse XRef entry [242].
Syntax Error: Failed to parse XRef entry [243].
Syntax Error: Failed to parse XRef entry [244].
Syntax Error: Failed to parse XRef entry [245].
Syntax Error: Failed to parse XRef entry [246].
Syntax Error: Failed to parse XRef entry [247].
Syntax Error: Failed to parse XRef entry [248].
Syntax Error: Failed to parse XRef entry [249].
Syntax Error: Failed to parse XRef entry [250].
Syntax Error: Failed to parse XRef entry [251].
Syntax Error: Failed to parse XRef entry [252].
Syntax Error: Failed to parse XRef entry [253].
Syntax Error: Failed to parse XRef entry [254].
Syntax Error: Failed to parse XRef entry [255].
Syntax Error: Missing 'endstream' or incorrect stream length
Syntax Warning: Failed parsing hints table object
Internal Error: xref num 0 not found but needed, try to reconstruct<0a>
Syntax Error: font resource is not a dictionary
Internal Error: xref num 0 not found but needed, try to reconstruct<0a>
Syntax Error: font resource is not a dictionary
Internal Error: xref num 0 not found but needed, try to reconstruct<0a>
Syntax Error: font resource is not a dictionary
Internal Error: xref num 0 not found but needed, try to reconstruct<0a>
Syntax Error: font resource is not a dictionary
Internal Error: xref num 0 not found but needed, try to reconstruct<0a>
Syntax Error: font resource is not a dictionary
Internal Error: xref num 0 not found but needed, try to reconstruct<0a>
Syntax Error: font resource is not a dictionary
Internal Error: xref num 0 not found but needed, try to reconstruct<0a>
Syntax Error: font resource is not a dictionary
 46%|███████████████████████████████████████████████████████████▌                                                                     | 231/500 [04:35<03:23,  1.32it/s]Syntax Error: Marked object is wrong type (boolean)
 47%|█████████████████████████████████████████████████████████████▏                                                                   | 237/500 [04:41<04:34,  1.04s/it]Syntax Error: Marked object is wrong type (boolean)
 48%|█████████████████████████████████████████████████████████████▋                                                                   | 239/500 [04:43<04:21,  1.00s/it]Syntax Error: Marked object is wrong type (boolean)
 48%|██████████████████████████████████████████████████████████████▏                                                                  | 241/500 [04:45<04:26,  1.03s/it]Syntax Error: Marked object is wrong type (boolean)
 48%|██████████████████████████████████████████████████████████████▍                                                                  | 242/500 [04:46<04:36,  1.07s/it]Syntax Error: Marked object is wrong type (boolean)
 49%|██████████████████████████████████████████████████████████████▋                                                                  | 243/500 [04:46<04:05,  1.05it/s]Syntax Error: Marked object is wrong type (boolean)
 49%|███████████████████████████████████████████████████████████████▋                                                                 | 247/500 [04:49<03:15,  1.30it/s]Syntax Error: Marked object is wrong type (boolean)
 50%|███████████████████████████████████████████████████████████████▉                                                                 | 248/500 [04:51<03:47,  1.11it/s]Syntax Error: Marked object is wrong type (boolean)
 50%|████████████████████████████████████████████████████████████████▏                                                                | 249/500 [04:51<03:26,  1.21it/s]Syntax Error: Marked object is wrong type (boolean)
 50%|████████████████████████████████████████████████████████████████▊                                                                | 251/500 [04:52<02:57,  1.40it/s]Syntax Error: Marked object is wrong type (boolean)
Syntax Error: Marked object is wrong type (boolean)
 50%|█████████████████████████████████████████████████████████████████                                                                | 252/500 [04:53<03:34,  1.16it/s]Syntax Error: Marked object is wrong type (boolean)
 52%|███████████████████████████████████████████████████████████████████▌                                                             | 262/500 [04:59<02:26,  1.63it/s]Syntax Error: Marked object is wrong type (boolean)
 53%|████████████████████████████████████████████████████████████████████                                                             | 264/500 [05:01<02:40,  1.47it/s]Syntax Error: Marked object is wrong type (boolean)
 54%|█████████████████████████████████████████████████████████████████████▏                                                           | 268/500 [05:05<03:05,  1.25it/s]Syntax Error: Marked object is wrong type (boolean)
Syntax Error: Marked object is wrong type (boolean)
Syntax Error: Marked object is wrong type (boolean)
 54%|██████████████████████████████████████████████████████████████████████▏                                                          | 272/500 [05:09<03:06,  1.22it/s]Syntax Error: Marked object is wrong type (boolean)
Syntax Error: Marked object is wrong type (boolean)
 55%|███████████████████████████████████████████████████████████████████████▍                                                         | 277/500 [05:13<03:21,  1.11it/s]Syntax Error: Marked object is wrong type (boolean)
 57%|█████████████████████████████████████████████████████████████████████████▌                                                       | 285/500 [05:20<02:36,  1.38it/s]Syntax Error: Marked object is wrong type (boolean)
Syntax Error: Marked object is wrong type (boolean)
 57%|█████████████████████████████████████████████████████████████████████████▊                                                       | 286/500 [05:22<03:29,  1.02it/s]Syntax Error: Marked object is wrong type (boolean)
 58%|██████████████████████████████████████████████████████████████████████████▌                                                      | 289/500 [05:23<02:10,  1.62it/s]Syntax Error: Marked object is wrong type (boolean)

These errors are all errors from Fonduer that occur during parsing of the PDFs. The errors themselves come from poppler, which Fonduer calls.
Some errors are expected, since we do not ensure all of the input PDFs are perfectly formed. You should be able to continue through the pipeline regardless of these errors.

Thanks for the prompt response luke. Yeah the model did train but can you suggest some way to improve on these errors

These errors are just tied to the input PDF. If you wanted to eliminate them completely, you could, for example, run pdfinfo on all your input documents and prune away those that threw errors.
The workflow of fonduer assumes that the user does not have direct control over the authoring of the PDFs themselves. But, if you do, you could also try and debug the way that you are generating the PDFs to ensure that they can be read without errors by poppler-utils.

authors: AshutoshUpadhya lukehsiao


text:
Parsing code example does not compile

Hi Luke,
I think, in the parsing code example in the readme file there are same wrong variable names.
I have made them fat below:
String grammarSpecFilename = "arithmetic.grammar";
String inputFilename = "arithmetic.input";
String topRuleName = "Program";
String[] recoveryRuleNames = { topRuleName, "Statement" };
String grammarSpec = Files.readString(Paths.get(grammarSpecFilename));
Grammar grammar = MetaGrammar.parse( grammarSpecInput );
String input = Files.readString(Paths.get(inputFilename));
MemoTable memoTable = metaGrammar .parse( srcStr );
ParserInfo.printParseResult(topRuleName, metaGrammar , memoTable, input, recoveryRuleNames, false);

Oops, I should have tested that the code color compiles! Fixed, thanks.

Thank you for the fix!

authors: lukehutch wrandelshofer

repo: lukehutch/pikaparser


text:
share, span options for twin x and y axes

Description
Hi, I really like the feature that twinx and twiny can be applied to axs, which was not possible with matplotlib.
Would it be possible to add share and span options to twinx and twiny? Such as twinx(sharey=3, spany=True).
Currently, when we specified ylabel for twin axes, it will plot to all axes.
Steps to reproduce
import numpy as np
import proplot as plot

fig, axs = plot.subplots(nrows=2, ncols=2)
axs1 = axs.twinx()

x = np.arange(10)

for ax, ax1 in zip(axs, axs1):
    ax.plot(np.sin(x), c='b')
    ax1.plot(np.cos(x), c='r')

axs.format(ycolor='b', ylabel='ylabel1')
axs1.format(ycolor='r', ylabel='ylabel2')

Current behavior:
ylabels and ticks are shown in every plots.

Proplot version
0.6.4

Yep this is a really important item on my to-do list -- you can monitor PR #183 for updates.

authors: kinyatoride lukelbd

repo: lukelbd/proplot


text:
cpu-z@1.87: hash check failed

Download: Status Legend:
Download: (OK):download completed.
Checking hash of cpu-z_1.87-en.zip ... ERROR Hash check failed!
App:         extras/cpu-z
URL:         http://download.cpuid.com/cpu-z/cpu-z_1.87-en.zip
First bytes: 3C 21 44 4F 43 54 59 50
Expected:    fad8c570c17bad4dd9154105959d6f591a878ee8ebb3dfb44a4d9744449a875f
Actual:      795c6733b912e7c750746433de7b4fa35c82ce821308ca653ba9fbc3a04102f7

now i checked it. my isp's secure internet filter cause the issue.

repo: lukesampson/scoop-extras

license: Unlicense


text:
pskubectlcompletion: Add version 1.0.4

This can be use to enable kubectl auto-completion for PowerShell

Thanks for the comments.. I've applied them

Thanks for the comments.. I've applied them

/verify


text:
"Warn on shim overwrite" does not work ?

I've had shim for xargs from unxutils and it was replaced by shim from findutils
This merge is not working anymore ?
https://github.com/lukesampson/scoop/pull/2033

#2033 is working fine, but the unxutils.json doesn't contain any information about the available binaries. It just gets added to the %PATH% and just has higher priority if installed last. You could flip the directories in your PATH to fix it for now.
The unxutils manifest could be changed to include all binaries.

@r15ch13 oh yeah, this was the case, thank you. I don't know why this feature even exists, scoop shouldn't pollute PATH like this.

repo: lukesampson/scoop

license: unlicense


text:
Drag on node to grab all selected

Right now it only drags the node under the cursor.

Done

repo: lukors/kanter


text:
Do big cleanup

The code needs to be gone through to remove unnecessary functions, clean stuff up, split out into several files, and stuff like that.
A big refactor.

Done


text:
Cannot get select multiple to work

Hi i've been at this for several hours and cannot get the select to work. Here what i got going so far:
					<lx-select ng-model="Current.status" lx-choices="Choices.status" lx-label="Lorem Ipsum" lx-multiple="true" flex>
						<lx-select-selected>
							{{ $selected }}
						</lx-select-selected>

						<lx-select-choices>
							{{ $choice }}
						</lx-select-choices>
					</lx-select>

var Portal_Main_App = angular
.module('Portal_Main_App',['ngParseExt','ngMaterial','md.data.table','ngMask','ngMaterialDatePicker','summernote', 'lumx'])
.controller('Portal_Main_Controller',LUMX_Controller)
.config( function($mdThemingProvider) {
	$mdThemingProvider.theme('default').primaryPalette('green').accentPalette('blue').warnPalette('red');
});

LUMX_Controller.$inject = ['$scope', '$http','$filter', '$mdDialog', '$q','LxNotificationService'];

function LUMX_Controller($scope, $http, $filter, $mdDialog, $q, LxNotificationService ) {

$scope.Choices = [];
$scope.Current = [];
$scope.Current.status = ["Open"];
$scope.Choices.status = ["N/A","Open","Ongoing","Closed"];

}

Anyone have any ideas?

Thanks @akinjide for answering this old issue (that wasn't on our radar anymore, sorry for that @Owizardo)

authors: Owizardo clementprevot

repo: lumapps/lumX


text:
Clean up dependencies

serde_json wasn't used at all in lumeo-commands
the new_v4 Uuid constructor is only used in a commands test

Seems a bit excessive to rewrite git history for such a small thing, but I'll keep it in mind for the future.

repo: lumeohq/lumeo-types-rs


text:
Supply-chain security

Consider explicitly supply-chain security. For example:https://github.blog/2022-04-07-slsa-3-compliance-with-github-actions/

https://slsa.dev/
https://www.openchainproject.org/get-started/conformance (iso.org/standard/81039.html)
https://github.blog/2022-04-07-slsa-3-compliance-with-github-actions/
https://github.blog/changelog/2022-05-31-improved-verification-of-historic-git-commit-signatures/

https://security.googleblog.com/2023/06/bringing-transparency-to-confidential.html
https://slsa.dev/blog/2023/06/slsa-github-worfklows-container-based

CISA and NSA Release Joint Guidance on Defending Continuous Integration/Continuous Delivery (CI/CD) Environments.

https://binary.transparency.dev/

repo: lumoin/Verifiable


text:
Feature - Brand custom attribute editing

Closes #1368

I will move changes on LunarInstall, the fix belongs to #1417 now.

I will move changes on LunarInstall, the fix belongs to #1417 now.

No, I don't think it does. These changes effect the core, not the admin panel.

authors: glennjacobs lguichard

repo: lunarphp/lunar


text:
Minimal exploitability impl

Notably missing:

anything that involves disassembling and analyzing the binary
linux checks based on /proc/self/maps

I'm kinda bleh on how I just add the raw error code to the ProcessState -- maybe I should just pass it down directly? Or CrashReason should always make it easy to get?

rebased and made it use the new ProcessorOptions infra, in case we want to land it as experimental.

Closing, see #25 for context.

repo: luser/rust-minidump


text:
Write a tweet

Could you write a tweet in English about your plugin with small screenshot? I want to retweet it in PostCSS twitter account.
Also, it is a great plugin. After some work it could become a killer feature for PostCSS :). @ben-eb told me some ideas about for better CSS minifing on top of your plugin.

Thank you :) I think a tweet is not already necessary because of it https://twitter.com/nucliweb/status/740544079898025984 Or not?

Let's tweet again on next feature release 😊

https://twitter.com/lutien2/status/762285039518412800

authors: ai lutien

repo: lutien/postcss-extract-value


text:
can not open *.pb

out.pb.zip
hi, I used my own framework to generate this model using the TF protocol, but Netron said it was not supported

@lqwang1025 please investigate this issue.

repo: lutzroeder/netron


text:
Add .build(nnArchive, config) to NeuralNetwork node

Added the function as well as python binding.

LGTM when tested, thanks!

authors: borbrudar moratom

repo: luxonis/depthai-core


text:
USB3 - First draft of install instructions

The USB3 install instructions are the most involved as we need to help the user install software on their host and setup the cameras.
I'd like to get a hand on a first pass for the instructions. I've put together an outline, but this could be wrong.
To get started:

Fork this repo in the GitHub UI
Modify setup.md with your take on the instructions. You can use markdown and/or HTML, but don't worry much about style, proofreading, etc. I'll help with that.
You can edit the file via the GitHub UI (see the pencil icon) and preview as well (since it is markdown). Alternatively, you can download the source and edit there.
Don't worry about running Jekyll locally - I'm fine w/a quick pass.

See https://docs.luxonis.com/products/bw1098ffc/#setup

repo: luxonis/depthai-docs-website


text:
🛑 BrandTag Blockchain API is down

In 36ea7d3, BrandTag Blockchain API (https://rest.brandtag.io/chain/height) was down:

HTTP code: 500
Response time: 738 ms

Resolved: BrandTag Blockchain API is back up in bdca9c8.

repo: luxtagofficial/upptime


text:
error: Can not change LVM config. Images or containers are still using LVs

Requirement: Create two trusty containers each on its own disk so I could setup a 2-node mongodb replica set. My idea was to create two LVM volume groups so that each container owns its own volume group (and disks associated).
sgireddy@sbox02:/var/lib$ lxc config show
config:
images.remote_cache_expiry: "10"
storage.lvm_thinpool_name: thinpool1
storage.lvm_vg_name: vgpool1
Then I was able to create a container on this new volume group.
Now I wan to switch over to my second volume group, but lxc is not letting me to do do that.
sgireddy@sbox02:/var/lib$ lxc config set storage.lvm_vg_name vgpool2
error: Can not change LVM config. Images or containers are still using LVs: [db01 ***]
Is there any alternate way to achieve what I want?

I think right now the easiest way would be to run two lxd instances.  Register them in your client as remotes r1 and r2, and 'lxc start r1:mongo1; lxc start r2:mongo2'.

sorry to bug, would you please elaborate (or point me to some documentation) on how to run multiple instances of lxd daemon on the same host?

I think I replied to this earlier today on askubuntu or stackoverflow.
My suggestion there was to use one VG or no LVM at all for the containers, then create one LV on each VG which you then mount into the right containers using a device disk entry.

Thank you.
I followed the procedure described here: http://askubuntu.com/questions/528161/how-to-make-a-hdd-device-file-dev-sdxy-available-in-lxc-container
sgireddy@sboxv1:~$ ls -l /dev/sd*
brw-rw---- 1 root disk 8,  0 Nov 29 18:46 /dev/sda
brw-rw---- 1 root disk 8,  1 Nov 29 18:46 /dev/sda1
brw-rw---- 1 root disk 8,  2 Nov 29 18:46 /dev/sda2
brw-rw---- 1 root disk 8,  5 Nov 29 18:46 /dev/sda5
brw-rw---- 1 root disk 8, 16 Nov 29 18:46 /dev/sdb
brw-rw---- 1 root disk 8, 17 Nov 29 18:46 /dev/sdb1
sgireddy@sboxv1:~$ sudo cat /var/lib/lxd/containers/db01/fstab
/dev/sdb1 mnt/sdb ext4 noatime 0 0
sgireddy@sboxv1:~$ sudo cat /var/lib/lxd/containers/db01/config
lxc.mount = /var/lib/lxd/containers/db01/fstab
But got the following error (in log) and the container won't even start:
lxc 1448851772.747 ERROR    lxc_utils - utils.c:open_without_symlink:1575 - No such file or directory - Error examining sdb in /usr/lib/x86_64-linux-gnu/lxc/mnt/sdb
lxc 1448851772.747 ERROR    lxc_conf - conf.c:mount_entry:1731 - No such file or directory - failed to mount '/dev/sdb1' on '/usr/lib/x86_64-linux-gnu/lxc/mnt/sdb'
Why is it looking @ x86_64-linux-gnu/lxc? Did I do anything wrong?

No, the path is correct, it's the temporary LXC mountpoint.
Do both /dev/sdb1 on the host and /mnt/sdb in the container exist?

/dev/sdb1 exists on the host but the container wont event start.
sgireddy@sboxv1:~$ lxc start db01
error: Error calling 'lxd forkstart db01 /var/lib/lxd/containers /var/log/lxd/db01/lxc.conf': err='exit status 1'
Try lxc info --show-log db01 for more info

Oh, hold on, you followed a LXC procedure with LXD, yeah, that's likely to cause you some trouble.
LXD doesn't use container config files at all, it's all DB driven.
A device entry to get /dev/sdb1 from the host mounted into /mnt of the container using LXD is:
lxc config device add db01 mnt disk source=/dev/sdb1 path=/mnt/sdb

Though as I said before, current LXD requires /mnt/sdb to already exist in the container. I'll push a commit to change that since creating the path if missing seems reasonable.
What's the output of "lxc info --show-log db01" and "lxc config show db01"?

authors: hallyn sgireddy stgraber

repo: lxc/lxd


text:
Unable to do stateful snapshots

Error: snapshot dump failed
(00.007478) Error (criu/namespaces.c:408): Can't dump nested net namespace for 67385
(00.007493) Error (criu/namespaces.c:626): Can't make netns id
(00.106487) Error (criu/util.c:714): exited, status=1
(00.189576) Error (criu/util.c:714): exited, status=1
(00.190180) Error (criu/cr-dump.c:1709): Dumping FAILED.
Required information

Distribution: Ubuntu
Distribution version: Bionic
The output of "lxc info" or if that fails:
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.15.0-38-generic
server: lxd
server_pid: 39879
server_version: 3.0.2
storage: zfs
storage_version: 0.7.5-1ubuntu16.4
server_clustered: false

Issue description
Error: snapshot dump failed
(00.007478) Error (criu/namespaces.c:408): Can't dump nested net namespace for 67385
(00.007493) Error (criu/namespaces.c:626): Can't make netns id
(00.106487) Error (criu/util.c:714): exited, status=1
(00.189576) Error (criu/util.c:714): exited, status=1
(00.190180) Error (criu/cr-dump.c:1709): Dumping FAILED
Steps to reproduce
lxc launch ubuntu:bionic m1
lxc snapshot m1 --stateful

Information to attach

Log:
lxc ry-criu-test-ub18-20181125 20181126050141.130 WARN     conf - conf.c:lxc_setup_devpts:1620 - Invalid argument - Failed to unmount old devpts instance
lxc 20181126050151.308 ERROR    criu - criu.c:do_dump:1329 - dump failed with 1
lxc 20181126050151.308 ERROR    criu - criu.c:do_dump:1343 - criu output: Will skip in-flight TCP connections

Config
architecture: x86_64
config:
image.architecture: amd64
image.description: ubuntu 18.04 LTS amd64 (release) (20181101)
image.label: release
image.os: ubuntu
image.release: bionic
image.serial: "20181101"
image.version: "18.04"
volatile.base_image: 8f9da4cd832ba0235749caa2249c1ecfcee0cee052c4647fb502955fcec70072
volatile.eth0.hwaddr: 00:16:3e:15:ee:49
volatile.idmap.base: "0"
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":231072,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":231072,"Nsid":0,"Maprange":65536}]'
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":231072,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":231072,"Nsid":0,"Maprange":65536}]'
volatile.last_state.power: RUNNING
devices:
eth0:
name: eth0
nictype: bridged
parent: lxdbr0
type: nic
root:
path: /
pool: default
type: disk
ephemeral: false
profiles:

default
stateful: false
description: ""

That's a CRIU failure, not a LXD one, closing.
You may find more details in the migration and dump logs present in /var/log/lxd/NAME/
Updating to a newer CRIU may help you, or you may just be trying to dump something from a process which cannot be dumped. Modifying your container to better be dumpable may help, or you may need to talk to CRIU upstream to figure out what's missing.

authors: rowhit stgraber


text:
doc/storage: add video links

Add a link to the YouTube video about storage buckets, and also link the volume/bucket videos from the respective how-tos.
Signed-off-by: Ruth Fuchss ruth.fuchss@canonical.com

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.11012/

authors: lxc-jenkins ru-fu


text:
[TESTING] proxy: udp support

Signed-off-by: Christian Brauner christian.brauner@ubuntu.com

@brauner can you split out the util_linux.go bits into a separate commit?

@stgraber, yes. I need to push a small change on top anyway. I think for UDP we need to suicide via SIGKILL otherwise we will have lingering forkproxies around because connnect blocks and never exits...

authors: brauner stgraber


text:
index.md build from source improvements

Adding some more detail on building from source (latest version) vs. building a release. Also adding information on installing required libraries.

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Thanks! Left a few comments in-line. Also you'll need to make sure your commits include the Signed-off-by line before we can merge this.

Thanks for the feedback. I wasn't familiar with the in-place running of the binaries. I will update the PR to reflect this and improve it.

Thanks!

OK, I made a bunch of improvements to the improvements and also rebased and added the Signed-off-by: line. Please review.

Thanks!

authors: danielrobbins lxc-jenkins stgraber


text:
lxd/instance/qemu: Enable multiqueue on tap NICs

Signed-off-by: Stéphane Graber stgraber@ubuntu.com

Testsuite passed

Testsuite passed

Testsuite passed

authors: lxc-jenkins stgraber


text:
Modernize certificates

Signed-off-by: Stéphane Graber stgraber@ubuntu.com

Testsuite passed

@brauner @tomponline good to go

@tomponline @brauner ready to go again, added a few more changes.
This is all cleanup ahead of pushing #7898


text:
App identifier dropped from Google Play store link, rendering link-check error

Hello,
In our markdown file, we have the following link: [Google Play](https://play.google.com/store/apps/details?id=de.danoeh.antennapod). The action gives the following error:
### Errors in _i18n/nl/documentation/general/ads.md
* [404] [https://play.google.com/store/apps/details](https://play.google.com/store/apps/details) | Cached: Error (cached)

The part with the question mark seems to get dropped from the URL, making the link, indeed, wrong. Are these parts with the question mark dropped on purpose, or would this be a bug?

I transferred this issue to the lychee repo.

Turns out, this is actually an issue with pulldown-cmark.
Here is a repro: https://github.com/mre/pulldown-cmark-multiline-link-repro
You can run it yourself to confirm.
Input:
works: [](https://example.com)
broken: [](https://example.com?
id=foo)

Output:
"works: [](https://example.com)\nbroken: [](https://example.com?\nid=foo)\n" -> [
  Start(Paragraph)
    Text(Borrowed("works: "))
    Start(Link(Inline, Borrowed("https://example.com"), Borrowed("")))
    End(Link(Inline, Borrowed("https://example.com"), Borrowed("")))
    SoftBreak
    Text(Borrowed("broken: "))
    Text(Borrowed("["))
    Text(Borrowed("]"))
    Text(Borrowed("(https://example.com?"))
    SoftBreak
    Text(Borrowed("id=foo)"))
  End(Paragraph)
]

Can you report it upstream?

Closing as out of spec.

authors: keunes mre

repo: lycheeverse/lychee


text:
Add sample users to QuickStart

With a bit of luck this should be able to light up the mic new /users/ pages brought by lyft/amundsenfrontendlibrary#90
Still marked as WIP because it reverts #16 encode(utf-8) change (which I don’t understand?) - can that behavior be moved - maybe to a universal transform step? If so this PR could add that commit as well.

thanks @jornh , I think we could get rid of the encoding part. Our internal API returns unicode for user info instead of string which I use the encode to transform the data. But I think I could work around in the user extractor. Let me know once the pr is ready for review. Super excited for the pr to enrich our sample data.

Thanks @feng-tao that was the doubt I had.
I hope you like the theme I picked for CSV content! My aim is to get example data shown in the Amundsen introductory blog post 🙂

@jornh , that's great. I wonder whether with the sample user data, you are able to view the user profile page in Amundsen. cc @danwom as we are still actively working on Amundsen people/user.

In the latest Amundsenfrontend you can visit the route /user/[user_id] to view a profile page. The page is still a WIP as we need to implement bookmarks, owned resources, and frequently used resources as tabs on this page. We also need to implement searching user resources.

A screenshot I created a little while back using the PR #90 branch before it got merged:

URL: http://localhost:5000/user/roald.amundsen@example.org

maybe we should mention on the example data we have in a place(or update the existing doc). But it could be a different pr. Thanks @jornh for the pr. This is awesome :)

I must admit I didn’t try it out end to end after frontend PR 90 got merged - I broke my container setup after they got pushed to DockerHub and mostly spent my Amundsen time the last few days on knowledge sharing.
Kudos to @danwom for the nice layout. Sorry for my schreenshot “leak” 😉

maybe we should mention on the example data we have in a place(or update the existing doc). But it could be a different pr.

Agree, it would be cool to have some kind of data flow illustration for each example source:

csv
which Databuilder pieces would be involved in reality (e.g)
Which pieces it lights up in the metadata model
API endpoints
Which UI components it lights up.
etc?

Not sure about the format - simplest would be a simple table. Something fancy could be overlaid on the architecture diagram.

Actually @ttannis build the profile page. I just merged in the feature branch. https://github.com/lyft/amundsenfrontendlibrary/pull/44

Hah, my bad, thanks @danwom for sharing a bit of history actually I think from before I met Amundsen ... waay back then
Yep there it is beautifully mocked up front and center in https://github.com/lyft/amundsenfrontendlibrary/pull/44

Guess, if I’m bored some rainy day I could go back and read up on PR history 😉

@jornh I don't expect anyone to have known this. Just wanted to give credit where it is due. 😄

authors: danwom feng-tao jornh

repo: lyft/amundsendatabuilder


text:
Please issue a release tag (e.g. 1.0.0)

Is it possible to create a release? It will be a lot easier to track changes and make sure we avoid deployment issues.
https://github.com/lyft/flyte/releases

Hi Floren,
Thanks for you request. We are working on an overall release process. For the time being, the individual components, namely: https://github.com/lyft/flytepropeller/releases, https://github.com/lyft/flyteadmin/releases, https://github.com/lyft/flytekit/releases, https://github.com/lyft/flyteconsole/releases, https://github.com/lyft/datacatalog/releases, https://github.com/lyft/flyteplugins/releases, https://github.com/lyft/flytestdlib/releases, https://github.com/lyft/flyteidl/releases
master of Flyte repo will always have compatible versions of all the above components in: https://github.com/lyft/flyte/blob/master/deployment/sandbox/flyte_generated.yaml

If you do have opinions/suggestions @fmunteanu about how that should look like or good practices (from prior experience) that you would like to share, that's most welcome!
The current thinking is that these individual components will continue to cut rapid releases as they have been... with Flyte repo releases being a cumulation of a bunch of these when the delta is significant enough to cut a new release. Still working on quantifying what's significant though, a breaking change definitely is, perhaps time-based measure? complexity? "importance" of features... etc.

We have for now decided to have a monthly release train for github/lyft/flyte releases. We will iterate individual components independently. We deploy Flyte continuously internally at Lyft, but we will cut lyft/flyte releases only when we believe it is absolutely stable. Thank you for reaching out, keep a look out for seeing the release process that will be posted soon.

authors: EngHabu fmunteanu kumare3

repo: lyft/flyte


text:
Fix for Discrepancy in CostEstimate model for current android SDK (v1.0.3) (as reported on the lyft developer community forum)

This PR covers a fix for an issue reported early October on the Lyft developer community forum. Here is the link to the issue:
https://devcommunity.lyft.co/t/discrepancy-in-costestimate-model-for-current-android-sdk-v1-0-3/202
The commit that actually has this fix is bcde284.
In addition to the aforementioned fix, I have filled a few more gaps that were in the SDK, for example:

The SDK in general (and in particular, the MockLyftPublicApi) is now aware of 3 additional Lyft Products which I think were added as products since the last time this SDK was updated in February (see commits 7c61fee and bbe009e.):

LYFT_PREMIER,
LYFT_LUX,
LYFT_LUX_SUV

Added several more model types to the SDK for objects received and returned by the API; some of which are polymorphic (See EtaLocation which extends LyftLocation and LyftDriver which extends LyftUser classes as examples). Other examples of models added include (but are not limited to) to (see commit: 395d14d ):

MonetaryAmount,
RideHistory,
RideRequest,
RideRequestResponse

Added LyftUserApi and and LyftUserApiRx, which is distinct from the LyftPublicApi and LyftPublicApiRx interface as in it exposes methods that require an access_token from a user -- whereas the LyftPublicApi exposes methods that do not require a user access_token (see commit: 395d14d.). In the same context, I have also modified ApiConfig and LyftApiFactory and abstracted them in such a way that a user can request for a LyftUserApi retrofit client or a LyftPublicApi retrofit client seamlessly. In fact the underlying mechanics that differentiates between a User Api and Public Api retrofit client is the fact that LyftApiFactory will create an OkHttpClient with a RequestInterceptor that passes either the client token via apiConfig#getClientToken() (as is the case with a LyftPublicApi) or the LyftApiFactory will create an OkHttpClient with a RequestInterceptor that passes either the user access token via: apiConfig#getUserAccessToken() . For more details see commit: 395d14d:

LyftApiFactory.java: line 27 (for Public Api)
LyftApiFactory.java: line 37 (for Public Api)
LyftApiFactory.java: line 72 (for Public Api)
LyftApiFactory.java: line 78-85 (for User Api)
ApiConfig.java: line 7 (for User Api)
ApiConfig.java: line 27-37 (for User Api)
LyftApiFactory.java: line 43-64 (for User Api)
LyftApiFactory.java: line 78-85 (for User Api)

Exposed overloads to the getEtas method in the LyftPublicApi interface. Effectively exposing a way for users of the SDK to make calls to the getEtas end point without the need to pass parameters that are deemed optional by that endpoint. (see commit: 25fd37e.)

Will Love to get your thoughts and feedback.
Awah T-

This is fantastic @awahnteh! We'll re-run the CLA check shortly, thanks so much for your contribution.

authors: acityinohio awahnteh

repo: lyft/lyft-android-sdk


text:
Issue model.safetensors.index.json should exist with loading model in safetensors format

When loading the model  unsloth/Meta-Llama-3.1-8B-Instruct-bnb-4bit, I have the error :  AssertionError: model.safetensors.index.json should exist.
from airllm import AutoModel

model = AutoModel.from_pretrained("unsloth/Meta-Llama-3.1-8B-Instruct-bnb-4bit")

Indeed in this model there is no file model.safetensors.index.json
The same goes for the model unsloth/Meta-Llama-3.1-70B-bnb-4bit
The file model.safetensors.index.json is present in the model unsloth/Meta-Llama-3.1-405B-Instruct-bnb-4bit

I get the same error. Could you fix this?

I get the same error

Same error

same error

have you enabled cuda cores ?

repo: lyogavin/airllm


text:
more efective compaction algorithm

[ ] -  use k-merge and dont read all values to memory.
[ ] - need update changelog

already.

repo: lysevi/dariadb


text:
Update serviceWorker.js

There is a small typo in !!(opts.cachePathPattern.exec(url.pathname), (a missing bracket). You could also write this using RegExp.prototype.test instead of RegExp.prototype.exec (saving the type conversion).

Thanks!

authors: lyzadanger nilssolanki

repo: lyzadanger/serviceworker-example


text:
[Question] How to build this as dylib (consumable in a .NET Core project)

How can I build this as a dylib on macOS, rather than a .a (static library)?
I've tried the following with no success:

passing -DBUILD_SHARED_LIBS=ON parameter to xcodebuild
Explicitly specified "Dynamic Library" as a "Match-O Type": https://take.ms/4Tzj6

P.S. Please disregard.
After the above steps, I've renamed the generated .a file to .dylib and was able to consume it in a .NET Core C# project.

repo: lzfse/lzfse


text:
Upstream synch

минулий зробив неправильно

Upstream sync 🤓


text:
Feature Update - Play and Save

I've implemented the directory structure w.r.t TDD by ResoCoder (Let me know I'll link his working if necessary).
Other than that, I've implemented state management using Bloc and then using that, implemented the Play functionality.
I've added a Saved Music screen where the saved music paths are loaded from Shared Preference for now. Can be implemented to be loaded from a file since Shared Preference has a specific limit to how much it can store.
Apart from that, a couple of small changes here and there. Hope that you'll accept the pull request.
I'll add comments and update the README as required in the next commit soon.

Are you done with, whatever you have mentioned "next commit soon"?

No I haven't commented the code yet. I'll do that now.

Are you done with, whatever you have mentioned "next commit soon"?

No I haven't commented the code yet. I'll do that now.

Are you done with, whatever you have mentioned "next commit soon"?

The code has now been commented. Feel free to update the gif in the README as I donot know how to do that myself.

authors: ShehriyarShariq m-hamzashakeel


text:
ndt7: map more variables from the kernel.

Improve the data provided from NDT7.
This is a reminder for @bassosimone. Check the old data returned from the speed test compared with the new NDT7.
Example of old data:
{

\"annotations\":{\"engine_name\":\"libmeasurement_kit\",\"engine_version\":\"0.9.0-alpha.2\",\"engine_version_full\":\"v0.9.0-alpha.2\",\"platform\":\"ios\"},\"data_format_version\":\"0.2.0\",\"id\":\"b964eb63-7e45-4692-920b-60c91d80389d\",\"input\":null,\"input_hashes\":[],\"measurement_start_time\":\"2019-03-21 21:21:30\",\"options\":[],\"probe_asn\":\"AS32110\",\"probe_cc\":\"US\",\"probe_city\":null,\"probe_ip\":\"127.0.0.1\",\"software_name\":\"measurement_kit\",\"software_version\":\"0.9.0-alpha.2\",\"test_helpers\":{},\"test_keys\":{\"advanced\":{\"avg_rtt\":235.577958672511,\"congestion_limited\":0.923405697248891,\"fast_retran\":5,\"max_rtt\":1041,\"min_rtt\":80,\"mss\":1238,\"out_of_order\":0.471422940480883,\"packet_loss\":0.000203252032520325,\"receiver_limited\":0.0184981344589309,\"sender_limited\":0.0580961682921784,\"timeouts\":0},\"client_resolver\":\"162.158.184.171\",\"failure\":null,\"phase_result\":{\"download\":\"\",\"meta\":\"\",\"upload\":\"\"},\"server_address\":\"ndt.iupui.mlab3v4.atl02.measurement-lab.org\",\"server_port\":3001,\"server_version\":\"v4.0.0.1-Web100\",\"simple\":{\"download\":28654.1809275501,\"ping\":80.0,\"upload\":39732.3181968809},\"summary_data\":{\"CWND-Limited\":0.0,\"CWNDpeaks\":5,\"Sndbuf\":2830968,\"aspd\":0.0,\"avgrtt\":235.58,\"bad_cable\":0,\"bw\":2.81,\"c2sAck\":6,\"c2sData\":6,\"congestion\":1,\"cwin\":10.0213,\"cwndtime\":0.9234,\"half_duplex\":0,\"link\":0,\"loss\":0.000203252,\"maxCWNDpeak\":1312280,\"minCWNDpeak\":131228,\"mismatch\":0,\"order\":0.4714,\"rttsec\":0.235578,\"rwin\":15.2622,\"rwintime\":0.0185,\"s2cAck\":4,\"s2cData\":9,\"sendtime\":0.0581,\"spd\":23.75,\"swin\":21.5986,\"timesec\":10.0,\"waitsec\":0.0},

\"test_c2s\":[{\"connect_times\":[0.0865039825439453],\"params\":{\"num_streams\":1},\"receiver_data\":{\"avg_speed\":25830.0},\"sender_data\":[[0.655593156814575,1899.32427917667],[1.22219800949097,5204.89718023003],[1.72243213653564,30525.482318075],[2.42827796936035,47352.2098533102],[2.93126106262207,14071.8208918349],[3.45268607139587,19858.4414359993],[3.95280909538269,23325.0769120909],[4.45877194404602,56992.0105323533],[4.96387100219727,43595.599011009],[5.46615815162659,63280.4562810592],[5.99089694023132,58699.5294971453],[7.05546712875366,16436.7856517643],[8.00848317146301,6189.02488066388],[8.50857400894165,53598.7104565678],[9.00996398925781,42611.0150556419],[10.0460510253906,7527.15141491289]]}],

\"test_s2c\":[{\"connect_times\":[0.103318929672241],\"params\":{\"num_streams\":1,\"snaps_delay\":0.5},\"receiver_data\":[[0.518100023269653,6912.3332158896],[1.02495908737183,28793.1084469235],[1.525062084198,35217.2574685085],[2.061527967453,28821.5159297472],[2.66359806060791,18851.5990563905],[3.31645703315735,10736.6036077098],[3.91677904129028,533.020605050253],[4.43011999130249,20058.9958774088],[4.93114900588989,3083.70165203372],[5.44105291366577,24686.9729924346],[5.9417200088501,26117.8258483031],[6.44191789627075,29733.7361352995],[6.94193696975708,31176.602706989],[7.44275999069214,31522.0653605839],[7.94766402244568,27834.5489759529],[8.44797992706299,25674.75445304],[8.94798707962036,31692.3466373448],[9.44800710678101,29142.5127164325],[9.94839692115784,32024.3768749702]],\"web100_data\":{\"AckPktsIn\":10148,\"AckPktsOut\":0,\"BytesRetrans\":1111724,\"CongAvoid\":2773,\"CongestionOverCount\":728,\"CongestionSignals\":5,\"CountRTT\":4791,\"CurCwnd\":339212,\"CurMSS\":1238,\"CurRTO\":287,\"CurRwinRcvd\":1999168,\"CurRwinSent\":14592,\"CurSsthresh\":328070,\"DSACKDups\":0,\"DataBytesIn\":0,\"DataBytesOut\":30536778,\"DataPktsIn\":0,\"DataPktsOut\":24600,\"DupAcksIn\":4784,\"DupAcksOut\":566,\"Duration\":10289436,\"ECNEnabled\":0,\"FastRetran\":5,\"MaxCwnd\":1313518,\"MaxMSS\":1238,\"MaxRTO\":1874,\"MaxRTT\":1041,\"MaxRwinRcvd\":2000448,\"MaxRwinSent\":14592,\"MaxSsthresh\":656140,\"MinMSS\":1238,\"MinRTO\":286,\"MinRTT\":80,\"MinRwinRcvd\":115712,\"MinRwinSent\":14480,\"NagleEnabled\":1,\"OtherReductions\":0,\"PktsIn\":10148,\"PktsOut\":24600,\"PktsRetrans\":898,\"RcvWinScale\":7,\"SACKEnabled\":3,\"SACKsRcvd\":3988,\"SampleRTT\":83,\"SendStall\":0,\"SlowStart\":1055,\"SmoothedRTT\":84,\"SndLimBytesCwnd\":28671246,\"SndLimBytesRwin\":247650,\"SndLimBytesSender\":1617882,\"SndLimTimeCwnd\":9499658,\"SndLimTimeRwin\":190302,\"SndLimTimeSender\":597672,\"SndLimTransCwnd\":28,\"SndLimTransRwin\":8,\"SndLimTransSender\":20,\"SndWinScale\":6,\"StartTimeUsec\":275110,\"SubsequentTimeouts\":0,\"SumRTT\":1128654,\"Timeouts\":0,\"TimestampsEnabled\":1,\"WinScaleRcvd\":6,\"WinScaleSent\":7,\"X_Rcvbuf\":87380,\"X_Sndbuf\":2830968}}],

\"test_suite\":54},\"test_name\":\"ndt\",\"test_runtime\":27.2959189414978,\"test_start_time\":\"2019-03-21 21:21:27\",\"test_version\":\"0.1.0\"

}

Se to P0 because this is a blocker for Asurion.

The complete list of required variables is: "congestion, max_rtt, min_rtt, upload, download, packet_loss" as mentioned by @miguelangelnet on Slack.

This is done. We have amended the specification to mention that the most useful TCPInfo variables are REQUIRED and we have changed the code to return all TCPInfo variables. Can't do more.

authors: bassosimone miguelangelnet

repo: m-lab/ndt-server


text:
Modify hopannotation1 formatter to include paris-traceroute data

This change is

Pull Request Test Coverage Report for Build 245

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 68.846%

Totals

Change from base Build 241:
0.0%

Covered Lines:
495

Relevant Lines:
719

💛  - Coveralls

authors: coveralls cristinaleonr

repo: m-lab/stats-pipeline


text:
GWT compilation errors when trying to use this library

Hi,
I'm trying to get this project moving forward to a state where it could actually be included in the standard gwt library but I can't even get a simple gwt project to compile.
Steps to reproduce:

Checkout the simplest possible project making use of this library:

git clone git@github.com:salvadordiaz/gwt-time-demo.git

Try to run a GWT compilation (everything is setup with maven):

mvn install

Watch it fail with errors in located in source code coming from the gwt-time jar:

[INFO]    [ERROR] Errors in 'jar:file:/home/salvador/.m2/repository/com/google/gwt/gwt-time/2.6.1-SNAPSHOT/gwt-time-2.6.1-SNAPSHOT.jar!/com/google/gwt/emul/java/time/ZoneId.java'
[INFO]       [ERROR] Line 383: No source code is available for type java.util.Locale; did you forget to inherit a required module?
[INFO]    [ERROR] Errors in 'jar:file:/home/salvador/.m2/repository/com/google/gwt/gwt-time/2.6.1-SNAPSHOT/gwt-time-2.6.1-SNAPSHOT.jar!/com/google/gwt/emul/java/time/ZoneOffset.java'
[INFO]       [ERROR] Line 81: No source code is available for type java.util.concurrent.ConcurrentMap<K,V>; did you forget to inherit a required module?
[INFO]       [ERROR] Line 81: No source code is available for type java.util.concurrent.ConcurrentHashMap<K,V>; did you forget to inherit a required module?

Possible fixes:
I'm the guy that offered to take the time to contribute to the project in order to get it in shape for inclusion in the official gwt distribution. I tried to make it work but I'm getting GWT compilation errors that I'm pretty sure you're not seeing because the project where you're using gwt-time has all the JRE-emulated classes needed to make it compile. So here's what we could do to make this work:

would you consider moving all this supersource stuff to a standalone project ?
or shoud I just copy-paste the necessary classes in the gwt-time project ?

Thanks again for your time and for gwt-time ;)

Too sad, I totally missed this out years ago. Your error was only missing source dependencies I assume. However, I think that GWT is not the big future anymore. Sad but true...
Thanks for your interest in supporting and improving. I might close done this repo in the future as I am not maintaining this stuff for years.

authors: hohwille salvadordiaz

repo: m-m-m/gwt-time


text:
CYC-80 CYC-82 CYC-83 Add Role model, and management controller functions

Description
Closes #69
See CYC-80 CYC-82 CYC-83
Adds the ability to assign existing roles to existing users as well as the ability to detach said roles.
Changes

Adds Role model
Adds Role migration
Adds Role relationship to User
Adds role based utility functions to user
Add RoleUserController

Adds Store function to allow for attaching roles to a user
Adds Destroy Function to allow for detaching roles from users
Add appropriate routes

Reorder routes

@luigibesani strange, it definitely works for me; it should be a Delete request to /user/roles the passed parameters are supposed to be role_ids and user_id, if you're getting a 400 it might be that you're trying to delete a role from a non existent user? we call find or fail so that would cause a 404.
You may want to php artisan migrate:fresh and php artisan db:seed to ensure you have all the correct users and roles

@IanjhPhillips or @RobertoNittolo can you see if you get weird behaviour like @luigibesani does at some point?

@IanjhPhillips or @RobertoNittolo can you see if you get weird behaviour like @luigibesani does at some point?

ya sure, I can give it a try later today or tomorrow!

authors: RobertoNittolo m-triassi


text:
allow for the pull of a single value using getContent on the Parser class

This PR updates the Parser class to allow for pulling just one value from the getContent method (if it exists). Otherwise, it will just return the full set as before.

"Faster" is pretty negligible in this case. Micro-optimizations like that really only matter when there's thousands of the operations happening. They both do the same thing.

The is_null change was purely for consistency, as is_null is used throughout the codebase.

@m1 take a look at that and see what you think

LGTM

woot! thanks :)


text:
add name prop in SelectInput component

Story

add name prop in SelectInput component to be controlled by form element
remove selected attribute in first <option> element

Resolved by #77


text:
added release 28

I've added a folder with release 28 of the nutritional database. I had to add in 2 entries the data_src.txt file which were missing and caused a constraint error
~S7924~^~Nutrient Data Laboratory, ARS, USDA~^~2013 Label Data~^~2013~^^^^^
~S7584~^~Nutrient Data Laboratory, ARS, USDA~^~2012 Label Data~^~2012~^^^^^
These are present in release 27 but have gone AWOL in release 28

Hi @alastair-duncan, thanks for the work you did. I also updated 27 -> 28 and did not find the two records being missing. (I did find two record counts being off by 1.) Perhaps the USDA updated the filed after you downloaded them.
Anyway, I checked in my own changes so this project is now up to date with the 28 release.


text:
Add UART ports

On the STM32F03F4P6 used in the device:
Pins 6/7 can be USART4_TX/RX, which are external pins IO0/IO1.
Pins 8/9 can be USART2_TX/RX, which are external pins IO2/IO3.
Pins 10/11 can be USART6_TX/RX, which are external pins IO4/IO5.
Maybe pins 12/13 (which are external pins IO6/IO7) can be a low speed bit-bang UART?
Proposed changes:
Registers 0x00-0x07 would have UART_MODE=5.
Pins could be individually set for applications that only require RX or TX but not both.
Serial mode would only be 8 bit, no parity, 1 stop bit at this time.
Registers 0x90-97 would be used for serial data received by the EXTIO2 (0x90, 0x92, 0x94, 0x96) and for how many bytes are available in the buffer (0x91,0x93,0x95,0x97).
Registers 0x98-9F would be used for serial data sent bye the EXTIO2 (0x98, 0x9A, 0x9C, 0x9E) and for how many bytes are available in the buffer (0x99,0x9B,0x9D,0x9F).
Registers 0xA0-A7 would be used for baud rates x 100.  (0xA0/0xA1 set to 576 sets baud to 57600).

Thank you very much for your suggestion. We greatly appreciate your interest and support in our project.

authors: JasonPittenger chenzhjie