text:
XSSFFormulaEvaluator.EvaluateAllFormulaCells fails on Linux

Hello, I have this excel file:
EIOPA_RFR_20220331_Term_Structures.xlsx
The file contains many sheets, and some of them contains formula.
I used the following code to load the file
var wb = new NPOI.XSSF.UserModel.XSSFWorkbook(path);
XSSFFormulaEvaluator.EvaluateAllFormulaCells(wb);

On Windows I do not have any issue.
On Linux I obtain the following error:
System.IndexOutOfRangeException : Index was outside the bounds of the array.
  at NPOI.SS.Formula.FormulaCellCacheEntrySet.AddInternal (NPOI.SS.Formula.CellCacheEntry[] arr, NPOI.SS.Formula.CellCacheEntry cce) [0x0000f] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.FormulaCellCacheEntrySet.Add (NPOI.SS.Formula.CellCacheEntry cce) [0x00064] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.CellCacheEntry.AddConsumingCell (NPOI.SS.Formula.FormulaCellCacheEntry cellLoc) [0x00000] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.FormulaCellCacheEntry.ChangeConsumingCells (NPOI.SS.Formula.CellCacheEntry[] usedCells) [0x00010] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.FormulaCellCacheEntry.SetSensitiveInputCells (NPOI.SS.Formula.CellCacheEntry[] sensitiveInputCells) [0x00027] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.FormulaCellCacheEntry.UpdateFormulaResult (NPOI.SS.Formula.Eval.ValueEval result, NPOI.SS.Formula.CellCacheEntry[] sensitiveInputCells, NPOI.SS.Formula.FormulaUsedBlankCellSet usedBlankAreas) [0x00008] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.CellEvaluationFrame.UpdateFormulaResult (NPOI.SS.Formula.Eval.ValueEval result) [0x0000d] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.EvaluationTracker.UpdateCacheResult (NPOI.SS.Formula.Eval.ValueEval result) [0x00029] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.WorkbookEvaluator.EvaluateAny (NPOI.SS.Formula.IEvaluationCell srcCell, System.Int32 sheetIndex, System.Int32 rowIndex, System.Int32 columnIndex, NPOI.SS.Formula.EvaluationTracker tracker) [0x000d7] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.WorkbookEvaluator.Evaluate (NPOI.SS.Formula.IEvaluationCell srcCell) [0x00027] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.XSSF.UserModel.BaseXSSFFormulaEvaluator.EvaluateFormulaCellValue (NPOI.SS.UserModel.ICell cell) [0x00008] in <23fa936cd8a6438893e9f135c11b7dc9>:0
  at NPOI.SS.Formula.BaseFormulaEvaluator.EvaluateFormulaCellEnum (NPOI.SS.UserModel.ICell cell) [0x0000e] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.BaseFormulaEvaluator.EvaluateFormulaCell (NPOI.SS.UserModel.ICell cell) [0x00000] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.BaseFormulaEvaluator.EvaluateAllFormulaCells (NPOI.SS.UserModel.IWorkbook wb, NPOI.SS.UserModel.IFormulaEvaluator evaluator) [0x00036] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.SS.Formula.BaseFormulaEvaluator.EvaluateAllFormulaCells (NPOI.SS.UserModel.IWorkbook wb) [0x0000c] in <fa640c79ff584c719f42c78fbe436bd4>:0
  at NPOI.XSSF.UserModel.XSSFFormulaEvaluator.EvaluateAllFormulaCells (NPOI.XSSF.UserModel.XSSFWorkbook wb) [0x00000] in <23fa936cd8a6438893e9f135c11b7dc9>:0

Any idea of the reason of this disallineament between Linux and Windows?

Please provide the following information:

NPOI version
.NET core version
Linux system version

See the information below

NPOI version = 2.5.5

.NET core version = I am using mono version 6.12.0.147

Linux system version = Ubuntu 21.10

authors: ftesser tonyqus

repo: nissl-lab/npoi


text:
Upgrade to NUKE 8.1

Now also enabling cancel-in-progress for PR workflow which will cancel earlier build if PR is updated.

You are a real expert of Nuke!

You are a real expert of Nuke!

It helps that I implemented the concurrency handling support 😆

LGTM

source: gharchive/pull-request

authors: lahma tonyqus

license_type: permissive

license_source: github-api


text:
Add bend constraint implementation

Implementing the bend constraint projection as outlined in the original PBD paper from 2007.

Thanks @aykae, this looks good so far - a few things:

As you mentioned in the comments, the createBendSheet implementation still needs to add bending constraints across grid cells.
One thing that's worth clarifying in the code or documenting is what the order of nodes (x1, x2, x3, and x4) to the bending constraint represent. A bending constraint is really a constraint between two triangles with a shared edge. I see in the code that we are doing computations on the following edges: x1x2, x1x3, x1x4. It's worth clarifying which one of these is said to be the shared edge and which vertices the two triangles are between. From a glance it looks like maybe x1x2 is the shared edge and so x1x2x3 and x1x2x4 are the two triangles? It would be worth clarifying in the code somewhere regardless.


text:
Rename deployment command to stack

remove "stack describe"
rename "stack new" to "new"
rename "deployment apply" to "stack up"
rename "deployment delete" to "stack down"
rename "deployment list" to "stack list"
remove user aliases
remove unimplemented command "provider list"

fixes #137

Codecov Report

Merging #140 (50b9a66) into develop (3e9326f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #140   +/-   ##
========================================
  Coverage    32.74%   32.74%
========================================
  Files           43       43
  Lines         3329     3329
========================================
  Hits          1090     1090
  Misses        2136     2136
  Partials       103      103

Flag
Coverage Δ

unittests
32.74% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

authors: asalkeld codecov-commenter

repo: nitrictech/cli


text:
有的漫画可以看，有的全是红叉

挂个梯子，或者切换下图片分流

挂个梯子，或者切换下图片分流

一样的情况 而且只有之前看过的封面能正常显示 内容全部都是x 官方app可以正常浏览

挂个梯子，或者切换下图片分流

卸载重新安装解决 应该程序哪里有问题，这种情况出现挺多了

挂个梯子，或者切换下图片分流

卸载重新安装解决 应该程序哪里有问题，这种情况出现挺多了

应该是旧版升新版的问题吧，之前有一版是这样的

之前确实是这样 但这次我并没有升级

source: gharchive/issue

repo: niuhuan/pikapika

license: MIT


text:
1.7.7以后的版本滑动很卡

设备14Pro，使用TrollStore
有前缀为1.7.6，无前缀为1.7.9
1.7.7以后的版本感觉过渡很不自然
https://github.com/niuhuan/pikapika/assets/17558260/00062c4b-7474-41cf-8a58-4c70f08895ee

用3.x版本的flutter

检查一下ipa是2.×引擎还是3.x引擎

可以了 感谢

authors: JamesLewisLiu niuhuan


text:
Fix react17 useRef error

See https://reactjs.org/blog/2020/08/10/react-v17-rc.html#potential-issues
Since react 17 this line lead into an error.

If this is the case, then this PR only fixes one place where the editor reference is used. I think is better to add undefined checks in those other places too. Gonna take a look into that.

i have this error too, please fix

This is included in version 1.26.2.

authors: Cyver0 TrejGun niuware

repo: niuware/mui-rte


text:
Energy settings reset after reboot

Just enabling plasma-manager with programs.plasma.enable = true makes energy setting does not save. I cannot change when I want my display to turn off and when my laptop should go to sleep.
Disabling plasma-manager fixes that. Even If I have no additional settings in plasma-manager problems occurs.

Unless overrideConfig is enabled, it really shouldn't happen. I will try to reproduce it. But you can declare your energy settings with the powerdevil module.

That's really strange. Honestly I don't know if it was happening from the beginning or appeared while I was using plasma-manager. Once I noticed it I tried to debug it and I see that just enabling plasma-manager breaks energy settings.

Right now I'm using power devil to declare my config however the issue still persist.

Right now I'm using power devil to declare my config however the issue still persist.

It is happening with the configuration that is being declared?

I would say it is probably due to the way powerdevil module is working.

authors: HeitorAugustoLN urioTV

repo: nix-community/plasma-manager


text:
Confusing deprecation notice for sys::epoll::epoll_ctl

https://docs.rs/nix/latest/nix/sys/epoll/fn.epoll_ctl.html
Currently it says "👎Deprecated since 0.27.0: Use Epoll::epoll_ctl() instead", but Epoll::epoll_ctl is private and I can't use it. So either deprecation message should talk about individual commands or Epoll::epoll_ctl should be public. Probably the former.

Thanks for catching it! It is indeed confusing.

Probably the former

Yeah, we should use the corresponding methods of Epoll: https://docs.rs/nix/latest/nix/sys/epoll/struct.Epoll.html#method.add

authors: SteveLauC pacak

repo: nix-rust/nix

license: mit

license_source: bigquery


text:
Improve documentation for ioctl

I'm working on converting my crate to use nix instead of ioctl-rs as nix is better maintained. The big issue here is that the documentation for using ioctls with nix is not good from a user's point of view. Here are some issues I ran into:

The difference between using ioctl! and using ior!, iow!, iorw!, and ioc is not listed clearly. I'm sure one is preferred over the other, but I'm not certain which. The example only uses ioctl!.
It should be clarified that ioctl constants should be upstreamed into libc and then those should be used as inputs/outputs. The example doesn't do that, so we'll have tons of people reimplementing everything per-crate.
The ioctl! example only uses read and write. Looking at the macro there are 8 forms of it, but the documentation doesn't actually describe any of them.
It's unclear how to use ioc_dir and friends. There are no docs and they don't take clear types, but there are constants that have similar names in the module, so maybe those are related?
There are various constants that are also a part of the ioctl module, but those don't seem attached to these functions.
nix doesn't provide helpful wrapper functions for ioctls even if they're quite common (TIOCEXCL would be an example) and well-defined. I'd suggest that wrapper functions be provided for well-defined ioctls. This may be controversial, as I think it's come up before, because ioctl's are unbounded and defined by kernel drivers. So maybe there is a role for an ioctl crate that does this on top of nix.

Even the most basic question, of how do I convert an ioctl that looks like ioctl(fd, TIOCEXCL) to a proper one using the API defined by nix isn't answered. I don't see where I'm supposed to pass a file descriptor to the macro and the example provided, even though there are 12 provided don't ever pass an fd. Looking into this further, it appears that the ioctl! macro generates unsafe functions, and those can then be called. The ioctl module docs show examples in generating the functions, but then they don't ever use it.

Yeah, there's not enough docs for me to convert a simple no-data ioctl to use nix, so I'm going to give up for now. Any help would be appreciated here.
cc @posborne as you wrote a big chunk of the current documentation and probably understand the system enough to help me with my first trivial use case.

The docs also refer to a bad variant within ioctl, which doesn't appear to exist. This should shortcut the various _IOC and related macros and use the hardcoded number instead. This is necessary for use with the TIOCEXCL and many other constants.

@cmr it looks like you originally wrote the macros.  Could you please add some documentation?

I spent some time using the ioctl module, so I have a pretty good understanding of it.
First, the ioc!, io!, ior!, iow! and iorw! macros correspond to the equivalent macros _IOC, _IO, ... defined by the linux kernel there : https://github.com/torvalds/linux/blob/f4dd029ee0b92b77769a1ac6dce03e829e74763e/include/uapi/asm-generic/ioctl.h#L68. They allow to calculate, given a direction, an ioctl "type", an ioctl number, and the size of the ioctl argument, an unique identifier for that ioctl.
The ioc_dir, ioc_nr, ioc_size and ioc_type function allow to reverse what the above macro do. Basically, ioc_dir(io!(0, 0)) == ioctl::NONE (no direction, because I used io!). Those functions aren't very useful AFAIK. I haven't had to use them anyhow.
The ioctl function allows sending an ioctl given an fd: RawFd, request_number: c_ulong, .... It's hidden from the docs with a mention that it should be removed in favor of the libc function when https://github.com/rust-lang/rust/pull/26809 is merged. Which was merged a while ago. So maybe it's time for this function to retire ?
Finally, the ioctl! macro defines an unsafe function that basically looks like this (minus some differences depending on the variant of ioctl used) :
// Result of ioctl!(read ioctl_name with b'b', 1; Type)
pub unsafe fn ioctl_name(fd: libc::c_int, val: *mut Type)
                            -> nix::Result<libc::c_int> {
    // Note that ioctl function used here should be libc::ioctl. The pr mentioned a
    // https://github.com/nix-rust/nix/blob/master/src/sys/ioctl/mod.rs#L117 was merged
    Errno::result(nix::sys::ioctl::ioctl(fd, ior!(b'b', 1,size_of::<Type>()) as libc::c_ulong, val))
}

There are multiple variants that depend on the ioctl definition :

ioctl!(none ioctl_name with b'b', 1) => An ioctl that takes no argument. It will use io! to calculate the request number.
ioctl!(read ioctl_name with b'b', 1; u8) => An ioctl that takes a *mut u8 (it will return a value at the given pointer). It will use ior!.
ioctl!(write ioctl_name with b'b', 1; u8) => An ioctl that takes a *const u8 (it takes the value at the given pointer). It will use iow!
ioctl!(readwrite ioctl_name with b'b', 1; u8) => An ioctl that takes a *mut u8 (it will both read the value at the given pointer, and modify it). It will use iorw!.
ioctl!(read buf ioctl_name with b'b', 1; u8) => An ioctl that returns an array of u8. It will take a *mut u8, and a len: size_t.
ioctl!(write buf ioctl_name with b'b', 1; u8) => same, but takes an array instead of returning it
ioctl!(readwrite buf ioctl_name with b'b', 1; u8) => same, but both takes an array and modify it
ioctl!(ioctl_name with 0x23) => This is what a bad ioctl is. It basically just creates an alias to the ioctl function.

I guess there's a mistake in the documentation concerning this.
I think a good plan would be this :

Make all the macro except ioctl! hidden from the docs. I don't think it's possible to prevent exporting them, due to how the macro system works, but the users shouldn't use them directly. They're basically an implementation detail.
convert_ioctl_res should be removed. It doesn't serve any purpose as far as I can see, and clutters the docs with one more macro.
The docs should be rectified concerning the bad ioctl.
The docs should explain a bit better that ioctl generates functions.
https://docs.rs/nix/0.8.1/nix/macro.ioctl.html should have a link to the ioctl module at least, and some (maybe more basic) docs as well.
Similar to error_chain, it'd be nice to have examples of the generated functions. See : https://docs.rs/error-chain/0.10.0/error_chain/example_generated/index.html
I'm not sure what to do for the ioc_dir family of function. I don't think they serve much purpose, but I could be wrong.

Make all the macro except ioctl! hidden from the docs. I don't think it's possible to prevent exporting them, due to how the macro system works, but the users shouldn't use them directly. They're basically an implementation detail.

They aren't just an implementation detail. The ioctl macro can't handle a few of the truly obscure ioctl "protocols".
I don't know about "read buf". I'm willing to bet it's buggy, I haven't had to use it. At one point I scraped and auto-generated https://github.com/cmr/ioctl/blob/master/src/platform/linux-generated-x86_64.rs from the Linux headers.
The original idea with my ioctl crate was to have a one-stop shop, but when I went to include it in nix they didn't want the system-specific concrete ioctls... The idea now is to wrap the ioctls you need ad hoc in crates  which do something. Eg, my evdev crate wraps all the evdev ioctls.

(Sorry for slow response, busy at OPLSS)

One example that isn't addressed here is for ioctls that have no arguments. For example, I want to do something like libc::ioctl(fd, TIOCEXCL). It doesn't appear that the ioctl! macro supports this use case. Neither does the module appear to re-export libc::ioctl. Is that correct? Do you think this is a valid use-case that should be supported by the macro, such that that's the only wrapper nix provides for writing ioctl APIs?

Is there value in providing such a wrapper ?
Technically speaking, the module does export libc::ioctl (well, as noted above, it's not directly libc::ioctl, but it should be), but it hides it from the doc see here. It probably shouldn't.
After some investigation, it turns out it's impossible to document functions generated by a macro in rust. See #571 and https://stackoverflow.com/questions/41361897/documenting-a-function-created-with-a-macro-in-rust.
So I'm wondering if it'd be possible to transform ioctl! to support something like
ioctl! {
    /// Some doc-comments
    readwrite some_ioctl(type: b'b', nr: 1, arg: some_arg)
}

This syntax looks dreadful so if someone has a better idea, feel free to comment. But the basic idea is to allow the doc comments to be inside the macro invocation so we can use it to generate the function with it.

@roblabla What do you mean by that comment? You mean we should re-export libc::ioctl in addition to our own ioctl! macro?

My use case for TIOCEXCL is still not supported by nix if I understand this discussion. Basically bad still assumes that there's data, so should a bad_none also be added?

@roblabla If you look at the rust-spidev source you'll see that the * buf ioctls expect the user to pass the total size in bytes as len, not just the number of elements. I think we should move that into our macro-generated function instead of relying on the user to do that. But at that point why even have these consume a raw pointer when they could take a slice reference and pull the length straight from that? I imagine there's a safety issue with that, but I'm not seeing it.

I'm also trying to figure out if the generated ioctl! can't be made safe by default if we use & and &mut references instead of raw pointers. I would think this should work, so I tacked on a commit that changes all of them. Please check out my latest changes to #670. I'd love to get some feedback there.

Also, if you wanted to see what the API looks like for a new project, I've added a branch for replacing my ioctl-rs dependency with using nix's ioctl! macro directly instead. You can see what this looks like here.

I'm also trying to figure out if the generated ioctl! can't be made safe by default if we use & and &mut references instead of raw pointers. I would think this should work, so I tacked on a commit that changes all of them. Please check out my latest changes to #670. I'd love to get some feedback there.

I don't think we can ever correctly make these generated functions safe.  In order to make the calls safe many system calls require additional semantics (that go well beyond the ioctl call itself) be followed.  A common pattern for libraries will be to use the macros to get the FFI bindings in a convenient, declarative way and then provide safe wrappers around those.

This leads me to ask, should these functions take references then or are raw pointers still better semantics? And if we're not providing a safe API here, why is this in nix?

References can't be null. Some ioctl might need this ?
On July 13, 2017 10:43:48 PM GMT+02:00, Susurrus notifications@github.com wrote:

This leads me to ask, should these functions take references then or
are raw pointers still better semantics? And if we're not providing a
safe API here, why is this in nix?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/nix-rust/nix/issues/641#issuecomment-315196435

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@roblabla That's a good point, I wonder if there are any ioctls that actually do that. Do you know of any other Rust projects using ioctl besides rust-spidev?
I think it's better that I keep the raw pointers for now in #670. I think after that this should be good to review. Would you have some time soon to look it over @roblabla?

Sorry, had a week-end. I'll take a look at #670 :)

authors: Susurrus asomers cmr posborne roblabla


text:
Decide on some sort of structure for the docs

e.g.:
linux
|
- rhel
  |
  - 7
    |
     - centos

or:
linux
|
- rhel
  |
  - centos
     |
     - 7

or:
something else, I hope you get the point.

I prefer the former.

As do I, at least in the context of something like Fedora/RHEL/Centos based docs. Trying to organize docs that cover other topics could be quite subjective thing on how to organize them, I'm open to suggestions (and PRs) to improve the current (rough) structure of the docs.

Theodore Seán Tubbs notifications@github.com writes:

Assigned #1 to @shymega.

Wait, so what am I expected to do?
Come up with a directory structure?
--
Best regards,
Dom Rodriguez

@shymega wups, kinda assigned you w/o thinking of it at the time, xD Sorry to bother you.

Theodore Seán Tubbs notifications@github.com writes:

@shymega wups, kinda assigned you w/o thinking of it at the time, xD
Sorry to bother you.

Apology not accepted.
I expect lots of bagels to make up for this ethical monster.
--
Best regards,
Dom Rodriguez

@shymega some price-2-performance bagels?

Theodore Seán Tubbs notifications@github.com writes:

@shymega some price-2-performance bagels?

price-2

what the hell does that even mean

bagels

yes

performance

like the JVM, performance is easy to achieve and doesn't hog memory
--
Best regards,
Dom Rodriguez

@shymega

price-2-performance bagels

Inside joke between a friend and I :P

What is the status on this?

Don't quite know, been quite busy lately.Sent from my Huawei Mobile-------- Original Message --------Subject: Re: [nixheads/trivial_docs] Decide on some sort of structure for the docs (#1)From: Dom Rodriguez To: nixheads/trivial_docs CC: Theodore Seán Tubbs ,Assign What is the status on this?
—You are receiving this because you were assigned.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/nixheads/trivial_docs","title":"nixheads/trivial_docs","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/nixheads/trivial_docs"}},"updates":{"snippets":[{"icon":"PERSON","message":"@shymega in #1: What is the status on this?"}],"action":{"name":"View Issue","url":"https://github.com/nixheads/trivial_docs/issues/1#issuecomment-267601961"}}}

authors: AdrianKoshka shymega


text:
GNNs.py

Hello, thanks for your work !
Is there something wrong in class RGAT's forward function of GNNs.py ?
In Section2.3.2 of the paper, (l+1)-th iteration is relative directly with l-th iteration. But in the code, I do not see any connections that output in each iteration is individual. Specifically, there are some local variables outside in the code. Should they be put inside the for ?

Thanks for your attention to our work. The node representations are stored in ‘graph.ndata['h']’. There should be a line '_g.ndata['h'] = h' after line #279 in GNNs.py.
I mistakenly deleted the line for update ’h‘ when I was cleaning up the code for uploading.
Thank you very much for pointing out this problem in the code. I'll update the code.
'batch_num_nodes' and 'batch_num_edges' will only be used after all iterations.
If you have any other problem, feel free to leave an issue message or send an email to me.

Thanks for your attention to our work. The node representations are stored in ‘graph.ndata['h']’. There should be a line '_g.ndata['h'] = h' after line #279 in GNNs.py.
I mistakenly deleted the line for update ’h‘ when I was cleaning up the code for uploading.
Thank you very much for pointing out this problem in the code. I'll update the code.
'batch_num_nodes' and 'batch_num_edges' will only be used after all iterations.
If you have any other problem, feel free to leave an issue message or send an email to me.

Thanks for your attention to our work. The node representations are stored in ‘graph.ndata['h']’. There should be a line '_g.ndata['h'] = h' after line #279 in GNNs.py.
I mistakenly deleted the line for update ’h‘ when I was cleaning up the code for uploading.
Thank you very much for pointing out this problem in the code. I'll update the code.
'batch_num_nodes' and 'batch_num_edges' will only be used after all iterations.
If you have any other problem, feel free to leave an issue message or send an email to me.

Hi starry-y:
I have updated the code.
Thanks again for pointing out this problem.
Have a good day!
Feel free to reopen it if you have any other questions.

Thank you very much ~!

repo: nju-websoft/AdaLoGN


text:
Variant "烹"

In Guangyun (廣韻), the character 烹 is written as 亨.

v0.1.0 已加入（忘了在 commit 裡寫了 :joy:）


text:
Zoom configuration button disappears under navigation buttons in landscape

Turn phone to landscape, tap in the middle in reader mode. Zoom button should be top right, but the navigation buttons hide it.

Thanks for noticing. Fixed in v1.3.0

authors: mkaito nkanaev

repo: nkanaev/bubble


text:
Provide code (not data) for Human3.6m + SMPL training

Hi there, great job!
Although I'm aware that obtaining the corresponding SMPL parameters for Human3.6m is now beyond the license, it would be super useful if the code for training on these parameters were still available.
I'm in a fortunate position that I had them saved before they were taken down so want to be able to train directly on them, but more broadly, other users may wish to implement their own MOSH procedure to generate these parameters in order to reproduce the results.
I'm looking at the code you've used for Unite the People as a template but if you could provide the Human3.6m code that would be awesome.
Thanks,
Ben

The code for training is already available on this repo. You just need to choose the FullDataset in the command line options.
We include code to prepare the test data of Human3.6M for evaluation. You can use this code to create the .npz file for the train data with only trivial modifications. You will need though to manually add the SMPL betas and shape parameters in the npz file. Our dataset class should be able to handle all that with no changes.

That's great thanks -- I'll close issue for now :)

I'm not sure this is quite trivial yet... The version of SMPL parameters I have contains a series of pkl files named _cam_aligned.pkl. In these files there is a 'new_poses' and 'betas' entry.
I'm struggling at present to get my SMPL renders to line up with the 3D key-points from S24 which originally come from 'D3_Positions_mono'.

I wonder if you have any tips on getting this to work?

Did you try to align them? E.g. subtract the 3D location of the same joint for the 2 sets of joints? This should remove any spatial offset.

That would work in theory, although (as far as I know) your code only expects a set of shape & pose parameters for SMPL... I wouldn't be able to provide these offsets downstream?

This is the standard process used in most implementations. We do not explicitly regress depth or the precise translation of the object in the camera coordinate system. In the training and evaluation code as you can see, I align them at the root joint. So it should work as intended with the pose and beta parameters we have.

I see... In this case, does it not matter that the 3D joints generated by the SMPL model (via shape + pose) align with the 3D key points from S24 (via D3_positions_mono) in the preprocessing script?

Yes it does not matter. But you might have to check this issue, where they had to reflect the pose.

Thanks so much for the help, and the tip about the 'upside-down' people. I'll close the issue again and train tonight.

As a very brief final question... is it strange that I can't see any 2D positions marked on the Human3.6m images when I view in tensorboard? It was this that began my debugging exercise -- I assumed I had them positioned incorrectly.

You should also populate the training .npz files with the correct 2D joints. This is probably why you can't see the 2D locations here.
Also, for the SMPL parameters, you can confirm that they are correct by generating the mesh and projecting it to the image. Then you can easily evaluate the alignment between the model and the image.

Hi @nkolot  , what is the different processing between *.pkl and the *_camx_aligned.pkl, or could you tell me where I can find the process scripts? I want to get the continuous smpl mesh.

Hi @nkolot , what is the different processing between *.pkl and the *_camx_aligned.pkl, or could you tell me where I can find the process scripts? I want to get the continuous smpl mesh.

Hello, have you found the process scripts to get the continuous smpl mash?

authors: LeoJoy39 NewCoderQ benjiebob geopavlakos nkolot

repo: nkolot/GraphCMR


text:
[Improve code]: lib/* 手動formatter・Linter対応

Resolves #58
本PRで行われた変更

再代入のない変数にconst宣言を追加 (6c056c348ed9b846ae19b1ceae3e47e809d64e4e)
Astroの環境変数を文字列とみなす記述を追加 (a7a4af9f1361ffe0638ea19be43491e567dc9c4f)
Nullish判定を明記 (08cb5fef13a1267b3f0c544d1ac48314fee7a1dd)
コメント内の空白形式を変更 (a33a3283aaf962ab09c293f3031bd714234b370d)
変数の型情報を明記 (e8bc3603707876354d11d033ae35176795a9fc6b)
Prettierによるコードの整形 (*.tsx, *.astroの変更なし)
ファイル名getIdの綴りを修正 (e5835ecf5098d95d9af405a78614561604f223a8)
Astro API用の型をZodで再定義 (c0b67f921f6aad6bee4ca94074e8f6dfe146e059)
Astro APIのレスポンス取得箇所にZodのバリデーションチェックを実装 (700b53181e13be4e662205cb0e536f86141c76f8, 3e1565ab8fe3f012926623bb828a6380aaf09496)
pagedbAPIのレスポンスに用いられる型名が、モジュール間で重複しないよう変更 (bad010e12f47a96a6c8c9fd302fedbbee3843cbb)
APIレスポンスの型定義厳密化に伴い、影響箇所を修正 (3e1565ab8fe3f012926623bb828a6380aaf09496)
getOgpMetaエラー時のレスポンス処理で不足していたstatusを追加 (dcaed422cb197e311b98ff402f3ce553e48de9d1)

ひとまずESLintのエラーを解消し終わりました
レビューをお願いします！

https://github.com/nkte8/skyshare/pull/84/commits/967b3278408780d935a0f1d8ffa5578e7a594f6f Zodオブジェクト命名規則の統一
https://github.com/nkte8/skyshare/pull/84/commits/4fd4e58ebfa102f12ab4c87186897d55d9a7d22e getOgpMetaのエラーレスポンスからhtmlを削除
https://github.com/nkte8/skyshare/pull/84/commits/ce937a78725085128e574cbfd463ea6b26e7aae5 使用されていないレスポンス型定義用のJSONを削除
https://github.com/nkte8/skyshare/pull/84/commits/0fc4c2d63d9c484a544fee9a5ca02badc3fed685 pages/post/[slug].astroエラー型判定の実装を改善

上記4点対応済みです。確認をお願いします！

@nkte8
今のタイミングで、エラーの型判定箇所を統一しておきたいですね

https://github.com/nkte8/skyshare/pull/83#discussion_r1559518736

こちらで一度、方針を伝えていただけるとありがたいです！

@ZEKE320

エラーの型判定箇所を統一しておきたいですね

上について、https://github.com/nkte8/skyshare/pull/83#discussion_r1559757051 での議論通り、error in valueでの判定に揃えていただいてOKです。以下コメントです

getOgpMeta関数については、ATProtoでのエラー時のレスポンスを同じような形式、error,messageで返すようにしているので、これと同じ方針を取っていただいて大丈夫です！

現在はtypeによりユニオン型として処理可能なようにしていますが、この方法でパラメータを外せそうですね。これは別途Issueを上げときます

getOgpBlobについても、現在はレスポンス自体発生しない作りになってしまっていますが、error in valueの判定によって、クライアント側でエラーハンドリングができそうな気がしますね

上と同じ題目でIssue上げようと思います。

@ZEKE 確認ありがとうございます！

こちらの件ですが、あまり良い実装例が思い浮かばず...すみません。
一度別のIssueでお願いしたいと思います。

承知です！

ここで条件式をif (!("error" in resDeletePage))とした場合、resDeletePage as typeof etypeの型アノテーションを削除できるのですが、おそらくresDeletePage.result === "ok"も判定したいということですよね

ここなんですけど、そもそも元の処理が以下のようになっています。
firebase/functions/src/editDbEndpoint/entrypoint.prod.ts
...
        if (resPagedbdel === null) {
            response.status(500).send(errRes(500))
            return
        }
        if (typeof resPagedbdel.result === "undefined") {
            response.status(502).send(errRes(502))
            return
        }
        // 正常に削除完了
        response.status(200).send({
            result: "ok"
        });
        // OGPを削除
        const ogpFilename = `${handleFromId}/${rkeyFromId}`
        await deleteOgp({
            env: envName,
            ogpFilename: ogpFilename
        })
        response.end();

このAPIだいぶ昔に書いたのですが、多分レスポンス自体に意味はなさそうなんですよね...エラーが発生しなかった場合は必ずresponse 200で、{ result: ok }が返却され、それ以外の200レスポンスは無い感じです。
現在のコードではerrorの判定方法が曖昧だったから念の為条件を書いた、というように見えています。過去の自分ならやりそう。
ので、resDeletePage.resultの判定は消しちゃっていいです。おおもとのこのAPIも改善しようと思います。

@nkte8 返信ありがとうございます！
対応行いましたので、再度レビューをお願いします


text:
Make X-Github-Event optional for Gitlab usage

I want to use githubhook for Gitlab as well. Its payload is very similar. Unfortunately there is no X-Github-Event header set, so your script will return a 404. I have commented out  this section and the rest is working for Gitlab too!
(Although the event variable remains undefined as neither Gitlab's payload is sending the event type explicitly nor a header similar to X-Github-Event. But that's okay.)
I think the easiest way would be to add a config option to omit the check for the X-Github-Event header field? :)

looks like gitlab now sends an X-Gitlab-Event header, so this support is on its way

authors: fnogatz nlf

repo: nlf/node-github-hook


text:
Repetitive data type while reading

Is this possible to get a value with auto data type detection?
Consider following:
struct Test {
       std::string value;
       int32_t index;
       std::vector<int32_t> acro;
}

To parse these, we need to do the following:
void from_json(const json& j, Files::Chapters::Test& p) {
    p.value = j.at("value").get<std::string>();
    p.index = j.at("index").get<int32_t>();
    p.acro = j.at("acro").get<std::vector<int32_t>>();
}

Thats quite a boilerplate.
We can also do this:
void from_json(const json& j, Files::Chapters::Test& p) {
    p.value = j.at("value").get<typeof(p.value)>();
    p.index = j.at("index").get<typeof(p.index)>();
    p.acro = j.at("acro").get<typeof(p.acro)>();
}

As you can see, this is repetitive thus redudant. Can't we simply get value with the data type of a object we assign to?

You can at least do this:
void from_json(const json& j, Test& p) {
    p.value = j.at("value");
    p.index = j.at("index");
    p.acro = j.at("acro").get<std::vector<int32_t>>();
}

For the vector, there seems to be confusion. Are the first two lines what you want?

Yep, good for common data types.
Thanks 👍

authors: nlohmann pompex

repo: nlohmann/json


text:
Add input adapter tests

This PR adds tests for the new input adapter implementation from #2145.

@FrancoisChabot I added some tests to check all possible character types. Strangely, the UTF-16 and UTF-32 tests fail on MSVC 2015, see https://ci.appveyor.com/project/nlohmann/json/builds/33373571. Any idea on this?

Coverage remained the same at 100.0% when pulling 2cf16625acefe244fc508284d5c2850e08976c73 on input_adapter_tests into 28048d82077916b88e373479dad64c269aecdeb5 on develop.

Thanks! I'll give it a try.

Looks good, thank you!

authors: coveralls nlohmann


text:
Artifacts from Python <=2.6

There are some artifacts from Python <=2.6 which is irrelevant today in Python 2.7 and Python 3.x, should we remove them?
Pylint caught one of them at https://github.com/nltk/nltk/blob/develop/nltk/decorators.py#L27

nltk/nltk/decorators.py:30: [E0401(import-error), ] Unable to import 'sets'

try:
    set
except NameError:
    from sets import Set as set

See also: https://stackoverflow.com/a/38042101/610569
Are there other artifacts from Python <=2.6 that anyone has noticed?

Python 2.6 is not officially supported, so in my view remove any code that only exists to support older versions such as <= 2.6

authors: alvations purificant

repo: nltk/nltk


text:
Using plugin for Amazon RDS

Hi, I am using Amazon RDS. How can I add .so file in there. Is there any way to write these function using SQL procedure or function instead of c plugin.

I have not used RDS, so I don't know what is possible there. If you do not have access to install new software on the db server, then I doubt you'll be able to install a UDF.
MySQL does not have a time function that returns milliseconds. The id's generated by this projects UDF depend on milliseconds. You can do roughly the same thing using seconds (UNIX_TIMESTAMP) and a flickr style Ticketing table like:
CREATE TABLE Tickets64 (
    `id` bigint(20) unsigned NOT NULL auto_increment,
    `stub` char(1) NOT NULL default '',
    PRIMARY KEY (`id`),
    UNIQUE KEY `stub` (`stub`)
) ENGINE=MyISAM;

DELIMITER $$

DROP FUNCTION IF EXISTS generate_shard_id$$
DROP FUNCTION IF EXISTS shard_id_to_utc$$

CREATE FUNCTION generate_shard_id( shard INT )
RETURNS BIGINT UNSIGNED NOT DETERMINISTIC
MODIFIES SQL DATA
BEGIN
    DECLARE seq_mask INT;
    DECLARE seq_id BIGINT;
    DECLARE now INT;
    DECLARE internal_epoch INT;
    DECLARE retval BIGINT;

    SET seq_mask = 4095;
    SET internal_epoch = 1370070000;
    REPLACE INTO Tickets64 (stub) VALUES ('a');
    SET seq_id = LAST_INSERT_ID() & seq_mask;
    SET retval = (UNIX_TIMESTAMP() - internal_epoch) << 32 | seq_id << 20 | shard;
    RETURN retval;
END
$$

CREATE FUNCTION shard_id_to_utc( id BIGINT )
RETURNS BIGINT UNSIGNED DETERMINISTIC
BEGIN
    DECLARE internal_epoch INT;
    SET internal_epoch = 1370070000;
    RETURN (id >> 32) + internal_epoch;
END
$$

DELIMITER ;

I don't know how correct the above is, but it should be close to correct. The upper 32-bits should be the unix timestamp. The middle 12-bits are an auto-increment value to prevent collisions on the same shard for the same second. The lower 20-bits are the shard the id was generated for, and you have to pass it in ahead of time. You can shift the bit allocations around to whatever makes sense for your setup.
There might be a way to get rid of the Tickets64 table, but I'm not sure how off the top of my head. The Tickets64 table provides us with a counter that will be shared across sessions and will be unique to each virtual shard.
You can also bake the shard into each generate_shard_id function per virtual shard, so that you don't need to pass it around.

authors: nmcquay pkbhadkoliya


text:
Support for React 16

I've updated React to 16 and npm gives me a Warning:
react-timeago@3.4.3 requires a peer of react@^15.0.0 but none is installed. You must install peer dependencies yourself.
Can you please confirm that it doesn't support React 16?
If it doesn't - can you please update support, or peer dependencies if it does support.

@nmn any feedback on this? I see there is a pending PR (#97) for make the change.

:+1: Update deps please

Finally out with v4.
I'm sorry for the LOOOOOONG wait.

authors: JustFly1984 TheSharpieOne nmn virgofx

repo: nmn/react-timeago


text:
Route: add support for cwnd attribute

Add support to define the route's clamp for the TCP congestion window (route's attribute name: cwnd).
According to man ip-route: It is ignored if the lock flag is not used. We have checked in the kernel that, indeed, setting cwnd without the lock flag is useless. Because of this, nmstate will set the lock flag automatically because the user's intention is clear enough just defining 'cwnd'.
Resolves: https://issues.redhat.com/browse/RHEL-19409

@cathay4t I have maintained the tcp_metric_lock_flags in RouteEntry. Otherwise we would need to consider "cwnd=20 lock-cwnd=false" as "cwnd=None", thus having inaccurate information about the route in nmstate. I fear that this can lead to future bugs.
Other option might be to use cwnd: Option<(u32, bool)> or a new enum TcpMetric { None, Locked(u32), Unlocked(u32) } that can be reused for other TCP metrics values that we might add in the future (we already have some requests).

Added tests for the cases "remove" and "remove and add".

Added tests for the cases "remove" and "remove and add".

Thanks, the integration tests look good to me.

repo: nmstate/nmstate


text:
Some fixes in version 1.1.0 ...

https://github.com/nnajm/orb/tree/v1.1.0/dist/v1.1.0
In this version there are several fixes, including I use this, in the implementation only changes is how to create the parameters.

I try your version but  you missing this
https://github.com/nnajm/orb/issues/35#issuecomment-148201322
for example.
Can you explain me please about several fixes ?
Thank's

authors: fcafra marciopaulinocampos

repo: nnajm/orb


text:
lose data point when .addData

When I add data to chart with addData, there seems a problem.
https://gist.github.com/fxp/44f963268200d6a4f4e1
https://docs.google.com/file/d/0BzmrcKHzthMnWXhWcXhqUzNINjg/edit?usp=drivesdk

need a test case to get anywhere with this issue, closing unresponsive

authors: fulldecent fxp


text:
[modified] modified mlops-plugin-parser for parsing updated json format.

json file is updated from separated files to a single file.
add parsing updated json format code in mlops-plugin-parser.cc.
an example of the json file is shown below. The name of the json file is rpk_config.json.

{
    "models": [
        {
            "name": "image_classification",
            "model": "mobilenet_v2_1.0_224.tflite",
            "activate": true,
            "description": "Image classification model for mobile devices (version 2.1.0)"
	},
        {
            "name": "object_detection",
            "model": "ssd_mobilenet_v1_100_320_uint8_default_1.tflite",
            "activate": true,
            "description": "Object detection model for system (version 1)"
        }
    ],
    "pipelines": [
        {
            "name": "pipeline1",
            "pipeline": "videotestsrc is-live=true ! videoconvert ! tensor_converter ! tensor_sink async=false"
        },
        {
            "name": "pipeline2",
            "pipeline": "audiotestsrc ! audioconvert ! audio/x-raw,format=S16LE,rate=16000 ! tensor_converter ! tensor_sink"
        }
    ],
    "resources": [
        {
            "name": "ml-resource",
            "path": [
                "orange.png",
                "orange.raw"
            ],
            "description": "The is sample data file."
        },
        {
            "name": "ml-resource2",
            "path": "labels.txt",
            "description": "This is another sample data file."
        }
    ]
}

@anyj0527 @yeonykim2 Now merging this PR, please prepare next commit for rpk installation.


text:
[BUG] refreshCookie() fails

Describe the bug
refreshCookie() fails to refresh the token provided.
To Reproduce
const rbx = require("noblox.js");
async function startApp() {
  await rbx.setCookie(
    "_|WARNING:-DO-NOT-SHARE-THIS.--Sharing-this-will-allow-someone-to-log-in-as-you-and-to-steal-your-ROBUX-and-items.|..."
  );
  let currentUser = await rbx.getAuthenticatedUser();
  console.log(currentUser);
  rbx.refreshCookie(
    "_|WARNING:-DO-NOT-SHARE-THIS.--Sharing-this-will-allow-someone-to-log-in-as-you-and-to-steal-your-ROBUX-and-items.|..."
  );
}
startApp();

Run the code.
Notice getAuthenticatedUser() succeeds as expected,
When attempting to refresh the cookie via refreshCookie() it'll throws an error:

const cookie = cookies.toString().match(/\.ROBLOSECURITY=(.*?);/)[1]
                                                                 ^

TypeError: Cannot read properties of null (reading '1')
    at node_modules\.pnpm\noblox.js@6.0.2\node_modules\noblox.js\lib\util\refreshCookie.js:42:74
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Expected behavior
Returning a new cookie.
Additional context
Upon further investigation, I noticed that the ROBLOXCOOKIE is no longer accessible via https://www.roblox.com/authentication/signoutfromallsessionsandreauthenticate.
This is returned instead:
rbx-ip2=1; domain=roblox.com; expires=Mon, 30-Sep-2024 06:11:21 GMT; path=/, RBXEventTrackerV2=CreateDate=09/30/2024 00:11:21; domain=roblox.com; expires=Fri, 16-Feb-2052 05:11:21 GMT; path=/, GuestData=UserID=-userid; domain=.roblox.com; expires=Fri, 16-Feb-2052 05:11:21 GMT; path=/

I would just like to note that refreshCookie is a deprecated function. Non-expiring cookies can be generated via logging in incognito mode.

This is a deprecated function pending removal from the library. This behavior is not a bug.

authors: Faf4a alanbixby commonly-ts


text:
Add event tracking

So you can see missions, nm hosts, time left, get warnings about finishing, etc. As per project goals.

New event format is nice, and this has never been that useful. Closing.
Perhaps warnings about event end might be good to have, but I'll add those separately later if so.
Or as part of the todo feature, or #34 perhaps.

repo: noccu/orchees


text:
Scroll assist

I notice when i have very long workflow then i have to move to the exact position to drop the step
Can we have something like a Scroll assist enable so that when i begin drag the step and move its around then the workflow able to move up,down, left, right
I can imagine if i move the step to the bottom of the svg then we can move up the workflow and vice versa
Its would be really cool to have that because all the workflow libs i found dont have this fearture
Like in this video
https://github.com/nocode-js/sequential-workflow-designer/assets/59781669/b6d6a547-dbfb-4c8a-bae9-5d80555f4ff8

Hi! This is a planned feature. You may increase a priority under a consulting service.

Hi @b4rtaz is this feature available or is it yet to be released?

@raBot1994 it's not available.

I'm closing this issue for now.

repo: nocode-js/sequential-workflow-designer


text:
[SD] Fix encoder error for model_max_length not beeing 77

Fix the error reported here: https://discord.com/channels/973663919757492264/1092903312740851843
Tested on prompthero/openjourney and confirmed:
pipe.tokenizer.model_max_length is returning 77 instead of 64, ending in a tensor shape error.
I suspect this tokenizer.model_max_length is always returning 77.
To fix the problem the real length was passed as an argument, and we're not relying on this tokeniser property anymore.
Wouldn't it be more appropriate to fix the property itself ?
I check the code and noticed than it is also used in the LoRA trainer.

lets land this as a hotfix and evaluate the right fix.

repo: nod-ai/SHARK


text:
Fix issues 571 and 572 by adding .nvmrc and updating .gitignore

.nvmrc sets the Node version to stable
.gitignore is based on the template from https://github.com/github/gitignore

Coverage remained the same at 100.0% when pulling 243cd9354c86d32dbef1ea7b5e2848ce96988208 on jkwuc89:gitignore_nvmrc into 615d703023fd9ff913da667dd036791b135917fa on node-apn:master.

repo: node-apn/node-apn


text:
Undefined symbol

I create a C code:
#include "stdio.h"

#if defined(WIN32) || defined(_WIN32)
#define EXPORT __declspec(dllexport)
#else
#define EXPORT
#endif

EXPORT  void etat_periph(char* periph,char* etat){
FILE* fichier=NULL;
fichier=fopen("log.txt","w");
fprintf(fichier,"The state of  "+ *periph + " is :"+ *etat);
fprintf(fichier,"**********END**********");
fclose(fichier);
}

EXPORT  void user_connect(char* user,char* date){
FILE* fichier=NULL;
fichier=fopen("log.txt","w");
fprintf(fichier,"***********New User*********");
fprintf(fichier,"User connected"+ *user + "at:"+ *date);
fclose(fichier);
}

ex.js:
var ffi = require('node-ffi');

var libfile = ffi.Library('./libfile', {
  'etat_periph': ["void",["string","string"]],
  'user_connect':["void",["string","string"]]
});
var current_date=new Date();
var date=current_date.toString();
libfile.user_connect(user,date);

then I run this command:
gcc -shared -fpic ex.c -o libfile.so

but when I run node ex.js I got this error message:
Error: Dynamic Symbol Retrieval Error: ./libfile.so: undefined symbol: etat_periph

It should be declared as extern or extern "C".

repo: node-ffi/node-ffi


text:
exposing file writable stream errors (from #316)

thanks to #316 by @gabipetrovay, closes #469, possible fix #470 too
Co-authored-by: Gabriel Petrovay gabipetrovay@gmail.com

Yea... of course, it breaks the "legacy" tests :D

Okay, i don't get it. Even with fs.createWriteStream the this._writeStream is undefined :scream: WAT?!

repo: node-formidable/node-formidable


text:
Null fix

Closes #4 (and then some)

:accept: Thank you for getting this done quickly!

authors: Fluidbyte stephen-ta

repo: node-modli/modli-mysql


text:
Performance Issues Rendering Lots of Text

I'm not sure if this is just a limitation of the shear complexity of rendering text on the screen, but I'm getting fairly slow rendering of lots of text on the screen:

It's taking around 250ms to render each time.  I've tried converting it all to paths but it doesn't seem to help.  Is this an expected performance limitation or is there something that can be done?

I've been rendering way more in way less time. ( see for example http://www.ideoloom.net/ )
However I'm caching glyphs in mini canvases and then paste them (a given glyph with a given size and color doesn't need to rendered twice)
https://github.com/nodebox/opentype.js/issues/286

Hi @darkfrog26,
rendering text is very complex indeed. Opentype has not been designed as a fast rendering library (what for, anyway ?) but as a glyph and font manipulation tool. Things could be improved, though.

I'm building a framework that, I'm hoping, will be a viable alternative to using HTML, but everything is drawn in Canvas.  The performance issues create serious problems with that being possible.

I suggest profiling to see which parts are slow (and then proposing a PR that fixes it ;-)).
As always, the solution will be caching. If you think about "normal" font rendering, the cache the glyphs of a specific font at a specific size in a texture atlas. If you want the same performance I think you will end up with a solution very similar to that.
Rendering a texture atlas from OpenType.js is out of scope, but I imagine you could build a library on top of OTjs...

The problem is, in the test I'm running I'm playing with a scenario that sets the fill of the text path to a video, so it needs to re-render with every video frame.  Obviously this is a pretty crazy scenario, but I figured if I could get the performance good enough to do that then HTML can effectively be considered antiquated. :-p
Unfortunately, this means that caching isn't really an option apart from caching the paths.  I have been considering using Path2D on browsers that support it, but I'm not sure if that will really offer much of a performance benefit over drawing the paths on-demand.

FYI, two changes in the way I deal with rendering paths increased performance from 250ms per render to 50ms:
1.) I removed all open and close path calls between letters so the entire block of text is represented by a single path.
2.) Utilize Path2D (https://developer.mozilla.org/en-US/docs/Web/API/Path2D) instead of raw instructions to canvas context (made a significant improvement per render).
Any other suggestions are appreciated, but 20 renders per second is pretty decent for the level of complexity I'm drawing (especially since I'm up-scaling rendering for retina displays, so it's rendering at twice the displayed size).

In case you want a video in the fill, how about just making a white/transparent cookie cutter of the whole text and apply it as "and-put" on each frame.
Heck you can even overlay two canvases, or a canvas above a  tag.

PS: the native type rendering libraries of your operating system do glyph and even word caching too. Also on the very first render of a new glyph aren't that fast either, native and canvas.drawText().
@fpirsch for me performance is important too, but as I said, opentype.js is very acceptable, if added some caching. Maybe some things can be improved, but IMO opentype.js is in the upper field of doable already anyway.
PPS: The reason why I switched to opentype.js from canvas.drawText() are unrepairable issue with textzooming there. First there is an upper limit in text size which makes unlimited zoom not possible. Secondly native canvas.drawText() adds fonthinting rounding errors to text propagation, while opentype.js can be changed for each letter to be rounded, but not add rounding decissions to following letters. (that is "oooooooooooooooo" and "oooooooooooooooo" in a slightly different font size can have suddendly vastly different total lengths)

@axkibe I'm not sure I understand the "cookie cutter" approach you're talking about...can you elaborate on how that would work?

Just make a transparent canvas above a video element. Or make two canvases atop each other one in which your text is transparent and the lower one behind with the animated content (however you want to animate it).
The web is full of examples that do this, it's simple CSS.

Ah, I see what you mean. Thanks. :)

:+1: for Path2D. Except that it only works in the browser, and it is not editable (remember OT.js is initialy a glyph edition library). Path2D could be used alongside the internal representation, just for rendering. But then memory could become an issue.

I understand, and I wasn't suggesting adding it to OpenType.js, but rather just as some feedback for anyone else looking to optimize their rendering.  It's incredibly unclear based on online reading if Path2D offers much benefit, and I'm here to say that it definitely does!

Just wondering, what you want to do can also be done with conventional canvas.strokeText -- using the stroke for globalCompositeOperation = 'destination-out' to cut out transparency. For this there is no need for opentype.js

authors: axkibe darkfrog26 fdb fpirsch


text:
[Apiary] Typos endpoints

Padrão REST determina endpoints com resources no plural
Endpoint de Criar um novo compartilhamento consta um parâmetro id desnecessário

http://polls.apiblueprint.org/compartilhamento/id

Endpoint de Recuperar lista de compartilhamentos consta um parâmetro id que na verdade é user_id

http://polls.apiblueprint.org/compartilhamento/id?page=

Endpoint de Recuperar lista de compartilhamentos não lista o parâmetro de id/user_id em Parameters
Endpoint de Recuperar lista de compartilhamentos não determina quantos compartilhamentos terão por página

Não tem listado o endpoint de get de um único compartilhamento por ID

repo: nodebr/nodebr

license: isc


text:
What does listener param do on Load?

related to #426
I would like to use it but not sure what it does. If #426 is correct, can I add a PR for docs?

To be honest, i have no idea why it was accepted and how consistent is it :). This parser has no right AST/Events layer and i would not recommend use related features. IMO it doesn't worth to promote this in docs.

Would be nice to see this documented so it can end up in the typescript definitions.

Would be nice to see this documented so it can end up in the typescript definitions.

It's not documented because we don't like to promote it. It works "as is", without any guarantees.

authors: diberry dinofx puzrin

repo: nodeca/js-yaml


text:
Rewrite scalar dumper for correctness

Rewrote the scalar dumper with an emphasis on rigor, based on a
careful reading of the YAML 1.2 spec and testing against LibYAML.
Corrections
Block style chomping accounts for added the extra newline
added by subsequent elements or at the end.
Fixes #238.
Top-level block scalars are indented.
Fixes dumper side of #221.
Folded style should be reliable now. The old dumper was not aware of
the subtle rules for more-indented lines.
More-indented lines no longer cause extra newlines to be added.
(The old dumper also had an off-by-one error that dropped
the last character from a long first word on a line.)
Fixes #215, #222. Removes #217 workaround.
Literal and folded styles can represent arbitrary "printable" strings,
including leading/trailing whitespace.
(Hopefully this improves readability for many use cases.)
NB. For the 'construct-string-types' dumper test, the strings are
dumped correctly. The test fails because a loader bug
loses a newline when using the keep "+" chomping indicator.
Additional improvements
Added test suite covering several former bugs, new edge cases,
and new expected behaviors. All previous applicable tests are included.
Styles are chosen in a well-defined order.

Plain and single are preferred for single lines under the width limit.
Folded is preferred when a line is longer than the width limit
(if enabled) and does not begin with a space.
Literal is used for all other multi-line "printable" strings.
Double-quoted is only used when a string is unrepresentable otherwise.

Plain style is relaxed to include more characters and strings.
Progress on #183.
As indent increases, line width decreases down to min(lineWidth, 40).
Setting lineWidth to -1 disables wrapping.
Previously there was unexpected behavior past 40 indent:
narrow lineWidth suddenly jumped to 40,
and -1 (no limit) suddenly enforced a limit of 40.

Very impressing. This week surprised me so much - 2 PRs (here & in pako), impossible without deep understanding of subject by authors.
@dervus could you take a look?

I can take a look on the weekend. Very busy right now, sorry.

Thanks for the compliment and the quick responses. I've updated the tests.
Regarding the loader bug, it seems to occur whenever the scalar is anything but trailing empty lines:
> yaml.safeLoad('a: |+\n\n\n')
{ a: '\n\n' }
> yaml.safeLoad('a: |+\n  \n\n')
{ a: '\n\n' }
> yaml.safeLoad('a: |+\n b\n\n')
{ a: 'b\n' }

> yaml.safeLoad('a: >+\n\n\n')
{ a: '\n\n' }
> yaml.safeLoad('a: >+\n  \n\n')
{ a: '\n\n' }
> yaml.safeLoad('a: >+\n b\n\n')
{ a: 'b\n' }

Also assert.equal in tests could be replaced with assert.strictEqual for consistency. But I don't really care about it.
Overall that's very good piece of work. Thank you, @aepsilon!
@puzrin, it's good for merge. However, we need to fix that loader bug before releasing this. I'll try to look into it during next week.

https://github.com/nodeca/js-yaml/commit/e0c4e4e3dea07b68bd62022a38944ce3a5b1afb9 - updated asserts use everywhere.

authors: aepsilon dervus puzrin


text:
Cannot download node on windows

I cannot download Node on windows platform
https://nodejs.org/dist/latest/node-v4.1.0-x64.msi

you caught a tiny window where we just released v4.1.1 and v4.1.0 was still "latest", try again at nodejs.org and you'll get an accurate link
@nodejs/website I'm thinking that instead of using "latest" we should use the version number, this isn't the first issue reported with this problem, there's a few minutes delay (at least) between the switch of "latest" and a website rebuild.

I see it. Great job.

@rvagg I just fixed the link on the home page.

authors: fhemberger rvagg sitthykun


text:
node-gyp is infuriating

No matter what OS I install this on, no matter what repo, no matter what version of Node or NPM, this product ALWAYS breaks and destroys all mental logic with comparison to a working install on another machine.
This isn't a bug report, just a unsolid complaint. Close/Delete as preferred...
I KNOW it's user error. I know it's not concretely, specifically, your fault.  I KNOW it's due to folder permissions, dependency chain discrepancies, node and npm version changes, lack of build tools, vendor product not properly referencing dependency versions that are uptodate with NPM version,  etc , etc, etc, etc.... But jesus baby in the freaking manger save me from node-gyp daily.
I regret writing this already but how else can one express it.
GO ahead i dare you to clone a repo to a different machine and run npm install. I dare you! I dare me.

@ensemblebd We feel your pain.  Node-gyp is open source so please help us to improve it in any areas that are frustrating you.  One way that you could help would be to create GitHub Actions that fail.  Pull requests that put Actions into https://github.com/nodejs/node-gyp/tree/master/.github/workflows would give the community shared demonstration of failures that could be fixed.  You can pick Linux, macOS, or Windows and install any package or repo.  If we have a public working demonstration of failure then we can work to fix it.

sorry on the rant, i know it was 100% unnecessary and uncalled for. Just been a day.

Understood.  Node Sass is deprecated in favor of Dart Saas and we have so many issues on that package that we have a Node Sass --> Dart Sass label.  We have four pages of issues mentioning `bcrypt so we could probably have a label there too.
Public demonstrations of failure are super helpful and GitHub Actions is a great way way of creating them.  Your active participation can help us to improve.

@ensemblebd the dirty little secret is that we all hate it too but are stuck with it for legacy reasons and because nobody has spent the time on coming up with a better solution - or the ecosystem hasn't coalesced on an alternative yet at least.
But, if you spend enough time with cross-platform build tools, these same kinds of issues come up again and again and a lot of it revolves around communicating clearly to the user what the nature of the problem is. Projects like CMake have to put in a lot of effort on that front to paper over the difficulties. We just don't have the developer-hours available to us to invest in a product that we didn't invent in the first place. We're stuck with Google's abandonware.

authors: cclauss ensemblebd rvagg

repo: nodejs/node-gyp


text:
AWS Elastic Beanstalk Build Error: node-gyp requires that the user home directory is specified in either of the environmental variables HOME or USERPROFILE

I have aws elastic beanstalk for node js application and I uploaded my node js app (zip file) to my instance but I saw this error in aws logs
The Error
node-gyp requires that the 'user'\''s' home directory is specified in either of the environmental variables HOME or 'USERPROFILE\n' at new Gyp '(/opt/elasticbeanstalk/node-install/node-v0.8.26-linux-x64/lib/node_modules/npm/node_modules/node-gyp/lib/node-gyp.js:54:11

Package.json
{
  "name": "testing-beanstalk",
  "description": "Testing Beanstalk",
  "author": "Bugan",
  "version": "1.0",
  "private": true,
  "dependencies": {
    "express": "3.x",
    "socket.io": "0.9.6",
    "mysql": "2.0.1",
    "cron": "1.0.0",
  }
}

Any idea to solve this problem? How to set user home directory?
Thank you before

@eric-tucker :+1:

What is the current status of this issue? Because i have the same problem.

FWIW, I deployed a Node app to EB based on Amazon Linux 2015.03 today and this problem is no longer present. I poked around a bit and /opt/elasticbeanstalk/containerfiles/ebnode.py (which is used to drive the npm install) now sets $HOME.
(I'm not a fan of build tools depending on a homedir, but it does now seem to work.)

good news. Maybe I will try eb again. I gave up after many, many confusing
and stalled deployments.
On Thu, Jul 23, 2015, 5:46 PM Kyle VanderBeek notifications@github.com
wrote:

FWIW, I deployed a Node app to EB based on Amazon Linux 2015.03 today and
this problem is no longer present. I poked around a bit and
/opt/elasticbeanstalk/containerfiles/ebnode.py (which is used to drive
the npm install) now sets $HOME.
(I'm not a fan of build tools depending on a homedir, but it does now seem
to work.)
—
Reply to this email directly or view it on GitHub
https://github.com/TooTallNate/node-gyp/issues/414#issuecomment-124248111
.

--
--chad

We ended up using a slightly modified version for our problem. Leaving it here for anyone else who may need it (bcrypt specific):
files:
  "/opt/elasticbeanstalk/hooks/appdeploy/pre/50npm.sh" :
    mode: "000775"
    owner: root
    group: root
    content: |
      #!/bin/bash
      #==============================================================================
      # Copyright 2013 Amazon.com, Inc. or its affiliates. All Rights Reserved.
      #
      # Licensed under the Amazon Software License (the "License"). You may not use
      # this file except in compliance with the License. A copy of the License is
      # located at
      #
      #       http://aws.amazon.com/asl/
      #
      # or in the "license" file accompanying this file. This file is distributed on
      # an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or
      # implied. See the License for the specific language governing permissions
      # and limitations under the License.
      #==============================================================================

      export HOME=/home/ec2-user
      export USERPROFILE=/home/ec2-user

      sudo rm -rf /tmp/deployment/application/node_modules/bcrypt

      set -xe

      /opt/elasticbeanstalk/containerfiles/ebnode.py --action npm-install

Thank you so much! @rhyeal and all. Your solution did the trick. Very painless process thanks to this thread.

Don't forget to have an .ebignore file. The .ebignore file should (generally) just be:
node_modules/
This was my error - I was on a wild goose chase for hours.

Hello,
Sorry I have the same issue , I have tried your solutions but nothing works..
I have tried deerawan's config
I have tried rhyeal's config
Do you have other solutions ?
node version:  4.4.3
os: 64bit Amazon Linux 2016.03 v2.1.1 running Node.js
Thanks !

this is still an issue; deploying to aws elastic beanstalk, and running into this same issue. Also have issues with it on windows, docker, and on it goes. It literally has to be the largest point of failure in the node world. fix it for christ sakes

+1

@GuillaumeSarfati Were you able to resolve the issue?
This is still active:/

Also still having issues deploying to AWS EB. node-gyp rebuild fails… anyone came up with a solution?

A solution is outlined in https://github.com/nodejs/node-gyp/issues/414#issuecomment-37620497.  As to this:

Fix this properly - $HOME should NOT be required to install ANY software.

node-gyp needs a place to download the SDK to.  If you don't pass --devdir, it defaults to $HOME/.node-gyp.  See the README for more info.

We ended up using a slightly modified version for our problem. Leaving it here for anyone else who may need it (bcrypt specific):
files:
  "/opt/elasticbeanstalk/hooks/appdeploy/pre/50npm.sh" :
    mode: "000775"
    owner: root
    group: root
    content: |
      #!/bin/bash
      #==============================================================================
      # Copyright 2013 Amazon.com, Inc. or its affiliates. All Rights Reserved.
      #
      # Licensed under the Amazon Software License (the "License"). You may not use
      # this file except in compliance with the License. A copy of the License is
      # located at
      #
      #       http://aws.amazon.com/asl/
      #
      # or in the "license" file accompanying this file. This file is distributed on
      # an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or
      # implied. See the License for the specific language governing permissions
      # and limitations under the License.
      #==============================================================================

      export HOME=/home/ec2-user
      export USERPROFILE=/home/ec2-user

      sudo rm -rf /tmp/deployment/application/node_modules/bcrypt

      set -xe

      /opt/elasticbeanstalk/containerfiles/ebnode.py --action npm-install

Thank you this worked for me, or at least got me past this issue :)

None of the above worked for me. This is what did. In root add .npmrc file and in it:
unsafe-perm=true

Then eb deploy again and you should be good to go.
from SO

authors: GuillaumeSarfati ajf akaNightmare andythecoderman bnoordhuis chadkouse dankolesnikov deerawan fahads florianbepunkt joelwass kylev pauloaguiar91 rhyeal smoya whatch


text:
Support for latest version of nodejs v4 (Question)

Hello - are there any plans to have this module support the latest version of nodejs? What is the latest version supported? Thanks in advance...

see our fork https://github.com/FreshXOpenSource/jt400.js or wait for the pull request beeing accepted

authors: FreshXOpenSource appdevjrcigars


text:
doc: initial version of dependencies section

Signed-off-by: Michael Dawson mdawson@devrus.com

In the last Ref arch meeting we agreed this should be pulled out as a separate section from the secure development process section.

probably need to add these 2 packages in npcheck.json?
"tslib@2.3.1" ----  package which is under the non-acceptable license "0BSD".
"caniuse-lite@1.0.30001282" ---- package which is under the non-acceptable license "CC-BY-4.0".

authors: helio-frota mhdawson

repo: nodeshift/nodejs-reference-architecture


text:
chore: use brillig from acvm

Description

Problem*

Resolves #1505
Summary*
Remove the temporary acvm_brillig.rs file and use the dependency from acvm 0.13 instead.
This PR sets out to
Example

Before:

After:

Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[X ] I have tested the changes locally.
[ X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

LGTM

authors: guipublic ludamad

repo: noir-lang/noir


text:
Separate parsing of inputs from toml format from file loading.

Related issue(s)
Fixes #553
Description
Summary of changes
Format.parse (Format.serialise) no longer reads from (writes to) a file but instead receives (returns) a string. It's now the responsibility of the caller to perform any I/O on the Prover.toml/Verifier.toml files.
This has a couple of benefits:

noirc_abi no longer performs any I/O so it can be used through wasm to perform any encoding of inputs (once #546 is merged).
We can make use of Format.parse in tests to create a set of inputs without having to load an actual file. This makes it easier to perform more localised tests in addition to doing e2e tests on nargo.

As loading/writing to files is now the responsibility of Nargo, I've changed the relevant errors to be CliErrors. We're also doing some unnecessary double formatting of CliErrors which I've removed.
Dependency additions / changes
N/A
Test additions / changes
N/A
Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[x] I have linked this PR to the issue(s) that it resolves.
[x] I have reviewed the changes on GitHub, line by line.
[x] I have ensured all changes are covered in the description.

Additional context
(If applicable.)

@TomAFrench can merge pending conflicts :)

authors: TomAFrench kevaundray


text:
$or is not working on the demo examples

Hi,
Great demo at http://nolanlawson.github.io/pouchdb-find/ but here is a weird thing.
$and seems to work fine, for example
// Multi-field queries and sorting are also supported
db.createIndex({
  index: {fields: ['series', 'debut']}
}).then(function () {
  return db.find({
    selector: {
      $and: [
        {series: {$eq: 'Mario'}},
        {debut: {$eq: 1990}}
      ]
    }
  });
});

but if I replace $and with $or then I get index error (even though both indices are there)
// Multi-field queries and sorting are also supported
db.createIndex({
  index: {fields: ['series', 'debut']}
}).then(function () {
  return db.find({
    selector: {
      or: [
        {series: {$eq: 'Mario'}},
        {debut: {$eq: 1990}}
      ]
    }
  });
});

Error
Error: couldn't find a usable index. try creating an index on: or. Make sure that only $eq, $gt, $gte, $lt, and $lte are used for the indexed fields.
    at createNoIndexFoundError (http://nolanlawson.github.io/pouchdb-find/dist/pouchdb.find.js:2145:10)
    at planQuery (http://nolanlawson.github.io/pouchdb-find/dist/pouchdb.find.js:2166:11)
    at http://nolanlawson.github.io/pouchdb-find/dist/pouchdb.find.js:1663:21

The issue here is the debut selector, which can't work with the ['series', 'debut'] index because series is first, not debug. In this case, the user would indeed be expected to create an index on debut.

authors: bahmutov nolanlawson

repo: nolanlawson/pouchdb-find


text:
@nolebase/markdown-it-unlazy-img is not avalible

docs is wrong about package installation: ni @nolebase/markdown-it-bi-unlazy-img -D. It should be @nolebase/markdown-it-unlazy-img
After setting config, dev or build will be fail:

      md.use(UnlazyImages, {
        imgElementTag: 'NolebaseUnlazyImg',
      })

ENOENT: no such file or directory, open ''
Error: ENOENT: no such file or directory, open ''
    at readFileSync (node:fs:441:20)

Sorry for the inconvenience, just a small docs issue, PR is welcome.

Sorry for the inconvenience, just a small docs issue, PR is welcome.

Yes It's just a negligible minor issue.
But after sucessful installation, I still can't run successfully, like the second problem above. Do you have some suggestions?

Did you configured @nolebase/vitepress-plugin-thumbnail-hash too? It requires @nolebase/vitepress-plugin-thumbnail-hash to pre-process the images since markdown-it plugin doesn't allow async function invoking, which means I cannot perform thumbhash operations in markdown-it's context (it should not be a async constructor too).
For more futuristic perspective, asking VitePress to switch to remark is more viable way, not sticking with md-it.

Did you configured @nolebase/vitepress-plugin-thumbnail-hash too? It requires @nolebase/vitepress-plugin-thumbnail-hash to pre-process the images since markdown-it plugin doesn't allow async function invoking, which means I cannot perform thumbhash operations in markdown-it's context (it should not be a async constructor too).
For more futuristic perspective, asking VitePress to switch to remark is more viable way, not sticking with md-it.

Ok I get the key. Thank u!

authors: Kutius nekomeowww

repo: nolebase/integrations


text:
Autoplay Progress

Hi there,
I would like to display a timer to the user based on autoplay progress. Is this possible? Like a timer  counting to autoplay delay number.

Not by default. Should implemented with totally custom solution


text:
How to use swiper in touch (mobile) when I want to "Pinch"(two fingers to zoom) and "move"(one finger to move around)

How to use swiper in touch (mobile) when I want to "Pinch"(two fingers to zoom in) and "move"(one finger to move around) with picture
I found the swiper api will change the pages ,but not the move action ,when I already zoom in the pictrure and I want to see different place of the picture.
The zoom in is support by web broswer and it can be disable by
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no"  />
but I don't have any option to alter this function(zoom in)

I use a baidu touch javascript library to solve this problem.
There are their website http://touch.code.baidu.com .

Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity.
If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


text:
onSlideChangeEnd before onInit

when load the page , the "onSlideChangeEnd" event run  before than the "onInit" event  .

It is correct, because onInit runs after all required routing is done in initialization


text:
Thumbs Swiper isn't working well in Shopify hydrogen

Check that this is really a bug

[X] I confirm

Reproduction link
https://hydrogen-a5ca48aa978097b02d14.o2.myshopify.dev/products/socks
Bug description
I am developing the Shopify hydrogen theme using RemixJS now.
The thumbs swiper is working at localhost, but it isn't working well at production mode.
import React, {useEffect, useState} from 'react';
import type {LinksFunction} from '@shopify/remix-oxygen';
import {Swiper, SwiperSlide} from 'swiper/react';
import {Image} from '@shopify/hydrogen';
import {FreeMode, Navigation, Thumbs} from 'swiper/modules';
import {MediaConnection} from '@shopify/hydrogen/storefront-api-types';
import type {Swiper as TSwiper} from 'swiper';
import styles from './desktopMediaGallery.css';

type TProps = {
  media: MediaConnection;
};

export const links: LinksFunction = () => [
  {
    rel: 'stylesheet',
    href: styles,
  },
];

export const DesktopMediaGallery: React.FC<TProps> = (props: TProps) => {
  const [thumbsSwiper, setThumbsSwiper] = useState<TSwiper | null>(null);
  const {media} = props;

  return (

      <Swiper
        onSwiper={(swiper) => setThumbsSwiper(swiper)}
        height={261}
        spaceBetween={26}
        slidesPerView={3}
        freeMode={true}
        loop={true}
        watchSlidesProgress={true}
        direction={'vertical'}
        modules={[FreeMode, Navigation, Thumbs]}
      >
        {media.nodes.map((node, index) => (
          <SwiperSlide key={index}>
            <Image src={node.previewImage?.url} width={'90%'} />
          </SwiperSlide>
        ))}
      </Swiper>

        <Swiper
          spaceBetween={30}
          slidesPerView={1}
          loop={true}
          thumbs={thumbsSwiper ? {swiper: thumbsSwiper} : undefined}
          modules={[FreeMode, Thumbs]}
          className="mySwiper2"
        >
          {media.nodes.map((node, index) => (
            <SwiperSlide key={index}>
              <Image src={node.previewImage?.url} />
            </SwiperSlide>
          ))}
        </Swiper>

            <Image
              src="https://crownandpaw.com/cdn/shop/files/icon-1_1_100x.png?v=1657724047"
              height={35}
              width={35}
            />

Made in USA

            <Image
              src="https://crownandpaw.com/cdn/shop/files/icon-2_1_100x.png?v=1657724064"
              height={35}
              width={35}
            />

Tracked shipping

            <Image
              src="https://crownandpaw.com/cdn/shop/files/icon-3_1_100x.png?v=1657724084"
              height={35}
              width={35}
            />

5 Star Reviews

  );
};

How to fix it?
Expected Behavior
No response
Actual Behavior
No response
Swiper version
10.1.0
Platform/Target and Browser Versions
Windows Chrome 115.0.5790.171
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

Do you want to ask a question? Are you looking for support? Stack Overflow or Swiper Discussions is the best places for getting support

Please, don't use GitHub issues for questions


text:
Fix typo

Fix demo typo
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.
Always follow the contribution guidelines when submitting a pull request.

Merged, thanks!


text:
Add sitemap.xml

This PR has...

Introduce a new sitemap package which generates sitemap.xml dynamically
Some code refactoring

Codecov Report

Merging #34 into master will decrease coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #34      +/-   ##
==========================================
- Coverage   87.25%   87.21%   -0.04%
==========================================
  Files          23       23
  Lines         800      798       -2
==========================================
- Hits          698      696       -2
  Misses        101      101
  Partials        1        1

Impacted Files
Coverage Δ

pkg/storage/handler.go
63.91% <ø> (ø)
:arrow_up:

pkg/graphql/server.go
100% <ø> (ø)
:arrow_up:

pkg/facebook/client.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io nomkhonwaan

repo: nomkhonwaan/myblog


text:
add a snapshot feature

Add a snapshot feature
arm_now snapshot -h
snapshot create [NAME]: create snapshot of the current VM
snapshot list: list all available snapshot
snapshot use [NAME]: overwrite the current VM with the snapshot [NAME]
use case
$ arm_now start x86-i686
# do some config
# poweroff
$ arm_now snapshot create MyBestVM
$ arm_now snapshot list
MyBestVM: maybe add a description here
$ arm_now start
# run some malwares or not trustworthy things
# poweroff
$ arm_now snapshot use MyBestVM
$ arm_now start
# Just go back in time

I'll try to do that this weekend my man :)

authors: SakiiR nongiach


text:
More reminders about right to protection about retaliation

some people are afraid to even mention their landlord's name

Might even want to allow the tenant to leave the landlord's name blank.

Make LL's address optional.


text:
Supporting supplemental groups for accounts

Environment info

NooBaa Version: master

Actual behavior

Currently, nsfs config setting of account creation/update does not include supplemental groups configuration.
When switching the user in FS_NAPI we only switch and restore to the user's uid gid.

Expected behavior

Support supplemental groups on account creation/update with nsfs account config.
When switching user in FS_NAPI, we should also switch groups to the supplemental groups received by the user using setgroups, and restore when restoring the uid gid.

More information - Screenshots / Logs / Other output

still not fixed, updating for stale bot

For distinguished user name we will use the following to get the supplemental groups list of the user -
https://man7.org/linux/man-pages/man3/getgrouplist.3.html
Here is the example of the linux coreutils groups cli tool that calls this library function internally - https://github.com/coreutils/coreutils/blob/master/src/groups.c
CC @madhuthorat @rkomandu

authors: guymguym romayalon

repo: noobaa/noobaa-core


text:
Optimize block download speed / fix block download stalling!

After: https://github.com/nopara73/HBitcoin/issues/6

https://github.com/nopara73/HBitcoin/commit/1fa5195c6e82df8b8fd5e0f9acc777d5730b10b6


text:
Unification dist/**/.min. files

For minificated JS files foldet in a separate folder. CSS - not.
I think it is not necessary to use an additional folder.

I actually think this is valid point. I wrote edaeccebf264a5eb3317c2a25448ec3ce3082221, but I should be very careful when releasing a new version as it will make some CDNs not to work properly as they refers to the original min directory automatically.
Thus I will leave this issue with the TODOs until the next release.

[ ] cdnjs
[ ] JSDelivr

repo: noraesae/perfect-scrollbar


text:
One liner for csh

Hi, is there a one liner to activate in csh?

The one liner is the same
dircolors ~/.dir_colors/dircolors.nordtheme
where dircolors.nordtheme is the file https://raw.githubusercontent.com/nordtheme/dircolors/develop/src/dir_colors copied directly.
You can run it standalone to see if the 'setenv LS_COLORS=<>` indeed has the color config.
In your ~/.cshrc file, you can add eval \dircolors ~/.dir_colors/dircolors.nordtheme`somewhere to set theLS_COLORS` env var.
However, I did have to change the TERM commands in the file to the following:
# Below, there should be one TERM entry for each termtype that is colorizable
TERM alacritty
TERM ansi
TERM color_xterm
TERM color-xterm
TERM con132x25
TERM con132x30
TERM con132x43
TERM con132x60
TERM con80x25
TERM con80x28
TERM con80x30
TERM con80x43
TERM con80x50
TERM con80x60
TERM cons25
TERM console
TERM cygwin
TERM dtterm
TERM dvtm
TERM dvtm-256color
TERM Eterm
TERM eterm-color
TERM fbterm
TERM gnome
TERM gnome-256color
TERM jfbterm
TERM konsole
TERM konsole-256color
TERM kterm
TERM linux
TERM linux-c
TERM mach-color
TERM mlterm
TERM nxterm
TERM putty
TERM putty-256color
TERM rxvt
TERM rxvt-256color
TERM rxvt-cygwin
TERM rxvt-cygwin-native
TERM rxvt-unicode
TERM rxvt-unicode256
TERM rxvt-unicode-256color
TERM screen
TERM screen-16color
TERM screen-16color-bce
TERM screen-16color-s
TERM screen-16color-bce-s
TERM screen-256color
TERM screen-256color-bce
TERM screen-256color-s
TERM screen-256color-bce-s
TERM screen-256color-italic
TERM screen-bce
TERM screen-w
TERM screen.linux
TERM screen.xterm-256color
TERM screen.xterm-new
TERM st
TERM st-meta
TERM st-256color
TERM st-meta-256color
TERM tmux
TERM tmux-256color
TERM vt100
TERM xterm
TERM xterm-new
TERM xterm-16color
TERM xterm-256color
TERM xterm-256color-italic
TERM xterm-88color
TERM xterm-color
TERM xterm-debian
TERM xterm-kitty
TERM xterm-termite

I use screen-256color inside my tmux sessions.

authors: LOUiSLiNG surmish

repo: nordtheme/dircolors


text:
Last update label, issue #10 ❔

Issue #10 done in this pull request
Last update label can be turned off completely from settings if user doesn't like that feature
Here's an screenshot:

I'm quite confused with the terminology used in the variable names. Do "last update", "last movement", "last change" and "last event" and "latest parcel event" all refer to the same thing? If they do, they should all be use the same terminology. I'm going to pick "last event date" as the basis of the review comments. It sounds the most descriptive to me.

I won't merge this but updated latest code from master here and corrected conflicts.

I'm quite confused with the terminology used in the variable names. Do "last update", "last movement", "last change" and "last event" and "latest parcel event" all refer to the same thing? If they do, they should all be use the same terminology. I'm going to pick "last event date" as the basis of the review comments. It sounds the most descriptive to me.
Edit: @norkator please don't merge yet, I'm reviewing.

Last update means when application updated / looked successfully parcel details from courier server
Last change looks to be checking latest timestamp when parcel had something going on at carrier's side.

Now that I am thinking we should remove that old "when got successful answer from server timestamp" and replace it fully with last change (parcel event)

@norkator Fine for me. Can't we just set showing the last status update by default? I've put an setting there so user can switch it on or off

So set the switch preference by default to true? And if no status is available, then last refreshed date will be shown.

@norkator Fine for me. Can't we just set showing the last status update by default? I've put an setting there so user can switch it on or off

Yes we can do that way too, it's already on by default: android:defaultValue="true"

Ok. I suggest let's keep it there, in my case I have a parcel that has no events but found in carrier's system.
Let the app show last status update. When it's not available, last update will be shown.
What's your opinion @norkator?

Yeah, I start merging pull requests today to get ready for next update.

authors: developerfromjokela norkator ristomatti

repo: norkator/paketin-seuranta


text:
No README.md?

The wiki home page should be the readme...

Maybe it should be the readme, not sure yet..

authors: nortxort swiftSwathSee

repo: nortxort/pinylib


text:
feat(icons): add whatsapp icon

@guastallaigor This is too pixelated. can we do better? It doesn't feel right 🙏

@evexoio Not sure what to do.. I grab the idea from here. But I will think of something or do some research on it.

@guastallaigor I think that one you linked works a little better because the phone handle is thicker and the circle seems more smoothed out, specifically the top right corner. Any reason we can't just use that design?

@guastallaigor I think that one you linked works a little better because the phone handle is thicker and the circle seems more smoothed out, specifically the top right corner. Any reason we can't just use that design?

None, I just didn't want to make a copy :smile: but that's fine I will do it.

Now I think it looks like the image I provided:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: BcRikko evexoio guastallaigor jjspace


text:
Update MetadataCoding.swift

Add a public init method to the structure, since auto-generated one is internal by default.
All public structs need to have public inits so that other users of the SDK can instantiate it.

Not sure why the GitHub workflow CI isn't running. I'm going to try closing the PR and reopening again to see if that does anything.

Temporarily lifted status check requirement to merge. I'll figure out what happened later.

authors: PavleKreator tyiu

repo: nostr-sdk/nostr-sdk-ios


text:
Update UsermodeMemory.cpp

HANDLES opened by "OpenProcess" do not return "INVALID_HANDLE_VALUE" upon failure, they return NULL (in C++11 we can just use the nullptr keyword)

Thanks for the pull request 👍

authors: laxodev not-matthias

repo: not-matthias/Nemesis


text:
Not able to build Notation project from source

What is the areas you experience the issue in?
Notation CLI
What is not working as expected?
After following the instructions to install notary from source. I'm unable to view the new changes while running docker --help.
What did you expect to happen?
I'm failing to see the following in docker --help
Management Commands:
  generate*   Generate artifacts (CNCF Notary Project, 0.1.0)
  notation*   Manage signatures on Docker images (CNCF Notary Project, 0.5.3-alpha)

How can we reproduce it?
Follow the instructions to build from source
Describe your environment
Installation method:Git
OS:  Ubuntu 22.04
Shell: bash
Golang Version : 20.1
What is the version of your Notation CLI or Notation Library?
Notation: Notary v2, A tool to sign, store, and verify artifacts.

Version:     v1.0.0-rc.1+unreleased
Go version:  go1.20
Git commit:  f463f0cb16753d5e398b3bb2d6e26a0e23e519c7

go.mod file
module github.com/notaryproject/notation

go 1.19

require (
	github.com/docker/docker-credential-helpers v0.7.0
	github.com/notaryproject/notation-core-go v1.0.0-rc.1
	github.com/notaryproject/notation-go v1.0.0-rc.1.0.20230203031935-510def1a3f48
	github.com/opencontainers/go-digest v1.0.0
	github.com/opencontainers/image-spec v1.1.0-rc2
	github.com/sirupsen/logrus v1.9.0
	github.com/spf13/cobra v1.6.1
	github.com/spf13/pflag v1.0.5
	oras.land/oras-go/v2 v2.0.0
)

require (
	github.com/Azure/go-ntlmssp v0.0.0-20221128193559-754e69321358 // indirect
	github.com/fxamacker/cbor/v2 v2.4.0 // indirect
	github.com/go-asn1-ber/asn1-ber v1.5.4 // indirect
	github.com/go-ldap/ldap/v3 v3.4.4 // indirect
	github.com/golang-jwt/jwt/v4 v4.4.3 // indirect
	github.com/inconshreveable/mousetrap v1.1.0 // indirect
	github.com/veraison/go-cose v1.0.0 // indirect
	github.com/x448/float16 v0.8.4 // indirect
	golang.org/x/crypto v0.5.0 // indirect
	golang.org/x/mod v0.7.0 // indirect
	golang.org/x/sync v0.1.0 // indirect
	golang.org/x/sys v0.4.0 // indirect
)

Hi Manas, building.md is obsolete. You don't need to run docker --help. As long as you can call notation command, you can use it directly. Thanks for your issue, we will update the installation guide later.

repo: notaryproject/notation


text:
Fix: Unknown key recipe-name

Not sure if this is the right way to fix this or not, so feel free to close it if it is not.

Thanks for the PR.
However I believe there is a better way to implement this. Added here:
https://github.com/notnotmelon/factorissimo-2-notnotmelon/commit/0e4fcf5a74c7ebc65ed08c37063f19eea6b0d09f

authors: notnotmelon rededog


text:
Update cats-effect to 3.3.12

Updates org.typelevel:cats-effect from 3.2.9 to 3.3.12.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Scalafix Migrations

org.typelevel:{cats-effect,cats-effect-laws}:3.3.0 (created no change)

github:typelevel/cats-effect/v3_3_0?sha=series/3.x

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.typelevel", artifactId = "cats-effect" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, scalafix-migrations, commit-count:1

Superseded by #396.

repo: notxcain/aecor


text:
Fixes empty env vars

Prefers empty string to bool for bash tests.

@bersace .. opm ?

OPM :-)

authors: bersace toopy


text:
Adding a basic service for loading and using CoreCLR

This adds a basic service for loading and using CoreCLR. This uses the official hosting APIs and therefore works with normal redistribution of the .NET Core Runtime.
This currently checks in the dll/lib files, which is undesirable. An issue tracking an actual vcpkg being created is here: https://github.com/microsoft/vcpkg/issues/8260.
The runtimeconfig.json should be updated to use the 3.0 RTM version once it is released Monday.

Test

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

Updated this to use the official vcpkg and renamed a few components. The unresolved comments from above are still valid and apply to the corresponding locations in the renamed files.

authors: CLAassistant tannergooding

repo: novelrt/NovelRT


text:
Auto register runners

Currently it is required to register the runner before running the terraform scripts. In branch https://github.com/npalm/terraform-aws-gitlab-runner/tree/feature/auto-register-runner I am preparing scripts so that the runner can register itself based on the registration token. Runner tokens will be kept in the parameter store.

The variable runners_token will become obsolete and replace it by a runner configuration which will be used to register the runner.
Define in the module the runner configuration as follow:
  gitlab_runner_registration_config = {
    registration_token = "<registration token>"
    tag_list           = "<your tags, comma separated"
    description        = "<some description>"
    locked_to_project  = "true"
    run_untagged       = "false"
    maximum_timeout    = "3600"
  }

And DO NOT specify the runners_token.  The runner will then be created if there is not one registered before. Registered runners will be stored in the AWS parameter store.
For migration to the new setup simply add the runner token to the parameter store. Once the runner is started it will lookup required values in the parameter store. If the value is null a new runner will be created.
# set the following variables, look up the variables in your Terraform config.
# see your Terraform variables to fill in the vars below.
aws-region=<${var.aws_region}>
token=<runner-token-see-your-gitlab-runner>
parameter-name=<${var.environment}>-<${var.secure_parameter_store_runner_token_key}>

aws ssm put-parameter --overwrite --type SecureString  --name "${parameter-name}" --value ${token} --region "${aws-region}"

Once you have created the parameter, you have to remove the variable runners_token from your config. Then next time your gitlab runner instance is created it look up the token from the parameter store.

repo: npalm/terraform-aws-gitlab-runner


text:
feat: use Slide with AppBar & ActionHeader

#238 の改善です
以下のスクリーンショットのように、
100px程度スクロールした段階で

上部AppBarが非表示になる
ActionHeaderはタイトルは張り付かず、ソートと検索のみ固定表示になる

ように変更しました

ガチャガチャと激しくスクロールを上下させるとAppBarとActionHeaderの隙間がチラ見えすることがある。

そうですね…ActionHeaderの固定表示部分はAppBarの下部に隙間なく張り付く想定で配置しているので、アニメーションの発火するタイミングの違いで微妙に隙間が生じますね。
対策としては、ActionHeader側でAppBarと重なる領域を用意しておけば、気になりにくいように改善できそうです。

対策としては、ActionHeader側でAppBarと重なる領域を用意しておけば、気になりにくいように改善できそうです。

これについては別PRで出せそうなら出してみたいと思います！

repo: npocccties/ChibiCHiLO


text:
chore: Switch change management action to shared custom action

Description
Switch to using the shared action in https://github.com/nrfta/action-change-management
How did you test the changes?
See that the change management action passes successfully

Not sure what we need to change here, to allow the action to be executed as this repo is public.

Not sure what we need to change here, to allow the action to be executed as this repo is public.

Ah, right. We can make a public version of our change management action, or just make the repo public.

This looks good to me. @josemarluedke, is there anything this PR needs?

This looks good to me. @josemarluedke, is there anything this PR needs?

Going to close this for now while we work on figuring out if we should make the private change management action public, or create a public version of it.

authors: gjarmstrong josemarluedke m-bodmer

repo: nrfta/go-paging


text:
fix: goTo command

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fix

What is the current behavior? (You can also link to an open issue here)
When trying to goTo a clip id the hyperdeck would return an error.
console.log(res)
{ name: 'goto', params: { clipId: '1' } }
Debug
sending str: goto:
clipId: 1
Response from Hyperdeck
{ code: 100, name: 'syntax error', params: {} }

What is the new behavior (if this is a feature change)?
goTo clip id now works.
console.log(res)
{ name: 'goto', params: { 'clip id': '1' } }
Debug
sending str: goto:
clip id: 1
Response from Hyperdeck
res { code: 200, name: 'ok', params: {} }

Other information:

Thanks!

authors: Vitupero baltedewit


text:
pendulum_swing_up.py example doesn't solve the task

Attached is a plot of the time domain performance of the controller after the 8 episodes. As you can see, it is not close to stabilizing about 0 or +/-2pi.

Hey @JoeMWatson,
Thanks for pointing this out, I'll look into this, I had previously run about 20 random seeds it seemed quite stable. There is always the chance that learning will diverge, but in these examples and with the chosen parameters, performance has been consistently good. I'll rerun some of these, I'll try another system too.
Could you share some details about your system, tf and gpflow versions etc?
Some things to check if you want:
Can you replicate the problem ?
Does it persist across random seeds (the random seed shouldn't be an issue but...) ?
Did PILCO get a reasonable solution on any of the previous episodes and diverged eventually or did it never get off?

Upon further investigation, it seems the random seed affects how many iterations are required for convergence. A random seed on 0 (currently on Master) needed 12 iterations but the script currently performs 8 on Master, meanwhile a random seed of 1 only required 3!
Maybe this sensitivity should be documented and a better performing seed chosen for the example script.

After recent updates and testing, performance is quite consistent across 10 random seeds so I am closing this.

authors: JoeMWatson kyr-pol

repo: nrontsis/PILCO