text:
Help us Improve Traefik; Take the Community Survey! (~5 min)

We are conducting the annual Traefik Community Survey and we would love to hear from you!  1 to 2 times a year we conduct a survey to look for how cloud-native networking is changing, what direction you want us to take the product in, and how we can improve your experience.
The first half of this survey is generally about Cloud-native networking.  The second half is how we can improve the community, docs, and other services.
Take the survey to tell us how to best serve you and you can win one of over 30 prizes worth up to $250.

Mhh, the survey is closed as of now. Was this intentional after 9 days?

Yes, We ran the survey for 3 weeks.  I am sorry for not closing this comment earlier--it was not on my checklist!

authors: bryanpedini tfny

repo: traefik/traefik


text:
Fix build of MaasCore, MaasComponents & MaasTheme

Previously the project would not build when opening MaasCore/Package.swift.

This should be covered by #97

This should be covered by #97

source: gharchive/pull-request

authors: Ignelios justasm

repo: trafi/maas-components

license_type: permissive

license_source: github-api


text:
Updated Wargames List

Inserted Solidified. More information with @fabiohild

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

authors: CLAassistant hanelore

repo: trailofbits/awesome-ethereum-security


text:
Default to production date, when available.

For records with a 'p' date_type, default to the second date (date of production). This is particularly useful for video/film resources where users will be trying to narrow results by release date, not the date the media carrier was produced.

Thanks @MrDys! Merging; will go into next release.

authors: MrDys billdueber

repo: traject-project/traject

license: MIT


text:
🛑 Matrix Chat WebUI is down

In ba127b8, Matrix Chat WebUI (https://chat.langstadlinger.eu) was down:

HTTP code: 521
Response time: 195 ms

Resolved: Matrix Chat WebUI is back up in 3ba2ac8.

source: gharchive/issue

repo: traktuner/status


text:
🐛 Expose exceptions raised by other middlewares and app code

🐛 Expose exceptions raised by other middlewares and app code
It seems the traceback for other exceptions is currently hidden. This could fix/related to: https://github.com/trallnag/prometheus-fastapi-instrumentator/issues/108
It seems it could also be related to: https://github.com/encode/starlette/issues/1634

The problem is the fact that the implementation is a BaseHTTPMiddleware. 😞

I'll see if I can finish https://github.com/trallnag/prometheus-fastapi-instrumentator/pull/23 ...

This was covered/included/handled by https://github.com/trallnag/prometheus-fastapi-instrumentator/pull/139, so this PR can be closed now. 😎 🔥

authors: Kludex tiangolo

license: ISC


text:
New view states:

Related Issues

links https://transcend.height.app/T-20520
links https://transcend.height.app/T-20359
links https://transcend.height.app/T-20447

I could use some help styling DoNotSellNotice, and getting confirmation that we want to trust that messages are pre-sanitized.
New states:
DoNotSellExplainer

PrivacyPolicyNotice

QuickOptions3

ben pushed to repo, and we synced offline. will get another sign off in main repo before this is deployed

repo: transcend-io/consent-manager-ui


text:
[ MB-16172 ] Payment service item review should show same information as SIT Dashboard

Jira ticket
Summary
This PR changes the calculations in payment_request/payment_request_shipments_sit_balance.go to utilize the functions in shipment_sit_status.go that calculate  totalSITDaysAuthorized, totalSITDaysRemaining, and totalSITEndDate.
Here is a link to how to replicate the issue: https://dp3.atlassian.net/wiki/spaces/~62dff422bc2c449f3d9403fd/pages/2213412919/MB-16172+notes#How-to-replicate-the-issue
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.
Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Take an approved move and create a SIT service item. The bug in staging is seen on a Destination SIT service item, but origin should cause the same bug. I used move code SITEXT. It already has a SIT extension requested and origin SIT service items, so for this one you would want to create Destination SIT service items.
Go in as a TOO and approve those service items.
Using Postman or in the prime simulator, create multiple payment requests for the DDASIT service item. Make sure you have non overlapping dates. Here is what that looks like in Postman:

Log in as the TOO and view the SIT Dashboard (on the Move task order tab). This is what you will use for comparison in the next step. Note the total days remaining and the sit authorized end date:

Log in as a TIO and go to the move in question. There should be multiple review service items buttons.

For each review button you click, you will view a different payment request. The Authorized remaining days and the end date should now match the information from the SIT Dashboard.

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 36e677ee6ce80e6dc569614bf46d70041d0cebe2

The tests look good to me at a high level. There are some details, that aren't clear to me. Could you provide some context for the following changes:

the removal of the last test in pkg/services/payment_request/payment_request_shipments_sit_balance_test.go. Is there another test that covers something similar or is there a different reason that this is no longer needed.
It appears as though the structure of the setup for some of these tests have changed to more accurately reflect how moves are actually created in actual usage, is there something that made these change required?

@ronaktruss
Answer to Question 1)
I meant to include a reason as to why I removed that test in the description of the PR. My apologies. That test was testing the days authorized when the field SITDaysAllowance is not set on the shipment object is not set. I switched to utilizing the CalculateShipmentSITAllowance in shipment_sit_status.go. This does not utilize the SITDaysAllowance field and instead calculates the allowance based off of the entitlement plus any SIT extensions requested. Since we are not utilizing that field any more, I removed the test.
Answer to Question 2)
The test scenarios do need to be more reflective of how SIT services items would be created in actual use cases. This is due to the following: The payment request SIT balances are calculated when reviewing payment requests made for DDASIT and DOASIT (the additional days SIT) service items. Before these calculations were done using information from the shipment and the D*ASIT service item. However, the calculations done in shipment_sit_status.go based off of approved DOPSIT and DDDSIT (delivery SIT) service items, since these service items will have the most accurate entry and departure dates. You can see that here.. Thus it is important that both the additional days and the delivery service items are present when creating test scenarios.

@ronaktruss I made changes to show 'Expired' instead of negative days.

authors: mmayo-truss robot-mymove

repo: transcom/mymove


text:
MB-14537 factory.BuildTariff400ngZip3 added as new version of testdatagen.MakeTariff400ngZip3

Jira ticket for this change
Summary
This ticket adds a factory package with first function BuildTariff400ngZip3 intended to be an eventual replacement for testdatagen.

Created BuildTariff400ngZip3 and shared functions
Created tests for all of those.
Replaced all makeTariff400ngZip3 and makeDefaultTariff400ngZip3calls

Setup to Run Your Code
make server_test should be enough.
Frontend

No frontend changes

Backend

[x] Code follows the guidelines for Logging
[x] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

No schema changes

Messages

:book:
:link: MB-14537

  Generated by :no_entry_sign: dangerJS against 20d8761ed53d200832473ca81381ff1a66af8623

authors: StuTruss robot-mymove


text:
"tx push" does not find project when specifying a resource, but "tx pull" does

$tx push -s my-project.my-resource is returning an error:
# Getting info about resources

my-project.my-resource - Error while fetching stats, 404, not_found: No `Project` resource found with the identifier `o:org-1:p:my-project`

However, the equivalent pull $tx pull my-project.my-resource does find the project and resource, and completes successfully.

This was a token issue. The server returns 404 for the project, instead of 401 Unauthorized. 🤷♂

This was a token issue. The server returns 404 for the project, instead of 401 Unauthorized. 🤷♂

Hey @tim-heighes-fishbrain , I'm struggling with the same issue and can't seem to wrap my head around why I'm getting a 404 when trying to push. Would be great if you can shed some light on how you resolved this issue.

This was a token issue. The server returns 404 for the project, instead of 401 Unauthorized. 🤷♂

Hey @tim-heighes-fishbrain , I'm struggling with the same issue and can't seem to wrap my head around why I'm getting a 404 when trying to push. Would be great if you can shed some light on how you resolved this issue.

I spoke with Transifex support who helped me through creating a new token.

Thanks @tim-heighes-fishbrain.

repo: transifex/cli


text:
Failed to launch the browser process on Heroku

I'm trying to host my app using chatgpt-api on Heroku, but puppeteer needs to run headless in order for that to work.
Would someone be able to add an option to run puppeteer headless?
I believe all that needs to change is /src/open-ai.ts line 132. headless: true,

@averybiskup this isn't recommended at the moment until we have a robust solution to bypass captchas. Right now, oftentimes the headful version is very much necessary in order to manually bypass captchas.

@transitive-bullshit Do you know if it's possible now to run puppeteer headless? Are you using chatgpt-api from your personal computer so far?

@elreco I'm currently running minimized puppeteer windows, so not completely headless.
I know some people are using xvfb successfully on linux to run with a fake virtual framebuffer.
I have not tried the "headless: true" option to puppeteer yet.

yes, I use with google auth provider and lunch a bot with xvfb inside docker. I'm curious,since google auth won't encounter CAPTCHAs,why not let google auth login can run with headless mode?

Hey! Any plans on adding this as an option now that theres 2captcha/nopecha implementation? Ty

authors: LaysDragon averybiskup elreco kraj011 transitive-bullshit

repo: transitive-bullshit/chatgpt-api


text:
🛑 TechinAsia_Laravel_API is down

In 0ea520c, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 172 ms

Resolved: TechinAsia_Laravel_API is back up in 85ac227 after 7 minutes.

repo: traqy/upptime


text:
🛑 TechinAsia_WordPress_API is down

In d7f74af, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 171 ms

Resolved: TechinAsia_WordPress_API is back up in 69d8c3c after 14 minutes.


text:
🛑 TechinAsia is down

In dc8f454, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 1015 ms

Resolved: TechinAsia is back up in f7cd70a after 14 minutes.


text:
🛑 TechinAsia is down

In bce302f, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 1025 ms

Resolved: TechinAsia is back up in bf8cdec after 7 minutes.


text:
🛑 TechinAsia is down

In fd7f128, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 969 ms

Resolved: TechinAsia is back up in 13fe4a8 after 7 minutes.


text:
🛑 TechinAsia_WordPress_API is down

In 26f40dc, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 173 ms

Resolved: TechinAsia_WordPress_API is back up in b958fe1 after 10 minutes.


text:
🛑 TechinAsia is down

In 4f2b7b4, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 762 ms

Resolved: TechinAsia is back up in 66f851f after 7 minutes.


text:
🛑 TechinAsia_Laravel_API is down

In 6450519, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 239 ms

Resolved: TechinAsia_Laravel_API is back up in 8910d61 after 7 minutes.


text:
🛑 TechinAsia_WordPress_API is down

In 4d0868b, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 225 ms

Resolved: TechinAsia_WordPress_API is back up in daf8f3a after 13 minutes.


text:
🛑 TechinAsia is down

In 79ce051, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 1029 ms

Resolved: TechinAsia is back up in ecfbb14 after 8 minutes.


text:
🛑 TechinAsia is down

In e5ba886, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 968 ms

Resolved: TechinAsia is back up in df753bb after 7 minutes.


text:
Snippet: Generate single page from multible MD files

Expected input files:
---
Category: green
Question: Question 1
Answer: Answer 1
---

---
Category: red
Question: Question 2
Answer: Answer 2
---

---
Category: red
Question: Question 3
Answer: Answer 3
---

Expected output:

    Question 1

Answer 1

    Question 2

Answer 2

    Question 3

Answer 3

Using https://vitejs.dev/guide/features.html#glob-import
const modules = import.meta.globEager("**/glob_that_matches_dir")

modules will be a Map like object.
const modules = {
  "../content/post_one.svx": {
    metadata: { Category: '...', Question: '...', Answer: '...' },
    default: Component
  },
  ...
}

So something like:

{#each Object.entries(grouped_modules) as [cat, contents]}

    {#each contents as question}

        {question.metadata.Question}

{question.metadata.Answer}

    {/each}

{/each}

Source: https://github.com/pngwn/MDsveX/issues/444#issuecomment-1094241618
Discussion: https://github.com/pngwn/MDsveX/discussions/445#discussioncomment-2538747

Here is an example REPL showing roughly how it works.

Here is an example REPL showing roughly how it works:
Generate single page from multible MD files.

repo: trasherdk/MDsveX


text:
config files - need explanation (fhd vs largea vs lowa vs mhead vs mida), differences between config files, how to choose, etc.

Can somebody explain the naming of the config files?
I gather all means detects all objects (car, pedestrian, cyclist, etc.) vs car means only detects cars.  Also I gather pp is short for PointPillars.  But what are the other abbreviations?  For example what do the following mean:
fhd
largea
lowa
mhead
mida

I'm under the impression that if I'm using the nuScenes set I should choose a config file in second.pytorch/second/configs/nuscenes whereas if I'm using the Kitti set I should choose a config file in second.pytorch/second/configs or second.pytorch/second/configs/pointpillars is this correct?
Also within second.pytorch/second/configs/pointpillars what is pp_pretrain.config, does pretrain mean it should not be used for training?  Also in, for example, second.pytorch/second/configs/pointpillars/car, what are the xyres_xx.config files and what is the advantage/disadvantage of using them vs the others?
Some general explanation of the config file organization and naming would be greatly appreciated.

hi all, I am also much appreciated it if someone could explain this.

authors: CDahmsSpireon chyohoo


text:
Arithmetic number test fails (and succeeds)

?- X = -1, Y = +1, Z is X + Y, number(Y).
   false. % If Y is not a number why does the next query succeed?

?- X = -1, Y = +1, Z is X + Y.
   X = -1, Y = +1, Z = 0.

Because *1 is an evaluable expression not a number, unlike -1 which is the
latter.
On Sun, Jul 2, 2023 at 9:12 AM flexoron @.***> wrote:

?- X = -1, Y = +1, Z is X + Y, number(Y).
false. % If Y is not a number why does the next query succeed?
?- X = -1, Y = +1, Z is X + Y.
X = -1, Y = +1, Z = 0.
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/230, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEQ5RAZSV4YH7U5D2ADXOCVF5ANCNFSM6AAAAAAZ3CDXHM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I mean +1
On Sun, Jul 2, 2023 at 9:12 AM flexoron @.***> wrote:

?- X = -1, Y = +1, Z is X + Y, number(Y).
false. % If Y is not a number why does the next query succeed?
?- X = -1, Y = +1, Z is X + Y.
X = -1, Y = +1, Z = 0.
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/230, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEQ5RAZSV4YH7U5D2ADXOCVF5ANCNFSM6AAAAAAZ3CDXHM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Do a write_canonical(+1) to see for yourself.
On Sun, Jul 2, 2023 at 9:12 AM flexoron @.***> wrote:

?- X = -1, Y = +1, Z is X + Y, number(Y).
false. % If Y is not a number why does the next query succeed?
?- X = -1, Y = +1, Z is X + Y.
X = -1, Y = +1, Z = 0.
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/230, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEQ5RAZSV4YH7U5D2ADXOCVF5ANCNFSM6AAAAAAZ3CDXHM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Oh, Ok then.

Still I've a problem with -0.
?- number(-0), write_canonical(-0).
0   true.
?- number(-1), write_canonical(-1).
-1   true.

What is -0 good for?

Absolutely nothing.
On Sun, 2 July 2023, 10:32 flexoron, @.***> wrote:

Still I've a problem with -0.
?- number(-0), write_canonical(-0).
0   true.
?- number(-1), write_canonical(-1).
-1   true.
What is -0 good for?
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/230#issuecomment-1616219730,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEWAC5O7PX6JPLBT6VTXOC6SRANCNFSM6AAAAAAZ3CDXHM
.
You are receiving this because you commented.Message ID:
@.***>

But - * - = +

X is -0 * -0.0.
  X = -0.0.

Looks like a floating point artefact.
On Sun, 2 July 2023, 10:40 flexoron, @.***> wrote:

But - * - = +
X is -0 * -0.0.
X = -0.0.
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/230#issuecomment-1616235179,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSETQ7P6XA2TC6XF3LVDXOC7RBANCNFSM6AAAAAAZ3CDXHM
.
You are receiving this because you commented.Message ID:
@.***>

Not really:
If -0 is a number then - is a minus-sign and  - * - = +

?- X is -0 * -0.0.
X = -0.0. % Prolog might be good for speculative mathematics research.

authors: flexoron infradig

repo: trealla-prolog/trealla


text:
String interpolation

See #34
After some blood, sweat and tears, I proudly present interpolated strings for PHP!
If the code can be improved in any way or there is an edge case I've missed, please educate me!
Big thanks to @ahelwer for helping me get unstuck on this issue!
Added nodes:

encapsed_string
escape_sequence
_simple_string_part (for inline $ usage without curly brackets)
_complex_string_part (for the complex notation using {$...})
_simple_string_member_access_expression, _simple_string_subscript_expression

Examples:
"This is {$great}";
(expression_statement
  (encapsed_string
    (string)
    (variable_name (name))
  )
)

"This works: {$arr['key']}";
(expression_statement
  (encapsed_string
    (string)
    (subscript_expression
      (variable_name (name))
      (string)
    )
  )
)

"Hello $people, you're awesome!";
(expression_statement
  (encapsed_string
    (string)
    (variable_name (name))
    (string)
  )
)

"$people->john drank some $juices[0] juice.".PHP_EOL;
(expression_statement
  (binary_expression
    (encapsed_string
      (member_access_expression
        (variable_name (name))
        (name)
      )
      (string)
      (subscript_expression
        (variable_name (name))
        (integer)
      )
      (string)
    )
    (qualified_name (name))
  )
)

Checklist:

[x] All tests pass in CI
[x] There are sufficient tests for the new fix/feature (see string.txt)
[x] Grammar rules have not been renamed unless absolutely necessary (0 rules renamed)
[x] The conflicts section hasn't grown too much (0 new conflicts)
[x] The parser size hasn't grown too much (master: 2595, PR: 2626)

@maxbrunsfeld everything is working like a charm except for _simple_string_part, which will always resolve to a variable - even though they have other options. So far, I've been unable to figure out how to work around that problem (I've tried adding a conflict and a few versions of precedence - which I do not fully understand yet).
Could you help me get unstuck when you have some time to spend on this?

I just want to thank you @cfroystad and @maxbrunsfeld for doing all the work here. I have no idea how all this parsing stuff works, but you make my day job A LOT easier ❤

After digging more into this and learning some ninja tricks of tree-sitter debugging, I think I've narrowed the problem down to the relation between the external lexing rule encapsed_string_chars and the _simple_string_part nodes.
However, no amount of conflicts, restructuring or precedence trickery has worked so far. Thus, this plea for help 😄
Take the following input:
<?php

"$people->john drank some";

We'd expect the following output:
(program
  (php_tag)
  (expression_statement
      (encapsed_string
        (member_access_expression
          (variable_name (name))
          (name)
        )
        (string)
      )
  )
)

But get:
(program
  (php_tag)
  (expression_statement
    (encapsed_string
      (variable_name (name))
      (string)
    )
  )
)

Debug output:
new_parse
process version:0, version_count:1, state:1, row:1, col:0
lex_internal state:77, row:1, column:0
  consume character:'<'
  consume character:'?'
  consume character:'p'
  consume character:'h'
  consume character:'p'
lexed_lookahead sym:php_tag, size:5
shift state:36
process version:0, version_count:1, state:36, row:1, col:5
lex_external state:2, row:1, column:5
  consume character:13
  consume character:10
  consume character:13
  consume character:10
lex_internal state:0, row:1, column:5
  skip character:13
  skip character:10
  skip character:13
  skip character:10
  consume character:'"'
lexed_lookahead sym:", size:5
shift state:1144
process version:0, version_count:1, state:1144, row:3, col:1
lex_external state:5, row:3, column:1
lex_internal state:6, row:3, column:1
  consume character:'$'
lexed_lookahead sym:$, size:1
shift state:1824
process version:0, version_count:1, state:1824, row:3, col:2
lex_internal state:3, row:3, column:2
  consume character:'p'
  consume character:'e'
  consume character:'o'
  consume character:'p'
  consume character:'l'
  consume character:'e'
  consume character:'p'
lexed_lookahead sym:name, size:6
shift state:1253
process version:0, version_count:1, state:1253, row:3, col:8
lex_external state:5, row:3, column:8
  consume character:'-'
  consume character:'>'
  consume character:'j'
  consume character:'o'
  consume character:'h'
  consume character:'n'
  consume character:' '
  consume character:'d'
  consume character:'r'
  consume character:'a'
  consume character:'n'
  consume character:'k'
  consume character:' '
  consume character:'s'
  consume character:'o'
  consume character:'m'
  consume character:'e'
lexed_lookahead sym:string, size:17
reduce sym:variable_name, child_count:2
reduce sym:_simple_string_variable_name, child_count:1
reduce sym:_simple_string_part, child_count:1
reduce sym:encapsed_string_repeat1, child_count:1
shift state:1357
process version:0, version_count:1, state:1357, row:3, col:25
lex_external state:5, row:3, column:25
lex_internal state:6, row:3, column:25
  consume character:'"'
lexed_lookahead sym:", size:1
reduce sym:encapsed_string_repeat1, child_count:1
reduce sym:encapsed_string_repeat1, child_count:2
shift state:731
process version:0, version_count:1, state:731, row:3, col:26
lex_external state:4, row:3, column:26
lex_internal state:4, row:3, column:26
  consume character:';'
lexed_lookahead sym:;, size:1
reduce sym:encapsed_string, child_count:3
reduce sym:_string, child_count:1
reduce sym:_primary_expression, child_count:1
reduce sym:_unary_expression, child_count:1
reduce sym:_expression, child_count:1
shift state:456
process version:0, version_count:1, state:456, row:3, col:27
lex_external state:2, row:3, column:27
lex_internal state:0, row:3, column:27
lexed_lookahead sym:end, size:0
reduce sym:expression_statement, child_count:2
reduce sym:program_repeat1, child_count:1
reduce sym:program, child_count:2
accept
done

Questions:

Is there a way to know the previous matched token in the external scanner? Thus, being able to disallow '->[char]' or '[' at the start of a string if a variable precedes it
If not, (or even if 🙂), is there a better way of handling this problem I've been unable to identify?

I see you took option two, very nice! One trip-up I should have mentioned when branching off values in the valid_symbols array: if tree-sitter encounters a parse error and enters error recovery mode, the first thing it does is call your external scanner with all symbols marked as valid (I first thought this was a bug). So it's probably a good idea to detect this has happened and then decide what to do; see my code here: https://github.com/tlaplus-community/tree-sitter-tlaplus/blob/4c05e1c54e1e26624b5f9cccc840159ab8bb924b/src/scanner.cc#L1626

Thanks for yet another helpful insight!
Since the main grammar is in the internal parser, I suppose it's correct to do as you've done in your code: Hand control back from the external scanner and rather have the main parser call it again if it should find it useful.

Okay I just tested it and it works, see here: https://github.com/tlaplus-community/tree-sitter-tlaplus/blob/11c65d44e60a4086556b4819037499399b903a8d/src/scanner.cc#L1619
You need to make the change on your grammar's side too, like here: https://github.com/tlaplus-community/tree-sitter-tlaplus/blob/4c05e1c54e1e26624b5f9cccc840159ab8bb924b/grammar.js#L84

Brilliant! That made the detection less brittle to future changes! Thanks 🙂

"hello ${a} world"; becomes (string [1, 1] - [1, 17]), but I would expect a variable_name to be in there.
"hello \0 world"; becomes a string, but I would expect an escape_sequence in there.
The following gives an error:

<?php
$ab = "ab";
echo "hello ${"a"."b"} world";

Also, braces can be escaped with a backslash. The following is valid in PHP but gives an error with tree-sitter in this branch:
<?php "\{$";

Thank you for testing and identifying some of the things I've missed. I'll look into fixing them when I get home from work. Most of them look like they'll be easy to fix (although slightly embarrassing 😄)

All review comments have been addressed in the last commit.
Thank you both for identifying bugs and suggesting good improvements.
With regard to escaping \{ it appears it's not really escaping but whenever those two letter coincide, they're both printed instead of interpreted. I've changed the implementation accordingly.

Nice work. It seems I was mistaken about dynamic variable names. "$$$$$$$$$$$$$a" is interpreted by PHP as many dollars and a single variable, not as a dynamic variable.
I also found some more edge cases that fail to parse:

"${a}["
"\u{$a}"

Thanks for testing!
I've fixed the two first items, but might need some guidance on the last one.
With the current implementation, I'd need to have two candidate mark_end (which as far as I understand is not supported):
" <- mark_end[string end: potential escape sequence]
\
u <- mark_end[string end: potential complex string element]
{ <- we don't know which to use yet
$ <- Ah, it's a complex string element, use "string end: potential complex string element" end
a
}
"

This might all be a consequence of me doing too much in the external scanner due to not having found a way to solve them in the main parser.
Any pointers/ideas on how to handle this would be greatly appreciated! (one option is of course to wait until Hack is done ironing out the same bugs, and try to adopt their approach)

There's a conflict. You probably need to merge master in your branch (or rebase).

Thanks! I forgot to update the branch after merging another PR earlier. However, the conflict is only in the generated parser and should thus not be a blocker for final review.
I'll try to find a few minutes to rebase when I get home from work in a few hours 🙂

Rebased

authors: Sjord ahelwer aryx cfroystad unansweredocd

repo: tree-sitter/tree-sitter-php


text:
github.com/treeverse/lakefs/pyramid TestMultipleConcurrentReads flakes out

E.g.:
ariels@redqueen:~/dev/lakeFS$ go test --count=20 --race github.com/treeverse/lakefs/pyramid
--- FAIL: TestMultipleConcurrentReads (0.01s)
    tier_fs_test.go:175:
                Error Trace:    tier_fs_test.go:206
                                                        tier_fs_test.go:175
                                                        asm_amd64.s:1374
                Error:          Not equal:
                                expected: []byte{0x68, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x77, 0x6f, 0x72, 0x6c, 0x64, 0x21}
                                actual  : []byte{}

                                Diff:
                                --- Expected
                                +++ Actual
                                @@ -1,3 +1,2 @@
                                -([]uint8) (len=12) {
                                - 00000000  68 65 6c 6c 6f 20 77 6f  72 6c 64 21              |hello world!|
                                +([]uint8) {
                                 }
                Test:           TestMultipleConcurrentReads
FAIL
FAIL    github.com/treeverse/lakefs/pyramid     53.283s
FAIL

This is on master on my box (Dell XPS), 095ac0e01a3dcad7cd5b246656d19e17372b8005 (HEAD -> master, origin/master, origin/HEAD) Validate catalog arguments based on current mvcc cataloger (#1138) .

This is on master on my box (Dell XPS), 095ac0e01a3dcad7cd5b246656d19e17372b8005 (HEAD -> master, origin/master, origin/HEAD) Validate catalog arguments based on current mvcc cataloger (#1138) .

repo: treeverse/lakeFS


text:
extract origin dual fisheye and imu measurements

Thanks so much for your job! i'm a newbie about gopro or ffmeg. I wonder  if could i get the origin dual fisheye images and imu measurements from gopro max .360 file as i want to use it to do vio job. Thanks for your help!

Thanks @fushi219 .
Check out this post, it might help: https://www.trekview.org/blog/2022/gopro-telemetry-exporter-getting-started/
If not, please raise any other general questions like this one on our Discord: https://discord.gg/ZVk7h9hCfw


text:
NavIcon not showing

Icon not showing ... Is there anything missing from me

facing same issue, here is the demo of CodeSandbox
https://codesandbox.io/s/interesting-wave-c21jf

@deshario
https://codesandbox.io/s/interesting-wave-c21jf
You can include Font Awesome css file in your html file, please see above mentioned link for your ready reference

thx @aakhan89  i was looking for a solution for hours ...

authors: MNzGenaud aakhan89 deshario

repo: trendmicro-frontend/react-sidenav


text:
Change default min-width of SideNav

Is there a way to change the 240px default width of the sidenav?
I found that in file sidenav-expanded.styl you can find that value, but I don't want to change it directly on the src file. Is there a way to configure it?

I have been fighting with this issue for two days. Ten minutes after posting the issue, I realized the answer... for tracking purpose, I post the answer:
const navWidthCollapsed = 64;
const navWidthExpanded = 280;
<SideNav style={{minWidth: expanded ? navWidthExpanded : navWidthCollapsed }}
Tks.

@crismarucci  How do you get "expanded" inside SideNav? Are you maintaining a local state?
<SideNav style={{minWidth: **expanded** ? navWidthExpanded : navWidthCollapsed }}

Sorry for the delay in my answer! Yes, I'm maintaining a local state with that variable.
`
const navWidthCollapsed = 64;
const navWidthExpanded = 220;
class App extends React.Component {
state = {
selected: 'home',
expanded: true
};
onSelect = (selected) => {
this.setState({ selected: selected });
};
onToggle = (expanded) => {
this.setState({ expanded: expanded });
};
render(){
const { expanded } = this.state
return (
  <Container>

    <Route render={({location, history}) => (
          <SideNav onToggle={this.onToggle} expanded={expanded}
            style={{...SideNavStyles, minWidth: expanded ? navWidthExpanded : navWidthCollapsed }}
            onSelect={(selected) => {
              const to = '/' + selected;
              if (location.pathname !== to) {
                history.push(to);
              }
            }}>

`

Sorry for the delay in my answer! Yes, I'm maintaining a local state with that variable.
`
const navWidthCollapsed = 64;
const navWidthExpanded = 220;
class App extends React.Component {
state = {
selected: 'home',
expanded: true
};
onSelect = (selected) => {
this.setState({ selected: selected });
};
onToggle = (expanded) => {
this.setState({ expanded: expanded });
};
render(){
const { expanded } = this.state
return (
  <Container>

    <Route render={({location, history}) => (
          <SideNav onToggle={this.onToggle} expanded={expanded}
            style={{...SideNavStyles, minWidth: expanded ? navWidthExpanded : navWidthCollapsed }}
            onSelect={(selected) => {
              const to = '/' + selected;
              if (location.pathname !== to) {
                history.push(to);
              }
            }}>

`

Thanks for your answer.


text:
🛑 api.tresl.co is down

In 4aad3f1, api.tresl.co (https://api.tresl.co/health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: api.tresl.co is back up in 10cecc4 after 7 minutes.

repo: tresl-co/uptime


text:
fixed a bug when generating shares with group_threshold=1

The _split_secret function only returns a single share when you pass in a group_threshold of 1. This change makes spreads that single share around to all of the groups in the case that the group_threshold is 1, but there is more than one group.

ISTM the fix should be in the _split_secret function? at the threshold == 1 check, you should return [(i, shared_secret) for i in range(share_count)]?
also the test case is a copy-paste of the other group share test. that's not great, it is unclear what it is that you're testing.
instead you should make a test case like this:
@pytest.mark.parametrize("threshold", (1, 2, 5))
def test_all_groups_exist(threshold):
    mnemonics = shamir.generate_mnenonics(threshold, [(2, 5)] * 5, MS)
    assert len(mnemonics) == 5
    # plus assert that 'threshold' groups combined is enough or something

Good work finding this bug @howech!
I think that the bug is actually in the specification https://github.com/satoshilabs/slips/blob/master/slip-0039.md#splitsecrett-n-s, where step 2 states that If T is 1, then let y1 = S and return. It should say If T is 1, then let yi = S for all i, 1 ≤ i ≤ N, and return. So I am in favor of making the fix inside _split_share like @matejcik proposed. In fact, that is exactly the code that we had there before the code review, which is paradoxically when this bug got introduced.

I made the correction to the SLIP-0039 specification as described above.

I think the test_group_sharing_threshold_1() that @howech added was OK, it just needed some cleanup. I added it back in with some minor changes and merged to master: https://github.com/trezor/python-shamir-mnemonic/commit/b836a948369866803061d45dd8b0fe392b666c0a
Thanks!

authors: andrewkozlik howech matejcik

repo: trezor/python-shamir-mnemonic


text:
Error connecting to repository database

This error occurs under the following conditions:
You are running the GUI from the service installation folder.  The config file is encrypted.  You haven't modified the connections to create the ConnectionStrings.json file in the AppData folder.  The error occurs even if you have password to decrypt config.

Fixed #633

repo: trimble-oss/dba-dash


text:
get rid of the dependency ch.qos.logback:logback-classic:jar:1.4.8:compile

resolves https://github.com/trinodb/trino-gateway/issues/195

Discussed with @andythsu .. we will just declare the dependency since this is approach is not really helping us improve the overall setup. Andy will send a PR for the dependency declaration.

authors: andythsu mosabua

repo: trinodb/trino-gateway


text:
Create Convays's life game.py

Please add this under Hactoberfest2024

Thanks for your contribution!

PR has been merged under Hacktoberfest!

Happy contribution!


text:
Read First Dimension Batching From Model Config

Read whether the first dimension can be batched directly from the model config, using the logic of ServerModelBatchProperties without the extra fields or need for the model to already be loaded.
PRs in this change (merge together):
https://github.com/triton-inference-server/backend/pull/47
https://github.com/triton-inference-server/identity_backend/pull/15
https://github.com/triton-inference-server/server/pull/3692

@tanmayv25 @CoderHam If either of you could reapprove (I rebased while getting the CI working), that'd be super helpful. This PR is ready to merge.

repo: triton-inference-server/backend


text:
Add per-response statistics

Example output:
{
  "model_stats": [
    {
      "name": "square_int32",
      "version": "1",
      "last_inference": 0,
      "inference_count": 0,
      "execution_count": 0,
      "inference_stats": {
        "success": {
          "count": 0,
          "ns": 0
        },
        "fail": {
          "count": 0,
          "ns": 0
        },
        "queue": {
          "count": 0,
          "ns": 0
        },
        "compute_input": {
          "count": 0,
          "ns": 0
        },
        "compute_infer": {
          "count": 0,
          "ns": 0
        },
        "compute_output": {
          "count": 0,
          "ns": 0
        },
        "cache_hit": {
          "count": 0,
          "ns": 0
        },
        "cache_miss": {
          "count": 0,
          "ns": 0
        }
      },
      "batch_stats": [],
      "response_stats": [
        {
          "responses": [
            {
              "index": 0,
              "success": {
                "count": 3758,
                "ns": 104645144
              },
              "fail": {
                "count": 0,
                "ns": 0
              },
              "compute_infer": {
                "count": 3758,
                "ns": 312936
              },
              "compute_output": {
                "count": 3758,
                "ns": 83222303
              }
            },
            {
              "index": 1,
              "success": {
                "count": 3758,
                "ns": 71950386
              },
              "fail": {
                "count": 0,
                "ns": 0
              },
              "compute_infer": {
                "count": 3758,
                "ns": 284120
              },
              "compute_output": {
                "count": 3758,
                "ns": 59387380
              }
            }
          ]
        },
        {
          "responses": [
            {
              "index": 0,
              "success": {
                "count": 3725,
                "ns": 111852810
              },
              "fail": {
                "count": 0,
                "ns": 0
              },
              "compute_infer": {
                "count": 3725,
                "ns": 321325
              },
              "compute_output": {
                "count": 3725,
                "ns": 85285353
              }
            },
            {
              "index": 1,
              "success": {
                "count": 3725,
                "ns": 79317289
              },
              "fail": {
                "count": 0,
                "ns": 0
              },
              "compute_infer": {
                "count": 3725,
                "ns": 284731
              },
              "compute_output": {
                "count": 3725,
                "ns": 64023205
              }
            },
            {
              "index": 2,
              "success": {
                "count": 3725,
                "ns": 65396800
              },
              "fail": {
                "count": 0,
                "ns": 0
              },
              "compute_infer": {
                "count": 3725,
                "ns": 274910
              },
              "compute_output": {
                "count": 3725,
                "ns": 53976564
              }
            }
          ]
        }
      ]
    }
  ]
}

Rebased.
Changes since last review:
$ git diff d7f8e411231431d58a3c5ed5008cb96263807826 07c66fe128bbb2c36c19c5115348a17e8c7a8add
diff --git a/include/triton/core/tritonbackend.h b/include/triton/core/tritonbackend.h
index cff61da..5c2deef 100644
--- a/include/triton/core/tritonbackend.h
+++ b/include/triton/core/tritonbackend.h
@@ -1257,7 +1257,7 @@ TRITONBACKEND_ModelInstanceReportBatchStatistics(

 /// Record statistics for an inference response.
 ///
-/// Set 'success' true to indicate that the inference response completed
+/// Set 'success' to true to indicate that the inference response completed
 /// successfully. In this case all timestamps should be non-zero values reported
 /// in nanoseconds and should be collected using
 /// std::chrono::steady_clock::now().time_since_epoch() or the equivalent.  Set
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index 4e22fb7..5fb4062 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -106,7 +106,6 @@ set(
   backend_model.cc
   backend_model_instance.cc
   buffer_attributes.cc
-  common.cc
   cuda_utils.cc
   dynamic_batch_scheduler.cc
   ensemble_scheduler.cc
@@ -150,7 +149,6 @@ set(
   backend_model.h
   backend_model_instance.h
   buffer_attributes.h
-  common.h
   constants.h
   cuda_utils.h
   dynamic_batch_scheduler.h
diff --git a/src/backend_model_instance.cc b/src/backend_model_instance.cc
index 35a7b7e..2eb0f53 100644
--- a/src/backend_model_instance.cc
+++ b/src/backend_model_instance.cc
@@ -966,7 +966,7 @@ TRITONAPI_DECLSPEC TRITONSERVER_Error*
 TRITONBACKEND_ModelInstanceReportResponseStatistics(
     TRITONBACKEND_ModelInstance* instance, TRITONBACKEND_Response* response,
     const bool success, const uint64_t response_start,
-    const uint64_t compute_output_start, const uint64_t response_end,
+    const uint64_t compute_output_start, const uint64_t compute_output_end,
     const uint32_t response_flags)
 {
 #ifdef TRITON_ENABLE_STATS
@@ -976,7 +976,7 @@ TRITONBACKEND_ModelInstanceReportResponseStatistics(
   INFER_STATS_DECL_TIMESTAMP(response_end_ns);
   ti->Model()->MutableStatsAggregator()->UpdateResponse(
       ti->MetricReporter(), ir, response_start, compute_output_start,
-      response_end, response_end_ns, response_flags, success);
+      compute_output_end, response_end_ns, response_flags, success);
 #endif  // TRITON_ENABLE_STATS
   return nullptr;
 }
diff --git a/src/common.cc b/src/common.cc
deleted file mode 100644
index 82b7bc9..0000000
--- a/src/common.cc
+++ /dev/null
@@ -1,39 +0,0 @@
-// Copyright (c) 2022, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
-//
-// Redistribution and use in source and binary forms, with or without
-// modification, are permitted provided that the following conditions
-// are met:
-//  * Redistributions of source code must retain the above copyright
-//    notice, this list of conditions and the following disclaimer.
-//  * Redistributions in binary form must reproduce the above copyright
-//    notice, this list of conditions and the following disclaimer in the
-//    documentation and/or other materials provided with the distribution.
-//  * Neither the name of NVIDIA CORPORATION nor the names of its
-//    contributors may be used to endorse or promote products derived
-//    from this software without specific prior written permission.
-//
-// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS'' AND ANY
-// EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-// IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-// PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR
-// CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-// EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
-// PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
-// PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-// OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-#include "common.h"
-
-namespace triton { namespace core {
-
-uint64_t CountedObject::instance_count_ = 0;
-
-CountedObject::CountedObject()
-{
-  std::lock_guard<std::mutex> guard(mu_);
-  instance_index_ = CountedObject::instance_count_;
-  instance_count_++;
-}
-}};  // namespace triton::core
diff --git a/src/common.h b/src/common.h
deleted file mode 100644
index 32e9fc5..0000000
--- a/src/common.h
+++ /dev/null
@@ -1,44 +0,0 @@
-// Copyright (c) 2022, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
-//
-// Redistribution and use in source and binary forms, with or without
-// modification, are permitted provided that the following conditions
-// are met:
-//  * Redistributions of source code must retain the above copyright
-//    notice, this list of conditions and the following disclaimer.
-//  * Redistributions in binary form must reproduce the above copyright
-//    notice, this list of conditions and the following disclaimer in the
-//    documentation and/or other materials provided with the distribution.
-//  * Neither the name of NVIDIA CORPORATION nor the names of its
-//    contributors may be used to endorse or promote products derived
-//    from this software without specific prior written permission.
-//
-// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS'' AND ANY
-// EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-// IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-// PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR
-// CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-// EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
-// PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
-// PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-// OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-#pragma once
-
-#include <atomic>
-#include <mutex>
-
-namespace triton { namespace core {
-class CountedObject {
- public:
-  CountedObject();
-
- protected:
-  uint64_t InstanceIndex() { return instance_index_; }
-
- private:
-  static uint64_t instance_count_;
-  uint64_t instance_index_;
-  std::mutex mu_;
-};
-}};  // namespace triton::core
diff --git a/src/infer_request.h b/src/infer_request.h
index b43daa4..d5f551b 100644
--- a/src/infer_request.h
+++ b/src/infer_request.h
@@ -31,7 +31,6 @@
 #include <unordered_map>
 #include <vector>
 #include "buffer_attributes.h"
-#include "common.h"
 #include "infer_response.h"
 #include "infer_stats.h"
 #include "infer_trace.h"
@@ -48,6 +47,9 @@ class Model;
 class InferenceServer;
 class MetricModelReporter;

+// Count the number of InferenceRequest instance created
+static std::atomic<uint64_t> inference_request_count_(0);
+
 //
 // An inference request. A request can be used multiple times for
 // inference but before each inference run, PrepareForInference() must
@@ -56,7 +58,7 @@ class MetricModelReporter;
 // valid. Preparing involves removing/resetting any state left over
 // from the previous inference.
 //
-class InferenceRequest : CountedObject {
+class InferenceRequest {
  public:
   // Input tensor
   class Input {
@@ -284,6 +286,7 @@ class InferenceRequest : CountedObject {
         requested_model_version_(requested_model_version), flags_(0),
         correlation_id_(0), batch_size_(0), timeout_us_(0), collect_stats_(true)
   {
+    inference_request_count_++;
     SetPriority(0);
   }

@@ -484,7 +487,7 @@ class InferenceRequest : CountedObject {
   {
     response_factory_.reset(new InferenceResponseFactory(
         model_shared_, id_, allocator, alloc_userp, response_fn, response_userp,
-        response_delegator_, InstanceIndex()));
+        response_delegator_, inference_request_count_));
     return Status::Success;
   }

diff --git a/src/infer_response.cc b/src/infer_response.cc
index 063fd90..91cfc16 100644
--- a/src/infer_response.cc
+++ b/src/infer_response.cc
@@ -40,12 +40,7 @@ Status
 InferenceResponseFactory::CreateResponse(
     std::unique_ptr<InferenceResponse>* response)
 {
-  uint64_t response_index;
-  {
-    std::lock_guard<std::mutex> guard{mu_};
-    response_index = total_response_idx_;
-    total_response_idx_++;
-  }
+  uint64_t response_index = total_response_idx_++;
   response->reset(new InferenceResponse(
       model_, id_, allocator_, alloc_userp_, response_fn_, response_userp_,
       response_delegator_, response_index, request_id_));
diff --git a/src/infer_response.h b/src/infer_response.h
index f9da7e2..43c1687 100644
--- a/src/infer_response.h
+++ b/src/infer_response.h
@@ -25,6 +25,7 @@
 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 #pragma once

+#include <atomic>
 #include <deque>
 #include <functional>
 #include <string>
@@ -99,8 +100,8 @@ class InferenceResponseFactory {
   // to handle the nullptr case.
   std::shared_ptr<Model> model_;

-  // The ID of the corresponding request that should be included in
-  // every response.
+  // The ID of the corresponding request that should be included in every
+  // response. This is a property that can be optionally provided by the user.
   std::string id_;

   // The response allocator and user pointer. The 'allocator_' is a
@@ -125,12 +126,12 @@ class InferenceResponseFactory {
   std::shared_ptr<InferenceTraceProxy> trace_;
 #endif  // TRITON_ENABLE_TRACING

-  // The internal unique ID of the request
+  // The internal unique ID of the request. This is a unique identification
+  // that triton attaches to each request in case user does not provide id_.
   uint64_t request_id_;

   // Response index
-  uint64_t total_response_idx_;
-  std::mutex mu_;
+  std::atomic<uint64_t> total_response_idx_;
 };

 //
@@ -270,7 +271,7 @@ class InferenceResponse {

   // The unique request ID stored in triton.
   uint64_t RequestUniqueId() const { return request_id_; }
-
+  // The timestamp in nanoseconds when the response started.
   uint64_t ResponseStartNs() const { return response_start_; }

   // Add an output to the response. If 'output' is non-null
@@ -370,7 +371,7 @@ class InferenceResponse {

   // Representing the request id that the response was created from.
   uint64_t request_id_;
-
+  // Timestamp in nanoseconds when the response started.
   uint64_t response_start_;
 };

diff --git a/src/test/CMakeLists.txt b/src/test/CMakeLists.txt
index 2b9c848..6c65ed4 100644
--- a/src/test/CMakeLists.txt
+++ b/src/test/CMakeLists.txt
@@ -94,8 +94,6 @@ if(${TRITON_ENABLE_GPU})
     ../status.cc
     ../status.h
     ../constants.h
-    ../common.h
-    ../common.cc
     ${MEMORY_SRCS}
     ${CUDA_MEMORY_MANAGER_SRCS}
     ${PINNED_MEMORY_MANAGER_SRCS}
$

authors: Tabrizian kthui

repo: triton-inference-server/core


text:
Upgrade node in CI to current and lts versions

Use node v18 and v20

Dropping node 12,14,16 would be breaking change

Released in v4.3.0

authors: byara harryzcy marklai1998

repo: trivago/prettier-plugin-sort-imports


text:
Small edits across docs and tutorials

Closes #30
Also, because the fmin function and some other functions in HOHQMesh were re-written the mesh statistics change (very) slightly such that the reference values in the tutorials are updated.

@ranocha Are the other checks not running because only the documentation source changed?

Yes


text:
Different test values on julia v1.9.3

Recently, CI fails due to different test values in one elixir with a 1D TreeMesh, see e.g. here. I was able to reproduce the error locally on julia v1.9.3 (and v1.10.0-beta2), but not on julia v1.9.2.

@andrewwinters5000 The failure occurs for one of the wet-dry elixirs. Could you maybe take a look at it and increase the test tolerance if required?

Thanks a lot!

Investigating the results of elixir_shallowwater_beach.jl using julia 1.9.0 versus julia 1.9.3 the error values for all the quantities start changing around the 10 decimal place. Because the error in the bottom topography is always quite small it seems to be more sensitive to whatever changes have happened "under-the-hood" in the new julia release. Running to tspan=(0.0,0.05) as done in the beach test we get:
# For julia 1.9.0
(l2 = [0.17979210479598923, 1.2377495706611434, 6.289818963361573e-8], linf = [0.845938394800688, 3.3740800777086575, 4.4541473087633676e-7])
# For julia 1.9.3
(l2 = [0.17979210239962704, 1.2377495649103047, 6.289758492103817e-8], linf = [0.8459383936345142, 3.374080078500849, 4.451690074347425e-7])

The fluid quantities pass but the bottom topography errors fail as, e.g.,
abs(l2_julia190[3] - l2_julia193[3]) = 6.047125775517298e-13

which is larger than the default atol=1.1102230246251565e-13 used in the testing.
We could adjust the tolerances, but I think a better way is to change this elixir to set adaptive=false in the SSPRK43 time integration scheme and update the reference values accordingly. My reasoning is two-fold. 1) The adaptive time stepping can cause the method to "lose" well-balancedness at least up to the (default) tolerances set in the adaptive integrator. This has not given us any positivity issues yet, but it is something to keep in mind. 2) When I run elixir_shallowwater_beach.jl to the final time I get a different number of accepted and total time steps between the two julia versions but using identical Trixi and OrdinaryDiffEq versions.
# For julia 1.9.0
Final time: 10.0  Time steps: 15078 (accepted), 20324 (total)
# For julia 1.9.3
Final time: 10.0 Time steps: 15073 (accepted), 20387 (total)

In contrast, when I run elixir_shallowwater_parabolic_bowl.jl that currently uses adaptive time stepping, the number of accepted and total time steps for both julia versions are identical. However, the parabolic bowl is a slightly simpler test case  than the beach run-up, which might explain the differences.

This is weird... Is there any discontinuous behavior involved in this setup that could explain these differences?

This is weird... Is there any discontinuous behavior involved in this setup that could explain these differences?

The velocity is discontinuous but the water height and bottom are not.

What I meant was more some discontinuity in the discretization. Since this is a test case with drying, we do use some thresholds etc. that may explain this

I think you could just use a slightly larger absolute tolerance in this case?

I think you could just use a slightly larger absolute tolerance in this case?

That would be okay from my side, although it is interesting that the error based time stepping changes so noticeably.

Yes, definitely...

authors: JoshuaLampert andrewwinters5000 ranocha


text:
🛑 qBit is down

In 68fecfe, qBit (https://tronflix.app/qbit/) was down:

HTTP code: 520
Response time: 235 ms

Resolved: qBit is back up in a9fb05c.

repo: tronyx/upptime


text:
🛑 FileBrowser is down

In 0f99ec2, FileBrowser (https://files.tronflix.app) was down:

HTTP code: 520
Response time: 145 ms

Resolved: FileBrowser is back up in 0002868.


text:
🛑 Bitwarden is down

In 46c7b71, Bitwarden (https://bitwarden.tronflix.app) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bitwarden is back up in 556e210 after 8 minutes.


text:
🛑 Nextcloud is down

In 92968b2, Nextcloud (https://nextcloud.tronflix.app/login) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nextcloud is back up in ad86fa8 after 7 minutes.


text:
Issue

I literally have 0 clue how I can use this I've been using MCSniperPY which was simple as putting a command in then the offset and the name that wanted to be sniped along with the account, if you can dumb it down for me and tell me the command I would put in to launch buckshot it'd be much appreciated. and if you don't know what I mean I mean as an example I'll use the MCSniperPY command : py -m mcsniperpy snipe
Something along the lines of this I need help
Thanks.

I agree that this is slightly more difficult to set up. Honestly if I were you I would use MCsniperGO instead which should be better than MCsniperPY. You could ask questions in their discord and since the instructions are almost copy and pasted from MCsniperGO instructions you should be able to use this too.
Yeah I realise this is not as user friendly as you would like but it is more meant for my personal use. You would not be missing much using MCsniperGO over this sniper (which tbf imo has a better success rate than MCsniperGO)

I just mainly wanted to use something like this sniper for gc sniping as I have no clue how to with MCSniperGO

Just ask on their discord. I guarantee you it's easier than this sniper

I tried finding it and I couldn’t for MCSniperGO or MCSniperPY

Nevermind I’m slow I found it.

repo: tropicbliss/buckshot


text:
dataServer EADDRINUSE Error

Hi there!
Using ftp-srv on a project and I am getting this error:
ftpServer.on('client-error', (data) => {

    // data.context
    context:"dataServer"

    // data.error
    address:"192.168.0.120"
    code:"EADDRINUSE"
    errno:"EADDRINUSE"
    port:8080
    syscall:"listen"

});

I have 2 CCTV cameras that FTP snapshots of CCTV Footage to ftp-srv every second. This is not a persistent error, it just happens every now and then, maybe once every few seconds? But every time it happens, there is a 10 second gap for ftp-srv to recover. I really can't pinpoint when or why this is happening though. Tried googling, failed.
Here is the bulk of the code, if it helps:
const ftpServer = new FtpSrv('ftp://192.168.0.120:9876', {
  pasv_range:8080
});

ftpServer.on('login', (data, resolve, reject) => {

  resolve({root: 'F:/path/to/ftp/root'});

  data.connection.on('STOR', (error, fileName) => {
    var filePath = data.connection.fs.cwd;
    if (error === null) {
      mainWindow.webContents.send('cctvSnapshot', {
        filePath: filePath,
        fileName: fileName
      });
    }
  });

});

Any idea how to fix this?

I tried to dig deeper here and I found out that the cause of this issue is because of simultaneous connections? To test I turned off 1 of the 2 CCTV Cameras and then poof the error went away.

I think this might be caused by how I'm choosing which port to use in a passive connection.
It always starts from the min pasv range and works it's way up.
If 2 connections attempt to get a passive connection at the same time, I can see them both being assigned the same port.
I'm working on some major changes which includes a generator for pasv ports so they are always incrementing.
But some more testing will be needed to see if this is the cause.

authors: joespina trs

repo: trs/ftp-srv

license: mit

license_source: bigquery


text:
Ingestion Status broken when multiple ingestions are started for a collection in LOCAL

Steps to reproduce:

Create a collection
Link 2 data sources to it.

Excepted Behaviour:

when one of the data sources has completed ingestion, its status changes to COMPLETED

Observed Behaviour:

in the attached screenshots, one of the data source has completed ingestion (see unstructured_api CPU usage, it was 200% when both were running) , but both have a status of DATA_INGESTION_STARTED.

when both are completed, the status for both of them is set to COMPLETED

Yes, actually same error occurs in deployed version as well, we shall check on this.

repo: truefoundry/cognita


text:
couchings, enabled

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,e]

/trunk merge

repo: trunk-io/mergequeue-staging


text:
gutturality, bosker

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,g]

/trunk merge


text:
foistiness, chalklike

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,f]

/trunk merge


text:
abusable, decerebration

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,d]

/trunk merge


text:
despiteous, admittatur

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,d]

/trunk merge


text:
cultirostres

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c]

/trunk merge


text:
contemporising, birrettas

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,c]

/trunk merge


text:
exobasidium

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[e]

/trunk merge


text:
afterlifetime, furzeling (logical-conflict)

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,f]

/trunk merge


text:
chromatinic, dithymol

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,d]

/trunk merge


text:
brachydomatic, gypsydom

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,g]

/trunk merge


text:
footslogged, confidingness

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,f]

/trunk merge


text:
calyptratae, formature

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,f]

/trunk merge


text:
basilic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b]

/trunk merge


text:
freshwoman, accusator

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,f]

/trunk merge


text:
coconsecrator, entomofauna

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[c,e]

/trunk merge


text:
gamodesmic, blenk

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,g]

/trunk merge


text:
firefall, euthyneura

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[e,f]

/trunk merge

repo: trunk-io/mergequeue


text:
adtevac, discriminates

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,d]

/trunk merge


text:
embryoferous, drapeability

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[d,e]

/trunk merge


text:
editor, arginines

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,e]

/trunk merge


text:
exocytosis, foremisgiving

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[e,f]

/trunk merge


text:
guest, foliature

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[f,g]

/trunk merge


text:
globous, basicity

This pull request was generated by the 'mq' tool

/trunk merge


text:
acinetaria

This pull request was generated by the 'mq' tool

/trunk merge


text:
czardases, eches

This pull request was generated by the 'mq' tool

/trunk merge


text:
gnaeus

This pull request was generated by the 'mq' tool

/trunk merge


text:
disjunct, complaintive

This pull request was generated by the 'mq' tool

/trunk merge


text:
blepharadenitis, armil

This pull request was generated by the 'mq' tool

/trunk merge


text:
drainable, galluptious

This pull request was generated by the 'mq' tool

/trunk merge


text:
fiefdom

This pull request was generated by the 'mq' tool

/trunk merge


text:
enterokinetic, gansey

This pull request was generated by the 'mq' tool

/trunk merge


text:
cramper, gaseity

This pull request was generated by the 'mq' tool

/trunk merge


text:
flimmer, didactylism

This pull request was generated by the 'mq' tool

/trunk merge


text:
blackfriars

This pull request was generated by the 'mq' tool

/trunk merge


text:
cirrus

This pull request was generated by the 'mq' tool

/trunk merge


text:
bhisti, goldfield

This pull request was generated by the 'mq' tool

/trunk merge


text:
griefful, filthy

This pull request was generated by the 'mq' tool

/trunk merge


text:
bankruptism

This pull request was generated by the 'mq' tool

/trunk merge


text:
doublehanded, edulcorator

This pull request was generated by the 'mq' tool

/trunk merge


text:
cowwheat, figurative

This pull request was generated by the 'mq' tool

/trunk merge


text:
gagelike

This pull request was generated by the 'mq' tool

/trunk merge


text:
gorgoneioneia, cachinnator

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,g]

/trunk merge


text:
crescograph, guilelessly

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,g]

/trunk merge


text:
gonfalons, agenda

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,g]

/trunk merge


text:
achylia

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a]

/trunk merge


text:
goslings, biunity

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b,g]

/trunk merge


text:
antiresonance

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a]

/trunk merge


text:
funt, diselectrify

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[d,f]

/trunk merge


text:
gnamma, decine

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[d,g]

/trunk merge


text:
brot, fortnights

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,f]

/trunk merge


text:
coggle, dyeing

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,d]

/trunk merge


text:
executer

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[e]

/trunk merge


text:
growthy, continually

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,g]

/trunk merge


text:
groggy, fishy

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[f,g]

/trunk merge


text:
eliminatory, contravallation

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,e]

/trunk merge


text:
fll, airpost

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,f]

/trunk merge


text:
Add unit tests for bridge/service

closes: https://github.com/trustlines-protocol/blockchain/issues/408
I hope it makes sense, knowing I had no idea about gevent, mock, or even the bridge before.

Codecov Report

Merging #413 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #413   +/-   ##
=======================================
  Coverage   91.79%   91.79%
=======================================
  Files          16       16
  Lines         865      865
=======================================
  Hits          794      794
  Misses         71       71

Flag
Coverage Δ

#bridge_end2end
84.39% <ø> (-1.39%)
:arrow_down:

#bridge_unit
73.41% <ø> (+1.5%)
:arrow_up:

Impacted Files
Coverage Δ

tools/bridge/bridge/validator_status_watcher.py
94.73% <0%> (-2.64%)
:arrow_down:

tools/bridge/bridge/confirmation_sender.py
86.29% <0%> (-1.62%)
:arrow_down:

tools/bridge/bridge/service.py
92.3% <0%> (+11.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 574a918...42fd79f. Read the comment docs.

Codecov Report

Merging #413 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #413   +/-   ##
=======================================
  Coverage   91.79%   91.79%
=======================================
  Files          16       16
  Lines         865      865
=======================================
  Hits          794      794
  Misses         71       71

Flag
Coverage Δ

#bridge_end2end
84.39% <ø> (-1.39%)
:arrow_down:

#bridge_unit
73.41% <ø> (+1.5%)
:arrow_up:

Impacted Files
Coverage Δ

tools/bridge/bridge/validator_status_watcher.py
94.73% <0%> (-2.64%)
:arrow_down:

tools/bridge/bridge/confirmation_sender.py
86.29% <0%> (-1.62%)
:arrow_down:

tools/bridge/bridge/service.py
92.3% <0%> (+11.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 574a918...bd18646. Read the comment docs.

authors: cducrest codecov-io

repo: trustlines-protocol/blockchain


text:
Feature/transfer info from event id

Based on https://github.com/trustlines-protocol/clientlib/pull/338
If I build the relay with https://github.com/trustlines-protocol/relay/pull/476, the e2e tests pass.

Codecov Report

Merging #339 into master will decrease coverage by 0.91%.
The diff coverage is 13.33%.

@@            Coverage Diff             @@
##           master     #339      +/-   ##
==========================================
- Coverage   61.42%   60.51%   -0.92%
==========================================
  Files          20       20
  Lines        1304     1327      +23
  Branches      256      265       +9
==========================================
+ Hits          801      803       +2
- Misses        441      462      +21
  Partials       62       62

Flag
Coverage Δ

#integration
34.21% <13.33%> (-0.46%)
:arrow_down:

#unit
60.51% <13.33%> (-0.92%)
:arrow_down:

Impacted Files
Coverage Δ

src/typings.ts
100.00% <ø> (ø)

src/Payment.ts
25.00% <13.33%> (-4.88%)
:arrow_down:

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 f1a49e8...9910a76. Read the comment docs.

repo: trustlines-protocol/clientlib


text:
🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅🦅

PLEASE CREATE RELEASE ISTG 😭

repo: tsar-boomba/prettier-java-action


text:
Handle some low hanging fruit

@mebelousov, since we're both committed to getting this done by the end of the year, I think we should start segmenting some of the low hanging fruit so we don't both work on the same things. This week, I'd like to knock the following completions:
LISTEN | 0/3 (0.00%)
LOCK | 0/34 (0.00%)
MOVE | 1/10 (10.00%)
NOTIFY | 0/2 (0.00%)
PREPARE | 0/46 (0.00%)
REASSIGN OWNED | 0/4 (0.00%)
REINDEX | 0/6 (0.00%)
RELEASE SAVEPOINT | 0/9 (0.00%)
RESET | 0/49 (0.00%)
REVOKE | 2/77 (2.60%)
ROLLBACK | 0/12 (0.00%)
ROLLBACK PREPARED | 0/4 (0.00%)
ROLLBACK TO SAVEPOINT | 0/10 (0.00%)
SAVEPOINT | 0/22 (0.00%)
SECURITY LABEL | 0/8 (0.00%)

They should be easy and bring lots more green into the test coverage status. I'm creating this issue so we don't end up working on the same things.

Grean! Thank you for planning.
I have implemented PREPARE. Will make PR soon.
https://github.com/mebelousov/antlr_psql/blob/4921e22f9f22d9d4bda5eaf7846240172ff4c7bd/antlr4/PostgreSQLParser.g4#L1121

I implemented all but REVOKE because that one wasn't so low-hanging.

authors: mebelousov tshprecher


text:
enhanced trace files

More data is needed in trace files to enable better performance analysis.  For starters, adding a timestamp to types.json lets us report types created during a timeframe and associate them with their checked expressions.  implementation here https://github.com/typeholes/TypeScript/tree/trace-data
Options for execution:

Get a PR merged upstream into typescript.  This is the preferred route.
Distribute a patched typescript with tracer.  The obvious downside is only having a single ts version
Provide a code mod so users can build their preferred version with enhanced trace data
a) possibly integrated into TS Version Switcher for ease of use.

This is being addressed in the live-trace branch.  No code mod will be needed

repo: tsperf/tracer


text:
Support lightweight build mode

Work in progress
This is a very early status of the idea i have to allow gamedev to customice 7h for their mod
forn now it only hides some elements depending on build options aka "conditional symbols"
TODO:

[x] add a button to check for game content updates and promt to download
[x] and the posiblity to add a custom 7heaven.var file
[ ] add a big picture behind all the controls customizable from theme

Thanks

I don't really know how to achieve the TODO :D

Fixed the syntax for you :) Feel free to tweak it at your own desire, and before saving use the Preview tab to double check.
Thank you for this amazing PR! Looking forward to see this implemented upstream.

@TurBoss how has this come have you been able to fix it?

yup I'm done Thanks all

I think this PR could be closed ?

authors: TurBoss barkermn01 julianxhokaxhiu

license: MS-PL


text:
paper code inquiry

is this the source code for Exploiting Cognitive Structure for Adaptive Learning？

Not exactly, here we publish three simulators, KSS is the source code of the KSS used in our paper

authors: tswsxk xueruafternoon

repo: tswsxk/EduSim


text:
cubeが表示されないことがある

初期処理がうまく行っているかうまく行っていないかが分からない．

Threear.js対応ブラウザの再起動で問題は解決する様子

キャッシュが原因の可能性があるので，キャッシュを禁止にした．
再現性がないので，しばらく様子見


text:
Failed the examples/test on MACOS while using AFL++ mode as the README.md requires.

These are my commans:
➜  test git:(main) ✗ AFL_DEBUG=1 afl-fuzz -i ./in -o ./out -m none -- ../../fpicker -m afl -u shm -e attach -p test -f harness.js -v
[+] Enabled environment variable AFL_DEBUG with value 1
[+] Enabled environment variable AFL_DEBUG with value 1
afl-fuzz++4.09a based on afl by Michal Zalewski and a large online community
[+] AFL++ is maintained by Marc "van Hauser" Heuse, Dominik Maier, Andrea Fioraldi and Heiko "hexcoder" Eißfeldt
[+] AFL++ is open source, get it at https://github.com/AFLplusplus/AFLplusplus
[+] NOTE: AFL++ >= v3 has changed defaults and behaviours - see README.md
[+] No -M/-S set, autoconfiguring for "-S default"
[*] Getting to work...
[+] Using exponential power schedule (FAST)
[+] Enabled testcache with 50 MB
[+] Generating fuzz data with a length of min=1 max=1048576
[*] Checking CPU scaling governor...
[+] You have 12 CPU cores and 3 runnable tasks (utilization: 25%).
[+] Try parallel jobs - see /usr/local/share/doc/afl/fuzzing_in_depth.md#c-using-multiple-cores
[*] Setting up output directories...
[+] Output directory exists but deemed OK to reuse.
[*] Deleting old session data...
[+] Output dir cleanup successful.
[*] Scanning './in'...
[+] Loaded a total of 6 seeds.
[*] Creating hard links for all input files...
[*] Validating target binary...
[*] Spinning up the fork server...
[+] All right - fork server is up.
[*] Extended forkserver functions received (00000000).
[*] No auto-generated dictionary tokens to reuse.
[*] Attempting dry run with 'id:000000,time:0,execs:0,orig:0'...
1
4
[D] DEBUG: calibration stage 1/7
5
6
7
8
7
AAAAA
../../fpicker

[-] Oops, the program crashed with one of the test cases provided. There are
    several possible explanations:

    - The test case causes known crashes under normal working conditions. If
      so, please remove it. The fuzzer should be seeded with interesting
      inputs - but not ones that cause an outright crash.

    - In QEMU persistent mode the selected address(es) for the loop are not
      properly cleaning up variables and memory. Try adding
      AFL_QEMU_PERSISTENT_GPR=1 or select better addresses in the binary.

    - On MacOS X, the semantics of fork() syscalls are non-standard and may
      break afl-fuzz performance optimizations when running platform-specific
      targets. To fix this, set AFL_NO_FORKSRV=1 in the environment.

    - Least likely, there is a horrible bug in the fuzzer. If other options
      fail, poke the Awesome Fuzzing Discord for troubleshooting tips.
[!] WARNING: Test case 'id:000000,time:0,execs:0,orig:0' results in a crash, skipping

and the syslogs are:
17:19:15.804460+0800	fpicker	[JS]: [*] afl_area_ptr: 0x0
17:19:15.804554+0800	fpicker	[JS]: [*] commap: 0x103f79000
17:19:15.804807+0800	fpicker	[JS]: [*] commap_id: /fp_comm_shm_10492_1804289383
17:19:15.805056+0800	fpicker	[JS]: [*] base: 0x1027ab000
17:19:15.805157+0800	fpicker	[JS]: [*] iteration_sem: 0x4
17:19:15.805352+0800	fpicker	[JS]: [*] exec_sem: 0x4
17:19:15.805589+0800	fpicker	[JS]: [*] Not excluding test from stalker
17:19:15.805721+0800	fpicker	[JS]: [*] Setting up interceptor
17:19:15.806433+0800	fpicker	[JS]: {"type":"send","payload":{"type":"_fpicker_ready","data":[{"name":"test","base":"0x1027ab000","size":16384,"path":"/Users/wujiesong3/Desktop/fpicker_test/fpicker/examples/test/test","id":0,"end":"0x1027af000"},{"name":"libSystem.B.dylib","base":"0x7ff811cf7000","size":8192,"path":"/usr/lib/libSystem.B.dylib","id":1,"end":"0x7ff811cf9000"},{"name":"libcache.dylib","base":"0x7ff811cf1000","size":24568,"path":"/usr/lib/system/libcache.dylib","id":2,"end":"0x7ff811cf6ff8"},{"name":"libcommonCrypto.dylib","base":"0x7ff811ca8000","size":49144,"path":"/usr/lib/system/libcommonCrypto.dylib","id":3,"end":"0x7ff811cb3ff8"},{"name":"libcompiler_rt.dylib","base":"0x7ff811cd5000","size":32768,"path":"/usr/lib/system/libcompiler_rt.dylib","id":4,"end":"0x7ff811cdd000"},{"name":"libcopyfile.dylib","base":"0x7ff811cc7000","size":57344,"path":"/usr/lib/system/libcopyfile.dylib","id":5,"end":"0x7ff811cd5000"},{"name":"libcorecrypto.dylib","base":"0x7ff805c26000","size":618448,"path":"/usr/lib/system/libcorecrypto.dyli<…>
17:19:15.806474+0800	fpicker	[*] MODULE=/Users/wujiesong3/Desktop/fpicker_test/fpicker/examples/test/test, start=0x1027ab000, end=0x1027af000
17:19:15.806587+0800	fpicker	[JS]: [1] before sem_wait in wait_for_exec (1694078355805)
17:19:15.809526+0800	fpicker	[*] Harness preparation done
17:19:15.809650+0800	fpicker	[*] Everything ready, starting to fuzz!
17:19:15.827044+0800	fpicker	[2] PRE SEM_POST in fuzz_iteration_in_process_shm: 1694078355827
17:19:15.827088+0800	fpicker	[*] POST SEM_POST in fuzz_iteration_in_process_shm: 1694078355827
17:19:15.827105+0800	fpicker	[*] PRE SEM_WAIT in fuzz_iteration_in_process_shm: 1694078355827
17:19:15.827117+0800	fpicker	[*] 1
17:19:15.827572+0800	fpicker	[JS]: [3] after sem_wait in wait_for_exec (1694078355827). This took 22 ms
17:19:15.827688+0800	fpicker	[JS]: 0x103f79020 5
17:19:15.827816+0800	fpicker	[JS]: [*] Interceptor ENTER (1694078355827)
17:19:15.829277+0800	fpicker	[JS]: {"type":"send","payload":{"type":"crash","msg":{"message":"access violation accessing 0xd8cd","type":"access-violation","address":"0x103f721b5","memory":{"operation":"read","address":"0xd8cd"},"context":{"pc":"0x103f721b5","sp":"0x700009691ef0","rax":"0xd8cd","rcx":"0xd8cd","rdx":"0x0","rbx":"0x10407c000","rsp":"0x700009691ef0","rbp":"0x700009691f20","rsi":"0x103f101f0","rdi":"0x700009692258","r8":"0x0","r9":"0x103eb66e0","r10":"0x0","r11":"0x1027aecd0","r12":"0x7000096925a0","r13":"0x1","r14":"0x2","r15":"0x0","rip":"0x103f721b5"},"nativeContext":"0x0","fileName":"test-fuzzer.js","lineNumber":38}}}
17:19:15.829315+0800	fpicker	[->] CRASH type received
17:19:15.829338+0800	fpicker	[->] message: {"type":"send","payload":{"type":"crash","msg":{"message":"access violation accessing 0xd8cd","type":"access-violation","address":"0x103f721b5","memory":{"operation":"read","address":"0xd8cd"},"context":{"pc":"0x103f721b5","sp":"0x700009691ef0","rax":"0xd8cd","rcx":"0xd8cd","rdx":"0x0","rbx":"0x10407c000","rsp":"0x700009691ef0","rbp":"0x700009691f20","rsi":"0x103f101f0","rdi":"0x700009692258","r8":"0x0","r9":"0x103eb66e0","r10":"0x0","r11":"0x1027aecd0","r12":"0x7000096925a0","r13":"0x1","r14":"0x2","r15":"0x0","rip":"0x103f721b5"},"nativeContext":"0x0","fileName":"test-fuzzer.js","lineNumber":38}}}
17:19:15.829353+0800	fpicker	[*] SEM_POST in _signal_exec_finished_with_ret_status 1694078355829
17:19:15.829380+0800	fpicker	[*] 2

I can't figure out where the mistakes lie. I just use the example in the repo and do as the README teaches.
This has been confuded with me for three days in work.

OK I succeed, because the log shows [*] afl_area_ptr: 0x0 so I just refer to the fuzzer.js and find it fails on the mmap(). So I compile the AFL++ again with CFALGS = "DUSEMMAP"=1，and it works.

OK I succeed, because the log shows [*] afl_area_ptr: 0x0 so I just refer to the fuzzer.js and find it fails on the mmap(). So I compile the AFL++ again with CFALGS = "DUSEMMAP"=1，and it works.

hi, add this flag, compile afl++ always show:
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; ASAN_OPTIONS=detect_leaks=0 AFL_QUIET=1 AFL_PATH=. AFL_LLVM_LAF_ALL=1 ./afl-cc -DUSEMMAP=1 -g -Wno-pointer-sign -Wno-variadic-macros -Wall -Wextra -Wno-pointer-arith -fPIC -I include/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -Wall -g -Wno-cast-qual -Wno-variadic-macros -Wno-pointer-sign -I ./include/ -I ./instrumentation/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DLLVM_BINDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/bin\" -DVERSION=\"++4.21a\" -DLLVM_LIBDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/lib\" -DLLVM_VERSION=\"18.1.4\" -DAFL_CLANG_FLTO=\"-flto=full\" -DAFL_REAL_LD=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/ld.lld\" -DAFL_CLANG_LDPATH=\"\" -DAFL_CLANG_FUSELD=\"1\" -DCLANG_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang\" -DCLANGPP_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang++\" -DUSE_BINDIR=1 -Wno-unused-function -fdebug-prefix-map="/private/tmp/AFLplusplus=llvm_mode" -Wno-deprecated -I/opt/homebrew/opt/openssl@3/include ./test-instr.c -o test-instr -L/opt/homebrew/opt/openssl@3/lib -L/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib
ASAN_OPTIONS=detect_leaks=0 ./afl-showmap -m none -q -o .test-instr0 ./test-instr < /dev/null
shmat for map: Invalid argument

[-] PROGRAM ABORT : the fuzzing target reports that the shmat() call failed.
         Location : report_error_and_exit(), src/afl-forkserver.c:494

any suggestions?

OK I succeed, because the log shows [*] afl_area_ptr: 0x0 so I just refer to the fuzzer.js and find it fails on the mmap(). So I compile the AFL++ again with CFALGS = "DUSEMMAP"=1，and it works.

hi, add this flag, compile afl++ always show:
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; ASAN_OPTIONS=detect_leaks=0 AFL_QUIET=1 AFL_PATH=. AFL_LLVM_LAF_ALL=1 ./afl-cc -DUSEMMAP=1 -g -Wno-pointer-sign -Wno-variadic-macros -Wall -Wextra -Wno-pointer-arith -fPIC -I include/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -Wall -g -Wno-cast-qual -Wno-variadic-macros -Wno-pointer-sign -I ./include/ -I ./instrumentation/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DLLVM_BINDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/bin\" -DVERSION=\"++4.21a\" -DLLVM_LIBDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/lib\" -DLLVM_VERSION=\"18.1.4\" -DAFL_CLANG_FLTO=\"-flto=full\" -DAFL_REAL_LD=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/ld.lld\" -DAFL_CLANG_LDPATH=\"\" -DAFL_CLANG_FUSELD=\"1\" -DCLANG_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang\" -DCLANGPP_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang++\" -DUSE_BINDIR=1 -Wno-unused-function -fdebug-prefix-map="/private/tmp/AFLplusplus=llvm_mode" -Wno-deprecated -I/opt/homebrew/opt/openssl@3/include ./test-instr.c -o test-instr -L/opt/homebrew/opt/openssl@3/lib -L/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib
ASAN_OPTIONS=detect_leaks=0 ./afl-showmap -m none -q -o .test-instr0 ./test-instr < /dev/null
shmat for map: Invalid argument

[-] PROGRAM ABORT : the fuzzing target reports that the shmat() call failed.
         Location : report_error_and_exit(), src/afl-forkserver.c:494

any suggestions?

maybe you should check the args of shmat() and find the root problem? I didn’t meet this problem. I think there is something wrong with your share memory and this can be an AFL++ problem so you can also refer to the issues of AFLplusplus repo.

OK I succeed, because the log shows [*] afl_area_ptr: 0x0 so I just refer to the fuzzer.js and find it fails on the mmap(). So I compile the AFL++ again with CFALGS = "DUSEMMAP"=1，and it works.

hi, add this flag, compile afl++ always show:
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; ASAN_OPTIONS=detect_leaks=0 AFL_QUIET=1 AFL_PATH=. AFL_LLVM_LAF_ALL=1 ./afl-cc -DUSEMMAP=1 -g -Wno-pointer-sign -Wno-variadic-macros -Wall -Wextra -Wno-pointer-arith -fPIC -I include/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -Wall -g -Wno-cast-qual -Wno-variadic-macros -Wno-pointer-sign -I ./include/ -I ./instrumentation/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DLLVM_BINDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/bin\" -DVERSION=\"++4.21a\" -DLLVM_LIBDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/lib\" -DLLVM_VERSION=\"18.1.4\" -DAFL_CLANG_FLTO=\"-flto=full\" -DAFL_REAL_LD=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/ld.lld\" -DAFL_CLANG_LDPATH=\"\" -DAFL_CLANG_FUSELD=\"1\" -DCLANG_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang\" -DCLANGPP_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang++\" -DUSE_BINDIR=1 -Wno-unused-function -fdebug-prefix-map="/private/tmp/AFLplusplus=llvm_mode" -Wno-deprecated -I/opt/homebrew/opt/openssl@3/include ./test-instr.c -o test-instr -L/opt/homebrew/opt/openssl@3/lib -L/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib
ASAN_OPTIONS=detect_leaks=0 ./afl-showmap -m none -q -o .test-instr0 ./test-instr < /dev/null
shmat for map: Invalid argument

[-] PROGRAM ABORT : the fuzzing target reports that the shmat() call failed.
         Location : report_error_and_exit(), src/afl-forkserver.c:494

any suggestions?

maybe you should check the args of shmat() and find the root problem? I didn’t meet this problem. I think there is something wrong with your share memory and this can be an AFL++ problem so you can also refer to the issues of AFLplusplus repo.

hi, thanks for reply, may I know your os version and afl++ version?

OK I succeed, because the log shows [*] afl_area_ptr: 0x0 so I just refer to the fuzzer.js and find it fails on the mmap(). So I compile the AFL++ again with CFALGS = "DUSEMMAP"=1，and it works.

hi, add this flag, compile afl++ always show:
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; ASAN_OPTIONS=detect_leaks=0 AFL_QUIET=1 AFL_PATH=. AFL_LLVM_LAF_ALL=1 ./afl-cc -DUSEMMAP=1 -g -Wno-pointer-sign -Wno-variadic-macros -Wall -Wextra -Wno-pointer-arith -fPIC -I include/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -Wall -g -Wno-cast-qual -Wno-variadic-macros -Wno-pointer-sign -I ./include/ -I ./instrumentation/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DLLVM_BINDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/bin\" -DVERSION=\"++4.21a\" -DLLVM_LIBDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/lib\" -DLLVM_VERSION=\"18.1.4\" -DAFL_CLANG_FLTO=\"-flto=full\" -DAFL_REAL_LD=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/ld.lld\" -DAFL_CLANG_LDPATH=\"\" -DAFL_CLANG_FUSELD=\"1\" -DCLANG_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang\" -DCLANGPP_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang++\" -DUSE_BINDIR=1 -Wno-unused-function -fdebug-prefix-map="/private/tmp/AFLplusplus=llvm_mode" -Wno-deprecated -I/opt/homebrew/opt/openssl@3/include ./test-instr.c -o test-instr -L/opt/homebrew/opt/openssl@3/lib -L/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib
ASAN_OPTIONS=detect_leaks=0 ./afl-showmap -m none -q -o .test-instr0 ./test-instr < /dev/null
shmat for map: Invalid argument

[-] PROGRAM ABORT : the fuzzing target reports that the shmat() call failed.
         Location : report_error_and_exit(), src/afl-forkserver.c:494

any suggestions?

maybe you should check the args of shmat() and find the root problem? I didn’t meet this problem. I think there is something wrong with your share memory and this can be an AFL++ problem so you can also refer to the issues of AFLplusplus repo.

hi, thanks for reply, may I know your os version and afl++ version?

My computer is not handy，maybe macos 13.x.x... and I really forget the afl version

OK I succeed, because the log shows [*] afl_area_ptr: 0x0 so I just refer to the fuzzer.js and find it fails on the mmap(). So I compile the AFL++ again with CFALGS = "DUSEMMAP"=1，and it works.

hi, add this flag, compile afl++ always show:
[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; ASAN_OPTIONS=detect_leaks=0 AFL_QUIET=1 AFL_PATH=. AFL_LLVM_LAF_ALL=1 ./afl-cc -DUSEMMAP=1 -g -Wno-pointer-sign -Wno-variadic-macros -Wall -Wextra -Wno-pointer-arith -fPIC -I include/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DDOC_PATH=\"/usr/local/share/doc/afl\" -Wall -g -Wno-cast-qual -Wno-variadic-macros -Wno-pointer-sign -I ./include/ -I ./instrumentation/ -DAFL_PATH=\"/usr/local/lib/afl\" -DBIN_PATH=\"/usr/local/bin\" -DLLVM_BINDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/bin\" -DVERSION=\"++4.21a\" -DLLVM_LIBDIR=\"/opt/homebrew/Cellar/llvm/18.1.4/lib\" -DLLVM_VERSION=\"18.1.4\" -DAFL_CLANG_FLTO=\"-flto=full\" -DAFL_REAL_LD=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/ld.lld\" -DAFL_CLANG_LDPATH=\"\" -DAFL_CLANG_FUSELD=\"1\" -DCLANG_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang\" -DCLANGPP_BIN=\"/opt/homebrew/Cellar/llvm/18.1.4/bin/clang++\" -DUSE_BINDIR=1 -Wno-unused-function -fdebug-prefix-map="/private/tmp/AFLplusplus=llvm_mode" -Wno-deprecated -I/opt/homebrew/opt/openssl@3/include ./test-instr.c -o test-instr -L/opt/homebrew/opt/openssl@3/lib -L/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib
ASAN_OPTIONS=detect_leaks=0 ./afl-showmap -m none -q -o .test-instr0 ./test-instr < /dev/null
shmat for map: Invalid argument

[-] PROGRAM ABORT : the fuzzing target reports that the shmat() call failed.
         Location : report_error_and_exit(), src/afl-forkserver.c:494

any suggestions?

maybe you should check the args of shmat() and find the root problem? I didn’t meet this problem. I think there is something wrong with your share memory and this can be an AFL++ problem so you can also refer to the issues of AFLplusplus repo.

hi, thanks for reply, may I know your os version and afl++ version?

Maybe you can try build an mmap demo to test the shared memory on your computer？And update your Clang or follow some advice such as https://github.com/search?q=repo%3AAFLplusplus%2FAFLplusplus+shm&type=issues

repo: ttdennis/fpicker


text:
chore(deps): update renovate/renovate docker tag to v35.25.0

This PR contains the following updates:

Package
Update
Change

renovate/renovate
minor
35.24.3 -> 35.25.0

Release Notes

renovatebot/renovate
v35.25.0
Compare Source
Features

manager/bitbucket-pipelines: support docker image object (#21102) (34b5401)

v35.24.6
Compare Source
Bug Fixes

merge config constraints over package file extracted constraints (#21207) (0b79b3d)

Miscellaneous Chores

use node: protocol imports (#21181) (176282e)

v35.24.5
Compare Source
Build System

deps: update dependency cacache to v17.0.5 (#21214) (c87d84c)

v35.24.4
Compare Source
Bug Fixes

onboarding: force branch creation to prevent diff-check (#21200) (874cfe8)

Miscellaneous Chores

deps: update dependency @types/node to v18.15.10 (#21203) (39493b7)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 4.4.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: tubenhirn/dagger-ci-modules


text:
As a player, I want multiple tabs in my character sheet app, So that I can navigate between my home page, inventory page and hireling page.

As a player,
I want multiple tabs in my character sheet app,
So that I can navigate between my home page, inventory page and hireling page.
Acceptance criteria

[ ] Posso navegar entre as páginas com gesto de swipe.
[x] O menu com os icones e os nomes das paginas em baixo desaparece se eu rolo.
[x] Posso navegar entre as paginas pelo menu em baixo.
[x] Adicionada home page.
[x] Adicionada inventory page.
[x] Adicionada hireling page.

Definition of Done:

[x] All acceptance criteria are met.
[x] Code is reviewed and approved.
[ ] Necessary tests are written and pass.
[x] Documentation is updated, if applicable.
[x] Feature is deployed.

Notes

Bottom tab bar.

Mockup

Wireframe

Closed by cd93ed45dc9c180c74ca13d49112caa38e73e1b0

repo: tucozz/project-rataiada

license: Unlicense


text:
User-initialized C++ references return NULL to Java

In the native-defined C++ object that creates a Java object to be returned to the JVM, env-NewObject(..) returns NULL.

Resolved


text:
Update README.md

you’ve forgot to change four to five.

Thanks for your kind remind.


text:
chore: inline format args

Applied auto-clippy fix and some manual minor cleanup:
cargo clippy --all-features --benches --examples --tests --workspace --fix -- -A clippy::all -W clippy::uninlined_format_args

Merged :)

authors: joshka nyurik

repo: tui-rs-revival/ratatui