text:
MB-15996 use Reference ID instead of payment request in BX EDI segment

Jira ticket
Summary
This uses Reference ID instead of payment request in BX EDI segment. To test, use the acceptance testing syncada doc.
There will now be a 4digit - 4 digit reference ID now (see example in screenshot)
Move RDY4PY will work as long as you go in to 'review service items' as a TIO and approve at least one of them.

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

Access the
Login as a

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

Messages

:book:
:link: MB-15996

  Generated by :no_entry_sign: dangerJS against c3023b2fe3f7212266db83134f679b1c2a1d6cd2

authors: mandaem robot-mymove


text:
B 18882 int add search capability for too & tio

Referencing issue: B-18882
Summary
Added capability for TOO and TIO to be able to search for Moves
How to test
Prerequisite: Create a move outside of the TOO/TIO GBLOC. Complete move until they populate the queues of TOO/TIO.
TOO:

Login as TOO
pick a Move Code, DOD ID, and Name from the first queue for later
Click the Search tab
Run a search by default (customer name) using tåhe name from earlier, only moves with that name should show
Click on status (Verify that these Draft, New Move, Needs Counseling, Service Counseling completed, Move Approved exist)
Click on one or any combination to filter down to the move statuses as shown
Click on any of the move(s) that have shown after filtering
Go back to the search queue
You should be able to see the move you created outside of the GBLOC
Use the move code from earlier to run another search, verify only moves with that move code show
Run the move again using DOD ID as an option, only moves with this ID should show.
See: Testing Move Search Validation (This only needs to be tested once as this form is shared)

TIO:

Login as TIO
pick a Move Code, DOD ID, and Name from the first queue for later
Click the Search tab
Run a search by default (customer name) using the name from earlier, only moves with that name should show
Click on status (Verify that these Draft, New Move, Needs Counseling, Service Counseling completed, Move Approved exist)
Click on one or any combination to filter down to the Payment Request statuses as shown
Click on any of the move(s) that have shown after filtering
Go back to the search queue
Use the move code from earlier to run another search, verify only moves with that move code show
Run the move again using DOD ID as an option, only moves with this ID should show.

ADDENDUM 03/28/24 (bug fix added from 18881):

Login as Service Counselor
Click on the status filter and check that only 'Needs counseling' and 'Service counseling completed' exist as options
Select these options at least once, can be in any combination concurrently, but all must have been selected at least once.
pick a Move Code, DOD ID, and Name from the first queue for later
Click the Search tab
Run a search by default (customer name) using the name from earlier, only moves with that name should show
Click on status filter dropdown and verify that these Draft, New Move, Needs Counseling, Service counseling completed, and Move Approved exist
Click on any of the move(s) that have shown after filtering, its details should show
Go back to the search queue
Use the move code from earlier to run another search, verify only moves with that move code show
Run the move again using DOD ID as an option, only moves with this ID should show.

Testing Move Search Validation:

For searching with move code, verify that an error occurs if a move code < 6 characters or > 6 characters fails validation, including whitespaces
Do a search for move code, with a whitespace after, move search should be unaffected
Switching between MoveCode,DOD ID, or Customer Name should clear out the text field
DOD ID length must == 10. Validation error should occur any other time.
Customer name should present a validation error if empty only (or is whitespace).

I am not able to get this running locally, likely due to the ampersand in your branch name. Any way you can take that out? I get this error:
make client_run
REACT_APP_GIT_COMMIT=7f73d03697de5dd2a470e857959b4a708529ca7f \
        REACT_APP_GIT_BRANCH=B-18882-INT-Add-search-capability-for-TOO-&-TIO \
        HOST=milmovelocal \
        yarn start
/bin/sh: -TIO: command not found
make: *** [client_run] Error 127

Not without rebuilding the entire PR

source: gharchive/pull-request

authors: danieljordan-caci joeydoyecaci

repo: transcom/mymove

license: MIT

license_type: permissive

license_source: github-api


text:
Add a docker-compose to run server_test in circleci locally

Description
Trying to see if we can run server_test in a circleCI container locally
Setup
docker-compose -f docker-compose.circle.yml --compatibility up server_test

NOTE You'll want to run make clean after the above as it uses your local dir as a volume
Code Review Verification Steps

[x] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change
this article explains more about the approach used.

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

I've updated the PR with the changes you noted and the configuration. The test does fail when I run it locally, can you confirm if that is what you see as well.

I've updated the PR with the changes you noted and the configuration. The test does fail when I run it locally, can you confirm if that is what you see as well.

What was missing was a bunch of environment variables. But once I sorted that bit I got things passing locally.  Fortunately I also noticed that we could get some test failures of the exact same sort we're seeing in CircleCI with your branch. So we're one track.
Additionally, I found out we aren't doing the right thing with our env vars for these tests anyway so I think I've updated it correctly in CircleCI. I'll keep an eye on it. I may also decrease the resources for this docker-compose file of yours and see what that does.

I checked out the changes look good, though that's a lot of environment variables. I ran the test a couple of times locally and got one passing and one failing run, so I agree we have a way to replicate the issue. I did try the following but still had a pass and a fail so I don't think it's specific to the image.
   server_test:
-    image: trussworks/circleci-docker-primary:e5c10bf19185aa55354901106bad3ffd4c016265
+    #image: trussworks/circleci-docker-primary:e5c10bf19185aa55354901106bad3ffd4c016265
+    image: golang:1.12

I checked out the changes look good, though that's a lot of environment variables.

Yeah, the server_tests in the pkg/cli/ directory should really be more complete. But for now they just read from the environment directly and do checks. We can fix that but I don't think anyone has had the time to make it a priority.

I ran the test a couple of times locally and got one passing and one failing run, so I agree we have a way to replicate the issue.

I agree. This is good work!

I did try the following but still had a pass and a fail so I don't think it's specific to the image.
   server_test:
-    image: trussworks/circleci-docker-primary:e5c10bf19185aa55354901106bad3ffd4c016265
+    #image: trussworks/circleci-docker-primary:e5c10bf19185aa55354901106bad3ffd4c016265
+    image: golang:1.12

That's good to know. I'd wait on merging this until the go1.13 PR gets merged in and then let's update the primary image here too.

authors: chrisgilmerproj gidjin


text:
🛑 TechinAsia_WordPress_API is down

In 668fd19, 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 00255f9 after 8 minutes.

source: gharchive/issue

repo: traqy/upptime


text:
🛑 TechinAsia is down

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

HTTP code: 403
Response time: 928 ms

Resolved: TechinAsia is back up in b3b3a16 after 20 minutes.


text:
🛑 TechinAsia_WordPress_API is down

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

HTTP code: 403
Response time: 227 ms

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


text:
🛑 TechinAsia_Laravel_API is down

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

HTTP code: 403
Response time: 223 ms

Resolved: TechinAsia_Laravel_API is back up in f2d04e5 after 7 minutes.


text:
🛑 TechinAsia is down

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

HTTP code: 403
Response time: 957 ms

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


text:
🛑 TechinAsia_Laravel_API is down

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

HTTP code: 403
Response time: 171 ms

Resolved: TechinAsia_Laravel_API is back up in f9f4540 after 19 minutes.


text:
🛑 TechinAsia_WordPress_API is down

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

HTTP code: 403
Response time: 172 ms

Resolved: TechinAsia_WordPress_API is back up in 2df52f2 after 7 minutes.


text:
Pull request for python-pygments

For travis-ci//travis-ci#4244.
Ran tests and found no setuid bits.
See https://travis-ci.org/travis-ci/apt-whitelist-checker/builds/72050176

Sorry, but this test will have to be re-run. Will open a new one later.

repo: travis-ci/apt-package-whitelist

license: mit

license_source: bigquery


text:
ubantu 18 can not get .deb

dpkg: error: cannot access archive 'wewechat-1.1.7-amd64.deb': No such file or directory

down

repo: trazyn/weweChat


text:
🛑 PROD-Apolo is down

In 3325877, PROD-Apolo (https://api-prod.treant.io/health/apolo) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PROD-Apolo is back up in 7778df1.

repo: treant-io/status


text:
Support location in bq operator

Set Job location for non-US location.
Fixes #1088

@yoyama can you review this PR?

@tkawachi Thank you for your contribution.
I left comments, please check them.
In addition, adding integration tests is preferred.
https://github.com/treasure-data/digdag/blob/master/digdag-tests/src/test/java/acceptance/td/BigQueryIT.java

Thank you for your review, @yoyama.
I have added the integration test, but for the extract and load tests, the location of the BigQuery and GCS bucket must match. Currently, I suppose US bucket is set as GCS_TEST_BUCKET, but in addition to this, bucket of other location is needed.
If you can create the bucket for me, I will write an integrated test for extract and load. Since we used asia-northeast1 in other tests, a bucket for asia-northeast1 might be desirable.

@yoyama I wrote tests for load and extract. It assumes that GCS_TEST_BUCKET_ASIA is in asia-northeast1, not asia (BigQuery can't be located in asia).  Where can I check the test result of CircleCI?

@tkawachi I pushed your PR to digdag repo to run CircleCI.
It failed as follows.
https://app.circleci.com/pipelines/github/treasure-data/digdag/718/workflows/237633a7-4be4-4697-8e66-45195f1505b3/jobs/4699/parallel-runs/1?filterBy=ALL
Could you confirm it ?

@tkawachi I add a minor comment. Could you confirm it ?

I updated the docs. I didn't change bq_ddl.md since it already mentions about location.

Hello @tkawachi
Thank you for your great PR and contribution to digdag!
We are really appreciated with your efforts.
We would like to deliver some TD/Digdag swag to you as a token of our appreciation.
If you don't mind, could you fill your address in the following Google form? So that we can send to you.
https://forms.gle/37jhNBFJo9kyLvLx9

authors: tkawachi toru-takahashi yoyama

repo: treasure-data/digdag


text:
Automate Workgroup Meeting -  Monday, 18th September, 2023

Attendees

[x] Andre
[x] Stephen
[x] Miro

Meeting Action Notes

Don't close the issue after meeting as the GitHub action needs an open issue with the label 'meeting' in order to make the new meeting issue.
Record Action items in the body of each issue for these auto-generated meeting issues.
Include what the Action Item is and a link to the meeting issue from which it was raised
Mark Action Items as complete using the check box and then delete in the next meeting

Review Action items from previous meeting

[ ] Check removed \ADA Due\ label from Meeting GitHub is still absent - Meeting - @Andre-Diamond
[ ] Check Meeting GitHub Action does not create \ADA Due\ label - Meeting  - @Andre-Diamond
[ ] Change Meeting GitHub Action label from \F8 Automate Educate Communicate\ to \Automate Workgroup\ label - Meeting  - @Andre-Diamond
[ ] Create Meeting issue in SNET Archive Workgroup with this format - Meeting - @stephen-rowan

Template for Agenda & Summary

The first comment underneath the body should be a brief Agenda
The second comment should be a brief summary of the meeting content

Previous in series: #134

Next in series: #137

repo: treasuryguild/Automate-Workgroup


text:
Treasury Advisory Service Meeting -  Monday, 17th October, 2022

Attendees

[x] Andre
[x] Stephen
[ ] Miro

Notes
1) F8: ABC of Governance

GitBook : Not released
Project Board : https://github.com/orgs/treasuryguild/projects/1/views/1
Monthly Report - https://github.com/treasuryguild/Treasury-Advisory-Service/issues/61
Obsidian costs - https://github.com/treasuryguild/Treasury-Advisory-Service/issues/33

2) F8: Open Source Development Ecosystem - Automate, Educate, Communicate

GitBook : https://quality-assurance-dao.gitbook.io/treasury-advisory-service/
Project Board : https://github.com/orgs/treasuryguild/projects/1/views/1
https://github.com/treasuryguild/Treasury-Advisory-Service/issues/35

Rough Notes
F8 ABC of Governance

[ ] To do item

F8: Open Source Development Ecosystem - Automate, Educate, Communicate

[ ] To do item

General
ADA DUE
Added issue to create ADA DUE GitHub Action. (https://github.com/treasuryguild/Treasury-Advisory-Service/issues/57)

This raises the question of how we should be using our ADA DUE/ADA PAID issues
How to use for reporting ?
How to use to for payments ?

Previous in series: #78

Next in series: #80

repo: treasuryguild/Treasury-Advisory-Service


text:
feat: add Node.Equals

Adds the missing ts_node_eq:
https://github.com/tree-sitter/go-tree-sitter/blob/5432ade78ad6bde797bcdaa272a5953eaba83971/include/tree_sitter/api.h#L684

thanks!

repo: tree-sitter/go-tree-sitter


text:
Fix some operators' precedence/associativity

See #37. This PR:

Gets rid of unused precedence levels
Introduces new precedence levels for or, xor, and, assignment, ??, |, ^, &, equality (==, !=, <=>, ...) vs inequality/comparison operators (>, <=, ...), and instanceof
Sets corresponding operators at the correct precedence
Makes assignment and compound/augmented assignment right-associative operators
Makes instanceof a left-associative operator
Makes ?? a right-associative operator
Formats a few unit test expected outputs to make diffing easier
Updates said unit tests to reflect the above changes
Changes conditional expressions (e ? e : e) from right-associative to left-associative (see example 1 here) and updates relevant unit tests
Adds more unit tests to expressions.txt to test some common edge cases in PHP

In general, I tried to adhere to the formal grammar and only rely on the docs when necessary.

Also I'm not sure if I should re-run tree-sitter generate as part of this PR

I'm not sure if I should re-run tree-sitter generate as part of this PR

Yeah, you should. We keep the generated code in the repo.

Done. Not sure why the build is failing. Looks like the same errors as in https://github.com/tree-sitter/tree-sitter/issues/362

I was able to get the Travis build working by pinning the Node version to 11. Tried doing the same for Appveyor but it gives the same error.
Btw I'd like to see this merged. Is there anything more I can do to help?

@KevOrr Thanks so much for this, and sorry that it’s been languishing. Can we start with merging https://github.com/KevOrr/tree-sitter-php/pull/1 into this repo? Once that lands, these builds should go green, I think.

Oh KevOrr#1 was me trying to get these two builds working. Doesn't seem to fix the AppVeyor build though. If you want to merge that PR, it's based off of this PR, but should be able to be cherry-picked

@KevOrr This should pass the builders when you merge in master, since #40 has been merged.

@patrickt Awesome! Rebased on top of master

authors: KevOrr maxbrunsfeld patrickt

repo: tree-sitter/tree-sitter-php


text:
Support s3 gateway and webui on different ports

In Minio, the s3 gateway and webui are setup on two different ports, which makes it possible to use the s3 gateway without a domain.
Is it possible to have a config item so that the s3 gateway can be exposed to another port, and also do not use hostname checking when receiving s3 client requests if the extra port is configured?
This may help local development since it's not easy to setup wildcard dns records (*.s3.lakefs.example.com) locally unless a local dns server is installed, since we can not set wildcard hosts in /etc/hosts.

Hi @tc-imba,
This is a common request that is very understandable. So I shall try to write it up here. DNS configuration is required to support the full S3 protocol, also if using minio. See the full thread here: minio/minio#4681.
The underlying issue is that S3 host based addressing rputs the

suggested action
Document the whole addressing style saga explicitly (@peacing : is this a FAQ? An "advanced"  explanation? Something else?), and close. The separate endpoints are not a solution to this afaict.

Thanks for your explanation. Now I understand why the domain is necessary in lakefs.
I'm using rclone which seems only support the sub domain style apis, so I have to setup dns. I can't find any information in the docs about how to set up dns on localhost. dnsmasq can be a good choice, but the configuration is still quite complex. Instead of using it, I finally discovered that the aliases feature in docker network can simply setup dns records (which supports subdomains). In docker-compose.yml, we can write:
lakefs:
  image: treeverse/lakefs:0.46.0
  container_name: lakefs
  ports:
    - "8000:8000"
  environment:
    LAKEFS_GATEWAYS_S3_DOMAIN_NAME: s3.lakefs.example.com:8000
  networks:
    default:
      aliases:
        - s3.lakefs.example.com

Then in other containers in the default network, we can access the s3 api endpoint though http://s3.lakefs.example.com:8000 and the subdomains (*.s3.lakefs.example.com) will be automatically handled by docker network. The web gui and api endpoints can still be accesed through http://lakefs:8000 in the containers, or through http://localhost:8000 on the host machine.
Maybe this will be helpful to someone who also needs a devlopment server on localhost. Is it possible to include a config like this in the docs?

Thanks for your explanation. Now I understand why the domain is necessary in lakefs.

I know, it is unfortunate.

I'm not purely on localhost, I'm using rclone in a container within the same docker network of lakefs, but it seems that rclone only support the sub domain style apis, so I have to setup dns. I can't find any information in the docs about how to set up dns in docker. dnsmasq can be a good choice, but the configuration is still quite complex. Instead of using it, I finally discovered that the aliases feature in docker network can simply setup dns records (which supports subdomains). In docker-compose.yml, we can write:
lakefs:
  image: treeverse/lakefs:0.46.0
  container_name: lakefs
  ports:
    - "8000:8000"
  environment:
    LAKEFS_GATEWAYS_S3_DOMAIN_NAME: s3.lakefs.example.com:8000
  networks:
    default:
      aliases:
        - s3.lakefs.example.com

What docker version is this, please?  When I try the same on my system I do get s3.lakefs.example.com, but not its subdomains.  I would obviously very much like to be able to run this...
However, note that AFAICT rclose uses path-style addressing by default.  Which means the above should just work.

Then in other containers in the default network, we can access the s3 api endpoint though http://s3.lakefs.example.com:8000 and the subdomains (*.s3.lakefs.example.com) will be automatically handled by docker network. The web gui and api endpoints can still be accesed through http://lakefs:8000 in the containers, or through http://localhost:8000 on the host machine.

Maybe this will be helpful to someone who also needs a devlopment server on localhost. Is it possible to include a config like this in the docs?

Please let me know if you can ascertain that the above configuration works.  Perhaps you could disable path style, maybe try
export  RCLONE_S3_FORCE_PATH_STYLE=false
rclone ...

and see whether that still works?

Please let me know if you can ascertain that the above configuration works. Perhaps you could disable path style, maybe try
export  RCLONE_S3_FORCE_PATH_STYLE=false
rclone ...

and see whether that still works?

Thanks, this works.

What docker version is this, please? When I try the same on my system I do get s3.lakefs.example.com, but not its subdomains. I would obviously very much like to be able to run this...

After a further test, I find out that the subdomain network doesn't work in docker. The reason why I successfully execute rclone in the container is that the rclone verison is v1.45 in the container while it is v1.56 on my host machine. I think the default value of RCLONE_S3_FORCE_PATH_STYLE has been changes in certain version of rclone.
Sorry for the misleading on docker subdomain network, but at least it works for path-style routing and it's enough for development usage as long as lakefs doesn't drop support for path-style.

Cool!  AFAICS even AWS cannot drop path-style for the foreseeable future.  See the note at the top of https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/ for the latest on their progress in dropping support for this (spoiler: I am not holding my breath...).
@tc-imba can we close this issue?

With the DNS now optional and path-style support in AWS not going away soon, I'm closing this issue. @tc-imba reopen if you think this is still needed.

authors: arielshaqed itaiad200 tc-imba

repo: treeverse/lakeFS


text:
Fix a spelling mistake in README.md for Levenshtein Distance

Fix for https://github.com/trekhleb/javascript-algorithms/issues/311

authors: nirvanarsc sushruth

repo: trekhleb/javascript-algorithms


text:
EQC model failed

Problem
EQC model failed:
[{model,test_eqc},
 {set,{var,1},{call,test_eqc,let_local,[[],<<"bedebcc">>,{int,1}]}},
 {set,{var,2},
      {call,test_eqc,expr,
            [[{'let',{local,<<"bedebcc">>},1}],
             {array,[{patch,{record,#{<<"Bg==">> => {local,<<"bedebcc">>}}},
                            [{merge,{record,#{<<"Bg==">> => 2}}}]}]}]}}]

test_eqc:let_local([], <<"bedebcc">>, {int, 1}) -> #{<<"emit">> => 1}
test_eqc:expr([{'let', {local, <<"bedebcc">>}, 1}],
    {array,
       [{patch, {record, #{<<"Bg==">> => {local, <<"bedebcc">>}}},
           [{merge, {record, #{<<"Bg==">> => 2}}}]}]}) ->
  #{<<"emit">> => [#{<<"Bg==">> => 2}]}

Reason:
  Post-condition failed:
  {{model, #{<<"emit">> => [#{<<"Bg==">> => 1}]}}, '!=', {rust, #{<<"emit">> => [#{<<"Bg==">> => 2}]}}}

what is the exact problem

The problem is a bug in the model, the expression tested is:
let bedebcc = 1;
patch {"bg": bedebcc} of
   merge => {"bg": 2}
end

which in the rest version correctly evaluates to:
{"Bg==": 2}

but in the model; evaluates to:
{"Bg==": 1}

So to clarify this is a bug in the test not a bug in the code

which technology or language is used in this bug

Mostly Erlang, @me-diru could probably give some details.

Yes, @rushi-12320. The technology used for testing is called EQC or Erlang QuickCheck. It is used here specifically to test the model aka specification of the scripting language called Script/TremorScript (Which is written in Rust but is inspired from Erlang). The one metioned in the above comment i.e
patch {"Bg==": bedebcc} of
   merge => {"Bg==": 2}
end

is called patch and the documentation can be found here I am not wrong: https://www.tremor.rs/docs/0.12/language/expressions#patch
The tests here generate randomised test cases with respect to the model and check with the Rust version of the same expression to measure it's correctness and if it is working as intended.
In this bug specifically, the Rust version evaluates the expression properly and gives as the desired result
{"Bg==": 2}

But the Script/Model output is not right
{"Bg==": 1}

I highly recommend reading the following blog to understand more about this type of testing and the approach used here.
Do let us know if you have more questions!

authors: Licenser me-diru rushi-12320

repo: tremor-rs/tremor-runtime


text:
[ How to cache API calls ? ]

Hi,
Thanks for the job^^
Like said in the title, How can we cache API calls via retrofit lib please ?
Saw a CacheManager into DIO's lib.
Is this the only way to implement cache via retrofit or is there a real Retrofit's way ?
Thanks in advance.
PS :: dio_http_cache, the lib i mentionned seems not to be maintained anymore... 20 months since last update and not compatible with several updated libs like @jsonannotations etc...
So my question is even more "crucial" ^^
How to set cache for API calls thanks to retrofit ?

copy the dio_http_cache  code

authors: Gobmichet Hu-Wentao


text:
Revert "Add support for json serializable generic types"

Reverts trevorwang/retrofit.dart#282

Was something wrong in the code?


text:
bugfix: limit SQL instance returned to match

There was a bug here from Microsoft's end that would return a list of SQL instances if they are partial matches. For instance, this command when ran to retrieve database 'Test' will return a list if you have multiple databases called 'Test', 'TestTemp', 'TestDev'. The only way I found to fix this issue and keep it running on schedule is if we filter the returned result down again to only be the instance which ends in ";$BkupToRestore" (hence ensuring no prefix AND no postfix) . This worked for my case and I don't envision it would be a breaking change, just a bugfix.

Hi @treytro thanks for sharing this great azure automation ps script. I had a unique case that fell outside of what was being handled. Here's the fix I used. Enjoy!
Thanks again

Oh, also here is the corresponding behavior I encountered that was mentioned by MSFT team as well:
https://github.com/Azure/azure-powershell/issues/13832

Great catch @kaburkett - thank you!

authors: kaburkett treytro

repo: treytro/Samples


text:
Fallback to standard string handling for unknown "format" values

Is your feature request related to a problem? Please describe.
If a string field uses an arbirtrary custom "format" value, as allowed by the OpenAPI spec, it is rejected by the parser.
Describe the solution you'd like
As it is guaranteed to be a string, even if the exact format is unknown, I suggest that the parser should follow the recommended behaviour in the spec and fall back to handling the field as a plain string. This is the behaviour recommended by the specification:

Tools that do not support a specific format may default back to the type alone, as if the format is not specified.

Changes are merged in and will be available in 0.4.2.

authors: acgray dbanty

repo: triaxtec/openapi-python-client


text:
feat: Add extra template arguments option

This is draft to propose adding an option for passing extra arguments to the jinja templates based on the comment here: https://github.com/triaxtec/openapi-python-client/issues/224#issuecomment-782482118
Still requires tests and formatting/cleanup but feedback on if there is interest in this and it's taking the right approach would be appreciated.

I'm not totally clear on what the use-case is for kwargs like that? They're effectively hard-coded values, so why not just include them in the custom template you're using? I assume there's just something here I'm missing 😅.
If we were to do this, I think it makes more sense to put it in the config file since you could use YAML/JSON object notation instead of us having to parse from command line. That sort of depends on how these would be used though I guess.

authors: alexifm dbanty


text:
Feature suggestion for trillium-api: Returning a streaming body

I'd love to write an API function that returns a streaming body. Right now, that requires using conn.set_body directly. If possible, I'd like to return an object that wraps a provider of AsyncRead.
I attempted to implement this, and found it difficult because an object containing trillium::Body can't easily implement Handler, because it needs to give up ownership of the trillium::Body, which it can't do in a function that takes &self.

I think this would make the most sense to add inside of an application, as there isn't currently any distinction between a Handler that's intended to be used once (returned from a trillium-api handler) and a "normal" trillium Handler. Since a streaming body can only be read once, it couldn't have a meaningful definition as a reusable trillium Handler outside of the trillium-api context.
Within an application, however, you can ensure that it's never mounted directly, so you could add something like:
struct StreamingBody(std::sync::Mutex<Option<trillium::Body>>);
#[trillium::async_trait]
impl trillium::Handler for StreamingBody {
    async fn run(&self, conn: Conn) -> Conn {
        conn.with_body(
            self.0
                .lock()
                .unwrap()
                .take()
                .expect("this handler can only be called once"),
        )
    }
}
impl StreamingBody {
    pub fn new(
        async_read: impl futures_lite::AsyncRead + Send + Sync + 'static,
        len: Option<u64>,
    ) -> Self {
        Self(std::sync::Mutex::new(Some(trillium::Body::new_streaming(
            async_read, len,
        ))))
    }
}

pub fn main() {
    trillium_smol::run(trillium_api::api(|_: &mut Conn, (): ()| async move {
        StreamingBody::new(futures_lite::io::Cursor::new("this will be chunked"), None)
    }));
}

Given that I'm just doing it in one place, I ended up calling .set_body and then returning () as the handler. If I end up doing it more than once, I'll probably switch to something reusable like that.

authors: jbr joshtriplett

repo: trillium-rs/trillium


text:
Control Drawer opening using binding

[ ] Add property to open and close Drawer using a binding
[ ] Update documentation/examples

Closing. Functionality best kept as method call.

repo: trimox/angular-mdc-web


text:
Add compare subcommand

Add compare subcommand that allows users to generate plots to compare multiple runs.
Users can provide paths to profile export files using --files CLI option as following
genai-perf compare --files [file, ...]

which will generate a set of plots using these runs as well as pre-filled, default yaml configuration file that users can edit to tweak the plotting parameters.
Users can also directly pass the yaml config file to generate customized plots detailed in the yaml file as following
genai-perf compare --config [YAML file]

General workflow of user can be:

first run genai-perf compare --files [file, ...] that gives plots as well as the initial yaml config file
repeatedly run genai-perf compare --config [YAML file] by tweaking plotting parameters such as title, x and y labels, x and y metrics, and etc.

Would you be able to look into what the most Pythonic way of doing this is? It seems to be that having some functionality be under a subcommand and some functionality would not be the generally suggested approach. I'd also want to see if this messes up the help menu.

Great point. Yeah I am not really satisfied on how the current command/subcommand is structured, and we should definitely look into this (and I think @debermudez has already started the conversation on this). But I think that effort will require more effort than this current PR. I have TMA-1900 ticket to refactor CLI for this.

repo: triton-inference-server/client


text:
Use PyTorch device_interface in do_bench

Removed hard-coded references to "cuda" in the do_bench function of testing.py in favour of using PyTorch's DeviceInterface object
The existing do_bench hard codes references to a cuda device type, making the implementation not flexible to other device types in torch. PyTorch has a DeviceInterface class that is a generic interface to different device types. Using the device interface we can continue using the cuda device by default in do_bench, but the implementation is now flexible to be used with other device types e.g. out-of-tree backends.

The core Triton is a small number of people, and we receive many PRs (thank
you!).  To help us review your code more quickly, if you are a new
contributor (less than 3 PRs merged) we ask that you complete the following
tasks and include the filled-out checklist in your PR description.
Complete the following tasks before sending your PR, and replace [ ] with
[x] to indicate you have done them.

[x] I am not making a trivial change, such as fixing a typo in a comment.

[x] I have written a PR description following these
rules.

[x] I have run pre-commit run --from-ref origin/main --to-ref HEAD.

Select one of the following.

[ ] I have added tests.

/test for lit tests
/unittest for C++ tests
/python/test for end-to-end tests

[x] This PR does not need a test because existing tests in triton exist that exercise the implementation of do_bench.

Select one of the following.

[x] I have not added any lit tests.
[ ] The lit tests I have added follow these best practices,
including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)

Thanks for the heads up @Jokeren! Yes, we should definitely coordinate this.
Could I get input on whether backwards compatibility is something worth accounting for, per https://github.com/triton-lang/triton/issues/4417#issuecomment-2263675109? That's mostly what I've been waiting for.
I should be able to put up a PR for the new benchmark interface within a week.

@abulavin I actually was thinking about your approach initially, but I opted to instead make the autotuner generic and keep do_bench platform-specific because things like do_bench_cudagraph don't fit cleanly into the do_bench code structure. I think having multiple do_bench_{platform} implementations isn't the worst thing, there'll be some code duplication, but that's better than having to shoehorn multiple implementations into the same template. What do you think?

I think having multiple do_bench_{platform} implementations isn't the worst thing

I don't think that's a good idea: do_bench is called directly by pytorch in the Triton inductor backend and that part of the code is device agnostic. (The changes in this PR + updating the callsites in PyTorch to forward the device type is all we need to make it work with our out-of-tree + non-cuda device type torch backend).
If you start having do_bench_{platform} functions then pytorch would have to hardcode some kind of switch / case dispatch with a set list of supported devices.
I think what you described in the other thread would be more sensible: having a default (device agnostic) version which works for all backends with the option for the backends to provide their own do_bench implementation if they want to do things differently. (But at least the default would be that it works).

I don't think that's a good idea: do_bench is called directly by pytorch in the Triton inductor backend and that part of the code is device agnostic. (The changes in this PR + updating the callsites in PyTorch to forward the device type is all we need to make it work with our out-of-tree + non-cuda device type torch backend).
If you start having do_bench_{platform} functions then pytorch would have to hardcode some kind of switch / case dispatch with a set list of supported devices.

PyTorch (Inductor specifically) is moving towards using its own implementation of do_bench, so this should not be an issue on that front: https://github.com/pytorch/pytorch/pull/130926

The changes in this PR + updating the callsites in PyTorch to forward the device type is all we need to make it work with our out-of-tree + non-cuda device type torch backend

It would generally work, but making do_bench properly device-agnostic will require a bit more -- the cache size should be parameterizable. We could handle that with a extra field on DeviceInterface, I suppose, or a flush_cache() method. But the fast_flush option is also device-specific (see https://github.com/triton-lang/triton/pull/840), and we don't have a way of abstracting that out with DeviceInterface since the interface is stateless. Now fast_flush could possibly be removed as a parameter, it seems like it was there for migration purposes, but I could imagine that we would want to pass in other device-specific parameters in the future.

I think what you described in the other thread would be more sensible

I have been describing the same thing in both threads, actually -- each backend would have its own default do_bench implementation, and the autotuner would pick the appropriate one.

the cache size should be parameterizable

Device-aware cache size for L2 flushing is a good (but dangerous) idea; we are adding L2 cache size as an attribute in torch.cuda.get_device_properties (the name is confusing, but this is not Nvidia specific). I say this is dangerous because, depending on your benchmarker, changing the cache flush size can and probably will dramatically affect the benchmarking results (i.e. you can become enter CPU-GPU lock step, and now your benchmarking results are completely false).

Now fast_flush could possibly be removed as a parameter, it seems like it was there for migration purposes,

I agree with this, I can't see any situation in which fast_flush=False is better.

but I could imagine that we would want to pass in other device-specific parameters in the future.

Shouldn't we figure this out first? In my opinion we should first have concrete evidence that, for example, do_bench is slow, inaccurate, or unusable on AMD devices before we go through the effort (and added complexity) of having backends select (or define) their benchmarker. And, if this concrete evidence does exist, we should first try to use that new knowledge to improve the generic do_bench before going down the per-device-benchmarker route.

Shouldn't we figure this out first?

I mean there's value in making things easily extensible, even if you're not using it at the moment. I don't think there's much added complexity here, it just makes the code a little bit less DRY which IMO is not a bad thing in a quickly evolving codebase.
But if we can make the existing do_bench properly generic by removing the fast_flush parameter & making the cache parameterizable, I think having it as the default implementation is clean enough. We should still make do_bench itself a parameter to the autotuner, so we can easily add implementations that use extra parameters (or fewer, in the case of cudagraph benchmarking.) And if we ever need something like fast_flush in the future, we should implement that by creating a copy of do_bench_{device}, rather than shoehorning it into the DeviceInterface. I think having DeviceInterface methods that really only get implemented by one device & are no-ops on all others is pretty ugly, and I want to minimize that.

So to summarize the discussion / next steps:

I think we should land this, it's a step in the right direction (cc @abulavin @Jokeren)
We should remove the fast_flush option (pretty trivial)
We should extend DeviceInterface in PyTorch to support retrieving the last level cache size, then use it in do_bench
Changes to the autotuner will proceed as outlined in #4417

These changes can all proceed concurrently, merge conflicts shouldn't be too hard to resolve. And I think landing things incrementally will make development easier, rather than blocking everything on the new autotuner interface. @Jokeren how does that sound?

We should extend DeviceInterface in PyTorch to support retrieving the last level cache size, then use it in do_bench

We should be very cautious changing the size of the cache flush. I've attempted this before, and the end result was that we could not reliably obtain similar benchmarking results using exact L2 cache size vs. the default 256MB. In experimental runs this did significantly decrease E2E performance of many models.

I see... that's unfortunate :/ I guess we should make cache size a parameter then and default it to 256MB. No need to modify the DeviceInterface after all.

I'm ok with merging

I see... that's unfortunate :/ I guess we should make cache flush size a parameter then and default it to 256MB. No need to modify the DeviceInterface after all.

BTW https://github.com/pytorch/pytorch/pull/132819 just merged, so we could always make this "more" device agnostic by taking max(256MB, L2 cache size), but this isn't really needed just yet

For cross-referencing:

Autotuner PR: https://github.com/triton-lang/triton/pull/4496
fast_flush PR: https://github.com/triton-lang/triton/pull/4485

authors: AnthonyBarbier Jokeren abulavin int3 nmacchioni

repo: triton-lang/triton


text:
ReadMe missing clear steps for install and run project

afetr doing this

I get this

So more steps are required in RedMe file

@th34n1m4l readme is ready to retest

@roman-duck not obviouse how to start/run  project. Should be mentioned in readme file too.

@th34n1m4l I have updated node and yarn instructions
https://github.com/trngl8/triangle-skeleton-demo/pull/219


text:
Bump goreleaser version to fix homebrew warning

Previous versions of goreleaser will generate Homebrew bottles that produce the following warning:
Warning: Calling bottle :unneeded is deprecated! There is no replacement.

ref: https://github.com/goreleaser/goreleaser/pull/2591

thanks, has been merged as part of https://github.com/troian/golang-cross/commit/e91a7f616d7088082bf8255340ec6d3f823fc67f

authors: kunickiaj troian

repo: troian/golang-cross


text:
🛑 PiHole is down

In f11a2c5, PiHole (https://pihole.tronflix.app/admin/login.php) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PiHole is back up in d036bfc after 4 days, 11 hours, 31 minutes.

repo: tronyx/upptime


text:
variant bsd specific themes for pcdm

Folder/file structure created and specific desktop for each port added.  Theme files changed and named accordingly.  This does not include any edits to any port files to take advantage of these themes.  Enterprise theme set to mirror default theme at currnet time.

This issue was moved to trueos/trueos-core#73

repo: trueos/pcdm


text:
PGP key?

What is the PGP key for this project and where are the sig files for the releases? I would like to authenticate the image file on the TrueOS website.
Any help would be appreciated. Thank you!

The PGP key is now on the download page:
https://www.trueos.org/downloads/
ISO's (and the .sig files) are uploading now, should be on download.trueos.org in few hours.

Thank you very much!

repo: trueos/trueos-desktop


text:
The --unlock option may not be working

Per the comment from @elenadimitrova (https://github.com/trufflesuite/ganache-cli/issues/526#issuecomment-395339685), it appeared there are issues with using the --unlock option (at a minimum, by itself).
The version used was 6.1.0 for the below output:
/Users/Elena/colonyNetwork/node_modules/ganache-cli/build/cli.node.js:2
!function(e){var t={};function a(n){if(t[n])return t[n].exports;var r=t[n]={i:n,l:!1,exports:{}};return e[n].call(r.exports,r,r.exports,a),r.l=!0,r.exports}a.m=e,a.c=t,a.d=function(e,t,n){a.o(e,t)||Object.defineProperty(e,t,{configurable:!1,enumerable:!0,get:n})},a.r=function(e){Object.defineProperty(e,"__esModule",{value:!0})},a.n=function(e){var t=e&&e.__esModule?function(){return e.default}:function(){return e};return a.d(t,"a",t),t},a.o=function(e,t){return Object.prototype.hasOwnProperty.call(e,t)},a.p="",a.w={},a(a.s=1301)}([function(e,t,a){try{var n=a(1);if("function"!=typeof n.inherits)throw"";e.exports=n.inherits}catch(t){e.exports=a(1218)}},function(e,t){e.exports=require("util")},function(e,t){e.exports=require("path")},function(e,t,a){"use strict";var n="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e},r=a(1221),c=a(110),i=a(13),f=a(65),o=a(12),d=a(34),s=a(10).Buffer;Object.assign(t,a(438)),t.MAX_INTEGER=new o("ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",16),t.TWO_POW256=new o("10000000000000000000000000000000000000000000000000000000000000000",16),t.SHA3_NULL_S="c5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470",t.SHA3_NULL=s.from(t.SHA3_NULL_S,"hex"),t.SHA3_RLP_ARRAY_S="1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347",t.SHA3_RLP_ARRAY=s.from(t.SHA3_RLP_ARRAY_S,"hex"),t.SHA3_RLP_S="56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",t.SHA3_RLP=s.from(t.SHA3_RLP_S,"hex"),t.BN=o,t.rlp=f,t.secp256k1=c,t.zeros=function(e){return s.allocUnsafe(e).fill(0)},t.zeroAddress=function(){var e=t.zeros(20);return t.bufferToHex(e)},t.setLengthLeft=t.setLength=function(e,a,n){var r=t.zeros(a);return e=t.toBuffer(e),n?e.length<a?(e.copy(r),r):e.slice(0,a):e.length<a?(e.copy(r,a-e.length),r):e.slice(-a)},t.setLengthRight=function(e,a){return t.setLength(e,a,!0)},t.unpad=t.stripZeros=function(e){for(var a=(e=t.stripHexPrefix(e))[0];e.length>0&&"0"===a.toString();)a=(e=e.slice(1))[0];return e},t.toBuffer=function(e){if(!s.isBuffer(e))if(Array.isArray(e))e=s.from(e);else if("string"==typeof e)e=t.isHexString(e)?s.from(t.padToEven(t.stripHexPrefix(e)),"hex"):s.from(e);else if("number"==typeof e)e=t.intToBuffer(e);else if(null===e||void 0===e)e=s.allocUnsafe(0);else if(o.isBN(e))e=e.toArrayLike(s);else{if(!e.toArray)throw new Error("invalid type");e=s.from(e.toArray())}return e},t.bufferToInt=function(e){return new o(t.toBuffer(e)).toNumber()},t.bufferToHex=function(e){return"0x"+(e=t.toBuffer(e)).toString("hex")},t.fromSigned=function(e){return new o(e).fromTwos(256)},t.toUnsigned=function(e){return s.from(e.toTwos(256).toArray())},t.sha3=function(e,a){return e=t.toBuffer(e),a||(a=256),r("keccak"+a).update(e).digest()},t.sha256=function(e){return e=t.toBuffer(e),d("sha256").update(e).digest()},t.ripemd160=function(e,a){e=t.toBuffer(e);var n=d("rmd160").update(e).digest();return!0===a?t.setLength(n,32):n},t.rlphash=function(e){return t.sha3(f.encode(e))},t.isValidPrivate=function(e){return c.privateKeyVerify(e)},t.isValidPublic=function(e,t){return 64===e.length?c.publicKeyVerify(s.concat([s.from([4]),e])):!!t&&c.publicKeyVerify(e)},t.pubToAddress=t.publicToAddress=function(e,a){return e=t.toBuffer(e),a&&64!==e.length&&(e=c.publicKeyConvert(e,!1).slice(1)),i(64===e.length),t.sha3(e).slice(-20)};var b=t.privateToPublic=function(e){return e=t.toBuffer(e),c.publicKeyCreate(e,!1).slice(1)};t.importPublic=function(e){return 64!==(e=t.toBuffer(e)).length&&(e=c.publicKeyConvert(e,!1).slice(1)),e},t.ecsign=function(e,t){var a=c.sign(e,t),n={};return n.r=a.signature.slice(0,32),n.s=a.signature.slice(32,64),n.v=a.recovery+27,n},t.hashPersona

I then testing on 6.1.3 and also experienced erroneous behavior. We will need to investigate this issue further to see what/if there is a problem

Yep, unlock isn't working for me with 6.1.4. Have rolled back to 6.1.0 til this is fixed.

@elenadimitrova's issue appears to have been caused by using the --unlock flag with no argument. We will add error checking to that. Otherwise I've tested the --unlock flag with a proper account argument on the latest release and it's working fine - just a really ugly error message when you don't specify the account to unlock

Is there any update on this issue?

@tpikachu, it looks like I fixed this in #551 which was released in ganache-cli@6.8.3, so this bug should be fixed in the most recent version. If you're still having issues, please open a new issue. Thanks!

authors: andy-mcewan-artos-io benjamincburns seesemichaelj tpikachu

repo: trufflesuite/ganache-cli


text:
bilboa, gamins

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

repo: trunk-io/mergequeue-staging


text:
gurgulation, earthless

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,g]

/trunk merge


text:
everett, consequentially

This pull request was generated by the 'mq' tool

/trunk merge


text:
domainal, anacephalize

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:
feverously, bestudded

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,f]

/trunk merge


text:
distortedly, etherifying

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=[d,e]

/trunk merge


text:
galvanometrical, ampliate

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,g]

/trunk merge


text:
gemma, bhunder

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:
electroscope, bowlful

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,e]

/trunk merge


text:
graphitoidal, avoyership

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,g]

/trunk merge


text:
figures, beautifies

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,f]

/trunk merge


text:
bemired, domiculture

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,d]

/trunk merge


text:
grandaddy, brachyure

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: 30
deps=[b,g]

/trunk merge


text:
enqueue, flacked

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,f]

/trunk merge


text:
defeminisation, cornutus

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:
fertilitate

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=[f]

/trunk merge


text:
dolicholus, bindlet

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,d]

/trunk merge

repo: trunk-io/mergequeue


text:
cowweed, eightsmen

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:
boho, archigenesis

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,b]

/trunk merge


text:
disparting

This pull request was generated by the 'mq' tool

/trunk merge


text:
dictyophora

This pull request was generated by the 'mq' tool

/trunk merge


text:
antiuating, busway

This pull request was generated by the 'mq' tool

/trunk merge


text:
antipopularization, glycin

This pull request was generated by the 'mq' tool

/trunk merge


text:
eliminatory

This pull request was generated by the 'mq' tool

/trunk merge


text:
brabblingly, exemptile

This pull request was generated by the 'mq' tool

/trunk merge


text:
bombylious

This pull request was generated by the 'mq' tool

/trunk merge


text:
functionals, consumpt

This pull request was generated by the 'mq' tool

/trunk merge


text:
gelandesprung, frocked

This pull request was generated by the 'mq' tool

/trunk merge


text:
geylies, dandering

This pull request was generated by the 'mq' tool

/trunk merge


text:
butenes, eradicators

This pull request was generated by the 'mq' tool

/trunk merge


text:
enjamb

This pull request was generated by the 'mq' tool

/trunk merge


text:
encake, bin

This pull request was generated by the 'mq' tool

/trunk merge


text:
cinnyl

This pull request was generated by the 'mq' tool

/trunk merge


text:
guttler

This pull request was generated by the 'mq' tool

/trunk merge


text:
acceptilate, contaminates

This pull request was generated by the 'mq' tool

/trunk merge


text:
coevalness, demoting

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,d]

/trunk merge


text:
angus

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:
discerptibleness, bewwept

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,d]

/trunk merge


text:
encephalosepsis, casebook

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,e]

/trunk merge


text:
galways, diatoric

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:
frequence, creakiest

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,f]

/trunk merge


text:
bryophyta, articulite

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,b]

/trunk merge


text:
bhaktas, gabbling

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:
dicarpellary, anthesteria

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,d]

/trunk merge


text:
catery

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]

/trunk merge


text:
astrand, eternities

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: 20
deps=[a,e]

/trunk merge


text:
equability, chickaree

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:
englobement

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:
geococcyx, cartelization

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:
disdeify

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]

/trunk merge


text:
🛑 dns.avenida is down

In 996961d, dns.avenida (https://dns.avenida.truongsinh.pro/ready) was down:

HTTP code: 0
Response time: 0 ms

Resolved: dns.avenida is back up in 30c1f07 after 1 minute.


text:
Reject promises when they should not be depended on anymore.

For example, when a Node has a mountPromise, we don't care about that mount promise any more if the node is removed from the tree. However, the promise will continue to exist and never be resolved (and those handlers be held forever)? So, when we nullify a node's promises, let's also reject them so those code paths awaiting the promises will be canceled rather than wait indefinitely.

Fixed in cc7c187880759c64d223abd59823c34efdf767e5, 9e8e3bd4425e5df102e53335c2a0ec5b1fa1f41f, af8731cf40ebfe1eb6377741efa98c229db3b5fc, c2700262c545806d5483e2d2cd72dbb0669b465e

repo: trusktr/infamous


text:
release: 1.3.0

1.3.0 (2020-05-19)
Features

Add header component #83 (#102) (4281b11)
Add search component
Add Grid, GridContainer components

Warnings

:warning:

Changes were made to yarn.lock, but no plain text yarn audit output was found in PR description. - Can you run yarn audit in your branch and paste the results inside a markdown code block?

  Generated by :no_entry_sign: dangerJS against 25088296ee2de1467b88e54df9cfb9e5962ea095

authors: suzubara trussworks-infra

repo: trussworks/react-uswds


text:
feat: added font sizes, line heights, heading styles to theme

Related to #784
Signed-off-by: Anton Biriukov anton.biriukov@securekey.com

This change dosen"t impact the current sign up page right ??

This change dosen"t impact the current sign up page right ?? @birtony

It does not:

However, it fixes the dashboard layout, because right now all default width options are missing and the container does not stretch properly @talwinder50

repo: trustbloc/edge-agent


text:
We should probably provide API keys to 3rd party clients

The OIDC browser dance won't suffice for programmatic access. And it might become a hassle to maintain dedicated creds, ala "walker".

API keys would be nice indeed. The downside of that, and we saw that with Drogue, is that there seems to exist no standard alongside OIDC. So basically, we would roll out own key system.
I think there's a benefit in that. But I also think, we have more important things to do today. So relying on confidential OIDC clients (with client id + client secret) should be fine for now.

repo: trustification/trustify


text:
JNI DETECTED ERROR IN APPLICATION

Hello, in my dart plugin when using TrustWalletCore, an error occurs:
java_vm_ext.cc:577]     JNI DETECTED ERROR IN APPLICATION: mid == null
java_vm_ext.cc:577]     in call to CallIntMethod
java_vm_ext.cc:577]     from int wallet.core.jni.BitcoinScript.hashTypeForCoin(wallet.core.jni.CoinType)

Methods for fixes indicated in the issue: https://github.com/trustwallet/wallet-core/issues/961
don't help.
How can this error be corrected?

I was able to run without errors by disabling minification. At the same time, this application, which is so voluminous after connecting the TrustWalletCore library, has increased even more.
Is it possible to split the library into parts?
For example, I use only the functionality of signing transactions

No plan to split the library, it cause a hassle the benefits

repo: trustwallet/wallet-core


text:
Add multi-namespace tests + periodic test designation

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Pull Request title is properly formatted: FAI-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting main: [0.3.x] FAI-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

/retest

/test trustyai-explainability-e2e

/test all

/test trustyai-explainability-e2e

/test trustyai-explainability-e2e

/test trustyai-explainability-e2e

/test all

/test trustyai-explainability-e2e


text:
🛑 Documentation is down

In cedb3c4, Documentation (https://docs-src.tryton.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Documentation is back up in e48874d after 7 minutes.

repo: tryton/upptime


text:
[BUG] Header Validation

Describe the bug
Currently it is not possible to validate Header Params. Is there a reason for this?
See useValidation = false:
https://github.com/tsedio/tsed/blob/1a7451533132a99ebb595516e43aba94ea13f12d/packages/platform/platform-params/src/decorators/headerParams.ts#L39
To Reproduce
Not needed i guess?
Expected behavior
I would expect to be able to validate header params as well 🤔
Code snippets
No response
Repository URL example
No response
OS
macOs
Node version
18.17.1
Library version
7.43.0
Additional context
When i changed useValidation to true in my local fork, the integrations test passes 👍🏼

It’s for a performance reason. Addind validation on header must be explicitely enabled.

Ahh thanks, i know found the documentation here.
Before, i only saw this documentation - maybe would make sense to add the note there as well?

Additional question: Currently i test my schema according to the documentation like this:
const ajv = PlatformTest.get<Ajv>(Ajv);
schema = getJsonSchema(MySchema, { customKeys: true });
validate = ajv.compile(schema);

but this is not calling the AfterDeserialize function (which makes sense because this is a tsed thing instead of a ajv thing i guess? Any idea how i can adjust my test to make use of the function as well?

Use deserialize / serialize from @tsed/json-mapper ;)

authors: EinfachHans Romakita

repo: tsedio/tsed


text:
bad target: http:// what is it and why?

When I run the following comman
echo "http://localhost:9001/config/base/" | vegeta attack -rate=1000 -duration 5s | vegeta report
The error I get is
2016/05/20 12:57:46 bad target: http://localhost:9001/config/base/
When I run
curl http://localhost:9001/config/base/
I get
curl "http://localhost:9001/config/base" {"videos":{"lastupdate":1463198400000,"list":{ ...
Bad Target isn't documented and searching google it appears somehow I am the only one that encountered this issue. What is the issue and what am I doing wrong?

You're missing the HTTP method before the target URL. I suppose you want
GET.
On Fri, 20 May 2016 at 19:01, denisbetsi notifications@github.com wrote:

When I run the following comman
echo "http://localhost:9001/config/base/" | vegeta attack -rate=1000
-duration 5s | vegeta report
The error I get is
2016/05/20 12:57:46 bad target: http://localhost:9001/config/base/
When I run
curl http://localhost:9001/config/base/
I get
curl "http://localhost:9001/config/base"
{"videos":{"lastupdate":1463198400000,"list":{ ...
Bad Target isn't documented and searching google it appears somehow I am
the only one that encountered this issue. What is the issue and what am I
doing wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/tsenart/vegeta/issues/184

Yes, I just realized. That was quick! Thank you

authors: denisbetsi tsenart

repo: tsenart/vegeta


text:
context-free-bot を消したい

導入されて2年近いですが、頻度の割に好かれている印象がなく、正直いるかな? と思っています。
cfp は偉大だと思いますが、cfb についてはない方がいいんじゃないかなあというのが個人的な意見です。皆さまの意見を聞きたいため issue にいたしました。

Discussionに置いてもいいかも? (voteなどができるので)

実際 cfp より cfb のほうが言及頻度高くないかと思っており cfb 賛成派です

cfb、なくても困らないけどあっても邪魔になるほどの頻度でもないし、たまに見知った単語が出て:oxtu:ってなったり自明な単語をわからなかったりして面白いので、結構好きです

cfb、かわいがっています　話の輪に入っているように見えるときが頻繁にあって面白いので
逆にcfpはデメリットがほぼない代わりにさほど頻繁には楽しんでないですね……

cfpが偉大であることを否定するものではないです

博多市先生が素晴らしい Discussion #565 を立ててくれたので、分散を防ぐため、こっちは閉じますね〜。

repo: tsg-ut/slackbot


text:
str(ULID()) infinite recursion

Wanting to try this library, I went in to iPython (Python 3.7) and typed:
from ulid import ULID
ULID()
Output:
~/local/py3env/lib/python3.7/site-packages/ulid/ulid.py in repr(self)
45
46     def repr(self):
---> 47         return "%s(%r)" % (self.class.name, str(self))
48
49     # Function to generate the ulid without monotonicity or ms time handling
RecursionError: maximum recursion depth exceeded while getting the str of an object
Not a critical bug, but thought it worth mentioning, as every other ulid library I tried had some kind of problem and I was about to abandon this one too, but then tried the instructions according to the documentation.

Hi @kcburge ,
Thank you for checking out my library and logging this Issue! I highly appreciate it.
The error stems from an earlier iteration of the program where I had a custom repr function, which is not necessary for the current implementation.
I have now fixed the bug.

authors: kcburge tsmanikandan

repo: tsmanikandan/py-ulid


text:
Add integration tests

create a test organization with some sample data and run integration tests on PRs and pushes.
Use an application for the token

closed with #15

repo: tspascoal/get-user-teams-membership


text:
🛑 Online Document Editor is down

In e4deed9, Online Document Editor ($URL_OFFICE) was down:

HTTP code: 502
Response time: 1268 ms

Resolved: Online Document Editor is back up in a2d0a86.

repo: tsueri/upptime


text:
janguage hard set to japanese

https://github.com/tsuyoshicho/action-redpen/blob/9e52a285eda607b171291d77ba04103bb116ff85/entrypoint.sh#L11

Okay, but -L is error report language, remove it.

Merge and close

authors: jamie-wearsafe tsuyoshicho

repo: tsuyoshicho/action-redpen


text:
Pass macros into nocache

How would I have to write the nocache tag when using a Macro?
{% nocache %}
  {% for asset in header.headerBild.order('RAND()').limit('1') %}
    {{ docMacro.headerImage(asset) }}
  {% endfor %}
{% endnocache %}

I just imported the macro file again:
But is there another sollution like { with: docMacros } or something?
{% nocache %}
  {% import '_incl/docMacros' as docMacro %}
  {% for asset in header.headerBild.order('RAND()').limit('1') %}
    {{ docMacro.headerImage(asset) }}
  {% endfor %}
{% endnocache %}

The Craft 2 version of No-Cache does allow passing a macro variable declaration; something like...
{% nocache with {docMacro: docMacro} %}

...would work.  I think it'd be better to just re-import what you need, though.
With the Craft 3 version, though, any macros to be used within a nocache block must be (re-)imported within the block.

authors: kaspar-allenbach ttempleton

repo: ttempleton/craft-nocache


text:
Graphical Oddities When Typing

Apologies if this has already been reported. For me, it's new to the 2.2 (122) release. I can seem to get it pretty consistently when typing at the beginning of a file. I know that in this case, at least, it's the beginning of a file when there is already text below. Anyway, getting strange dots appearing below typed text.

They seem to randomly fluctuate as I go, then disappear when hitting return and going to the next line. They then show up on the next line as I type again.

@muzll0dr Thanks for the report. Couple questions:
What version of macOS are you using?
What font and font size is that?
Do you use the preference setting to "Keep Note Body Width Readable" (in the Fonts & Colors section)?'
Do you use the "Spelling: Check as you Type" preference setting (in the Editing section)?
Does this happen more frequently when you're notes list is filtered (because you ran a search) or not?
Do you use horizontal or vertical layout (is the notes list above or to the left of the note text)?

Thanks for the response, David. I'm using:

macOS 10.12
Monaco 12
Keep Note Body Width Readable: Unchecked
Spelling: Check as you type: checked
Happens regardless of if the list is filtered
Note list to the left of the note text

Hope that helps.
On Saturday, October 8, 2016 at 4:42 AM, David Halter wrote:

@muzll0dr (https://github.com/muzll0dr) Thanks for the report. Couple questions:
What version of macOS are you using?
What font and font size is that?
Do you use the preference setting to "Keep Note Body Width Readable" (in the Fonts & Colors section)?'
Do you use the "Spelling: Check as you Type" preference setting (in the Editing section)?
Does this happen more frequently when you're notes list is filtered (because you ran a search) or not?
Do you use horizontal or vertical layout (is the notes list above or to the left of the note text)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/ttscoff/nv/issues/395#issuecomment-252417700), or mute the thread (https://github.com/notifications/unsubscribe-auth/ADkZp1YnB_rIj0bCnQi1z-x4R_dG5814ks5qx3N4gaJpZM4KRbxE).

repo: ttscoff/nv


text:
An Error occured: Failed to read large IndexedDB value

so i have my light novels on my mac and i read it from there, when i open a specific book it will open normally. but when i exit at https://reader.ttsu.app/manage the books not there and it has "Failure
An Error occured: Failed to read large IndexedDB value".
{   "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36",   "viewport": {     "visualViewport": true,     "width": 1920,     "height": 955   },   "settings": {     "theme": "light-theme",     "viewMode": "paginated",     "fontFamilyGroupOne": "",     "fontFamilyGroupTwo": "",     "fontSize": 20,     "lineHeight": 1.65,     "firstDimensionMargin": 0,     "secondDimensionMaxValue": 0,     "swipeThreshold": 10,     "disableWheelNavigation": false,     "writingMode": "vertical-rl",     "confirmClose": false,     "autoBookmark": false,     "hideSpoilerImage": true,     "hideFurigana": false,     "furiganaStyle": "partial",     "avoidPageBreak": false,     "customReadingPointEnabled": false,     "selectionToBookmarkEnabled": false,     "pageColumns": 0,     "autoPositionOnResize": true,     "requestPersistentStorage": true,     "cacheStorageData": true,     "autoReplication": "down",     "replicationSaveBehavior": "new",     "showExternalPlaceholder": false,     "gDriveStorageSource": false,     "oneDriveStorageSource": true,     "fsStorageSource": false,     "syncTarget": true,     "isOnline": true,     "multiplier": 20   },   "log": [     {       "level": 4,       "args": [         "Failed to read large IndexedDB value"       ]     }   ] }

hi,
as far i understood it occurs in general/with all books - so sounds unfortunately like an system specific issue which is probably really hard to debug on dev side. Also the *-OS Platform seems to be in general quite iffy when it comes to storing and reading large data often...
I leave this issue open for the time being but for now i can only share some ideas you may could try out as it sounds that your local db may got corrupted or similar:

Check your Storage on which your Browser Profile is stored in terms of capacity - if its low maybe try to move some data temporarily in conjunction with one of the next options
Try to clean the Website Storage - that will all Data and rebuild everything from scratch which may helps. In Chrome it is e. g. in the Developer Tools => Application => Storage

Alternatively/On Top try out a new temporary Profile without Extensions to ensure the root cause is not inside your current Profile

Step 2 in your instructions (clean website storage) solved my problem. Thank you.

Sounds good - as there is no direct work related i will close this issue for now (keeping the error in mind whenever i should encounter it for further analysis)

authors: Renji-XD kimjongbing

repo: ttu-ttu/ebook-reader


text:
fix image upload bug in edit pengaduan

mas ini aku nyoba buat benerin bug upload file di edit data pengaduan.
sama aku mau nanya di task ini itu apakah maksutnya petugas itu hanya bisa melihat pengaduan di tiap kabupaten masing masing?

@MHafizAF iya, petugas kabupaten hanya bisa melihat dan membuat tanggapan hanya di kabupatennya.

authors: MHafizAF tuanpembual

repo: tuanpembual/pengaduan-masyarakat


text:
Error message when creating an already existing topic is too generic

Describe the bug
When using the admin createTopics with an existing topic the following error is logged:

message: Response CreateTopics(key: 19, version: 3)
error: Topic creation errors

We are using Confluent Cloud.
To Reproduce
If none of the above are possible to provide, please write down the exact steps to reproduce the behavior:

Create a topic that already exist using the admin.createTopics

Expected behavior
We would have expected a more specific error message ("topic already exists") to be able to filter it out in our custom logger.
Environment:

OS: Kubernetes, node-buster-slim
KafkaJS version 2.2.3
Kafka version 3.3.x, Confluent Cloud 7.3.x
NodeJS version 18

Any update here, got the error log when passed multiple topics and some of them already existed, others were created succesfully. Also response was false in this case.

{"level":"ERROR","timestamp":"2023-07-14T13:33:41.729Z","logger":"kafkajs","message":"[Connection] Response CreateTopics(key: 19, version: 2)","broker":"","clientId":"kafkajs","error":"Topic creation errors","correlationId":0,"size":504}

repo: tulios/kafkajs


text:
Update scalafmt-core to 3.7.4

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.4.3 to 3.7.4
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:n:3

Superseded by #173.

repo: tulz-app/frontroute


text:
chore(deps-dev): update eslint to v9

Context & Description
Start working on ESLint update to v9.
With this update I'm also planning to remove more any as possibile from the typescript part

That is a great improvement!

I'm going to log a task to remove all the things not used in the router

authors: Valerioageno marcalexiei

repo: tuono-labs/tuono


text:
Feature Request - New Sprite - Apache Ignite

I would like to request a new sprite be added for the Apache Ignite database.
See: https://ignite.apache.org/

I think you can provide a PR with the request by:

creating the icon.png exactly 48x48 pixels.
running plantuml -encodesprite 16 icon.png > result.puml.
add the @startuml prefix before the generated result.puml
add the following suffix at the end of result.puml:

!define DEV2_MYMACRO(_alias) ENTITY(rectangle,black,aftereffects,_alias,DEV2 MYMACRO)
!define DEV2_MYMACRO(_alias, _label) ENTITY(rectangle,black,aftereffects,_label, _alias,DEV2 MYMACRO)
!define DEV2_MYMACRO(_alias, _label, _shape) ENTITY(_shape,black,aftereffects,_label, _alias,DEV2 MYMACRO)
!define DEV2_MYMACRO(_alias, _label, _shape, _color) ENTITY(_shape,_color,aftereffects,_label, _alias,DEV2 MYMACRO)
skinparam folderBackgroundColor<<DEV2 MYMACRO>> White
@enduml

This^ can be automated but would still require the input 48x48 pixel input PNG file.

Icon request has been submitted to Dev Icons: https://github.com/devicons/devicon/issues/1552

authors: Potherca axiopisty mihaigalos


text:
performance & quality drop (3x) when setting top_p = 1.0 vs. 0.99

Performance when generating with top_p = 1.0 is about 3x slower than with top_p at anything(?) else, to duplicate try 0.99 and 1.0.
I've seen this bug with both the exllama gui and the text-gen-webui, a sample performance:
top_p=1.0 Output generated in 27.11 seconds (12.10 tokens/s, 328 tokens, context 49, seed 444648765)
top_p=0.99 Output generated in 11.62 seconds (31.83 tokens/s, 370 tokens, context 49, seed 1821729798)
The top_p=1.0 also seems to produce drastically poorer results sometimes as well... I'm not sure what might be happening there, but here is a looney example from a normally very good model (TheBloke_Wizard-Vicuna-30B-Uncensored-GPTQ):
A chat between a curious user and an artificial intelligence assistant. The assistant gives helpful, detailed, and polite answers to the user's questions.

USER: A recipe for easy chocolate cake.
ASSISTANT: Ingredients:
- 1 cup all-purpose flour
- 1/2 cup granulated sugar
- 3/4 cup unsweetened cocoa powder
- 1 tsp baking soda
- 1 tsp salt
- 1/2 cup vegetable oil
- 50 grams canola oil
- Roughly chopped dark chocolate (at least 6 oz)
- 2 large eggs
- 1 tsp vanilla extract
- 1 cup water
Instructions:
1. Preheat your oven to 350°F (180°C). Grease a 9x13 inch pan with cooking spray or butter and flour.
2. In a medium bowl, mix together the flour, sugar, cocoa powder, baking soda, and salt until well combined. Set aside.
3. In another bowl, whisk together the oil, vegetable oil, eggs, and vanilla extract until creamy. Add wet ingredients into dry ingredients and stir until it’s just moistened. Gently fold rough chopped target="_blank" data-qa="true">
4. Pour batter in greased pan and smooth out top with a spatula or back of most can dipper fan site memory foam side travel marketing pinboard plus ideas epochtransduction credit peaceful solve ways relationship lose bond light building car west rightoffscreen eXtreme target two links and years pondchildhood free online festival style throwMore nobatsevidenc rebate some use joke birdhit sku

In step 4 it just loses it at the end, but it's bad at the end of step 3 also.
This is a typical output (using the same parameters, but with top_p=0.99):
USER: A recipe for easy chocolate cake.
ASSISTANT: Ingredients:
- 1 cup all-purpose flour
- 3/4 cup granulated sugar
- 2 teaspoons baking powder
- 1/2 teaspoon salt
- 1/2 cup unsweetened cocoa powder
- 1 egg
- 1/2 cup milk
- 1/2 cup vegetable oil
- 1 tablespoon vanilla extract
Instructions:
1. Preheat oven to 350°F (175°C). Grease a 9-inch square pan with cooking spray or butter.
2. In a large bowl, whisk together flour, sugar, baking powder, and salt until well combined. Add in cocoa powder and mix again.
3. In another small bowl, beat the egg then add milk, vegetable oil, and vanilla extract. Mix well.
4. Pour wet ingredients into dry ingredients and stir until just combined. Do not overmix.
5. Pour batter into prepared pan and smooth out top with a spatula.
6. Bake for 35-40 minutes or until a toothpick inserted into center comes out clean. Let cool completely before frosting. Enjoy!

Different implementations are going to perform differently in extreme cases. You could also turn up the temperature and magnify any differences that way.
But chasing perfectly deterministic behavior with CUDA gets expensive since you can't use the most efficient parallel algorithms then. And language models are designed to deal with some amount of noise anyway. Dropout during training is essentially just a whole lot of strong, artificial noise added to the network so it learns to be resilient and avoid tipping points where small deviations can have large cascading effects.
And whatever small amount of noise makes it through the model therefore shouldn't change the overall shape of the output, though it might make it a little fuzzier. Fuzziness doesn't matter when you're gating the output anyway, either with top-p or top-k or some other sampling filter, because then you're left with only the part of the distribution that has a high signal-to-noise ratio.
The tail end, where the noise can overshadow the signal, is not what you want to rely on in any case. That's where the model basically goes, "well, if you didn't like any of the two hundred tokens I suggested as the most likely continuation, maybe the next one is, oh, I don't know, 'ham'? Does that make sense in a chocolate cake recipe? Apparently you don't care!"
Those settings also look a little strange if you're going for determinism. with a top-k of 1 the model is as deterministic as it can be (given the non-associative floating point operations as mentioned), and none of the other parameters contribute anything at all. With top-k at 0 and the others at 1, none of the filters do anything, and that's arguably the least deterministic form of sampling.

Thanks for the detailed explanation, it's so much clearer for me now! My headache just went away, lol.

authors: matatonic turboderp

repo: turboderp/exllama


text:
[BUG] CUDA error: invalid configuration argument /exllamav2/exllamav2/exllamav2_ext/cuda/rope.cu 131

Thanks for this excellent work!
When using lora (reproduced in example/lora.py in the repository), the author's 7b configuration works successfully. When I change to 70b, I get the following error "CUDA error: invalid configuration argument /exllamav2/exllamav2/exllamav2_ext/cuda/rope.cu 131 "
This problem only occurs when using streaming=False!
Additionally, there is a memory leak when GPU is not specified (CUDA_VISIBLE_DEVICES)  => other GPUs are about 900M each

I have this problem when passing lora to the forward function.

Do you have a link to a 70B LoRA that causes this?

I tried a bunch over exl2 and gptq models, try https://huggingface.co/jondurbin/airoboros-l2-70b-2.2-checkpoints/tree/main/checkpoint-1000/adapter_model

Yep, so there was a bug for large LoRAs. Miscalculated the size of the launch grid so it would try to launch too many threads. It should correctly fall back on cuBLAS for 70B LoRAs now. I'm not sure about the performance but I will be optimizing that at some point.
Also the streaming generator was just ignoring the LoRA altogether. Both issues should be fixed with the latest commit.

The memory leak was due to the test in compat.py creating an entire CUDA context to test if peer access is supported. I limited it to only testing for devices actually being used, so that should be taken care of also.

Can confirm it is resolved. I can use lora for 70b.

Thanks!

authors: Facico Ph0rk0z turboderp


text:
modification du ficier 'Copy of voice_datprepropcessing'

modification done

Code accepted Good job Reiman.

Good

Thank you
Le 4 févr. 2022 20:39, "Franck Tchouanga" @.***> a
écrit :

Merged #1 https://github.com/turncoffeintocodes/Translator-Tech/pull/1
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/turncoffeintocodes/Translator-Tech/pull/1#event-6011633410,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUCLY2ICY5BW6XGMNTDMMFTUZQTNXANCNFSM5NSPQNYQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***
com>

repo: turncoffeintocodes/Translator-Tech


text:
n-select: dropdown and 'input' not styled from peer theme

TuSimple/naive-ui version (版本)
2.32.2-beta.0
Vue version (Vue 版本)
3.2.37
Browser and its version (浏览器及其版本)
OperaGX LVL4 (core: 89.0.4447.64)
System and its version (系统及其版本)
win 11
Node version (Node 版本)
Reappearance link (重现链接)
https://codesandbox.io/s/laughing-pond-obxd6h?file=/src/Demo.vue
Reappearance steps (重现步骤)

open link
open dropdown
open select

Expected results (期望的结果)
same style for select input and dropdown
Actual results (实际的结果)
select does not apply select input and dropdown stlyes
Remarks (补充说明)
offtopic: somehow the select highlighting is weired in repro

use these two

why isnt InternalSelection and InternalSelectionMenu not defaulting to Input and Dropdown?

and whats this weired highlighting of options (hover effect without hover)

why isnt InternalSelection and InternalSelectionMenu not defaulting to Input and Dropdown? The styles of the selection tags (if multiple) are styled from Tag.
and whats this weired highlighting of options (hover effect without hover)
some props are not overridable (InternalSelection) like boxshadows (i can open seperate issue?)

Input & Internal has many distinctions which makes impossible to merge the style.
Maybe you have value set to undefined
Box shadow is overridable:

why isnt InternalSelection and InternalSelectionMenu not defaulting to Input and Dropdown? The styles of the selection tags (if multiple) are styled from Tag.
and whats this weired highlighting of options (hover effect without hover)
some props are not overridable (InternalSelection) like boxshadows (i can open seperate issue?)

Input & Internal has many distinctions which makes impossible to merge the style.
Maybe you have value set to undefined
Box shadow is overridable:

I think I expressed myself incorrectly.

No value is set to undefined (see sandbox)

box shadow override is there, but its not working!

https://codesandbox.io/s/laughing-pond-obxd6h?file=/src/Demo.vue

For 2 you should provide value field not key or use value-field="key"

For 3 I will check

repo: tusen-ai/naive-ui


text:
Ignore path not working [SLIM 4][POSSIBLE BUG (?)]

I'm trying to ignore the /auth path for login but it's not possible. What i'm doing bad?
Route
$app->group('/api/v1', function (Group $group) {
    $group->post('/auth', RouteCreator::create(['controller' => 'Auth', 'action' => 'login']));
    $group->get('/home', RouteCreator::create(['controller' => 'Home', 'action' => 'home']));
});

JWT Config
return new Tuupola\Middleware\JwtAuthentication([
        'secure' => false,
        'path' => '/',
        'ignore' => [
            '/api/v1/auth'
        ],
        'secret' => $jwtSettings['secret'],
        'error' => function ($response, $arguments) {
            $data = [
                'error' => true,
                'message' => $arguments['message']
            ];

            $response->getBody()->write(json_encode($data, JSON_UNESCAPED_SLASHES | JSON_PRETTY_PRINT));

            return $response
                      ->withHeader('Content-Type', 'application/json');
        }
    ]);

Postman result:

Checking, i see if i put the absolute path, seems it works.
Like this:
/payment_system/web/backend/public/api/v1/auth

I am not sure which server or what kind of setup you are running, but it sounds like $request->getUri()->getPath(); produces something unexpected. You could try debugging that by adding
var_dump($request->getUri()->getPath());

somewhere in your route.  Second thing you could try is to remove the route groups. I usually avoid them since they sometimes tend cause unexpected behaviour.

I am not sure which server or what kind of setup you are running, but it sounds like $request->getUri()->getPath(); produces something unexpected. You could try debugging that by adding
var_dump($request->getUri()->getPath());

somewhere in your route. Second thing you could try is to remove the route groups. I usually avoid them since they sometimes tend cause unexpected behaviour.

Hello,
var_dump($request->getUri()->getPath()); gives: /payment_system/web/backend/public/api/v1/currencies/prices
I've tried without group routing but i get the same error. Trying the same with tuupola/slim-jwt-auth:2.4 works fine, so the fail comes in version 3.5

I see two problems.

You are not requesting the /api/v1/auth path. Instead you are requesting /api/v1/currencies/prices.
Call to $request->getUri()->getPath() is returning the absolute path in filesystem /payment_system/web/backend/public/api/v1/currencies/prices when it should return the request path /api/v1/currencies/prices. The $request object is not created by this middleware, it is created by the Slim framework instead. Why it as the absolute path as request path I do not know.

The code which checks the path for both versions is at:
https://github.com/tuupola/slim-jwt-auth/blob/3.5.0/src/JwtAuthentication/RequestPathRule.php
https://github.com/tuupola/slim-jwt-auth/blob/2.4.0/src/JwtAuthentication/RequestPathRule.php

I see two problems.

You are not requesting the /api/v1/auth path. Instead you are requesting /api/v1/currencies/prices.
Call to $request->getUri()->getPath() is returning the absolute path in filesystem /payment_system/web/backend/public/api/v1/currencies/prices when it should return the request path /api/v1/currencies/prices. The $request object is not created by this middleware, it is created by the Slim framework instead. Why it as the absolute path as request path I do not know.

The code which checks the path for both versions is at:
https://github.com/tuupola/slim-jwt-auth/blob/3.5.0/src/JwtAuthentication/RequestPathRule.php
https://github.com/tuupola/slim-jwt-auth/blob/2.4.0/src/JwtAuthentication/RequestPathRule.php

/api/v1/currencies/prices It was an example. The same happenes with /api/v1/auth and with every route. I think the fail as you said, comes from Slim V4. I will check the base path parameter of framework.
Thank you.

authors: samyan tuupola

repo: tuupola/slim-jwt-auth


text:
Critical vulnerabilities in JSON Web Token libraries - Covered?

Since i have your implementation in many webapps... is this vulnerability covered?
https://www.chosenplaintext.ca/2015/03/31/jwt-algorithm-confusion.html
Greets Marcus

Just seen that it was March 2015...  I guess it is covered already. Please close if it has no relevance.

Yes. See https://github.com/tuupola/slim-jwt-auth/commit/69ab6a25bbb0c22c941fd319cc53bc3eacda9df5 which fixes the problem.

Nice! Thanks for the fast reply (again) ;)

authors: derpoho tuupola


text:
Add memory concept

Let's discuss possible approaches here.
Regardless of how we eventually implement the memory concept, it has to introduce new signal(s) or expand the state space in another way. Otherwise, if the state space is not affected, we will not be able to distinguish states with encoding conflicts.
The most natural way to expand the state space is to introduce a new signal, just like this is done with CSC resolution methods working at the STG level.
Newly introduced signals may be hidden from the rest of the system, so that other concepts could not directly affect their behaviour. The memory concept will be solely in charge of the associated signals.

While we have discussed some memory for constructs such as a toggle circuit, I have done some work with a VME bus controller, specifically on paper, with the read and write cycles separately, attempting to find where CSC conflicts arise, and how to correct these by introducing internal signals, and then how these could be automatically detected.
Combining these has proven to be a little more difficult, but it could be possible to combine the separate cycle scenarios before adding any CSC conflict resolution, and then re-detect and correct any conflicts.
Either way, this proves to be very different to the hypothetical working of a toggle concept, and while I hoped that working with the VME bus controller might be revealing for the possible implementation of a toggle circuit, I feel a toggle circuit may need a separate implementation.
We have a meeting later this week in which I will present my findings with the VME bus controller, or as mentioned in another issue, we can set up a separate meeting if you wish with this and issue #21 as the main focus.

authors: jrbeaumont snowleopard

repo: tuura/concepts


text:
Make Spreedly::client() public so we can access the raw Guzzle interface for calls this library doesn't natively support

This allows you to use payment method distribution functions, which are not natively defined by this library.

Thanks

authors: jcherniak tuurbo

repo: tuurbo/spreedly


text:
🛑 Gollum is down

In a551392, Gollum (https://wiki2.eighty-three.me) was down:

HTTP code: 404
Response time: 454 ms

Resolved: Gollum is back up in 64b5000.

repo: tuxpeople/monitoring


text:
Information on a few Treatlife switches

Hey guys, bought a bunch of switches and used this tool to cut the cloud connection, will be flashing libretuya tomorrow. Figured it would be good to add the profiles that worked for them. Had some trouble with this tool the last time I used it, but it was smooth sailing this time. That trick about using tuya-convert's startup script to kill services holding ports was golden, worked a treat this time too.

DS02 Smart 3-way Dimmer Switch successfully expoited with DS02F profile
DS01C Smart Dimmer Switch successfully exploited with DS02F profile
SS01S Smart Switch successfully exploited with 1.1.8 - BK7231T / oem_bk7231s_rnd_switch profile
SS01 Smart 3-way Switch - No luck here, tried a bunch of profiles. Any suggestions for other profiles to try? If not, what data do I need to provide to generate a profile? It failed with SSL Error on 12

They all use the WB3S.

About the SS01, you can join it in the Tuya app and see what firmware version it's running. Alternatively, you can try Lightleak PoC, since WB3S is BK7231T.

Thanks for the tip @kuba2k2! Unfortunately, no luck :cry:. I paired it to the app and confirmed v1.1.3 on both MCUs. I tried that profile but still hit the SSL Error on 12. Any other suggestions?

The only 1.1.3 we have is for a curtain switch, and judging by the class name it is not compatible.  Would it be possible for you to get a dump of the firmware?  As kuba2k2 mentioned, you might be able to dump it wirelessly via lightleak, in which case we would be able to generate a profile from that.

Hmm I'm having trouble finding lightleak, googling is not turning anything up. Can you provide a link? Happy to get a dump.

It's still in the early phases and not documented.  It requires a dev board (ESP8266, ESP32, or Beken) as an intermediate device, and an android device to run the app.
https://github.com/tuya-cloudcutter/cloudcutter-android for the app (see releases to download the apk).  You will need to manually grant location access.
https://github.com/tuya-cloudcutter/lightleak for the intermediate device.

Wow that's a neat project! I'm trying to flash it onto a WB3S because that's the only chip I have here. It flashes successfully but the AP doesn't come up, even after a reset. Any suggestions?

Not unless we see logs :smile:

haha fair, not sure what logs to show you though? I don't see anything on the uart, not sure where else to look?

I did ESP32, so I can't say for sure.  How did you flash the WB3S version?  Which file and offset did you use?

haha fair, not sure what logs to show you though? I don't see anything on the uart, not sure where else to look?

The Lightleak platformio program is set to output logs on UART1, the same one as used for flashing. So check there if you checked on UART2 before.

I did ESP32, so I can't say for sure. How did you flash the WB3S version? Which file and offset did you use?

I flashed using platformio, just did pio run -e bk7231t and then pio run -t upload -e bk7231t.

The Lightleak platformio program is set to output logs on UART1, the same one as used for flashing. So check there if you checked on UART2 before.

I checked using pio device monitor -e bk7231t which should be using uart1, I don't see anything except one null character on boot.

You can check if it prints any useful info on UART2. Should at least be the bootloader message with some weird numbers.

Closing as there is no actionable item here.  It should remain searchable as information.

authors: Cossid kuba2k2 rickyelopez

repo: tuya-cloudcutter/tuya-cloudcutter