Added app.js to spawn service scripts, PM2 compatibility

Issue: https://github.com/bitpay/bitcore-wallet-service/issues/597
Start app with PM2:
pm2 start app.js --name "bitcoin-wallet-service"

Coverage remained the same at 81.216% when pulling dee50e8d30ef1ffd52382402cc8ad0b5bd0636da on huangbong:master into 3fb33218a7e995c178e670cd6bda741edcb1be14 on bitpay:master.

Coverage remained the same at 81.216% when pulling dee50e8d30ef1ffd52382402cc8ad0b5bd0636da on huangbong:master into 3fb33218a7e995c178e670cd6bda741edcb1be14 on bitpay:master.

:100:!  Yes please!  You might also be interested in running Insight using PM2, something I tried to do before this repo existed.  Exciting to see someone else doing the same thing here!
May I suggest renaming it to bws.js or something non-generic, so PM2 automatically displays a correct name?  This will reduce confusion with other processes managed by the same instance.

Is there anything pending with this PR in order to merge into master? Renaming app.js to bws.js ?

as stated by @huangbong, we can use --name option of PM2.
e.g.
pm2 start app.js --name "bitcoin-wallet-service"

Sorry the delay, thanks for the contribution!

I added some related doc on the readme.


Error: System shows future date in backup

Recent messages not backing up because last backup date shows July 7, 2020 which is in the future (today is June 25, 2020)

Android version 9
Samsung Galaxy S8
SMS Backup+ version installed 1.5.11
Messaging app standard google messages version <IP_ADDRESS>

Any chance your cellular provider messed up the clock on your device?

Hi Martin,
I don't think the carrier is the problem. I haven't had any other issues.
I uninstalled and reinstalled the app.
Same problem persists today. I attached a screenshot I just took. The app
updated the mms & call log today. The sms date is still incorrect.
Thanks for replying!
On Fri, Jun 26, 2020, 6:52 AM Martin Kealey<EMAIL_ADDRESS>wrote:

Any chance your cellular provider messed up the clock on your device?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jberkel/sms-backup-plus/issues/1024#issuecomment-650138764,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQCOE55CB275DE6G4S2FF5LRYSDZHANCNFSM4OIPNJPA
.

I'm considering the case where the clock in your phone is wrong for a brief period, during which a backup occurs. Unless you're looking at the phone at the time you probably wouldn't notice anything. And yes, phone carriers do screw up their clocks quite often.
Then to avoid overloading the IMAP server, SMS Backup+ does not make another backup until a minimum time after the previous backup - which happens to be 2 weeks in the future.
Restarting or even reinstalling the app won't help so long as that "lasted backed up" time is still recorded.
The problem will resolve itself in 9 days' time, but I will see if I can track down where the last-backed-up date is stored.

@android987987 can you confirm that backups have returned to normal operation as the "future" date has now passed?
(I will continue to investigate in case anyone else encounters this problem.)

Yes they have. Thank you!
On Thu, Jul 9, 2020, 7:34 PM Martin Kealey<EMAIL_ADDRESS>wrote:

@android987987 https://github.com/android987987 can you confirm that
backups have returned to normal operation as the "future" date has now
passed?
(I will continue to investigate in case anyone else encounters this
problem.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jberkel/sms-backup-plus/issues/1024#issuecomment-656417618,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQCOE52VK4OG7DNDP35M7CDR2ZO23ANCNFSM4OIPNJPA
.

I have a similar problem. I received an SMS dated for the year 2221, so SMS Backup is stuck until that time. Unlike the first poster, I can't wait this out! Can someone help suggest a resolution?

@haroldong8 Some possibilities include:

setting the system clock of your device to the far future (requires turning off GPS and NTP/network time synch), or
going "clear data" (or equivalently, uninstalling and reinstalling),
or using adb to download the database file, modify it, and upload it again. Sadly the latter requires your phone to be in unrestricted developer mode (aka "rooted"), and getting into unrestricted developer mode requires erasure of the whole device.

Fortunately SMS Backup+ doesn't store messages on your phone, just its settings and its next-time-to-run timestamp, so clearing the app data isn't the end of the world. Just make sure you've written down the settings including the app password first - or you could generate a new app password and revoke the old one.
Reminder: Google's IMAP server is imap.gmail.com, not imap.google.com.


[IMP] Add env var expansion for repo.yml

Expand environment variables in repo.yml before use

My use case being a dynamic odoo version, which interestingly enough could also work for module branches too.

Don't you think PR for gitaggregator would be better?

Env vars seem a bit more on the side of the system configuration vs. a CLI tool IMO, but I could be wrong. TBH this is the first I've heard of the tool, so I'm not sure of a use case outside of this one. If you think I should submit that way though, I don't have any problems with it.
TIL with envsubst - not sure how I've gone this long in life without needing it! Updated.

I added a little fix, but there's still a problem: this would break the scaffolding's setup-devel step.
We could either support this also in tecnativa/git-aggregator or you could propose this PR to upstream.

Hrmmm alright so out of the choice of git-aggregator Docker container vs. library, library is probably best. Seems like the feature would get buried. PR in https://github.com/acsone/git-aggregator/pull/8

Nice, I merged acsone/git-aggregator#8 in our fork's master branch, so you have it in https://hub.docker.com/r/tecnativa/odoo-base/~/settings/automated-builds/

Hooray thanks @Yajo! This feature should help me quite a bit 😄


Limit max-width of timeline to 100%

An extremely long code line caused the layout to exceed window width and a horizontal window scrollbar appeared.
Test case:
a {
    background-image: url("data:image/svg+xml !important;utf8,<svg xmlns='http://www.w3.org/2000/svg' width='100' height='100' > <polygon points='0,0 50,100 100,0' fill='#888' stroke='#000' stroke-width='1' /> </svg>"); background: url("data:image/svg+xml !important;utf8,<svg xmlns='http://www.w3.org/2000/svg' width='100' height='100' > <polygon points='0,0 50,100 100,0' fill='#888' stroke='#000' stroke-width='1' /> </svg>");
}

1280px browser window before the fix:

After:

Instead of using calc, can we identify the problem that causes this?

The problem appears because of width: auto !important; in github-wide style.

I'm asking because it's not fixing the source problem, it's just another patch to fix something caused by some other CSS :). I've not real problem with calc other than we likely don't need it.

It's a combination of both #22 and width: auto on .discussion-timeline. Adding a max-width of ~85% on the flexed .discussion-timeline would work as well.

calc is more precise than ~85%, and I still don't get what's wrong with patching. Anyway it works4me, so...

I think we're good to go on this—I changed some stuff up around the columns with the latest updates.


TLS error when trying to reconnect to MQTTS broker after loosing internet connection (IDFGH-4633)

Environment

Module or chip used:  ESP32-WROVER-B

IDF version (run git describe --tags to find it):
4.0.1

Build System:        idf.py

Compiler version (run xtensa-esp32-elf-gcc --version to find it):
8.2.0

Operating System:     Linux

Using an IDE?: No

Power Supply:        external 5V

Problem Description
I use ESP to send data on broker via MQTTS. The internet connection is done via ethernet. The first connection on the broker (after a reboot) always work fine but it happens that internet connection is lost and when ESP is reconnected to internet, I have TLS error "The certificate is not correctly signed by the trusted CA" when it try to reconnect to the broker.
Expected Behavior
The esp is able to reconnect to the broker via MQTTS
Actual Behavior
The esp fail to verify the certificate even if it has already verified it during the first connection to the broker
Steps to reproduce

Start a mqtt connection to a broker with CA, CERT and PRIVATE KEY
Disconnect the ethernet cable
Reconnect the ethernet cable

Debug Logs
E (64123) esp-tls: mbedtls_ssl_handshake returned -0x2700
I (64133) esp-tls: Failed to verify peer certificate!
I (64133) esp-tls: verification info:   ! The certificate is not correctly signed by the trusted CA
E (64143) esp-tls: Failed to open new connection
E (64143) TRANS_SSL: Failed to open a new connection
E (64163) MQTT_CLIENT: Error transport connect
E (64163) MQTT_MANAGER: MQTT_ERROR_TYPE_ESP_TLS: esp_tls_last_esp_err = 32784
E (64163) MQTT_MANAGER: MQTT_ERROR_TYPE_ESP_TLS: esp_tls_stack_err = 9984
E (64173) MQTT_MANAGER: MQTT_ERROR_TYPE_ESP_TLS: esp_tls_cert_verify_flags = 8
I (64183) MQTT_MANAGER: MQTT_EVENT_DISCONNECTED
Other items if possible
mqtt_cfg.client_cert_pem = (char *)mqtt_cert_crt;
mqtt_cfg.client_key_pem = (char *)mqtt_cert_key;
mqtt_cfg.cert_pem = (char *)mqtt_cert_ca;

Hi @FrGrQuim
Is this happening every time you unplug the ethernet and plug again?
Could you please share more verbose log for us to better understand the problem?
Please enable mbedTLS debugging in component config:
(Top) → Component config → mbedTLS
[*] Enable mbedTLS debugging

And post just the last failing handshake (note that some part of the console log may contain your private key)
Also, thinking of potential memory corruption of the referenced data, please double check that the pointers to the certificates and keys remain valid for entire application lifetime as mentioned here: https://github.com/espressif/esp-idf/blob/master/components/tcp_transport/include/esp_transport_ssl.h#L63

Hi @FrGrQuim
Is this happening every time you unplug the ethernet and plug again?
Could you please share more verbose log for us to better understand the problem?
Please enable mbedTLS debugging in component config:
(Top) → Component config → mbedTLS
[*] Enable mbedTLS debugging

And post just the last failing handshake (note that some part of the console log may contain your private key)
Also, thinking of potential memory corruption of the referenced data, please double check that the pointers to the certificates and keys remain valid for entire application lifetime as mentioned here: https://github.com/espressif/esp-idf/blob/master/components/tcp_transport/include/esp_transport_ssl.h#L63

This happens every time internet connection is lost even if the ethernet cable isn't unpluged (I unplug ethernet cable in order to simulate it). I will make a test in order to check if the pointer to cert files are OK. While waiting it a send you the logs a have with mbedtls debug enable.
MQTTS_fail_logs.log

This happens every time internet connection is lost even if the ethernet cable isn't unpluged (I unplug ethernet cable in order to simulate it). I will make a test in order to check if the pointer to cert files are OK. While waiting it a send you the logs a have with mbedtls debug enable.
MQTTS_fail_logs.log

Can someone help me? I can give more information if required.

@FrGrQuim The log above shows a different failure, but this time it failed to parse the private key. This seems like the original thought on corruption of the cert data sounds more plausible.
Could you please post the portion of your code where you allocate the cert/key data? Or a simple check could be to just print out the textual data to the console and check if it stays the same after reconnecting; you can use BEFORE_CONNECT event for that.

@FrGrQuim Thanks for reporting, would you please help share if any updates for the issue? Thanks.

@FrGrQuim Thanks for reporting. Would you please help share if any updates for this issue? Thanks.


Enhance light client verification functions for standalone use

Description
Currently, the verification functions in ibc-rs such as verify_header and verify_misbehaviour require a validation context interface to be provided. However, many of the interface functions within the context are not actually used in these verification functions.
For example, in the verify_header function, it would create a better user experience to allow the user to provide host_timestamp and trusted_consensus_state directly rather than the entire context.
Use case
I am trying to use ibc-rs's 07-tendermint with Succinct's sp1 to create a POC ZK IBC light client for use in Solidity. In this context, it makes sense to avoid maintaining a full light client context and state. This issue is not a blocker but could significantly improve the UX.
Note
I acknowledge that I might not have the full context of the current implementation and usage patterns. If this functionality is already possible or if there are reasons for the current design that I might have missed, I would appreciate any guidance or feedback on this suggestion.

I hear you. We will consider upstreaming your suggestions.
But I am curious how you are using them. It sounds like we can benefit from keeping a consistent light client trait between sp1 usecase and ibc-rs. (We did the same for wasm light clients.)
Can you please share your work (here over slack)?

https://github.com/srdtrk/sp1-ics07-tendermint Here is my work. It can already verify the ZK proofs for ibc-rs's 07-tendermint in Solidity.


MSID: 91685 Version: 2 DOI: 10.1101/2<IP_ADDRESS>7916

MSID: 91685
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>7916
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=91685
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>7916

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/91685v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>7916
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/91685/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: [journal-ref-article-title] This journal reference (id c21) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c32) has no article-title element.
error: [journal-ref-article-title] This journal reference (id c33) has no article-title element.
error: [journal-ref-article-title] This journal reference (id sc22) has no article-title element.
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c29) has a publication-type='other'. Is that correct?
warn: [title-upper-case] Content of  element is entirely in upper case: Is that correct? 'SUPPLEMENT'


Ability to include code outside of project root

Use-case: uncovering and removing un-needed dependencies from large applications
I work on a HUGE application with 50+ gems as dependencies. It's become evident that there are a few gems that were included early on in the project's life that may no longer be necessary or that may be rarely used (maybe one method from it is needed, for example).
The more dependencies there are, the slower the application is when running the tests, starting the app, running rake tasks, starting the console, etc. Finding the least-used gems by using a coverage tool when running the complete suite of specs/cukes would be an ideal way to remedy this problem.

Closing as stale. Please reopen if this is still an issue. (And take a look at https://github.com/colszowka/simplecov/issues/340 )


Kapex Upgrade fails due to bug in Totem fork of Transaction Payment Pallet

Background
The SR Labs audit on the Totem Accounting Parachain Pallets highlighted an issue with the illegal use of sp_io::offchain::random_seed() in the Accounting Pallet.
The audit was conducted after the code head had been uploaded to Polkadot, and after the Kapex Parachain had won a parachain slot.
Our initial reaction was that we could fix this bug with an upgrade.
The bug does not affect block production or collation for the Kapex Parachain, however it does prevent the ability to upgrade the network as described here. The upgrade itself fails because it calls the offending function.

The bug
In a previous iteration the code had been commented, however that comment was lifted in the days before the final head and wasm blob were created for reasons that are lost in the mists of time in April 2022, possibly after transactions testing had already completed.
The severity of the issue was not realised until the audit. It was clear the code was illegal and so corrections were made to the code fixing the bug. This allowed the audit to continue and has now been applied to this branch which was expected to be the first upgrade.
The upgrade process
During the Call to parachainSystem -> authorizeUpgrade the Transaction Payment Pallet is called to reserve a fee.
As the Transaction Payment Pallet is non-standard (adapted to record the fee information into the accounting), this call unfortunately reaches the illegal code and would otherwise cause a panic.
Conclusion
The authorizeUpgradeextrinsic cannot be used to alert the Relaychain to the upcoming upgrade and enactAuthorizedUpgrade would also fail for the same reason.
The Kapex chain whilst producing blocks, is still in its genesis state, due to the existence of a transaction lock which was put in place to ensure that upgrades could be performed before "users were allowed in".
The issue implies a hard fork (new head and wasm blob) to solve.

To solve your problem, you can use the code_substitutes field in your chain spec. You will need to use the same commit that you used to create the current wasm file that is on chain. Then you only modify the code to remove the call to random_seed. The resulting wasm file you have to put into your chain spec as code substitute. The block number can be some recent one. Then you will need to go to the council and ask for force overwriting your validation code to the exact same file that you also have put into your chain spec. After this happened on the relay chain, you can send your upgrade call.

@bkchr Thanks.
We have staging on Rococo, so I presume we can do a pre-production test there as this is identical code to production?
Since the fix lasts only as long as the next spec_version (which would change by normal upgrade) I suppose that we should not increment but instead use the current on-chain spec_version when we create the new wasm code? Is that correct?

increment but instead use the current on-chain spec_version when we create the new wasm code

If you speak about the one that you will put into the chain spec, then yes! The spec version in the code_substitute should be the same as you currently use on chain.

Yes that is what I meant.

@bkchr one last question. We are running some nodes with docker, can we update them before using the new raw chainspec even though the force overwriting your validation code is not enacted yet? I suppose that makes no difference as the collators will only obey Polkadot? Or do we have to wait until the overwriting has been done?
That second option doesn't make any sense to me, but I thought I'd ask.

changes applied on this branch

@bkchr one last question. We are running some nodes with docker, can we update them before using the new raw chainspec even though the force overwriting your validation code is not enacted yet? I suppose that makes no difference as the collators will only obey Polkadot? Or do we have to wait until the overwriting has been done?
That second option doesn't make any sense to me, but I thought I'd ask.
...and is the format like this?
"codeSubstitutes": {
    "blocknumber": "0x52bc5376....."
}

blocknumber should be a number and not the word blocknumber. You can already use the new chain spec. As long as you will not send any transaction that runs the problematic code path it will work. Otherwise you will get an error on the relay chain while validating your Parachain block, because the relay chain still uses the old runtime.

@bkchr yes I knew that its was the actual block number that was needed and not the word! the update in the branch where changes were applied used recent block numbers from the 3 networks. mentioned.
Whilst i think of it, I put recent parachain blocknumbers - perhaps it should have been a recent relaychain blocknumber?
Again on this point obviously this blocknumber (whichever is correct) will become old and not "recent" by the time the council performs the force overwrite. Does this matter? Should we consider pitting a block numbeer in the near future that is likely to be surpassed before the force overwrite so that it would be a "recent" block number?
I have so many questions - apologies because it's not entirely

Blocknumber of the Parachain. Just use some recent block number from of your Parachain.

@bkchr could you just review what I did here please.

Created a branch from the commit used to create the genesis state applied to Polkadot for the current chain.

Commented out the offending line.

Recompiled code, and extracted the new chainspec-for-code-sub-wasm.json, and compared it to the original chainspec-for-wasm.json extract to check that it was indeed different.

made copies of the Lego (Rococo Local Dev Parachain) and Kapex (Production) readable chainspecs, and added the code from chainspec-for-code-sub-wasm.json into codeSubstitutes:

Lego Chainspec with Code Substitutes Readable

Kapex Chainspec with Code Substitutes Readable

Note: The chainspec update for Stagex (Public Rococo) will be applied once this branch is merged with Main.

Converted the readable specs to raw, renaming original chain spec to "original".

Open Questions:

How do we (safely) extract the validation code into a file to be used by the Relaychain?

As we will test this on our dev environment first, which extrinsic is used to overwrite the validation code? Do we also need a new head?

The steps seem right to me, everything follows the guidelines that have been shred.
In you want to double check, be sure that point 1 is using the right commit, I am positive that it is the case. But be sure as if that is not the case, then this won't work as expected :)
If anything, I would like to double click on the BlockNumber needed for Stagex chainspec, at the moment of writing your height is around #81128 ( this will be higher at the moment of reading ). Just make sure you set this right.

The upgrade was successful on Rococo local. We used the codeSubstitutes file here and the upgraded the network with the file here

The update was performed on Rococo Stagex this morning and was successful. The KAPEX collators are now running the Docker image used for Staging which has migrated to Production. The UI nodes will be migrated shortly.

Good to hear @chrisdcosta!

@bkchr we are still not clear on the next steps and haven't got a clear answer on element.
Is the account that uploaded the parachain code to Polkadot able to execute the paras.forceSetCurrentCode() on Polkadot or not?

Is the account that uploaded the parachain code to Polkadot able to execute the paras.forceSetCurrentCode() on Polkadot or not?

No, it is not. You need to go to the council to get a referendum for doing this as you need root origin for this.

We reproduced this in our development relaychain environment as well.
Data

ParaID 2007(Stagex) 2000(Lego)

Both parachain-code-substitution-wasm.wasm and the hash here runtime_fix_v110.compact.compressed.wasm are identical by hash.

This is the hash for runtime_fix_v110.compact.compressed.wasm
[
    0x1c0c15c2070eac5039736140b657254a09b5d6570860453d07a918c01f02c103
]

Relay chain state:
Rococo local:
Check the current Validation code by hash: paras.codeByHash() on Rococo Local Dev Network (only one parachain)
[
    [
        [
        0x1c0c15c2070eac5039736140b657254a09b5d6570860453d07a918c01f02c103
        ]
        0x52bc537646db8e0528b52ffd0058848704ee91c56211501050cc281dc01bbdb01e7ec2ad3947233a21f5ec02c58da344e3b2be55279765528ae5e0059f5ca2cd...207970a7801
    ]
]

This result agrees with the result on Rococo public.
[
    0x52bc537646db8e0528b52ffd0058848704ee91c56211501050cc281dc01bbdb01e7ec2ad3947233a21f5ec02c58da344e3b2be55279765528ae5e0059f5ca2cd...207970a7801
]

Both the local dev Relaychain network and Rococo public are in the same state.
The parachain Stagex has an issue because the storage parachainSystem.pendingValidationCode() contains the validation code here instead of being empty. This will trigger and 'Overlapping Upgrade' error when any subsequent upgrade occurs.
Steps to reproduce:
We have set up a fresh relaychain/parachain to reproduce the error.
It uses Rococo Local and our parachain collator docker image totemlive/totem-parachain-collator:test-codeSubstitute. This node uses our own sudo key.
Rococo Local Relaychain has been set with paras.forceSetCurrentCode() for this parachain, as confirmed above and the code substitute occurs at block 50 on the Lego Parachain.
Inspect the state of the parachainSystem.pendingValidationCode() at each step. The current state is:
[
    0x
]

Using the sudo user we execute this on the parachain: sudo.sudoCall(paras.authorizeUpgrade(<parachain-code-substitution-wasm.wasm>)) (pulling the wasm file directly from a local directory)
Check parachainSystem.pendingValidationCode() after transaction:
[
    0x
]

Using the sudo user we execute this on the parachain: sudo.sudoCall(paras.enactUpgrade(<parachain-code-substitution-wasm.wasm>))
Check parachainSystem.pendingValidationCode() after transaction:
[
    0x52bc537646db8e0528b52ffd0058848704ee91c56211501050cc281dc01bbdb01e7ec2ad3947233a21f5ec02c58da344e3b2be55279765528ae5e0059f5ca2cd...207970a7801
]

Now attempting a further upgrade on the parachain: sudo.sudoCall(paras.authorizeUpgrade(<v120_compact_compressed.wasm>)) (a new upgrade pulling the wasm file directly from a local directory)
[
    0x786233b426f99e8101c4881976d11f4328d0840f6f716cee41502b56762c9d86
]

This is successful - setting the new expected hash of the coming upgrade.
Check parachainSystem.authorizedUpgrade() after transaction:
[
    0x786233b426f99e8101c4881976d11f4328d0840f6f716cee41502b56762c9d86
]

However, when enacting the upgrade on the parachain: sudo.sudoCall(paras.enactUpgrade(<v120_compact_compressed.wasm>)) fails due to OverlappingUpgrades error in Cumulus.

Detail on the files

Parachain id 2007 (Stagex on Rococo Public, Kapex on Polkadot)

Parachain id 2000 (Lego on Totem Rococo local)

All the following files are in the current Main branch of totem-parachains
Build the runtime from scratch cargo build --release -p totem-parachain-node. This will include chainspecs so that you can start an individual chain using the arguments chain=stagex or chain=kapex .
Docker
Current production docker image is aligned with the main branch build, including the chainspecs containing the codeSubtitutes mentioned here.
Rococo / Stagex
To run the public Rococo version with Stagex you will need to specify the rococo v2 spec added manually into the chain argument because the polkadot version used here (v0.9.18) was before it was included. This issue is blocking from upgrading to the later version.
Specific file links (by commit)
Totem Rococo local chainspec
Common
Genesis WASM Lego, Stagex and Kapex
27 April LEGO
Kapex and Lego wasm and state build
Lego original chainspec
Genesis State Lego
27 April KAPEX
Kapex original chainspec
Genesis State Kapex
10 October STAGEX
Stagex wasm and state build
Stagex original raw chainspec
Genesis State Stagex
11 October New Validation Code
New Validation code wasm for Code Substitution
Stagex updated code subtitutes chainspec
Kapex updated code subtitutes chainspec - placeholder

There is something I think I could be misunderstanding.
You are executing both
sudo.sudoCall(paras.authorizeUpgrade(<parachain-code-substitution-wasm.wasm>))
sudo.sudoCall(paras.enactUpgrade(<parachain-code-substitution-wasm.wasm>)) btw this call doesn't require root origin
But at that point in time, the code substitution should have already happened, right ?
You have already set the wasm on your chainspec, then waited until the block number you chose, and then  executed paras.forceSetCurrentCode() on the relay with the same  wasm that was used on codeSubstitute.
So why trying to do a runtime upgrade with the same wasm ? Is it not the same one and I am just looking at this the wrong way ?

@al3mart no that was not the procedure that was followed.
I followed the procedure mentioned above in this comment, specifically:

The blocknumber was not set to some future block number - it was set to "some recent blocknumber" meaning a blocknumber that had already passed.

"after that you can send your upgrade call", which I understood to be the upgrade to this new validation code that was used in the paras.forceSetCurrentCode()
What you appear to be saying is that it is a much simpler case:

paras.forceSetCurrentCode() on the relay chain is all that is required on condition that

the parachain collators are already aware of the new validation code via the chainspec codeSubtitution

the parachain block number on which that changeover occurs is in past relative to the relaychain blocknumber at which paras.forceSetCurrentCode() is executed.

Then any normal upgrade can occur.

Put the new validation code with a recent Parachain block number into codeSubstitution.
Issue the paras.forceSetCurrentCode() on the relay chain with the same code as in 1.
Do a normal runtime upgrade.

Sorry if my comment was confusing. Please, try again as per the last comment instructions and let us know how that went, and if you are observing the same behavior than before.


getChangeLocalUrl function name to getChangeLocaleUrl

Hello! Thanks so much for your work to update Keycloakify, super excited!
Small nit but should getChangeLocalUrl here be getChangeLocaleUrl?

Hey @chloeshiauisme,
Thanks a lot!

Small nit but should getChangeLocalUrl here be getChangeLocaleUrl?

Damn it, you're wright! It's going to be a breaking change.
Thanks for reporting!

Thanks so much for the quick change!


desmume: avoid errors with with -fpermissive

Prior to this change, desmume would fail to build on nixos-unstable due to an error:
utils/libfat/directory.cpp:142:33: error: ISO C++ forbids comparison between pointer and integer [-fpermissive]
I guess this is due to the recent switch to GCC7.
Motivation for this change
Things done

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

[x] 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 nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

:crying_cat_face: I'm pretty sure that evaluation error is unrelated, it builds and runs fine from this branch locally.

@GrahamcOfBorg eval
Yeah, a PR mistakenly broke master :) Should be fixed up now. Sorry!

@GrahamcOfBorg build desmume

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘desmume-0.9.11’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/misc/emulators/desmume/default.nix:44 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11
shrinking /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11/bin/desmume-cli
shrinking /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11/bin/desmume
gzipping man pages under /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11/bin
patching script interpreter paths in /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11
checking for references to /tmp/nix-build-desmume-0.9.11.drv-0 in /nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11...
/nix/store/q9az497sqn6zpn5hsn5v8c1q5lcppp75-desmume-0.9.11

Success on aarch64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11
shrinking /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11/bin/desmume-cli
shrinking /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11/bin/desmume
gzipping man pages under /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11/share/man/
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11/bin
patching script interpreter paths in /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11
checking for references to /build in /nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11...
/nix/store/ibfq95ym5gs9mbc1q5hac2glvykxgnc9-desmume-0.9.11

@grahamc @Mic92 thanks!


Frederick - State change

Wishlist state change does not work with the rest of the code. The wishlist view works individually, but it is not prompted to open when the state change actually occurs with rest of the code.
Check the state react used in ResultsView

It works with the rest of the code now.


Update site not found

Update site not found when added to Eclipse : https://dl.bintray.com/anjlab/eclipse-tapestry5-plugin not working.

Please see https://github.com/anjlab/eclipse-tapestry5-plugin/issues/28
This project needs new home for binaries after Bintray sunrise.
I'll probably host it using gh-pages as per this advice but don't have time right now, sorry.

Please check version 2.13.5 in releases:
https://github.com/anjlab/eclipse-tapestry5-plugin/releases
Until we find a better way of publishing we can use binary attachments in releases


Engineering ?component name? design & Prod QA testing support template

User Story

As a [user role below]:
DDS developer

I need to:
fix the defects created by the Designers and Prod QA testers

so that I can:
be confident that the component developed is of high quality

Additional information

(Are there tools I should like to here?)
Design (#  )
Functional Specs (#  )

Acceptance criteria

[ ] Sev 1-3 QA defects are created, prioritized and scheduled
[ ] Tested React component within the Patterns Storybook

We are no longer using this template.  Closing.


Add BoundedTaskQueue<? extends Task> to Concurrency Library

Describe the solution you'd like
It would be convenient to have an internal Queue for the concurrency library library.
This would include:

TaskQueue<? extends Task> interface
BoundedTaskQueue<? extends Task>
AutomatedBoundedTaskQueue<? extends Task>
Issue #3 can become an implementing class of the BoundedTaskQueue class or TaskQueue interface.

closed with #104


Does PolySharp support multitargeting?

I recently saw this package and decided to try.
Config:
<PackageReference Include="PolySharp" Version="1.10.0">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>

Output:

If I change reference to
 <PackageReference Include="PolySharp" Version="1.10.0" Condition="'$(TargetFramework)' != 'net5' AND '$(TargetFramework)' != 'net6' AND '$(TargetFramework)' != 'net7'">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>

then there are no errors.
I would like PolySharp does not require Conditional attribute on TFMs where all necessary attributes are present.

PolySharp already supports this (eg. I'm personally using already in several multi-targeted projects, like you can see here: https://github.com/Sergio0694/ComputeSharp/pull/471). I'm not entirely sure what's going on here. Are you able to provide a minimal repro?

Maybe this has more to do with multiple projects rather than multiple targets.  Is the injected code internal?

"Is the injected code internal?"

@Shane32 it is by default, yes, unless you explicitly set the "PolySharpUsePublicAccessibilityForGeneratedTypes" property.

@Sergio0694 It may be due to the fact that the test project, where the build is failing, has references to two different projects both of which utilize InternalsVisibleTo back towards the test project...

Ah, yeah that makes sense. If the test project is, say, targeting .NET 6 (which has the attribute), but is referencing a project on, say, the .NET Standard 2.0 project, that project will have IsExternalinit generated for it, but then InternalsVisibleTo will make that give visibility to the test project as well, which now has two versions of that attirbute... I guess that could be possible 🤔

Attempting to reproduce now.......

Anyway if the issue is in a test project this definitely doesn't seem related to PolySharp per se. The library is correctly generating only the polyfills that are needed on each TFM, if then this specific repo has some weird configuration with test projects and InternalsVisibleTo settings caausing this issue in a separate project, this seems like a different issue 😅
Closing this for now, happy to reopen in case more info is provided that links this to an actual issue in PolySharp 🙂
I assume for that project, adding the condition on the PackageReference seems like an easy enough workaround at least.

FYI, below is a sample.  Removing PolySharp from the console app, or setting the TFM for ClassLibrary1 to netstandard2.0;net5.0, adding a condition to prevent PolySharp from being included on .NET 5+ "solves" the issue.
ClassLibrary1
<Project Sdk="Microsoft.NET.Sdk">

	<PropertyGroup>
		<TargetFramework>netstandard2.0</TargetFramework>
		<ImplicitUsings>enable</ImplicitUsings>
		<Nullable>enable</Nullable>
		<LangVersion>11</LangVersion>
	</PropertyGroup>

	<ItemGroup>
		<InternalsVisibleTo Include="ConsoleApp1" />
	</ItemGroup>

	<ItemGroup>
		<PackageReference Include="PolySharp" Version="1.10.0">
			<PrivateAssets>all</PrivateAssets>
			<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
		</PackageReference>
	</ItemGroup>

</Project>

namespace ClassLibrary1
{
    public class Class1
    {
    }
}

ConsoleApp1
<Project Sdk="Microsoft.NET.Sdk">

	<PropertyGroup>
		<OutputType>Exe</OutputType>
		<TargetFramework>net7.0</TargetFramework>
		<ImplicitUsings>enable</ImplicitUsings>
		<Nullable>enable</Nullable>
	</PropertyGroup>

	<ItemGroup>
		<ProjectReference Include="..\ClassLibrary1\ClassLibrary1.csproj" />
	</ItemGroup>

	<ItemGroup>
		<PackageReference Include="PolySharp" Version="1.10.0">
			<PrivateAssets>all</PrivateAssets>
			<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
		</PackageReference>
	</ItemGroup>

</Project>

// See https://aka.ms/new-console-template for more information
Console.WriteLine("Hello, World!");

I've got the same issue with IsExternalInit, also in a test project that references another project in the same repository. It's likely to prevent the use of PolySharp as a replacement for IsExternalInit and Nullable in Remora.Sdk for the time being - see https://github.com/Remora/Remora.Results/pull/10 for the discussion.


Change color of object

Hi, i'm using your great library with a FAB attached, is possible to change the color of it during the animation? Maybe using some methods like : http://stackoverflow.com/a/33404475

Yes you can now do it with animator set, new version of SupportAnimator extends native Animator, so we can now combine animators and run them sequently or parallel using AnimatorSet class

Yes you can now do it with animator set, new version of SupportAnimator extends native Animator, so we can now combine animators and run them sequently or parallel using AnimatorSet class


multi-select gets values of options and show them

I want this multi-select to get an array of values and show the options but it doesn't work even for showing one option.
Could you please help me with this?
thanks in advanced

yeah this one is working, but my problem is this
for example, I have this :

one
two
three

then with this part, I want the third option to be selected :
jQuery(document).ready(function ($) {$('.slc').find('option[value=3]').attr('selected', 'selected');});
with this -> deselect: false, the first option is selected and it doesn't change.
sorry I am a beginner :D


Do not wait until config watcher is ready in order to launch the Atom window

Based on some profiling done locally, this await takes ~300-500ms on Windows machines (I couldn't find the root cause of it but may be related to https://github.com/atom/atom/pull/19242).

Do you think a comment should be added saying why it's not awaited? Because I could potentially see someone changing it back in the future if they weren't aware.

I'm concerned about this introducing a race condition where we don't catch config file changes that occur just after the window starts up. Does it make sense to skip the await only on Windows so that we only introduce the race condition when it is the lesser of two evils? The downside of that is that we're introducing inconsistent behavior across platforms.

I can do that

How can we remember to revisit this change once we upgrade Electron and see if it's still an issue?

What do you think about what I suggested in https://github.com/atom/atom/pull/19242#issuecomment-488337557 ?


Merge IstioControlPlane into MeshConfig

See https://docs.google.com/document/d/19IKo6DDv0x6DKtollcbFivjqLkQGwts3dFCzIFm2swM/

https://github.com/istio/api/pull/1101

https://github.com/istio/api/pull/1177 is the latest attempt.

@ostromart are there more changes here, or this current rev what we are sticking to for now?


question: incremental backups (again)

Hi,
as there are multiple ways to backup lxd containers from one server to another (https://lxd.readthedocs.io/en/latest/backup/) this doesn`t quite fit for my use case.
I know, it would be much easier to have on both sides the same storage driver (btrfs/zfs) and use the filesystems send/receive capabilities but I cant use them in my current setup.
I have a production LXD server:
driver: lxc
  driver_version: 3.1.0
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.4.0-141-generic
  server: lxd
  server_pid: 32108
  server_version: "3.11"
  storage: btrfs
  storage_version: "4.4"
  server_clustered: false
  server_name: data-prod01
  project: default

and a backup LXD server also as a container running inside Proxmox:
driver: lxc
  driver_version: 3.0.3
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.15.18-12-pve
  server: lxd
  server_pid: 387
  server_version: 3.0.3
  storage: dir
  storage_version: "1"
  server_clustered: false
  server_name: data-bckp01
  project: ""

The containers inside Proxmox are running on a zfs pool
lxc copy data-prod01:cont11 cont11 is woking fine but AFAIK this approach doesn`t do incremental transfers.(?!)
[sidenote]
The copy method changes also the file permissions:
source container
drwxr-xr-x   1 root   root    1068 May 23  2016 bin
drwxr-xr-x   1 root   root       0 Jan 28  2014 boot
drwxr-xr-x   7 root   root     460 Feb 21 04:13 dev
drwxr-xr-x   1 root   root    2168 Mar 25 13:45 etc
drwxr-xr-x   1 root   root       0 Jan 28  2014 home
drwxr-xr-x   1 root   root      90 May 23  2016 lib
drwxr-xr-x   1 root   root      40 Aug 26  2016 lib64
drwxr-xr-x   1 root   root       0 Apr  2  2014 media

after lxc copy remote:cont11 cont11
drwx------   2 root   root    104 May 23  2016 bin
drwx------   2 root   root      2 Jan 28  2014 boot
drwxr-xr-x   6 root   root    440 Mar 25 14:02 dev
drwx------  63 root   root    134 Mar 25 14:02 etc
drwx------   2 root   root      2 Jan 28  2014 home
drwx------   8 root   root      9 May 23  2016 lib
drwx------   2 root   root      3 Aug 26  2016 lib64
drwx------   2 root   root      2 Apr  2  2014 media

why is this so?
[/sidenote]
I´ve also tried to rsync (rsnapshot) the snapshot from the prod01 server but for some reason rsync fails to transfer one of my container:
packet_write_wait: Connection to xxx.xxx.xxx.118 port 2006: Broken pipe
rsync: connection unexpectedly closed (22237737 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(235) [receiver=3.1.2]
rsync: connection unexpectedly closed (3184714 bytes received so far) [generator]
rsync error: unexplained error (code 255) at io.c(235) [generator=3.1.2]

This particular container is 30GB big.
Anyway, by rsync-ing the snapshot would mean to alter the backup.yaml file as the source datastore is btrfs, creating a symlink in /var/lib/lxd/containers and then do a lxd import <container>
So my question is, what would be the right approach do incremental backups of containers from one LXD instance to another?
Thanks

The right approach would be to use the --refresh options we introduce a few releases ago which lets you transfer only the data that has changed and re-sync the snapshot list with the source.

Been trying to reproduce the permission issue, so far no luck using an Alpine container, a LXD 3.11 source server and LXD 3.0.3 target server, source is on btrfs, target on dir, same as described above.

And tried with both the 3.0.3 snap and the 3.0.3 deb on the target, same behavior on both.
I also always remember us passing -a to rsync so I don't see how the permissions would get stripped during an rsync migration...

Do you have a reliable reproducer for the permission issue?

OK, since the --refresh option is available only on the newer releases, I´ve removed the deb 3.0.3 version and installed snap inside the container.
apt install squashfuse fuse snapd
snap install lxd

driver: lxc
  driver_version: 3.1.0
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.15.18-12-pve
  server: lxd
  server_pid: 2270
  server_version: "3.11"
  storage: dir
  storage_version: "1"
  server_clustered: false
  server_name: data-bckp01
  project: default

I`ve created a snapshot on the source LXD server of container cont11 and this are the permissions:
ls -la /var/snap/lxd/common/lxd/storage-pools/default/containers-snapshots/cont11/rsnapshot/rootfs/
total 0
drwxr-xr-x 1 1000000 1000000  164 Feb  3  2018 .
drwx------ 1 1000000 1000000   34 May 15  2018 ..
drwx------ 1 1000000 1000000  108 Jun  6  2016 .keychain
drwxr-xr-x 1 1000000 1000000 1068 May 23  2016 bin
drwxr-xr-x 1 1000000 1000000    0 Jan 28  2014 boot
drwxr-xr-x 1 1000000 1000000  464 Feb  3  2018 dev
drwxr-xr-x 1 1000000 1000000 2168 Mar 25 13:07 etc
drwxr-xr-x 1 1000000 1000000    0 Jan 28  2014 home
drwxr-xr-x 1 1000000 1000000   90 May 23  2016 lib
drwxr-xr-x 1 1000000 1000000   40 Aug 26  2016 lib64
drwxr-xr-x 1 1000000 1000000    0 Apr  2  2014 media
drwxr-xr-x 1 1000000 1000000    0 Jan 28  2014 mnt
drwxr-xr-x 1 1000000 1000000    0 Apr  2  2014 opt
drwxr-xr-x 1 1000000 1000000    0 Jan 28  2014 proc
drwx--S--- 1 1000000 1000000  378 Oct 20 17:06 root
drwxr-xr-x 1 1000000 1000000  110 Jun 20  2016 run
drwxr-xr-x 1 1000000 1000000 1430 Aug 26  2016 sbin
drwxr-xr-x 1 1000000 1000000   14 Apr  2  2014 selinux
drwxr-xr-x 1 1000000 1000000    0 Apr  2  2014 srv
drwxr-xr-x 1 1000000 1000000    0 Jul 14  2013 sys
drwxrwxrwt 1 1000000 1000000   48 Mar 25 12:39 tmp
drwxr-xr-x 1 1000000 1000000   70 Apr  2  2014 usr
drwxr-xr-x 1 1000000 1000000   96 Apr  3  2014 var

Now on the backup LXD:
root@data-bckp01:~# lxc copy remote:cont11/rsnapshot cont11
lxc list
+--------+---------+----------------------+-----------------------------------------------+------------+-----------+
|  NAME  |  STATE  |         IPV4         |                     IPV6                      |    TYPE    | SNAPSHOTS |
+--------+---------+----------------------+-----------------------------------------------+------------+-----------+
| cont11 | RUNNING | <IP_ADDRESS> (eth0) | fd42:32aa:c1e5:a34d:216:3eff:fec3:ff79 (eth0) | PERSISTENT |           |
+--------+---------+----------------------+-----------------------------------------------+------------+-----------+

ls -la /var/snap/lxd/common/lxd/storage-pools/default/containers/cont11/rootfs/
total 103
drwx------ 23 root root  23 Mar 25 21:20 .
drwx------  3 root root   4 May 14  2018 ..
drwx------  2 root root   5 Jun  6  2016 .keychain
drwx------  2 root root 104 May 23  2016 bin
drwx------  2 root root   2 Jan 28  2014 boot
drwx------  3 root root  13 Feb  3  2018 dev
drwx------ 63 root root 134 Mar 25 21:20 etc
drwx------  2 root root   2 Jan 28  2014 home
drwx------  8 root root   9 May 23  2016 lib
drwx------  2 root root   3 Aug 26  2016 lib64
drwx------  2 root root   2 Apr  2  2014 media
drwx------  2 root root   2 Jan 28  2014 mnt
drwx------  2 root root   2 Apr  2  2014 opt
drwx------  2 root root   2 Jan 28  2014 proc
drwx------ 12 root root  23 Oct 20 15:06 root
drwx------  8 root root  11 Jun 20  2016 run
drwx------  2 root root  92 Aug 26  2016 sbin
drwx------  2 root root   3 Apr  2  2014 selinux
drwx------  2 root root   2 Apr  2  2014 srv
drwx------  2 root root   2 Jul 14  2013 sys
drwx------  3 root root   4 Mar 25 11:39 tmp
drwx------ 10 root root  10 Apr  2  2014 usr
drwx------ 12 root root  14 Apr  2  2014 var

Regarding the --refresh option: how is this supposed to be used?
lxc copy --refresh remote:cont11 cont11
Error: Failed container creation: Cannot refresh a running container
root@data-bckp01:~# lxc stop cont11
root@data-bckp01:~# lxc copy --refresh remote:cont11 cont11
Error: Failed container creation:
 - https://<IP_ADDRESS>:4443: Error transferring container data: Unable to connect to: <IP_ADDRESS>:4443
 - https://example.com:4443: Error transferring container data: exit status 23
 - https://176.9.xxx.xxx:4443: Error transferring container data: websocket: bad handshake

<IP_ADDRESS> is the bridge IP of the source LXD server.
 This may take a minute...

Ah and refresh works fine here too:
root@vm05:~# lxc copy vm04:a1 a1 --mode=relay --refresh
root@vm05:~#

Ok, so yes, your problem is about running this inside a container. Rsync will attempt to do things like create device nodes which isn't going to work inside an unprivileged container, that explains the error 23, at least that's what I'm seeing here when looking at the source server logs:
t=2019-03-25T22:47:23+0000 lvl=eror msg="Rsync send failed: /var/snap/lxd/common/lxd/snapshots/a1/snap0/: exit status 23: rsync: mknod \"/var/snap/lxd/common/lxd/containers/a1/rootfs/dev/null\" failed: Operation not permitted (1)\nrsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.1]\n"

After making the backup container privileged, the copy worked properly here, as did a refresh copy:
root@backup:~# lxc copy vm04:a1/snap0 a1 --mode=relay
root@backup:~# lxc copy vm04:a1 a1 --mode=relay --refresh
root@backup:~#

So I think the answer to this issue is likely that if you want to run a backup LXD server inside a container, you should have it run privileged so that it can backup all file types from any container you may have around and avoid running into odd rsync issues when a particular file operation isn't allowed by the kernel. (rsync annoyingly only gives us pretty cryptic exit codes)

Thank you for being thorough in this matter. Ive started the container in privileged mode but snap lxd doesnt seem to like that
root@nas-10-backup:~#snap install lxd
error: cannot perform the following tasks:
- Setup snap "core" (6531) security profiles (cannot setup udev for snap "core": cannot reload udev rules: exit status 2
udev output:
)
- Setup snap "core" (6531) security profiles (cannot reload udev rules: exit status 2
udev output:
)

Run the install again

For whatever reason snaps need to tries inside privileged containers

root@nas-10-backup:~# snap install lxd
error: cannot perform the following tasks:
- Setup snap "core" (6531) security profiles (cannot setup udev for snap "core": cannot reload udev rules: exit status 2
udev output:
)
- Setup snap "core" (6531) security profiles (cannot reload udev rules: exit status 2
udev output:
)
root@nas-10-backup:~# snap install lxd
error: cannot perform the following tasks:
- Setup snap "core" (6531) security profiles (cannot setup apparmor for snap "core": cannot create host snap-confine apparmor configuration: cannot reload snap-confine apparmor profile: cannot load apparmor profiles: exit status 243
apparmor_parser output:
apparmor_parser: Unable to replace "mount-namespace-capture-helper".  Permission denied; attempted to load a profile while confined?
apparmor_parser: Unable to replace "/snap/core/6531/usr/lib/snapd/snap-confine".  Permission denied; attempted to load a profile while confined?
)
- Setup snap "core" (6531) security profiles (cannot create host snap-confine apparmor configuration: cannot reload snap-confine apparmor profile: cannot load apparmor profiles: exit status 243
apparmor_parser output:
apparmor_parser: Unable to replace "mount-namespace-capture-helper".  Permission denied; attempted to load a profile while confined?
apparmor_parser: Unable to replace "/snap/core/6531/usr/lib/snapd/snap-confine".  Permission denied; attempted to load a profile while confined?
)

tail -f /var/log/syslog
Mar 27 12:07:52 nas-10-backup snapd[153]: api.go:1077: Installing snap "lxd" revision unset
Mar 27 12:07:53 nas-10-backup systemd[1]: Reloading.

Mar 27 12:07:53 nas-10-backup systemd[1]: Mounted Mount unit for core, revision 6531.
Mar 27 12:07:54 nas-10-backup kernel: [23702.499799] audit: type=1400 audit(1553688474.237:117): apparmor="STATUS" operation="profile_replace" info="not policy admin" error=-13 label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" pid=12682 comm="apparmor_parser"
Mar 27 12:07:54 nas-10-backup kernel: [23702.499869] audit: type=1400 audit(1553688474.237:118): apparmor="STATUS" operation="profile_replace" info="not policy admin" error=-13 label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" pid=12682 comm="apparmor_parser"
Mar 27 12:07:54 nas-10-backup systemd[1]: Reloading.

Mar 27 12:05:38 nas-10-backup systemd[75]: Failed to attach 75 to compat systemd cgroup /system.slice/apparmor.service: No such file or directory
Mar 27 12:05:38 nas-10-backup apparmor[75]: /sbin/apparmor_parser: Unable to replace "mount-namespace-capture-helper".  Permission denied; attempted to load a profile while confined?
Mar 27 12:05:38 nas-10-backup apparmor[75]: /sbin/apparmor_parser: Unable to replace "/usr/lib/snapd/snap-confine".  Permission denied; attempted to load a profile while confined?
Mar 27 12:05:38 nas-10-backup apparmor[75]: /sbin/apparmor_parser: Unable to replace "mount-namespace-capture-helper".  Permission denied; attempted to load a profile while confined?
Mar 27 12:05:38 nas-10-backup apparmor[75]: /sbin/apparmor_parser: Unable to replace "/usr/lib/snapd/snap-confine".  Permission denied; attempted to load a profile while confined?
Mar 27 12:05:38 nas-10-backup apparmor[75]:    ...fail!
Mar 27 12:05:38 nas-10-backup systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a
Mar 27 12:05:38 nas-10-backup systemd[1]: apparmor.service: Failed with result 'exit-code'.
Mar 27 12:05:38 nas-10-backup systemd[1]: Failed to start AppArmor initialization.

However, lxd runs fine from the deb repository
driver: lxc
  driver_version: 3.0.3
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.15.18-12-pve
  server: lxd
  server_pid: 1794
  server_version: 3.0.3
  storage: dir
  storage_version: "1"
  server_clustered: false
  server_name: nas-10-backup
  project: ""

lxc list
+--------+---------+---------------------+-----------------------------------------------+------------+-----------+
|  NAME  |  STATE  |        IPV4         |                     IPV6                      |    TYPE    | SNAPSHOTS |
+--------+---------+---------------------+-----------------------------------------------+------------+-----------+
| bionic | RUNNING | <IP_ADDRESS> (eth0) | fd42:ac20:517b:a3e9:216:3eff:fe00:9331 (eth0) | PERSISTENT | 0         |
+--------+---------+---------------------+-----------------------------------------------+------------+-----------+

OK, adding
lxc.cap.drop =
lxc.cap.drop = mac_override sys_time sys_module sys_rawio

to the proxmox config  /etc/pve/lxc/$vmid.conf did the trick
 lxc list
+----------+---------+----------------------+-----------------------------------------------+------------+-----------+
|   NAME   |  STATE  |         IPV4         |                     IPV6                      |    TYPE    | SNAPSHOTS |
+----------+---------+----------------------+-----------------------------------------------+------------+-----------+
| lxd-snap | RUNNING | <IP_ADDRESS> (eth0) | fd42:7d71:c7f3:5c88:216:3eff:feab:22c8 (eth0) | PERSISTENT |           |
+----------+---------+----------------------+-----------------------------------------------+------------+-----------+

driver: lxc
  driver_version: 3.1.0
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.15.18-12-pve
  server: lxd
  server_pid: 1401
  server_version: "3.11"
  storage: dir
  storage_version: "1"
  server_clustered: false
  server_name: nas-10-backup
  project: default

What exactly happend? Thanks

Ah, it was most likely appamor misbehaving inside the proxmox managed container.
I assumed you were running the container on LXD which does have additional support for apparmor nesting.
Okay, so looks like we tracked this one down to:

LXD version without --refresh (now on 3.11 so should be fine)
Environment which didn't allow for enough uid/gid or mknod capability (now fixed with a privileged container)

Yes, thank you!


Editor themes

We want to add a dropdown that lets you select the theme of the Ace editor like in the old Dawn. The theme preference should be persistent.

can i be assigned this task?

im justin yang on slack


acp_basics Branch (Old 207)

In gitlab by @A-Lawrence on Aug 31, 2015, 01:09
Get rid of acp_basics, just make sure there's no major things left in there we require.

In gitlab by @A-Lawrence on Aug 31, 2015, 01:15
Removed.
ALawrence66 - 2015-01-18T19:17:49.118021+00:00


Add UTF-8 locale to Dockerfile

This fixes an issue with pip crashing on several package installs due to
non-ASCII charsets.

Automated message from Dropbox CLA bot
@apuranik1, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@apuranik1, thanks for signing the CLA!

Merged, thanks @apuranik1!


[hotfix] Prevent CA from downscaling node running etcd pod

Signed-off-by: Shreyas Rao<EMAIL_ADDRESS>What this PR does / why we need it:
This hotfix PR adds annotation "cluster-autoscaler.kubernetes.io/safe-to-evict": "false" to etcd pod (instead of etcd sts) so that cluster-autoscaler does not downscale any node running etcd pod.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This will cause the etcd pods to restart, but only in maintenance window.
Release note:

Prevent cluster-autoscaler from downscaling any node running etcd pod.

Is this change merged in the master branch ?

Actually, in the master we are using etcd druid https://github.com/gardener/gardener/pull/1762 now, so it cannot be implemented there, right?

@vpnachev correct. This PR makes sense only for release-v1.1 branch, because druid isn't part of this

Please add a release note user noteworthy that the etcd will be restarted in the next maintenance window.

Does the etcd-druid adds this annotation? Are we sure that etcd-druid won't regress this? Do we want both etcd-main and etcd-events to be critical or only etcd-main as I see this PR will make them both critical?

Does the etcd-druid adds this annotation? Are we sure that etcd-druid won't regress this?

Yes, druid add this annotation (check here).

Do we want both etcd-main and etcd-events to be critical or only etcd-main as I see this PR will make them both critical?

i prefer both.

@amshuman-kr Does it makes sense to add the node labels in seed bootstrap and make use of node affinity in etcd statefulset , so that one can separate out the etcd pods to isolated nodes. And such workerpool can be configured separately to autoscaler. This prevents the auto-scalling impact, which was generally introduced from other control plane components based on shoot workload. We discussed this vaguely sometime back. This has another benefit of configuring the etcd related workpool more IO reach rather than compute/memory reach. WDYS?
I expect this to be small change and won't extend hotfix timeline too much. And avoid additional change to etcd in future.
cc @hardikdr

Do we want both etcd-main and etcd-events to be critical or only etcd-main as I see this PR will make them both critical?

Good catch. I don't see why etcd-events should block CA.

Does it makes sense to add the node labels in seed bootstrap and make use of node affinity in etcd statefulset , so that one can separate out the etcd pods to isolated nodes. And such workerpool can be configured separately to autoscaler. This prevents the auto-scalling impact, which was generally introduced from other control plane components based on shoot workload. We discussed this vaguely sometime back. This has another benefit of configuring the etcd related workpool more IO reach rather than compute/memory reach. WDYS?

I have been thinking about heterogenous worker pools for seeds for a long time. To me, it makes sense to schedule different kinds of workloads to different dedicated worker pools in the seeds. It makes sense to schedule etcd to dedicated pool so that rest of the pools are not free to scale down independently. In future, we could think about having a pool of preemptive/spot instances for normal controller pods.

@amshuman-kr I assume this as affirmative to have affinity change in this PR.
@shreyas-s-rao  Will you please do the change?  Basically add ndoeaffinity to etcd sts as
  affinity:
    nodeAffinity:
      preferredDuringSchedulingIgnoredDuringExecution: //SOFT affinity
      - weight: 1
        preference:
          matchExpressions:
          - key: node-restriction.kubernetes.io/allowed-component
            operator: In
            values:
            - etcd-main
           - etcd-events

@georgekuruvillak : It makes sense for druid to also expose the affinity parameter on etcd CRD.
Regarding node labels : Now thinking over it in deep, hardcoding node labels in seed bootstrap is doesn't sound good. Cause gardener don't expect any knowledge about the seed cluster worker nodes configuration. Some labeling could be applied for shootSeed, but that can be changed later in code without change to etcd.

For node labelling, i have considered the  node-isolation-restriction feature and allow future common labelling pattern regarding affinity for other components like kube-apiserver as well. Please feel free to suggest any other, if above mentioned lable key-values doesn't work.

@swapnilgm @amshuman-kr can we move the discussion to another ticket? It's out of scope of this PR.

Are you guys OK with getting this PR in now?

We should do the absolute minimum to stabilize this release. Any tweaks should be done in further releases to not put the v1.1.x at stake.

I'm fine with keeping discussion away from this PR and merging this PR. I was considering about adding  node affinity in same release. But if, majority feel it's risky then, let's keep it out this release.

I'm fine with keeping discussion away from this PR and merging this PR. I was considering about adding node affinity in same release. But if, majority feel it's risky then, let's keep it out this release.

I do feel it is risky to do it in one shot. Also, we will need to introduce multiple worker pools in the seeds with some taints and tolerations rather than node affinity for this to work well.


Update mb-5g-data-class-support.md

Clarify the wording for the purpose these MBIM extensions with the 1903 release.

Hi @jefsong, I've tweaked the grammar a bit to polish the wording. Can you re-check and see if this is still the correct wording for your messaging?

Thank you Michael. I agree with your edits.
Appreciate the fast support.

From: Duncan MacMichael<EMAIL_ADDRESS>Sent: Friday, July 12, 2019 3:46:17 PM
To: MicrosoftDocs/windows-driver-docs<EMAIL_ADDRESS>Cc: Jeffrey Song<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-driver-docs] Update mb-5g-data-class-support.md (#1663)
Hi @jefsonghttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjefsong&data=02|01|Jeffrey.Song%40microsoft.com|4672d2dfe34245e4783408d7071ac0a4|72f988bf86f141af91ab2d7cd011db47|1|0|636985683798116759&sdata=mwNIKEHT4vZdycPJORpS8lQkGGnyKKdeENFkd%2FmTJiM%3D&reserved=0, I've tweaked the grammar a bit to polish the wording. Can you re-check and see if this is still the correct wording for your messaging?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-driver-docs%2Fpull%2F1663%3Femail_source%3Dnotifications%26email_token%3DAJ5MCQ5DEXFS5UKVRGFB2C3P7ECTTA5CNFSM4ICOJY3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3BOSQ%23issuecomment-511055690&data=02|01|Jeffrey.Song%40microsoft.com|4672d2dfe34245e4783408d7071ac0a4|72f988bf86f141af91ab2d7cd011db47|1|0|636985683798126757&sdata=I3KpLacQavwGUYS7H6UgEzUdfW7F7RD2XYLINy34vVM%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJ5MCQY4Y4CAU75KVOW7JMDP7ECTTANCNFSM4ICOJY3A&data=02|01|Jeffrey.Song%40microsoft.com|4672d2dfe34245e4783408d7071ac0a4|72f988bf86f141af91ab2d7cd011db47|1|0|636985683798126757&sdata=TYGxlPRyZIizaVV2Yh%2FnERt%2F2YSV%2Flr033ZvxB%2B2XBQ%3D&reserved=0.

Great; I'll go ahead and merge this then. No problem!


Add trace_tracy feature for Tracy profiling

Objective
Tracy is:

A real time, nanosecond resolution, remote telemetry, hybrid frame and sampling profiler for games and other applications.

With the trace_tracy feature enabled, you run your bevy app and either a headless server (capture) or a live, interactive profiler UI (Tracy), and connect that to your bevy application to then stream the metric data and events, and save it or inspect it live/offline.
Previously when I implemented the spans across systems and stages and I was trying out different profiling tools, Tracy was too unstable on macOS to use. But now, quite some months later, it is working stably with Tracy 0.7.8. You can see timelines, aggregate statistics of mean system/stage execution times, and much more. It's very useful!

Solution

Use the tracing-tracy crate which supports our tracing spans
Expose via the non-default feature trace_tracy for consistency with other trace* features

also some sort of doc on tracing could be useful but can be done in another pr

Could you also document the new feature in https://github.com/bevyengine/bevy/blob/main/docs/cargo_features.md

Done.

also some sort of doc on tracing could be useful but can be done in another pr

Once I have used it a bit more I will write something as a quick start guide, but Tracy has a pretty comprehensive pdf documentation that ships with each release, so I would probably defer to that.

If people are interested to see how I've been using this, you can check out the Visibility culling thread in #rendering-dev on Discord. Basically looking at mean system execution times to understand how much of an improvement frustum culling was producing, and in which systems. It's great for getting more of that sort of engineering feel for how the engine 'sounds'. :) It lead to me learning some stuff about how vsync seems to misbehave on macOS too.

Maybe consider updating https://github.com/bevyengine/bevy/blob/main/docs/profiling.md

This could use an overhaul in general. Imo we shouldn't recommend thread_profiler anymore when we have tracing and we should add a section for the various tracing backends.

Imo we should do that separately.

bors r+


DSEGOG-70 adding preloader animation

Description
Giving the preloader a bit of style!
Testing instructions
Reloading the webpage should trigger a spinning preloader while loading

[ ] Review code
[ ] Check Actions build
[ ] Review changes to test coverage

Agile board tracking
Closes DSEGOG-70

Hope @louise-davies doesn't mind but as this is such a small PR I'm just going to go ahead and merge it to close the issue off nicely before close of sprint


Update post gen hook to change access permissions on all systems

Previously, post gen hook had Windows specific instruction to change access permissions for Bootstrap.sh. These access permissions changes are required on Ubuntu and macOS as well
Testing
Verified that generated GitHub Actions workflows run to completion on all systems (seen here)

Updates
Latest commit sets execution permissions in post-gen script so permissions are set locally before being sent to git index.
Testing

Ensured all GitHub Actions workflows run to completion on all systems (here)
Ensured ./Bootstrap.sh can be run locally without needing to change execution permissions


Development Failures:

classes/DropboxAccountController.cls(350,7):Invalid type: ffhttp_Client.Credentials
classes/DropboxTestHarnessController.cls(840,5):Invalid type: ffhttp_Client.Credentials
permissionsets/Dropbox_Sample_App_Permissions.permissionset(Dropbox_Sample_App_Permissions):In field: apexClass - no ApexClass named DropboxAccountController found
pages/DropboxTestHarness.page(DropboxTestHarness):Apex class 'DropboxTestHarnessController' does not exist
pages/DropboxMoveAccountAttachments.page(DropboxMoveAccountAttachments):Apex class 'DropboxAccountController' does not exist

Having the same issue . Did you find a resolution?


Add support for RFC 3161

Add module and test for RFC 3161.  It seems to want to include the files for RFC 8520 again.  I think those were already sent in an earlier PR.  If not, please accept them too.

Codecov Report

Merging #32 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #32   +/-   ##
=======================================
  Coverage   98.96%   98.96%
=======================================
  Files          36       36
  Lines        3488     3488
=======================================
  Hits         3452     3452
  Misses         36       36

Impacted Files
Coverage Δ

pyasn1_modules/rfc8520.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thank you!


Question on permissions

My scanner got a few additional checks last week, so on today's update of your app it reported:
! repo/me.sankethbk.dairyapp_2018.apk declares risky permission(s): android.permission.RECORD_AUDIO android.permission.READ_EXTERNAL_STORAGE

May I ask what those permissions are needed for? I could not find a matching feature in the app description (but might simply have missed it). Thanks in advance!

Hi, I am currently using these permissions
<uses-permission android:name="android.permission.USE_FINGERPRINT" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.SCHEDULE_EXACT_ALARM" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />

RECORD_AUDIO was added recently, I added a feature for attaching audio files in notes which can be picked from file manager or audio can be recorded from within the app. I am assuming file_picker library is using READ_EXTERNAL_STORAGE permission, which is used to add images, audio and video to the note

Thanks! Yes, an integrated voice recorder totally explains this. And as I meanwhile found out, READ_EXTERNAL_STORAGE is needed to access other app's media files until Android 9, so I've added that to the allow-list of your app as well.
All clear then, thanks again!


Support triples of form x86_64-apple-macosx10.7.0

This is the default triple rustc passes to LLVM since https://github.com/rust-lang/rust/pull/60788.

Fixed in https://github.com/CraneStation/target-lexicon/pull/14


Searching for a user doesnt work in Google Chat

Describe the bug

Searching for a user doesn't work in Google chat
Search for a user who is not in the cached list of Google Chat.
To Reproduce

Steps to reproduce the behavior:

Go to Google Chat and search for a user using the search bar on the top left panel
Type in a few words and observe that no results are returned

Expected behavior
Matching users should be listed in the dropdown.
Screenshots
Look for the autocomplete requests failing in the console

Here is a response of the autocomplete request:
{   "error": {     "code": 401,     "message": "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",     "status": "UNAUTHENTICATED"   } }
Desktop:

OS: [Windows 10]
Ferdi Version [e.g. 5.4.3]
Server Used: [e.g. https://api.getferdi.com]

@mahadevans87 is it still happening in 5.5.0-gm?

@mahadevans87 is it still happening in 5.5.0-gm?

I can confirm this works in the latest 5.5.0-gm as well as building from the develop branch

Have made some progress on this. Hopefully the fix should resolve all of the Google related issues

@kytwb : Created a PR each in both ferdi as well as the recipe repo. Please review the same.


images in root directory

The image https://github.com/geoscixyz/em/blob/master/zteminv2d3d_section.png is currently sitting in the root directory. Could it please be moved to the relevant case history directory or removed if it is a duplicate?
cc @sgkang

@sgkang : would you mind taking a look at this when you get a chance? It should be a small update. Thanks!!

closed with #483


Add object type support

Requires #21

MERGED
https://github.com/frictionlessdata/jsontableschema-bigquery-py/issues/40


Hello, can you provide client and run tutorial

I like your project very much. I have v1122 client, but I can't run with your server source code. We look forward to your tutorial

Hey, this is still a project under development and not yet ready for the production, please follow up more on the C# project, because that is what is being developed right now, and then it will be ported to this language with better code and structuring.

Currently the server is working with the CF Phoenix client


Manual installation instructions?

Great job! Any chance you can provide manual installation instructions?

@titizali nope... This project is discontinued and we haven't scheduled any further enhancement.
Sorry...


(,,18+ MMS,,) Desi MMS Leaked Video From Yor Phone Indian Girl Leaked MMS TRENDING

(,,18+ MMS,,) Desi MMS Leaked Video From Yor Phone Indian Girl Leaked MMS TRENDING
Watch 🟢 ➤ 🌐 Click Here To Watch Now
Watch 🟢 ➤ 🌐 Click Here To link Full Viral Video
Watch 🟢 ➤ 🌐 Click Here To link Full Viral Video
Bhojpuri Hot Viral Videos Leaked app is a collection of Viral videos of Girl and Leaked Videos. This app contains best collection of Hot Videos. Many Private videos of girl dancing
on Bhojpuri Songs which can be enjoyed with friends and family members. We will be adding more Hot videos every week. Keep yourself updated with this app and please rate this app along with few comments and suggestions. You may also write the type of videos you wish to watch in this app and we will be adding them regularly. This Bhojpuri Songs and Bhojpuri Dance is commonly of girls and they are really hot which you cannot resist to watch. Do enjoy this app and share it on social media.
As the situation unfolds, the truth remains shrouded in mystery, leaving the public to ponder the authenticity of the rumors. In a world where fame and infamy are two sides of the same coin, the saga of Ishowspeedis a testament to the power of social media to shape narratives and challenge the boundaries of privacy and consent.
The viral video of Leaked viral link 2024 Nude Lea𝚔 emerging online has amed tremendous views across fan accounts and social media sites with one video clip. The viral video circulating recently shows Leaked viral link 2024 Nude Lea𝚔 in an unexpected and hilarious moment while in public running errands.
Numerous fans have rushed to watch the viral video and share the clip amongst followers featuring Leaked viral link 2024 Nude Lea𝚔 caught in an amusing and awkward situation. While surprising, the authentic and candid video showing Leaked viral link 2024 Nude Lea𝚔 handling a real life blooper so genuinely has earned praise from viewers. Nonetheless, fans watch the current viral video of Leaked viral link 2024 Nude Lea𝚔 that emerged online with delight and clamor for what the celebrity icon s reaction to the widely spread viral video will be.
The fan video showing Leaked viral link 2024 Nude Lea𝚔 first emerged on Twitter on Monday, posted by an amused fan who claimed to have captured the silly incident on their phone camera while out and about. The viral Clip of Leaked viral link 2024 Nude Lea𝚔 had garnered over 2 million views by Tuesday morning as more users on Instagram, Facebook and YouTube began uploading and sharing the embarring yet entertaining video.
Leaked viral link 2024 Nude Lea𝚔 Leaked viral link Lea𝚔 video
Leaked viral link 2024 Nude Lea𝚔 Leaked pictures
Leaked viral link 2024 Nude Lea𝚔 explicit content Lea𝚔
Leaked viral link account breach
Leaked viral link data hack
Leaked viral link 2024 Nude Lea𝚔 personal information exposed
Desi Xvideos Pakistani Sexy
Campinos 2014 Kajal
Leaked viral link 2024 Leaked Video
XnX VIRAL Leaked viral link Noodles Viral Video L𝚎aked on X Twitter
latest Leaked Video Viral On Social Media
Kompoz Me Leaked Com
Scoop Big Xn Celebrity
Latest News, Photos, Videos on Leaked Video
Outdoor Desi Village The
Latest Videos of Leaked Videos
Xnx VIRAL Leaked viral link Noodles Leaked Video Trending
Viral Leaked Video, Aakhir Woh Larki Kon Thi
Blue Flims 2024 Leaked
Trending Leaked Videos Viral
Leaked viral link
Viral Ice Spice Leaked Video Trending ON Twitter
18+ viral mms Leaked video telegram links
Telegram LINK!!


Amend table

Codecov Report

Merging #165 into master will increase coverage by 0.27%.
The diff coverage is 79.16%.

@@             Coverage Diff              @@
##             master     #165      +/-   ##
============================================
+ Coverage     51.84%   52.11%   +0.27%
- Complexity      564      566       +2
============================================
  Files           114      114
  Lines          2494     2502       +8
  Branches        305      307       +2
============================================
+ Hits           1293     1304      +11
+ Misses         1115     1110       -5
- Partials         86       88       +2

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/seedu/address/ui/HelpWindow.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

...java/seedu/address/logic/commands/DoneCommand.java
80.55% <77.27%> (-5.16%)
10.00 <1.00> (ø)

.../seedu/address/logic/parser/DoneCommandParser.java
100.00% <100.00%> (+100.00%)
2.00 <1.00> (+2.00)

Continue to review full report at Codecov.

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


[BUG] Adding a space at the bottom of an outline disables the ability to move lists and sublists

Describe the bug
Moving lists and sublists up and down does not work if the line immediately following the outline starts with a space.
Expected behavior
I don't know if this is intended behavior or not, but it was unexpected.
Desktop (please complete the following information):

OS: Windows 11
Obsidian Version: 1.0.2

Can you attach an example file?

Below is a demo. It appears that the issue only occurs when there is one top-level bullet.

I think coz the empty bullet at the end is not a valid item 🤔
You also can't add a new one if the last item is empty


change CLI to support specific extenasions as does the Slang verifier

Support only:

sl
sl.yaml
sl.yml

Do not support other extensions

At what point to we want the error to occur? I can check right in the run method of SlangCLI before anything compiles and just show a message, or maybe throw an error in CompilerHelperImpl. ATM I implemented the first approach.

Also as FilenameUtils.getExtension does return just extensions from files like "file.extension" (not "file.extension.extension") I had to implement a custom method. If anyone knows a better suited library for this action I would appreciate it :).

Look at SlangContentVerifier.
You can still use FileUtils.listFiles(), and pass as the file extensions: {"sl", "sl.yaml", "sl.yml"}

FileUtils.listFiles() gets all the files with that specific extension from a directory(parent directory of the file given in the CLI). Afterwards I have to iterate them and check that my file is among them. If the file is in a directory that contains a lot more files then it might not be very efficient.
Wouldn't it be easier just to substring the given filename from the first "." to get the extension and just check it corresponds to the ones we are looking for?

@oritstone please review


[WIP] Update to rotor filter component

Added functionality to filter rotors by minimum no. of rotors to be present, additional filter_by arg in the function which defaults to 'max' so that previous tests and functionality are unaffected, and added new tests
Description
If we decide to fragment molecules during dataset creation that have rotors above a threshold value this filter helps in keeping only molecules that meet this threshold.
Todos

[x] Filters rotors by minimum number of rotors to be present

Status

[ ] Ready to go

@pavankum Thanks for putting this together this looks great. One thing I think could be changed is the filter_by argument this would then let users filter by both max and min at the same time in one go like the element/weight filters. Users could still filter by max/min if we allow the other to take None which would skip the check so we would have something like
# filter molecules with between 2 and 6 rotatable bonds
rotor_filter.maximum_rotors = 6
rotor_filter.minimum_rotors = 2

# filter molecules with at least 2 rotatable bonds
rotor_filter.maximum_rotors = None
rotor_filter.minimum_rotors = 2

# filter molecules with no more than 5 rotatable bonds
rotor_filter.maximum_rotors = 5
rotor_filter.minimum_rotors = None

otherwise users wishing to filter by max and min in the workflow would have to add the component twice which is possible but more work.

@pavankum Thanks for putting this together this looks great. One thing I think could be changed is the filter_by argument this would then let users filter by both max and min at the same time in one go like the element/weight filters. Users could still filter by max/min if we allow the other to take None which would skip the check so we would have something like
# filter molecules with between 2 and 6 rotatable bonds
rotor_filter.maximum_rotors = 6
rotor_filter.minimum_rotors = 2

# filter molecules with at least 2 rotatable bonds
rotor_filter.maximum_rotors = None
rotor_filter.minimum_rotors = 2

# filter molecules with no more than 5 rotatable bonds
rotor_filter.maximum_rotors = 5
rotor_filter.minimum_rotors = None

otherwise users wishing to filter by max and min in the workflow would have to add the component twice which is possible but more work.

@jthorton Thanks Josh for the review. Yeah, it makes sense to have a general filter, I made the changes.

@jthorton Thanks Josh for the review. Yeah, it makes sense to have a general filter, I made the changes.

@pavankum thanks for making the changes only the last two things to change and this should be good to go.

@pavankum thanks for making the changes only the last two things to change and this should be good to go.

@pavankum Thanks for starting this I have finished this in #132 as this has been parked for a while let me know if you find any issues.


Reduce permissions needed for Login with Github

Helps reduce friction to get users on the platform.
Fixes #519

Pull Request Test Coverage Report for Build 1830

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 66.938%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

util/passport.js
0
1
0.0%

Totals

Change from base Build 1825:
0.08%

Covered Lines:
6843

Relevant Lines:
9612

💛  - Coveralls


OrientDB version was updated till 2.2.10, mistakes are fixed

Several mistakes in OrienDBClient (mostly related to initialization in multithreaded loads) were fixed.

@kruthar Not sure you have time to review this, but I think you were the last to look at the OrientDB code.

Hi @risdenk , I have updated pull request according to your comments.

@laa Saw your comments about addressing some items but not sure the changes were pushed to this branch? ie: still see the author tags

@risdenk what do you mean ,  authors tags should be present or absent ?

There should be no author tags. Attribution is based on commit username.

@risdenk done, tags are removed

@risdenk sorry for delay seems all observations are fixed.

@laa changes look good. I'm pulling it down locally to check and waiting on CI tests to finish. Is it possible for you to squash the commits and start the single commit message with [orientdb]?

@laa changes and tests pass. It looks like I can squash and merge through Github. I'll do that in a few minutes. Thanks for your patience!


Improve win32 compatibility

Versions
nx-vite-federation: sha 84580e72ae78f0f8eb05ebf32d920aa36a5fdccf
OS: Windows 11
terminal: bash
npm: 9.7.2
node: 20.4.0
spawn config isn't setup the best way in scripts/start-federation.js

Fix Suggestion:
Add
{stdio: 'inherit', shell: true}

to all spawn() functions in the file.
lines:
60,
62,
66,
68

That's a very cool project, I'm looking forward to use and maybe even to contribute.

Versions
nx-vite-federation: sha 84580e7 OS: Windows 11 terminal: bash npm: 9.7.2 node: 20.4.0
spawn config isn't setup the best way in scripts/start-federation.js

Fix Suggestion:
Add
{stdio: 'inherit', shell: true}

to all spawn() functions in the file.
lines:
60, 62, 66, 68

That's a very cool project, I'm looking forward to use and maybe even to contribute.

Thanks a lot for your feedback, I'll be back after finishing some of my work soon!!

problem has been resolved. Please check out the repo!!


Taskcat container missing go lang runtimes?

Describe the bug
I get errors trying to use taskcat that seems to indicate that it is missing the go lang runtimes (or they are not mapped when I enter the container with sh):
Initial Error:
This command docker run -it -v $(pwd):/mnt -v ${HOME}/.aws/credentials:/root/.aws/credentials:ro -v /var/run/docker.sock:/var/run/docker.sock taskcat/taskcat taskcat --debug test run --no-delete --keep-failed --test-names smallest-possible --regions eu-central-1
Eventually results in this error:
[INFO   ] : Packaging lambda source from /mnt/submodules/quickstart-amazon-eks/functions/source/HelmReleaseResource using docker image taskcat-build-9bcb5b76772059b7bbae56916a00c99a
[WARN   ] : No stacks were created... skipping cleanup.
[ERROR  ] : BuildError The command '/bin/sh -c GOPROXY=direct go mod download' returned a non-zero code: 1
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/taskcat/_cli.py", line 46, in main
    [cli.run](http://cli.run/)()
  File "/usr/local/lib/python3.8/site-packages/taskcat/_cli_core.py", line 314, in run
    return getattr(command(), subcommand)(**args)
  File "/usr/local/lib/python3.8/site-packages/taskcat/_cli_modules/test.py", line 167, in run
    with test:
  File "/usr/local/lib/python3.8/site-packages/taskcat/testing/base_test.py", line 58, in __enter__
    raise ex
  File "/usr/local/lib/python3.8/site-packages/taskcat/testing/base_test.py", line 55, in __enter__
    [self.run](http://self.run/)()
  File "/usr/local/lib/python3.8/site-packages/taskcat/testing/_cfn_test.py", line 102, in run
    LambdaBuild(self.config, self.config.project_root)
  File "/usr/local/lib/python3.8/site-packages/taskcat/_lambda_build.py", line 34, in __init__
    self._build_submodules()
  File "/usr/local/lib/python3.8/site-packages/taskcat/_lambda_build.py", line 41, in _build_submodules
    self._recurse(self._project_root, rel_source, rel_zip)
  File "/usr/local/lib/python3.8/site-packages/taskcat/_lambda_build.py", line 52, in _recurse
    self._build_lambdas(source_path, output_path)
  File "/usr/local/lib/python3.8/site-packages/taskcat/_lambda_build.py", line 67, in _build_lambdas
    self._docker_build(path, tag)
  File "/usr/local/lib/python3.8/site-packages/taskcat/_lambda_build.py", line 135, in _docker_build
    _, logs = self._docker.images.build(path=str(path), tag=tag)
  File "/usr/local/lib/python3.8/site-packages/docker/models/images.py", line 287, in build
    raise BuildError(chunk['error'], result_stream)
docker.errors.BuildError: The command '/bin/sh -c GOPROXY=direct go mod download' returned a non-zero code: 1

Loading container and trying to run go commands from above:
$ docker run -it -v $(pwd):/mnt -v ${HOME}/.aws/credentials:/root/.aws/credentials:ro -v /var/run/docker.sock:/var/run/docker.sock taskcat/taskcat sh
/mnt # /bin/sh -c GOPROXY=direct go mod download
/mnt # GOPROXY=direct go mod download
sh: go: not found

To Reproduce
Steps to reproduce the behavior:

Are you testing a QuickStart or Custom template?
Attach or link a copy of the template if possible (remove any sensitive info)
Provide the parameters that you passed. (remove any sensitive info)
How did you install taskcat? (docker or pip3)
Are you using a profile, an instance role or  access keys to run taskcat?
Is your AWS environment configured via aws configure?

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
**Version (Please make sure you are running the latest version of taskcat)

Taskcat Container AND Binary Version: 0.9.30

Note: Python Version (python3 required)
To find versions:
Via taskcat: taskcat -V
Via pip3: pip3 show taskcat
Note: both version should match => Yes they match
Additional context
Add any other context about the problem here.

I am looking into this

@troy-ameigh - I just added the version details to the description - it is 0.9.30

@troy-ameigh - I just tested the 0.9.31 container you pushed and I get the same error.

My code is here if it helps: https://github.com/aws-quickstart/quickstart-eks-gitlab/pull/128


Update jsoniter-scala-core to 2.24.2

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

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.plokhotnyuk.jsoniter-scala", artifactId = "jsoniter-scala-core" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #260.


refactor: move src/global to src/components/core

Moves the global directory into src/components as core directory.

Codecov Report

:exclamation: No coverage uploaded for pull request base (lit-migration@54e23ce). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@               Coverage Diff                @@
##             lit-migration    #2140   +/-   ##
================================================
  Coverage                 ?   95.68%
================================================
  Files                    ?      223
  Lines                    ?    35541
  Branches                 ?     2095
================================================
  Hits                     ?    34008
  Misses                   ?     1495
  Partials                 ?       38

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Adding some risky secrets 08/15/23 19 51

@JoeVayApiiro Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.