Composer file with altered ports gives errors

Do you know why this composer file does not work?
It's the example file, just with changed port numbers.
Are there hardcoded port numbers in the images?
The composer file:
# cat ./docker-compose-acala.yml
services:
  acala-mandala-node:
    image: ghcr.io/acalanetwork/mandala-node:sha-f045637
    container_name: acala-mandala-node
    ports:
      - 4444:4444
    command:
      - --dev
      # - -lruntime=debug
      # - -levm=debug
      - --ws-port=4444
      - --ws-external
      - --rpc-port=4433
      - --rpc-external
      - --rpc-cors=all
      - --rpc-methods=unsafe
      #- --instant-sealing
  acala-postgres:
    image: postgres:12-alpine
    container_name: acala-postgres
    ports:
      - 5432:5432
    volumes:
      - postgres:/mnt/big1/POSTGRES_ACALA
    environment:
      POSTGRES_PASSWORD: postgres

  acala-subquery-node:
    image: acala/evm-subql:c65f9c3
    container_name: acala-subquery-node
    ports:
      - 4400:4400
    depends_on:
      - acala-postgres
      - acala-mandala-node
    restart: always
    extra_hosts:
      - host.docker.internal:host-gateway
    environment:
      DB_USER: postgres
      DB_PASS: postgres
      DB_DATABASE: postgres
      DB_HOST: host.docker.internal
      DB_PORT: 5432
    command:
      - -f=project.yaml
      - --network-endpoint=ws://acala-mandala-node:4444
      - --db-schema=acala_evm
      - --log-level=debug
      - --unsafe
      - --disable-historical

  acala-graphql-engine:
    image: onfinality/subql-query:v1.4.0
    container_name: acala-graphql-engine
    ports:
      - 4401:4401
    depends_on:
      - acala-postgres
      - acala-subquery-node
    restart: always
    extra_hosts:
      - host.docker.internal:host-gateway
    environment:
      DB_USER: postgres
      DB_PASS: postgres
      DB_DATABASE: postgres
      DB_HOST: host.docker.internal
      DB_PORT: 5432
      PORT: 4401
    command:
      - --name=acala_evm
      - --playground
      - --indexer=http://subquery-node:4400

  acala-eth-rpc-adapter-server:
    image: acala/eth-rpc-adapter:c65f9c3
    container_name: acala-eth-rpc-adapter-server
    restart: always
    depends_on:
      - acala-mandala-node
      - acala-subquery-node
      - acala-graphql-engine
    ports:
      - 4402:4402
    extra_hosts:
      - host.docker.internal:host-gateway
    environment:
      - SUBQL_URL=http://acala-graphql-engine:4401
      - ENDPOINT_URL=ws://acala-mandala-node:4444
      #- LOCAL_MODE=1
      #- SAFE_MODE=1
    command: yarn start

volumes:
  postgres:

Running gives this error over and over:
docker-compose -f ./docker-compose-acala.yml up
...
acala-eth-rpc-adapter-server    |   ------------------------------------------
acala-eth-rpc-adapter-server    |   ⚡ running in production (standard) mode ⚡
acala-eth-rpc-adapter-server    |   ------------------------------------------
acala-eth-rpc-adapter-server    |
acala-mandala-node              | 2023-01-03 16:35:15 Accepting new connection 1/100
acala-eth-rpc-adapter-server    | 2023-01-03 16:35:15        API/INIT: RPC methods not decorated: evm_blockLimits
acala-eth-rpc-adapter-server    | Error: Check Graphql failed: FetchError: request to http://acala-graphql-engine:4401/ failed, reason: connect ECONNREFUSED <IP_ADDRESS>:4401 (code=UNKNOWN_ERROR, version=bodhi.js/providers/2.5.3)
acala-eth-rpc-adapter-server    |     at Logger.makeError (/app/common/temp/node_modules/.pnpm/@ethersproject+logger@5.5.0/node_modules/@ethersproject/logger/src.ts/index.ts:225:28)
acala-eth-rpc-adapter-server    |     at Logger.throwError (/app/common/temp/node_modules/.pnpm/@ethersproject+logger@5.5.0/node_modules/@ethersproject/logger/src.ts/index.ts:237:20)
acala-eth-rpc-adapter-server    |     at SubqlProvider.checkGraphql (/app/eth-providers/lib/utils/subqlProvider.js:14:33)
acala-eth-rpc-adapter-server    |     at processTicksAndRejections (node:internal/process/task_queues:96:5)
acala-eth-rpc-adapter-server    |     at async start (/app/eth-rpc-adapter/src/index.ts:37:5) {
acala-eth-rpc-adapter-server    |   reason: 'Check Graphql failed: FetchError: request to http://acala-graphql-engine:4401/ failed, reason: connect ECONNREFUSED <IP_ADDRESS>:4401',
acala-eth-rpc-adapter-server    |   code: 'UNKNOWN_ERROR'

your docker-compose.yml works for me.
After the node produces blocks, the services will work

hey zjb0807... so you didn't get this connection error:
acala-eth-rpc-adapter-server    | Error: Check Graphql failed: FetchError: request to http://acala-graphql-engine:4401/ failed, reason: connect ECONNREFUSED <IP_ADDRESS>:4401 (code=UNKNOWN_ERROR, version=bodhi.js/providers/2.5.3)

I've run it all for 1 hour and it's still doing that.
I did it all again on fresh server and i don't get that error.

- --indexer=http://subquery-node:4400
should be
- --indexer=http://acala-subquery-node:4401

change the port mapping to 4400:3000

  acala-subquery-node:
    image: acala/evm-subql:c65f9c3
    container_name: acala-subquery-node
    ports:
      - 4400:3000

change command in acala-graphql-engine:
- --indexer=http://subquery-node:4400
should be
- --indexer=http://acala-subquery-node:3000

docker logs -f acala-subquery-node
2023-01-03T21:48:36.297Z <subql-node> INFO Node started on port: 3000

the default define here: https://github.com/AcalaNetwork/bodhi.js/blob/e5f27cb6f2fa1a604e15a3d07f47e3ce995f0132/evm-subql/package.json#L13

I got this working by changing acala-eth-rpc-adapter-server:
      - SUBQL_URL=http://host.docker.internal:4401

I'm wondering though, the example composer file doesn't use volumes (except for postgres) don't you need to persist the data the acala node is storing?

I am currently running postgres, subql, subquery and rpc on docker, but using an existing acala node not on docker. It's indexing fast, so i'm hoping this will work.

Only postgres needs volumes, since the subql metadata (such as curblock, highest block) is stored in it. The indexer should continue from latest indexed height after restarting (without needing volume), as long as it correctly communicate with postgres.

can you check the _metadata table in your schema, it should be something like this. If the lastProcessedHeight is correct, that means indexer (subquery-node) is not reading the database.

BTW the example compose file is just a minimum example to demonstrate how everything work together. In prod we usually need to start each service separately, instead of using a big docker compose directly.

can you check the _metadata table in your schema, it should be something like this
If the lastProcessedHeight is correct, that means indexer (subquery-node) is not reading the database, otherwise it should just start from lastProcessedHeight

postgres=# select * from acala_evm._metadata;

          key           |                                value                                 |         createdAt          |         updatedAt
------------------------+----------------------------------------------------------------------+----------------------------+----------------------------
 genesisHash            | "0xfc41b9bd8ef8fe53d58c7ea67c794c7ec9a73daf05e6d54b14ff6342c99ba64c" | 2023-01-07 19:13:36.711+00 | 2023-01-07 19:13:36.711+00
 chain                  | "Acala"                                                              | 2023-01-07 19:13:36.714+00 | 2023-01-07 19:13:36.714+00
 specName               | "acala"                                                              | 2023-01-07 19:13:36.716+00 | 2023-01-07 19:13:36.716+00
 indexerNodeVersion     | "1.9.1"                                                              | 2023-01-07 19:13:36.722+00 | 2023-01-07 19:13:36.722+00
 indexerHealthy         | true                                                                 | 2023-01-07 19:14:36.126+00 | 2023-01-09 16:25:05.303+00
 historicalStateEnabled | false                                                                | 2023-01-07 19:13:36.684+00 | 2023-01-09 16:25:40.143+00
 runnerNode             | "@subql/node"                                                        | 2023-01-07 19:13:36.702+00 | 2023-01-09 16:25:40.255+00
 runnerNodeVersion      | "1.9.1"                                                              | 2023-01-07 19:13:36.702+00 | 2023-01-09 16:25:40.255+00
 runnerQuery            | "@subql/query"                                                       | 2023-01-07 19:13:36.702+00 | 2023-01-09 16:25:40.255+00
 runnerQueryVersion     | "1.4.0"                                                              | 2023-01-07 19:13:36.702+00 | 2023-01-09 16:25:40.255+00
 targetHeight           | 2686449                                                              | 2023-01-07 19:14:36.123+00 | 2023-01-09 16:25:05.296+00
 lastProcessedHeight    | 2611544                                                              | 2023-01-07 19:13:40.515+00 | 2023-01-09 03:45:03.006+00
 lastProcessedTimestamp |<PHONE_NUMBER>005                                                        | 2023-01-07 19:13:40.515+00 | 2023-01-09 03:45:03.006+00
 processedBlockCount    | 1771545                                                              | 2023-01-07 19:13:36.719+00 | 2023-01-07 19:13:36.719+00
(14 rows)


channel/:channelName/range returns weird/incorrect time ranges

E.g. see: https://logs.ivr.fi/channel/pajlada/range
Returned are messages from 2019-06-27 and 2019-07-27 so this is basically [now, now - 24h] ∪ [now - 30d, now - 31d] when it (I'm guessing) really should only show the last 24 hours.

Yea, idk what I was thinking here https://github.com/gempir/justlog/blob/d9577b693765b81c177cb2188fa5e970b3719cc0/api/channel.go#L178

Range is now removed just pass from and/or to and it should give out the correct logs


Management policies for storage account using ARM template

I wanted to confirm whether we can create policies using ARM template for an existing storage account ?
I referred the following template "https://docs.microsoft.com/en-us/azure/templates/microsoft.storage/2019-04-01/storageaccounts/managementpolicies" but was unable to access the storage account .

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 06288d35-3c83-c29d-95d8-a56823d910a3
Version Independent ID: 002fb5f5-5e4a-a95a-4564-2c399bcb5e06
Content: Storage account overview - Azure Storage
Content Source: articles/storage/common/storage-account-overview.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

@UtsaVakani The creation of policies using ARM is currently supported. I'd recommend posting in  the forums https://social.msdn.microsoft.com/Forums/en-US/home?forum=windowsazuredata ? It would have a higher visibility on forums since this is not an issue with the documentation itself.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Blank bottom card in some cases

Blank bottom card in some cases. @stephanegigandet is experiencing this. It might be a first use issue, or a network issue.

I will look into it..

@teolemon Which bottom card are you talking about?

The scan mode card, completely blank. Haven't found a pattern yet.
@stephanegigandet can you share a barcode ?
possibly different screen densities, or network issues ?

a perhaps a failed query ?

The scan mode card, completely blank. Haven't found a pattern yet.
@stephanegigandet can you share a barcode ?
possibly different screen densities, or network issues ?

yeah, sharing the barcode would be helpful to track the bug. I have tried with different products, didn't find this issue. I will go through the code once again, check if there is any unhandled exception.

is it fixed with https://github.com/openfoodfacts/openfoodfacts-androidapp/issues/2297 ?

yes it is @deniger , thanks :-)


feat: added matrix multiplication algorithm

added matrix multiplication algorithm to the maths folder

No, sorry
Had some problems and won't be able to be coding for a few weeks

Oh sorry to hear that! None of my comments are blockers though, this PR is pretty much fine as-is.


Decoder issues

Device - SM-M127G
Download link - https://driveseed.org/file/cH8FkqwKwdJhp9NxxIJ1
You can download it from here from that im getting issues
Just click instant download
This video is currently unsupported please take a look by downloading . Thanks.

The video is HDR HEVC so it's the same issue as in #491. You might have better luck trying Next Player which includes extra decoders for AVC and HEVC.

But you have add a support for this videos mostly all foss app plays this like vlc.

Bro did you understand please respond.Because Samsung inbuilt player is same as good.

But you can add a support for this videos mostly all foss app plays this like vlc.

Just Player uses ExoPlayer which relies basically only on device video decoders. Nothing more is planned beyond that.


Unclear semantics on how to correlate response with request

The rendezvous server protocol is full duplex. The client can receive messages from the server at any time, and the server can receive messages from the client at any time.
However, some messages that originate from the client have RPC semantics. e.g. list or allocate (or even ping). These messages are requests that need a response.
AFAICT, the Python client assumes that the first response of the right type is the intended response for the message. e.g. the first allocated message after an allocate request must be the response.
If this is the intended semantics of the protocol, then server-protocol.md should be updated accordingly.
These are OK semantics, but they mean that only one concurrent thread of execution can use a wormhole connection at a time (is this my allocate response, or someone else's?)
Perhaps a better approach would be to elevate the importance of the id field, making it the way to correlate request & response. This would require fixing #259, and ideally renaming the ping and pong fields to id.

Hm.. each websocket connection is dedicated to a single Wormhole instance. If there are multiple connections, they need to use separate connections. (I'll agree this is wasteful if you're doing a lot of simultaneous connections, but I consider that an unusual use case, and the protocol simplicity of one-connection-per-wormhole is compelling).
The id field is intended for debugging and logging/timing/tracing, not for operational use. The main purpose is for the timing diagram tools (misc/dump-timing.py).
If we want to enable sharing a single connection for multiple wormholes.. hm, I think we'd need to invent another field (maybe wormhole_id?), and use that to decide which Wormhole object each response should get routed to. I'll agree that we could probable re-use id for this, if we were more deliberate about how it gets used. I'm up for fixing the other issues you mentioned, if only for completeness/consistency.
The requests that have RPC-like semantics are still handled by a state machine: there's no table of pending requests (like the way Foolscap would do it). Instead, there's a state machine that's now in the "I want a response" state, and if/when a response arrives, that'll move it to the "I no longer care about responses" state (and deliver some event to some higher-level state machine). This helps us with connection re-establishment: if the websocket connection is dropped and then reestablished while we're in the "I want a response" state, the request will be re-transmitted (since we don't know whether the connection dropped before or after the request got delivered).

IIUC (particularly the 4th paragraph)

the first message of the expected type (e.g. namespaces for list, allocated for allocate) is the response
clients are free to re-transmit the exact same message

Inferring from that…

generally speaking transmitting a message of the same type with different values is a no-no

Fixing up the use of id would be nice, thanks. However, if I understand you correctly, client implementations and server implementations should not rely on it for dispatch.
Is this an accurate summary?
Personally I'm not particularly concerned about the resource cost of one socket per connection (yet!), just interested in how to correctly write a client library in a highly concurrent language.


Removed duplicate functions in TUF

Signed-off-by: Oluwatobi Popoola<EMAIL_ADDRESS>Please fill in the fields below to submit a pull request.  The more information
that is provided, the better.
Fixes issue #: 656
Description of the changes being introduced by the pull request:
Removed functions that did not expand functionality to equivalent functions in securesystemslib.
Please verify and check that the pull request fulfills the following
requirements:

[x] The code follows the Code Style Guidelines
[x] Tests have been added for the bug fix or new feature
[x] Docs have been added for the bug fix or new feature

@tobithegreat, would you like to look through and see where the tests failed as a result of this PR?
The automated testing / continuous integration we use helps identify possible issues with new pull requests.  You can see on this page that the builds running the tests failed, and click Details (I'd look at the Travis results to start.) to see what happened.  Sometimes code changes necessitate test changes -- for example, there may be test functions that test pieces of code that are no longer necessary and were removed -- and sometimes test failures indicate that there is a mistake and something was broken.
It should help to know that you can run the TUF tests locally by running python aggregate_tests.py from the tests directory in your local repository.  You can run individual test modules similarly:  python test_updater.py, for example, from inside the tests directory.

Thanks, will do!

@awwad sorry to bother, but I'm having trouble running the tests locally. Upon running test aggregate_tests.py from within the tests directory, I receive an ImportError. Stacktrace below:
Oluwatobis-MBP:tests oluwatobipopoola$ python aggregate_tests.py
Traceback (most recent call last):
  File "aggregate_tests.py", line 93, in <module>
    suite = unittest.TestLoader().loadTestsFromNames(test_modules_to_run)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/loader.py", line 130, in loadTestsFromNames
    suites = [self.loadTestsFromName(name, module) for name in names]
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
    module = __import__('.'.join(parts_copy))
  File "/Users/oluwatobipopoola/Desktop/tuf/tests/test_slow_retrieval_attack.py", line 59, in <module>
    import tuf.log
ImportError: No module named tuf.log

I suspect this has to do with my file hierarchy?

Have you installed tuf?
pip install -r dev-requirements.txt
(from main repo directory)
On Sat, Nov 17, 2018 at 07:51 Oluwatobi Popoola<EMAIL_ADDRESS>wrote:

@awwad
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_awwad&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=lmb4ogFqgMptuKWQok14rSU0yJ3xUDL7l3ttC3XYeMw&m=TDcSTJRuNI5ZvNxAx0mxnCxUMlZo8yHmkfDrHrT2en0&s=WxkP4YmqJt0japoPBt4bVtrTMgms7uvOO-upCzebUmM&e=
sorry to bother, but I'm having trouble running the tests locally. Upon
running test aggregate_tests.py from within the tests directory, I
receive an ImportError. Stacktrace below:
Oluwatobis-MBP:tests oluwatobipopoola$ python aggregate_tests.py
Traceback (most recent call last):
File "aggregate_tests.py", line 93, in
suite = unittest.TestLoader().loadTestsFromNames(test_modules_to_run)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/loader.py", line 130, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
module = import('.'.join(parts_copy))
File "/Users/oluwatobipopoola/Desktop/tuf/tests/test_slow_retrieval_attack.py", line 59, in
import tuf.log
ImportError: No module named tuf.log
I suspect this has to do with my file hierarchy?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_theupdateframework_tuf_pull_804-23issuecomment-2D439614379&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=lmb4ogFqgMptuKWQok14rSU0yJ3xUDL7l3ttC3XYeMw&m=TDcSTJRuNI5ZvNxAx0mxnCxUMlZo8yHmkfDrHrT2en0&s=y-w9M_QeqyMwcy7oB8AMvqIGqHOk4YBYiukfDNdsjMM&e=,
or mute the thread
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMpkOA8-2DLaEbwToelOOuOlKBjuiLdVCEks5uwAZQgaJpZM4YfmrW&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=lmb4ogFqgMptuKWQok14rSU0yJ3xUDL7l3ttC3XYeMw&m=TDcSTJRuNI5ZvNxAx0mxnCxUMlZo8yHmkfDrHrT2en0&s=MCohhHOGqkoOEtKUas7DGCwNKHjDpMuefMzWG4U7yc4&e=
.

Have you installed tuf? pip install -r dev-requirements.txt (from main repo directory)
…
On Sat, Nov 17, 2018 at 07:51 Oluwatobi Popoola @.***> wrote: @awwad https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_awwad&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=lmb4ogFqgMptuKWQok14rSU0yJ3xUDL7l3ttC3XYeMw&m=TDcSTJRuNI5ZvNxAx0mxnCxUMlZo8yHmkfDrHrT2en0&s=WxkP4YmqJt0japoPBt4bVtrTMgms7uvOO-upCzebUmM&e= sorry to bother, but I'm having trouble running the tests locally. Upon running test aggregate_tests.py from within the tests directory, I receive an ImportError. Stacktrace below: Oluwatobis-MBP:tests oluwatobipopoola$ python aggregate_tests.py Traceback (most recent call last): File "aggregate_tests.py", line 93, in  suite = unittest.TestLoader().loadTestsFromNames(test_modules_to_run) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/loader.py", line 130, in loadTestsFromNames suites = [self.loadTestsFromName(name, module) for name in names] File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName module = import('.'.join(parts_copy)) File "/Users/oluwatobipopoola/Desktop/tuf/tests/test_slow_retrieval_attack.py", line 59, in  import tuf.log ImportError: No module named tuf.log I suspect this has to do with my file hierarchy? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_theupdateframework_tuf_pull_804-23issuecomment-2D439614379&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=lmb4ogFqgMptuKWQok14rSU0yJ3xUDL7l3ttC3XYeMw&m=TDcSTJRuNI5ZvNxAx0mxnCxUMlZo8yHmkfDrHrT2en0&s=y-w9M_QeqyMwcy7oB8AMvqIGqHOk4YBYiukfDNdsjMM&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMpkOA8-2DLaEbwToelOOuOlKBjuiLdVCEks5uwAZQgaJpZM4YfmrW&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=lmb4ogFqgMptuKWQok14rSU0yJ3xUDL7l3ttC3XYeMw&m=TDcSTJRuNI5ZvNxAx0mxnCxUMlZo8yHmkfDrHrT2en0&s=MCohhHOGqkoOEtKUas7DGCwNKHjDpMuefMzWG4U7yc4&e= .

Ah, thank you. I had, but on a different computer than the one my local repo was on. Thanks!

This latest commit updates all unit tests to reflect removal of duplication code.
Received an AppVeyor build fail:
Environment: PYTHON=C:\Python27, PYTHON_VERSION=2.7, PYTHON_ARCH=32
9 min 18 sec

Error:
======================================================================
ERROR: test_download_url_to_tempfileobj_and_lengths (test_download.TestDownload)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\projects\tuf-j90sw\tests\test_download.py", line 137, in test_download_url_to_tempfileobj_and_lengths
    download.safe_download, self.url, self.target_data_length + 1)
  File "C:\Python27\lib\unittest\case.py", line 473, in assertRaises
    callableObj(*args, **kwargs)
  File "c:\projects\tuf-j90sw\tuf\download.py", line 115, in safe_download
    return _download_file(url, required_length, STRICT_REQUIRED_LENGTH=True)
  File "c:\projects\tuf-j90sw\tuf\download.py", line 303, in _download_file
    average_download_speed=average_download_speed)
  File "c:\projects\tuf-j90sw\tuf\download.py", line 586, in _check_downloaded_length
    raise tuf.exceptions.SlowRetrievalError(average_download_speed)
SlowRetrievalError: Download was too slow. Average speed: 38.28114266658803 bytes per second.
----------------------------------------------------------------------
Ran 208 tests in 366.551s
FAILED (errors=1, expected failures=1)

Not sure how to deal with this error.

I re-ran the build and it passed.  I think that was an unusual build error, and I'll keep an eye out for it if it happens again.  Thanks for taking a look.  I'll review this PR shortly. :)

The commit history is a bit hard to read:
https://github.com/theupdateframework/tuf/pull/804/commits
See the three upstream-to-local merge commits "Merge branch 'develop' of https://github.com/tobithegreat/tuf into develop..."?  Two of them contain no changes, and the other contains changes.  Generally, you shouldn't try to push merge commits like that back upstream: it's convoluted and makes the commit history hard to read.  (If this isn't in our lab guidelines yet, it will be soon.)
Those merges happen when you pull from the repository.  I advise instead fetching (git fetch --all), and then using git rebase <origin>/develop to keep the history clean.  I'll give you some tips toward that end.

For starters, you only really need to fetch new upstream code if you're concerned that it might impact what you're doing.  You can instead rebase when you're ready to make a pull request.

If you want to pull down from the remote repo, you can fetch (git fetch --all), finish up your commit or stash (git stash) what you're working on, then rebase your branch onto the tip of the remote branch (probably git rebase <origin>/develop in your case -- using whatever you've named the upstream theupdateframework repo (git remote -v to see your remotes), and then pop the stash again.  If you encounter conflicts, you can fix them this way, in each commit.

If some upstream-to-local merge commits have already been added with additional changes, as in this case, you can either rebase or, if necessary, squash the commits.

Another, unrelated tip: it's usually best to start a feature branch when you do something like this.  So, for example, before you start adding commits, you could have run git checkout -b remove_duplicate_ssl_funcs before adding your commits.

In this case, here's how I might go about fixing the PR (without creating a new one):
git checkout develop
git rebase tuf/develop
git rebase --continue
git push tobithegreat develop --force

Note that those names are based on this remote listing:
git remote -v
  ...
  tobithegreat	https://github.com/tobithegreat/tuf (fetch)
  tobithegreat	https://github.com/tobithegreat/tuf (push)
  tuf	https://github.com/theupdateframework/tuf (fetch)
  tuf	https://github.com/theupdateframework/tuf (push)

If any of that doesn't make sense to you, please feel free to ask about it!

When that's fixed, this looks good to me.  Did you see any other functions that could be replaced by securesystemslib features?

I re-ran the build and it passed. I think that was an unusual build error, and I'll keep an eye out for it if it happens again. Thanks for taking a look. I'll review this PR shortly. :)

Thanks! I should also note that I had to update a few lines in the tests that caused errors unrelated to my changes.
For example, in test_repository.lib.py, on line 422, self.assertEqual(repo_lib.get_target_hash(filepath), target_hash) was changed to self.assertEqual(securesystemslib.util.get_target_hash(filepath), target_hash), as there was no get_target_hash function available in repository_lib.py.
Please let me know if this was a mistaken change.

@awwad Wow, thanks for all the feedback! I'll be sure to make these changes.
Also, I updated a few lines in the test cases, that caused errors unrelated to my changes.
For example, on line 422, self.assertEqual(repo_lib.get_target_hash(filepath), target_hash) was changed to self.assertEqual(securesystemslib.util.get_target_hash(filepath), target_hash), since get_target_hash is a function not available in repository_lib.py.
Please let me know if this change was mistaken!

get_target_hash is in repository_lib.py here.  If it weren't there, that test would have generated an error. 😄
However, get_target_hash is an example of another function that is available in securesystemslib, and therefore may not need to be in TUF itself.  Would you like to look and see if removing get_target_hash in TUF and swapping in SSL's makes sense?

My mistake! Here is the exact error:
======================================================================
ERROR: test_get_target_hash (test_repository_lib.TestRepositoryToolFunctions)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/oluwatobipopoola/Desktop/tuf/tests/test_repository_lib.py", line 422, in test_get_target_hash
    self.assertEqual(repo_lib.get_target_hash(filepath), target_hash)
AttributeError: 'module' object has no attribute 'get_target_hash'

And I'm happy to see if it can be replaced.

Hello again!
Thanks once again for explaining everything in such depth. I'm still learning best git practices, and this was a big help.
I ran the steps you outlined above. My remotes are as follows:

origin	https://github.com/tobithegreat/tuf.git (fetch)
origin	https://github.com/tobithegreat/tuf.git (push)
tuf	https://github.com/theupdateframework/tuf (fetch)
tuf	https://github.com/theupdateframework/tuf (push)

running  git push origin develop --force returned Everything up-to-date. Is the PR more clean now?

No; you can see the git history in the commits page here, with (roughly) the same merge commits.  I can't really say what went wrong without more information, though I have guesses....  Can you send me the output of these commands?

git status
git log --oneline --decorate --graph --all      (You only need to go back far enough to show tuf/develop and 3-4 lines after origin/develop.)

I assume the output of git remote -v is the same; if not, show me that, too.

Output of git status:
`On branch develop
Your branch is up to date with 'origin/develop'.
Untracked files:
(use "git add ..." to include in what will be committed)
tests/ssl_certs/proxy_certs/
tests/tmp3_z3I6/
tests/tmp4h_R6v/
tests/tmp7kFriU/
tests/tmp9FB297/
tests/tmpBXCty8/
tests/tmpDAQS4e/
tests/tmpDUlfUf/
tests/tmpF2CMve/
tests/tmpGymUM5/
tests/tmpRwnumb/
tests/tmpTHQYss/
tests/tmpVnsdRq/
tests/tmpWshCrP/
tests/tmp_9OMiX/
tests/tmpdfZ32c/
tests/tmphhumHv/
tests/tmprriis8/
tests/tmpv6ZqrR/
tests/tmpyV4HGM/
tests/tmpzG5YOY/
virtualenv-15.0.3.tar.gz

nothing added to commit but untracked files present (use "git add" to track)
`
Some of the output from git log --oneline --decorate --graph --all
`*   30f9561 (HEAD -> develop, origin/develop, origin/HEAD) Merge branch 'develop' of https://github.com/tobithegreat/tuf into develop
|\
| *   4c10eea Merge branch 'develop' of https://github.com/tobithegreat/tuf into develop
| |\

| \   4e2294a Merge branch 'develop' of https://github.com/tobithegreat/tuf into develop
|\ \ \
| |/ /
|/| /
| |/
| * d8f8763 Removed duplicate functions in TUF
| d33024c Removed duplicate functions in TUF
|/
| *   05a9aa2 (refs/stash) WIP on develop: fffc533 Merge pull request #803 from theupdateframework/test_delay_increases
| |\
|/ /
| * b9e70d2 index on develop: fffc533 Merge pull request #803 from theupdateframework/test_delay_increases
|/
fffc533 Merge pull request #803 from theupdateframework/test_delay_increases
|\
| * 8866abb (origin/test_delay_increases) test: remove port collison chance and lengthen delays for AppVeyor
`

git fetch --all
git rebase theupdateframework/develop

Good and bad news. 😄
The one test that failed on AppVeyor was a fluke I'm familiar with, so I restarted it and it succeeded.  (A server didn't start up on AppVeyor within the 3s expected window....  I should adjust those subprocess calls to wait for some flexible period of time, but that's not related to this.  😄 )
There are meaningful errors in the Travis-CI build, though.  Travis-CI is running pylint and that is complaining that there are calls in developer_tool to methods that don't exist.  Those calls should also be fixed in this PR, so that's a good build failure.  (You can see the lint failures in the Travis-CI build logs.)

Finished the commit and fixed the tests, but it was signed off incorrectly. Sorry to ask again, but is there an efficient way to correct the commit without clogging up the history again?

Yes:
git commit -s --amend
git push origin develop --force
On Fri, Nov 30, 2018 at 15:30 Oluwatobi Popoola<EMAIL_ADDRESS>wrote:

Finished the commit and fixed the tests, but it was signed off
incorrectly. Sorry to ask again, but is there an efficient way to correct
the commit without clogging up the history again?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_theupdateframework_tuf_pull_804-23issuecomment-2D443330280&d=DwMCaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=lmb4ogFqgMptuKWQok14rSU0yJ3xUDL7l3ttC3XYeMw&m=hmz4JvrTgnHGI7997wkSaDC_mqLo7ECf04VAtaOzw0w&s=viaWHRU5my-gqkPYwXKiNcosHnO3WJKhF4MYV0x5u_g&e=,
or mute the thread
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMpkOPupr42V7We4OWpCSsZMWueYX7B9ks5u0ZVygaJpZM4YfmrW&d=DwMCaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=lmb4ogFqgMptuKWQok14rSU0yJ3xUDL7l3ttC3XYeMw&m=hmz4JvrTgnHGI7997wkSaDC_mqLo7ECf04VAtaOzw0w&s=QSmlLPuZL3DTYkZGYE8TDCN8E-AxdZIBPEGmtKTf-xc&e=
.

Ran those commands and force pushed once again. This time is states that the DCO is missing.
Really sorry about this, if there's something very obvious I am not seeing.

Thanks very much for your assistance.
I definitely could have done more reading in the docs to be more prepared to make contributions. I'll be sure to do so in the future.

Closing in favor of an updated version of this PR in #919. Thanks for the efforts!


Feature request: Project badges

Description
It would be super nice if you could add bagdes to a project like the way you can add them in Gitlab this would enable repository maintainers to clearly show the status of their pipelines or code coverage reports without having to out the into the readme.md. The badges should addable via the repo settings with a link_url and a image_url setting.

What about putting the badges in the repository description? Then render these images in Markdown.

But you can preview the README badges when you clone it locally.

Do people actually tend to open README.md files with tools capable of rendering the images in them ?
Myself I always open README files with a pager (less,more,view,...) just expecting text-only, nicely formatted to be somewhat machine-readable, but still for text-only (console?) consumption!
Badges in repository description I guess would be a possible workaround, but proper space for badges sounds even better to me, given the widespread use of badges.

I just experienced that the GitLab way of doing this has the limit of NOT allowing people to send pull-requests to add badges, so while I still think that it is nice to have an ad-hoc space for rendering the badges, it would be also good for the badges information to be in a file in the repository, like .badges.yml or something. That way different mirrors might eventually end up rendering the same badges  too

Or .badges.md if people really do render the markdown-with-images locally.
Or .header.md to be rendered before README.md, to be more generic and less intrusive in the life of text-only console-based reading of README files ?

.yaml could be better option imho, also would be nice to allow way for badges to pass branch/tag name in image url, so that it would be possible to link to specific version/branch docs/build status etc

Gitea gained actions (CI/CD) feature. Can this be implemented now as a part of Gitea Actions?

I think they are different features.

Yes, please don't bundle this with Gitea Actions !
I think use case is bigger and not all of use use Gitea Actions ...

But you can preview the README badges when you clone it locally.

Do people actually tend to open README.md files with tools capable of rendering the images in them ? Myself I always open README files with a pager (less,more,view,...) just expecting text-only, nicely formatted to be somewhat machine-readable, but still for text-only (console?) consumption!

I do yes. VS Code can preview markdown and see the badges. But to be honest, only reason I preview is when I edit.


Utils: Add clang-format for Mac

Description
Adds an ARM clang-format binary and adjusts shell script accordingly.

This change is not desired as I do not want to add a binary to the repository for the benefit of a tiny number of people on an unsupported platform. You can use clang-format locally, it does not have to be committed to the repository.


This might break availabilty during cluster upgrade

See more https://github.com/coreos/coreos-kubernetes/pull/730

@alex-slynko - I don't think we want to hardcode the assumption that there will only be one apiserver in the bosh release.
Feel free to reopen the PR if you feel otherwise but I'd like to keep the release to not make assumptions about it's configuration.

Hey @alex-slynko seems that 1 is the default so the behaviour will not change even if we remove it: https://github.com/kubernetes/website/pull/6695/files#diff-f1740b3dc59376d8eeb5d86fbb755bb6R207.
However, you pose an interesting concern as 1.9 seems be introducing a new reconciler which means we will have to rethink how we use --apiserver-count.
Can you explain what you think is different in the new reconciler and why you think we should avoid setting --apiserver-count regardless of the value.

@glestaris current value is not the best. If we use CFCR with multiple masters and single master goes down, API can experience downtime.
I sent this PR under influence of this talk https://kccncna17.sched.com/event/CU5x/101-ways-to-crash-your-cluster-i-marius-grigoriu-emmanuel-gomez-nordstrom


profile-icons with web sources are not shown on the taskbar

Windows Terminal version (or Windows build number)
1.8.1521.0
Other Software
No response
Steps to reproduce
I am using WINDOWS 11, I do not know how this behaves in Win10.

Create a new profile (or use an existing one)
For the icon, paste a weblink to an ico file (eg https://github.com/favicon.ico)
As you will see, that works fine (the icon gets shown in new tabs and in the settings menu)

keep winterm open
right-click onto the program in the taskbar
As you will see, the icons are not rendered here

Expected Behavior
Profile Icons are rendered the same way everywhere across the device
Actual Behavior
Profile Icons from the web are not rendered at all in the taskbar dialog

You know, I am confident that we have a dupe for this floating around on the repo, but I can't find it. The same thing happens when using an emoji as the icon for a profile.
I suppose theoretically, we could actually download the image locally and set the path for the jumplist entry to that file.

I suppose theoretically, we could actually download the image locally and set the path for the jumplist entry to that file.

I someone is going to implement that, maybe also make copies of local images to an app-internal path. I found it somewhat annoying that I have to make sure that my custom local icons do not get deleted by accident.
Like for example when I download an image, set it as profile icon, and then clean up my downloads folder, the profile icon is gone.

Yeah -- we should cache local and remote paths, honestly. We need to be extra careful to not cache old copies of local icons that have changed, but that should present little issue.
Technically -- and unrelately, mind you -- we should also be caching them in memory. Reloading every image every time the settings changes is a right pain. :smile:

Hello @torgeros, is this issue is still open, I like to work on this issue. I am new to open source and want to contribute.

I am not planning on working on this myself. No one else has posted something about them working on it.
Feel free to fork the repo and then open a pull request referencing this issue.

This is still an issue

This is still an issue

@JavierCCC try to re-pin it or reinstall.

facing same issue

This is still an issue

@JavierCCC try to re-pin it or reinstall.

didnt work

Facing this issue too

Soon, profile icons with web sources will not be shown at all. It's a trivial security risk.


Fix bad mouse offset with Control::wrap_mouse()

Fix #55705
Issue description
Right click in the 3D viewport capture the mouse for free look.
After releasing the mouse button, mouse cursor is wrapped at a bad position.
Identified cause
get_screen_transform() need to be reverted to get_global_transform() in Control::warp_mouse() function.
I've added this changed to my PR about popup offset when including Gil's PR changes but it seems it was a bad idea.
Before

After

Thanks!


changes from vedant

i adding my name

hey Vedant,
now your conflict issue has been resolved and merged successfully.


⚠ ClamAV has degraded performance

In a2e671c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 335 ms

Resolved: ClamAV performance has improved in 703bb2a.


Repeated sentece

In the paragraph:
When role nears its expiration, use PIM to extend or renew the roles. Both user-initiated actions require an approval from a Global administrator or Privileged role administrator. Both user-initiated actions require an approval from a Global administrator or Privileged role administrator.
The last sentence is repeated

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 66c20f5e-ca50-337e-8fc1-1d3d434178a7
Version Independent ID: 4f7c30ee-a49c-a79e-e06d-2c788ae91e39
Content: Plan a Privileged Identity Management deployment? - Azure AD
Content Source: articles/active-directory/privileged-identity-management/pim-deployment-plan.md
Service: active-directory
Sub-service: pim
GitHub Login: @BarbaraSelden
Microsoft Alias: baselden

@Rykimaruh
Thanks for your feedback! We will investigate and update as appropriate.

@Rykimaruh
Thank you for pointing this out! I've created a PR to update the documentation and it's currently waiting for the author to review and sign off.
I will now close out this issue. Please allow some time for the author to review and the changes to reflect.
Thank you for your time and patience!


$state.href returns incorrect URL with custom type object

I have a route with custom type applied on it
$stateProvider.state('root.projects', {
   url: "projects/{filterPath:nonURIEncoded}",
   params: {
       filterPath: {
           value: null,
           squash: true
       }
   }
})

The purpose of the custom type "nonURIEncoded" is to treat the trailing slashes in state parameter as the valid url parameter
Below code gives me incorrect output
$state.href("root.projects", {
     filterPath: "computer-engineering/"
}, {
  absolute: true
});

Expected Output: http://localhost/projects/mechanical-engineering/
Output i am getting: http://localhost/projects/electronics-engineering%2F
It seems state.href encodes the URL parameters and doesn't apply custom type object given to particular ui-state param.

Yeah its an ongoing issue. There are a few tickets open already that is similar to this. For now, can you just not use the /?

Well, I needed a generic solution for the issue, above given example is just one of the scenario, I am looking for a solution  in which i get a URL having custom type applied to it if applicable.


Can Edge agent reach out to server on any other port than 8000?

Question:
I have been trying to deploy Portainer and experiment with a few edge agents. My company is already hosting an internal app on port 8000 and so it is not available for me to be used as tunnel server address port. Is there any way Portainer server can listen on a custom port other than 8000?

Hi @Ankurkh1
We have a CLI flag you can use to set a new port:
--tunnel-port: Specify an alternate tunnel port to use with the Edge agent. Use --tunnel-port 8001 with -p 8001:8001 to make the Edge agent communicate on port 8001
Have a look at our WiP documentation for more info https://documentation.portainer.io/v2.0/deploy/cli/

This is awesome.
Thank you!!!


ISPN-8299 LocalStream*Passivation random failure

LocalStreamIteratorWithPassivationTest.testConcurrentPassivation random
failure

Made sure Local and Dist tests weren't sharing loader
When rewiring persistence manager was restarted, have to stop first

https://issues.jboss.org/browse/ISPN-8299

Merged, thanks


Issue/merge 8226

Description
Second stage for #8226

Processing this pull request

Merged into branches iso7 in 8c1e39047e97901d44ce003c15216d505e3667d1


docs: Added a guide to install react-native-reanimated in drawer-navigator.md

Info
i just added a guide to install react-native-reanimated in drawer-navigator.md

Thanks for the PR. The detailed installation instructions are already mentioned in Reanimated's docs so I don't see the need to duplicate it and potentially get outdated. If you think the link to reanimated docs should be emphasized then ideas welcome.


Add ConfigCacheDocsTest to TeamCity

Add a docsTest with -PenableConfigurationCacheForDocsTests=true, as requested by @mlopatkin .

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


JsonReaderException while calling BuildClientAsync

I've encountered the error as seen in the picture above, all the information of Telegram like apphash, AppId, and Public Key I was copied from here. However, I've no idea what cause the error like Newtonsoft.Json.JsonReaderException: 'Unexpected character encountered while parsing value: �. Path '', line 0, position 0.'
Which the error is not specific enough, got no idea how to debug on this, I hope someone would help me on this. I'm truly appreciate.

@jefferyleo try to remove session.dat file

@vik-borisov where will be the session.dat file located at? Or just remove the sessionTag?

@jefferyleo in "bin" directory

@vik-borisov Thanks for the help, I'm appreciated. It works now


add support for HA

This adds experimental support for mesh networking and resolves #20.
Example configuration is provided in defaults/main.yml
PR needs to be tested before merging. @bernhardrabe would you be able to verify if this works?
@rdemachkovych please review code.

Sure. Can you tell me how to do this with minimal effort?

Simplest way would be to define alertmanager_mesh with following content:
alertmanager_mesh:
  peers:
    - "alertmanager1:6783"
    - "alertmanager2:6783"

and running this playbook with this role against those 2 hosts (alertmanager1, alertmanager2).

sorry for being not that precise. I meant: How can I use the modified role?

You can install it from github with ansible-galaxy: http://docs.ansible.com/ansible/latest/galaxy.html#version
Or by using requirements.yml file: http://docs.ansible.com/ansible/latest/galaxy.html#installing-multiple-roles-from-a-file
Basically sth like:
ansible-galaxy install git+https://github.com/cloudalchemy/ansible-alertmanager.git,issue20

I can confirm that this fix works
(though I was confused at first because I needed to use the role "ansible-alertmanager" but I think this is due to this PR)

Thanks! :+1:


[RFC] v0.7 Release Planning

Thanks to everyone who works hard in the past cycle. This RFC to plan for v0.7 release.  The community has always been focusing on high quality releases.
One of the major highlights in the past cycle is that we have gone through major refactors to make sure we have a fresh new foundation for new things we want to develop, and there are also exciting new features such as auto scheduler and uTVM coming in.
Considering the nature of the new foundational change, we propose to focus of this release on landing key foundational changes we have made -- for example the new TIR/target and pass infra, since they affect the API itself.
Because we are landing new features at a fast pace, we might include experimental features(that does not affect API itself) that may still need stabilization and work to cut another release after these features stabilize. We would include auto_scheduler(ansor) and intitial uTVM would be part of this release as experimental features we will continue to polish the features in the incoming cycle.
Please share your thoughts.
In the next few days we will be populating the release note in this thread.  Most release note content will be derived from our monthly report.

@ZihengJiang and @zhiics have kindly agreed to serve as release managers for this release

Do we have a target date for the release?

Of course the the date would depends on the status of the release, because we should always aim for quality. Based on our past experience, it might takes a few weeks.

Is the error reporting feature included in this release as an experimental feature or it would be in the next release?

For the experimental features, auto_scheduler and uTVM, would that be better to decorate their entry points with something like @experiment so that it pops a warning to tell users this feature is experimental (and maybe the actions we expect users to take when they encounter issues)?

@comaniac if we land the final error reporting PR it removes the existing error reporting from type checker completely, I think we should either choose to ship it this release or delay until next release. One worry is that there will probably be a period of stability where we iterate/polish on new errors.

@comaniac if we land the final error reporting PR it removes the existing error reporting from type checker completely, I think we should either choose to ship it this release or delay until next release. One worry is that there will probably be a period of stability where we iterate/polish on new errors.

Make sense to me (including the worry as well). Different from auto_scheduler and uTVM, error reporting is not just a standalone module that users can completely ignore, so we should be more careful.

I agree that we should mark certain features as initial support/experimental in the release note. We could also come up with documentation tags to mark the feature as experimental. I am less certain sure about shooting a warning for each function call, as they harm the overall user experience, perhaps we can start with the release note and docs?

Yeah, I also prefer to document it instead of throwing many warnings. In addition, we have some checker in the codebase claiming that some APIs will be deprecated in the next release. We probably want to take some actions on them as well.

I'd like to see the tvmc work to be functional before we cut the release please. I'd also like to see the Ethos-N PRs land as well.

@apache/tvm-committers  @jroesch @u99127 @comaniac
We have a release note candidate here: https://github.com/apache/incubator-tvm/issues/6486
Please comment it if you have anything want to be added into this release or other opinion.

Also jump in here. Let us plan to cut a release next week. At this point we should "freeze the features", but please suggest a list of PRs(fixes) that need to be merged.

A brief summary of the related PRs missed in the current release note candidates. Not sure if all of them have to be listed so just for reference. Except for the note followed by the PR indicating its status, all PRs listed here are merged.
Automatic Scheduling (Experimental)

[AutoTVM][Ansor] Enable random fill and CPU cache flush for AutoTVM and Ansor (#6391)
[Minor] Fix typos in Ansor (#6425)
[TUTORIAL][ANSOR] Using the template-free auto-scheduler on CPU (#6488)
[ANSOR] Auto-scheduler tutorial for GPU and necessary refactor/fix (#6512)
[Ansor] Parallel the InitPopulation (#6512)
[Ansor][FLAKY] Bug fix for compute at mutation error (#6557)

BYOC

[BYOC][CONTRIB] Vitis-AI codegen integration (#6343) -- expected to merge in 2 weeks.
[BYOC][ETHOSN] Introduce further operator support (#6355)
[BYOC][JSON] Support input nodes with multiple entries (#6368)
[BYOC][TensorRT] TensorRT BYOC integration (#6368) -- expected to merge in 2 weeks.
[BYOC][ACL] Add maximum support for float32 (#6506)
[BYOC][ACL] Support add operation (#6532) -- expected to merge in 1 week.
[BYOC][ETHOSN] Fix tests for new module API (#6560) -- expected to merge in 1 week.

TVMC(Experimental)

[tvmc] Introduce 'tune' subcommand (part 3/4) (#6537) -- expected to merge in 1 week.
TVMC part 4/4: Tutorial -- not filed yet but I suppose it's required if we list TVMC as an experimental feature in 0.7 (cc @leandron, @u99127).

At this point, we should focus on stablization, so we don't have to rush in features like Vitis-AI and TensorRT and we do them in v0.8 cycle(for better stablization).  We should instead list PRs that contains necessary fixes that need to be inlcuded.

At this point, we should focus on stablization, so we don't have to rush in features like Vitis-AI and TensorRT and can do them in the v0.8 cycle(for better stablization). We should instead list PRs that contains necessary fixes that need to be inlcuded.

Make sense. Removed them from the list.

@comaniac Thanks for checking! I have added missing ones except those are not merged yet.

TVMC(Experimental)
* [tvmc] Introduce 'tune' subcommand (part 3/4) (#6537) -- expected to merge in 1 week.
* TVMC part 4/4: Tutorial -- not filed yet but I suppose it's required if we list TVMC as an experimental feature in 0.7 (cc @leandron, @u99127).

@comaniac, yes, it would be great to merge #6537 before, lets try to solve all the issues early next week; Also, "part 4/4", related to tvmc run is coming very soon, Monday max, and it would be great to have it as well, so that we have the first package complete

Let us aim for Oct 1st as the tentative date for the release cutting. would be great to merge #6537  before then

Let us aim for Oct 1st as the tentative date for the release cutting. would be great to merge #6537 before then

So, #6537 and #6578 would be the final two PRs to complete the first version of tvmc.

So, #6537 and #6578 would be the final two PRs to complete the first version of tvmc.

Per offline discussion with @leandron, the final PR for TVMC would be a simple tutorial planned to be sent by tomorrow. We will do our best to review and merge them before Oct 1st.

So, #6537 and #6578 would be the final two PRs to complete the first version of tvmc.

Per offline discussion with @leandron, the final PR for TVMC would be a simple tutorial planned to be sent by tomorrow. We will do our best to review and merge them before Oct 1st.

The mentioned tutorial PR is https://github.com/apache/incubator-tvm/pull/6597

@leandron @comaniac @tqchen
We are still waiting CI for #6597 and #6578 . I have added them into the release note and let's merge them tomorrow morning.

@leandron @comaniac @tqchen
We are still waiting CI for #6597 and #6578 . I have added them into the release note and let's merge them tomorrow morning.

Thanks. I am actually waiting to merge them today but still waiting for their CIs.

@ZihengJiang both were merged.

@comaniac cool, thanks. We plan to make a cut tomorrow.

https://github.com/apache/incubator-tvm/tree/v0.7


Error in README.md

I've seen an error in its readme file.
In this https://github.com/jonathantneal/precss/blob/master/README.md#mixins say 'background-url' when it should be "background-image".
A greeting and congratulations for your work

Fixed via https://github.com/jonathantneal/precss/pull/72


Sway workspaces module hover style

Is it possible to remove/change hover event of the module sway/workspace? (it creates a white border on top of the button)

Have a look here: https://github.com/Alexays/Waybar/wiki/FAQ#the-workspace-buttons-have-a-strange-hover-effect

Perfect, it fixed my problem :)
I think that should be by default inside style.css, maybe with a comment that link to that FAQ.

I'll add it in the default config file


feat(node): Generate events for data sampling that can be used by front-end

Events are not exposed to node-wasm yet. Should I do it now or after https://github.com/eigerco/lumina/pull/265?

there is high chance that the approach won't change after 265, so I'd say you can start already

Merged with bypassing two failing checks, @oblique checked manually that they're passing on previous nightly rust.


[WIP] Experiment with jpackage to create executable binaries

Based on https://dotnet.social/@fornever/112560707798240443, I tried to implement a generic jpackage target that can produce self-contained executables for any JavaModule (or ScalaModule). This is a WIP PR just to see what works.


Issue 158 - Builtin Error Metrics

Added a new "is_builtin" field to the error model.
Updated all errors created via fixtures to be flagged as built-in.
Added new field to REST services/docs.
Created a new errors daily metrics table that counts these error types based on job executions.

NOTE: Although there is a migration to add the new field, it will default all existing records to false. Production systems will need to manually change the value to true where applicable.
Closes #158

The fixtures should automatically update the existing builtin errors when the load_initial_data is run.
LGTM, merging.


No possibility to run tests with long VSTestTestCaseFilter

Description

I think this problem connected with Win API. CreateProccessA function has a limitation on lpCommandLine parameter. lpCommandLine. The maximum length of this string is 32,767 characters

Steps to reproduce

compose file with hundreds of test case filters, for example, tests.rsp:
/p:VSTestTestCaseFilter=(FullyQualifiedName="Test1")|(FullyQualifiedName="Test2")|...|(FullyQualifiedName="Test9999")
run dotnet test @tests.rsp

Expected behavior

tests should be run

Actual behavior

task failed unexpectedly

Diagnostic logs
C:\Program Files\dotnet\sdk\5.0.103\Microsoft.TestPlatform.targets(32,5): error MSB4018: System.ComponentModel.Win32Exception (206): The filename or extension is too long.
C:\Program Files\dotnet\sdk\5.0.103\Microsoft.TestPlatform.targets(32,5): error MSB4018:    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
C:\Program Files\dotnet\sdk\5.0.103\Microsoft.TestPlatform.targets(32,5): error MSB4018:    at System.Diagnostics.Process.Start()
C:\Program Files\dotnet\sdk\5.0.103\Microsoft.TestPlatform.targets(32,5): error MSB4018:    at Microsoft.TestPlatform.Build.Tasks.VSTestForwardingApp.Execute()
C:\Program Files\dotnet\sdk\5.0.103\Microsoft.TestPlatform.targets(32,5): error MSB4018:    at Microsoft.TestPlatform.Build.Tasks.VSTestTask.Execute()
C:\Program Files\dotnet\sdk\5.0.103\Microsoft.TestPlatform.targets(32,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
C:\Program Files\dotnet\sdk\5.0.103\Microsoft.TestPlatform.targets(32,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask)

Environment

OS Name:                   Microsoft Windows Server 2016 Standard
OS Version:                10.0.14393 N/A Build 14393
.Net SDK:                    5.0.103
MSBUILD:                   16.8.3+39993bd9d for .NET

Limit by OS, not by TestPlatform

Limit by OS, not by TestPlatform

Absolutely, but the test platform can import a huge filter from a file as an option to avoid restrictions.
For example, NUnit console runner support --testlist option to pass a list of tests as a file.
https://docs.nunit.org/articles/nunit/running-tests/Console-Command-Line.html#options

Some people have very large test suites!
Being able to specify easily a large sub-set of tests to execute seems to be a valid use case to me (think of splitting for parallel execution).
This is not possible with this command-line restriction, neither with /Tests (which by the way specifies search patterns, not exact test method names) nor /TestCaseFilter ...
(There might be some workarounds here but ...)

The solution linked above is stable, it is not just for VS: https://github.com/microsoft/vstest/issues/2273#issuecomment-595292726
Another option is using response files. They currently don't work with dotnet test and dotnet vstest, but work just fine for vstest.console. Tracking that bug here: https://github.com/microsoft/vstest/issues/3513

Ok, great, Thanks @nohwnd  for the clarification!


failure on some devices Object reference not set to an instance of an object.

I am getting a failure running this on some devices using Datto RMM,
in the stderr I just get the message
Log4Shell Enumeration, Mitigation and Attack Detection Tool [WIN]
Object reference not set to an instance of an object.
this device is a 2012 R2 Server

Hi;
Please direct all questions related to use of this Component via Datto RMM to Datto RMM Support.
The "object reference not set to instance of an object" error is an unintuitive way for the software to tell you that the job timed out. This may have been caused by setting the scan scope too wide for the timeout, which is set to an hour by default.
I will be pushing an update to the ComStore script shortly to add some adjustments (specific to RMM, so the GitHub script will not be receiving them) and at that time I will also adjust the timeout to make it longer.
When you see that this ComStore Component has an update available, apply it, then try re-running and see if you get the same error.


Suggest adding a check for comments in the Thrift files.

Thrift is a popular format for many IDLs, and it's possible to add comments to the IDL, such as adding comments to the fields of a struct, which can be used to generate documentation with explanations (such as the simplest thrift --gen html command). Therefore, a Linter that checks for the existence of comments can be very helpful in maintaining code standards. So, it might be worth considering adding some of these checks.
If possible, I would be willing to submit some PRs to do this.

This requires comment support in the underlying thriftrw, which thriftcheck uses to parse Thrift IDL files. I started on an implementation (https://github.com/thriftrw/thriftrw-go/pull/556) but wasn't able to finish it.

I've had a look and at this stage field has been implemented inside the field to get the comment, using the Doc field on it (I haven't seen the underlying implementation yet), this is currently ready to do some checking.
As for checking comments in many other places, may need to follow up with thrift-go to implement this
I know we can use //, /* xx */, /* xx */ in thrift file, etc., but only /* xx */ can be extracted as a description

Yes, if you're only interested in documentation block comments (/** ... */), you should have everything you need in the current code base.


WIP: Increase e2e info/json test exit timeout

Increase e2e info/json test exit timeout
For whatever reason, this specific test frequently fails on Ubuntu with
an error similar to:
  Timed out after 1.000s.
  Expected process to exit.  It did not.

  /var/tmp/go/src/github.com/containers/libpod/test/e2e/info_test.go:38

Ths changes alters the test behavior to use the defaultWaitTimeout
value (so 90 vs former 60 seconds) only for this test.
Signed-off-by: Chris Evich<EMAIL_ADDRESS>

@mheon By the looks of it, this is a one-line change to bump timeout by 30-seconds..  I fudged the tests to do 20x ubuntu runs, hopefully none will fail...

/approve

So 20x parallel ubuntu runs and no 'podman info' flake.  Removing the test-commit...

LGTM once the test commit is gone

/lgtm


[BUTTON IDEA]:CURL BOTTOM CORNERS ON HOVER

1. Name of button: CURL BOTTOM CORNERS ON HOVER
2. Description: Curls the bottom corners on hover
3. Button Type (Animated, Special, etc...):Animated
4. Will you work on it?:Yes of course

@wisetok12680 I'm not sure that's a good idea to be honest. Can you show me an example of it?

I had something like this in my mind.
Its okay I wasn't confident about it either. I would work for something similar.

That doesn't look bad. You can go ahead and work on it.

Hey there,
I don't understand why you closed the issue. I was about make PR as the button is ready.

@wisetok12680 I closed the issue since I didn't get any update from you on it and the button idea isn't essential to keep it in issues, but if you would like to submit a PR you still can.


docs: Standardise error messages format

Returned errors per service should have the following format:
fmt.Errorf("<service name>/<service component>: <error message>")

for example:
fmt.Errorf("header/store: no valid headers were given")

Ref.

Grooming 01/11/2022:
Good first issue -> renaming the title


Added lang attribute to literals in wikidata

Added lang attribute to literals as asked in the issue wherever a non-english literal could be expected. And made some indentation changes.

Good start, but #84 was meant to tag all literals in all files. The example shown in the issue is just an example and not the entire change needed.

okay so I have to add literals in whichever file available right? Do I need to add tag unordered lists literals too because it will be way too much complicated?

@Ainali I have made some more changes please check


[TEST] refactor longhorn-tests terraform scripts

What's the test to develop? Please describe
too many redundant/duplicate files and code in test_framework/terraform/aws/
Describe the items of the test development (DoD, definition of done) you'd like

Please use a task list for items on a separate line with a clickable checkbox https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists

[ ] modularize terraform scripts

cc @longhorn/qa


Change 'minion' to 'node' in docs

It's less than I wanted to get in, but better than nothing.

https://github.com/GoogleCloudPlatform/kubernetes/pull/10843 is also making a similar change

Few comments, but first pass looks good to me.

new push is up

LGTM other than the one typo that was introduced

LGTM

Got unresolved merge conflicts

Merge resolved.  Watching shippable.  So tired of saying that.

LGTM

1/2 shippable fails the same way every time:
--- FAIL: TestServiceRegistryIPUpdate (0.01s)
rest_test.go:698: Unexpected error type: <nil>
FAIL
coverage: 74.8% of statements
FAIL	github.com/GoogleCloudPlatform/kubernetes/pkg/registry/service	0.122s

But it passes for me manually.

Merge and cross fingers.


python3Packages.aio-georss-gdacs: 0.4 -> 0.5

Motivation for this change
Update to latest upstream release 0.5
Change log: https://github.com/exxamalte/python-aio-georss-gdacs/releases/tag/v0.5
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126130 at 7f6056dd run on aarch64-linux 1

2 packages built successfully:

python38Packages.aio-georss-gdacs
python39Packages.aio-georss-gdacs


INVALID_LED_DETAILS, Must specify both ledOnMs and ledOffMs to configure the blink cycle on older versions of Android before Oreo

@Junama
When opening an issue, please use the template and fill out requested details to properly address this issue.
Closing as no info is provided.


Trait for common ops

Client should define a trait for the common operations against and API, e.g. list, get, create, update, delete.
Then each api object can implement this trait and the client can implement a common set of functions to call them.
Lastly a macro can be written to provide default implementations of the trait functions.

Macro not yet implemented.


Hey @Sean-Bradley, a few observations:

Hey @Sean-Bradley, a few observations:

what's the problem with buttons being recreated on each render? Is there some scaling issue that I'm not aware of?
there's no problem with bypassing the  exhaustive-deps lint rule in general, as long as you know what you're doing. We actually do that a lot in Leva 🤧

However, here the solution to your problem is pretty obvious:
 const buttons = useMemo(() => {
     const _buttons = {}
    positions.forEach((p, i) => {
      _buttons['button ' + i] = button(() => setTo(p))
    })
   return _buttons
  }, [positions, setTo])

And if you're a fan of the reduce function:
 const buttons = useMemo(() => positions.reduce((acc, p, i) =>
  Object.assign(acc, { [`button ${i}`]: button(() => setTo(p)) }), {}), [positions, setTo])

Originally posted by @dbismut in https://github.com/pmndrs/leva/discussions/393#discussioncomment-3881633

What are you doing. You are copying/pasting from an issue that was already solved and closed.
https://github.com/pmndrs/leva/discussions/393#discussioncomment-3881633
I think you shgould delete this issue.


Adding sub-domains to a domain in Amplify Apps

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting questions.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d3n83m9lokqccc
AWS Region
ap-south-1
Amplify Hosting feature
Not Applicable
Is your feature request related to a problem? Please describe:
There is a way to add new sub-domains.
Domain management --> Manage subdomains --> Add
But there is no way to achieve this programmatically.
Describe how you'd like this feature to work
I would like to add new sub-domains programmatically through an API call or by using SDKs.

Hi @lifehetu, have you had a chance to look at the UpdateDomainAssociation API? This should allow you to use the AWS SDK/CLI to programmatically add subdomain by updating an existing Domain association.
Let me know if this is something that would work for you.

Hi,
I did have a look at this API but this API supposedly automates subdomain
creation for the linked code repository branch. I need to add a sub-domain
without needing to associate it with any branch.
Please let me know if my understanding is correct. Thanks for your response.
[image: image.png]
Thanks,
Puneet Pandey,
LifeHetu Technology.
On Wed, 24 May 2023 at 21:40, Dan Kiuna @.***> wrote:

Hi @lifehetu https://github.com/lifehetu, have you had a chance to look
at the UpdateDomainAssociation
https://docs.aws.amazon.com/amplify/latest/APIReference/API_UpdateDomainAssociation.html
API? This should allow you to use the AWS SDK/CLI to programmatically add
subdomain by updating an existing Domain association.
Let me know if this is something that would work for you.
—
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-hosting/issues/3401#issuecomment-1561488044,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUTKSX7PKHRFLY2ROLIQD5LXHYXHZANCNFSM6AAAAAAWOS4NQI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @lifehetu following up here - you are correct, however currently it is not possible to add a subdomain without associating it with any branch. I can mark this as a feature request, and I'd like to gather more specific information on your use case. Could you elaborate?


feat(turbo): task access trace & cached configs

Description
v0 of work required for zero config (experimental):

Support config caching
Support task tracing

Requires: https://github.com/vercel/next.js/pull/59553
TODO

[ ] Testing
[ ] Support caching outputs on first run instead of second (turbo.json uncoupling)

@chris-olszewski PR updated.
There were a lot of conflicts here, so split the commits between resolving conflicts, and addressing review. But let me know if you have any questions!
NOTE: This is stacked on top of https://github.com/vercel/turbo/pull/7293


fix: merge azion.config user with preset azion.config

Merge Azion Config
This PR refactors the code in the Dispatcher class to merge the user'sazion.config.js file with the preset azion.config.js file. It uses the lodash.mergeWith function to combine the two configurations, giving priority to the user's config. This ensures that the final configModule used in the code is a merged version of the two configurations.
Bonus
Fix: Typo in pre-build success message

:tada: This PR is included in version 4.0.1-stage.1 :tada:
The release is available on:

npm package (@stage dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Deploy:vendor step--composer install success but not completely

Q
A

Issue Type
Question

Deployer Version
master

Local Machine OS
windows 10 pro 1803

Remote Machine OS
CentOS Linux release 7.4.1708 (Core)

Description
When deployer run the deploy:vendor step
 cd /var/www/demo-app/releases/19 && /usr/bin/php /usr/local/bin/composer install --verbose --prefer-dist --no-progress --no-interaction --no-dev --optimize-autoloader

Here's the log
[<IP_ADDRESS>] < Loading composer repositories with package information
[<IP_ADDRESS>] < Installing dependencies from lock file
[<IP_ADDRESS>] < Dependency resolution completed in 0.000 seconds
[<IP_ADDRESS>] < Analyzed 112 packages to resolve dependencies
[<IP_ADDRESS>] < Analyzed 235 rules to resolve dependencies
[<IP_ADDRESS>] < Package operations: 53 installs, 0 updates, 0 removals
[<IP_ADDRESS>] < Installs: doctrine/inflector:v1.3.0, doctrine/lexer:v1.0.1, erusev/parsedown:1.7.1, vlucas/phpdotenv:v2.5.0, symfony/css-selector:v4.1.1, tijsverkoyen/css-to-inline-styles:2.2.1, symfony/polyfill-mbstring:v1.8.0, symfony/var-dumper:v3.4.12, symfony/routing:v3.4.12, symfony/process:v3.4.12, symfony/polyfill-ctype:v1.8.0, paragonie/random_compat:v2.0.17, symfony/polyfill-php70:v1.8.0, symfony/http-foundation:v3.4.12, symfony/event-dispatcher:v4.1.1, psr/log:1.0.2, symfony/debug:v3.4.12, symfony/http-kernel:v3.4.12, symfony/finder:v3.4.12, symfony/console:v3.4.12, egulias/email-validator:2.1.4, swiftmailer/swiftmailer:v6.1.2, ramsey/uuid:3.7.3, psr/simple-cache:1.0.1, psr/container:1.0.0, symfony/translation:v4.1.1, nesbot/carbon:1.32.0, mtdowling/cron-expression:v1.2.1, monolog/monolog:1.23.0, league/flysystem:1.0.45, laravel/framework:v5.5.40, fideloper/proxy:3.3.4, psr/http-message:1.0.1, guzzlehttp/psr7:1.4.2, guzzlehttp/promises:v1.3.1, guzzlehttp/guzzle:6.3.3, hieu-le/active:3.5.1, jakub-onderka/php-console-color:0.1, predis/predis:v1.1.1, cakephp/chronos:1.2.2, laravel/horizon:v1.3.1, nikic/php-parser:v4.0.3, jakub-onderka/php-console-highlighter:v0.3.2, dnoegel/php-xdg-base-dir:0.1, psy/psysh:v0.9.6, laravel/tinker:v1.0.7, intervention/image:2.4.2, mews/captcha:2.2.0, ezyang/htmlpurifier:v4.10.0, mews/purifier:2.1.0, caouecs/laravel-lang:3.0.54, overtrue/laravel-lang:3.0.8, overtrue/pinyin:3.0.6
[<IP_ADDRESS>] <   - Installing doctrine/inflector (v1.3.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing doctrine/lexer (v1.0.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing erusev/parsedown (1.7.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing vlucas/phpdotenv (v2.5.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/css-selector (v4.1.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing tijsverkoyen/css-to-inline-styles (2.2.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/polyfill-mbstring (v1.8.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/var-dumper (v3.4.12): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/routing (v3.4.12): Loading from cache
[<IP_ADDRESS>] <  Extracting archive
[<IP_ADDRESS>] <   - Installing symfony/process (v3.4.12): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/polyfill-ctype (v1.8.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing paragonie/random_compat (v2.0.17): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/polyfill-php70 (v1.8.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/http-foundation (v3.4.12): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/event-dispatcher (v4.1.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing psr/log (1.0.2): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/debug (v3.4.12): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/http-kernel (v3.4.12): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/finder (v3.4.12): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/console (v3.4.12): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing egulias/email-validator (2.1.4): Loading from cache
[<IP_ADDRESS>] <  Extracting archive
[<IP_ADDRESS>] <   - Installing swiftmailer/swiftmailer (v6.1.2): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing ramsey/uuid (3.7.3): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing psr/simple-cache (1.0.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing psr/container (1.0.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing symfony/translation (v4.1.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing nesbot/carbon (1.32.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing mtdowling/cron-expression (v1.2.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing monolog/monolog (1.23.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing league/flysystem (1.0.45): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing laravel/framework (v5.5.40): Loading from cache
[<IP_ADDRESS>] <  Extracting archive
[<IP_ADDRESS>] <   - Installing fideloper/proxy (3.3.4): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing psr/http-message (1.0.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing guzzlehttp/psr7 (1.4.2): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing guzzlehttp/promises (v1.3.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing guzzlehttp/guzzle (6.3.3): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing hieu-le/active (3.5.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing jakub-onderka/php-console-color (0.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing predis/predis (v1.1.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive
[<IP_ADDRESS>] <   - Installing cakephp/chronos (1.2.2): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing laravel/horizon (v1.3.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing nikic/php-parser (v4.0.3): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing jakub-onderka/php-console-highlighter (v0.3.2): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing dnoegel/php-xdg-base-dir (0.1): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing psy/psysh (v0.9.6): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing laravel/tinker (v1.0.7): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing intervention/image (2.4.2): Loading from cache
[<IP_ADDRESS>] <  Extracting archive
[<IP_ADDRESS>] <   - Installing mews/captcha (2.2.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing ezyang/htmlpurifier (v4.10.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing mews/purifier (2.1.0): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing caouecs/laravel-lang (3.0.54): Loading from cache
[<IP_ADDRESS>] <  Extracting archive
[<IP_ADDRESS>] <   - Installing overtrue/laravel-lang (3.0.8): Loading from cache
[<IP_ADDRESS>] <  Extracting archive  - Installing overtrue/pinyin (3.0.6): Loading from cache
[<IP_ADDRESS>] <  Extracting archive
[<IP_ADDRESS>] < Generating optimized autoload files
[<IP_ADDRESS>] < > post-autoload-dump: Illuminate\Foundation\ComposerScripts::postAutoloadDump
[<IP_ADDRESS>] < > post-autoload-dump: @php artisan package:discover
[<IP_ADDRESS>] < Discovered Package: fideloper/proxy
[<IP_ADDRESS>] < Discovered Package: hieu-le/active
[<IP_ADDRESS>] < Discovered Package: intervention/image
[<IP_ADDRESS>] < Discovered Package: laravel/horizon
[<IP_ADDRESS>] < Discovered Package: laravel/tinker
[<IP_ADDRESS>] < Discovered Package: mews/captcha
[<IP_ADDRESS>] < Discovered Package: mews/purifier
[<IP_ADDRESS>] < Discovered Package: nesbot/carbon
[<IP_ADDRESS>] < Discovered Package: overtrue/laravel-lang
[<IP_ADDRESS>] < Package manifest generated successfully.

When deploy finish, I change directory to current/vendor and found something missing.Here is the packages when deploy finish:
autoload.php  cakephp  composer  doctrine  erusev  fideloper   hieu-le       jakub-onderka  league  monolog    nesbot  overtrue   predis  psy     swiftmailer  tijsverkoyen
bin           caouecs  dnoegel   egulias   ezyang  guzzlehttp  intervention  laravel        mews    mtdowling  nikic   paragonie  psr     ramsey  symfony      vlucas

Change the directory to current and run composer install.When it finish, the packages:
autoload.php  cakephp   dnoegel   erusev     filp        hamcrest      jakub-onderka  maximebf  monolog    nesbot    paragonie      phpspec  psr     sebastian    symfony       vlucas
barryvdh      caouecs   doctrine  ezyang     fzaninotto  hieu-le       laravel        mews      mtdowling  nikic     phar-io        phpunit  psy     summerblue   theseer       webmozart
bin           composer  egulias   fideloper  guzzlehttp  intervention  league         mockery   myclabs    overtrue  phpdocumentor  predis   ramsey  swiftmailer  tijsverkoyen

some packages like barryvdh/laravel-debugbar add. I need to run composer install again in the server. Is something I need to know? I'm a new userer of deployer.
Content of deploy.php
<?php
namespace Deployer;

require 'recipe/common.php';

// Project name
set('application', 'my_project');

// Project repository
set('repository', 'git@github.com:rust17/hello_laravel.git');

// [Optional] Allocate tty for git clone. Default value is false.
set('git_tty', false);

// Shared files/dirs between deploys
set('shared_files', ['.env']);
set('shared_dirs', [
	'storage'
	]);

// Writable dirs by web server
set('writable_dirs', []);

set('cleanup_use_sudo', true);
set('ssh_multiplexing', false);

// Hosts

host('<IP_ADDRESS>')
    ->user('deployer')
    ->identityFile('~/.ssh/deployerkey')
    ->set('deploy_path', '/var/www/demo-app');

// Tasks

desc('Deploy your project');
task('deploy', [
    'deploy:info',
    'deploy:prepare',
    'deploy:lock',
    'deploy:release',
    'deploy:update_code',
    'deploy:shared',
    'deploy:writable',
    'deploy:vendors',
    'deploy:clear_paths',
    'deploy:symlink',
    'deploy:unlock',
    'cleanup',
    'success'
]);

// [Optional] If deploy fails automatically unlock.
after('deploy:failed', 'deploy:unlock');

Output log
see above

I found those packages are require-dev.So I add this into my deploy.php:
set('composer_options', 'install --verbose --prefer-dist --no-progress --no-interaction --optimize-autoloader');

It works.
And those may be helpful:
https://github.com/deployphp/deployer/issues/878
https://github.com/deployphp/deployer/issues/1298


Optimise/add receipt[-*] icons

Closely related to #1402 and #1406.

Use cases:

To indicate totals of an order in a (online) store
Menu item "receipts" of an online store.


Pre-processing slow for Subtask A on a dataset of 30,000 entries

Hi!
First, thanks for sharing the code!
I am trying to run the Subtask A on a different language (Latvian) dataset of ~30,000 entries, but the pre-processing takes now more than a day (and is stuck at 89% for over 8 hours). It seems that the disk usage is at 9% (why does it require so much disk I/O?), but the RAM usage is only at 1.5-3GB out of 16GB (i.e., there is plenty left). In terms of CPU, only one thread (out of 12) is used at 100%. I have my own word embedding file (from FastText). That is ~1.5GB large. Apart from that I just removed everything from the download directory, placed there the 30,000 dataset file (in the same format as the other files and also named as one of the training files), and replaced the contents of the test and gold files with a dataset of 1000 entries.
I have two questions:

Does the fact that there is English hard-coded in the (pre-processing) code mean that the solution won't support other languages out-of-the-box (i.e., without re-writing the pre-processing part)? I have pre-processed the data externally using my own tools. So ... all that I would expect to be done internally, would be splitting tokens on spaces.
What is the part that slows everything down so much and do you have an idea of whether it is reasonable to remove the part that is so slow?

Hi @pmarcis,
Can you please check if there is a token with an unusual large length in your dataset? In the past I have encountered a similar problem, where there was a token in my dataset consisting of 150+ characters. I assume that this issue has to do with ekphrasis (regex pattern matching).

Hi!
I am working on a tweet dataset. The dataset contained one token of 90 symbols. Apart from that everything else looks normal. I stopped the process after 3 days. It finished processing the 30K entry dataset, but got stuck on the evaluation set (for a bit less than 2 days), which did not have any abnormally long tokens.
I looked at the ekphrasis code and changed the segment function to (was this enough to skip the pre-processing?):
def segment(self, word):
        if word.islower():
            #return " ".join(self.find_segment(word)[1])
            return word
        else:
            return word

This seems to have fixed the data preprocessing speed issue. However, I am getting rather low precision scores out of the classifier - ~30-40% (in comparison - the lstm implementation from mxnet-sentiment-analysis without word embeddings achieves precision of 46%, a perceptron classifier shows to be even better at 59% without using positive/negative word lists). I am wondering whether I am doing something wrong? Am I right to assume that tweet IDs are not used?

After profiling ./models/nn_task_message.py I determined that the @lru_cache directives in ekphrasis ./classes/segmenter.py are very small. I upped them both to 262144 in size. The pre-processing now takes less than a minute (as compared to days) and the memory footprint looks to be around 1.1GB.

True, I also had problems here. Pre-processing took more than 6 hours to reach 80%, and then it stuck there for more than 10 hours till I killed the process.
Had around 15'000x speedup (takes few seconds) in the processing speed once I increased lru_caches from 4096 to 8192 and 10000, as well as de-comment some lru_caches that were disabled in the pip-installed ekphraris module.
I would seriously recommend changing this repo to include a modified ekphraris here, if @cbaziotis don't want to have the caches turned on in the ekphraris repo.

Ok, I increased the cache size in ekphrasis. Please upgrade:
pip install ekphrasis -U


Function to disable a connection

Write a function that uses the NM DBus API to disable a previously configured connection.
It should take a connection, it should return a result.
Questions:

How should the connection be passed in?

Object path
SSID
SNR
??

Should the function return instantly or once the connected has been successfully disabled, should this be optional?
Should the function accept a timeout, should this be optional?

https://github.com/resin-io/hq/pull/453


[Ambari-23041] Increase config combo widget width

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/728/
Test PASSed.


bison: 3.1 -> 3.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bison/versions.
meta.description for bison is: '"Yacc-compatible parser generator"'.

Checks done (click to expand)

built on NixOS
/nix/store/y5hjzpxdr0r4qxjkknmlcqm19rg0nkd0-bison-3.2/bin/bison passed the binary check.
/nix/store/y5hjzpxdr0r4qxjkknmlcqm19rg0nkd0-bison-3.2/bin/yacc passed the binary check.
2 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 3.2 with grep in /nix/store/y5hjzpxdr0r4qxjkknmlcqm19rg0nkd0-bison-3.2
directory tree listing: https://gist.github.com/c245c562c4d0283a2c82bad472a988b9
du listing: https://gist.github.com/c47702f26251f09c731e96af743f9c16

Outpath report (click to expand)

Outpath difference report
82738 total rebuild paths
26788 package rebuilds
26640 x86_64-linux rebuilds
20914 i686-linux rebuilds
14922 x86_64-darwin rebuilds
20262 aarch64-linux rebuilds
First ten rebuilds by attrpath
AMB-plugins
AgdaSheaves
AgdaStdlib
CoinMP
DisnixWebService
EBTKS
EmptyEpsilon
FIL-plugins
Fabric
LASzip

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/y5hjzpxdr0r4qxjkknmlcqm19rg0nkd0-bison-3.2 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A bison https://github.com/r-ryantm/nixpkgs/archive/43af73d701e2311370c049c3e69057352539e91c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/y5hjzpxdr0r4qxjkknmlcqm19rg0nkd0-bison-3.2
ls -la /nix/store/y5hjzpxdr0r4qxjkknmlcqm19rg0nkd0-bison-3.2/bin

Duplicate of #49454


image upload (ignore)

https://github.com/teia-community/teia-blog/assets/97635650/c0c62455-2ec8-44c8-81ab-794126938240


[CLI][python-package][docs] Add n_estimators as num_iteration alias

Scikit-Learn's ensemble methods use the term n_estimators for the number of
iterations of training models. To make it more accessible for newcomers who are
familiar with Scikit-Learn, it would help if the Parameters page mentioned
n_estimators and what parameter that maps to within LightGBM's API.
Addresses discussion brought up in #954

I felt like this might help smooth adoption for any people coming from Scikit-Learn's API.

@mathcass Did you add the parameter in C++? I can't find it in your commit.
As n_estimators seems to be a scikit-learn exclusive parameter, it should not be in docs/Parameters.rst .

ping @wxchan or @StrikerRUS

I suppose the best solution is to edit the first Note in Parameters.rst:

... methods instead and n_estimators in sklearn wrapper

@StrikerRUS, Thanks!
Here's how changing the wording on the Scikit-Learn API would look https://github.com/mathcass/LightGBM/commit/8ad98ea568780902045f74d775fddd820c8e19c2
I think in some sense, that may make more sense, because users of other APIs don't need to know a thing about n_estimators and thus don't need another term to get confused about. @Laurae2's original question in the PR made me realize that Paramters.rst might not be the best place for this.
Alternatively, here's how your recent suggestion would look, https://github.com/mathcass/LightGBM/commit/07482be795426179a916b57c3c2c244a8b7714e8
so that it sits alongside the notes about Python & R-specific parameters.
I think personally, I favor the note being specifically in the sklearn implementation because the sklearn API sits atop the core API and not vice versa.

@mathcass What do you think about merging two your variants into one? I think it's good point to write as more details as we can if it leads to better users' understanding.
But please notice that your second variant needs paraphrase because there is no train and cv methods in sklearn wrapper.

I think it is better to add the parameter both in C++ and the documentation so there are no confusion for quick readers who don't read the documentation carefully.

@mathcass
OK, update please default value here to 100 for consistency:
https://github.com/Microsoft/LightGBM/blob/8a5ec366aa5b0ec6301cb6ca8e85a70cc7ac4cf1/python-package/lightgbm/sklearn.py#L136
https://github.com/Microsoft/LightGBM/blob/8a5ec366aa5b0ec6301cb6ca8e85a70cc7ac4cf1/python-package/lightgbm/sklearn.py#L157
https://github.com/Microsoft/LightGBM/blob/8a5ec366aa5b0ec6301cb6ca8e85a70cc7ac4cf1/python-package/lightgbm/engine.py#L325
https://github.com/Microsoft/LightGBM/blob/8a5ec366aa5b0ec6301cb6ca8e85a70cc7ac4cf1/python-package/lightgbm/engine.py#L310
Add n_estimators here:
https://github.com/Microsoft/LightGBM/blob/8a5ec366aa5b0ec6301cb6ca8e85a70cc7ac4cf1/python-package/lightgbm/engine.py#L96
https://github.com/Microsoft/LightGBM/blob/8a5ec366aa5b0ec6301cb6ca8e85a70cc7ac4cf1/python-package/lightgbm/engine.py#L386
https://github.com/Microsoft/LightGBM/blob/8a5ec366aa5b0ec6301cb6ca8e85a70cc7ac4cf1/include/LightGBM/config.h#L404

@mathcass
Do you have time to take this job?

@StrikerRUS, sorry, had a busy week.
I can give this a shot in the coming week. Unless there's some urgency to get it done sooner.

@mathcass Yeah, sure! It's not urgent at all.

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

Thank you for the pointers on making this change @StrikerRUS! I've pushed them up to this PR. I can confirm that building the app works and running the CLI tool on each of the examples works. Changing a tree-based parameter in any of the train.conf files within the examples seems to work.
cd examples/binary_classification
sed -i 's/num_trees = 100/n_estimators = 47/' train.conf
../../lightgbm config=train.conf

[LightGBM] [Info] Finished loading parameters
[LightGBM] [Info] Loading weights...

...

[LightGBM] [Info] Iteration:47, valid_1 binary_logloss : 0.508427
[LightGBM] [Info] 0.328891 seconds elapsed, finished iteration 47
[LightGBM] [Info] Finished training

@mathcass Many thanks for your contribution!


New label smoothing

See https://github.com/k2-fsa/icefall/issues/107
This PR modifies custom LabelSmoothing to match the implementation in PyTorch and in the original paper.

I run an experiment with this new LabelSmoothing, the result is the same as baseline (actually slightly better).

New LabelSmoothing
Tensorboard: https://tensorboard.dev/experiment/PwsxEyJsQ1qRXjvjWjDLNQ/#scalars

Results:

Baseline
Tensorboard : https://tensorboard.dev/experiment/ubHmWJXZRK6VlEPzoqlTqw/#scalars

Results:

Here is the WER for using this PR.

The following table compares the WER of this PR with the one from the master

test-clean
test-other

Master branch
2.42
5.73

This PR
2.59
5.59

I am going to merge it.