text:
Crash during todo list due to sort comparison

I installed todoman yesterday (version 1.6.0); after getting it to read my vdir the list command fails to list my todos; it throws
Traceback (most recent call last):
  File "/usr/local/bin/todo", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 696, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 1037, in invoke
    return Command.invoke(self, ctx)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 889, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/todoman/cli.py", line 64, in cli
    ctx.invoke(cli.commands["list"])
  File "/usr/local/lib/python3.4/dist-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/todoman/cli.py", line 232, in list
    reverse=reverse
TypeError: other argument must be K instance

By printing the value of rv (main.py#L82) we get
[0, False, inf, <functools.KeyWrapper object at 0x7fd9f2cd1970>]
[0, False, inf, <functools.KeyWrapper object at 0x7fd9f2cd18f0>]
...
[<functools.KeyWrapper object at 0x7fd9f2cd19b0>, False, inf, <functools.KeyWrapper object at 0x7fd9f2cd1990>]

which causes the comparison to fail when the first and last todos are compared, since the first element is of a different type. The first element is for the priority field (main.py#L40); because it is a "negative" field it enters the main.py#L73 condition. I believe the fix should be to change the condition to if neg, in order to allow the comparison to occur. I've PR'd in #25, please check it and see if I'm understanding this correctly. Tell me if you need any sample data or more info.
And thank you very much for developing and maintaining todoman, I was looking for a CLI todo manager for a while!

Thanks for tracing down the issue. I recently added a unit test, that exposes this bug (currently, master is failing due to it), but failed horribly to track down what was causing it.

Ah, and thanks for the kind words regarding todoman. It's nice to know it's of use to others! :)

authors: hobarrera jlbribeiro

repo: pimutils/todoman

license: isc


text:
Print output with plain text--i.e. not color formatted

Just a suggestion but it might be useful to print the output without color-formatted text. While I am actually in support of more color support throughout the project as a whole, it could be useful to have a --no-color option for those wanting to print the output for the use of commands not yet supporting color formatting.
Case in point: I currently set up keybindings for each of my calendar-linked task list which prints the output to dunst via notify send. Dunst, as far as I can tell, cannot intemperate the color formatting being output by todo. Before doing this I have to strip away all of the color formatting with something along the lines of notify-send "$(echo -e "\t\t\tComputer\n"; todo list computer --no-reverse --status ANY | tr -dc '[:print:]\n\r\t' | sed 's/\[[0-9][0-9];.*\[0m//g;s/\[[0-9][0-9]m//g;s/\[0m//g')". Calling this command from xmonad via haskell gets even more ugly.
In sum, while not a deal breaker, I could certainly see some utility in having the option to output text without color formatting

I think todo --colour=never should do the trick.
For scripting. todo --porcelain piped with jq might also be worth looking at.

Thanks, I'll have to take a look at that. I could have sworn that I had gone over the docs a couple of time looking for a no color option; I must have missed it. Again, though, you've been a big help!

source: gharchive/issue

license_type: permissive

license_source: bigquery


text:
vfs: Fix counting in inode_avail_count

As seen in inode_del and inode_alloc, a free (VFS_TYPE_NOT_INIT) node can be found anywhere in g_vfs_dev_nodes; it’s a “sparse” list.
So when checking for free nodes, the iterating index variable (e) shall be used, not the counter (count). The code got that wrong.
For instance, if the first node is not available (type is not VFS_TYPE_NOT_INIT), then the function previously returned 0, no matter what, and was iterating the node list in vain.

Thank you very much for your pull request!
For receiving the free PineCone, please sign up at this link.
(If there will be any issues with signing up, please let me know here).

You’re welcome.
I could successfully sign up for the free PineCone. Thanks to you!

source: gharchive/pull-request

authors: PaulCapron gamelaster

license_source: github-api


text:
Proper error codes (and return failure code)

Seeds more error code values into the code, and ensures that the CLI tool returns these as exit codes.
Not tested on hardware (yet).
Should close #29 when merged.

This is working great for me locally, so going to merge.

license: MIT


text:
Copy Namespace Feature

Is there any copy namespace feature available in pinecone?
I have tried to search about it but have not been able to find any sort of solution provided by pinecone SDK.
It seems like the only way to copy the namespace is to get all the results and copy it and re upload it.

Also interested in that feature

Hey @igorbilyk2 and @Ahtesham00 , thanks for the feedback. Can you expand more on:

What motivated you to submit this feature request/what problem this would solve?
A clear and concise description of what you want to happen.
Any alternatives you've considered?

@anawishnoff

What motivated you to submit this feature request/what problem this would solve?

My software users want the ability to copy the namespace or the data I am storing under a specific namespace so they can have it replicated elsewhere in the system. The issue isn't with copying itself, as I can point my users to the same vectors. The problem arises when they want to expand on the copied namespace. For example, if I have 100 vectors in namespace X, and my application users want to copy this namespace, they should be able to upload more vectors to the copied namespace.

A clear and concise description of what you want to happen.

I would like to have a feature that allows users to duplicate an existing namespace along with its vectors and then enable them to add more vectors to the duplicated namespace. This functionality should allow the copied namespace to be independent of the original, enabling users to expand on it as needed.

Any alternatives you've considered?

In the past, I've used an alternative method where I extract all the results and then reupload them. However, this approach has its limitations. Specifically, I have to assign a specific top_k value during the extraction, which can change over time and may not be optimal for all scenarios.

Hey @Ahtesham00 , thanks for providing those details! Have you looked into collections (for pod-based indexes) or backups (launched recently for Serverless indexes)? You can find the documentation here: https://docs.pinecone.io/guides/indexes/understanding-backups-and-collections. This allows you to create copies of your indexes, and reupload it somewhere where it can be added to/modified.

repo: pinecone-io/pinecone-ts-client


text:
Mini OSSInsight

[ ] docker image for backend
[ ] docker image for frontend
[ ] docker image for api server
[ ] docker setup for tidb & tiflash
[ ] docker-compose to run ossinsight components
[ ] Prepare sample data, about 500M records, smoothly distributed from 2011 to 2022

FE:

[ ] Front end API base url should be parameterized if it use another domain

shall we support share api?

shall we support share api?

No need

Also make blacklist_users and blacklist_repos tables in the migrate

repo: pingcap/ossinsight


text:
Support debug/pprof/symbol call to enable remote jeprof

What is changed and how it works?

Issue Number: Close #xxx

What's Changed:

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

Note, we still have to set
export MALLOC_CONF="prof:true,prof_active:false"

in scripts/run_tiflash.sh
before a newer version of tiup than 1.16 is released.

Sleep 10s on proxy's side
perl /DATA/disk3/calvin_81/disk1/tiflash/tics2/contrib/tiflash-proxy/proxy_components/proxy_server/src/status_server/jeprof.in --raw "http://127.0.0.1:5765/debug/pprof/heap"

stdout
!!!!! CMD is curl -s --fail 'http://127.0.0.1:5765/debug/pprof/heap' > /DATA/disk1/calvin/jeprof/.tmp.tiflash.1724656693.127.0.0.1.pprof.heap
Fetching /pprof/heap profile from http://127.0.0.1:5765/debug/pprof/heap to
  /DATA/disk1/calvin/jeprof/tiflash.1724656693.127.0.0.1.pprof.heap
Wrote profile to /DATA/disk1/calvin/jeprof/tiflash.1724656693.127.0.0.1.pprof.heap

Proxy's log
[2024/08/26 15:18:13.222 +08:00] [INFO] [profile.rs:111] ["!!!!!! start_one_heap_profile start"] [thread_id=670]
[2024/08/26 15:18:23.223 +08:00] [INFO] [profile.rs:115] ["!!!!!! start_one_heap_profile end"] [thread_id=670]

repo: pingcap/tidb-engine-ext


text:
Fix gtest_dm_minmax_index.cpp clang tidy.

Signed-off-by: Jigao Luo luojigao@outlook.com
What problem does this PR solve?
Issue Number: close #4604
Problem Summary:
What is changed and how it works?
Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/cc @ywqzzy

/run-unit-test

@cakebytheoceanLuo Thanks for your contribution!

/merge

authors: Lloyd-Pottiger cakebytheoceanLuo

repo: pingcap/tiflash


text:
CDC "/status" API may cause panic

What did you do?
│[2022/08/16 18:35:57.674 +05:30] [INFO] [version.go:47] ["Welcome to Change Data Capture (CDC)"] [release-version=v6.1.0-20220812] [git-hash=b3cd5a49c75ceca1faeae6f6f9f3a1c03fb071eb] [git-branch=heads/refs/tags/v6.1.0-20220812] [utc-build-time="2022-08-12 11:56:07"] [go│
│[2022/08/16 18:35:57.674 +05:30] [INFO] [server.go:78] ["creating CDC server"] [pd="[http://lockin-cm-ch-pd:2379]"] [config="{\"addr\":\"0.0.0.0:8301\",\"advertise-addr\":\"lockin-cm-ch-ticdc-3.lockin-cm-ch-ticdc-peer.rigel-clusters-prod.svc:8301\",\"log-file\":\"/dev/s│
│[2022/08/16 18:35:58.411 +05:30] [INFO] [server.go:320] ["/ticdc/data is set as data-dir (62GB available), sort-dir=/ticdc/data/tmp/sorter. It is recommended that the disk for data-dir at least have 500GB available space"]                                                │
│[2022/08/16 18:35:58.412 +05:30] [INFO] [server.go:199] ["http server is running"] [addr=0.0.0.0:8301]                                                                                │
│2022/08/16 18:35:58 http: panic serving 10.39.136.210:51186: runtime error: invalid memory address or nil pointer dereference                                                                                │
│goroutine 224 [running]:                                                                                │
│net/http.(*conn).serve.func1()                                                                                │
│       net/http/server.go:1825 +0xbf                                                                                │
│panic({0x2dcea20, 0x647e000})                                                                                │
│       runtime/panic.go:844 +0x258                                                                                │
│github.com/pingcap/tiflow/cdc/capture.(*Capture).Info(0x27?)                                                                                │
│       github.com/pingcap/tiflow/cdc/capture/capture.go:321 +0x8c                                                                                │
│github.com/pingcap/tiflow/cdc/api.(*statusAPI).handleStatus(0xc000944848, {0x7fc681959868, 0xc000d16100}, 0xc000b82000?)                                                                                │
│       github.com/pingcap/tiflow/cdc/api/status.go:77 +0xf0                                                                                │
│github.com/gin-gonic/gin.WrapF.func1(0xc000d16100)                                                                                │
│       github.com/gin-gonic/gin@v1.7.4/utils.go:41 +0x59                                                                                │
│github.com/gin-gonic/gin.(*Context).Next(...)                                                                                │
│       github.com/gin-gonic/gin@v1.7.4/context.go:165                                                                                │
│github.com/gin-gonic/gin.(*Engine).handleHTTPRequest(0xc0002c0340, 0xc000d16100)                                                                                │
│       github.com/gin-gonic/gin@v1.7.4/gin.go:489 +0x63e                                                                                │
│github.com/gin-gonic/gin.(*Engine).ServeHTTP(0xc0002c0340, {0x3a2d840?, 0xc0006600e0}, 0xc000d16000)                                                                                │
│       github.com/gin-gonic/gin@v1.7.4/gin.go:445 +0x1c5                                                                                │
│net/http.serverHandler.ServeHTTP({0xc000592180?}, {0x3a2d840, 0xc0006600e0}, 0xc000d16000)                                                                                │
│       net/http/server.go:2916 +0x43b                                                                                │
│net/http.(*conn).serve(0xc000a640a0, {0x3a2f530, 0xc00055c570})                                                                                │
│       net/http/server.go:1966 +0x5d7                                                                                │
│created by net/http.(*Server).Serve                                                                                │
│       net/http/server.go:3071 +0x4db                                                                                │

What did you expect to see?
No panic.
What did you see instead?
Panic.
Versions of the cluster
TiCDC version (execute cdc version):
v6.1.0

/severity Major

/close

authors: fubinzh nongfushanquan overvenus

repo: pingcap/tiflow


text:
puller(ticdc):  fix resolvedTs get stuck when region split and merge

What problem does this PR solve?

Issue Number: ref #10157
What is changed and how it works?
Always delete the the mapping in cachedRegions when a span's regionID changes.
This can prevent an old span node in the frontier from becoming an orphan node, which would cause the resolvedTs of the corresponding span to not be updated.
Check List
Tests

Unit test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Fix a bug where region split and merge cause the changefeed resolvedTs to get stuck.

/retest-required


text:
filter (ticdc): add unit test case to cover all event type for event filter

What problem does this PR solve?

Issue Number: ref #10511
What is changed and how it works?
Check List
Tests

Unit test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest


text:
sink/mq(ticdc): make the topic manager use the correct number of partitions

What problem does this PR solve?

Issue Number: close https://github.com/pingcap/tiflow/issues/5076
What is changed and how it works?
make the topic manager use the correct number of partitions.
It uses the wrong number of partitions when kafka turns on auto-create configuration.
Check List
Tests

Unit test
Integration test

Code changes

Has exported function/method change

Side effects
None
Related changes
None
Release note
None

/run-all-tests

/run-all-tests

/run-kafka-integration-test

/run-kafka-integration-test

/run-kafka-integration-test

/run-kafka-integration-test

/run-kafka-integration-test

/run-kafka-integration-test

/run-all-tests

Codecov Report

Merging #5116 (4a65745) into master (687e248) will decrease coverage by 0.2471%.
The diff coverage is 57.3770%.

Flag
Coverage Δ

cdc
60.8420% <52.1159%> (+0.2434%)
:arrow_up:

dm
51.9254% <84.3373%> (-0.5441%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #5116        +/-   ##
================================================
- Coverage   56.1240%   55.8768%   -0.2472%
================================================
  Files           522        526         +4
  Lines         65325      67851      +2526
================================================
+ Hits          36663      37913      +1250
- Misses        25094      26203      +1109
- Partials       3568       3735       +167

/run-all-tests

/run-leak-test

/run-kafka-integration-test

/merge

/run-all-tests

/run-verify

authors: asddongmen codecov-commenter hi-rustin zhaoxinyu


text:
metrics(ticdc): fix no sorter metrics

What problem does this PR solve?

Issue Number: close #5690
What is changed and how it works?
Check List
Tests

Manual test (add detailed scripts or steps below)

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
fix no sorter metrics

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-5.1@75dfaa2). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release-5.1      #5695   +/-   ##
================================================
  Coverage               ?   62.3484%
================================================
  Files                  ?        162
  Lines                  ?      17075
  Branches               ?          0
================================================
  Hits                   ?      10646
  Misses                 ?       5525
  Partials               ?        904

/merge

/run-unit-tests

authors: asddongmen codecov-commenter


text:
tikv-server: fix clap short argument bug

fixes #1833

LGTM

authors: andelf ngaut

repo: pingcap/tikv


text:
*: support to_socket_addr.

@ngaut @BusyJay

LGTM

LGTM

authors: BusyJay ngaut siddontang


text:
Refactor expr system

What problem does this PR solve?
This PR makes current expression system being aware of data type info. By doing this, we can take advantage of spark's type coercer system.
After this PR, ExpressionTypeCoercer is not used any more and can be safely deleted. MetaResolver will be only called in ExprUtils.
We also convert Expression from interface to  an abstract class. In addition, dataType and resolved are added as filed of Expression.

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests mode=full

/run-all-tests mode=full

I recommend that explain details contain more info about types such as decimal and string types.  e.g., col_decimal@Decimal(20, 3) @zhexuany

I recommend that explain details contain more info about types such as decimal and string types. e.g., col_decimal@Decimal(20, 3) @zhexuany

Advice taken.

/run-all-tests mode=full

/run-all-tests mode=full

/run-all-tests mode=full

/run-all-tests mode=full

/run-all-tests mode=full

/run-all-tests mode=full

authors: birdstorm zhexuany

repo: pingcap/tispark


text:
FatalErrorException

runnning:
php artisan generate:migration create_users_table
i got:
[Symfony\Component\Debug\Exception\FatalErrorException]
Method Pingpong\Generators\Stub::__toString() must not throw an exception
but running php artisan make:migration create_users_table
ok

I've fixed this issue via this commit https://github.com/pingpong-labs/sky/commit/5705abf37c42462b636ec86ab1c7b82c204c1161. And will pushed to this repository soon. Thanks!

thank you
can you tell me how you debug,
I can't finf throw problem with regular exception...
Il 08/07/2015 06:40, Gravitano ha scritto:

I've fixed this issue via this commit pingpong-labs/sky@5705abf
https://github.com/pingpong-labs/sky/commit/5705abf37c42462b636ec86ab1c7b82c204c1161.
And will pushed to this repository soon. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/pingpong-labs/generators/issues/3#issuecomment-119428961.

Just basic debugging. If using artisan, you can add -v option to see the error trace is something went wrong.

authors: gravitano ummira

repo: pingpong-labs/generators


text:
Toast: fix for darkMode

Summary
Toast was not working in darMode. The color white was redering as black if darkMode is set.
What changed?
changed default color to darkGray. And the Box Component takes care of it during darkMode.

Hi there @zifahm - I apologize that the docs are confusing, but our Toast was actually working properly in dark mode. The key is to look at this example: https://gestalt.pinterest.systems/toast#displayExample
When you use that example to show the Toast while in darkMode on the docs, you'll see it works appropriately.
I will add a note to the docs to showcase that the other examples are not currently picking up dark mode properly. Thanks for bringing this up!

Hi @ayeshakmaz , when I tried to reporduce the same example in codesanbox with colorSchema set to dark, toast is not picking it up. Could you help me with how would I make it work?
https://codesandbox.io/s/example-how-to-display-forked-12evnw?file=/example.js

@zifahm I believe if you add an "id" to your ColorSchemeProvider, it works well and produces the right Toast. I'll double check on the docs and see if the guidance around "id" prop needs to be updated. Thanks for the sandbox!

Hi, @ayeshakmaz
I have a problem if I pass an id for the ColorSchemaProvider and setting to darkmode, my other models or layers does not pick up.
But if I dont pass an Id there isnt any problem, but here now as you suggested above toast doesnt pick it up if it dark mode is set.
It's like, if id is present model or layer fails , if id is'nt passed toast fails.
How would one solve this problem?

Hi @zifahm, are you able to reproduce this issue in a code sandbox by chance?

Hi @ayeshakmaz
sure : https://codesandbox.io/s/overlaying-content-forked-k46v71?file=/example.js
So if you open the layer first, you see its lightGray and then if you remove the id for colorSchema its goes back to being dark because darkMode is set. This is true for toast as well.
Right now I'm doing a patch package on toast with the same code fix of this PR

Hi @zifahm we recently made an update to Toast in dark mode, so I believe this issue should be resolved now. Let me know if you still see it after version 59.0.0

authors: ayeshakmaz zifahm

repo: pinterest/gestalt


text:
Secor failure upload policy

If max file age set to more than 24 hours Secor fails to upload files when using DateMessageParser or other parsers that partition message based on date. Probably because every new day there will be new file created in each topic partition that renews the result of getModificationAgeSec method in FileRegistry.

The upload should not be delayed indefinitely. In the worst case, there could be a delay of 48h. For details, see https://groups.google.com/forum/#!topic/secor-users/wxO0Eb83_R4

I understand how secor uses the age of newest file in partition for the upload policy, but if I configure secor to use a DateMessageParser, when the new day comes(the timestamp of messages extract local machine time), a new file will be created in the same partition to store messages of the new date, will this behavior set file age zero everyday? Will it constrain secor upload policy?

I think you are right. It is rather unconventional to set the upload delay to a value larger than the partition time interval but there is a corner case here that is not supported.

Thanks for confirmation. I was thinking about some use cases that when the total message throughput is small, it is better to batch messages for longer time to create larger and lesser file on object store server, cause when the number of objects is large on S3 or other object store such as Swift, the performance may suffer.

repo: pinterest/secor


text:
Disable disallowed func lint per line

instead of excluding whole file.
This change allow to unify lint script among the repositories.
ref: https://github.com/pion/dtls/pull/166#discussion_r364023754

Codecov Report

Merging #167 into master will increase coverage by 0.05%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #167      +/-   ##
==========================================
+ Coverage   72.01%   72.07%   +0.05%
==========================================
  Files          60       60
  Lines        3431     3431
==========================================
+ Hits         2471     2473       +2
+ Misses        660      659       -1
+ Partials      300      299       -1

Impacted Files
Coverage Δ

internal/crypto/ccm/ccm.go
64.7% <0%> (ø)
:arrow_up:

client_handlers.go
78.7% <0%> (+0.53%)
:arrow_up:

Continue to review full report at Codecov.

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

rebasing

authors: at-wat codecov-io

repo: pion/dtls


text:
Fix handling of retransmitted cookie-echo

Relates to pion/webrtc#1270
Description
Please see this comment(https://github.com/pion/webrtc/issues/1270#issuecomment-653953743) for details.
What's in this PR

Fixed the issue by sending COOKIE-ACK on the receipt of COOKIE-ECHO even in the Established state.
Added a reproducible test using vnet, successfully confirmed the problem, and the fix.

@Sean-Der This is a fix for a fundamental error in handling delayed cookie-echo received in the "established" state (which would happen on lossy connection).  If you could review this at your earliest convenience, that would really be appreciated.

$ bash .github/lint-commit-message.sh
Update association.go

Accepted the change.

Co-authored-by: Atsushi Watanabe <atsushi.w@ieee.org>

-------------------------------------------------
The preceding commit message is invalid
it failed 'Separate subject from body with a blank line' of the following checks

* Separate subject from body with a blank line
* Limit the subject line to 50 characters
* Capitalize the subject line
* Do not end the subject line with a period
* Wrap the body at 72 characters

Commit message from GitHub web UI uses CR+LF which is currently not supported by our commit message lint script. https://github.com/pion/.goassets/issues/6
git commit --amend and remove CR will fix the error.

authors: at-wat enobufs

repo: pion/sctp

license: mit


text:
Add fuzzer

This is an updated version of https://github.com/pion/sdp/pull/12 by @maxhawkins.

This now also includes a test and fix for #13, which I rediscovered while running this fuzzer.

I've added my name to the readme, although I'm not happy about it. I'll raise that on slack.
I've also added some performance optimizations. There's plenty more low hanging fruit after this, but it is a start.

The build failure is because it claims that "marshalling" is the wrong spelling.
https://stackoverflow.com/questions/4434590/marshall-or-marshal-marshalling-or-marshaling
The wikipedia entry contains both spellings: https://en.wikipedia.org/wiki/Marshalling_(computer_science)
I will change it, but under protest.

Travis failed this PR, saying:

it failed 'Separate subject from body with a blank line'

But I don't see that any of my commit messages match this description. (And, unhelpfully, it doesn't appear to tell me which commit message is the problem.) I extracted the test it is doing  (awk 'NR == 2 {print $1;}' | wc -c != 1 and ran it on each commit in turn, and they all passed.
Any hints?
I've now spent more time trying to fix lint complaints (spelling, commit messages, where to write my name) than actually working on the code.

OK, the CI finally passes on this PR.

@josharian amazing work :fire:
So my only question is how can we get this into CI? I see there are some services that run fuzz testing against master non-stop, should we sign up for something like that?

authors: Sean-Der josharian

repo: pion/sdp


text:
Close accepted listener connections

This is a new PR for the issue originally addressed in #232

@rg0now Would you approve and merge the PR for me? Thanks :)

Thanks @rg0now for the review. But apparently I still can not merge the PR :(
@at-wat do you mind approving it as well?

repo: pion/turn


text:
HTML export doesn't seem to work on 2.0 release

Or it takes an extremely long time.
Downgrading back to 1.9.1 worked immediately

Hi @Amie-chan, I have a few questions to check with you.

Is it a long document?
Do you have more than 20 existing chat history?
Does this also happened on text and markdown?

Hi @Amie-chan, I have a few questions to check with you.

Is it a long document?
Do you have more than 20 existing chat history?
Does this also happened on text and markdown?
Take extremely long...Like how long?

Tried both long (4 scroll pages worth), and short (single reply) with same results
No, <10
I only tried screen cap and it works, I can try the others later

10 minutes with no result

No

The html generation worked within 2s after downgrading, using the same conversation

Can you see your history? Seems like history API has been disabled for an unknown reason.

We will have to wait for the history module back.
I will add an enhancement on the UI to let user know what happened and why.

I cannot see the history. It was available earlier today when I submitted the issue

I cannot see the history. It was available earlier today when I submitted the issue

The script itself also has a bug here. I will fix it.

This

And I'm considering bringing some local parsing back as a fallback.

v2.1.0 has been released. But it will not fix the problem. It can only reflect the actual situation properly.
If you really want to use the export feature, then downgrading to 1.9.1 is also a solution.

Well... it gets weird now. They unlocked the history feature toggle... but you will get an empty history list from the API.
window.__NEXT_DATA__.props.pageProps.shouldDisableHistory // false

Ditto, I concur.

I suggest renaming this issue to avoid duplicates. The name is misleading as this affects all export capability.

Thanks @pionxzh for your excellent work on this btw! I can confirm v1.9.1 works.

Thanks @pionxzh for your excellent work on this btw! I can confirm v1.9.1 works.

You can use 2.1.1, which is equivalent to 1.9.1.
This approach enables most of the people to stay up-to-date and still be able to get something functional.

Looks like the history API is back, but now I'm away from my PC. I will put back 2.1.0 when I'm available.

You can log out and log back in, see what happens, sourced from this reddit post. See what happens.

Oh wow, thanks dude 😭

authors: Amie-chan alex-rosenberg35 pionxzh

repo: pionxzh/chatgpt-exporter


text:
Add RevisionManifest for CloudRun

What this PR does / why we need it:
Add RevisionManifest for CloudRun.
I don't force Manifest to be common because it'll more complicated than this.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

Nice.
/lgtm

👍
/approve

authors: khanhtc1202 knanao nghialv

repo: pipe-cd/pipecd


text:
Implement LMNT full-duplex TTS generation

LMNT has an interesting approach to 'full-duplex' TTS:
async def main():
  async with Speech() as speech:
    connection = await speech.synthesize_streaming('lily')
    t1 = asyncio.create_task(reader_task(connection))
    t2 = asyncio.create_task(writer_task(connection))
    asyncio.gather([t1, t2])
    connection.close()

This doesn't really work with our FrameProcessor architecture, but it does actually work pretty well with the idea of a custom pipeline. I've started building that out in examples/foundational/02a-async-llm-say-one-thing.py.
I'm currently stuck because I think there's a bug in their implementation. After I get the first chunk of audio back, the websocket connection to LMNT seems to close. I've tried logging just about everywhere I can think of, and I can't find an explanation. I'm going to try and get in touch with the LMNT team to troubleshoot.
(I found out about LMNT through Andy Korman, who I met at our Voice + AI Summit.)

Hi Chad, this is awesome! I patched this and was able to initially repro the issue you describe, but after the issue manigesting on my first test room and connection, it is now working every time.
Do you have specific repro steps that you find surface the issue each time? This would make debugging easier.
A guess is that somehow the way the pipeline logic is set up for a new room, or an edge case on entering a room, is causing the in/out tasks to immediately conclude. Also open to getting on Slack or a VC to discuss more efficiently whenever works for you, FYI @sayitwithai

Closing in favor of #391

authors: aconchillo chadbailey59 shaper

repo: pipecat-ai/pipecat


text:
Scope and URL mismatch

Hey guys,
Please help me!
I give this error:
Unirest\Response {#1172 +code: 403 +raw_body: "{"success":false,"error":"Scope and URL mismatch","errorCode":403}" +body: {#1181 +"success": false +"error": "Scope and URL mismatch" +"errorCode": 403 } +headers: array:21 [ 0 => "HTTP/1.1 403 Forbidden" "Date" => "Thu, 02 Jul 2020 18:00:31 GMT" "Content-Type" => "application/json" "Transfer-Encoding" => "chunked" "Connection" => "keep-alive" "Set-Cookie" => "__cfduid=d76208080a8f8cda75657cdf957e5528c1593712830; expires=Sat, 01-Aug-20 18:00:30 GMT; path=/; domain=.pipedrive.com; HttpOnly; SameSite=Lax" "x-correlation-id" => "4fcd6f7f-3b89-4568-891f-6f45382685fa" "badi" => "Routing: us-east-1=>us-east-1; Version: c2a6; Host: bari;" "Cache-Control" => "no-cache" "Access-Control-Expose-Headers" => "X-RateLimit-Remaining, X-RateLimit-Limit, X-RateLimit-Reset" "pdtrusted-wgw-real-user-ip" => "18.230.84.218" "X-XSS-Protection" => "1; mode=block" "X-Content-Type-Options" => "nosniff" "Strict-Transport-Security" => "max-age=31536000; includeSubDomains" "Content-Encoding" => "gzip" "CF-Cache-Status" => "DYNAMIC" "cf-request-id" => "03b24901c90000d01cda0ac200000001" "Expect-CT" => "max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"" "Server" => "cloudflare" "CF-RAY" => "5aca44494bf9d01c-GRU" "alt-svc" => "h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400" ]}
But in my account, i have permission on Call Logs, when i create new App.
Why this error ?
The method of the authentication is: OAuth
Request:
Method: POST
URL: https://api.pipedrive.com/v1/callLogs/7441/recordings
Parameters: ^ array:11 [
"user_id" => "11419111"
"activity_id" => null
"subject" => "asdfasdfasdfasdfadsf"
"from_phone_number" => null
"to_phone_number" => "41992512151"
"outcome" => "connected"
"start_time" => "2020-07-02 19:33:40"
"end_time" => "2020-07-02 19:33:40"
"deal_id" => null
"person_id" => "9865"
"org_id" => null
]

Sorry guys... this is my error .. my fault... i passed wrong parameters on route API https://api.pipedrive.com/v1/callLogs/7441/recordings and get the above error...
For help somebody that have the same error, review your parameters and try again.
Thanks to Helio on PIpedrive that helps me: https://sharing.pipedrive.com/hvOebT

repo: pipedrive/client-php


text:
Wget missing despite following directions on docker-compose page?

My Install Process on Synology DSM 6
User@IPAddr:/volume1/dkr$ git clone https://github.com/pirate/ArchiveBox && cd ArchiveBox
Cloning into 'ArchiveBox'...
remote: Enumerating objects: 37, done.
remote: Counting objects: 100% (37/37), done.
remote: Compressing objects: 100% (37/37), done.
remote: Total 4755 (delta 21), reused 3 (delta 0), pack-reused 4718
Receiving objects: 100% (4755/4755), 3.75 MiB | 7.48 MiB/s, done.
Resolving deltas: 100% (3124/3124), done.

User@IPAddr:/volume1/dkr/ArchiveBox$ mkdir data && chmod 777 data

/volume1/dkr/ArchiveBox$ sudo docker-compose up -d
Password:
Creating network "archivebox_default" with the default driver
Building archivebox
Step 1/17 : FROM node:11-slim
 ---> 1f1634a1b9c0
Step 2/17 : LABEL maintainer="Nick Sweeting <archivebox-git@sweeting.me>"
 ---> Using cache
 ---> e475d59f9a18
Step 3/17 : RUN apt-get update     && apt-get install -yq --no-install-recommends         git wget curl youtube-dl gnupg2 libgconf-2-4 python3 python3-pip     && rm -rf /var/lib/apt/lists/*
 ---> Using cache
 ---> c285b80bb08c
Step 4/17 : RUN apt-get update && apt-get install -y wget --no-install-recommends     && wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -     && sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list'     && apt-get update     && apt-get install -y google-chrome-unstable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst ttf-freefont       --no-install-recommends     && rm -rf /var/lib/apt/lists/*     && rm -rf /src/*.deb
 ---> Using cache
 ---> fc7d4fb1a388
Step 5/17 : ADD https://github.com/Yelp/dumb-init/releases/download/v1.2.0/dumb-init_1.2.0_amd64 /usr/local/bin/dumb-init

 ---> 8f41f559d375
Step 6/17 : RUN chmod +x /usr/local/bin/dumb-init
 ---> Running in 3e363d2600d5
Removing intermediate container 3e363d2600d5
 ---> 7181b6a8ddb7
Step 7/17 : ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true
 ---> Running in 2be880b6f424
Removing intermediate container 2be880b6f424
 ---> e984ae3dc0f7
Step 8/17 : RUN npm i puppeteer
 ---> Running in b5116eb2af14

> puppeteer@2.0.0 install /node_modules/puppeteer
> node install.js

**INFO** Skipping Chromium download. "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" environment variable was found.
npm WARN saveError ENOENT: no such file or directory, open '/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/package.json'
npm WARN !invalid#1 No description
npm WARN !invalid#1 No repository field.
npm WARN !invalid#1 No README data
npm WARN !invalid#1 No license field.

+ puppeteer@2.0.0
added 43 packages from 22 contributors and audited 50 packages in 4.692s
found 0 vulnerabilities

Removing intermediate container b5116eb2af14
 ---> b75f1c9a10be
Step 9/17 : RUN groupadd -r pptruser && useradd -r -g pptruser -G audio,video pptruser     && mkdir -p /home/pptruser/Downloads     && chown -R pptruser:pptruser /home/pptruser     && chown -R pptruser:pptruser /node_modules
 ---> Running in 1aacf807028f
Removing intermediate container 1aacf807028f
 ---> 7ff9f381e09c
Step 10/17 : COPY . /home/pptruser/app
 ---> 83e6e5fd2558
Step 11/17 : RUN mkdir -p /data     && chown -R pptruser:pptruser /data     && ln -s /data /home/pptruser/app/archivebox/output     && ln -s /home/pptruser/app/bin/* /bin/     && ln -s /home/pptruser/app/bin/archivebox /bin/archive     && chown -R pptruser:pptruser /home/pptruser/app/archivebox
 ---> Running in f8ebfba3762a
Removing intermediate container f8ebfba3762a
 ---> eb03c7593be7
Step 12/17 : VOLUME /data
 ---> Running in 276ffa6ab135
Removing intermediate container 276ffa6ab135
 ---> 8c388a99f6ec
Step 13/17 : ENV LANG=C.UTF-8     LANGUAGE=en_US:en     LC_ALL=C.UTF-8     PYTHONIOENCODING=UTF-8     CHROME_SANDBOX=False     CHROME_BINARY=google-chrome-unstable     OUTPUT_DIR=/data
 ---> Running in 67497c78ee6d
Removing intermediate container 67497c78ee6d
 ---> d000923c6cfa
Step 14/17 : USER pptruser
 ---> Running in 2165ba6e9197
Removing intermediate container 2165ba6e9197
 ---> 1a4b71b4e2b3
Step 15/17 : WORKDIR /home/pptruser/app
 ---> Running in 8c461766a5cd
Removing intermediate container 8c461766a5cd
 ---> 4c2f3b6a4b63
Step 16/17 : ENTRYPOINT ["dumb-init", "--"]
 ---> Running in d443468d040f
Removing intermediate container d443468d040f
 ---> 723fba1ff206
Step 17/17 : CMD ["/bin/archive"]
 ---> Running in 8093f3faa0e4
Removing intermediate container 8093f3faa0e4
 ---> 1f9f3aca1d9a
Successfully built 1f9f3aca1d9a
Successfully tagged archivebox_archivebox:latest
WARNING: Image for service archivebox was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating archivebox_nginx_1      ... done
Creating archivebox_archivebox_1 ... done

Trying to Add Links
/volume1/dkr/ArchiveBox$ sudo docker-compose exec archivebox /bin/archive /data/bookmarks.html
Password:
Traceback (most recent call last):
  File "/bin/archive", line 15, in <module>
    from links import links_after_timestamp
  File "/home/pptruser/app/archivebox/links.py", line 25, in <module>
    from util import (
  File "/home/pptruser/app/archivebox/util.py", line 20, in <module>
    from config import (
  File "/home/pptruser/app/archivebox/config.py", line 77, in <module>
    WGET_AUTO_COMPRESSION = USE_WGET and WGET_BINARY and (not run([WGET_BINARY, "--compression=auto", "--help"], stdout=DEVNULL, stderr=DEVNULL).returncode)
  File "/usr/lib/python3.5/subprocess.py", line 383, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.5/subprocess.py", line 1282, in _execute_child
    raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] No such file or directory: '"wget"'

What happened to WGET? I have literally been trying to add this program for over 3 hours...

woah that super weird, never seen that happen before...
is it getting '"wget"' double-quoted somehow? maybe try adding WGET_BINARY=wget to the environment: section of the docker-compose file?

Same error with WGET_BINARY="wget" and WGET_BINARY=wget.
Tested for WGET
wget --version
GNU Wget 1.19.1 built on linux-gnu.

docker-compose.yml
version: '3'

services:
    archivebox:
        build: .   # replace this with nikisweeting/archivebox to use the docker-compose.yml file as a standalone file without avoid having to clone the repo (???)
        stdin_open: true
        tty: true
        env_file: ArchiveBox.conf
        environment:
            - USE_COLOR=False
            - SHOW_PROGRESS=False
            - FETCH_MEDIA=False
            - WGET_BINARY=wget
        volumes:
            - ./data:/data
        command: bash -c 'echo "https://github.com/pirate/ArchiveBox" | /bin/archive; tail -f /dev/null'  # archive the Github repo homepage as a starting point so the index doesn't just show an empty list to new users

    nginx:
        image: 'nginx'
        ports:
            - '8098:80'
        volumes:
            - ./etc/nginx/nginx.conf:/etc/nginx/nginx.conf
            - ./data:/var/www

Visiting the site

I ended up deleting it and starting over. I used sudo for everything Docker-related, starting from docker-compose up -d and it worked (i.e. sudo docker-compose up -d).

authors: pirate shimizurei

repo: pirate/ArchiveBox


text:
Show event animal

Show de event Animal. Dos cosas que tengo que arreglar que no pude arreglar aun, si alguien me tira algun pique se agradece.

El componente lista de eventos sea scroleable. asi la lista no sigue yendo pa abajo.
Un bug, la lista no queda limpia. cuando veo lista de eventos de un animal luego al mirar la de otro animal, la lista vieja se queda mostrandose. No se cual es problema.

Para corregir ese bug tenes que poner en el reduce de eventos que cuando escucha el evento getAnimal( SHOW_ANIMAL_PROFILE) se vacié la lista de eventos

Me salta este error cuando pido mas eventos

Todavia le falta mucho visualmente, que quede IGUAL que el diseño!

@davidgivad todos los componentes que tengan que ver con los eventos colocalos en /components/animals/events para mayor organizacion del proyecto

Esta muy Feo Visualmente el view del evento

Ponele algún margin a la descripción del evento, que la galeia quede mas linda en  la vista no pegada directo después del texto(mas margin)
Esta como forzado a enter los complementos

@davidgivad correcciones:

Pedi mas animales por vez, la primera vez q entras hay mucho espacio en blanco y podria ser ocupado con mas eventos.
Cuando cargo los eventos de un animal y luego voy a otro animal mientras esta cargando me aparecen los eventos del animal que ingrese antes(esto se soluciona haciendo que cuando desmontas el componente limpiar los eventos que tenes en el store)

authors: bernabe9 davidgivad felparodi


text:
Restructered tests to not rely on the Summary View

Removed two coverageReportGenerated() where no report is generated in the newest PIT version

@LorenzoBettini @echebbi this is the requested PR from #152, please review this if you have time.

So if I understand correctly, this PR cleans up things a bit, by removing an intermediate layer, but without changing the semantics of the test right? (Besides the last comment).

It fixes an issue which causes test to fail, if they are running longer than the SWTBotPreference.TIMEOUT, which by default is set to 5 seconds.
Also, why I reworked it in the first place, no tests break, if the pit summary view is changed in any way. Prior the html of the pit summary view was used to get the html text and parse it. If we decide to change the view, looking at synchronization I proposed or deleting the view (Editor highlighting instead of this view), all tests will remain fine. Would you delete this view currently it would break every other test which uses coverageReportGenerated.

Basically, this is not strictly required to make tests succeed or it's required for the other PRs of yours? Again, just to understand things better, NOT because I'm against it ;)

As stated above, I think it is required to have better tests and be less dependent on things which are not related with the tests at all. Also, yes it is needed for my PRs.

I now made a bigger overhaul with waiting for pit in general. RunPit now is runPitAndWaitForIt which imo makes a lot more sense, because we don't parse the console output for the result, which could change in the future with pit.
@echebbi maybe this is what you thought of in this comment.
@LorenzoBettini This is now solved with a separate call to noCoverageReportGenerated. Also this is solved.

The failures I'm seeing are related with consoleContains, which I personally dislike, because as mentioned before the output of the console can change in the future. I will try to get this check working differently.

The failures I'm seeing are related with consoleContains, which I personally dislike, because as mentioned before the output of the console can change in the future. I will try to get this check working differently.

I'm not a big fan of consoleContains either though I personally introduced that O:)
I did that when I wrote from scratch many UI tests with SWTBot (without using Cucumber, though we're still use some old code of the Cucumber steps... we'll have to get rid of Cucumber dependencies at some point and remove lots of unused testing code).
I introduced that as a first mechanism for checking whether PIT ran correctly and as expected because I did not want to use the browser in the Pit View to do that.
If we find a better way of checking the results of PIT without using any of our UI views in some specific tests then I'd be very happy. Maybe as you started to do: wait for notification from PIT and parse the results of HTML? That way, we'd be able to test that our run configurations work correctly independently from the PIT View tree and from the PIT View browser. Of course, we still need to test that the tree view works correctly (as we already do by double-clicking on some nodes and verifying that the corresponding editor is opened) and that the browser shows the expected contents. But, as I said, I agree that for verifying PIT runs we shouldn't need to use the Console (by the way, when migrating to PIT 1.6.7 those tests broke and had to be adapted to the new output). @echebbi what do you think?

[...] If we find a better way of checking the results of PIT without using any of our UI views in some specific tests then I'd be very happy. Maybe as you started to do: wait for notification from PIT and parse the results of HTML? [...]

@LorenzoBettini If you can live without the test on testsRun and testsPerMutations of the method
consoleContains(int generatedMutants, int killedMutants,             int killedPercentage,             int testsRun,             int testsPerMutations) we could easily parse them from the HTML file.

[...] If we find a better way of checking the results of PIT without using any of our UI views in some specific tests then I'd be very happy. Maybe as you started to do: wait for notification from PIT and parse the results of HTML? [...]

@LorenzoBettini If you can live without the test on testsRun and testsPerMutations of the method
consoleContains(int generatedMutants, int killedMutants, int killedPercentage, int testsRun, int testsPerMutations) we could easily parse them from the HTML file.

Yes, I think we can definitely live without them... it was just a further check I was doing at that time, but I don't think they're required to verify that we can actually run PIT

@echebbi maybe this is what you thought of in this comment.

@JKutscha Yes, mostly. I'm a bit worried by the approach though. If I understand your implementation correctly, runPitAndWaitForIt makes UI tests wait for Pitest to end running before moving on. Tests are "unblocked" when PitResultNotifier receives the results sent by PitRunnerMain. However, since views receive the results at the same time and then take some time to update, we might run into cases where the tests move on before the views are updated, leading to unexpected failures. Am I mistaken?

But, as I said, I agree that for verifying PIT runs we shouldn't need to use the Console (by the way, when migrating to PIT 1.6.7 those tests broke and had to be adapted to the new output). @echebbi what do you think?

@LorenzoBettini I agree that if we just want to make sure Pitest run and sent the expected results then we shouldn't have to read the console. Additional tests checking that Pitest correctly prints on the console could still be useful though, I don't really have a strong opinion on that.

[...] If we find a better way of checking the results of PIT without using any of our UI views in some specific tests then I'd be very happy. Maybe as you started to do: wait for notification from PIT and parse the results of HTML? [...]

@LorenzoBettini If you can live without the test on testsRun and testsPerMutations of the method
consoleContains(int generatedMutants, int killedMutants, int killedPercentage, int testsRun, int testsPerMutations) we could easily parse them from the HTML file.

Just so you know we don't have to manually parse the HTML file.
Firstly, a HTML parser is already implemented: ResultsParser which use is demonstrated in PitResultNotifier.
Secondly, PitRunnerMain sends a PitResults object when Pitest is done; this object contains all the mutations that have been detected by Pitest and we can use it to check PIT results. PitResultsNotifier already catches this object (it uses it to feed the summary view) so we should be able to retrieve it from the tests with just minor changes.

@echebbi maybe this is what you thought of in this comment.

@JKutscha Yes, mostly. I'm a bit worried by the approach though. If I understand your implementation correctly, runPitAndWaitForIt makes UI tests wait for Pitest to end running before moving on. Tests are "unblocked" when PitResultNotifier receives the results sent by PitRunnerMain. However, since views receive the results at the same time and then take some time to update, we might run into cases where the tests move on before the views are updated, leading to unexpected failures. Am I mistaken?

I think this is not unexpected and should be managed by the tests which need to wait for specific views, because otherwise we would make an approach which waits longer than it needs to. Also, we didn't do it different before. Now it is always the same and we don't wait indirectly for the tests. This approach is IMHO more straightforward and is more consistent.

Just so you know we don't have to manually parse the HTML file.

I looked into the parser and I'm not sure if this is the best way, if we could use the result object instead.

[...] Secondly, PitRunnerMain sends a PitResults object when Pitest is done; this object contains all the mutations that have been detected by Pitest and we can use it to check PIT results. PitResultsNotifier already catches this object (it uses it to feed the summary view) so we should be able to retrieve it from the tests with just minor changes.

I will try to retrieve all the necessary information from the results directly, without parsing.

I will try to retrieve all the necessary information from the results directly, without parsing.

Sadly, line coverage and mutation coverage can only be parsed. I deleted HTMLTable, because I think my approach using regex is more compact and still easy to understand.
Regarding my failed tests from the CI, I tested them all locally and they run well, but yesterday I couldn't run maven locally because of some dependency which could not be accessed. It seems this still is the case today, at least in some cases.
From my part, I think this PR is finished.
@LorenzoBettini @echebbi I kindly ask you guys to review this PR, thanks :)

@LorenzoBettini @echebbi I kindly ask you guys to review this PR, thanks :)

Thank you for your work @JKutscha :) I'll take the time to review your code today! I just have a few comments/questions beforehand.

Regarding my failed tests from the CI, I tested them all locally and they run well, but yesterday I couldn't run maven locally because of some dependency which could not be accessed. It seems this still is the case today, at least in some cases.

Indeed, I don't know what's going on but some old Eclipse p2 update sites are unavailable since yesterday. I guess that it should be fixed soon.

@echebbi maybe this is what you thought of in this comment.

@JKutscha Yes, mostly. I'm a bit worried by the approach though. If I understand your implementation correctly, runPitAndWaitForIt makes UI tests wait for Pitest to end running before moving on. Tests are "unblocked" when PitResultNotifier receives the results sent by PitRunnerMain. However, since views receive the results at the same time and then take some time to update, we might run into cases where the tests move on before the views are updated, leading to unexpected failures. Am I mistaken?

I think this is not unexpected and should be managed by the tests which need to wait for specific views, because otherwise we would make an approach which waits longer than it needs to.

Yes, tests should wait for views to be updated but in your implementation they don't, do they?

Also, we didn't do it different before.

We were waiting for the UI in PitclipseSteps::coverageReportGenerated. There's a synchronization mechanism thanks to the org.pitest.pitclipse.ui.results extension point: basically, the view sends an event when it's updated and PitSummaryView waits for it.
I'm not saying that coverageReportGenerated is the right place to wait but I believe that we should make sure that tests are paused until the corresponding view is fully updated.

Sadly, line coverage and mutation coverage can only be parsed.

I'm fine with them being parsed for now. Just for the record, in the future we may want to check how Pitest generates its HTML reports: we may be able to retrieve the coverages without having to depend on the HTML report. The corresponding class seems to be MutationHtmlReportListener.

I deleted HTMLTable, because I think my approach using regex is more compact and still easy to understand.

Once again you're starting to refactor a lot of things in a single PR :) Is there any functional reason to refactor this class? It looks like you need two new properties (generatedMutants and killedMutants) but you get them from PitResults so I don't think a rewrite was needed. If it's just a cosmetic refactor I'd prefer to have it addressed in another PR.
And by the way, if you only wanted to change the implementation, why did you removed the whole HTMLTable class? Now that getRows, getHeaders, etc. methods are in ResultsParser the code looks less clear to me.

Yes, tests should wait for views to be updated but in your implementation they don't, do they?

They kind of do, because we are using the SWTBot. The bot itself waits for things to appear. In our case is done while getting the tree, which holds the mutators int the MutationView

We were waiting for the UI in PitclipseSteps::coverageReportGenerated. There's a synchronization mechanism thanks to the org.pitest.pitclipse.ui.results extension point: basically, the view sends an event when it's updated and PitSummaryView waits for it.

You are correct, but I didn't count that because we were waiting for the PitSummaryView which currently is not tested in any way. The view we test is the MutationView and we wait there, mentioned above.

Once again you're starting to refactor a lot of things in a single PR :) Is there any functional reason to refactor this class? It looks like you need two new properties (generatedMutants and killedMutants) but you get them from PitResults so I don't think a rewrite was needed. If it's just a cosmetic refactor I'd prefer to have it addressed in another PR.

I added these new properties and wanted them to be in the summary, so the refactor was necessary. Maybe I don't understand what you mean, would you try to explain it to me differently.

And by the way, if you only wanted to change the implementation, why did you removed the whole HTMLTable class? Now that getRows, getHeaders, etc. methods are in ResultsParser the code looks less clear to me.

Maybe I should rename them, but I also could put them back to the HTMLTable class. I thought having one parser class would be more clear.

They kind of do, because we are using the SWTBot. The bot itself waits for things to appear. In our case is done while getting the tree, which holds the mutators int the MutationView

Ok, makes sense.

I added these new properties and wanted them to be in the summary, so the refactor was necessary. Maybe I don't understand what you mean, would you try to explain it to me differently.

I was talking about refactoring the way the HTML report is parsed. You replaced the existing implementation with a regex-based one; was there any need to?

I was talking about refactoring the way the HTML report is parsed. You replaced the existing implementation with a regex-based one; was there any need to?

I refactored the HTMLTable because the summary was created there and now it has the two additional fields, which aren't parsed from the HTML. Also I wanted to get all in the parser class.
The parsing inside the HTMLTable was working, but I figured if I'm already reworking parts of it, make it less code.

I refactored the HTMLTable because the summary was created there and now it has the two additional fields, which aren't parsed from the HTML.

I'm sorry, that doesn't make sense to me. Summary is created in ResultsParser and since the two additional fields aren't parsed from HTML then there's no functional need to refactor HTMLTable.

The parsing inside the HTMLTable was working, but I figured if I'm already reworking parts of it, make it less code.

Maybe, but, since it has nothing to do with decoupling the tests from the Summary view, making the change here just adds noise to your contribution. Refactoring HTMLTable brings several questions/comments;

does it bring any value?
do we really want to get rid of the HTMLTable abstraction?
regex patterns should be compiled statically instead of within a method
the getTable, getRows and getHeaders method may be refactorable as a single method
we may want additional tests to prevent regressions
etc.

and I believe that this PR already brings a lot of discussion. So if you do think that refactoring this class is worth it then please submit a new PR for it (yes, yet another one). The shorter a PR, the quicker it can be reviewed and merged :)

[...] and I believe that this PR already brings a lot of discussion. So if you do think that refactoring this class is worth it then please submit a new PR for it (yes, yet another one). The smaller a PR, the quicker it can be reviewed and merged :)

I will revert it back to the original HTMLTable.

I'm sorry, that doesn't make sense to me. Summary is created in ResultsParser and since the two additional fields aren't parsed from HTML then there's no functional need to refactor HTMLTable.

@echebbi I reverted it back now and I hope the results good.

@echebbi @LorenzoBettini IMO this PR is ready for review. I would like to get this merged, that I can work on #150 and #152.
The reason I want to move faster, is that I write my Bachelor Thesis about this work and I need to get my changes merged, that I can introduce Pitclipse in a selected group of people. My deadline isn't so long in the future, so please find some time to review, thanks :)

@LorenzoBettini can we merge?

I'm going to review it right now, in the meantime I created the companion PR https://github.com/pitest/pitclipse/pull/171 for SonarCloud analysis

OK, thanks for your answers @JKutscha and @echebbi as soon as the companion PR completes, I'm going to merge this one!

OK, thanks for your answers @JKutscha and @echebbi as soon as the companion PR completes, I'm going to merge this one!

Thanks

Thank you @JKutscha for your contribution, which is now merged!
You may want to delete this branch (using the web interface of this PR)

authors: JKutscha LorenzoBettini echebbi

repo: pitest/pitclipse


text:
Rename executables to be more automation friendly

Hi there,
At the moment the executable are called om-ARCH-VERSION, would it be possible to called them om-ARCH only? For instance instead of om-linux-3.0.0 -> om-linux
Our team tries to always keep om up-to-date by using a link like this one: https://github.com/pivotal-cf/om/releases/latest/download/om-linux-3.0.0. However, because the assent name contains the version, it doesn't really work.
Would it be a hard thing to change for the next releases?

@nodo I’m not quite sure why the version number is an issue here. Are you able to clarify why the file cannot be downloaded? The link you provided above has the version number in it.
The version name is ideal to have because if someone downloads it locally they can identify what version they downloaded.

We would like to have a link that always points to the latest version (E.g. we would love to have a link like https://github.com/pivotal-cf/om/releases/latest/download/om-linux).
Since the executable name contains the version, the link: https://github.com/pivotal-cf/om/releases/latest/download/om-linux-VERSION breaks every time  a new version of om is released. What we had before was: https://github.com/pivotal-cf/om/releases/latest/download/om-linux-2.0.1 and broke because latest is now https://github.com/pivotal-cf/om/releases/latest/download/om-linux-3.0.0.
I can see from the release history that you used to not put the version in the assets name (see here). Do you think we could go back to that?

@nodo, we cannot provide that, sorry. It is very intentional to have the version name in the binary.
We can help you find an alternative to do the same thing, though.
curl https://api.github.com/repos/pivotal-cf/om/releases/latest | jq -r '.assets | map(select(.browser_download_url | contains("linux"))) | first | .browser_download_url'

Using Github's API, we can get the latest release, and whittle down to the correct release. That should be deterministic.

authors: jtarchie nodo

repo: pivotal-cf/om


text:
Targeting UAA of a CF foundation

tl;dr, this is the same issue as https://github.com/pivotal/hammer/issues/20 except with the use-case of retrieving uaa credentials & passing commands via the uaa-cli.
Again, apologies for blowing up the issue backlog with these-- they're just ideas I felt compelled to log, and feel free to close them whenever 👍

Seems like a reasonable suggestion, my only worry is the one you touched upon in #20 that this might slightly balloon the feature set of hammer. I will definitely take a look at this though.
No need to apologise, happy to have all this input!

authors: aegershman edwardecook

repo: pivotal/hammer


text:
Plugin installation error breaking sprout-vim cookbook build

See https://travis-ci.org/pivotal-sprout/sprout-vim/builds/136839029
Potential culprit:
Error detected while processing /Users/travis/.vim/bundle/j-split/plugin/j-spli

Those warnings are (unfortunately) normal. The problem is that some of the plugins we include don't play well with getting loaded after the Vundle installation process. It's a sort of chicken-and-egg problem since Vundle runs within Vim and also modifies the vim-config.
If anyone knows a way to either send Return once Vundle finishes, or to silence its warnings, then installing things in an automated fashion will be much easier.

I don't have enough experience with vim to contribute much but perhaps @luan has some tips?

I just fixed it by forking the plugins that had problems and improving the install script to be non-blocking. I triggered a rebuild of sprout-vim at https://travis-ci.org/pivotal-sprout/sprout-vim/builds/136845025 so let's see how that turns out. Should be better overall!

See 48ab11862e4841ef33db0d6b883660522aca2fd0...31a8e091739a8b7da64d73fdfb5228b90794631a for more details.

@nertzy - it looks like that got us past the error updating the vim plugins, thanks!

Feel free to close

authors: aramprice nertzy

repo: pivotal/vim-config


text:
Update plenticore.js

Höchstmöglicher Wert auf 38000 geändert. Das ist der höchste Wert den man im Wechselrichter eintragen kann.

Hallo @StrathCole,
Hallo @pixcept,
aktuell weiß ich gar nicht, wer die Hoheit über den Adapter hat.
Dieser Pull Request wartet schon eine Zeit auf seinen Merge und wäre vermutlich für mehrere Leute nützlich (z.B. für mich :-)). Kann bei Gelegenheit jemand einen Blick darauf werfen und ihn übernehmen?

Hallo @PastCoder .
Auf absehbare Zeit wird wohl nicht viel Arbeit hier fließen können. Wenn jemand Interesse hat, den Adapter zu übernehmen, wäre das kein Problem.

authors: PastCoder earl80 pixcept


text:
Drop support for "any page" target

I had implemented the any page target to ensure that the fastest target could respond. Unfortunately further logic around this make handling this complicated, especially #77.

Fixes https://github.com/pixiebrix/pixiebrix-extension/issues/4078

Replaced by #82

The fix was easy

repo: pixiebrix/webext-messenger


text:
Pixi-display - worth using for simple depth sorting?

Is pixi-display recommended to use for basic z-index management?
In my case I have a simple tile-engine where I need to handle z-index for the game character.
Similar to this http://labs.phaser.io/view.html?src=src\depth%20sorting\Depth%20Sorting.js
The charater is only one image (no shadows etc).
I understand that pixi-display has a lot of clever features for handling z-index.  But I am wondering if it worth using for more simple depth sorting as the one above.
My own idea was just to keep all displayobjects in a array and sort them on yPos and then re-add them to the displaylist on each update.

If you dont need to sort through the tree, you can use easier approach: https://github.com/pixijs/pixi-display/wiki#how-to-not-use-pixi-display
As you see, I favor gradual approach.

Ahh, thanks I missed the wiki.
Then I go for sorting on each update and re-adding them to the list.

I'm sure you will figure out the best sorting algorithm for your game. When you actually need to sort through the tree, give me your cirrent algorithm and i'll tell you how to embed it into pixi-display.

In my case the displaylist is really shallow.
I just have one object (this.display) where I keep everything.
Below my render method, in the end I have added the sorting stuff (not tested yet).
Don't know if .sort is bad for performance.
render() {
  const startCol = Math.floor(this.cameraX / MapConfig.tileSize.width);
  const startRow = Math.floor(this.cameraY / MapConfig.tileSize.height);
  const endCol = Math.ceil(startCol + (this.cameraWidth / MapConfig.tileSize.width));
  const endRow = Math.ceil(startRow + (this.cameraHeight / MapConfig.tileSize.height));
  const offsetX = -this.cameraX + startCol * MapConfig.tileSize.width;
  const offsetY = -this.cameraY + startRow * MapConfig.tileSize.height;
  // Mark previously moved items.
  for (let i = this.activeItems.length - 1; i >= 0; i--) {
    this.activeItems[i].remove = true;
  }
  // Compensate for none tiled layers.
  this.playerContainer.x = -Math.abs(this.cameraX);
  this.playerContainer.y = -Math.abs(this.cameraY);
  // Move items that are visible
  for (let c = startCol; c <= endCol; c++) {
    for (let r = startRow; r <= endRow; r++) {
      const x = (c - startCol) * MapConfig.tileSize.width + offsetX;
      const y = (r - startRow) * MapConfig.tileSize.height + offsetY;
      // If item has been moved previously
      const item = this.itemList[`${c}_${r}`];
      if (item) {
        item.x = x;
        item.y = y;
        item.remove = false;
      } else {
        this.addItem(c, r, { x, y }, MapConfig.tileSize);
      }
    }
  }
  // Remove items that has not moved
  for (let i = this.activeItems.length - 1; i >= 0; i--) {
    if (this.activeItems[i].remove) {
      this.removeItem(i);
    }
  }
  // Depth sorting
  this.activeItems.sort((obj1, obj2) => obj1.y - obj2.y);
  for (let i = this.activeItems.length - 1; i >= 0; i--) {
    this.display.addChild(this.activeItems[i]);
  }
}

That page was updated. I suggest to look at new version, it has faster sorting.

authors: Pandan ivanpopelyshev

repo: pixijs/pixi-display


text:
Bug: Text color doesn't work

Current Behavior
Applying color to text doesn't seem to work. In my case, I was trying to set my text color to white using the fill attribute, with the value either "0xfff" or "white".
Another issue is that when fill is an array, it only accepts numbers
Expected Behavior
Text should render color as the setting
Steps to Reproduce
Here is my sample code written in Typescript:
const nodeTextStyle = new TextStyle({
    fontSize: 20,
    fontWeight: '400',
    fill: 'pink'
  });

...
...
...
<Text text= {node.type} x = {0} y={60} anchor={0.5} style={nodeTextStyle}/>
...

Here is the result:

Environment

@pixi/react version: ^7.1.2
pixi.js version: ^8.1.0
React version: 18.0.0
ReactDOM version: 18.0.0
Browser & Version: Chrome 124.0.6367.118
OS & Version: MacOS Sonoma 14.4.1

Possible Solution
No response
Additional Information
No response

Work around for me:
<Text         text={Some text}         x={10}         y={10}         style={           new PIXI.TextStyle({             fontSize: 24,             fill: 'white', // doesnt work             // @ts-ignore             _fill: ['#ffffff', '#00ff99'], // work pretty well           })         }       />

The workaround works well for development, but it has issues when compiling, making it unfeasible to use in production.
 Checking validity of types  .Failed to compile.
./src/components/Galeria/BallTree/index.tsx:22:5
Type error: Object literal may only specify known properties, but '_fill'
does not exist in type 'Partial<TextStyleOptions>'. Did you mean to write
'fill'?

Stack:
@pixi/react": "^7.1.2",
"next": "14.2.14",
"pixi.js": "^8.6.4",
"react": "^18.2.0",

authors: a-pedraza kilisniki tphamz

repo: pixijs/pixi-react


text:
Feature request for React renderer

I really love Pixi for it's good performance and the fallback to context2d when it can't use webgl. I'm using almost React to everything at the moment. I can't live without declarative/functional programming but I would really want a solid renderer for Pixi for React. Then I would probably use Pixi a lot more 😄
Right now there is one project with Pixi renderer for React (https://github.com/Izzimach/react-pixi). The problem is that is backed by one active developer (love the guy for trying) but the documentation is lacking and the task seems to big for one person. There is also some API issues with "pure" components. I would be super happy to see a bigger organisation that have the strength to build someone like this. Not just a renderer but all the documentation that is needed as well.
Here are some examples of bad API decisions from mentioned project:
<Text anchor={new PIXI.Point(0.5,0)} />

Should have implemented like below. Not create instances (only use primitive values as strings/numbers/booleans) when rendering. To be able to create "PureComponents".
<Text anchorX{0.5} anchorY={0} />

Also missing out some simple feature like onDimensionChange on native components that might change size if some prop is changed. If you trying to build a button component and the text change you probably have to update the rectangle etc if the dimension changes and you want to know how big is the text on initial render.
// My proposal
const Button = ({ padding, width, height, value, onDimensionChange, ...props }) => (
  <Container {...props}>
    <Rectangle width={width + padding} height={height + padding} />
    <Text x={padding / 2} y={padding / 2} value={value} onDimensionChange={onDimensionChange} />
  </Container>
);

Would be awesome to not use <Text /> instead use lowercased <text /> so the native components is built into the React renderer. So you don't have to import { Text } from 'react-pixi-renderer'; etc.
const test1 = <Text />;
// JSX compiled
React.createElement(Text, null);

const test2 = <text />;
// JSX compiled
React.createElement("text", null);

If this could be combined somehow with react-dom. It will blow my mind!
EDIT: Maybe it's better to import components so it's can be combined with react-dom.

More resources about the subject. To write custom renderers.
https://github.com/iamdustan/tiny-react-renderer

This is not something that we are likely to support in the core, I don't think we can afford to spend time officially supporting this and still maintain the feature set we want to give for everyone.

authors: EloB englercj


text:
How to create a line segment that can change the endpoint coordinates ?

const lineSegment = new PIXI.Graphics()
lineSegment.lineStyle(1, 0xff0000, 1)
lineSegment.moveTo(0, 0)
lineSegment.lineTo(50, 50)

Now I can create a line segment with the above code, but I can't change the coordinates of one end point of the line segment in the future.
In fact, I tried to show the direction and distance of the robot in real time with a movable line segment, but I didn't find the relevant implementation.
I look forward to your help. Thank you.

Graphics usual way:

clear
fill with whatever you want

There's a technique how to change coords and ask pixi to re-calculate vertex buffers graphics.geometry.invalidate()  , but its not for newbies and requires extensive usage of chrome devtools or reading PixiJS sources. Here's previous issue about that: https://github.com/pixijs/pixi.js/issues/6529
Are you sure you want to go that way?
Why not just use "lineSegment.rotation = ... " ?

Ivan’s answer here is good, clear and redraw the line. Hope that answers your question sufficiently. Closing issue.

authors: bigtimebuddy elewen ivanpopelyshev


text:
Objects with filters are rendered in lower quality if the renderer's resolution is greater than 1

Current Behavior
If the app's (or renderer's) resolution is set to anything other than 1, e.g. if window.devicePixelRatio is used and greater than 1, then filters with (default) resolution 1, render to textures of relatively lower resolution. Consequently the visual quality degrades as soon as a filter is applied and the filter's resolution isn't adjusted to the renderer's resolution. This behavior is best shown by the demo below.

Expected Behavior
The filter's resolution should be relative to renderer's/render texture's resolution. Manually setting the resolution of every filter used to the same resolution as the renderer doesn't seem like the right way to go, neither solving the problem by changing the settings globally like this, which at the moment is the best way to do it as far as I can tell:
PIXI.settings.RESOLUTION = window.devicePixelRatio;
PIXI.settings.FILTER_RESOLUTION = window.devicePixelRatio;

Possible Solution
After the resolution is determined that is used for the filters in FilterSystem.push(), we need to multiply it by the renderer's/render texture's resolution.
if (renderer.current) {
    // Rendering to a texture...
    const baseTexture = renderer.current.baseTexture as BaseRenderTexture;
    resolution *= baseTexture.resolution;
} else {
    // Rendering to the screen...
    resolution *= renderer.resolution;
}

I haven't tested it yet, but it seems like this would work.
Steps to Reproduce
Check out the demo here. To see it, you have to zoom in of course. Zoom in as far as possible and click Refresh.
Environment

pixi.js version: 5.3.3+
Browser & Version: Chrome 87, Firefox 83
OS & Version: Windows 10
Running Example: https://www.pixiplayground.com/#/edit/KXGbyIOJzQBv7MQVT_8QT

The linked change does what I intended,  but also it uncovered another bug I'm going to report separately.


text:
Momentum pump does not generate power from falling mobs immune to fall damage

Such as the chicken or iron golem.

Intended

authors: Da-Technomancer pixlepix

repo: pixlepix/Aura-Cascade


text:
[BUG] Logout problem

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
The logout screen when u get banned for 1 day or more bugs out and u cant click it and basically covers the client and u can press log in and whatever but u cant see it. for more info on it add me on discord eggoofficial

As per the preliminary instructions, did you check if this only happened with Bloxstrap? https://github.com/pizzaboxer/bloxstrap/wiki/Switching-between-Roblox-and-Bloxstrap

Issue has been awaiting clarification for over a month, closing as stale. If you have anything further to add, just respond and I'll reopen.

Im also having the same problems, and it's only happening with bloxstrap.

I fixed it; this is how. I opened the bloxstrap menu, went down to 'Behavior', and turned on Force Roblox Reinstallation. I went on the Roblox site, opened a game, then, after installing, opened the Roblox player, logged out from there, then opened the bloxstrap, and it should ask you to sign up or login.

authors: Returnofxuqin TheEmoBoy9887 pizzaboxer

repo: pizzaboxer/bloxstrap


text:
low fps

I get lower fps, but I'm not sure why, I don't use any necessary fastflags.

Let me see your FastFlag configuration just to be sure.

max fps: 120
lightning technology: chosen by game
escape menu: default
hide GUIs: on
old materials: off
rendering mode: direct3D 11
21 graphics quality selector: off

What's your average framerate with and without?

90-120

but i dont know why i get lower fps when lauching the game from the browser

Answer the question, I want to get an idea of how much performance you're actually losing, and if it's even caused by Bloxstrap which I doubt it is.

Answer the question, I want to get an idea of how much performance you're actually losing, and if it's even caused by Bloxstrap which I doubt it is.

okay, 5 mins

when i have these all of 'em off then i get 140-200 fps on 5 graphic bar and 130-150 with full graphic quality.
and with direct3d 11 i get 90-140

Only happens when you change your rendering mode to Direct3D?

idrk, i issued that camera delay bug so now idk if this causes, but yes, mostly it takes my fps down

Roblox should always be using Direct3D 11 by default if your rendering mode is set to automatic. Set it to automatic again, launch Roblox, and send me the latest log file from %localappdata%\Roblox\logs.

0.586.0.5860000_20230722T121235Z_Player_F5876_last.log

And you're absolutely sure there's a difference in framerates between force-enabling Direct3D 11 and having it automatically chosen?

yes, but idk why but now i have 60-80

does the fullscreen optimizations give more fps after enabling that in?

i'll try the force again

Anyway, I'll close this since it's clear by now that this isn't a problem with Bloxstrap.

it fixed, it was because roblox didnt closed


text:
Server halts after errors

When I zoom in quickly I get errors. For me these are 'acceptable' if the server would continue working after these, but it halts and becomes unresponsive (not after all errors, but it is common). Anything that can be done about that maybe? When I break with Ctrl+C and restart the server everything is working again.
Example of server output after which it frooze:

2017-06-29 05:57:57.946 INFO GET /customlayer/3/3/3.pbf
2017-06-29 05:57:57.949 INFO GET /customlayer/3/4/2.pbf
2017-06-29 05:57:58.446 WARN Get V4(92.110.243.159:48004) AbsolutePath("/customlayer/3/3/3.pbf") "Failed to send: Connection reset by peer (os error 104)" None
Error: Failed to send: Connection reset by peer (os error 104)
2017-06-29 05:57:58.657 INFO GET /customlayer/5/15/12.pbf
2017-06-29 05:57:58.960 INFO GET /customlayer/6/31/23.pbf
2017-06-29 05:57:58.961 INFO GET /customlayer/6/31/24.pbf
2017-06-29 06:13:53.458 WARN Get V4(92.110.243.159:46614) AbsolutePath("/customlayer/3/3/3.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:13:53.459 INFO GET /customlayer/7/62/48.pbf
2017-06-29 06:14:14.450 WARN Get V4(92.110.243.159:48040) AbsolutePath("/customlayer/5/15/12.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:14:14.450 INFO GET /customlayer/7/62/47.pbf
2017-06-29 06:14:14.451 INFO GET /customlayer/8/125/96.pbf
2017-06-29 06:14:43.122 WARN Get V4(92.110.243.159:48054) AbsolutePath("/customlayer/6/31/24.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:14:43.123 INFO GET /customlayer/8/125/97.pbf
2017-06-29 06:14:43.123 INFO GET /customlayer/9/250/192.pbf
2017-06-29 06:14:44.658 WARN Get V4(92.110.243.159:48002) AbsolutePath("/customlayer/3/4/2.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:14:44.659 INFO GET /customlayer/9/250/193.pbf
2017-06-29 06:30:21.116 WARN Get V4(92.110.243.159:48072) AbsolutePath("/customlayer/7/62/48.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:30:21.127 INFO GET /customlayer/9/251/192.pbf
2017-06-29 06:30:21.138 INFO GET /customlayer/9/251/193.pbf
2017-06-29 06:30:21.140 INFO GET /customlayer/10/501/385.pbf
2017-06-29 06:30:42.099 WARN Get V4(92.110.243.159:48088) AbsolutePath("/customlayer/8/125/96.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:30:42.103 INFO GET /customlayer/10/501/386.pbf
2017-06-29 06:31:10.770 WARN Get V4(92.110.243.159:48104) AbsolutePath("/customlayer/9/250/192.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:31:10.772 INFO GET /customlayer/11/1002/772.pbf
2017-06-29 06:31:12.306 WARN Get V4(92.110.243.159:48106) AbsolutePath("/customlayer/9/250/193.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:31:12.306 INFO GET /customlayer/11/1003/772.pbf

Looks like all threads are blocked because of the synchronous http server.This will be solved with hyper 0.11 (https://github.com/nickel-org/nickel.rs/issues/402). In the meantime you can only increase the number of threads (command line or config). For production use it is strongly recomended to put a web server like Nginx or Apache in front of t-rex.

authors: musicformellons pka

repo: pka/t-rex


text:
refactor: replace set-output with GITHUB_OUTPUT environment files writes

This PR replaces set-output calls with GITHUB_OUTPUT environment files writes as described here:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
I run the CI tests on a local PR and they seem to be green. I expected to have to review this test file, but i can't see how it gets actually executed :)
Closes #56

@dominykas looks like we have lots of approvals, can you merge this PR?

Thanks! Released as 0.1.7

I don't think this set-output issue is resolved entirely. See https://github.com/nodejs/citgm/actions/runs/6244928993/job/16965961626?pr=959 (expand the "Prepare the matrix" step). These appear to be the result of calls to ActionsCore.setOutput().

You can also see the set-output calls by running node index.js from the .github/actions/prepare-node-test-matrix-action directory.

Thanks, I'll take a look next week if nobody else does before that.

#69 makes the warnings go away.

authors: Trott dominykas simoneb toomuchdesign

repo: pkgjs/action


text:
MathJax_SVG_glyphs missing xmlns

mathjax-node-page outputs a big svg element at the very end of an input (X)HTML file that contains a defs with @id=MathJax_SVG_glyphs. The svg does not have an @xmlns attribute set, and this seems to be preventing browsers (or ePub readers, which is my ultimate output destination) from being able to use the definitions. If I add xmlns="http://www.w3.org/2000/svg" to that final svg element then I get the desired result. I can't figure out what adds that svg, so I'm not able to submit a pull request on my own to fix the problem, unfortunately.

Thanks for the report. I remember running into the same problem elsewhere and vaguely recollect a jsdom serialization issue. Will have to find time to check.
FWIW be sure to test support for a global SVG element in epub3 reading systems -- some RSs do not handle them well (though my latest tests indicate that all major RSs are ok now).

Having good luck so far with the major ones. Rasterization for Kindle is a different ballgame, unfortunately. (This is all work for the PreTeXt project, btw. Right now it's easy to find the one svg missing its @xmlns and add it using sed, but it will be great to have this fixed when you have a chance to find the source of the problem.)

@mitchkeller I cannot reproduce this on master. Could you give it a try (the code on master has not yet been released).

Oh, nevermind. I see it.

It looks like a jsdom serialization issue. Adding the namespace as an attribute seems to work.

authors: mitchkeller pkra

repo: pkra/mathjax-node-page


text:
After installation Target class [App\Policies\RolePolicy] does not exist

Prerequisites

[x] Able to reproduce the behaviour outside of your code, the problem is isolated to Nova Permissions.
[x] Checked that your issue isn't already filed.
[x] Checked if no PR was submitted that fixes this problem.

Versions

PHP version: 7.4.20
Laravel version: 7.30.4
Nova version: 3.19.1
Package version: ^2.1

Description
I have installed the module following the whole procedure but once I reload the page the following error appears:
Illuminate\Contracts\Container\BindingResolutionException
Target class [App\Policies\RolePolicy] does not exist. (View: /var/www/nova/resources/views/layout.blade.php)

I suppose the error is in

namespace App\Providers;

use App\Policies\UserPolicy;
use App\User;
use App\Models\InfoWeb\Customer as InfoWebCustomer;
use App\Policies\InfoWebCustomerPolicy;
use Illuminate\Foundation\Support\Providers\AuthServiceProvider as ServiceProvider;
use Illuminate\Support\Facades\Gate;
use Pktharindu\NovaPermissions\Traits\ValidatesPermissions;

class AuthServiceProvider extends ServiceProvider
{
    use ValidatesPermissions;
    /**
     * The policy mappings for the application.
     *
     * @var array
     */
    protected $policies = [
        User::class => UserPolicy::class,
        InfoWebCustomer::class => InfoWebCustomerPolicy::class,
        \Pktharindu\NovaPermissions\Role::class => \App\Policies\RolePolicy::class,
    ];

    /**
     * Register any authentication / authorization services.
     *
     * @return void
     */
    public function boot()
    {
        $this->registerPolicies();

        foreach (config('nova-permissions.permissions') as $key => $permissions) {
            Gate::define($key, function (User $user) use ($key) {
                if ($this->nobodyHasAccess($key)) {
                    return true;
                }

                return $user->hasPermissionTo($key);
            });
        }
    }
}

\Pktharindu\NovaPermissions\Role::class => \App\Policies\RolePolicy::class, -> the `RolePolicy::classics missing
Steps to Reproduce
Install following the procedure
Expected behavior:
No errors after following the installation guide
Actual behavior:
Missing App\Policies\RolePolicy
Additional Information

The RolePolicy::class doesn't come with the package. So you need to create your own using php artisan make:policy RolePolicy.
Let me know if that doesn't work. 🙂

@pktharindu I've created my own RolePolicy::class and it's working fine.
Just as suggestion, please consider to edit the installation guide with php artisan make:policy RolePolicy instruction or additional it by default in the package. This will help users!
Thanks
Riccardo

Thanks! Actually, it is already there in the notes here: https://github.com/pktharindu/nova-permissions#create-a-model-policy 🙂

@pktharindu I've stumbled across the same issue as @RiccardoFrancescato, perhaps you'd consider modifying the readme so that the "Create a Model Policy" section comes before "A new resource called Roles will appear in your Nova app after installing this package."?
As I am new to Nova, I was following the instructions step by step, and when I read that "A new resource called Roles will appear in your Nova app after installing this package.", I immediately refreshed my page, only to fine the error mentioned above...

I just added that bit. Thank you!

repo: pktharindu/nova-permissions


text:
use a python3 approach please

My application is failing because of this

Hey @tousif101, thanks for that.
This would need to work on both python2 and python3. What do you think of the following solutions?

https://stackoverflow.com/a/7321970/1515819
https://stackoverflow.com/a/31687067/1515819

please also make sure the checks are passing

I think the idea makes sense but due to inactivity I'm closing it, feel free to reopen

repo: plamere/spotipy


text:
Remove aptitude from Ansible playbooks

Enforce ansible >= 2.9 in doc

[x] Add / update the documentation

This should fix #149.

Thanks!

:tada:

authors: jtpio pierrepo

repo: plasmabio/plasmabio


text:
Incompatible with Atom 1.39 beta 10 and higher - Error when opening terminal

[ ] I have reset Atom to defaults prior to submitting report.
[x] I have not reset Atom to defaults prior to submitting report.

Description
I have upgraded to latest Atom version and getting this error message now:

Steps to reproduce

Click View -> Terminal -> New Terminal Window

Expected behavior:
Terminal works
Actual behavior:
Terminal does not work.
I'm getting error message inside terminal window:
For more info check out the docs: https://nuclide.io/docs/features/terminal
Error starting process:
Error: The specified module could not be found.
\\?\C:\Users\xxx\.atom\packages\atom-ide-ui\node_modules\nuclide-prebuilt-libs\pty\build\pty-node-v64-win32-x64\pty.node

Reproduces how often:  100%
Versions

> atom --version
Atom    : 1.39.0-beta1
Electron: 3.1.10
Chrome  : 66.0.3359.181
Node    : 10.2.0

> apm --version
apm  2.2.4
npm  6.2.0
node 8.9.3 x64
atom 1.39.0-beta1
python 3.8.0b1
git 2.8.1.windows.1
visual studio 2015

OS name and version: Win 10 x64
Platformio-ide-terminal version: 2.9.1

Hi @Zireael and thank you for reaching out with this issue report.
There are two things of note I see in your report.

Your version of Atom 1.39.0-beta10 with Node version 10.2.0 which requires

https://github.com/lgeiger/node-abi/blob/79d73c3b676add0bd63899f021dabfa7e240be44/index.js#L57
Please test with the stable version of Atom. Because of (2)

The error in your terminal seems unrelated to this project.

This is because node-pty-prebuilt 0.7.6 is latest release with Windows binaries is only support Node up to version 9.0.0  and electron up to 1.8.0
As such marked this as external because there are no Windows node-pty-prebuilt with Windows binaries that support higher Node/Electron versions.
Please make a comment in related issue that would solve this report @ https://github.com/daviwil/node-pty-prebuilt/issues/14
When node-pty-prebuilt 0.8.1 or newer comes out with Windows binaries, then you need to uninstall/reinstall platformio-ide-terminal in the beta versions of Atom.

@Zireael Any feedback after my reply?

Please test with the stable version of Atom. Because of (2)

I have added a post in the linked project having the same issue, but reverting to the latest stable version hasn't worked for me yet and is giving me the same error. Is there anything I need to do before running the latest production installer to reset everything and make that work?
Cheer, Jos

Is there anything I need to do before running the latest production installer to reset everything and make that work

@jvanderzande
Understand that simple stating your issue is not enough to even guess what may be the issue.
If you are looking for help, you must fill in our issue template fully and including any extra details at the bottom like screenshots or error logs or anything else helpful like a list of 3rd party antivirus/softwares you have installed. (McAffee is known to interfere with Atom for instance).
This way we can have actionable information and try to see if there is anything we can do to, help us, help you better.
Thanks for understanding.

I didn't want to create yet another issue, as I the same issue as reported here, just reverting back to the old production still doesn't download the platformio-ide-terminal older version and it still seems to point the Beta I had installed when the problem started. In the meantime I found some remaining old files in directory "C:\Users\xxxxxx\AppData\Roaming\Atom" which I renamed after which the next start of Atom everything worked fine and that directory was regenerated.
Hope this helps other having this issue and thanks for your support.

I didn't want to create yet another issue

No need, just replying to the comment in this issue with the template filed in, is infinitely more helpful to someone trying to help you, than just a me too report.

just reverting back to the old production still doesn't download the platformio-ide-terminal older version

I think you meant to write Atom, ;)

and it still seems to point the Beta I had installed when the problem started. In the meantime I found some remaining old files in directory "C:\Users\xxxxxx\AppData\Roaming\Atom"

Atom documentation is what you would have wanted, particularly the part about resetting Atom to defaults which is what you ended up doing in a roundabout way.

which I renamed after which the next start of Atom everything worked fine and that directory was regenerated.

Yes, its recreated (it has to), but with the production version of Atom files instead of your beta file contents which like you aptly found out, fouling up the intended downgrade.

Hope this helps other having this issue and thanks for your support.

Hope is a good choice of words, so do I. And youre welcome.
On a second note, node-pty-prebuilt developer/maintainer @daviwil GtHub page indicates a change of employer, if this will affect that project IDK, This project relies on that project, so you/others may want to find out how to compile the required binaries for Windows/ when Atom production node/electron versions reach unsupported ABI we know will break as reported here. That or find another Terminal project for Atom or move to VScode.

1.39.0 is out and platformio-ide-terminal still won't install (at least on macOS). Are there any fixes in sight?

@birnstiel nope, the issue is node-pty-prebuilt has no binaries for the new node/electron for Windows and macOS.
You can try (read from that comment and below) this https://github.com/platformio/platformio-atom-ide-terminal/issues/707#issuecomment-514454289
Failing that we are royally stuffed.

@the-j0k3r Adding a log file for this issue, only if it helps. Though as you stated, I understand there isn't an immediate fix. BTW #707 (Comment) helps!
2019-07-24T14_40_56_779Z-debug.log

@clair513 logs wont help, we know what the issue is in this case. But Im very happy to hear that that workaround works.
Take care.

Same error occured to me now.
When I upgrade to Atom 1.39.0, platformio-ide-terminal failed to start...

@chd1998
See https://github.com/platformio/platformio-atom-ide-terminal/issues/707#issuecomment-514634895 for a possible workaround

Duplicate of https://github.com/platformio/platformio-atom-ide-terminal/issues/707

Please upgrade to https://github.com/platformio/platformio-atom-ide-terminal/releases/tag/v2.9.2

sadly already broken reports
https://github.com/platformio/platformio-atom-ide-terminal/issues/755

repo: platformio/platformio-atom-ide-terminal


text:
It keeps loading the terminal 1.47.0-nightly3

Versions

> atom --version
Atom    : 1.47.0-nightly3
Electron: 5.0.13
Chrome  : 73.0.3683.121
Node    : 12.0.0

> apm --version
apm  2.4.3
npm  6.2.0
node 10.2.1 x64
atom 1.45.0
python 3.7.6
git 2.25.1

OS name and version: Fedora Workstation 31
Platformio-ide-terminal version: 2.10.0
Additional Information

It keeps loading the terminal:

Hi,
I have already seen formal Issues regarding this "Package". However the resolution suggestions posted are not perfect for everyone.
Can you please assist the resolution or guide us to the appropriate route?
Cheers,
Norbi

How can I validate it?

I have supposed you have some work around or  recommendation.

authors: Stenfrank stnorbi