text:
Create @openverse/eslint-plugin package with inagural rule for analytics config

Fixes

Fixes the same issue as https://github.com/WordPress/openverse/pull/1125 but using ESLint instead of TypeScript, which allows for much more descriptive and helpful error messages.
Description

Create new @openverse/eslint-plugin package and setup scaffolding necessary for local packages including testing, typescript, etc.
Add @openverse/eslint-plugin to the base eslint configuration
Create @openverse/analytics-configuration rule to lint the events configuration

TODO:

Get frontend unit tests running locally. For some reason I can't run the frontend unit tests locally successfully at all, even after recloning the repository, clearing my pnpm cache to redownload all packages, running the tests on main.
Setup scripts for continuously building packages to make development easier. This should be possible via tsc's watch: https://www.typescriptlang.org/docs/handbook/configuring-watch.html

Testing Instructions

Checklist

[ ] My pull request has a descriptive title (not a vague title like
Update index.md).
[ ] My pull request targets the default branch of the repository (main) or
a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible
errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

I still intend to work on this, I just haven't had time this week yet. I'll try to make some headway on it today if I can but it might have to wait until next week.

Unfortunately I still cannot run the frontend tests locally, not even on main :cry: That leaves me completely blocked on further work on this PR until I can resolve that, but I'm literally all out of ideas on how to do so. I spent a bit of time trying to quickly get the tests running inside of docker, just to see if it's an environment issue, but even that fails. When I run the tests inside Docker, they fail with the same exact errors.
I'm at a loss, at this point. I don't know why the tests pass on main anywhere else or why they would fail inside a docker image. I tried to think of what environmental issues might exist, but I can't think of any that shouldn't also affect CI, and CI doesn't do anything special as far as I can tell. At least not anything that I'm not also doing on my local.

Switching to ESLint FlatConfig would make this a lot easier: https://eslint.org/blog/2022/08/new-config-system-part-2/#from---rulesdir-to-runtime-plugins
Though it looks like this could have used --rulesdir to begin with, avoiding much of the complications.
In any case, it'll be a lot easier once #2224 is merged and the configuration is simplified, especially with respect to the pre-commit configuration, which was a pain!

@sarayourfriend Now that #2224 is this blocked onto something else?

Nope! I've just been working on high priority stuff right now.
This PR needs to be re-written, so I'm going to close this PR and open an issue to assign to myself for this.

authors: krysal sarayourfriend


text:
Help needed 🙏🙏

This is what I get when trying to complie the filterscripts
Please I really need this

OK, I see. I've quickly made a new release that brings the include and examples up to date with the latest versions of FCNPC and the compiler: FCNPC-AI 1.1.2

source: gharchive/issue

authors: WoutProvost chuksthemodder

repo: WoutProvost/FCNPC-AI

license: MIT

license_type: permissive

license_source: github-api


text:
[Feature Request] More GenericModConfigMenu Support

This is based #7 .

Support the rest configs: WhoChecks, BypassInventory, ChestCoords and ChestDefs.
Add in-game config changes support.

WhoChecks config is added in #25.

In game Config changes is added in #27

BypassInventory, ChestCoords and ChestDefs configs are added in #30


text:
fix: unbind onclick for whole StyledCard

只是把onclick搬了个位置

close #16

source: gharchive/pull-request

repo: WuhanZhuRong/DonationChannel


text:
404 https://wyam.io/modules/searchindex

I tried to look at the documentation of search index, but the wyam page gave me a 404.
I tried some other random  modules, they worked. But I didn't test all.

Yikes! I think you may have found a bug in the Netlify web server :open_mouth:

Netlify has confirmed this looks like a bug and are researching. I'll update or resolve the issue here once I get an update. Thanks for finding this.

Resolved by Netlify

authors: LokiMidgard daveaglick

license: mit

license_source: bigquery


text:
int not passed from cli as int

if you pass an int to the cli it is interpreted as a string

fixed

repo: Wytamma/snk


text:
feat: add personal info (#6)

Signed-off-by: zhiweil20 kerryli0220@163.com

What is the purpose of the change
Related #6

Add lizhiwei's personal info

Brief change log

Add lizhiwei's personal info

 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.


text:
🛑 XAONIX.com is down

In 56b0ba2, XAONIX.com (https://xaonix.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XAONIX.com is back up in bba5581.

repo: XAONIX/status


text:
real word data

Very, very good work, thanks for your open source. Recently, I have been studying using this CA to simulate fire, and I see that these data and parameters seem to be given randomly in your code. I am not sure whether these data and parameters can be replaced by real-world data and how to use real-world data? Could you give me some advice? I just started my research in this direction

你好，这个程序是根据repo里的那篇pdf论文设计的，所以你可以读一下那篇文章，然后修改相应的参数。
另外，Repo里的Wild_Fire.py是单线程的版本，读起来应该比较简单，可以从那里入手。

authors: XC-Li rongtongxueya


text:
🛑 ga is down

In 17c7bb7, ga (https://codeforces.ga) was down:

HTTP code: 504
Response time: 6037 ms

Resolved: ga is back up in 9172cd9.


text:
Keeps the live data entry in the rundoc

Rather than removing all trace of the live data existing once live processing concludes and the data on disk is deleted, its entry in the rundoc is kept, but its location is changed to "deleted".

Thanks Darryl. I've fixed a missing comma and also replaced one other instance where we delete dat to be consistent with what you propose.
As soon as Travis finishes I'll merge it with master.

authors: darrylmasson jorana

repo: XENONnT/straxen


text:
Use zstd as compressor of peaks

What does the code in this PR do / what does it improve?
Because sometimes peaks chunk is very large.
Can you briefly describe how it works?
Can you give a minimal working example (or illustrate with a figure)?
Please include the following if applicable:

[ ] Update the docstring(s)
[ ] Update the documentation
[ ] Tests to check the (new) code is working as desired.
[ ] Does it solve one of the open issues on github?

Notes on testing

Until the automated tests pass, please mark the PR as a draft.
On the XENONnT fork we test with database access, on private forks there is no database access for security considerations.

All italic comments can be removed from this template.

Coverage: 93.752% (-0.01%) from 93.763% when pulling c04615708bb4e0263aa6baaaf2a8a8cb0a124b01 on peaks_zstd into fca35df0ca2fbc52bf0aab2a60d3d41c3690a646 on master.

authors: coveralls dachengx


text:
Relax unnecessary dependency constraints

There are a lot of very specific version windows in setup.py, some of which span fewer than 9 months of released versions of tools, and create a situation where it's increasingly hard to satisfy them in larger systems.
Specifically, signxml works fine with versions of cryptography that pre-date 2.1.4 (which only added an unused dummy symbol), but arbitrarily prevents users from using them.  Is there any reason to have moved the minimum version from 1.8, where it was before?  Similarly with lxml, etc?
The commit in question is https://github.com/XML-Security/signxml/commit/439ea916662a5ab215a9b0ee5b2a2f664dba7281 and unfortunately doesn't provide any rationale for the change.

Thanks for the comment. The commit does provide a rationale: the dependencies are set to match those included as APT packages in Ubuntu 18.04.
I'd advise using the release of signxml before this commit. Do you have a specific setup in which you are unable to update your dependencies?

To provide a fuller rationale: supporting wider version ranges requires testing, and this package does not currently have a test suite that tests it against older versions of its dependencies. In the absence of such testing, I choose to support only those dependency versions which are expected to be well-supported upstream, such as those bracketed by LTS operating system releases.
If you are interested in support for other dependency versions, you are welcome to submit a PR which would implement a test suite over the full range of dependency versions.

authors: kislyuk nbastin

repo: XML-Security/signxml


text:
Hope to support a1111 sd webui

Hope to support a1111 sd webui, thank you developers.

Thank you for your interest in DiffBIR! We will add this interface as soon as possible.

Thank you🤗

Thank you for your interest in DiffBIR! We will add this interface as soon as possible.

Maybe you can also consider supporting ComfyUI, which is more convenient and scalable than sd webui.

repo: XPixelGroup/DiffBIR


text:
Test the Apiary token on the spot and reset the client eventually

The following PR will make sure to test the newly grabbed token on the post and notice the user if something goes wrong.

Thanks Vincenzo, that improve usability

authors: XVincentX marcoCasamento

repo: XVincentX/vscode-apielements


text:
[FEATURE] - Add progress bar to OpenKh.Tools.IdxImg

Describe the solution you'd like
Add a progress bar either as a child window to the tool or built into the main one during the extraction process.
Describe alternatives you've considered
Detect the number of files within the IDX/IMG and show the number of files extracted over the total number rather than an arbitrary bar.

This has been discussed for quite a while.
I will look into it, although, I cannot promise if I can address it.

authors: Topaz-Reality Vladabdf

repo: Xeeynamo/OpenKh


text:
Benchmark

Fix double linked list benchmark, so both versions can run

Ideally we should include double linked list as part of the standard benchmark suite, i.e. being tracked here https://xiangpenghao.github.io/pmwcas/

repo: XiangpengHao/pmwcas


text:
Has any benchmark result for NNlib

Hi, all!
Has any benchmark result for nnlib with mace, ncnn or etc? Besides, I wanna ask which performance is better between nnlib and SNPE?
Thanks in advance.

I don't think ncnn has support nnlib yet. For Mace and SNPE, they have almost the same performance. For model prepare time, Mace is better.

Excuse, I'm little confused, what's the nnlib? Is an Android common API for deep learning? Does it have raw implementation?

It's a library which can be found in https://developer.qualcomm.com/software/hexagon-dsp-sdk as hexagon nn, you can get all the information from Hexagon DSP SDK.
So basically, it's for Hexagon DSP and is usually integrated with deep learning inference engines, e.g., SNPE, MACE.
The benchmark results of DSP of MACE and SNPE all use nnlib.

Greatly thank you, bin.
Besides, I wanna ask what's the relationship between DSP/AIP runtimes of SNPE and Hexagon NN. Of course, I wanna know the performance between them. Any idea?

DSP of SNPE is based on Hexagon NN, so its performance is also based on Hexagon NN.

Greatly and always Thanks you ~~ bin

authors: lee-bin liyinhgqw ysh329

repo: XiaoMi/mobile-ai-bench


text:
🛑 MBOT-4 is down

In ac5f9f5, MBOT-4 (https://MBOT-4.tikihed.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MBOT-4 is back up in 42bbfcb.

repo: Xiija/UpMonitor


text:
Reduce/Allreduce issues on cyt_rdma

I'm getting errors on repeated runs of Reduce and Allreduce:
...
Pass accl barrier
host measured durationUs:91.724
2th item is incorrect! (1.000000 != 2.000000)
3th item is incorrect! (2.000000 != 4.000000)
4th item is incorrect! (3.000000 != 6.000000)
5th item is incorrect! (4.000000 != 8.000000)
...

The first run succeeds.
I'm using a sligthly modified version of the script https://github.com/Xilinx/ACCL/blob/dev/test/host/Coyote/run_scripts/run.sh on commit https://github.com/Xilinx/ACCL/commit/a0ba7ea3040b026359d5f790acb7f83b67e29645
Output of first run(allreduce):

stdout
Arguments: '../accl_on_coyote' '-d' '-f' '-r' '-z' '1' '-y' '10' '-c' '512' '-l' './accl_log/fpga' '-p' '1' '-n' '1'
Running ACCL test in coyote...
Initializing MPI...
Reading MPI rank and size values...
Parsing options
Hardware rdma mode
count:512 rxbuf_size:4194304 seg_size:4194304 num_rxbufmem:2
Getting MPI Processor name...
[process 0] rank 0 size 2 alveo-u55c-07.inf.ethz.ch
Testing ACCL base functionality...
10.253.74.92
10.253.74.96
Initializing QP connections...
Exchanging QP...
Local rank 0 sending local QP to remote rank 1
Local rank 0 receiving remote QP from remote rank 1
Queue Pair: id: 1
Local Queue: local: QPN 0x000002, PSN 0x13da2b, VADDR 00007fe623800000, SIZE 00200000, IP 0x0afd4a5c,
Remote Queue: remote: QPN 0x000001, PSN 0x46045d, VADDR 00007f4951e00000, SIZE 00200000, IP 0x0afd4a60,
rank: 0 FPGA IP: afd4a5c
Rendezvous Protocol
sw nop time [us]:106.15
hw nop time [ns]:940
Start allreduce test and reduce function 0...
Repetition 0
Pass accl barrier
host measured durationUs:410.125
Test is successful!

ACCL base functionality test completed successfully!

-- STATISTICS - ID: 0
-----------------------------------------------
          Read command FIFO used: 	0
         Write command FIFO used: 	0
                 Host reads sent: 	96
                Host writes sent: 	64
                 Card reads sent: 	64
                Card writes sent: 	64
                 Sync reads sent: 	5
                Sync writes sent: 	0
                     Page faults: 	0

 -- NET STATS QSFP0

RX pkgs: 320
TX pkgs: 132
ARP RX pkgs: 2
ARP TX pkgs: 2
ICMP RX pkgs: 0
ICMP TX pkgs: 0
TCP RX pkgs: 0
TCP TX pkgs: 0
ROCE RX pkgs: 152
ROCE TX pkgs: 130
IBV RX pkgs: 195
IBV TX pkgs: 195
PSN drop cnt: 0
Retrans cnt: 0
TCP session cnt: 0
STRM down: 0

Finalizing MPI...
Done. Terminating...

stderr
XRT build version: 2.13.466
Build hash: f5505e402c2ca1ffe45eb6d3a9399b23a0dc8776
Build date: 2022-04-14 17:43:11
Git branch: 2022.1
PID: 21032
UID: 500207
[Tue May 14 12:09:44 2024 GMT]
HOST: alveo-u55c-07.inf.ethz.ch
EXE: /pub/scratch/lawirz/XACCL/integrations/pytorch_ddp/accl/test/host/Coyote/accl_on_coyote
[XRT] ERROR: No devices found
[XRT] ERROR: No devices found
[XRT] ERROR: No devices found
ACLL DEBUG: aquiring cProc: targetRegion: 0, cPid: 0
ACLL DEBUG: aquiring qProc: targetRegion: 0, cPid: 1
ACLL DEBUG: aquiring qProc: targetRegion: 0, cPid: 2
CCLO HWID: 2696576574 at 0x0
CCLO source commit (first 24b): a0ba7e
CCLO Capabilities:
Stack type: RDMA
Internal DMA:True
External DMA:False
Reduction:True
Compression:True
Kernel Streams:True
Debug:False
Doing a soft reset
Configuring Eager RX Buffers
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:64,n_pages:1
Allocation successful! Allocated buffer: 7fe622c00000, Size: 64
calling offload: 7fe622c00000, size: 64
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:64,n_pages:1
Allocation successful! Allocated buffer: 7fe622a00000, Size: 64
calling offload: 7fe622a00000, size: 64
Configuring Rendezvous Spare Buffers
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:4194304,n_pages:2
Allocation successful! Allocated buffer: 7fe622600000, Size: 4194304
calling offload: 7fe622600000, size: 4194304
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:4194304,n_pages:2
Allocation successful! Allocated buffer: 7fe622200000, Size: 4194304
calling offload: 7fe622200000, size: 4194304
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:4194304,n_pages:2
Allocation successful! Allocated buffer: 7fe621e00000, Size: 4194304
calling offload: 7fe621e00000, size: 4194304
Configuring a communicator
Configuring arithmetic
Configuring collective tuning parameters
CCLO configured
Set timeout
Set max eager size: 64
Set max rendezvous reduce size: 4194304
Accelerator ready!
Communicator 0 (0x40):
local rank: 0 	 number of ranks: 2
> rank 0 (ip 10.253.74.92:5005 ; session 0 ; max segment size 4194304) : <- inbound seq number 0, -> outbound seq number 0
> rank 1 (ip 10.253.74.96:5005 ; session 2 ; max segment size 4194304) : <- inbound seq number 0, -> outbound seq number 0

Rank 0 passed last barrier before test!
CCLO address: 0
rx address: 4
Spare RX Buffer 0:	 address: 0x7fe622c00000 	 status: ENQUEUED 	 occupancy: 0/64 	 MPI tag: 0 	 seq: 0 	 src: 0
Spare RX Buffer 1:	 address: 0x7fe622a00000 	 status: ENQUEUED 	 occupancy: 0/64 	 MPI tag: 0 	 seq: 0 	 src: 0

CoyoteBuffer contructor called! page_size:2097152, buffer_size:2048,n_pages:1
Allocation successful! Allocated buffer: 7fe621c00000, Size: 2048
CoyoteBuffer contructor called! page_size:2097152, buffer_size:2048,n_pages:1
Allocation successful! Allocated buffer: 7fe621a00000, Size: 2048
Reducing data...
Free user buffer from cProc cPid:0, buffer_size:2048,7fe621c00000
Free user buffer from cProc cPid:0, buffer_size:2048,7fe621a00000
Communicator 0 (0x40):
local rank: 0 	 number of ranks: 2
> rank 0 (ip 10.253.74.92:5005 ; session 0 ; max segment size 4194304) : <- inbound seq number 0, -> outbound seq number 0
> rank 1 (ip 10.253.74.96:5005 ; session 2 ; max segment size 4194304) : <- inbound seq number 64, -> outbound seq number 64

CCLO address: 0
rx address: 4
Spare RX Buffer 0:	 address: 0x7fe622c00000 	 status: ENQUEUED 	 occupancy: 32/64 	 MPI tag: ffffffff 	 seq: 62 	 src: 1
Spare RX Buffer 1:	 address: 0x7fe622a00000 	 status: ENQUEUED 	 occupancy: 32/64 	 MPI tag: ffffffff 	 seq: 63 	 src: 1

Removing CCLO object at 0
Doing a soft reset
Free user buffer from cProc cPid:0, buffer_size:64,7fe622c00000
Free user buffer from cProc cPid:0, buffer_size:64,7fe622a00000
Free user buffer from cProc cPid:0, buffer_size:4194304,7fe622600000
Free user buffer from cProc cPid:0, buffer_size:4194304,7fe622200000
Free user buffer from cProc cPid:0, buffer_size:4194304,7fe621e00000

Second run:

stdout
Arguments: '../accl_on_coyote' '-d' '-f' '-r' '-z' '1' '-y' '10' '-c' '512' '-l' './accl_log/fpga' '-p' '1' '-n' '1'
Running ACCL test in coyote...
Initializing MPI...
Reading MPI rank and size values...
Parsing options
Hardware rdma mode
count:512 rxbuf_size:4194304 seg_size:4194304 num_rxbufmem:2
Getting MPI Processor name...
[process 0] rank 0 size 2 alveo-u55c-07.inf.ethz.ch
Testing ACCL base functionality...
10.253.74.92
10.253.74.96
Initializing QP connections...
Exchanging QP...
Local rank 0 sending local QP to remote rank 1
Local rank 0 receiving remote QP from remote rank 1
Queue Pair: id: 1
Local Queue: local: QPN 0x000001, PSN 0x709eba, VADDR 00007fe2c6c00000, SIZE 00200000, IP 0x0afd4a5c,
Remote Queue: remote: QPN 0x000002, PSN 0xd26325, VADDR 00007f9402e00000, SIZE 00200000, IP 0x0afd4a60,
rank: 0 FPGA IP: afd4a5c
Rendezvous Protocol
sw nop time [us]:87.215
hw nop time [ns]:940
Start allreduce test and reduce function 0...
Repetition 0
Pass accl barrier
host measured durationUs:79.17
2th item is incorrect! (1.000000 != 2.000000)
3th item is incorrect! (2.000000 != 4.000000)
4th item is incorrect! (3.000000 != 6.000000)
5th item is incorrect! (4.000000 != 8.000000)
6th item is incorrect! (5.000000 != 10.000000)
7th item is incorrect! (6.000000 != 12.000000)
8th item is incorrect! (7.000000 != 14.000000)
9th item is incorrect! (8.000000 != 16.000000)
10th item is incorrect! (9.000000 != 18.000000)
11th item is incorrect! (10.000000 != 20.000000)
12th item is incorrect! (11.000000 != 22.000000)
13th item is incorrect! (12.000000 != 24.000000)
14th item is incorrect! (13.000000 != 26.000000)
15th item is incorrect! (14.000000 != 28.000000)
16th item is incorrect! (15.000000 != 30.000000)
17th item is incorrect! (16.000000 != 32.000000)
18th item is incorrect! (17.000000 != 34.000000)
19th item is incorrect! (18.000000 != 36.000000)
20th item is incorrect! (19.000000 != 38.000000)
21th item is incorrect! (20.000000 != 40.000000)
22th item is incorrect! (21.000000 != 42.000000)
23th item is incorrect! (22.000000 != 44.000000)
24th item is incorrect! (23.000000 != 46.000000)
25th item is incorrect! (24.000000 != 48.000000)
26th item is incorrect! (25.000000 != 50.000000)
27th item is incorrect! (26.000000 != 52.000000)
28th item is incorrect! (27.000000 != 54.000000)
29th item is incorrect! (28.000000 != 56.000000)
30th item is incorrect! (29.000000 != 58.000000)
31th item is incorrect! (30.000000 != 60.000000)
32th item is incorrect! (31.000000 != 62.000000)
33th item is incorrect! (32.000000 != 64.000000)
34th item is incorrect! (33.000000 != 66.000000)
35th item is incorrect! (34.000000 != 68.000000)
36th item is incorrect! (35.000000 != 70.000000)
37th item is incorrect! (36.000000 != 72.000000)
38th item is incorrect! (37.000000 != 74.000000)
39th item is incorrect! (38.000000 != 76.000000)
40th item is incorrect! (39.000000 != 78.000000)
41th item is incorrect! (40.000000 != 80.000000)
42th item is incorrect! (41.000000 != 82.000000)
43th item is incorrect! (42.000000 != 84.000000)
44th item is incorrect! (43.000000 != 86.000000)
45th item is incorrect! (44.000000 != 88.000000)
46th item is incorrect! (45.000000 != 90.000000)
47th item is incorrect! (46.000000 != 92.000000)
48th item is incorrect! (47.000000 != 94.000000)
49th item is incorrect! (48.000000 != 96.000000)
50th item is incorrect! (49.000000 != 98.000000)
51th item is incorrect! (50.000000 != 100.000000)
52th item is incorrect! (51.000000 != 102.000000)
53th item is incorrect! (52.000000 != 104.000000)
54th item is incorrect! (53.000000 != 106.000000)
55th item is incorrect! (54.000000 != 108.000000)
56th item is incorrect! (55.000000 != 110.000000)
57th item is incorrect! (56.000000 != 112.000000)
58th item is incorrect! (57.000000 != 114.000000)
59th item is incorrect! (58.000000 != 116.000000)
60th item is incorrect! (59.000000 != 118.000000)
61th item is incorrect! (60.000000 != 120.000000)
62th item is incorrect! (61.000000 != 122.000000)
63th item is incorrect! (62.000000 != 124.000000)
64th item is incorrect! (63.000000 != 126.000000)
65th item is incorrect! (64.000000 != 128.000000)
66th item is incorrect! (65.000000 != 130.000000)
67th item is incorrect! (66.000000 != 132.000000)
68th item is incorrect! (67.000000 != 134.000000)
69th item is incorrect! (68.000000 != 136.000000)
70th item is incorrect! (69.000000 != 138.000000)
71th item is incorrect! (70.000000 != 140.000000)
72th item is incorrect! (71.000000 != 142.000000)
73th item is incorrect! (72.000000 != 144.000000)
74th item is incorrect! (73.000000 != 146.000000)
75th item is incorrect! (74.000000 != 148.000000)
76th item is incorrect! (75.000000 != 150.000000)
77th item is incorrect! (76.000000 != 152.000000)
78th item is incorrect! (77.000000 != 154.000000)
79th item is incorrect! (78.000000 != 156.000000)
80th item is incorrect! (79.000000 != 158.000000)
81th item is incorrect! (80.000000 != 160.000000)
82th item is incorrect! (81.000000 != 162.000000)
83th item is incorrect! (82.000000 != 164.000000)
84th item is incorrect! (83.000000 != 166.000000)
85th item is incorrect! (84.000000 != 168.000000)
86th item is incorrect! (85.000000 != 170.000000)
87th item is incorrect! (86.000000 != 172.000000)
88th item is incorrect! (87.000000 != 174.000000)
89th item is incorrect! (88.000000 != 176.000000)
90th item is incorrect! (89.000000 != 178.000000)
91th item is incorrect! (90.000000 != 180.000000)
92th item is incorrect! (91.000000 != 182.000000)
93th item is incorrect! (92.000000 != 184.000000)
94th item is incorrect! (93.000000 != 186.000000)
95th item is incorrect! (94.000000 != 188.000000)
96th item is incorrect! (95.000000 != 190.000000)
97th item is incorrect! (96.000000 != 192.000000)
98th item is incorrect! (97.000000 != 194.000000)
99th item is incorrect! (98.000000 != 196.000000)
100th item is incorrect! (99.000000 != 198.000000)
101th item is incorrect! (100.000000 != 200.000000)
102th item is incorrect! (101.000000 != 202.000000)
103th item is incorrect! (102.000000 != 204.000000)
104th item is incorrect! (103.000000 != 206.000000)
105th item is incorrect! (104.000000 != 208.000000)
106th item is incorrect! (105.000000 != 210.000000)
107th item is incorrect! (106.000000 != 212.000000)
108th item is incorrect! (107.000000 != 214.000000)
109th item is incorrect! (108.000000 != 216.000000)
110th item is incorrect! (109.000000 != 218.000000)
111th item is incorrect! (110.000000 != 220.000000)
112th item is incorrect! (111.000000 != 222.000000)
113th item is incorrect! (112.000000 != 224.000000)
114th item is incorrect! (113.000000 != 226.000000)
115th item is incorrect! (114.000000 != 228.000000)
116th item is incorrect! (115.000000 != 230.000000)
117th item is incorrect! (116.000000 != 232.000000)
118th item is incorrect! (117.000000 != 234.000000)
119th item is incorrect! (118.000000 != 236.000000)
120th item is incorrect! (119.000000 != 238.000000)
121th item is incorrect! (120.000000 != 240.000000)
122th item is incorrect! (121.000000 != 242.000000)
123th item is incorrect! (122.000000 != 244.000000)
124th item is incorrect! (123.000000 != 246.000000)
125th item is incorrect! (124.000000 != 248.000000)
126th item is incorrect! (125.000000 != 250.000000)
127th item is incorrect! (126.000000 != 252.000000)
128th item is incorrect! (127.000000 != 254.000000)
129th item is incorrect! (128.000000 != 256.000000)
130th item is incorrect! (129.000000 != 258.000000)
131th item is incorrect! (130.000000 != 260.000000)
132th item is incorrect! (131.000000 != 262.000000)
133th item is incorrect! (132.000000 != 264.000000)
134th item is incorrect! (133.000000 != 266.000000)
135th item is incorrect! (134.000000 != 268.000000)
136th item is incorrect! (135.000000 != 270.000000)
137th item is incorrect! (136.000000 != 272.000000)
138th item is incorrect! (137.000000 != 274.000000)
139th item is incorrect! (138.000000 != 276.000000)
140th item is incorrect! (139.000000 != 278.000000)
141th item is incorrect! (140.000000 != 280.000000)
142th item is incorrect! (141.000000 != 282.000000)
143th item is incorrect! (142.000000 != 284.000000)
144th item is incorrect! (143.000000 != 286.000000)
145th item is incorrect! (144.000000 != 288.000000)
146th item is incorrect! (145.000000 != 290.000000)
147th item is incorrect! (146.000000 != 292.000000)
148th item is incorrect! (147.000000 != 294.000000)
149th item is incorrect! (148.000000 != 296.000000)
150th item is incorrect! (149.000000 != 298.000000)
151th item is incorrect! (150.000000 != 300.000000)
152th item is incorrect! (151.000000 != 302.000000)
153th item is incorrect! (152.000000 != 304.000000)
154th item is incorrect! (153.000000 != 306.000000)
155th item is incorrect! (154.000000 != 308.000000)
156th item is incorrect! (155.000000 != 310.000000)
157th item is incorrect! (156.000000 != 312.000000)
158th item is incorrect! (157.000000 != 314.000000)
159th item is incorrect! (158.000000 != 316.000000)
160th item is incorrect! (159.000000 != 318.000000)
161th item is incorrect! (160.000000 != 320.000000)
162th item is incorrect! (161.000000 != 322.000000)
163th item is incorrect! (162.000000 != 324.000000)
164th item is incorrect! (163.000000 != 326.000000)
165th item is incorrect! (164.000000 != 328.000000)
166th item is incorrect! (165.000000 != 330.000000)
167th item is incorrect! (166.000000 != 332.000000)
168th item is incorrect! (167.000000 != 334.000000)
169th item is incorrect! (168.000000 != 336.000000)
170th item is incorrect! (169.000000 != 338.000000)
171th item is incorrect! (170.000000 != 340.000000)
172th item is incorrect! (171.000000 != 342.000000)
173th item is incorrect! (172.000000 != 344.000000)
174th item is incorrect! (173.000000 != 346.000000)
175th item is incorrect! (174.000000 != 348.000000)
176th item is incorrect! (175.000000 != 350.000000)
177th item is incorrect! (176.000000 != 352.000000)
178th item is incorrect! (177.000000 != 354.000000)
179th item is incorrect! (178.000000 != 356.000000)
180th item is incorrect! (179.000000 != 358.000000)
181th item is incorrect! (180.000000 != 360.000000)
182th item is incorrect! (181.000000 != 362.000000)
183th item is incorrect! (182.000000 != 364.000000)
184th item is incorrect! (183.000000 != 366.000000)
185th item is incorrect! (184.000000 != 368.000000)
186th item is incorrect! (185.000000 != 370.000000)
187th item is incorrect! (186.000000 != 372.000000)
188th item is incorrect! (187.000000 != 374.000000)
189th item is incorrect! (188.000000 != 376.000000)
190th item is incorrect! (189.000000 != 378.000000)
191th item is incorrect! (190.000000 != 380.000000)
192th item is incorrect! (191.000000 != 382.000000)
193th item is incorrect! (192.000000 != 384.000000)
194th item is incorrect! (193.000000 != 386.000000)
195th item is incorrect! (194.000000 != 388.000000)
196th item is incorrect! (195.000000 != 390.000000)
197th item is incorrect! (196.000000 != 392.000000)
198th item is incorrect! (197.000000 != 394.000000)
199th item is incorrect! (198.000000 != 396.000000)
200th item is incorrect! (199.000000 != 398.000000)
201th item is incorrect! (200.000000 != 400.000000)
202th item is incorrect! (201.000000 != 402.000000)
203th item is incorrect! (202.000000 != 404.000000)
204th item is incorrect! (203.000000 != 406.000000)
205th item is incorrect! (204.000000 != 408.000000)
206th item is incorrect! (205.000000 != 410.000000)
207th item is incorrect! (206.000000 != 412.000000)
208th item is incorrect! (207.000000 != 414.000000)
209th item is incorrect! (208.000000 != 416.000000)
210th item is incorrect! (209.000000 != 418.000000)
211th item is incorrect! (210.000000 != 420.000000)
212th item is incorrect! (211.000000 != 422.000000)
213th item is incorrect! (212.000000 != 424.000000)
214th item is incorrect! (213.000000 != 426.000000)
215th item is incorrect! (214.000000 != 428.000000)
216th item is incorrect! (215.000000 != 430.000000)
217th item is incorrect! (216.000000 != 432.000000)
218th item is incorrect! (217.000000 != 434.000000)
219th item is incorrect! (218.000000 != 436.000000)
220th item is incorrect! (219.000000 != 438.000000)
221th item is incorrect! (220.000000 != 440.000000)
222th item is incorrect! (221.000000 != 442.000000)
223th item is incorrect! (222.000000 != 444.000000)
224th item is incorrect! (223.000000 != 446.000000)
225th item is incorrect! (224.000000 != 448.000000)
226th item is incorrect! (225.000000 != 450.000000)
227th item is incorrect! (226.000000 != 452.000000)
228th item is incorrect! (227.000000 != 454.000000)
229th item is incorrect! (228.000000 != 456.000000)
230th item is incorrect! (229.000000 != 458.000000)
231th item is incorrect! (230.000000 != 460.000000)
232th item is incorrect! (231.000000 != 462.000000)
233th item is incorrect! (232.000000 != 464.000000)
234th item is incorrect! (233.000000 != 466.000000)
235th item is incorrect! (234.000000 != 468.000000)
236th item is incorrect! (235.000000 != 470.000000)
237th item is incorrect! (236.000000 != 472.000000)
238th item is incorrect! (237.000000 != 474.000000)
239th item is incorrect! (238.000000 != 476.000000)
240th item is incorrect! (239.000000 != 478.000000)
241th item is incorrect! (240.000000 != 480.000000)
242th item is incorrect! (241.000000 != 482.000000)
243th item is incorrect! (242.000000 != 484.000000)
244th item is incorrect! (243.000000 != 486.000000)
245th item is incorrect! (244.000000 != 488.000000)
246th item is incorrect! (245.000000 != 490.000000)
247th item is incorrect! (246.000000 != 492.000000)
248th item is incorrect! (247.000000 != 494.000000)
249th item is incorrect! (248.000000 != 496.000000)
250th item is incorrect! (249.000000 != 498.000000)
251th item is incorrect! (250.000000 != 500.000000)
252th item is incorrect! (251.000000 != 502.000000)
253th item is incorrect! (252.000000 != 504.000000)
254th item is incorrect! (253.000000 != 506.000000)
255th item is incorrect! (254.000000 != 508.000000)
256th item is incorrect! (255.000000 != 510.000000)
257th item is incorrect! (256.000000 != 512.000000)
258th item is incorrect! (257.000000 != 514.000000)
259th item is incorrect! (258.000000 != 516.000000)
260th item is incorrect! (259.000000 != 518.000000)
261th item is incorrect! (260.000000 != 520.000000)
262th item is incorrect! (261.000000 != 522.000000)
263th item is incorrect! (262.000000 != 524.000000)
264th item is incorrect! (263.000000 != 526.000000)
265th item is incorrect! (264.000000 != 528.000000)
266th item is incorrect! (265.000000 != 530.000000)
267th item is incorrect! (266.000000 != 532.000000)
268th item is incorrect! (267.000000 != 534.000000)
269th item is incorrect! (268.000000 != 536.000000)
270th item is incorrect! (269.000000 != 538.000000)
271th item is incorrect! (270.000000 != 540.000000)
272th item is incorrect! (271.000000 != 542.000000)
273th item is incorrect! (272.000000 != 544.000000)
274th item is incorrect! (273.000000 != 546.000000)
275th item is incorrect! (274.000000 != 548.000000)
276th item is incorrect! (275.000000 != 550.000000)
277th item is incorrect! (276.000000 != 552.000000)
278th item is incorrect! (277.000000 != 554.000000)
279th item is incorrect! (278.000000 != 556.000000)
280th item is incorrect! (279.000000 != 558.000000)
281th item is incorrect! (280.000000 != 560.000000)
282th item is incorrect! (281.000000 != 562.000000)
283th item is incorrect! (282.000000 != 564.000000)
284th item is incorrect! (283.000000 != 566.000000)
285th item is incorrect! (284.000000 != 568.000000)
286th item is incorrect! (285.000000 != 570.000000)
287th item is incorrect! (286.000000 != 572.000000)
288th item is incorrect! (287.000000 != 574.000000)
289th item is incorrect! (288.000000 != 576.000000)
290th item is incorrect! (289.000000 != 578.000000)
291th item is incorrect! (290.000000 != 580.000000)
292th item is incorrect! (291.000000 != 582.000000)
293th item is incorrect! (292.000000 != 584.000000)
294th item is incorrect! (293.000000 != 586.000000)
295th item is incorrect! (294.000000 != 588.000000)
296th item is incorrect! (295.000000 != 590.000000)
297th item is incorrect! (296.000000 != 592.000000)
298th item is incorrect! (297.000000 != 594.000000)
299th item is incorrect! (298.000000 != 596.000000)
300th item is incorrect! (299.000000 != 598.000000)
301th item is incorrect! (300.000000 != 600.000000)
302th item is incorrect! (301.000000 != 602.000000)
303th item is incorrect! (302.000000 != 604.000000)
304th item is incorrect! (303.000000 != 606.000000)
305th item is incorrect! (304.000000 != 608.000000)
306th item is incorrect! (305.000000 != 610.000000)
307th item is incorrect! (306.000000 != 612.000000)
308th item is incorrect! (307.000000 != 614.000000)
309th item is incorrect! (308.000000 != 616.000000)
310th item is incorrect! (309.000000 != 618.000000)
311th item is incorrect! (310.000000 != 620.000000)
312th item is incorrect! (311.000000 != 622.000000)
313th item is incorrect! (312.000000 != 624.000000)
314th item is incorrect! (313.000000 != 626.000000)
315th item is incorrect! (314.000000 != 628.000000)
316th item is incorrect! (315.000000 != 630.000000)
317th item is incorrect! (316.000000 != 632.000000)
318th item is incorrect! (317.000000 != 634.000000)
319th item is incorrect! (318.000000 != 636.000000)
320th item is incorrect! (319.000000 != 638.000000)
321th item is incorrect! (320.000000 != 640.000000)
322th item is incorrect! (321.000000 != 642.000000)
323th item is incorrect! (322.000000 != 644.000000)
324th item is incorrect! (323.000000 != 646.000000)
325th item is incorrect! (324.000000 != 648.000000)
326th item is incorrect! (325.000000 != 650.000000)
327th item is incorrect! (326.000000 != 652.000000)
328th item is incorrect! (327.000000 != 654.000000)
329th item is incorrect! (328.000000 != 656.000000)
330th item is incorrect! (329.000000 != 658.000000)
331th item is incorrect! (330.000000 != 660.000000)
332th item is incorrect! (331.000000 != 662.000000)
333th item is incorrect! (332.000000 != 664.000000)
334th item is incorrect! (333.000000 != 666.000000)
335th item is incorrect! (334.000000 != 668.000000)
336th item is incorrect! (335.000000 != 670.000000)
337th item is incorrect! (336.000000 != 672.000000)
338th item is incorrect! (337.000000 != 674.000000)
339th item is incorrect! (338.000000 != 676.000000)
340th item is incorrect! (339.000000 != 678.000000)
341th item is incorrect! (340.000000 != 680.000000)
342th item is incorrect! (341.000000 != 682.000000)
343th item is incorrect! (342.000000 != 684.000000)
344th item is incorrect! (343.000000 != 686.000000)
345th item is incorrect! (344.000000 != 688.000000)
346th item is incorrect! (345.000000 != 690.000000)
347th item is incorrect! (346.000000 != 692.000000)
348th item is incorrect! (347.000000 != 694.000000)
349th item is incorrect! (348.000000 != 696.000000)
350th item is incorrect! (349.000000 != 698.000000)
351th item is incorrect! (350.000000 != 700.000000)
352th item is incorrect! (351.000000 != 702.000000)
353th item is incorrect! (352.000000 != 704.000000)
354th item is incorrect! (353.000000 != 706.000000)
355th item is incorrect! (354.000000 != 708.000000)
356th item is incorrect! (355.000000 != 710.000000)
357th item is incorrect! (356.000000 != 712.000000)
358th item is incorrect! (357.000000 != 714.000000)
359th item is incorrect! (358.000000 != 716.000000)
360th item is incorrect! (359.000000 != 718.000000)
361th item is incorrect! (360.000000 != 720.000000)
362th item is incorrect! (361.000000 != 722.000000)
363th item is incorrect! (362.000000 != 724.000000)
364th item is incorrect! (363.000000 != 726.000000)
365th item is incorrect! (364.000000 != 728.000000)
366th item is incorrect! (365.000000 != 730.000000)
367th item is incorrect! (366.000000 != 732.000000)
368th item is incorrect! (367.000000 != 734.000000)
369th item is incorrect! (368.000000 != 736.000000)
370th item is incorrect! (369.000000 != 738.000000)
371th item is incorrect! (370.000000 != 740.000000)
372th item is incorrect! (371.000000 != 742.000000)
373th item is incorrect! (372.000000 != 744.000000)
374th item is incorrect! (373.000000 != 746.000000)
375th item is incorrect! (374.000000 != 748.000000)
376th item is incorrect! (375.000000 != 750.000000)
377th item is incorrect! (376.000000 != 752.000000)
378th item is incorrect! (377.000000 != 754.000000)
379th item is incorrect! (378.000000 != 756.000000)
380th item is incorrect! (379.000000 != 758.000000)
381th item is incorrect! (380.000000 != 760.000000)
382th item is incorrect! (381.000000 != 762.000000)
383th item is incorrect! (382.000000 != 764.000000)
384th item is incorrect! (383.000000 != 766.000000)
385th item is incorrect! (384.000000 != 768.000000)
386th item is incorrect! (385.000000 != 770.000000)
387th item is incorrect! (386.000000 != 772.000000)
388th item is incorrect! (387.000000 != 774.000000)
389th item is incorrect! (388.000000 != 776.000000)
390th item is incorrect! (389.000000 != 778.000000)
391th item is incorrect! (390.000000 != 780.000000)
392th item is incorrect! (391.000000 != 782.000000)
393th item is incorrect! (392.000000 != 784.000000)
394th item is incorrect! (393.000000 != 786.000000)
395th item is incorrect! (394.000000 != 788.000000)
396th item is incorrect! (395.000000 != 790.000000)
397th item is incorrect! (396.000000 != 792.000000)
398th item is incorrect! (397.000000 != 794.000000)
399th item is incorrect! (398.000000 != 796.000000)
400th item is incorrect! (399.000000 != 798.000000)
401th item is incorrect! (400.000000 != 800.000000)
402th item is incorrect! (401.000000 != 802.000000)
403th item is incorrect! (402.000000 != 804.000000)
404th item is incorrect! (403.000000 != 806.000000)
405th item is incorrect! (404.000000 != 808.000000)
406th item is incorrect! (405.000000 != 810.000000)
407th item is incorrect! (406.000000 != 812.000000)
408th item is incorrect! (407.000000 != 814.000000)
409th item is incorrect! (408.000000 != 816.000000)
410th item is incorrect! (409.000000 != 818.000000)
411th item is incorrect! (410.000000 != 820.000000)
412th item is incorrect! (411.000000 != 822.000000)
413th item is incorrect! (412.000000 != 824.000000)
414th item is incorrect! (413.000000 != 826.000000)
415th item is incorrect! (414.000000 != 828.000000)
416th item is incorrect! (415.000000 != 830.000000)
417th item is incorrect! (416.000000 != 832.000000)
418th item is incorrect! (417.000000 != 834.000000)
419th item is incorrect! (418.000000 != 836.000000)
420th item is incorrect! (419.000000 != 838.000000)
421th item is incorrect! (420.000000 != 840.000000)
422th item is incorrect! (421.000000 != 842.000000)
423th item is incorrect! (422.000000 != 844.000000)
424th item is incorrect! (423.000000 != 846.000000)
425th item is incorrect! (424.000000 != 848.000000)
426th item is incorrect! (425.000000 != 850.000000)
427th item is incorrect! (426.000000 != 852.000000)
428th item is incorrect! (427.000000 != 854.000000)
429th item is incorrect! (428.000000 != 856.000000)
430th item is incorrect! (429.000000 != 858.000000)
431th item is incorrect! (430.000000 != 860.000000)
432th item is incorrect! (431.000000 != 862.000000)
433th item is incorrect! (432.000000 != 864.000000)
434th item is incorrect! (433.000000 != 866.000000)
435th item is incorrect! (434.000000 != 868.000000)
436th item is incorrect! (435.000000 != 870.000000)
437th item is incorrect! (436.000000 != 872.000000)
438th item is incorrect! (437.000000 != 874.000000)
439th item is incorrect! (438.000000 != 876.000000)
440th item is incorrect! (439.000000 != 878.000000)
441th item is incorrect! (440.000000 != 880.000000)
442th item is incorrect! (441.000000 != 882.000000)
443th item is incorrect! (442.000000 != 884.000000)
444th item is incorrect! (443.000000 != 886.000000)
445th item is incorrect! (444.000000 != 888.000000)
446th item is incorrect! (445.000000 != 890.000000)
447th item is incorrect! (446.000000 != 892.000000)
448th item is incorrect! (447.000000 != 894.000000)
449th item is incorrect! (448.000000 != 896.000000)
450th item is incorrect! (449.000000 != 898.000000)
451th item is incorrect! (450.000000 != 900.000000)
452th item is incorrect! (451.000000 != 902.000000)
453th item is incorrect! (452.000000 != 904.000000)
454th item is incorrect! (453.000000 != 906.000000)
455th item is incorrect! (454.000000 != 908.000000)
456th item is incorrect! (455.000000 != 910.000000)
457th item is incorrect! (456.000000 != 912.000000)
458th item is incorrect! (457.000000 != 914.000000)
459th item is incorrect! (458.000000 != 916.000000)
460th item is incorrect! (459.000000 != 918.000000)
461th item is incorrect! (460.000000 != 920.000000)
462th item is incorrect! (461.000000 != 922.000000)
463th item is incorrect! (462.000000 != 924.000000)
464th item is incorrect! (463.000000 != 926.000000)
465th item is incorrect! (464.000000 != 928.000000)
466th item is incorrect! (465.000000 != 930.000000)
467th item is incorrect! (466.000000 != 932.000000)
468th item is incorrect! (467.000000 != 934.000000)
469th item is incorrect! (468.000000 != 936.000000)
470th item is incorrect! (469.000000 != 938.000000)
471th item is incorrect! (470.000000 != 940.000000)
472th item is incorrect! (471.000000 != 942.000000)
473th item is incorrect! (472.000000 != 944.000000)
474th item is incorrect! (473.000000 != 946.000000)
475th item is incorrect! (474.000000 != 948.000000)
476th item is incorrect! (475.000000 != 950.000000)
477th item is incorrect! (476.000000 != 952.000000)
478th item is incorrect! (477.000000 != 954.000000)
479th item is incorrect! (478.000000 != 956.000000)
480th item is incorrect! (479.000000 != 958.000000)
481th item is incorrect! (480.000000 != 960.000000)
482th item is incorrect! (481.000000 != 962.000000)
483th item is incorrect! (482.000000 != 964.000000)
484th item is incorrect! (483.000000 != 966.000000)
485th item is incorrect! (484.000000 != 968.000000)
486th item is incorrect! (485.000000 != 970.000000)
487th item is incorrect! (486.000000 != 972.000000)
488th item is incorrect! (487.000000 != 974.000000)
489th item is incorrect! (488.000000 != 976.000000)
490th item is incorrect! (489.000000 != 978.000000)
491th item is incorrect! (490.000000 != 980.000000)
492th item is incorrect! (491.000000 != 982.000000)
493th item is incorrect! (492.000000 != 984.000000)
494th item is incorrect! (493.000000 != 986.000000)
495th item is incorrect! (494.000000 != 988.000000)
496th item is incorrect! (495.000000 != 990.000000)
497th item is incorrect! (496.000000 != 992.000000)
498th item is incorrect! (497.000000 != 994.000000)
499th item is incorrect! (498.000000 != 996.000000)
500th item is incorrect! (499.000000 != 998.000000)
501th item is incorrect! (500.000000 != 1000.000000)
502th item is incorrect! (501.000000 != 1002.000000)
503th item is incorrect! (502.000000 != 1004.000000)
504th item is incorrect! (503.000000 != 1006.000000)
505th item is incorrect! (504.000000 != 1008.000000)
506th item is incorrect! (505.000000 != 1010.000000)
507th item is incorrect! (506.000000 != 1012.000000)
508th item is incorrect! (507.000000 != 1014.000000)
509th item is incorrect! (508.000000 != 1016.000000)
510th item is incorrect! (509.000000 != 1018.000000)
511th item is incorrect! (510.000000 != 1020.000000)
512th item is incorrect! (511.000000 != 1022.000000)
511 errors!

ERROR: ACCL base functionality test failed!

-- STATISTICS - ID: 0
-----------------------------------------------
          Read command FIFO used: 	0
         Write command FIFO used: 	0
                 Host reads sent: 	98
                Host writes sent: 	66
                 Card reads sent: 	65
                Card writes sent: 	64
                 Sync reads sent: 	10
                Sync writes sent: 	0
                     Page faults: 	0

 -- NET STATS QSFP0

RX pkgs: 510
TX pkgs: 138
ARP RX pkgs: 4
ARP TX pkgs: 2
ICMP RX pkgs: 0
ICMP TX pkgs: 0
TCP RX pkgs: 0
TCP TX pkgs: 0
ROCE RX pkgs: 180
ROCE TX pkgs: 136
IBV RX pkgs: 235
IBV TX pkgs: 236
PSN drop cnt: 0
Retrans cnt: 0
TCP session cnt: 0
STRM down: 0

Finalizing MPI...
Done. Terminating...

stderr
XRT build version: 2.13.466
Build hash: f5505e402c2ca1ffe45eb6d3a9399b23a0dc8776
Build date: 2022-04-14 17:43:11
Git branch: 2022.1
PID: 21422
UID: 500207
[Tue May 14 12:11:34 2024 GMT]
HOST: alveo-u55c-07.inf.ethz.ch
EXE: /pub/scratch/lawirz/XACCL/integrations/pytorch_ddp/accl/test/host/Coyote/accl_on_coyote
[XRT] ERROR: No devices found
[XRT] ERROR: No devices found
[XRT] ERROR: No devices found
ACLL DEBUG: aquiring cProc: targetRegion: 0, cPid: 0
ACLL DEBUG: aquiring qProc: targetRegion: 0, cPid: 2
ACLL DEBUG: aquiring qProc: targetRegion: 0, cPid: 1
CCLO HWID: 2696576574 at 0x0
CCLO source commit (first 24b): a0ba7e
CCLO Capabilities:
Stack type: RDMA
Internal DMA:True
External DMA:False
Reduction:True
Compression:True
Kernel Streams:True
Debug:False
Doing a soft reset
Configuring Eager RX Buffers
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:64,n_pages:1
Allocation successful! Allocated buffer: 7fe2c6000000, Size: 64
calling offload: 7fe2c6000000, size: 64
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:64,n_pages:1
Allocation successful! Allocated buffer: 7fe2c5e00000, Size: 64
calling offload: 7fe2c5e00000, size: 64
Configuring Rendezvous Spare Buffers
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:4194304,n_pages:2
Allocation successful! Allocated buffer: 7fe2c5a00000, Size: 4194304
calling offload: 7fe2c5a00000, size: 4194304
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:4194304,n_pages:2
Allocation successful! Allocated buffer: 7fe2c5600000, Size: 4194304
calling offload: 7fe2c5600000, size: 4194304
get_device_type: coyote_device
get_device_type: coyote_device
CoyoteBuffer contructor called! page_size:2097152, buffer_size:4194304,n_pages:2
Allocation successful! Allocated buffer: 7fe2c5200000, Size: 4194304
calling offload: 7fe2c5200000, size: 4194304
Configuring a communicator
Configuring arithmetic
Configuring collective tuning parameters
CCLO configured
Set timeout
Set max eager size: 64
Set max rendezvous reduce size: 4194304
Accelerator ready!
Communicator 0 (0x40):
local rank: 0 	 number of ranks: 2
> rank 0 (ip 10.253.74.92:5005 ; session 0 ; max segment size 4194304) : <- inbound seq number 0, -> outbound seq number 0
> rank 1 (ip 10.253.74.96:5005 ; session 1 ; max segment size 4194304) : <- inbound seq number 0, -> outbound seq number 0

Rank 0 passed last barrier before test!
CCLO address: 0
rx address: 4
Spare RX Buffer 0:	 address: 0x7fe2c6000000 	 status: ENQUEUED 	 occupancy: 0/64 	 MPI tag: 0 	 seq: 0 	 src: 0
Spare RX Buffer 1:	 address: 0x7fe2c5e00000 	 status: ENQUEUED 	 occupancy: 0/64 	 MPI tag: 0 	 seq: 0 	 src: 0

CoyoteBuffer contructor called! page_size:2097152, buffer_size:2048,n_pages:1
Allocation successful! Allocated buffer: 7fe2c5000000, Size: 2048
CoyoteBuffer contructor called! page_size:2097152, buffer_size:2048,n_pages:1
Allocation successful! Allocated buffer: 7fe2c4e00000, Size: 2048
Reducing data...
Free user buffer from cProc cPid:0, buffer_size:2048,7fe2c5000000
Free user buffer from cProc cPid:0, buffer_size:2048,7fe2c4e00000
Communicator 0 (0x40):
local rank: 0 	 number of ranks: 2
> rank 0 (ip 10.253.74.92:5005 ; session 0 ; max segment size 4194304) : <- inbound seq number 0, -> outbound seq number 0
> rank 1 (ip 10.253.74.96:5005 ; session 1 ; max segment size 4194304) : <- inbound seq number 0, -> outbound seq number 1

CCLO address: 0
rx address: 4
Spare RX Buffer 0:	 address: 0x7fe2c6000000 	 status: ENQUEUED 	 occupancy: 0/64 	 MPI tag: 0 	 seq: 0 	 src: 0
Spare RX Buffer 1:	 address: 0x7fe2c5e00000 	 status: ENQUEUED 	 occupancy: 0/64 	 MPI tag: 0 	 seq: 0 	 src: 0

Removing CCLO object at 0
Doing a soft reset
Free user buffer from cProc cPid:0, buffer_size:64,7fe2c6000000
Free user buffer from cProc cPid:0, buffer_size:64,7fe2c5e00000
Free user buffer from cProc cPid:0, buffer_size:4194304,7fe2c5a00000
Free user buffer from cProc cPid:0, buffer_size:4194304,7fe2c5600000
Free user buffer from cProc cPid:0, buffer_size:4194304,7fe2c5200000

@lawirz can you specify what is the threshold for Eager transfers in your ACCL initialization?

The errors are fixed on the issue branch

authors: lawirz quetric

repo: Xilinx/ACCL


text:
Query on hardware emulation profiling with PYNQ

I am trying to analyze the waveform generated from the PYNQ-ALVEO example notebook "2_hardware-emulation.ipynb". In waveform I observed that there is no section of host interacting with global memory. Is it that python host profiling is not yet supported & profiler expects host program to be coded in C++?

Correct me if I am wrong, but I think the host<->mem part is a bit out of scope with what is provided in that notebook. You are emulating the kernel execution in Vivado, so anything that happens outside of the kernel execution scope is not included in the waveform.

I am actually new to the PYNQ flow. I was going through the tutorials & material available for Vitis. In one of the documents
on page-208 , I found that while doing hardware emulation with profiling on (using conventional host.cpp) there is a section in waveform window which captures data flow from host to global memory. Just wanted to confirm that is it intrinsically not supported using PYNQ flow or I have missed some setting switch.

There is one example notebook "1-efficient-accelerator-scheduling" where concept of compute & data transfer overlapping (pipelining) is explained. If we can baseline host call timings with respect to kernel execution time (as with conventional host.cpp) , we can do this overlapping more efficiently. Let me know if I am mistaken here.

I am actually new to the PYNQ & Vitis flow. I want to baseline host API (wrapped over openCL APIs) call timings with respect to the kernel execution time using PYNQ flow.
I was going through the tutorials & material available for Vitis. In one of the Xilinx documents https://www.xilinx.com/support/documentation/sw_manuals/xilinx2019_2/ug1393-vitis-application-acceleration.pdf
on page-210 , I found that while doing hardware emulation with profiling on (using conventional host.cpp) there is a section in waveform window which captures data flow from host to global memory. Just wanted to confirm if it is intrinsically supported using PYNQ flow and if that is the case I might have missed some config setting.

That should be kernel to global memory, not host.
As the first paragraph on the previous page states:
<<The Vitis core development kit can generate a Waveform view when running hardware
emulation. It displays in-depth details at the system-level, CU level, and at the function level. The
details include data transfers between the kernel and global memory and data flow through interkernel pipes. These details provide many insights into performance bottlenecks from the systemlevel down to individual function calls to help optimize your application.>>

There is a description which follows this image on page 211. It reads
The hierarchy of the Waveform and Live Waveform views include the following:
• Device "name": Target device name.
• Binary Container "name": Binary container name.
• Memory Data Transfers: For each DDR Bank, this shows the trace of all the read and
write request transactions arriving at the bank from the host.
• Kernel "name" 1:1:1: For each kernel and for each compute unit of that kernel, this
section breaks down the activities originating from the compute unit.

Unfortunately the way memory profiling is done in Vitis is OpenCL specific. It's something we're looking into but I can't give a time on when it might be supported. We're somewhat at the mercy of the lower-level libraries we build on for this type of functionality.

Thanks Peter for the clarification.

authors: PeterOgden giunatale rahulj175

repo: Xilinx/Alveo-PYNQ


text:
Update readme.md

Organization


text:
🛑 MOMO is down

In c6953b8, MOMO (https://www.momoshop.com.tw/main/Main.jsp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MOMO is back up in 62c3f6c.


text:
Composer Fails on graham-campbell/markdown Dependency

I tried to do a fresh install of Quarx and hit a composer conflict:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- yab/quarx v2.2.0 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.1 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.10 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.11 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.12 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.2 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.3 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.4 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.5 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.6 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.7 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.8 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- yab/quarx v2.2.9 requires graham-campbell/markdown ^6.1 -> satisfiable by graham-campbell/markdown[v6.1.0].
- Conclusion: don't install graham-campbell/markdown v6.1.0
- Installation request for yab/quarx ^2.2 -> satisfiable by yab/quarx[v2.2.0, v2.2.1, v2.2.10, v2.2.11, v2.2.12, v2.2.2, v2.2.3, v2.2.4, v2.2.5, v2.2.6, v2.2.7, v2.2.8, v2.2.9].

... aaaaand it's because I was installing against Laravel 5.4 instead of 5.3. Sorry about that.
Any thoughts on when Quarx will officially support 5.4? Thanks!

End of the week is the goal

Awesome, thank you @mlantz!

authors: humbugz mlantz

repo: YABhq/Quarx


text:
Make it better

Purpose

Make Future/Task now can works with const or lvalue
WhenAll now support WhenPolicy::None
Fix missing pragma once in yaclib/async/contract.hpp

Related Information

[ ] Design document: ...
[ ] Bench PR: ...

Testing

[ ] This change is a trivial rework or code cleanup without any test coverage.
[ ] This change is already covered by existing tests.
[ ] This PR adds tests that were used to verify all changes.
[ ] There are tests in an external testing repository: ...

Pull Request Test Coverage Report for Build 3257400600

25 of 25 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 3211091320:
0.0%

Covered Lines:
1358

Relevant Lines:
1358

💛  - Coveralls

authors: MBkkt coveralls

repo: YACLib/YACLib


text:
#8 절약 엔티티 리팩토링

사용자별 절약 데이터는 자주 수정이 되지 않는 마스터성 데이터이므로 그 날 수행한 절약을 기록하는 절약 기록 테이블과 분리한다.
=> Saving 엔티티를 Product 엔티티와 Saving 엔티티로 분리

Product Repository, SavingRecordRepository 테스트 코드 작성

확인했습니다 👏👏

authors: IceChoco kimyubi


text:
🛑 Haty is down

In 9c48e56, Haty (https://chat.hashi.sbs) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Haty is back up in 95243c2 after 6 hours, 30 minutes.

repo: YAT-Publish/status


text:
安装过程死循环了

版本号
~ master
什么问题
~ npm install 死循环刷屏
gyp verb command install [ '12.13.1' ]
gyp verb install input version string "12.13.1"
gyp verb install installing version: 12.13.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 12.13.1
gyp verb ensuring nodedir is created /data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1
gyp WARN EACCES user "root" does not have permission to access the dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '12.13.1' ]
gyp verb install input version string "12.13.1"
gyp verb install installing version: 12.13.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 12.13.1
gyp verb ensuring nodedir is created /data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1
gyp WARN EACCES user "root" does not have permission to access the dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '12.13.1' ]
gyp verb install input version string "12.13.1"
gyp verb install installing version: 12.13.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 12.13.1
gyp verb ensuring nodedir is created /data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1
gyp WARN EACCES user "root" does not have permission to access the dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '12.13.1' ]
gyp verb install input version string "12.13.1"
gyp verb install installing version: 12.13.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 12.13.1
gyp verb ensuring nodedir is created /data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1
gyp WARN EACCES user "root" does not have permission to access the dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '12.13.1' ]
gyp verb install input version string "12.13.1"
gyp verb install installing version: 12.13.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 12.13.1
gyp verb ensuring nodedir is created /data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1
gyp WARN EACCES user "root" does not have permission to access the dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '12.13.1' ]
gyp verb install input version string "12.13.1"
gyp verb install installing version: 12.13.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 12.13.1
gyp verb ensuring nodedir is created /data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1
gyp WARN EACCES user "root" does not have permission to access the dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp/12.13.1"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/data/qsapi/vendors/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '12.13.1' ]
gyp verb install input version string "12.13.1"
gyp verb install installing version: 12.13.1
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 12.13.1

如何复现此问题
mkdir yapi && cd yapi
git clone https://github.com/YMFE/yapi.git vendors --depth=1
cp vendors/config_example.json ./config.json
# edit
cd vendors
npm install  --registry https://registry.npm.taobao.org # 安装依赖

什么系统（Linux, Windows, macOS）
centos 7.7

nodejs建议8.x，换成8.16.2验证ok了。

repo: YMFE/yapi


text:
How can I import Side-Menu.Android to existed project

I add lines to build.gradel(Module:app) like this.
And building gradle is completed.
But I cannot use the library, because there aren't generated any library directory.
How can I use this library???

Hi, @suspectuser! After adding the above lines, just refer to classes from the library in your project. Please, checkout the main page of repository to look how to use it in your project. Also, sample app can help you.

authors: suspectuser warko-san


text:
about train dataset

hello. you paper is very good .but your train dataset is the ssid only?

I found another dataset DND, but I didn't find RID. To obtain the DND dataset, you need to register an account at:  https://noise.visinf.tu-darmstadt.de/login/?redirect=https%3A%2F%2Fnoise.visinf.tu -darmstadt.de%2Fdownloads

I found another dataset DND, but I didn't find RID. To obtain the DND dataset, you need to register an account at:  https://noise.visinf.tu-darmstadt.de/login/?redirect=https%3A%2F%2Fnoise.visinf.tu -darmstadt.de%2Fdownloads

i found SIDD is dufficult to download，so i  choose to download DND, i will try if it can work welly

do you have dnd datasets  can you show me a link of google drive or another which is not in official website?

thanks

Has anyone successfully downloaded the SIDD dataset?

I found another dataset DND, but I didn't find RID. To obtain the DND dataset, you need to register an account at: https://noise.visinf.tu-darmstadt.de/login/?redirect=https%3A%2F%2Fnoise.visinf.tu -darmstadt.de%2Fdownloads

I am not able to get the DNDdataset at the moment. Can you please share the dnd dataset zip package with me?


text:
Update scala-library to 2.13.7

Updates org.scala-lang:scala-library from 2.13.6 to 2.13.7.
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

labels: library-update, early-semver-patch, semver-spec-patch

Superseded by #54.

repo: YannMoisan/sbopt


text:
u-popup 组件能否增加背景样式自定义，如透明 u-mode-center-box样式

看看popup是否有背景颜色的prop 如果有就直接使用 如果没有 可以单独拉出来组件进行使用

看看popup是否有背景颜色的prop 如果有就直接使用 如果没有 可以单独拉出来组件进行使用

props custom-style 可以自定义样式，不过背景色是mask，如果要去掉白色则要将背景注释，这是需要改源码才能实现
.u-mode-center-box {
min-width: 100rpx;
min-height: 100rpx;
/* #ifndef APP-NVUE /
display: block;
/ #endif */
position: relative;
// background-color: #ffffff;
}

只能改源码吗

/deep/ .u-mode-center-box {
background-color: transparent !important;
}
这样就可以改掉了。

repo: YanxinNet/uView


text:
Feat: Auto-detection for current user locationf, Enhancement: Search dialog auto-close on choosing a location

Description
Currently, the default location is always Oxford, the user experience would be much better if SkyCast detected the user's location automatically rather than them having to search for it.  Implemented this using the geolocation api that works on pretty much all browsers, should not cause any issues and should work perfectly fine with the existing code.
Secondly, the search dialog box does not close once the user has selected a location, added a listener to close it once a new setActiveCityCoords are set.
Type of change

[ ] New feature (non-breaking change which adds functionality)

Checklist:

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

Merge conflicts exist as I did not clone the latest version of the app, as it has a bug which was not present yesterday. Opened an issue for the same.


text:
Remove Update Nag From Video Pages

I think it'd be better to remove the "A new developer build is available etc" banner nag from video pages and instead only show it on the front page. I can't close this banner on video pages because the "hide header while video is playing" feature makes the header pop out whenever I hover my cursor near the close button. The nag is also persistent until I close it. I know I can adjust the popout deadzone for the header for the time being but I like it the way it is.
If you must show this notification on video pages, it should at least be under the video.

If you have no intention of updating, then disable the update check. The entire purpose of the "nag" is to inform users that a new build has been compiled for testing.

The script auto updates. All I'm saying is its placement is awkward, and conflicts with the feature that auto hides the header while playing. I watch videos in fill mode with the header hidden so I can have multiple videos open in tabs as big as possible while not having to use fullscreen mode. It's the main reason I like this script.

The placement is exactly the same as YouTube's own alerts since it uses that as a basis.

authors: ErdeFB Zarggg sanitysama

repo: YePpHa/YouTubeCenter


text:
TOKEN_MISSING

I try to retrieve some information from Yelp API for a UWP app. As they say here, I need to pass some parameter as header for a HTTP request, and then perform a Json request using this link. I know how to parse a Json file once I get it, but I have no idea how to get access to this file.
If for example I put
https://api.yelp.com/v3/businesses/search?term=delis&latitude=37.786882&longitude=-122.399972&access_token=my access_tokenid
this link on my browser
and I am getting error that token_missing.
{"error": {"description": "An access token must be supplied in order to use this endpoint.", "code": "TOKEN_MISSING"}}
How should I enter this TOKEN_MISSING?
Also i got some answer https://github.com/Yelp/yelp-fusion/issues/45#issuecomment-242809007, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AUM4uk52HmESKid6KJJaaEMOqXbgZ23Oks5qjyuogaJpZM4JuN3b.
but not get any help.

@rahuls2704 : Check out https://www.yelp.com/developers/documentation/v3/get_started .
First, follow "Get an access token" to use POST api.yelp.com/oath2/token with your App ID and App Secret to get an access token.
Next, include that access token in the "Authorization" header:

Header Name ("Key" in Postman)
Header Value ("Value" in Postman)

Authorization
Bearer MY_TOKEN

How you specify a header depends on what program you're using to make the GET request.
If you're using Postman, use the Headers tab; for curl use -H, etc.
Does that help?  If so, we'll put more of this explanation up on the main docs.

Thanks for your response, but not getting any success.
//**********//
Check out https://www.yelp.com/developers/documentation/v3/get_started .
First, follow "Get an access token" to use POST api.yelp.com/oath2/token with your App ID and App Secret to get an access token.
//**********//
I'm not getting the above point. please explained in detail. Thanks in advance.

@rahuls2704 : Are you using Postman, curl, or something else to make your request?  I can try to use the words your tool uses.
Do you know how to make a POST request?  It's not easy to do manually in a web browser, so most people use either Postman or curl.  If you're just starting out I'd suggest Postman:

https://www.getpostman.com/

We've set up a list of our URLs in Postman's config format, so you don't have to type them in:

https://www.yelp.com/developers/documentation/v3/get_started => "Run in Postman"

Click "Postman for Chrome."
In the left bar, click "Collections".
Click "POST https://api.yelp.com/oauth2/token"
Click "Body".
On the line "client_id", replace "value" with your "App ID" from https://www.yelp.com/developers/v3/manage_app (22 characters long).
On the line "client_secret", replace "value" with your "App Secret" from https://www.yelp.com/developers/v3/manage_app .  (64 characters long, you'll need to click "Show"  to see it behind the "*****").
On the line "grant type", leave "client_credentials" as-is.
Click the big blue "Send" button.
In the "Response" field, you should see something like:
{
  "access_token": "MY_TOKEN",
  "token_type": "bearer",
  "expires_in": 15552000
}

The access token will be 128 characters long.
Let me know when you've gotten that far, and we'll do the next step --- but don't reveal your actual access token on the internet!

Hello sir, Thanks for your positive response. I have follow above all
steps, also i got my access token. please see below code
{
"expires_in": 15551999,
"token_type": "Bearer",
"access_token": "my 128 digit code"
}
When i hit below URL
https://api.yelp.com/v3/businesses/search?term=delis&latitude=37.786882&longitude=-122.399972&access_token=my_access_tokenid
I will  get following respnose
{"error": {"description": "An access token must be supplied in order
to use this endpoint.", "code": "TOKEN_MISSING"}}
How should i resolve these.
Please reply. Thanks in advance.
On Tue, Jan 17, 2017 at 10:52 PM, Ken Mitton notifications@github.com
wrote:

@rahuls2704 https://github.com/rahuls2704 : Are you using Postman,
curl, or something else to make your request? I can try to use the words
your tool uses.
Do you know how to make a POST request? It's not easy to do manually in a
web browser, so most people use either Postman or curl. If you're just
starting out I'd suggest Postman:

https://www.getpostman.com/

We've set up a list of our URLs in Postman's config format, so you don't
have to type them in:

https://www.yelp.com/developers/documentation/v3/get_started => "Run
in Postman"

Click "Postman for Chrome."
In the left bar, click "Collections".
Click "POST https://api.yelp.com/oauth2/token"
Click "Body".
On the line "client_id", replace "value" with your "App ID" from
https://www.yelp.com/developers/v3/manage_app (22 characters long).
On the line "client_secret", replace "value" with your "App Secret" from
https://www.yelp.com/developers/v3/manage_app . (64 characters long,
you'll need to click "Show" to see it behind the "*****").
On the line "grant type", leave "client_credentials" as-is.
Click the big blue "Send" button.
In the "Response" field, you should see something like:
{
"access_token": "MY_TOKEN",
"token_type": "bearer",
"expires_in": 15552000
}
The access token will be 128 characters long.
Let me know when you've gotten that far, and we'll do the next step ---
but don't reveal your actual access token on the internet!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Yelp/yelp-api/issues/184#issuecomment-273236300, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AX62X-GcsF4WTXVZEGMGvEHhy9D3ZB-Lks5rTPjVgaJpZM4Lkpd3
.

@rahuls2704 : Great, that's the first step.
Now, for the /v3/business/search request: Do not put your "access_token" in the URL.  It needs to go in a Header instead.

If you're using Postman, click the "Headers" tab (https://www.getpostman.com/docs/requests#headers), and add:

Header Name ("Key" in Postman)
Header Value ("Value" in Postman)

Authorization
Bearer MY_TOKEN

If you're using curl:

curl -H "Authorization: Bearer MY_TOKEN" "https://api.yelp.com/v3/businesses/search?term=delis&latitude=37.786882&longitude=-122.399972"

(You can read more about HTTP headers in https://en.wikipedia.org/wiki/List_of_HTTP_header_fields , but we only need one of them today.)

Really Great Support from your site. Thanks a lot. You save me lots of time. Thanks a bunch of tone.

@rahuls2704 : Wonderful!  If you have any more questions, head over to

https://github.com/Yelp/yelp-fusion

and good luck!

Could you make the Java example for this, sir? I understand the Java v2 sample, but when I try to do with v3, I got stuck at this step {"error": {"description": "An access token must be supplied in order
to use this endpoint.", "code": "TOKEN_MISSING"}}.
I tried to change the key and token from Java v2 file into like this:

And change the TwoStepOAuth file into like this:

Sorry for the question cuz I'm not good with the documentation

repo: Yelp/yelp-api


text:
Python sample fails when business ID contains special characters

Hello!
Using the Search API python sample to search for restaurants sometimes fails with the error:
Traceback (most recent call last):
File "search-yelp.py", line 170, in
main()
File "search-yelp.py", line 164, in main
query_api(input_values.term, input_values.location)
File "search-yelp.py", line 149, in query_api
response = get_business(business)
File "search-yelp.py", line 119, in get_business
return request(API_HOST, business_path)
File "search-yelp.py", line 63, in request
url = 'http://{0}{1}?{2}'.format(host, path, encoded_params.encode('utf8'))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 16: ordinal not in range(128)
This happens because business IDs can contain special characters like "é", which cannot be put into URLs before being decoded. For example, in this instance the specific cause of failure is trying to access the API endpoint "/v2/business/café-pro-bono-palo-alto-3".
This is easily fixed by changing line 59 to:
url = 'http://{0}{1}?{2}'.format(host, urllib.urlencode(path), encoded_params)

This change is still not updated in the example.

Taking a look.

Reproduced using
DEFAULT_TERM = 'cafe pro bono'

Newer stacktrace is:
Querying http://api.yelp.com/v2/search/? ...
Traceback (most recent call last):
  File "sample.py", line 158, in <module>
    main()
  File "sample.py", line 152, in main
    query_api(input_values.term, input_values.location)
  File "sample.py", line 134, in query_api
    business_id
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 3: ordinal not in range(128)

Whipping up a slightly-larger version of @tathougies fix.

authors: lechatpito mittonk tathougies


text:
[Feature] 支持负载均衡

多个api轮流使用

公众号：《我的代码会好吗》，有教程

repo: Yidadaa/ChatGPT-Next-Web


text:
The require introduction is replaced by import, and the npm source is replaced with the new one

1.https://registry.npm.taobao.org with https://registry.npmmirror.com
2.require(".. /polyfill") with import introduction
3.Maybe we need to use a stable version such as next

taobao 源有什么问题吗？
import 的 pollyfill 不会生效
next 13.0 有 bug #870

require语法可能不生效，netlif平台

淘宝源已经替换了新地址，不知道npm.taobao.org什么时候就会突然关闭，建议替换

第三个问题没注意，哈哈我的问题

我测试的是 import 在 vercel 上不会生效
不要把 *.lock 加入 .gitignore

这个 PR 先关了。

authors: Evans-Cai Yidadaa


text:
Compiling errors in Centos

I am unable to compile HAMS source code using gfortran (v7.1.0) in Centos OS. I get following two errors:
**Warning: Unused variable ‘md’ declared at (1) [-Wunused-variable]
gfortran -g -m64 -c -O3 -fno-align-commons -fPIC -fdec-math -fbacktrace -fcheck=all -Wall -o AssbMatx_irr.o AssbMatx_irr.f90
AssbMatx_irr.f90:260:132:
      DIST=SQRT((iXYZ_P(IEL-NELEM,1)-XYZ_P(JEL,1))**2+(iXYZ_P(IEL-NELEM,2)-XYZ_P(JEL,2))**2+(iXYZ_P(IEL-NELEM,3)-XYZ_P(JEL,3))**2)
                                                                                1

Error: Line truncated at (1) [-Werror=line-truncation]
AssbMatx_irr.f90:260:132:
      DIST=SQRT((iXYZ_P(IEL-NELEM,1)-XYZ_P(JEL,1))**2+(iXYZ_P(IEL-NELEM,2)-XYZ_P(JEL,2))**2+(iXYZ_P(IEL-NELEM,3)-XYZ_P(JEL,3))**2)
                                                                                1

Error: Syntax error in argument list at (1)
AssbMatx_irr.f90:586:32:**

With the latest code, I am getting an error (see below) while compiling.
Error: Function ‘atan2d’ at (1) has no IMPLICIT type.

Make sure you use the -fdec-math compiler option.  This is activated in the makefile in the source directory.  If you are using an old version of gfortran, that might also be an issue.

For some reason, I deactivated it as I was using an older version of gfortran but now I switched to gfortran 7.1.0 and I am using the fdec-math option. However, now I have few linker errors. I am using Lapack version 3.9.1
/soft/opensoft/math/lapack-3.9.1/liblapack.a(zgetrf.o): In function zgetrf_': zgetrf.f:(.text+0x37e): undefined reference to ztrsm_'
zgetrf.f:(.text+0x437): undefined reference to zgemm_' /soft/opensoft/math/lapack-3.9.1/liblapack.a(zgetrs.o): In function zgetrs_':

On 17 May 2021, at 21:22, Garrett Barter @.***> wrote:
Make sure you use the -fdec-math compiler option https://gcc.gnu.org/onlinedocs/gcc-9.2.0/gfortran/ATAN2D.html. This is activated in the makefile in the source directory. If you are using an old version of gfortran, that might also be an issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/YingyiLiu/HAMS/issues/4#issuecomment-842437072, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFBMHVVUDL5C4VSA7O2SU3TOE3UZANCNFSM44V3HFPQ.

Sorry you are still having issues.  That one is tough for me to help with remotely as you are using custom installs of Lapack.  Maybe double cross check with the makefile flags that are working.
When I get around to setting up a CI workflow, maybe some of these issues will get ironed out.

Finally, I managed to compile HAMS without any errors by using another compiled version of Lapack from PETSC-3.12.0 module

Congratulations, @ramisetti , could you share the link of that Lapack package, so that others can follow? Thanks.

I compiled the PETSC-3.12.0 library which also has Lapack package. The link for Petsc is https://www.mcs.anl.gov/petsc/download/index.html. However, I will not suggest this procedure to all users because in my case I was trying to use Lapack library (https://www.netlib.org/lapack/lug/node11.html) that I compiled from its source code. For some reason, HAMS is not working with this version. So I used the libraries from PETSC that I compiled for other codes.
In general, one can install the Lapack library files on their personal Linux machine if not already available. Then, I think they will be able to compile HAMS without any problem. For instance, on Ubuntu OS the following command in the terminal will install Lapack library.
sudo apt-get install liblapack-dev

It's been a while since I ran a RedHat/Centos machine, but Lapack should be available via your package manager too . .

Yes, it is indeed available in Centos machines as well. In my case, I prefer not to install it in the system location so as to avoid any conflicts with other codes that depend on it.

On 18 May 2021, at 15:56, Garrett Barter @.***> wrote:
It's been a while since I ran a RedHat/Centos machine, but Lapack should be available via your package manager too . .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/YingyiLiu/HAMS/issues/4#issuecomment-843051961, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFBMHUHVMPT37OPWCRX6H3TOI6GTANCNFSM44V3HFPQ.

authors: YingyiLiu gbarter ramisetti

repo: YingyiLiu/HAMS


text:
Traverse between "marked" points of the history

I'm using baobab to make a game, and I wanted to save snapshots of the tree at the start of each game tick, it's almost like the history feature, but instead of traversing between state changes, I wanted to traverse between the initial states of the game ticks.
My initial idea was to mark the history somehow, but I don't know, maybe there's a better way to do it.

Found a kinda hacky way to do it (saving the tree state to a separate object and restoring it when needed).

Hello @kress95. The solution is indeed to store your tree's state and archive it somewhere in an index with a hashed key or something so you can retrieve it and then just reset the tree indeed. Since the tree is persistent (it will fail of course if you disable the tree's persistence) the history can be stashed easily.

I'm using it only for debug purposes, so no problems with disabling tree persistence during "real" gameplay. Thanks for attention :+1:

repo: Yomguithereal/baobab


text:
osu stats

osu stats gelsin kaç yıldız kaç bpm falan oynuyoz ortalamaası falan
original message by @eruism

this will be on hold until I get a large enough database to calculate the maps' performance results without any significant slowdown

repo: YoruNoKen/HanamiBot


text:
Transfer Json

how do you port psych engine chart to yoshi crafter?(because its has a different json format i think)

should work as long as it has no events iirc

Psych Engine charts should work with Yoshi Engine, as long as the events are present with the other notes instead of in the "events" key of the json.

authors: MJFNF YoshiCrafter29 blissedandpissed


text:
Valid RTLIL produces invalid Verilog, which Yosys then cannot read back

From an nMigen issue.
Steps to reproduce the issue
bug.rtlil:
module \top
  wire width 1 input 0 $signal
  wire width 1 output 1 \a
  wire width 1 $next\a
  wire width 1 $1
  cell $reduce_bool $2
    parameter \A_SIGNED 0
    parameter \A_WIDTH 0
    parameter \Y_WIDTH 1
    connect \A {}
    connect \Y $1
  end
  process $group_0
    assign $next\a 1'0
    assign $next\a $1
    sync init
    sync always
      update \a $next\a
  end
end

On latest master (0e7901e4), run the following:
yosys -p "read_ilang bug.rtlil; write_verilog bug.v; delete; read_verilog bug.v"

Yosys gives a parse error when reading back the Verilog it has just generated. The cause is a zero-item concatenation list, which is syntactically illegal (1364-2005 A.8.1).
However, the following succeeds:
yosys -p "read_ilang bug.rtlil; synth; write_verilog bug.v; delete; read_verilog bug.v"

This produces a 1'h0 assignment to a.
Expected behavior
Zero-item concatenations are explicitly special-cased in ilang_parser.y, and zero-width wires are not disallowed in the RTLIL documentation. As far as I have read through the source code (admittedly not very) Yosys copes with these in its in-memory representation.
OTOH the Verilog standard explicitly forbids zero-item concatenations, forbids zero-length wires in a roundabout way, and is surprisingly woolly on zero-length signals produced by expressions (with surprising edge cases, e.g. being allowed inside of concatenations).
As:

Zero-length signals are not disallowed by RTLIL, but are disallowed by Verilog
The or reduction of a zero-width signal is logically zero (empty sum convention)
The current synthesis behaviour is to produce zero for the or reduction

I would expect read_ilang bug.rtlil; write_verilog bug.v to produce a zero assignment to a. If not, some other valid Verilog, based on some documented behaviour. Note that the above is a minimal example to provoke the problematic behaviour, but it was isolated from real code.
Actual behavior
Yosys produces invalid Verilog, which it cannot then read back. Paste of write_verilog output:
/* Generated by Yosys 0.8+354 (git sha1 0e7901e4, gcc 8.2.0-7ubuntu1 -fPIC -O2) */

module top(a, _2_);
  wire _0_;
  reg _1_;
  input _2_;
  output a;
  reg a;
  assign _0_ = | {  };  // syntax error here
  always @* begin
    _1_ = 1'h0;
    _1_ = _0_;
  end
  initial begin
  end
  always @* begin
      a <= _1_;
  end
endmodule

You should never use write_verilog with an RTLIL design with processes. It even gives you the following warning:

Warning: Module top contains unmapped RTLIL processes. RTLIL processes
can't always be mapped directly to Verilog always blocks. Unintended
changes in simulation behavior are possible! Use "proc" to convert
processes to logic networks and registers.

I think I've fixed it in #953. But generating Verilog with zero-width expressions is really asking for troubles imho. I think it's better to get rid of them by running something like opt_expr before writing the Verilog output.

You should never use write_verilog with an RTLIL design with processes. It even gives you the following warning:

This is true in general, but nMigen specifically generates only RTLIL processes that it knows it can use with write_verilog. The alternative to this is not using Yosys or RTLIL at all, which I think you will agree is a massive waste of time.

The alternative to this is not using Yosys or RTLIL at all, which I think you will agree is a massive waste of time.

Running proc is not an option?

Running proc is not an option?

The output of oMigen has historically been readable, since it is the source of truth that is used when debugging incorrect behavior of the kind that is not easily visible from Python. I've added tooling in nMigen to handle the most common cases without having to resort to read the processed output but it is not a silver bullet.
Althuogh it has been readable, it has never been particularly easy to read, especially due to the fact that the design was completely flat. nMigen has fixed this and produces hierarchical designs now. But reading RTLIL corresponding for them almost negates that advantage due to its verbosity; RTLIL is a reasonably good IR but it is not so useful as an output of a tool for finding problems at a glance.
That's the primary reason nMigen emits Verilog, and that's why nMigen emits Verilog with processes, and of course that's the reason for having #726. If I am not able to use Yosys to do so, I would have to implement a Verilog backend for nMigen from scratch; and, the Verilog backend in oMigen is seriously buggy in all the little nasty Verilog edge cases Yosys is good at handling, and really should be the single source of truth for, in this case.

Reopening since it seems unclear per LRM whether "" has width 0 or 8.

authors: Wren6991 cliffordwolf whitequark

repo: YosysHQ/yosys

license: isc


text:
🛑 Xiaohongshu-Wang is down

In a6ce474, Xiaohongshu-Wang (https://www.xiaohongshu.com/user/profile/5d1d9a0400000000160115c6?xhsshare=CopyLink&appuid=64d8c888000000000100dc16&apptime=1691929476) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Xiaohongshu-Wang is back up in e5c4d58 after 12 minutes.

repo: Yourrrrlove/upptime


text:
🛑 UPC is down

In 3443657, UPC (https://www.upc.edu.cn/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UPC is back up in 65ea30f after 6 minutes.


text:
🛑 cheeselist is down

In bb69c4c, cheeselist (https://www.runningcheese.com/aaa) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cheeselist is back up in b05a48a after 5 minutes.


text:
Application to reproduce the experimental results of the industrial dataset

Hello, I am very interested in your work, can you provide the download link of industrial dataset？If possible, please send it to my email wu.surqing@gmail.com or reply to me directly.

Thank you for your interest in our paper! As the industrial dataset is real large-scale data from Alibaba's production environment, based on the company's data privacy policy, we are unable to make the industrial data public. The other public datasets involved in the paper are all accessible in Google Drive. I hope these can help your reproduction.

Okay, thank you for your reply.

authors: YuanchenBei surqing

repo: YuanchenBei/MacGNN


text:
About applying AudioAttNet only after 300k steps

Hi Yudong,
Thanks for releasing your code for the audio-driven NeRF! I love the idea of using NeRF to solve this problem, and your implementation is pretty decent and neat.
I have a question in your implementation. I observed that the AudioAttNet is not applied in the first 300k steps (or more specifically, the values given by args.nosmo_iters, default to be 300k), and only applied after the 300k steps. That basically means it will not be used in the HeadNeRF training (which default to have 300k steps at max) and only in TorsoNeRF combined training. May I kindly ask the reason behind this way of implementation? And/or is there a reason to choose 300k as a specific point to apply AudioAttNet?
Thanks in advance!

Hi Jerry,
Thanks for your kind words. It's my mistake that set N_iters not greater than nosmo_iters in HeadNeRF. Thanks for pointing out this. Also note that in this implementation the AudioNet and AudioAttNet are only trained in HeadNeRF, and they are fixed during TorsoNeRF training.

Hi Yudong,
Thanks for your quick reply. May I ask is there a particular reason that AudioAttNet is trained only after 300k (or args.nosmo_iters steps?

Hi Jerry,
There is no particular reason for this strategy. We just want to make the network first learn to predict reasonable neural radiacen fields for each frame and then learn to smooth the prediction. I didn't try to train the AudioAttNet at the beginning, while I think they will produce similar results.

Hi Yudong,
Got it - it's good to know that, thanks!

repo: YudongGuo/AD-NeRF