Use build name as default context and description.

If context is left blank now defaults to the environmental
variable "BUILD_JOB_NAME" which is passed as metadata by
Concourse and contains the job name.
If description is left blank now defaults to a string
specifying the build name and the build number.
This change, together with the use of anchors in the
pipeline configuration file, can significantly reduce
the amount of duplication required.
Signed-off-by: Alessandro Degano<EMAIL_ADDRESS>

@colstrom Hello, when you have a minute could you please give a look at this?
Thank you!

@colstrom Do you have time to maintain this repository? Thanks!

@aledeganopix4d @marco-m Thanks for your patience.
This seems like a useful enhancement, thanks for contributing! Merging now.

These changes are available in 0.6.6.


Add OLM manifests for Dynatrace OneAgent Operator v0.8.0

New Submissions

[x] Does your operator have nested directory structure?
[x] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@DTMad Can you please signoff this, since you are previous contributor? Thanks

@DTMad Can you please signoff this, since you are previous contributor? Thanks

Hey @mvalahtv!
@lrgar and me are the two main dev's on the Dynatrace-oneagent-operator, so for me this is fine.
Would you like us to commit it again by me to also have it signed by me or is it ok like that?
Thanks,
Marco


Push Notification not received in background in Oppo Phones

Oppo phones do not receive Firebase push notifications in the background in Oppo Nougat 8

You may received that error because of any one of the following 3 reasons:

Oauth Id mismatch in DB

The role supposed to be either SELLER or SHOP_OWNER

You also need to add an entry in 'user_shop' table, which links the user with the given shop. So basically userId = 5, shopId = 1, there should be entry (user_id, shop_id) = (5, 1) in user_shop table.

Join our discord group to clear your doubts and get updates about latest development in zinger framework.
Discord invite : https://discord.gg/TqADaXV


Fix issue #11 tri-linear logos at the top

I thinks this was the best way to add the bullets between the logos. Check in css and tell me with you think there is a better approach.
Obs: There is an error in the "npm test" not related with my changes
Close issue #11

Perfect!!

If you enjoyed the work, a ⭐ to the repo would be highly appreciated.


wss client support Http authentication (IDFGH-7090)

hello, I was doing a job with websocket and I see the need to use basic authentication in the handshake, when reviewing the documentation I found that it is not supported at the moment, I would like to know if they will add this feature (which should not be difficult ) or if using the header field of esp_websocket_client_config_t the same result can be obtained

Hi @diazmanuel
Yes, you can use additional header for that.
Here's an example of generating the basic http authentication header:
    #define USER "user"
    #define PASSWORD "password"
    ....
    unsigned char user_auth[] = USER ":" PASSWORD;
    char add_header[]="Authorization: Basic ";
    size_t outlen = 0;
    size_t encoded_len = sizeof(user_auth)*4/3 + sizeof(user_auth)/96 + 6 + sizeof(add_header);
    unsigned char * encoded = calloc(1, encoded_len);
    memcpy(encoded, add_header, sizeof(add_header));
    esp_crypto_base64_encode(encoded + sizeof(add_header) - 1, encoded_len - sizeof(add_header), &outlen, user_auth, sizeof(user_auth) - 1);
    esp_websocket_client_config_t websocket_cfg = { .headers = (char *)encoded, ... };
    ... // after starting the client
    free(encoded);

Thanks for reporting, will close due to short of feedback, feel free to reopen with more updates. Thanks.

Hello @david-cermak,
I tried using the headers for a token-based authorization, but couldn't make it work.
Here is my code
esp_websocket_client_config_t websocket_cfg = {};

websocket_cfg.uri = "ws://localhost:5000/testing";
websocket_cfg.port = 80;
websocket_cfg.headers = "authorization: token"
websocket_cfg.user_agent = "my-custom-user-agent"

esp_websocket_client_handle_t client = esp_websocket_client_init(&websocket_cfg);

Any help would be highly appreciated.

Hi, This issue can be resolved by placing the newline character at end of the auth token string in the headers parameter.
For example,
websocket_cfg.headers = "Authorization: token\n
This will work definitely we have tried from our end.

Hi all,
I am trying the basic Auth for websocket just like @david-cermak suggested. It seems to work as I get an answer though the response I get gives me an error:
E (652021) TRANSPORT_WS: Error read response for Upgrade header GET /xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Connection: Upgrade
Host: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
User-Agent: ESP32 Websocket Client
Upgrade: websocket
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sec-WebSocket-Protocol: ocpp1.6
Authorization: Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Do you have an idea on how to solve this?


[$250] Expense report-Submit & approve button not disappear until page refreshed

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: Y
Reproducible in production?: N
Found when validation PR: https://github.com/Expensify/App/pull/48362
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition: log into OD as an admin, create a control policy, enable workspace chats, select "Advanced Approvals", invite 3 members (non-admin): 2 approvers and 1 submitter, set the approval flow as submitter submits to approver 1

Log into ND as submitter
Navigate to the workspace chat
Submit one manual expense
Open the report and click on the "Submit" button
As admin, change the the submitter's submitsTo to approver 2 in OD
Log into ND as approver 1
Opened the submitted report
Click on the "Approve" button

Expected Result:
The 'Submit" button disappears immediately for the submitter (step 4) and the "Approve" button disappears for the approver (step 8)
Actual Result:
The "Submit" and "Approve" button do not disappear until the page is refreshed or it is clicked on the second time (the "Approve" button)
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/fbe312ce-13f0-4ca2-b847-90377f45606f

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01efec68070b933fc3
Upwork Job ID:<PHONE_NUMBER>567798044
Last Price Increase: 2024-10-29
Automatic offers:

nkdengineer | Contributor | 104649054

Issue OwnerCurrent Issue Owner:

We think this issue might be related to the #wave-control

Production
https://github.com/user-attachments/assets/22cd9b0c-8fcf-4a91-a157-6a32110a047f
https://github.com/user-attachments/assets/226b3376-227d-489b-b719-69b05e0ddb4e

Looked into this and I think this might be a problem with manually submitting reports. I verified this by:

Creating a workspace
Setting the submit frequency to manual
Creating an expense
Submitting the expense
Seeing the submit button re-appear

https://github.com/user-attachments/assets/5f94e465-37f8-4c63-8a2c-e0edc2ef4563

I don't think this is a backend bug because the SubmitReport response is the same on staging and production.

I think this could be a possible culprit

I think this could be a possible culprit

No, that PR didn't hit staging yet

Ah you're right thanks

Hm, I'm not able to reproduce this in the latest dev.
https://github.com/user-attachments/assets/0396d84c-ea8b-419d-ada7-756d4b8aba57

Still debugging on dev but going to add the external label to see if we can speed things up

Hmm, actually this might be backend. After the SubmitReport call, we do a GetMissingOnyxUpdates which is setting the status of the report back to 0 which is re-rendering the submit button. For some reason, this only happens in staging and not production:

Seeing some flickering behavior on production as well occasionally:
https://github.com/user-attachments/assets/be7404be-37e0-494e-b88a-6a703d57338a

Yeah actually I'm able to reproduce this on production pretty reliably:
https://github.com/user-attachments/assets/46ba12dd-5a7f-4599-8611-c33c5b216457
I think this is a larger problem with the SettlementButton. Since this is occurring on production as well, I think we can demote this from a DeployBlocker, what do you think @roryabraham?

Yep, agreed that since it's reproducible on prod we can demote this

Proposal
Please re-state the problem that we are trying to solve in this issue.
The "Submit" and "Approve" button do not disappear until the page is refreshed or it is clicked on the second time (the "Approve" button)
What is the root cause of that problem?

The "Submit" and "Approve" button do not disappear until the page is refreshed or it is clicked on the second time (the "Approve" button)

The submit button still appears because after SubmitReport API is complete the GetMissingOnyxMessage API is called that returns the data of the expense report with stateNum and statusNum as 0.

When we submit an expense report, the manager of the expense report is the approver 1 then when we change the approver the manager is still approver 1 then the canApproveIOU function returns true because it only covers the case submit and approve mode, it doesn't cover the case advance approve.

https://github.com/Expensify/App/blob/3e5da7810fdc48ce391db3ed3aa7dab86a59c490/src/libs/actions/IOU.ts#L6815-L6823
What changes do you think we should make in order to solve the problem?

For the submit button, we should fix it from BE side

For the approve button, we should update canApproveIOU to cover the case advance approve mode then for this case the submitTo of the ownerAccountID of expense report can approve the report

const isControlOnAdvancedApprovalMode = PolicyUtils.isControlOnAdvancedApprovalMode(policy);
if (isControlOnAdvancedApprovalMode) {
    const ownerAccountID = iouReport?.ownerAccountID ?? '-1';
    const employee = policy?.employeeList?.[ownerAccountID];
    return employee?.submitsTo === currentUserEmail;
}

What alternative solutions did you explore? (Optional)

@nkdengineer Thanks for your proposal.

The submit button still appears because after SubmitReport API is complete the GetMissingOnyxMessage API is called that returns the data of the expense report with stateNum and statusNum as 0.

Can you elaborate on this part? What's the current behaviour of the API that causes the bug? And what the expected behaviour should be for the API? So, it'll be easier for the internal engineering team to look into the issue.

Can you elaborate on this part? What's the current behaviour of the API that causes the bug? And what the expected behaviour should be for the API?

The SubmitReport API returns the correct data  with stateNum and statusNum as 1. After that GetMissingOnyxMessage  API is called that returns stateNum and statusNum as 0 which causing the first bug.

I agreed with @nkdengineer 's investigation. Let's go with their proposal.
@srikarparsi Please help with the backend part and all yours!
🎀👀🎀 C+ reviewed

Hey @slafortune! My K2 is pretty full right now and since this is a backend issue I don't think I'll have time for it this week or next week. Do you think you could check if this fits into a wave/vip so that someone with bandwidth can maybe work on it? This is the SO for that I believe.

@slafortune We also need the front-end change in this issue as I mentioned in my proposal. We can do it separately since the front-end bug doesn't require the BE change.

Precondition: log into OD as an admin, create a control policy,

Moving to the #wave-control project.

Not overdue, we're waiting for the backend fix

Not overdue, we're waiting for the backend fix

Not overdue. Same^

Not overdue, we're waiting for the backend fix

Not overdue. Same^

Same^

Not overdue, we're waiting for the backend fix

Not overdue. Same^

Same^

Same^
@slafortune Can you help to ask an internal engineer to pick up this? Or maybe we can demote it to weekly

@slafortune Can you ask an internal engineer to hot pick this one for the backend fix?

Not overdue, we're still waiting for hot pick

Bumped in slack https://expensify.slack.com/archives/C01GTK53T8Q/p1728660271578649

@eh2077 Another thing, we have two problems in this issue and the frontend bug doesn't depend on the BE change then can you add a C+ review comment here again then we can move forward with the frontend bug.

@eh2077 Another thing, we have two problems in this issue and the frontend bug doesn't depend on the BE change then can you add a C+ review comment here again then we can move forward with the frontend bug.

@nkdengineer Thanks for your comment. Can you check if the frontend bug is still reproducible? If so, then I think we can move forward with the frontend bug and handle the backend issue separately

Since the GH does have the Hotpick tag, it is seen for an engineer to pick up.  Once you've tested if this is reproducible, I can post it to a room to have the status updated to something appropriate 👍

Issue not reproducible during KI retests. (First week)

Issue not reproducible during KI retests. (First week)

Not overdue

@eh2077 The BE bug is no longer reproducible. I can still reproduce the FE bug.

Sounds like I can remove the hotpick and internal tags - is there a FE fix in the works?

@eh2077 is there a fix here that can be assigned?

@nkdengineer Thanks for your proposal!
I also managed to reproduce the frontend bug. I think we can go with @nkdengineer 's proposal to fix it.
🎀👀🎀 C+ reviewed

Hey @NikkiWines - does the recommended proposal look like a go?

Oops, sorry - missed this one somehow. Agreed that @nkdengineer's proposal to fix the FE bug is good 👍

@eh2077 We have a problem after we submit the report to approver 1 and change the submitsTo to approver 2. If approver 2 clicks on the approver button, BE returns the error.

PR is in the works, @nkdengineer do you need further clarification on this comment?

@eh2077 We have a problem after we submit the report to approver 1 and change the submitsTo to approver 2. If approver 2 clicks on the approver button, BE returns the error.

@nkdengineer Does the backend error block testing your PR? If so, can you share the detail reproduction steps? Then we can we ask help from @NikkiWines

^^ in the works

@nkdengineer Does the backend error block testing your PR? If so, can you share the detail reproduction steps? Then we can we ask help from @NikkiWines

The problem is when I display the approve button for the approver 2 with the original step of the bug, the approver 2 cannot approve the expense report.

@nkdengineer Do you mean after step 5, As admin, change the the submitter's submitsTo to approver 2 in OD, you can't approve the expense if login as approver 2?

@nkdengineer can you respond to @eh2077 here please 🙇

Do you mean after step 5, As admin, change the the submitter's submitsTo to approver 2 in OD, you can't approve the expense if login as approver 2?

@eh2077 Yes, that's correct.

Do you mean the report when approver1 clicks Approve is then sent to the "new" approver to approve as well? If so, I'm not aware of that historical logic.

@trjExpensify Yes, you can check the above video from 0:50 to 1:05

Nice, thanks! I'm confused what we're doing with this issue then? The OP is pretty unclear really. It sounds like it was created from this PR, but the expected results still confuse me when looking at that PRs test steps.
It sounds like we expect this:

After someone manually submits a report, the submit button should disappear for them right away. It's submitted.
If the report is submitted AND THEN the approver is changed.
a. Approver1 should still see the GBR on the expense report and the approve button
b. Approver 1 should be able to click that button to approve the report
c. Approver2 does not see the GBR nor the approve button.

Does that sound right to you? CC: @Beamanator @marcochavezf from the linked PR as well.

I could be wrong, but I think Approver 1 doesn't see GBR on the expense report at first (when they're in the submitter's approval chain) b/c they should see GBR on the policy chat report instead.
Once Approver 1 is swapped with Approver 2, Approver 1 should see the GBR on the expense report b/c they no longer have access to the policy chat & shouldn't see the policy chat in the LHN

Ah yes, great clarification. 👍

Thanks! 🙏  Curious if there's anything else I'm needed for here? Happy to help, don't want y'all to be waiting on me

Nice, thanks! I'm confused what we're doing with this issue then? The OP is pretty unclear really. It sounds like it was created from this PR, but the expected results still confuse me when looking at that PRs test steps.
It sounds like we expect this:

After someone manually submits a report, the submit button should disappear for them right away. It's submitted.
If the report is submitted AND THEN the approver is changed.
a. Approver1 should not see the GBR on the workspace chat (they've been removed), they should instead see the GBR on the expense report and the approve button
b. Approver 1 should be able to click that button to approve the report
c. Approver2 does not see the GBR nor the approve button.

@trjExpensify Thanks for driving clarity!
@Beamanator @NikkiWines I think we'll have to fix 2c from backend because, after performing 2b, the approver2 is able to see the approve button. See the video from 0:50 to 1:05 of this https://github.com/Expensify/App/issues/48463#issuecomment-2483687769

I'm pretty sure what @trjExpensify was saying was that, after step 2, all of a, b, and c should be true. But after 2.b happens, it sounds likely that 2.c should be true, right?

Perhaps you could write out numbered steps on this particular concern with where it might not be working as expected, @eh2077?

Precondition: log into OD as an admin, create a control policy, enable workspace chats, select "Advanced Approvals", invite 3 members (non-admin): 2 approvers and 1 submitter, set the approval flow as submitter submits to approver 1

Log into ND as submitter
Navigate to the workspace chat
Submit one manual expense
Open the report and click on the "Submit" button
As admin, change the the submitter's submitsTo to approver 2 in OD

========== Check Approve button existence of expenses from two approvers ==========

Log into ND as approver 1 and open the submitted report
The Approve button is still available for approver 1, which is expected according to 2.a
Log into ND as approver 2 and open the expense report
There's no Approve button to approve the expense, which is expected according to 2.c

========== Check the workflow of approving ==========

Log into ND as approver 1 and open the expense report
The approver 1 clicks the Approve button and is able to approve the expense, which is expected according to 2.b
The expense is submitted to approver 2. Is this expected?
Log into ND as approver 2 and open the expense report
The approver 2 clicks the Approve button and is able to approve the expense. Is this expected?
The expense is approved without error and the status is changed to Waiting for an admin to pay expense(s). Is this expected?

https://github.com/user-attachments/assets/58212f47-4923-4a78-8147-f21cf341a5de
@trjExpensify @Beamanator Please help to confirm the expected behaviours of highlighting steps, thanks! See the video from 0:50 to 1:05

As far as I know, YES all of those are expected because AFTER approver 1 approves the report (in step 11), we look at the submitter's current approval chain (which at that step, only includes approver 2) - and since approver 2 hasn't approved yet, they become next on the list to approve the report 👍

Interesting. That's the behaviour on OldDot as well? Do you have the code to link for ref? I asked @NikkiWines about that above, and neither of us could confirm that's the case.

Do you mean the report when approver1 clicks Approve is then sent to the "new" approver to approve as well? If so, I'm not aware of that historical logic. I would have assumed this report would go to the approvesTo || overLimitForwardsTo set for approver1. Any new reports get submitted to the new approver, or if the report is rejected and resubmitted. @NikkiWines I had a rummage for this one in the code, but couldn't find it to confirm/deny.

Agreed with @trjExpensify - I just checked the flow on oldDot and for reports that are 'in progress' (i.e. going through the approval process), we don't seem to update the approver to the newly set one. The updated approver only applies if the report is rejected & resubmitted or if a new report is made.

Do you mean the report when approver1 clicks Approve is then sent to the "new" approver to approve as well? If so, I'm not aware of that historical logic. I would have assumed this report would go to the approvesTo || overLimitForwardsTo set for approver1.

I know I USED TO think that way 😅  then I did a decent amount of testing and found that not to be the case, I thinkkkkk I explained in slack somewhere... it's all related to this "conclusion" i posted

So the points are:

If a report already has a manager & they get removed from the approval chain, we stop caring about the current manager's approval chain, and we purely care about "who is next to approve in the submitter's current / new approval chain"

In ReportUtils::buildApprovalChain (this is the OldDot approval-chain building... NewDot does it all in Auth) you can see that the current report manager is never inserted into the chain, we ONLY insert:

$ruleApprovers (category / tag approvers)
The approvalChain built from the policy's submitsTo -> forwardsTo -> ...

Not overdue, discussion is ongoing

In ReportUtils::buildApprovalChain (this is the OldDot approval-chain building... NewDot does it all in Auth) you can see that the current report manager is never inserted into the chain, we ONLY insert:

$ruleApprovers (category / tag approvers)
The approvalChain built from the policy's submitsTo -> forwardsTo -> ...

Great stuff! So I agree we can close this issue then. :)

Thanks all!  Those details are super helpful

@slafortune Should I have compensation for this issue since it was assigned and I spent a lot of effort following this issue and worked on the PR here before we decided to close this as expected? This is a similar case.

@slafortune friendly bump here


Fix deserialization

Fix deserialization: two-byte extensions, keep options and payload as bytearray before parsing, skip unknown options, if they are not critical

Coverage decreased (-0.3%) to 89.426% when pulling 0e950fd3497968dd7e3a16b08f88f5650ea9772a on yarisx:master into f67da59cb68254513786a22d5de47c45a1bfea75 on Tanganelli:master.


Problem with libsqlite3

2022-03-05 10:06:07 ERROR (MainThread) [homeassistant.setup] Setup failed for recorder: Unable to import component: Error loading shared library libsqlite3.so.0: No such file or directory (needed by /usr/
2022-03-05 10:06:07 ERROR (MainThread) [homeassistant.setup] Setup failed for recorder: Unable to import component: Error loading shared library libsqlite3.so.0: No such file or directory (needed by /usr/
lib/python3.9/lib-dynload/_sqlite3.cpython-39.so)
2022-03-05 10:06:13 ERROR (MainThread) [homeassistant.setup] Setup failed for analytics: Unable to import component: Error loading shared library libsqlite3.so.0: No such file or directory (needed by /usr
/lib/python3.9/lib-dynload/_sqlite3.cpython-39.so)
2022-03-05 10:06:13 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of onboarding. Setup failed for dependencies: analytics
2022-03-05 10:06:13 ERROR (MainThread) [homeassistant.setup] Setup failed for onboarding: (DependencyError(...), 'Could not setup dependencies: analytics')
2022-03-05 10:06:13 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of frontend. Setup failed for dependencies: onboarding
2022-03-05 10:06:13 ERROR (MainThread) [homeassistant.setup] Setup failed for frontend: (DependencyError(...), 'Could not setup dependencies: onboarding')
2022-03-05 10:06:14 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of history. Setup failed for dependencies: recorder
2022-03-05 10:06:14 ERROR (MainThread) [homeassistant.setup] Setup failed for history: (DependencyError(...), 'Could not setup dependencies: recorder')
2022-03-05 10:06:14 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of logbook. Setup failed for dependencies: frontend, recorder
2022-03-05 10:06:14 ERROR (MainThread) [homeassistant.setup] Setup failed for logbook: (DependencyError(...), 'Could not setup dependencies: frontend, recorder')
2022-03-05 10:06:14 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of my. Setup failed for dependencies: frontend
2022-03-05 10:06:14 ERROR (MainThread) [homeassistant.setup] Setup failed for my: (DependencyError(...), 'Could not setup dependencies: frontend')
2022-03-05 10:06:14 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of map. Setup failed for dependencies: frontend
2022-03-05 10:06:14 ERROR (MainThread) [homeassistant.setup] Setup failed for map: (DependencyError(...), 'Could not setup dependencies: frontend')
2022-03-05 10:06:15 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of energy. Setup failed for dependencies: history, recorder
2022-03-05 10:06:15 ERROR (MainThread) [homeassistant.setup] Setup failed for energy: (DependencyError(...), 'Could not setup dependencies: history, recorder')
2022-03-05 10:06:20 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of default_config. Setup failed for dependencies: energy, frontend, history, logbook, map, my
2022-03-05 10:06:20 ERROR (MainThread) [homeassistant.setup] Setup failed for default_config: (DependencyError(...), 'Could not setup dependencies: energy, frontend, history, logbook, map, my')
2022-03-05 10:06:20 WARNING (MainThread) [homeassistant.bootstrap] Detected that frontend did not load. Activating safe mode
2022-03-05 10:06:20 WARNING (MainThread) [homeassistant.helpers.frame] Detected integration that called async_timeout.current_task. The current_task call is deprecated and calls will fail after Home Assis
tant 2022.3; use asyncio.current_task instead. Please report issue for ssdp using this method at homeassistant/components/ssdp/__init__.py, line 520: return await self._description_cache.async_get_descrip
tion_dict(location) or {}
2022-03-05 10:06:22 ERROR (MainThread) [homeassistant.setup] Setup failed for analytics: Unable to import component: Error loading shared library libsqlite3.so.0: No such file or directory (needed by /usr
/lib/python3.9/lib-dynload/_sqlite3.cpython-39.so)
2022-03-05 10:06:24 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of onboarding. Setup failed for dependencies: analytics
2022-03-05 10:06:24 ERROR (MainThread) [homeassistant.setup] Setup failed for onboarding: (DependencyError(...), 'Could not setup dependencies: analytics')
2022-03-05 10:06:24 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of frontend. Setup failed for dependencies: onboarding
2022-03-05 10:06:24 ERROR (MainThread) [homeassistant.setup] Setup failed for frontend: (DependencyError(...), 'Could not setup dependencies: onboarding')

Some issue with dependency, but lib files is present in the lib folder
root@OpenWrt:/tmp# ls /usr/lib/python3.9/lib-dynload
_asyncio.cpython-39.so            _ctypes_test.cpython-39.so        _multibytecodec.cpython-39.so     _ssl.cpython-39.so                mmap.cpython-39.so
_bisect.cpython-39.so             _curses.cpython-39.so             _multiprocessing.cpython-39.so    _statistics.cpython-39.so         ossaudiodev.cpython-39.so
_blake2.cpython-39.so             _curses_panel.cpython-39.so       _opcode.cpython-39.so             _struct.cpython-39.so             parser.cpython-39.so
_bz2.cpython-39.so                _datetime.cpython-39.so           _pickle.cpython-39.so             _uuid.cpython-39.so               pyexpat.cpython-39.so
_codecs_cn.cpython-39.so          _dbm.cpython-39.so                _posixshmem.cpython-39.so         _xxsubinterpreters.cpython-39.so  readline.cpython-39.so
_codecs_hk.cpython-39.so          _decimal.cpython-39.so            _posixsubprocess.cpython-39.so    _xxtestfuzz.cpython-39.so         resource.cpython-39.so
_codecs_iso2022.cpython-39.so     _elementtree.cpython-39.so        _queue.cpython-39.so              _zoneinfo.cpython-39.so           select.cpython-39.so
_codecs_jp.cpython-39.so          _gdbm.cpython-39.so               _random.cpython-39.so             array.cpython-39.so               spwd.cpython-39.so
_codecs_kr.cpython-39.so          _hashlib.cpython-39.so            _sha1.cpython-39.so               audioop.cpython-39.so             syslog.cpython-39.so
_codecs_tw.cpython-39.so          _heapq.cpython-39.so              _sha256.cpython-39.so             binascii.cpython-39.so            termios.cpython-39.so
_contextvars.cpython-39.so        _json.cpython-39.so               _sha3.cpython-39.so               cmath.cpython-39.so               unicodedata.cpython-39.so
_crypt.cpython-39.so              _lsprof.cpython-39.so             _sha512.cpython-39.so             fcntl.cpython-39.so               xxlimited.cpython-39.so
_csv.cpython-39.so                _lzma.cpython-39.so               _socket.cpython-39.so             grp.cpython-39.so
_ctypes.cpython-39.so             _md5.cpython-39.so                _sqlite3.cpython-39.so            math.cpython-39.so

problem has gone after adding open lumi repositories to opkg sourcers list and reinstaling libsqlite3
[ -f /lib/libustream-ssl.so ] && echo "libustream already installed" || opkg install libustream-mbedtls
(! grep -q openlumi /etc/opkg/customfeeds.conf) && (
wget -q https://openlumi.github.io/openwrt-packages/public.key -O /tmp/public.key &&
opkg-key add /tmp/public.key && rm /tmp/public.key &&
echo 'src/gz openlumi https://openlumi.github.io/openwrt-packages/packages/19.07/arm_cortex-a9_neon' >> /etc/opkg/customfeeds.conf &&
echo "Feed added successfully!"
) || echo "Feed added already. Skip."


messagesReducer: Address a performance TODO for EVENT_NEW_MESSAGE.

Discovered while working on #4390, which was recently merged.

messagesReducer: Address a performance TODO for EVENT_NEW_MESSAGE.
Using the recently added getNarrowsForMessage.
And leave bidirectional comments with narrowsReducer so that we
never end up with messages in state.narrows that don't exist in
state.messages.

Thanks for the review! Revision pushed.

Thanks for the review! Revision pushed.

Looks good, thanks! Merged.
The rebase required a small fix to replace action.ownUser with action.ownUserId, to avoid a type error after rebasing past #4424.

Looks good, thanks! Merged.
The rebase required a small fix to replace action.ownUser with action.ownUserId, to avoid a type error after rebasing past #4424.

The rebase required a small fix to replace action.ownUser with action.ownUserId, to avoid a type error after rebasing past #4424.

Whew—thanks for catching that and doing that.

The rebase required a small fix to replace action.ownUser with action.ownUserId, to avoid a type error after rebasing past #4424.

Whew—thanks for catching that and doing that.

You can thank Flow for catching it :wink: -- which was probably the trickier part.

You can thank Flow for catching it :wink: -- which was probably the trickier part.


Cross-Correlation crashes with 'RUN' station

RUN seemed to be the culprit because when i remove it it works
Slack Message

The issue was a missing space after RUN and before \:
noisepy cross_correlate --format zarr --raw_data_path s3://scedc-pds/continuous_waveforms/ \
--xml_path s3://scedc-pds/FDSNstationXML/CI/ \
--ccf_path s3://marines-bucket/CCF \
--stations=SBC,RIO,DEV,CHN,RUN\
--start=2022-02-02 \
--end=2022-02-05

Without the space it becomes: --stations=SBC,RIO,DEV,CHN,RUN--start=2022-02-02 which means we are missing a start date and hence find no data.


.get returning undefined when inside an EventEmitter listener

As per this gist:
https://gist.github.com/dazld/6493549
output is as follows:
in dispatch:<PHONE_NUMBER>313
handler:<PHONE_NUMBER>313
routeMatched listener:  undefined

seems like this should work, but can't see what might be causing the problem - any ideas..?
Using node 0.10.13 and CLS 2.1.1

updated to 10.18 and output is the same.

Just to put it clear.
Do I get it right that CLS won't work with mongodb (and hence mongoose) out of the box?
Every query must be "fixed" to be CLS-aware?

It will work some of the time, and with some effort (look at the MongoDB instrumentation in newrelic -- lib/transaction/tracer/index.js and lib/instrumentation/mongodb.js are the places to start) you can put together a shim that will take care of everything, but yeah, out of the box there are some holes. As I mention above, I would like to automate the shimming process, but there's a tricky trade-off between having CLS take care of these things automatically and keeping CLS as lightweight as possible. CLS isn't useful if it imposes a heavy overhead.

Also, I'm pretty sure the original issue here is resolved, so I'm going to close this out. Requests and patches for better package-specific shims should be filed individually. Thanks!


Spawn notifications at 50% and 100% tech/civic progress

This should make playing without the tech/civic popups more enjoyable and improve overall qol

Please, let there be an option for this

@chaorace
Interested in contributing to this project. I could work on trying to figure this out if no one is doing it already.

@RatchetJ Be my guest! Also, here's a little intro:
https://github.com/chaorace/cqui/wiki/How-to-contribute-to-CQUI
Hopefully that'll cover the basics. Just ask if you need anything at all!

Sounds good.

@chaorace Any ideas on how to create a notification once it's determined it should be triggered? It doesn't seem like anything in NotificationPanel.lua does the actual creation.

@RatchetJ  Check out the MakeDebugNotification function

Ahh, yep, that might work. thanks.

Got it working using the status messages, which are a lot easier than the notifications. I know that's not what we want long term, but it's something. It spawns a new message each turn that the player is at or over 50%, and also once it's completed. More work could be done to reduce it to a certain range around 50%, or just one time once it goes over 50%. What do you think?

Maybe it alerts the player once and then after that not anymore. Also it might be nice to alert the player before they would cross the 50% threshold so that they can switch and then after the boost still have 1 turn left so that no science or culture is wasted.

Right now it displays once after progress exceeds 50%, then not again until that tech/civic completes. To switch it to doing the alert 1 turn before 50% is an easy switch (I would just have to multiply something by 2), so whichever one people want. Other than that decision I think I'm ready to initiate a pull request.

@RatchetJ Excellent! I believe throwing the notification 1 turn before 50% is best because it guarantees 0 wasted science points

Done. Also just created the pull request.

Resolved in PR #66


Add apiUrl to DiscoveredClusterSpec

Issue: https://github.com/open-cluster-management/backlog/issues/12445

/hold

/lgtm

/unhold


Colamanga could not find key type again

Source information
COLAMANGA 1.4.20
Source language
Chinese
Steps to reproduce
Refresh for new chapters to download
Unable to download new chapters
Expected behavior
Should automatically download chapters.
Actual behavior
It's same issue with #4942
Mihon/Tachiyomi version
0.17.0
Android version
Android 13
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Can't reproduce. Do you have manga and chapter to test with?

It seems work again now


add docker to contribution guide

As with roslibpy, I think it makes sense to add how to run the integration tests within the contribution guide.
What type of change is this?

[ ] Bug fix in a backwards-compatible manner.
[ ] New feature in a backwards-compatible manner.
[ ] Breaking change: bug fix or new feature that involve incompatible API changes.
[x] Other (e.g. doc update, configuration, etc)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I added a line to the CHANGELOG.rst file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
[ ] I ran all tests on my computer and it's all green (i.e. invoke test).
[ ] I ran lint on my computer and there are no errors (i.e. invoke lint).
[ ] I added new functions/classes and made them available on a second-level import, e.g. compas_fab.robots.Configuration.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary documentation (if appropriate)

oh, i suppose stopping the docker containers should also be listed...

Good idea.  Do you mean this docker compose file to be used for local testing or also for the github workflow?

Good idea. Do you mean this docker compose file to be used for local testing or also for the github workflow?

Ah good point! I thought about local testing, but this would make the github workflow faster (because it does not load the X forwarding part), so using it for both would be great

ok, @gonzalocasas, i added your docker-compose file, and it seems to work.  the integration tests are failing because of the compas.get('faces.obj') thing


Add 3 more projects

There's also:
https://github.com/turt2live/matrix-email-bot
https://github.com/turt2live/matrix-voyager-bot
https://github.com/turt2live/matrix-appservice-instagram
(which are all on the try matrix now page)

We'll just leave this up to Try Matrix Now.


Made controller code shorter

A bit of grammatical improvements and making redirection code shorter

@freekmurze Not much big change but I just saw a code review video on YouTube stating redirection code was a bit longer so thought of shortening it.

This change will slightly modify the behaviour. I'm going to keep things as they are for now.


number of detections in the tflite graph

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Linux Ubuntu 16.04

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:

TensorFlow installed from (source or binary): binary

TensorFlow version (use command below): 1.12.0

Python version: 2.7

Bazel version (if compiling from source):

GCC/Compiler version (if compiling from source):

CUDA/cuDNN version: CUDA Version 9.0.176

GPU model and memory:
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Dell Device [1028:0802]
Flags: bus master, fast devsel, latency 0, IRQ 130
Memory at db000000 (64-bit, non-prefetchable) [size=16M]
Memory at 70000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities:
Kernel driver in use: i915
Kernel modules: i915

You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior
Describe the expected behavior
Hi
I'm trying to detect more than 10 objects in the image ( which is default )
I'm usin the following commands:
bazel run -c opt tensorflow/contrib/lite/toco:toco -- --input_file=$OUTPUT_DIR/tflite_graph.pb --output_file=$OUTPUT_DIR/mobile_net_500.tflite --input_shapes=1,300,300,3 --input_arrays=normalized_input_image_tensor --output_arrays='TFLite_Detection_PostProcess','TFLite_Detection_PostProcess:1','TFLite_Detection_PostProcess:2','TFLite_Detection_PostProcess:3' --inference_type=FLOAT --max_detections=500 --max_classes_per_detection=1 --allow_custom_ops
I also modified
export_tflite_ssd_graph.py
flags.DEFINE_integer('max_detections', 500 <--- instead of 10,
'Maximum number of detections (boxes) to show.')
flags.DEFINE_integer('max_classes_per_detection', 1,
'Number of classes to display per detection box.')
but still giving 10 objects as output in the android [1,10,4].
any idea?
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
bazel run -c opt tensorflow/contrib/lite/toco:toco -- --input_file=$OUTPUT_DIR/tflite_graph.pb --output_file=$OUTPUT_DIR/mobile_net_500.tflite --input_shapes=1,300,300,3 --input_arrays=normalized_input_image_tensor --output_arrays='TFLite_Detection_PostProcess','TFLite_Detection_PostProcess:1','TFLite_Detection_PostProcess:2','TFLite_Detection_PostProcess:3' --inference_type=FLOAT --max_detections=500 --max_classes_per_detection=1 --allow_custom_ops
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Edit TFLiteObjectDetectionAPIModel.java NUM_DETECTIONS to be something bigger.

@SteveIb Is your bug resolved now?

Closing this, feel free to open if issue still persists.

@achowdhery yes thanks


Add commands for Windows

Hi, @clalancette,
I have removed all instances of "~/" from the documentation to ensure compatibility with Windows systems, as per your suggestions.
I have reviewed the modifications to ensure accuracy and compatibility. It would be greatly appreciated if you could take some time to review the updated content and provide any further feedback or approval as needed.
Thank you very much for your guidance and valuable suggestions. I look forward to your response.

@Mergifyio backport rolling humble


In profile page on dark mode text color issue

Description
In profile page on dark mode text color issue
I'm a GSSoC'23 contributor please assign me this issue under gssoc label and level.
Steps to reproduce
go to website and click on the post of view profile.
Screenshots

Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Description
In profile page on dark mode text color issue I'm a GSSoC'23 contributor please assign me this issue under gssoc label and level.
Steps to reproduce
go to website and click on the post of view profile.
Screenshots

### Desktop (please complete the following information)
_No response_
Smartphone (please complete the following information)
No response
Additional information
No response
Record

[x]  I agree to follow this project's Code of Conduct
[x]  I have checked the existing issues
[x]  I'm a GSSoC'23 contributor
[x]  I want to work on this issue

Hi @biplavmz , there's actually an background image. Text's colour's fine, it's problem with some browsers I guess which is not loading the background image, I don't know why?

Can you try resolving this browser issue? I want to fix this issue instead of using an alternative, like different css to load background?

Hii @narayan954  can we use linear gradient hear

because images are breaking in the Microsoft edge

I think if It doesn't affects the Ui, we can do this!! you can go ahead!

ok @narayan954


Fix map component javascript

Motivation
The javascript was probably removed when transforming the app to .Net core.
Retrieved the map javascript and stored it in the same folder as other js files.
Checklist

[ ] Code follows coding conventions held in this repo
[ ] Automated tests have been added
[ ] Tests are passing
[ ] Docs have been updated (if applicable)
[ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test
Should fix the map component on Contact and Cafes pages. (Already tested locally).

yup, lost in translation .) thx Ondra


Allow separate strong emphasis marker

Bug/issue #, if applicable: N/A
Summary
As it stands, the selection of an emphasisMarker in MarkupFormatter.Options determines the marker used for both emphasis and strong emphasis. However, the Markdown spec allows one to, and I prefer to, use different markers for emphasis as compared to strong emphasis. For example: _emphasis_ and **strong emphasis**.
This PR adds an Optional parameter to MarkupFormatter.Options that allows one to specify the marker used for strong emphasis. If omitted, it takes on the value of the marker used for normal emphasis.
Dependencies
None
Testing
I've updated the bundled markdown-tool as well, so you can simply run:
echo "Here's some **strong emphasis** and some _normal emphasis_" | swift run markdown-tool format --emphasis-marker _ --strong-emphasis-marker \*

which will replicate the input as output. But if one runs:
echo "Here's some **strong emphasis** and some _normal emphasis_" | swift run markdown-tool format --emphasis-marker _

the output is Here's some __strong emphasis__ and some _normal emphasis_ — i.e., the previous behavior is honored.
Steps:

Clone this PR/my repository
Run the above commands

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[ ] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

The ./bin/test script already fails for me on main, but I haven't introduced any new issues.

@swift-ci please test

@Kyle-Ye @QuietMisdreavus I've just rebased this PR on master, and all the tests (at least the ones that I can see) now pass. Would it be possible to get this merged?

@swift-ci please test

We are actually using GFM. So I believe we should refer into this spec

I was just about to link that, yeah

One more issue is for "___a___" or "***a***" input. If we specify emphasisMarker to be "_" and strongEmphasisMarker to be "*".
The result would be "_**a**_".
The order is expected but I do not see spec covers such usage. Can you provide some insights on this?

What specifically is your question? The ordering or whether it is allowed to have two different types of delimiters next to each other?
The ordering should be addressed by Example 476, and the fact that you are allowed to have different delimiters right next to each other is addressed by Example 472

Ah, I see what you are asking. I'll give two examples.

_**a**_ (which GitHub renders properly as a)

In this case, the first _ is a left-flanking delimiter run because it is a delimiter run 1) not followed by unicode whitespace and 2b) followed by a punctuation character and preceded by unicode whitespace (the start of line). The first ** is a left-flanking delimiter run because it is a delimiter run 1) not followed by unicode whitespace and 2a) not followed by a punctuation character.
 The second _ is a right-flanking delimiter run because it is a delimiter run 1) not preceded by unicode whitespace and 2b) preceded by a punctuation character and followed by unicode whitespace (the end of line).
The first _ can open emphasis because it is part of a left-flanking delimiter run and a) not part of a right-flanking delimiter run. The first ** can open strong emphasis because it is part of a left flanking delimiter run.
The second ** can close strong emphasis because it is part of a right flanking delimiter run. The second _ can close emphasis because it is part of a right-flanking delimiter run and a) not part of a left-flanking delimiter run

"_**a**_" (which GitHub renders properly as "a")

In this case, the first _ is a left-flanking delimiter run because it is a delimiter run 1) not followed by unicode whitespace and 2b) followed by a punctuation character and preceded by a punctuation character. The first ** is a left-flanking delimiter run because it is a delimiter run 1) not followed by unicode whitespace and 2a) not followed by a punctuation character.
 The second _ is a right-flanking delimiter run because it is a delimiter run 1) not preceded by unicode whitespace and 2b) preceded by a punctuation character and followed by a punctuation character.
The first _ can open emphasis because it is part of a left-flanking delimiter run and a) not part of a right-flanking delimiter run. The first ** can open strong emphasis because it is part of a left flanking delimiter run.
The second ** can close strong emphasis because it is part of a right flanking delimiter run. The second _ can close emphasis because it is part of a right-flanking delimiter run and a) not part of a left-flanking delimiter run

@Kyle-Ye hopefully that addresses your question. I do wish that they had examples, though

@Kyle-Ye hopefully that addresses your question. I do wish that they had examples, though

Got it. They are indeed grammatically correct. Just hoping we go a example in the spec though. LOL

I think that latest commit should address your other concern — let me know if you'd like any other changes to be made

@swift-ci test

I feel like combined emphasis and strong emphasis should all be rendered with the strong emphasis marker, but that requires that visitEmphasis checks its immediate parent and/or child to see if it's part of a combination emphasis.
That would look something like this:
    public mutating func visitEmphasis(_ emphasis: Emphasis) {
        let emphasisMarker: String
        if let parent = emphasis.parent as? Strong, parent.childCount == 1 {
            emphasisMarker = formattingOptions.strongEmphasisMarker.rawValue
        } else if emphasis.childCount == 1, emphasis.child(at: 0) is Strong {
            emphasisMarker = formattingOptions.strongEmphasisMarker.rawValue
        } else {
            emphasisMarker = formattingOptions.emphasisMarker.rawValue
        }
        print(emphasisMarker, for: emphasis)
        descendInto(emphasis)
        print(emphasisMarker, for: emphasis)
    }

And then adding more tests to make sure that combination emphasis works as expected.
This way, we don't have to worry about semantics surrounding mixed emphasis markers. Even though we correctly parse the mixed result, it will look better in the rendered output to have these mixed emphasis spans use the same marker, even if we've been given separate emphasis markers.

I feel like combined emphasis and strong emphasis should all be rendered with the strong emphasis marker

I think this would be unexpected behavior. When the strong emphasis marker and normal emphasis marker are both set, the former should be used for strong emphasis, and the latter should be used for normal emphasis.

This way, we don't have to worry about semantics surrounding mixed emphasis markers. Even though we correctly parse the mixed result, it will look better in the rendered output to have these mixed emphasis spans use the same marker, even if we've been given separate emphasis markers.

Personally, I would still prefer my output to use different strong and normal emphasis markers even when they are both in use. I think this PR shouldn't include special cases where it diverges from the behavior one would expect when specifying two different emphasis markers

Unless there are any other concerns, would it be possible to merge this?

+1. cc @QuietMisdreavus


feat: nicer formatting for fill in the blank challenges

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Before:

After:

In order to make use of the changes in this PR, the text in the ## --sentence-- section will need its backticks removing.

I see this on the challenges:

Is the idea that we would not put the sentences in backticks?

@naomi-lgbt isn't it possible to hide the strings?
If not, it should be possible to leave them in backticks in the markdown, but strip them before rendering.

Not in a reliable way, in this case.
I have a couple of options for hiding strings:

Hide based on the context (e.g. this is a code tag, this is a front-matter string)
Hide based on string content (I can hide a specific string, for example).

Hiding the strings in a section gets trickier, because I can't reliably assert that the order of the strings returned in Crowdin is the order of the strings in the document.

Alright, that makes sense.
It sounds like pulling the text out of the code blocks is going to be the easiest one to pull off, so I'll try to implement that.

pulling the text out of the code blocks is going to be the easiest one to pull off

🤦 That was probably the way to go in the first place - instead of trying to add them

Okay, I think this does the trick.
Since it's not so obvious that you're doing something wrong, I added a few error messages to help people fix their .md files.
I still need to add the source .md files, (so people can see where the ast files came from), but otherwise this is good to go.

Were you planning to add that on this PR @ojeytonwilliams? Or save it for another?

Sorry, Tom, I meant the files like tools/challenge-parser/parser/fixtures/with-fill-in-the-blank-bad-paragraph.md. I added them in the last commit, so I think it's good to go.

oh, yea I should have seen that 👍


Support AWS resource: aws_iam_group_policy_attachment

Description
Add AWS support for aws_iam_group_policy_attachment (TF)

This issue has been referenced in the v0.31.1 release.


Define maximum message sizes to avoid DoS on the network layer

See https://github.com/fedimint/minimint/pull/145#issuecomment-1162124392

Might be relevant for people thinking about the issue: https://github.com/rust-bitcoin/rust-bitcoin/blob/97c680db8cc34cfb7b80c3f95a1ac40dacc15a1d/src/consensus/encode.rs#L322

What's the status on this one?

@elsirion What's the status on this one?

TODO, needs research for correct bounds and changes in a lot of other places to not accidentally break consensus.
An easier first step would be to limit user input (e.g. max tx size etc.). That would protect against users but not other guardians. Next step would be deriving network message size bounds from these limits to also protect against other, malicious guardians.

Stale, old, and alephbft already has a max citem size.


Improve the Initialization of RxUI

The Initialization of RxUI is a bit clunky at the moment
https://github.com/reactiveui/rfcs/issues/14
Implement a change around the discussion in the RFC.

Ana came up with a point that at the moment on the platforms it works it works.
On the original RFC there was the following comment

So instead of something like options.UseDefaults() we would add some additional verbosity by splitting options out into their own functions?
Like
RxUIOptions options = new RxUIOptions();
options.UsePlatformSchedulers();
options.UsePlatformBindingConverters();
options.UsePlatformActivationForViewFetcher();
// etc..
Presumably the equivalent to options.UseDefaults() is simply RxApp.Start()? So what's the difference between this:
RxApp.Start(new RxUIOptions());
and this:
RxApp.Start();
or even this:
RxApp.Start(null);
Is the first just an "empty" RxApp whereas the second is an RxApp with all of the default platform registrations? (and the last is an ArgumentNullException?) I think if that's the case we might want to look at something like RxApp.StartDefault() instead of RxApp.Start() just to help make the behavior less surprising.
Also, would we be able to call RxApp.Start() multiple times with different options? What sort of bugs would we run into if that was supported? I would like to be able to call Start() multiple times so I can use different options for different unit tests, but calling Start() twice in a normal application seems like something that we probably don't want to support.

Just thinking we'd probably want to take advantage of the Target Framework where we can with a generic "Start()", maybe we can make this a extension method against our NuGet packages.
Also our error messages have to be really consistent if we are in a non-initialized state if possible since at the moment the users really have to hunt the documentation.

I think the over all plan is to give the flexibility of some of the .NET Core Startup concepts, but keep a simple RxApp.InitializeWPF() option.  This would institute a huge breaking change and for consumers that go from not having to do anything to initialize ReactiveUI to having to provide an entire Startup file might feel overwhelming.  So providing a default init method per platform that gives you OOTB what you get today is ideal.

I know this is an old thread, but do we have an eta on delivering this?
I think it preferable to have an init() method implemented rather than having to click continue 3 or 4 times for FileNotFoundException every time I start an app with CLR exception management turned on.
As an aside - I tried just unchecking the System.IO.FileNotFoundException (or adding a condition for ReactiveUI.dll) - but this doesn't seem to work :( (VS for Windows)

Use https://github.com/reactiveui/ReactiveUI/blob/fa25c488d4997f75d2c034e17b240ecbb549a65a/src/ReactiveUI/PlatformRegistrationManager.cs#L25 before any other call to RxUI and register the platforms you are using.

Thanks @glennawatson
We're using Forms, and I've registered it as suggested:
PlatformRegistrationManager.SetRegistrationNamespaces(RegistrationNamespace.XamForms);
The result, however, is that it still moans about trying to find XamForms (but at least it doesn't about the other platforms :) )

Also, this seems to happen when running the iOS project, but I'm not seeing it when running Android.

This fixed the issue for me in my MAUI project(targeting net8.0-windows10.0.19041.0), I just called this before creating a new page:
PlatformRegistrationManager.SetRegistrationNamespaces(RegistrationNamespace.Maui);


add new data-driven test suite + move all existing tests to it

This change moves us over to a data-driven test suite and moves all existing tests over to it.
The basic idea is that instead of writing a bunch of DOM mocking code like we used to, we now just create a test by performing some Vecty actions and the DOM operations are recorded to a file. We keep the file of wanted DOM operations around, and they are compared.
For example, TestSetTitle used to look like this:
func TestSetTitle(t *testing.T) {
	titleSet := ""
	document := &mockObject{
		set: func(key string, value interface{}) {
			if key != "title" {
				panic(fmt.Sprintf(`expected document.set "title", not %q`, key))
			}
			titleSet = value.(string)
		},
	}
	global = &mockObject{
		get: map[string]jsObject{
			"document": document,
		},
	}
	want := "foobar"
	SetTitle(want)
	if titleSet != want {
		t.Fatalf("titleSet is %q, want %q", titleSet, want)
	}
}

The vast majority of this code is setting up a fake JS DOM global, global.get, document, document.set, etc. objects & methods in order to properly check was global.document.title set to the string "foobar"?. It's far too verbose and unreadable for such a simple test. The problem is even worse for larger tests that we have.
Instead of the above, the new test suite makes this test be written just as:
// TestSetTitle tests that the SetTitle function performs the correct DOM
// operations.
func TestSetTitle(t *testing.T) {
	ts := testSuite(t, "TestSetTitle")
	defer ts.done()

	SetTitle("foobartitle")
}

When go test is ran, a new file testdata/TestSetTitle.got.txt is written which looks like this:
global.Get("document")
global.Get("document").Set("title", "foobartitle")

It tells us that first global.Get("document") was called, and subsequently Set("title", "foobartitle") was called on the pointer returned by global.Get("document") originally (that is, the second line does not say that global.Get("document") was called twice).
The test suite also tells you that testdata/TestSetTitle.got.txt does not match (the non-existent) testdata/TestSetTitle.want.txt file and it shows you a nice colored diff and informs you:
    	testsuite_test.go:211: to accept these changes:

    		$ mv testdata/TestSetTitle.got.txt testdata/TestSetTitle.want.txt

If you then run the suggested command and commit the testdata folder changes, the test now succeeds & no regressions can occur here in the future.
Additionally, what the diff stats on GitHub here does not show is that:

1,668 lines of hand-written Go test code have been removed(!)
Only 588 lines of Go code have been added to build this new test suite.
493 lines of automatically generated testdata/**.want.txt files have been added.

I think that this new test suite will substantially help in our goal to achieve 100% test coverage (#168) because adding a new test requires no more mocking. Just perform some Vecty actions in the Go test code, run go test from the command line, confirm the DOM operations look correct &  follow the instructions when prompted. 😃
Note: I will merge this change not as a squash commit, because it is in logical commits & is useful to see how each individual test was migrated over to the new test suite.
Helps #168
/cc @pdf (and @shurcooL who may find this to be an interesting/cool simplification :) )

This is awesome.

This change looks generally well received (two hearts + 1 good comment), and only affects our test suite so I will merge it now. Plus, it's blocking some other changes I have in the pipeline like https://github.com/gopherjs/vecty/pull/180.


Widget doesn't show up for the first time when s user tries to access the site

We have noticed that the widget did not show up for the first time in any of the test branch servers. We were able to get the widget only by appending #ALWAYS_SHOW_BFTN_WIDGET to the url.

Past widgets were set up to only fire on the day of action. If you clear cookies and set your computer's clock to July 12, does the widget display as expected?
Sent from my iPhone

On Jul 7, 2017, at 05:21, vsraghavan89<EMAIL_ADDRESS>wrote:
We have noticed that the widget did not show up for the first time in any of the test branch servers. We were able to get the widget only by appending #ALWAYS_SHOW_BFTN_WIDGET to the url.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Per email, this is has been resolved - setting a custom date in _bftn_options is another option for testing.


Add support for npm engine override

a la https://github.com/heroku/heroku-buildpack-nodejs and documented here: https://devcenter.heroku.com/articles/nodejs-support#specifying-an-npm-version

@tonycoco it would be great if this repo got pulled back in sync with https://github.com/heroku/heroku-buildpack-nodejs (or if that project had the right before/after hooks to support your layered customizations). In the mean time, this PR gets me back up-n-running since node 0.12 version of npm is broken for private repo dependencies.

Planning on refactoring this soon to align with the NodeJS buildpack, so yeah... I'll make sure this feature sticks around. Thanks!


Conversion from valarray to json fails to build

There seems to be a regression from 2.0.8 and 2.1.1. This no longer compiles.
std::valarray<double> v;
nlohmann::json j;
j["test"] = v;

P.S. Is there any chance we can get a release with std::vector fix released?

Oops, this is due to the has_iterator traits that check for a iterator type alias, which valarray doesn't provide. Sorry about that.
namespace nlohmann
{
template <typename T>
struct adl_serializer<std::valarray<T>>
{
  static void to_json(json &j, std::valarray<T> const &v)
  {
    detail::external_constructor<detail::value_t::array>::construct(j, v);
  }

  static void from_json(json const &j, std::valarray<T> &v)
  {
    // checks omitted, not the best implem, never played with valarray myself
    auto arr = j.get<std::vector<T>>();
    v = std::valarray<T>(arr.data(), arr.size());
  }
};
}

As for the bug fix release, I don't know what @nlohmann thinks about it.

We need to fix this and add std::valarray support for the 3.x.x release. I did not plan to create a bug fix release for this.

Fixed with 9fd031b.


Image compression library

Change from imagemin to ReCompress.
https://github.com/ArcaneDigital/recompress

For the time being this blocked until https://github.com/ArcaneDigital/ReCompress/issues/1 is complete


[folder-refactor] pylon and end-to-end-test refactor + fix promethus service delete path bug

Coverage decreased (-19.6%) to 51.958% when pulling 74b8949c3fa6da60ac515d734dbf315961afc8dd on canwan/pylon_refactor into d860338876259ac4ecc45d42bb40041b217c33ef on folder-refactor.


Support 2.5.32 version

I changed these 2 files (download URL checked, sha256 computed after downloading .exe file), hope this is enough.
Regards

Thank you for your PR!
Yes, in theory that should be enough. Did you already run this through the chocolatey testing environment?

Thanks for committing this PR. I have made some unitary tests before, I don't know how to use "the chocolatey testing environment"... Will try it next time ...


out of memory (gcn)

Hi,
Nice work.
When training the searched model on ModelNet40 (using the provided command, and trained the model on one Tesla v100), the error occurs. What is the batchsize you used? And other parameters?
Thanks.

Hi @visionman67 .
Did you use Tesla V100 32G or Tesla V100 16G? We used Tesla V100 32G to train the large model.
If you suffer from Out of Memory (OOM) issue, you can train a compact model by runing:
python main_modelnet.py --phase train --arch Cri2_ModelNet_Best --num_cells 3 --init_channels 128 --k 9 --save Cri2_modelnet40_best_l3_c128_k9
or reduce to batch size from 32 to 16 or even 8.

Thanks for your quick reply. It indeed is 16G. Thanks for your advice so
much.
Best
Guohao Li<EMAIL_ADDRESS>于2020年5月11日周一 下午9:55写道：

Hi @visionman67 https://github.com/visionman67 .
Did you use Tesla V100 32G or Tesla V100 16G? We used Tesla V100 32G to
train the large model.
If you suffer from Out of Memory (OOM) issue, you can train a compact
model by runing:
python main_modelnet.py --phase train --arch Cri2_ModelNet_Best
--num_cells 3 --init_channels 128 --k 9 --save
Cri2_modelnet40_best_l3_c128_k9
or reduce to batch size from 32 to 16 or even 8.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lightaime/sgas/issues/5#issuecomment-626656125, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APLWXDHKVJ7FYDXPIK44OQLRQ7RRJANCNFSM4M5Z2O4Q
.


Replace gdk_pixbuf_new_from_inline() with gdk_pixbuf_new_from_resource()

Following the instruction of
https://developer.gnome.org/gdk-pixbuf/2.31/gdk-pixbuf-Image-Data-in-Memory.html#gdk-pixbuf-new-from-inline,
replace the deprecated function gdk_pixbuf_new_from_inline() with
gdk_pixbuf_new_from_resource() to make use of GResource.
To do this,

Restore icon image files from the icon data inlined in
pixmaps/stock_icons.h, and place them in the directory pixmaps.
Add an XML file which enumerates those icon files.
Modify the build system to use glib-compile-resources(1) to create a C
file from the XML file.  The C file is used to incorporate the
information of the XML file into the Vim source.
Modify the implementation of gui_gtk_register_stock_icons() in
gui_gtk.c so that it will use the GResource facility.
The last two modifications are made enable only if gdk-pixbuf >= 2.32;
otherwise, the current implementation is used.

Hopefully, this PR gives one of the ways to fix the issue raised by Tony Mechelynck, e.g., https://groups.google.com/forum/#!topic/vim_dev/MLL4NhDWuGc
Best regards,
Kazunobu Kuriyama

Kazunobu Kuriyama wrote:

Following the instruction of
https://developer.gnome.org/gdk-pixbuf/2.31/gdk-pixbuf-Image-Data-in-Memory.html#gdk-pixbuf-new-from-inline,
replace the deprecated function gdk_pixbuf_new_from_inline() with
gdk_pixbuf_new_from_resource() to make use of GResource.
To do this,

Restore icon image files from the icon data inlined in
pixmaps/stock_icons.h, and place them in the directory pixmaps.
Add an XML file which enumerates those icon files.
Modify the build system to use glib-compile-resources(1) to create a C
file from the XML file.  The C file is used to incorporate the
information of the XML file into the Vim source.
Modify the implementation of gui_gtk_register_stock_icons() in
gui_gtk.c so that it will use the GResource facility.
The last two modifications are made enable only if gdk-pixbuf >= 2.32;
otherwise, the current implementation is used.

Hopefully, this PR gives one of the ways to fix the issue raised by Tony Mechelynck, e.g., https://groups.google.com/forum/#!topic/vim_dev/MLL4NhDWuGc

Thanks, that is quite a big change.  Will this still work with older GTK
versions?
--
Microsoft says that MS-Windows is much better for you than Linux.
That's like the Pope saying that catholicism is much better for
you than protestantism.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Will this still work with older GTK versions?

Yes, it will.
With the current implementation, the GUI obtains icon data through GtkIconFactory, and the latter gets them through GtkIconSet.
GtkIconSet only knows icon data in the form of GdkPixbuf, and therefore needn’t know where the original data come from and how they are converted into GdkPixbuf data.
IOW, for the GTK layer, it doesn’t matter which function, *_from_inline() or *_from_resource(), is used.
This PR honors that wonderful indirection mechanism, which makes it GTK-version independent.

Updated.
In addition to minor fixes and changes, there’s a substantial change in this update.
By default, glib-compile-resources yields C source code making use of __attribute__((constructor)) and __attribute__((destructor)) (and the equivalent for Windows) to automatically register and unregister GResource, respectively.
Obviously, the code won’t be compiled in case the compiler to be used doesn’t support those attributes, although the GResource manual says the default code is OK for Linux, OS X and Windows.
With this update, the option --manual-register is passed to glib-compile-resources and some code is added to gui_gtk_x11.c to register and unregister GResource manually, so that the code automatically generated by glib-compile-resources can be compiled on platforms other than Linux, OS X and Windows.


embeds_one with multiple schemas

I have one column named especifications of type :map, but i want store different attributes like:
Examples below: Model(attributes: possible values)

Parent model:
Offer(offer_type: 'static' or 'video' )

Children models:
Offer.Static(title, content)
Offer.Video(title, video_url, provider)

The model Offer just accept one struct as param:
embeds_one :especifications, YodelJobs.Offer.Static

I searched but wont find any solutions without put all attributes in just one schema, has some way to setup this without put one more column or add all attributes in same schema ? I post here because maybe could turn on a feature.

I believe you can implement it today as a custom type. You lose some of the
embeds conveniences but you gain flexibility (which is what you want).
On Friday, September 16, 2016, Marcelo Oliveira<EMAIL_ADDRESS>wrote:

I have one column named especifications of type :map, but i want store
different attributes like:
Examples below: Model(attributes: possible values)
Parent model:
Offer(offer_type: 'static' or 'video' )
Children models:
Offer.Static(title, content)
Offer.Video(title, video_url, provider)
The model Offer just accept one struct as param:
embeds_one :especifications, YodelJobs.Offer.Static
I searched but wont find any solutions without put all attributes in just
one schema, has some way to setup this ? I post here because maybe could
turn on a feature.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/elixir-ecto/ecto/issues/1698, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAlbuIsTinCbedl0_QAcNquMfYXQGkXks5qqu52gaJpZM4J_RTL
.

--
José Valim
www.plataformatec.com.br
Skype: jv.ptec
Founder and Director of R&D

Right, in this case so i preferred not use embeds_one but create the schemas separated without the association, so i just convert when i needed, because is a few cases. The return of json object itself should be enough for most of cases.
Thanks much by now =).

I've a similar issue. I want to associatiate a list of different schemas with my projects. Something like [%Image{}, %Vimeo{}, %Image{}, %Issuu{}, %Image{}]. I cannot figure out how I would do that with ecto.

@LostKobrakai you can store it in a map field and just keep it as a key-value with a type field, such as type: "vimeo". If you really want to convert it to %Vimeo{} and so on, you can use implement a custom type that checks for the type field on load and convert to the proper struct, and dumps the structs back with the type field when necessary.

I got the first part, but creating a custom type seems not to be as straight forward when being used as part of embed_many. It doesn't seem to use load/1, but rather errors because the type does not implement struct on it's own.
Would such a custom type need to handle the whole list, or could it only handle each item and it's conversion?

You cannot use it as an embed at all. Rather a regular field of type
{:array, CustomType}.
--
José Valimwww.plataformatec.com.br
http://www.plataformatec.com.br/Founder and Director of R&D


Cannot access database on the main thread

name: 'Android Basics: Introduction to Room and Flow issue template'
about: 'Cannot access database on the main thread.'
title: 'Android Basics: Introduction to Room and Flow'
labels: ''
assignees: ''

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-intro-room-flow?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-5-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-intro-room-flow#7
In which task and step of the codelab can this issue be found?
8 - 4. (really  9, also bad numbers on indexes)Finally, to update a list view, call submitList(), passing in the list of bus stops from the view model
8- 11 Then configure the recycler view in onCreate(). This time you just need to pass in an empty block (function) with {}. You don't actually want anything to happen when rows on this screen are tapped.
Describe the problem
these lines  code
busStopAdapter.submitList(viewModel.scheduleForStopName())
busStopAdapter.submitList(viewModel.fullSchedule())
java.lang.IllegalStateException: Cannot access database on the main thread since it may potentially lock the UI for a long period of time.
no sure but need to run it on corouitines? (only that way i make it work)
also the onCreate() of 8 - 11 (onViewCreated)
Steps to reproduce?
complete the codelabs to the poit 8 inclusive 6/12 inclusive
Versions
_Android Studio version:_4.2.1
API version of the emulator: 28
Additional information

@raulhaag
Were you able to find any solution for this problem. I am facing the exact same problem and cannot resolve it.

@tnahata try to go through this codelab. Maybe, you will find an answer there (https://developer.android.com/codelabs/android-room-with-a-view-kotlin#0)

@raulhaag
I had this issue as well but it is resolved after completing the next step (9) in the codelab. There we add coroutine scopes around the busStopAdapter.submitList calls.

Sure it's resolving on next step, cuz you adding there a coroutine when accessing database
Soz you have to add something like this:
in viewModel
    suspend fun fullSchedule(): List<Schedule> = withContext(Dispatchers.IO) {
        scheduleDao.getAll()
    }

    suspend fun scheduleForStopName(name: String): List<Schedule> = withContext(Dispatchers.IO) {
        scheduleDao.getByStopName(name)
    }

in  fragments:
        lifecycleScope.launch {
            busStopAdapter.submitList(viewModel.fullSchedule())
        }
        lifecycleScope.launch {
            busStopAdapter.submitList(viewModel.scheduleForStopName(stopName))
        }

Thanks to all that trying to help me, but i only opened this issue to inform about it and the team in charge correct it, i make it in a similar way described by @pentiux

and on the step 9 when there is error in the collect function. We need to also add the
import kotlinx.coroutines.flow.collect
in the top of the file also to fix that problem. The error message is misleading, for more info we can find in here:
https://stackoverflow.com/questions/65559153/is-kotlin-flows-collect-is-only-internal-kotlinx-coroutines-api

Thanks a lot, friends!
I am facing that problem and I don't know what to do.
Now I realized to continue the code-lab section 9.

Thanks for pointing this out @raulhaag , and thanks to everyone chiming in with possible solutions!
The fix is indeed mentioned in a later step, but that does cause a confusing experience if you're following the codelab step by step and trying to run the app after each step. We'll be improving the instructions for the codelabs so that this issue doesn't appear if you try launching the app immediately after Step 8.

This has now been fixed, thanks for filing!
As a temporary solution to ensure the app can run after the initial step, we use GlobalScope which is later replaced with lifecycleScope