Comments missing from Sheet

Hey,
I do have an issue with a document.
It does contain v- this in sheets4.xml.rels but it has no relationship for the comments%d.xml
<Relationship Id="rId4" Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/vmlDrawing" Target="../drawings/vmlDrawing2.vml"/>

I open this file with excelize it sets LegacyDrawing to this relationship for sheet4 (the sheet does not contain any comments yet).
I add a comment to sheet4 cell doesn't matter
xl/comments%d.xml gets added to file list containing the correct data
since LegacyDrawing is already set the comments relationship is not added to the sheets relationships
I save the file to disk
As expected excel warns me about a corrupt file and that some comments could not be displayed.

I guess there needs to be another check to see if relationships contains a valid reference to the a comments.xml for sheet x.
Btw. the source file is not considered corrupt by excel.
Libreoffice silently ignores the issue and the comments are missing there, too.
If you need more info please feel free to contact me.

Thanks for your issue. Please provides file attachments and code if you can.

I'll try to create new files reproducing the issue tomorrow. I cannot provide these files due to their contents.

I was not able to figure the exact issue out.
But I could construct a similar file structure (by hand) that reproduces the issue I have with a valid file.
You cannot open and save this constructed example since it will be fixed by that.
Somehow the real file I cannot share has some additional stuff I can't seem to find, since saving that file won't fix the issue.
Nonetheless you should be able to see the problem with your current approach in AddComment.
I hope a fix to this issue, fixes it for the other file, too.
issue228.zip

Could you provide the xlsx file that not add the comment, and tell me to add the comment to which cell will missing. I will try to reproduce this case and find fix it.

Hey,
the xlsx file is included in the link i posted in the last message.
Just try to add a comment to any cell in the second sheet named Why is this so sheety.
It will not show up.

Sorry for my so late reply, the spreadsheet in the attachment is already corrupted, did you mean open an existing corrupted document and resave it? if not please provide the source file which can be open by Excel application normally. A few years later, some API has been changed in the later version, so I'm not sure if this issue still goes, I'll close this issue, if you have any questions, code, and attachments to reproduce this issue, please let me know, and reopen this issue at any time.


Can't see icons in React Native v0.57.3

Environment
Icons works in    react-native: 0.57.0
Does not works in react-native:  0.57.3  Which current version

Description
I have 2 app totally same but react-native versions.
I can't see my icon in the new version of react native.
Reproducible Demo
Upgrade your project 0.57.0 to 0.57.3,
I upgraded my React native project because of Xcode 10.

I'm sorry, It was a Navigation Element issue. Now it works  properly. I can't find way for delete the issue. Thank you


[FEAT] Sensor configuration

Is your feature request related to a problem? Please describe.
I want the ability to enable or disable the different sensors.
Describe the solution you'd like
Make config.json actually use the enable: true/false values.
Describe alternatives you've considered
Additional context
This is blocking #4

Closed by https://github.com/muniter/halinuxcompanion/commit/fa52de3a9125d3e4c4437a6d1e44a94676440fd0


⚠ Bofrost.at has degraded performance

In 4986992, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1583 ms

Resolved: Bofrost.at performance has improved in 893c671 after 36 minutes.


Upgrade Jena from version 2.13.0 to 4.4.0. Upgrade Java to version 11.

Upgrade Jena to the newest version and upgrade Java along with it to version 11.
It compiles successfully, the Dockerfile builds successfully and it also runs successfully when tested like docker run --network="host" lodview and opening http://localhost:8080/lodview/Berlin.
However I still recommend another manual test by someone else.

Is there anything I can do to help getting this merged?


Trigger ArtifactHub update

Signed-off-by: Michael Mattsson<EMAIL_ADDRESS>

Not needed.


getButtonProps() returns different result locally and in production

downshift version: 1.22.5
node version: 8.9.4
npm version: 5.6.0

Problem description:
In a project I am working on there is a discrepancy between the output of getButtonProps() when I run the project locally and when it is in production. The element that is created with downshift has "type": "button" when in production but when it is run locally it does not have that property.
Relevant code or config
Output of getButtonProps():

local with npm start:

{
  "role": "button",
  "aria-label": "open menu",
  "aria-expanded": false,
  "aria-haspopup": true
}

built and deployed:

{
  "type": "button",
  "role": "button",
  "aria-label": "open menu",
  "aria-expanded": false,
  "aria-haspopup": true
}

Do you have any hints where I could start looking for the root of that problem?

Hi @HansWurst90!
Make sure that you're using the same version locally that you are in production. A recent release added type: "button".
I'm going to bet that's the issue. If  you want it to have a different type, then you can do: getButtonProps({type: 'submit'})
I'll go ahead and close this.

I'm going to bet that's the issue.

You won that bet 😄 .
getButtonProps({type: null}) helped me to get the same result as before.
Thanks a lot!

Thanks! Sorry for the breaking change. I didn't expect anyone actually wanted the button to have a type of submit so I considered it a bug.


redirect ibm distribution docs to new website

This PR redirects the "Kubeflow on IKS" docs to their new external website as part of https://github.com/kubeflow/website/issues/3074
The link to the new website was already added to the "installing kubeflow" guide in PR https://github.com/kubeflow/website/pull/3469.

@jbottum @zijianjoy @james-jwu I think this is important to redirect these old docs to the new website.
I am trying to close out https://github.com/kubeflow/website/issues/3074 to make the website actually clear about how to get Kubeflow installed (especially with all the new eyes about to look after the CNCF adoption).

/lgtm
Tommy and I will update the index page in a separate PR.

@zijianjoy @james-jwu one of you will need to approve because I have updated redirects.

@zijianjoy since we have approval from @yhwang can you please approve this (as only you can do it).

/lgtm
/approve
The content/en/_redirects change can probably be improved for mapping the current subpage to the ibm corresponding page. But will let @yhwang to fix that in future PR.


GlobalConfig: BudgetReportConfig + SNS Topics- inconsistent documentation / functionality

Describe the bug
The BudgetReportConfig object has an attribute subscriptionType, which states :

The type of notification that AWS sends to a subscriber.
An enum value that specifies the target subscription type either EMAIL or SNS

While the config validator says the subscription will fail validation:
<EMAIL_ADDRESS>To Reproduce
global-config.yaml
snsTopics:
  deploymentTargets:
    organizationalUnits:
      - Root
  topics:
    - name: Security
      emailAddresses:
        -<EMAIL_ADDRESS>
  budgets:
    - deploymentTargets:
        accounts:
          - Management
      name: accel-budget-management-account
      timeUnit: MONTHLY
      .... # removed for brevity
      notifications:
        - type: ACTUAL
          thresholdType: PERCENTAGE
          threshold: 100
          comparisonOperator: GREATER_THAN
          subscriptionType: SNS
          address: Security

Expected behavior
reports.budgets clarification:
Ability to publish budget alerts to SNS topics OR corrected documentation
snsTopics clarification
Further clarity on how the global-config: snsTopics is leveraged. https://docs.aws.amazon.com/solutions/latest/landing-zone-accelerator-on-aws/amazon-sns-topics.html does not explain this attribute in detail:

1 Topic in LogArchive (as I may have seen) or many topics in the deploymentTargets
How to target with cloudwatch alarms. AlarmConfig example shows snsAlertLevel (deprecated)

Please complete the following information about the solution:

[x] Version: development/1.4.3

[x] Region: ap-southeast-2

[ ] Was the solution modified from the version published on this repository?

[ ] If the answer to the previous question was yes, are the changes available on GitHub?

[ ] Have you checked your service quotas for the sevices this solution uses?

[ ] Were there any errors in the CloudWatch Logs?

Screenshots
❯ yarn validate-config /Users/richardkeit/git/versent/my-lza

yarn run v1.22.19
$ ts-node<EMAIL_ADDRESS>/Users/richardkeit/git/my-lza
2023-07-21 16:37:36.530 | info | config-validator | Config source directory -  /Users/richardkeit/git/my-lza
2023-07-21 16:37:36.541 | info | accounts-config-validator | accounts-config.yaml file validation started
2023-07-21 16:37:36.541 | info | global-config-validator | global-config.yaml file validation started
2023-07-21 16:37:36.542 | info | global-config-validator | email count: 1
2023-07-21 16:37:36.542 | info | iam-config-validator | iam-config.yaml file validation started
2023-07-21 16:37:36.543 | info | network-config-validator | network-config.yaml file validation started
2023-07-21 16:37:36.545 | info | organization-config-validator | organization-config.yaml file validation started
2023-07-21 16:37:36.546 | info | security-config-validator | security-config.yaml file validation started
2023-07-21 16:37:36.546 | warn | config-validator | Config file validation failed !!!
2023-07-21 16:37:36.552 | warn | config-validator | global-config.yaml has 1 issues:
Invalid report notification email Security.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Additional context
Add any other context about the problem here.

I saw that from v1.5.0 it's now possible to put a SNS ARN on the configuration https://github.com/awslabs/landing-zone-accelerator-on-aws/commit/6a99ccbcc5e06f9390de56b7725ddb795c6d04d1. However, would it be possible to use global SNS Topics by name as discussed here?


Code refactoring (cgw_cache / cgw_device function naming) +fmt required

Newely pushed changes require formatting enforced + refactoring done to address naming of the functions etc;

@SviatoslavBoichuk

Addressed in https://github.com/Telecominfraproject/openlan-cgw/pull/19


Function to determine padding

Is there any way that I can find out how much padding was added when running runBitPut?

Nothing builtin, no :/


Remove enums from schemas. "token_type" field treated as case-insensitive

This PR removes the enumerations associated with the "grant_type" and "response_type" fields due to the new grant types ("hybrid", etc) and response types ("id_token", "none", etc.) )introduced in the OpenID Connect protocol, as well custom grant types also  being defined.
It also states that the value of the "token_type" field should be case-insensitive, due to some OTS Auth Servers producing a value of "bearer" instead of "Bearer"

Merged

It also states that the value of the "token_type" field should be case-insensitive, due to some OTS Auth Servers producing a value of "bearer" instead of "Bearer"

:+1: That is as per RFC 6749 Section 5.1.


ORION-3575 Fix inconsistencies of interface fulfillment

Some resource.Resouce implementation referred to TransferEndpointResource instead of an actual resource defined in a file with a type assertion. This is fixed.
In README.md, extra $ signs are removed from bash scripts.

Sharp eye! Thanks.


Audit of API docs changes notes against central changelog (feature levels 1-27)

Unless otherwise noted, each entry just needs Changes note(s) added to API documentation:
Feature level 1:

[ ]  POST /register: Added zulip_feature_level to the response if zulip_version is among the requested event_types.
[ ] GET /api/v1/user_uploads: Added new endpoint for requesting a temporary URL for an uploaded file that does not require authentication to access (e.g. for passing from a Zulip desktop, mobile, or terminal app to the user's default browser).
[ ] Added EMAIL_ADDRESS_VISIBILITY_NOBODY possible value for email_address_visibility.
[ ] Added private_message_policy realm setting.
[ ] muted_topic objects now are a 3-item tuple: (stream_id, topic, date_muted). Previously, they were a 2-item tuple.
[ ]  GitLab authentication is now available.
[ ] Added None as a video call provider option.

Feature level 3:

[ ]  zulip_version and zulip_feature_level are always returned in POST /register; previously they were only returned if event_types included zulip_version.
[ ] Added new presence_enabled user notification setting; previously presence was always enabled.

Feature level 4:

[ ] jitsi_server_url, development_environment, server_generation, password_min_length, password_min_guesses, max_file_upload_size_mib, max_avatar_file_size_mib, server_inline_image_preview, server_inline_url_embed_preview, server_avatar_changes_disabled and server_name_changes_disabled fields are now available via POST /register to make them accessible to all the clients; they were only internally available to Zulip's web app prior to this.

Feature level 5:

[ ] GET /events: realm_bot events, sent when changes are made to bot users, now   contain an integer-format owner_id field, replacing the owner   field (which was an email address).

Feature 6:

[ ]  GET /events: realm_user events to update a user's avatar now include the avatar_version field, which is important for correctly refetching medium-size avatar images when the user's avatar changes.
[ ] GET /users, GET /users/{user_id}: User objects now contain the avatar_version field as well.

Feature 7:

[ ]  GET /events: realm_user and realm_bot events no longer contain an email field to identify the user; use the user_id field instead.  Previously, some (but not all) events of these types contained an email key in   addition to to user_id) for identifying the modified user.
[ ] GET /events:  realm_user events sent when a user's role changes now include role property, instead of the previous is_guest or is_admin booleans.

Documented as feature level 8, but listed in changelog as feature level 7

[ ]  PATCH /users/{user_id}: The is_admin and is_guest parameters were removed in favor of the more general role parameter for specifying a change in user role.

Feature level 10:

[ ]  GET users/me: Removed client_id and short_name from the response to this endpoint. These fields had no purpose and were inconsistent with other API responses describing users.

Feature level 11:

[  ]  POST /register: The response now contains a is_owner, similar to the existing is_admin and is_guest fields.

Inconsistent or incomplete: Added to GET /events as well and null information not documented:

[ ]  POST /register: Added realm_community_topic_editing_limit_seconds to the response, the time limit before community topic editing is forbidden.  A null value means no limit. This was previously hard-coded in the server as 86400 seconds (1 day).

Documented as feature level 11 but listed in changelog as feature level 12

[ ]  GET users/{user_id}/subscriptions/{stream_id}:
New endpoint added for checking if another user is subscribed to a stream.

Feature level 13:

[ ]  GET /events: delete_message events have new behavior. The sender and sender_id fields were removed, and the message_id field was replaced by a message_ids list for clients with the bulk_message_deletion client capability. All clients should upgrade; we expect bulk_message_deletion to be required in the future.

Feature level 14:

[  ]  GET users/me/subscriptions: Removed the is_old_stream field from Stream objects. This field was always equivalent to stream_weekly_traffic != null on the same object.

Feature level 16: Question: unlike other parameters / return values that have been removed from endpoints, this was removed as a whole concept from Zulip. So do we want a Change note for this in the main endpoint description?

[  ]  GET /users/me: Removed pointer from the response, as the "pointer" concept is being removed in Zulip.

Feature level 19:

[ ]  GET /events: subscriptions event with op="peer_add" and op="peer_remove" now identify the modified stream by a stream_id field, replacing the old name field.

Feature level 21: NOTE: would document on the PATCH /settings endpoint

[ ]  PATCH /settings/display: Replaced the night_mode boolean with color_scheme as part of supporting automatic night theme detection.

Feature level 26:

[ ]  The sender_short_name field is no longer included in GET /messages.
[ ]  The short_name field is removed from display_recipients in GET /messages.

Feature level 27:

[ ]  The short_name field is removed from display_recipients in POST /users.

Excellent! Looking forward to these fixes.
Skimming a few of these, one thing I notice is that some of them are missing links from the changelog to the endpoint that changed. For example several of the entries you have for feature level 1; and one at FL 2 and one at 22 and a few in between. Those would be nice to fix too; in some cases, like "Added None as a video call provider option.", it's actually not easy to be sure exactly what is said to have changed.
The changelog also has a misformatting at FL 5 that's probably a tiny fix but is kind of confusing as rendered:

Question: unlike other parameters / return values that have been removed from endpoints, this was removed as a whole concept from Zulip. So do we want a Change note for this in the main endpoint description?

[  ]  GET /users/me: Removed pointer from the response, as the "pointer" concept is being removed in Zulip.

Yeah, I'd imagine documenting this in much the same format as any other removed response property.


Bump Kubernetes dependencies to v1.28.0 GA tags

anyone want to pick? if no, i will pick now
/assign


Cobbs Creek - Amenity Missing (Meeting Room)

16211

Updated weight room to "Large Multi-purpose room"


easyTipViewDidDismiss called twice

Hi,
After updating to 0.2.1 i encountered a problem when the delegate easyTipViewDidDismiss(tipView : EasyTipView) called twice.

Fixed in #36

fix released in version 0.2.2


about code

I try to figure out how this code works.But i encountered a bit of confusion. In "guided_diffusion/gaussian_diffusion.py" ,line 276 use "model_output, attn_map = model(x, self._scale_timesteps(t), **model_kwargs, perturb=perturb)" . The model has input parameter perturb. When I read the code of "UNetModel" in guided_diffusion/unet.py, line 890. The parameter perturb seems to corresponds to parameter "drop_attn" in funtion "forword". But I didn't see the parameter "drop_attn" play a role in the function。

Hi, I'm sorry for the late reply. drop_attn is a legacy that I should delete and no longer in use.
The actual perturbation is determined before running the inference.
You can see Line74 in classifier_sample.py runs  replace_attn_layers(model, perturb) and it does the trick by replacing attention processor to perform perturbed-attention.

Thank you for your interest in our work and if you have any further questions feel free to open issue.


patch: bump mockttp from 0.9.1 to 2.0.0

Bumps mockttp from 0.9.1 to 2.0.0.

Release notes
Commits

updated-dependencies:

dependency-name: mockttp
dependency-type: direct:development
update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
Resolves: #
HQ:
See:
Depends-on:
Change-type: major|minor|patch

Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

@balena-ci retest

@balena-ci I self-certify!


feat: Added inline error messaging for text and select input components

TISNEW-4531

Modified the existing components TextInputField and SelectInputField to include components from the NHS React library that support inline error messaging and hint text. https://nhsdigital.github.io/nhsuk-react-components/?path=/story/input--with-error-string

Added option to render multi-line html textarea instead of input field by setting a rows property

Updated error summary in line with NHS React component to improve accessibility through improved labelling.

Added new component, InputFooterLabel to allow insertion of additional text below the form field that supports html markup to allow for inclusion of links.

Added missing label properties to the address form fields on formr part a.

Added hint text to email form field on formr part b, advising on preference for NHS.net email addresses.

Updated version of nhsuk-react-components in package.json. This package update is required in order to render the new components correctly.

Good job mate!
Please check and fix the tests.

nvm.. I updated it. Snapshot had to be updated as we have updated the nhs library which changed the logo code a bit.

Cheers guys. I've been looking into the input field issue that Johno has flagged.
I agree there is an issue with text inputs where the field is pre-populated with data and the length exceeds the width of the input such that the text is hidden. For fields where we might expect the text to exceed the default width, we could simply set the width property on that input. Alternatively, if no width property is set, we could set the width of the field based on the length of the text. My preference is to avoid setting all inputs to full width, which is also inline with recommendations.
The select input appears to work as expected and auto-sizes depending on the width of the longest option label. The issue arises on smaller screens such as mobile whereby the text is truncated. This appears to be unavoidable and is a limitation of the select input type since the text doesn't wrap. To prevent this issue we could either shorten the option label or implement using radio buttons where labels can wrap.


Rich Text WYSIWYG Editor - Design System

What this PR does / why we need it:
Adds a new Rich Text Editor component to the design system.
This component is made with Tiptap npm packages.
Tiptap is a headless wrapper around ProseMirror – a toolkit for building rich text WYSIWYG editors, which is already in use at many well-known companies such as New York Times, The Guardian or Atlassian.
Cons: It does not support markdown as output, the output is html.
Pros:

It does support Markdown shortcuts.
Compatible with what dataverse already handles for rich content, that is html.
Tiptap is headless, that means there is no styling provided so all styles were matched to what the rest of the SPA components look like.

Which issue(s) this PR closes:

Closes #525

Suggestions on how to test this:
Visual code inspection and Storybook story manual testing.
The component has 100% unit test coverage as well.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:

coverage: 97.517% (+0.1%) from 97.385%
when pulling dee7698e4567b644855c22369edc8e3089bd3ced on feat/525-rich-text-editor
into 02bc675bcd35fdf3b33c198622e5e2e53fbfbc9e on develop.

@ChengShi-1 empty lines added 👍🏼 , thanks

Came across one observation - @ChengShi-1 can you confirm this is expected or a bug:
https://646fbe232a8d3b501a1943f3-dvpreauelj.chromatic.com/?path=/story/rich-text-editor--default
Steps to Reproduce:

Navigate to the WYSIWG Editor
Click on Add Link
Add: https://www.google.com/

Issue: After adding the link, nothing happens (link not generated).

Came across one observation - @ChengShi-1 can you confirm this is expected or a bug: https://646fbe232a8d3b501a1943f3-dvpreauelj.chromatic.com/?path=/story/rich-text-editor--default
Steps to Reproduce:

Navigate to the WYSIWG Editor
Click on Add Link
Add: https://www.google.com/

Issue: After adding the link, nothing happens (link not generated).

Hi Omer! After adding a link, you can type your text, and it will appear blue and clickable. Alternatively, you can type the text first, highlight the words, and then attach the link to those words. Picture attached.

Thanks for clarifying @ChengShi-1! - Merging PR


i18n(zh-cn): Update modified-time.mdx

Description (required)
Update modified-time.mdx
Related issues & labels (optional)

#9520
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
recipes/modified-time.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Attribute map name added to radio input name

I encountered an issue when having two properties each with a radio view with the same choice values
ie. ( choices: [ [ true, 'yes' ], [ false, 'no' ] ] )
I did some investigation and saw that we were assigning the name of our radio inputs as the first index in our choices. This presents issues when several properties share the same values since HTML registers them as a group - making only one capable of being selected.
The following changes specifies the name on the radio input if an attributeMap is present.

I fixed the bug with this:
commit 7c033d9ba7a7694a3099c17def6da3fcda8739b8
Author: Kevin Greer<EMAIL_ADDRESS>Date:   Thu Jul 4 10:01:56 2019 -0400
Fix RadioView to set name to be name of Property.


Policy compliance data enable pagination

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.
[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

/azp run automation - sdk

Automation for azure-sdk-for-python

@najagasi , please fix the check failures of avocado. There're many un-referenced example files needs to be removed.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Please do not merge this PR yet

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

"title": "PolicyStatesClient",

Do you need to add PolicyEventsClient for this version?

Refers to: specification/policyinsights/resource-manager/Microsoft.PolicyInsights/stable/2019-10-01/policyStates.json:4 in 03198ee. [](commit_id = 03198eed76a3e7742052629e820ed005fd63a234, deletion_comment = False)

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@raych1
I am getting a breaking change caused by sending a new property nextLink.
This should not be considered as  breaking change as the user behavior will not be changing and the user is additionally provided with a link to retrieve more results.
Can this be considered ?
Also not sure why automation-sdk is failing, will suppressing the breaking change fix it ?
https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/Breaking changes guidelines.md#adding-read-only-field-to-response

@pilor for visibility.

"/{scope}/providers/Microsoft.PolicyInsights/policyEvents/$metadata": {

We removed it from policyStates recently. Please check if it should be removed from events too.

Refers to: specification/policyinsights/resource-manager/Microsoft.PolicyInsights/stable/2019-10-01/policyEvents.json:603 in 1c9ee7f. [](commit_id = 1c9ee7f85f8e9bc82337fa4fdc795ea04c2f411d, deletion_comment = False)

  "description": "The $expand query parameter. For example, to expand components use $expand=components",

might want to mention that results won't be paginated for this expand option?

Refers to: specification/policyinsights/resource-manager/Microsoft.PolicyInsights/stable/2019-10-01/policyEvents.json:1068 in 1c9ee7f. [](commit_id = 1c9ee7f85f8e9bc82337fa4fdc795ea04c2f411d, deletion_comment = False)

@raych1
I am getting a breaking change caused by sending a new property nextLink.
This should not be considered as breaking change as the user behavior will not be changing and the user is additionally provided with a link to retrieve more results.
Can this be considered ?
Also not sure why automation-sdk is failing, will suppressing the breaking change fix it ?
https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/Breaking changes guidelines.md#adding-read-only-field-to-response

@pilor for visibility.

Breaking change cannot be suppressed and needs to be forcibly merged if all other issue are resolved. For SDK Net failure, it can be ignored.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@raych1 this PR is ready to merge from my side, have described the breaking change error that can be ignored in the above comment.

@najagasi , it needs ARM sign off.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@majastrz I have addressed your comment.
Please let me know if other changes are required
thank you

/azp run automation - sdk

@raych1 We have received ARM signoff and branch has the latest commits.
Please let me know If anything else is needed.
thank you

@akning-ms , the breaking change is adding a readonly property nextlink. Could you help force merge this PR?


New package: Prova_ABF v0.1.0

Registering package: Prova_ABF
Repository: https://github.com/Gios89/Prova_ABF
Created by: @Gios89
Version: v0.1.0
Commit: e05fe90f585c06158cde58ebbc8633cd1a596da0
Git reference: HEAD

@Gios89 this seems to be a test package?

Yes, I am just learning.
Il Dom 20 Giu 2021, 12:02 AM Mosè Giordano @.***> ha
scritto:

@Gios89 https://github.com/Gios89 this seems to be a test package?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JuliaRegistries/General/pull/39195#issuecomment-864469098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT23D6OU2GFQ27AKUPFMR6TTTUHYRANCNFSM467E3A5Q
.


Build error on IOS

Hi,
i got error when build on ios: ibrary not found for -lRNLanguages
React-native: 0.58.6
please help.
Thanks

@TuanGiang Please respect the issue template and provide full env details: https://github.com/react-native-community/react-native-localize/blob/master/.github/ISSUE_TEMPLATE.md


fixing misspellings, fixing IneffAssign reported issues

Continuing to fix some of the issues discovered through the GoReportCard.

2 misspellings
all of the in-effectual assignments
also removing encode-perf-rig since codec-perf-rig serves this purpose better

@cmasone-attic PTAL if you don't mind

LGTM

I think some of those ineffectual assigns in perf rig were required to get realistic numbers out of perf rig.

I woudn't be surprised if that were so, to keep the compiler from
optimizing stuff out. If so, then we should leave a comment indicating that
On Thu, Aug 25, 2016 at 9:13 AM Aaron Boodman<EMAIL_ADDRESS>wrote:

I think some of those ineffectual assigns in perf rig were required to get
realistic numbers out of perf rig.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/attic-labs/noms/pull/2436#issuecomment-242446406, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMnImsli5-Tql-WyU56Yz_6SbhN1KrYTks5qjb8QgaJpZM4JtLJJ
.

I am not seeing any noticeable performance difference. I thought the same thing originally - "oh, those assignments (while not being used) are to ensure the code doesn't get optimized away".  If the compiler is smart, it would already be seeing the same thing as IneffAssign and optimizing these calls away even without the code changes. I don't think it can optimize away the IterAll calls which are really all that matters for the perf results. The cost of assigning the variables or calling the callback functions is tiny. I decided to run it with a larger count to still try to tease out any change of performance. The only numbers that should change are in the scan columns - the readList/readSet/readMap calls.  Do you see anything below?
 I can put the assignments back if you are still concerned after reviewing the timing information above.

...huh. I don't see any difference. @aboodman ?

I just vaguely remember this. If the data doesn't show any difference I'm
fine removing them.
On Thu, Aug 25, 2016 at 10:12 AM, cmasone-attic<EMAIL_ADDRESS>wrote:

...huh. I don't see any difference. @aboodman
https://github.com/aboodman ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/attic-labs/noms/pull/2436#issuecomment-242468210, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAE6BKt5_ItZiqn3TL_iZvOE6ZBJQQRqks5qjcz3gaJpZM4JtLJJ
.


Tweak the identity request type

Hey, I just made a Pull Request!
I am doing this in the hope that it will fix some type validation issues when using various versions of express.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

@punkle what's the error that we were getting here with different versions of express?

honestly I am not sure yet. I was noticing some issues, where the adr-backend was returning a different set of types from the createRouter than the backend plugin setup expected. The adr-backend seems to be the only plugin that requires a different set of express deps. I then tried to go about adding resolutions for the express deps, then I started to hit problems with this generic Request type.
Perhaps I am going about this the wrong way. Maybe I can try to resolve the differnces between the versions required by the adr-backend?

Hmm yeah, I'd be a little cautious of merging this - even though it might be fine, would still be good to see what's causing this for reals so we can be on the lookout if this is something that's going to break something else.

Totally agree. Let me close this for the moment. In mean time we configured adr like this:
import { createRouter } from '@backstage/plugin-adr-backend';
import { Router } from 'express';
import { PluginEnvironment } from '../types';

export default async function createPlugin(
  env: PluginEnvironment,
): Promise<Router> {
  const router = await createRouter({
    reader: env.reader,
    cacheClient: env.cache.getClient(),
    logger: env.logger,
  });
  // TODO remove express.Router type casting
  //  We have added this type casting because adr-backend brings in a special version of
  //  the express types. We should remove this type casting when we have fixed the dependencies
  return router as unknown as Promise<Router>;
}


[MWCC]: mwcceppc file path behavior broken

#75 (wibo 0.6.14+) causes issues with mwcceppc paths that worked in previous versions. This causes issues on all Linux environments.
Our setup uses assetrip + assetinc to rip binary assets from the source binaries into build/include/assets/... and we have -i build/include passed into mwcceppc.exe. Since the issue started occurring with wibo 0.6.14, the issue must be these lines: https://github.com/decompals/wibo/pull/75/files#diff-35916b9fc9415b9ed5c6c9e5cb55c16f9c61754053de1ac138aa4456378610dfR685-R691
Example error:
[422/1595] CC build/iconv/src/static/version.c
FAILED: build/src/static/version.o
/opt/devkitpro/devkitPPC/bin/powerpc-eabi-cpp -M build/iconv/src/static/version.c -MF build/src/static/version.o.d -nostdinc -I include -I tools/ppcdis/include -I build/include -I /N64_SDK/ultra/usr/include && wibo tools/1.3.2/mwcceppc.exe -O4 -char unsigned -fp hard -inline on -enum int -sdata 0 -sdata2 0 -d _LANGUAGE_C -d F3DEX_GBI_2 -d NDEBUG -d DEBUG=0 -d MUST_MATCH -nostdinc -proc gekko -maxerrors 1 -Cpp_exceptions off -I- -i include -i tools/ppcdis/include -i build/include -ir /N64_SDK/ultra/usr/include -c build/iconv/src/static/version.c -o build/src/static/version.o
### mwcceppc.exe Compiler:

User break, cancelled...
#    File: build\iconv\src\static\version.c
# -----------------------------------------
#       4: #include "assets/__Creator__.inc"
#   Error:                                 ^
#   the file 'assets/__Creator__.inc' cannot be opened
#   Too many errors printed, aborting program
[434/1595] Order floats config/rel.yml 806432c0 806432c8
ninja: build stopped: subcommand failed.
Dumping dump/forest_1st.arc
Dumping dump/forest_2nd.arc
Error running Ninja build

Thanks for opening the issue, I'll take a look into this and see what I can find out.

Any updates on this?

Have you tried the latest commit?

Have you tried the latest commit?

Unfortunately it did not fix the issue for us. In fact, it appears even more broken than before. Now it can't even find top level include directives. These are in our /include/ directory.
[8052/9273] CC src/static/initial_menu.c
FAILED: build/src/static/initial_menu.o
/opt/devkitpro/devkitPPC/bin/powerpc-eabi-cpp -M src/static/initial_menu.c -MF build/src/static/initial_menu.o.d -nostdinc -I include -I tools/ppcdis/include -I build/include -I ~/n64sdk/ultra/usr/include && wibo tools/sjiswrap.exe tools/1.3.2/mwcceppc.exe -O4 -char unsigned -fp hard -inline on -sdata 0 -sdata2 0 -d _LANGUAGE_C -d F3DEX_GBI_2 -d NDEBUG -d DEBUG=0 -d MUST_MATCH -nostdinc -proc gekko -maxerrors 1 -Cpp_exceptions off -I- -i include -i tools/ppcdis/include -i build/include -ir ~/n64sdk/ultra/usr/include -c src/static/initial_menu.c -o build/src/static/initial_menu.o
### mwcceppc.exe Compiler:

User break, cancelled...
#    File: src\static\initial_menu.c
# ----------------------------------
#       1: #include "initial_menu.h"
#   Error:                         ^
#   the file 'initial_menu.h' cannot be opened
#   Too many errors printed, aborting program

I can confirm that reverting to wibo 0.6.13 fixes both the issues with 0.6.14 and 0.6.15.


Move Jira Issue into GitHub

Reason
Post Consortia Phase is comming so good start to move issues into here
AC

epics should be viewable
all issues are here in GitHub

issues from backlog are usable in GitHub execept some WIP issues that are referencing the current work of our collegues.
Modified Project Board after team discusssion so, should be fine for now.
End of former Tool not clearified


Found a SQL injection issue

Example: http://uoj.ac/problems?tag=1%27%20not%20in%20(select%20tag%20from%20problems_tags)%20and%20id=2;%23

fixed.
Thanks!


default value gets used when given block evaluates to false

So, given this hypothetical scenario (using grape v1.0.1):
params do
  requires :foo, type: Symbol, values: [:a, :b]
  given foo: ->(val) { val == :a } do
    optional :bar, type: Symbol, default: :my_default
  end
end
put do
  binding.pry # Setting a breakpoint to highlight the following examples
end

I get the following when foo is :a, as expected:
> request.url
=> "http://example.com/api?foo=a"
> params
=> {"foo"=>:a, "bar"=>:my_default}

However, when foo is :b, this seems unexpected:
> request.url
=> "http://example.com/api?foo=b"
> params
=> {"foo"=>:b, "bar"=>:my_default}

Reason why I was surprised by this is that the parameters contract says that the default value of :my_default is only relevant when foo is a. Instead, I should be getting the following:
> params
=> {"foo"=>:b}

Is this a known case, or a bug?

Looks like a bug to me. Default-value population is probably not looking at the given constraints.

@darren987469 another one? :)

No problem, I will try it. 😄

@dblock close this?


Properly apply leave-to-class

After a little digging the fix to that warning I found in #2 is pretty simple. Still stumped about the whole slots warning though...

I get the same warning messages in chrome console. Can we merge this in main? Thanks!

I up this PR that can be really usefull. Thanks.

Please merge

You can get rid of the slots warning (Non-function value encountered for default slot) by replacing this:
// VTNotification.vue
[
  this.$slots.default({
    notifications: this.sortedNotifications,
    close: this.close,
  }),
]

with this:
{
  default: () => {
    return this.$slots.default({
      notifications: this.sortedNotifications,
      close: this.close,
    })
  }
}

Sorry guys, missed this PR


Use ksp_version_max instead of ksp_version_min in build script

I'm hoping this alleviates the issue of older versions of MM not being available (and thus causing failures in Jenkins installs). Most recent PR with this issue: #748

In cases where a ksp_ver_min is set but no ksp_ver_max I'd rather it not pass Jenkins so that we can address it manually as part of https://github.com/KSP-CKAN/CKAN-meta/issues/623

So there's 2 sides to this:

We don't want mods using their lowest compatible version as the grounds for their Jenkins test. In the case of #748 it's failing not because there are any errors in the metadata, but rather it's failing because a very old version of a dependent mod is no longer available. We should be using the highest compatible ksp version for testing to assure that it works now. (There's probably a discussion to be had about testing both min and max, but IMO that's a much more complicated issue).

We don't want mods without ksp_version compatibility caps unless they're explicitly set to ksp_version any (ex. flag-only mods). As a convention we tend to use ksp_version_max 1.0.99 when there's nothing suspected that will break a mod as long as no major changes occur, however 1.1 will represent a very major/fundamental change. While Squad will undoubtedly do their best to maintain mod compatibility, no mod should be assumed compatible until it's tested.

@plague006 Thanks for the extra explanation. It barfed on things unrelated to this PR and the change looks correct. Merging with thanks :+1:


Implement a collapsible view using a card view in Android

We ask that you please be patient as our team works through approving and publishing all articles/tutorials in a timely manner. Allow 1-3 days for a topic to be reviewed and/or approved - allow 3-7 days for an articles to be reviewed and/or published.
Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
We're looking for the first 2-3 paragraphs of the article that appropriately summarize what your article will be about.
Proposed title of article
Your title should be descriptive of the article/tutorial. Be Specific. Use keyword research to gain your article higher ranking.
Implement a collapsible view using a card view in Android
Introduction paragraph (2-3 paragraphs):
Please write the Introductory paragraph(s), that would be included in your article. We will use this writing snippet to help us assess overall quality before approval. We're looking for the first 2-3 paragraphs of the article that appropriately summarize what your article will be about.
Take your time and write the content as you would intend to get it published.
In this article, you are going to learn about the card view and how to style and customize it. We will implement a collapsible view that expands to reveal more information and folds when an image in a card is clicked.
A Card View is useful for display data in similarly styled containers and may contain content and actions about a single object.
Similarly, It can display a moderate amount of data in a way that is easy to visualize. It is also particularly useful when you want to present a large number of objects at once within the same summary page.
Key takeaways:
What are the 3-5 most important things the reader should understand or be able to do after reading this article? Use this area to get your ideas down on the bulk of your article or tutorial.

Explore the card component in android
Learn how to style card views.
Set and respond to click listeners.
Learn how to add vector assets to a project in android studio.
Learn how to constrain and group views with constraint layout.

References:
Please list links to any published content/research that you intend to use to support/guide this article.

https://material.io/components/cards

Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

@Lamouresparus
Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

@Lamouresparus
Sounds like a helpful topic - lets please be sure it add value beyond what is in the official docs and what is covered in other blog sites.
Please be sure to double check that it does not overlap with any existing EngEd articles or incoming topic suggestions (if you haven't already) to avoid any potential article closure, please reference any relevant EngEd articles in yours. - Approved

@Lamouresparus
Just pinging you on this topic form - as I'm making some room in the topic queue.
No rush if you're still working on this one - if you need more time we can always re-open at a later date.


Add Html and css files

Correctly installed lighthouse, and removed the errors
Create index.html
Create style.css
Add images downloaded from template
Copied and pasted all the CSS for the content on the template to the styles.css
Add div for the different sections of the model
Add multiple selectors and properties in styles.css
Removed all errors from styles locally using linters

Hi <STUDENT_MENTION>,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that has no pull request description. Please add a pull request description that summarizes all the changes you implemented on the branch. Kindly check here for more information.
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.
Invalid Code Review Request does not count into the code reviews limit.


algolia search seems broken

Probably from the migration.

Perhaps take if off the page while we're fixing it @christian-bromann?

On it

I reached out to the support team as it is unfortunately not possible to updated the domain given it is an Open Source account. Will report back when this has been updated.

Fixed by https://github.com/stateful/docs.runme.dev/pull/174


push some color changes and code removal

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

👷 Deploy Preview for betsweatwin processing.

Name
Link

🔨 Latest commit
1860f2dae47af665dcfa8d284e9f9cbf2c572444

🔍 Latest deploy log
https://app.netlify.com/sites/betsweatwin/deploys/65512c98cf86600008f68825


PR: Adding Verify-dependant application details to Prove ID choice page

Relates to issues #400 #401 #402 #477 plus user needs to a) know online application length and b) know permit wait length which I can't see tickets for but was asked to include at the front of the application.
Before

After

@lizziebruce Thanks for moving the info that was on the start page to this page, as we agreed. I still think it's right that it's more suited to this page, and the content that you've written communicates the info needs as clearly as they can be communicated.
However, now I've seen it, I'm a little worried about adding more information to this page, because (as we all know) when people see a block of text, or even more than two lines, they tend not to read any of it.
I'd like to dive deeper into the two new points added:
Temp permit - Do people find this a more important benefit than the working days to receive permit? If so, can we remove that line instead? If not, do we need to say it at all? Or maybe we can combine the two things into one? (ie "You'll be able to park straight away" VS "You'll need to wait 10 working days to receive your permit" or something)
Time to do application - I consciously didn't include this information when designing this page* because it gets really complicated with all the different options, and I wanted to see if we didn't include it how much it would come up as a need. Do we have research any where that this is a need? I think certainly now we're almost exclusively working at LOA1, we'll see the "It took too long" issue much less.
*Some options I looked at whilst redesigning this page.

Hi @lizziebruce @sanjaypoyzer I think it looks good as is, in regards to temp permits vs time to arrive I think the original reasoning to have time to arrive information was to incentivise users to choose the Verify route. In reality the temporary permit is a greater benefit because for the user, as It would take a similar amount of time to receive a normal permit no matter the route taken. So if on Monday we find that users don't read the text, then my vote would be to remove the 'time to arrive' line

@EUzkuraityte @sanjaypoyzer thanks both for your review. @petegale was really happy when I showed him this screen. He mentioned that users would be likely to read the bullets carefully even though there are several as they can see it's information directly relating to the choice they're making.
@sanjaypoyzer "You'll be able to park straight away" throws up its own lengthly text as you'd need to add "with a temporary permit which you'll recieve from us" as by itself it is meaningless, the user can already physically park straight away it just wouldn't be legal. Content design is trickier than it looks :-)
However I can see the user case to remove "time to arrive" as the UR I observed people weren't commenting on that as a benefit, it looked only 1 person noticed (is this right @petegale ?)
Shall we go ahead for Monday as is and see if users react badly to the "excess" text and if so then remove the time to arrive line?


add zerolog structure output for debug logging

Could you export Logger interface for opportunity for redefine it ?

SetLogOutput  was added to master branch da7b08c0e3e9b546abd9e0ef6339ebf3a1ff0d53


total irradiance docs don't show poa_diffuse as a return, but package overview uses it

Thought I was going crazy today, when I couldn't find any references of total_irrad returning poa_diffuse, but there it is in the package overview procedural example and I've been using it my code.
Looking through the code it was changed in #105 to output global, beam, diffuse sum, just sky diffuse and just ground diffuse. To avoid craziness, the docs should probably be updated. Should be an quick, easy fix.

closed by #376


It does not seem to do anything

Hi,
the script does not seem to do anything, not even launching curl. JS and curl are installed.
This is the output when launched with bash -x
-sh-3.2$ bash -x check_graylog_node -H graylog.fdqn.tld -a node_id
+ DEBUG=0
+ WORKDIR=/tmp
++ basename check_graylog_node
+ LOG=/tmp/check_graylog_node.log
+ APIPORT=9000
+ USERNAME=zabbix
+ PASSWORD=monitoring
+ getopts hH:a:p::l:d opts
+ case $opts in
+ HOSTNAME=graylog.fdqn.tld
+ getopts hH:a:p::l:d opts
+ case $opts in
+ ATTR=node_id
+ getopts hH:a:p::l:d opts
+ '[' 0 == 1 ']'
+ [[ 5 -lt 4 ]]
++ basename check_graylog_node
+ LOCKFILE=/tmp/check_graylog_node-graylog.fdqn.tld.lock
+ LOCKFD=99
+ _prepare_locking
+ eval 'exec 99>"/tmp/check_graylog_node-graylog.fdqn.tld.lock"'
++ exec
+ trap _no_more_locking EXIT
+ CURL_BASE_CMD='curl -u zabbix:monitoring -sS http://graylog.fdqn.tld:9000/api'
+ NODE_INFO_FILE=/tmp/graylog.fdqn.tld-node.json
+ JOURNAL_INFO_FILE=/tmp/graylog.fdqn.tld-journal.json
+ SYSTEM_INFO_FILE=/tmp/graylog.fdqn.tld-system.json
+ CLUSTER_INFO_FILE=/tmp/graylog.fdqn.tld-cluster.json
+ case $ATTR in
+ shlock
+ _lock s
+ flock -s 99
+ get_node_id
+ debug '[get_node_id] Executing'
+ '[' 0 == 1 ']'
+ jq -e -r .node_id /tmp/graylog.fdqn.tld-node.json
+ _no_more_locking
+ _lock u
+ flock -u 99
+ _lock xn
+ flock -xn 99
+ rm -f /tmp/check_graylog_node-graylog.fdqn.tld.lock

The curl if launched manually works:
-sh-3.2$ curl -u zabbix:monitoring -sS http://graylog.fdqn.tld:9000/api
{"cluster_id":"c0ca4d64-71ad-4bb4-8088-19420246bbb8","node_id":"80d2da2a-56af-48d2-b2b4-da7f3fffcf75","version":"2.2.ge your logs in the dark and have lasers going and make it look like you're from space!"}-

But it seems that the script does not even attempt to launch curl.
Thanks in advance for any help!

Hi,
Can you please let me know of the versions of zabbix, graylog?
Do you have anything in the json files that get created in /tmp?
Thanks.

Just to make sure.. are you calling poll_data first?

Yeah that was the problem. I didn't run poll_data first. My bad.
Even tough technically it would work if used with the provided zabbix template (which run poll_data every 25s), may I suggest to write in the notes that the script works only if poll_data is called before?

Will do ;-) Thanks.


Bump scalacheck and scalatest versions

This PR bumps scalacheck and scalatest version and fix all tests which started to fail.
Fixed failures:

scalacheck generates better arbitrary functions now, this cause fail of "match scala for leftJoin jobs", "match scala for leftJoin repeated tuple leftJoin jobs" and "match scala for leftJoin with store (no dependency between the two) jobs", also it uncovered that memory law about leftJoin and sumByKey doesn't make sense
oneOf generator fails in case of empty input sequence now
some tests were failing on empty input elements, because they assumed input time interval is empty

This looks fine to me.
MemoryPlatform is pretty much a toy, and for cases where there are real races in time, it makes sense that the law might fail.

@johnynek note that I changed BatcherLaws in the end. I think this change is ok because a) it shouldn't affect users, b) it makes batchIds more consistent.

Codecov Report

Merging #722 into develop will increase coverage by 0.44%.
The diff coverage is 86.36%.

@@             Coverage Diff             @@
##           develop     #722      +/-   ##
===========================================
+ Coverage    70.93%   71.38%   +0.44%
===========================================
  Files          141      141
  Lines         3475     3491      +16
  Branches       201      199       -2
===========================================
+ Hits          2465     2492      +27
+ Misses        1010      999      -11

Impacted Files
Coverage Δ

.../scala/com/twitter/summingbird/memory/Memory.scala
94.73% <ø> (ø)
:arrow_up:

...ain/scala/com/twitter/summingbird/TestGraphs.scala
93.67% <ø> (+7.77%)
:arrow_up:

...twitter/summingbird/batch/MillisecondBatcher.scala
100% <100%> (ø)
:arrow_up:

...com/twitter/summingbird/scalding/TestService.scala
97.5% <100%> (+4.16%)
:arrow_up:

...la/com/twitter/summingbird/scalding/TestUtil.scala
48.27% <50%> (-0.85%)
:arrow_down:

.../com/twitter/summingbird/TestGraphGenerators.scala
96.25% <75%> (-2.4%)
:arrow_down:

...cala/com/twitter/summingbird/batch/TimeStamp.scala
59.45% <0%> (+2.7%)
: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 ab747e6...5e58c25. Read the comment docs.

@johnynek Do you mind to look one more time? Thanks!

[info] ! BatchID.range, toInterval and toIterable should be equivalent: Exception raised on property evaluation.
[info] > ARG_0: BatchID.9223372036854775807
[info] > ARG_1: 0
[info] > Exception: java.util.NoSuchElementException: Either.right.value on Left

Can you run the batcher tests locally and get them green? Might save time since travis is so slow.

@johnynek I did run it locally and it passed. I guess test you mentioned is flaky, I'm gonna investigate it as well.
Main reason I still didn't merge is this:

The log length has exceeded the limit of 4 MB (this usually means that the test suite is raising the same exception over and over).

Looks like either we started to print a little bit more logs then before (I saw size of logs exactly around 4mb in local runs) or travis changed this limit recently.
What I found is that we already try to print much less logs on travis (see last commit in regards to log4j), but it doesn't change anything. I'll merge this branch as soon as I fix this issue.

@johnynek I tried to rerun BatcherLaws locally a lot of times, and I haven't seen this error. Where did you find it?

on the link from travis. See the red x next to pr?

@johnynek you're right, it's a legit failure: range, toInterval and toIterable should be equivalent fails in case of BatchId == MAX_LONG - 1 & diff == 0 =) It's also very rare that's why I didn't see it locally.
I'm tired of slow travis with non legit exceptions, that's why I missed this one, thanks for pointing out!
I'll fix it.

@johnynek Actually this failure is pretty interesting. Root cause for that is - BatchID.range can handle intervals like [MAX_LONG, MAX_LONG], while it's impossible to handle this interval through Interval.leftClosedRightOpen instances. I'm wondering can we use intervals closed from both sides?

these tests are so frustrating.
Looks like travis killed 2.11:
/home/travis/.travis/job_stages: line 54:  2273 Killed                  ./sbt -Dlog4j.configuration=$LOG4J ++$TRAVIS_SCALA_VERSION clean coverage test coverageReport mimaReportBinaryIssues

Agree, the tests are very frustrating. I'll try to spend some time on them when I get a chance.

lgtm


top level files logic

Just defined a logic for the files that should be only-top-level files for the checks - like README.md
Add more files here - https://github.com/senecajs/seneca-maintain/pull/8/files#diff-8051daf8dce492535eee0bbd1fb18cc86d611c08336ef52f7f5649635430ea8eR178

Thanks for bringing this up as an issue and a PR - it has been solved with a simpler fix here (b94593cf397c0502638d4a9eb1a1ccc0c6724cc3)


fullRobot animation

Reported by frank.rettig on 28 Mar 2011 13:52 UTC
The "fullRobotR3" (Modelica.Mechanics.MultiBody.Examples.Systems.RobotR3.fullRobot) example doesn't give a meaningful animation. The animation works only in Dymola if the "extra" value of all shapes in the example is set to zero. According to the documentation, the extra value should not have any influence on dxf-shapes.
Since the model is part of the MSL the animation should work without any dymola specific settings.

Migrated-From: https://trac.modelica.org/Modelica/ticket/510

Modified by dietmarw on 28 Mar 2011 15:01 UTC

Comment by anonymous on 1 Apr 2011 08:28 UTC
I got the information from the Dymola support (thanks Ulf), that the "extra" value of a cad-shape defines whether the geometry is scaled (extra = 1) or not (extra = 0). If extra = 1 the scaling factors are "length", "width" and "height" of the shape.
This information is missing in the documentation.

Comment by otter on 30 Jun 2011 19:35 UTC
Fixed in ecd3a56cb41f506867eba2abebb7660ee30da320 (added the suggested documentation)


Add Makefile Parser

One of the problems with building arbitrary packages is getting a clear idea of undeclared dependencies. Most C/C++ projects mention their dependencies in their documentation or assume some kind of base set of dependencies. When it actually comes to the configure step (if one exists) they will do actual dependency detection and report errors if dependencies are not found.
The idea for this feature is a function that parses a Makefile and returns a searchable list of rules. These rules can be analysed to find any dependencies relied on to compile the final executable.
I understand this is a significant undertaking parsing very complex build systems but I'd like to take this incrementally. The first version will only support very simple Makefiles.
This will also be a first step towards parsing more build system definitions like CMake and Autoconf in the future. The long term goal is to be able to take a random archive of source code and automatically determine a valid package definition to build it.

Well that works. I added a Makefile evaluator based on https://github.com/google/kati (it used to be written in Go and I pulled the last version of that).
It passes most of the test cases in that repo.
The next goal is to get it to spit out dependency graphs for the Linux kernel :). This is going to be hard.

I embedded the code into my shell_context which also supports evaluating shell scripts.  That would mean making the filesystem support a little less cursed and eventually trying to match Unix semantics as close as I can.

This is the top level dependency graph for the Linux kernel. You need to evaluate the subtrees to get the full graph though.
 DepNode{Makefile, kernel}
   DepNode{Makefile, prepare}
     DepNode{Makefile, prepare0}
       DepNode{Makefile, archprepare}
         DepNode{Makefile, prepare1}
           DepNode{Makefile, prepare2}
             DepNode{Makefile, prepare3}
               DepNode{Makefile, include/config/kernel.release}
                 DepNode{Makefile, include/config/auto.conf}
                   DepNode{Makefile, .config}
                   eval []
                   DepNode{Makefile, include/config/auto.conf.cmd}
                   eval []
                 eval ["make -f ./Makefile silentoldconfig"]
                 DepNode{Makefile, FORCE}
                 eval []
               eval ["rm -f include/config/kernel.release", "echo \"2.6.39$( ./scripts/setlocalversion .)\" > include/config/kernel.release"]
             eval []
             DepNode{Makefile, outputmakefile}
             eval []
           eval []
           DepNode{Makefile, include/linux/version.h}
             DepNode{Makefile, Makefile}
             eval []
             DepNode{Makefile, FORCE}
             eval []
           eval ["set -e; echo '  CHK     include/linux/version.h'; mkdir -p include/linux/; \t(echo \\#define LINUX_VERSION_CODE $(expr 2 \\* 65536 + 6 \\* 256 + 39); echo '#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))';) < Makefile > include/linux/version.h.tmp; if [ -r include/linux/version.h ] && cmp -s include/linux/version.h include/linux/version.h.tmp; then rm -f include/linux/version.h.tmp; else echo '  UPD     include/linux/version.h'; mv -f include/linux/version.h.tmp include/linux/version.h; fi"]
           DepNode{Makefile, include/generated/utsrelease.h}
             DepNode{Makefile, include/config/kernel.release}
               DepNode{Makefile, include/config/auto.conf}
                 DepNode{Makefile, .config}
                 eval []
                 DepNode{Makefile, include/config/auto.conf.cmd}
                 eval []
               eval ["make -f ./Makefile silentoldconfig"]
               DepNode{Makefile, FORCE}
               eval []
             eval ["rm -f include/config/kernel.release", "echo \"2.6.39$( ./scripts/setlocalversion .)\" > include/config/kernel.release"]
             DepNode{Makefile, FORCE}
             eval []
           eval ["set -e; echo '  CHK     include/generated/utsrelease.h'; mkdir -p include/generated/; \tif [ `echo -n \"$(cat include/config/kernel.release 2> /dev/null)\" | wc -c ` -gt 64 ]; then echo '\"$(cat include/config/kernel.release 2> /dev/null)\" exceeds 64 characters' >&2; exit 1; fi; (echo \\#define UTS_RELEASE \\\"$(cat include/config/kernel.release 2> /dev/null)\\\";) < include/config/kernel.release > include/generated/utsrelease.h.tmp; if [ -r include/generated/utsrelease.h ] && cmp -s include/generated/utsrelease.h include/generated/utsrelease.h.tmp; then rm -f include/generated/utsrelease.h.tmp; else echo '  UPD     include/generated/utsrelease.h'; mv -f include/generated/utsrelease.h.tmp include/generated/utsrelease.h; fi"]
           DepNode{Makefile, include/config/auto.conf}
             DepNode{Makefile, .config}
             eval []
             DepNode{Makefile, include/config/auto.conf.cmd}
             eval []
           eval ["make -f ./Makefile silentoldconfig"]
         eval ["mkdir -p .tmp_versions "]
         DepNode{Makefile, scripts_basic}
         eval ["make -f scripts/Makefile.build obj=scripts/basic", "rm -f .tmp_quiet_recordmcount"]
       eval []
       DepNode{Makefile, FORCE}
       eval []
     eval ["make -f scripts/Makefile.build obj=.", "make -f scripts/Makefile.build obj=. missing-syscalls"]
   eval []
   DepNode{Makefile, scripts}
     DepNode{Makefile, scripts_basic}
     eval ["make -f scripts/Makefile.build obj=scripts/basic", "rm -f .tmp_quiet_recordmcount"]
     DepNode{Makefile, include/config/auto.conf}
       DepNode{Makefile, .config}
       eval []
       DepNode{Makefile, include/config/auto.conf.cmd}
       eval []
     eval ["make -f ./Makefile silentoldconfig"]
     DepNode{Makefile, include/config/tristate.conf}
       DepNode{Makefile, .config}
       eval []
       DepNode{Makefile, include/config/auto.conf.cmd}
       eval []
     eval ["make -f ./Makefile silentoldconfig"]
   eval ["make -f scripts/Makefile.build obj=scripts"]
 eval ["make -f scripts/Makefile.build obj=kernel"]

After a bunch of fixes in the recent commits it can now evaluate the Linux Makefile without errors. Lots of unimplemented commands and bugs with existing commands though.

I'd say the Makefile parser works but the shell commands need more work.


Fix recursive issue of isAnydata method while checking record types with same refrence

Purpose

Stack over flow issue can be observed in isAnydata method  while manipulating record types which has same reference. This PR will fix that.
ex.

type Person record {
    string name = "";
    int age = 0;
    Person? parent = ();
    json info = ();
    map<anydata>? address = ();
    int[]? marks = ();
    anydata a = ();
    float score = 0.0;
    boolean alive = false;
    Person[]? children = ();
    !...
};

function testCyclicRecordAssignment() returns (anydata) {
    Person p = {name:"Child",
                age:25,
                parent:{name:"Parent", age:50},
                address:{"city":"Colombo", "country":"SriLanka"},
                info:{status:"single"},
                marks:[67, 38, 91]
    };
    anydata adp = p;
    any p2 =  <Person>adp;
    if(p2 is anydata){
        return p2;
    } else {
        return ();
    }
}

testCyclicRecordAssignment function will produce stack overflow issue at compiler time and runtime due to isAnydata method not supporting cyclic record types.

Closing this. Please find new PR  for df-endpoint-change branch.
https://github.com/ballerina-platform/ballerina-lang/pull/11781


There might be a light flicker as the default lights are turned off and new lights are added in

Not an issue.


[C2M] Float constants from math.h give errors and warnings

Doing some more tests with C2M I've found that the following is unable to compile:
#include <stdio.h>
#include <math.h>
void main() {
  printf("%lf\n", NAN);
  printf("%lf\n", INFINITY);
  printf("%lf\n", HUGE_VAL);
  printf("%f\n", HUGE_VALF);
  printf("%Lf\n", HUGE_VALL);
}

When running the example with c2m the output is:
/usr/include/math.h:62:21: warning -- number 1e10000f is out of range
/usr/include/math.h:55:19: warning -- number 1e10000 is out of range
/usr/include/math.h:62:21: warning -- number 1e10000f is out of range
/usr/include/math.h:63:21: warning -- number 1e10000L is out of range
/usr/include/math.h:103:16: Division by zero

What was expected is no warnings or errors.
The culprits are those lines from GLIBC 2.30:
https://github.com/bminor/glibc/blob/glibc-2.30/math/math.h#L62
https://github.com/bminor/glibc/blob/glibc-2.30/math/math.h#L103

Thank you for reporting this issue.  GLIBC uses GCC builtins for getting inifinity and NaN.  For non GCC conforming compilers, math.h uses big values and 0.0 / 0.0 for NAN.
I can not remove warnings because these warnings are useful in other cases but I can fix the error.  The patch will be  ready soon.

Here is the patch
https://github.com/vnmakarov/mir/compare/84b277a..5f91154

Is there a way to get Nan, -Inf and Inf values in MIR.
I am using following in my C output but not sure if this works:
#define nan (0./0.)
#define inf (1./0.)

Basically in a JIT mode, it is better to not have to rely on any external headers; in Ravi, no headers are used, and I rely only upon MIR.

Is there a way to get Nan, -Inf and Inf values in MIR.
I am using following in my C output but not sure if this works:
#define nan (0./0.)
#define inf (1./0.)

It might be target-dependent.  But for x86-64 1.0/0.0 is infinitity.  0.0/0.0 is actually -nan.  It is better to use function nanl for getting NAN or the following code
static unsigned long nan_long = 0x7fffffffffffffff;
#define nan (*(double *)&nan_long)

Another problem is that NAN and INFITITY is defined in math.h.  If I define builtin functions for such values and define macro __GNUC__, there would be no problem.  But defining __GNUC__ would create much more other problems because most of GCC extensions are not implemented in c2m and a lot of programs check this to use these extensions.

Basically in a JIT mode, it is better to not have to rely on any external headers; in Ravi, no headers are used, and I rely only upon MIR.

@vnmakarov Okay thank you. I suppose I can use just a macro - or would the static be optimized away?
I agree it is not a good idea to define GNUC unless you want years of pain! :-)
Regards

As <math.h> can be included without issues since the patch and the warnings can be silenced with -w, I am closing this.


Ephemeral [?]

Hi,
Is it possible to set "ephemeral: true" under the ping command? if so how shall it be set?

Yes, you just need do add it under reply
  inter.reply({
    content: `${client.user.tag}: pong`,
    ephemeral: true,
  });

@GuriZenit it worked. Would be nice, if it's possible bot will "restart or reload" when there is changes from .js file e.g :-)

@GuriZenit it worked. Would be nice, if it's the possible bot will "restart or reload" when there are changes from .js file e.g :-)

I'll look for it, thanks for the suggestion!
I need to add permissions too, if have any other people in your guild, they can use add and delete command and that's a problem.

I'll look for it, thanks for the suggestion! I need to add permissions too, if have any other people in your guild, they can use add and delete command and that's a problem.

That's good to know! :+1:

@GuriZenit it worked. Would be nice, if it's the possible bot will "restart or reload" when there are changes from .js file e.g :-)

You can clone de repo again and use it, #18 here is a simple tutorial, It's a third-party package so I didn't have to do much

#21 fixes the error of using the package nodemon which has been removed.


Fill correctly hasNext and total fields in paged models

Describe the bug
Currently, we have places in project where paged responses are returned with hardcoded hasNext and total properties. Need to fix this and return valid values to frontend. Frontend need to use these values instead of current solution

Closing this as completed in previous various PRs.


Added arp-scan util for device tracker to Dockerfile

I added the arp-scan util to Dockerfile to support a fast device tracker based on it.
I hope I have edited the correct file, and I need directions on how to build it locally, to test the PR.

Hello @cyberjunky,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

d0333d1ad5b3f3dee1153fa4d3c368330fbc6e56 - This commit has something that looks like an email address (ron@home-assistant). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Hello @cyberjunky,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

84c6274589e80c0b24356444566b46b73457f0fb - This commit has something that looks like an email address (ron@home-assistant). Maybe try linking that to GitHub?.
d0333d1ad5b3f3dee1153fa4d3c368330fbc6e56 - This commit has something that looks like an email address (ron@home-assistant). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Hello @cyberjunky,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

9771b4472b9524968026aee04f06f71d41bab9ca - This commit has something that looks like an email address (ron@home-assistant). Maybe try linking that to GitHub?.
a8f886f135418f205d7b39986586401449b2abbd - This commit has something that looks like an email address (ron@home-assistant). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:


A PHP Error was encountered

A PHP Error was encountered
Severity: 8192
Message: Creation of dynamic property CI_URI::$config is deprecated
Filename: core/URI.php
Line Number: 102
Backtrace:
File: /opt/lampp/htdocs/salescon1/index.php
Line: 292
Function: require_once

@fauwaz-911
Which version of php you use?

I use php version 8.2.4

@fauwaz-911
In php 8.2, dynamic properties are deprecated. You can use it with php 8.1 as latest.
If CodeIgniter Foundation make an update to version 3.1.13 , i will update this repo.

@kirilkirkov Okay, Thanks


Update run_id when adding ds in mem to db

This should fix the issue of run_ids not getting incremented when importing netcdf datasets or datasets in memory in general.
Addressing the issue we have talked about @jenshnielsen .
I have replaced the table name return value, as I could not find it used anywhere and it is not a part of a public API.

@Dominik-Vogel Thanks. Looks like it is used in database_extract_runs.py see typechecking error.
I think we should see if we can write a test for this too

@Dominik-Vogel I have added tests and implemented the same fix for counter and exp_id. Could you have another look?


Consider separating return type from thrown exception in API docs

I just noticed that we're "bundling" the type of the exception that's thrown with the return type of a method, e.g. for delete:

IMO, this is not quite accurate because the exception doesn't impact the return type. E.g. in this snippet:
const x = await prisma.user.delete({ where: { id: 1 } });

x is just typed to User, so the return type of the entire method is just User, it never can return anything else:

It can however throw an exception, which in my understanding is different than a return type and therefore probably should be treated separately in the docs as well.

https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#delete

Thanks, @nikolasburk thanks for catching this. Question: can one ever actually get a return value (an output) of RecordNotFound?
It might "just"  be semantics... but in general I agree with you that exceptions/errors are not really return types, and so it should not be included in that table, nor the column labeled "Return type". There could be a H3 section below for exceptions.

There could be a H3 section below for exceptions.

I think it might be worth looking at how other API docs handle such cases and how they're pointing out whether method throws an exception or not.

This is just a special one of this kind of method I guess, so it might need to be "Method specific Exceptions" or similar.

I had in mind something similar as well. I also wonder whether there are already any best practices for this, e.g. in JSDoc you can use the @throws annotation which would be appropriate here I guess.


Remove stale link for air gap single node page with config private registry

Below page returns a 404 as it is moved to a different location. I bumped upon this page while looking for private registry docs online using keywords "rancher private registry"
https://rancher.com/docs/rancher/v2.x/en/installation/air-gap-single-node/config-rancher-for-private-reg/
Moved to
https://rancher.com/docs/rancher/v2.x/en/installation/air-gap/install-rancher/

fixed in docs


Vagrant cleanups

Some drive-by cleanups to the Vagrant setup.

I nominate @pchaigno as reviewer :P. Thanks!

I nominate @pchaigno as reviewer :P. Thanks!

Done :see_no_evil:


osu_irc no longer working after server changes

Now getting this error after bot connects to irc.
[MBOT]: Starting the bot...
[MBOT]: Connecting to MySQL...
[MBOT]: Connected to MySQL!
[MBOT]: Connecting to Bancho...
[MBOT]: Connected to Bancho!
Traceback (most recent call last):
File "C:\venv\MeqBot\lib\site-packages\osu_irc\Classes\client.py", line 97, in main
await self.listen()
File "C:\venv\MeqBot\lib\site-packages\osu_irc\Classes\client.py", line 133, in listen
if payload in ["", " ", None] or not payload: raise EmptyPayload()
osu_irc.Utils.errors.EmptyPayload
Task was destroyed but it is pending!
task: <Task pending coro=<addTraffic() running at C:\venv\MeqBot\lib\site-packages\osu_irc\Utils\traffic.py:13> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x000002AA753978B8>()]>>
Task was destroyed but it is pending!
task: <Task pending coro=<addTraffic() running at C:\venv\MeqBot\lib\site-packages\osu_irc\Utils\traffic.py:13> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x000002AA753979D8>()]>>
Task was destroyed but it is pending!
task: <Task pending coro=<addTraffic() running at C:\venv\MeqBot\lib\site-packages\osu_irc\Utils\traffic.py:13> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x000002AA75397858>()]>>
Task was destroyed but it is pending!
task: <Task pending coro=<trafficQuery() running at C:\venv\MeqBot\lib\site-packages\osu_irc\Utils\traffic.py:27> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x000002AA75397948>()]>>

soo it took some time, but now osu is next on my list, as i done with my twitch_irc lib, i will rewrite this one aswell,
i fixed that bug already and it will be applied in the next major version push.
are there any things you might want in the lib?

@TheMeq major update has been released, please test if anything workes.
if not let me know.
(gonna close this issue on 2020-09-30)


How to detect if new message has come?

Hi.
Good extension. But I have some problems.
I need to show to users that somebody recently received new message in my application. How I can do that?

Query with updated_at in conversations table

Thanks for reply.
But how I can do in real time?

Why you need this?

In general, our tech support answers to user questions. Users write to the chat. If user's waiting is too long, obviously they would leave our website. Or users chat with each other in order to communicate. They need fast messaging to do actions, deals and so on. We need so much that.

Decided to implement like this https://pusher.com/tutorials/realtime-notifications

Talk is also Pusher ready with realtime chat. I think our doc will help you.

I decided to integrate their notification solution into talk


Method not work when upgrade to 4.0

    func downloadProgress(bytesRead: Int64, totalBytesRead: Int64,
        totalBytesExpectedToRead: Int64) {
        let percent = Float(totalBytesRead)/Float(totalBytesExpectedToRead)

        dispatch_async(dispatch_get_main_queue(), {
            self.progress.setProgress(percent,animated:true)
        })
        print("Progress：\(percent*100)%")
    }

    func downloadResponse(request: NSURLRequest?, response: NSHTTPURLResponse?,
        data: NSData?, error:NSError?) {
        if let error = error {
            if error.code == NSURLErrorCancelled {
                self.cancelledData = data
            } else {
                print("Failed to download file: \(response) \(error)")
            }
        } else {
            print("Successfully downloaded file: \(response)")
        }
    }

    @IBAction func continueBtnClick(sender: AnyObject) {
        if let cancelledData = self.cancelledData {
            self.downloadRequest = Alamofire.download(resumeData: cancelledData,
                destination: destination)

            self.downloadRequest.progress(downloadProgress)

            self.downloadRequest.response(completionHandler: downloadResponse)

            self.stopBtn.enabled = true
            self.continueBtn.enabled = false
        }
    }

The codes works fine on version 3.1, but it refuse to work after upgrading to 4.0
The following two line shows error "no such memeber fo progress" and " no such member of response"

self.downloadRequest.progress(downloadProgress)
self.downloadRequest.response(completionHandler: downloadResponse)

How to solve these two problem? Thanks.

You need to switch over to using the new downloadProgress API on a DownloadRequest documented here in the migration guide and here in the README.
Cheers. 🍻

Thanks your guide, I finally found the key.

@jdleung, could you help me out? What is this key you are referring to?
I also had a error.code == NSURLErrorCancelledcomparison, but I'm now unable to get this error.
I also tried to go trough the downloadProgress API, but was unable to get a way of knowing the request failed because it was user canceled.

@nmdias I just meant I found the solution. I'm sorry that I forgot how I solved it, it's been some days after all. You can post your code here ;-)


Force 60fps recordings

I was wondering if it is possible to force wf-recorder to record at a consistent 60fps? (ie. an ffmpeg parameter)
It seems right now, wf-recorder records at a variable framerate.
This causes programs like kdenlive to render videos recorded by wf-recorder at a very low framerate.
Output of mediainfo, ran with wf-recorder -f file.mp4
...
Duration                                 : 11 s 545 ms
Bit rate                                 : 4 007 kb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Variable
Frame rate                               : 13.253 FPS
Minimum frame rate                       : 0.315 FPS
Maximum frame rate                       : 106.257 FPS
Original frame rate                      : 60.000 FPS
...

Thanks!

Since a recent commit we started to not request frames continuously from the compositor. Is the situation better with the 0.2.1 release instead of master?
Btw, we can't really force 60fps because the frames are sent by the compositor. And the compositor rarely works at exactly 60fps, but rather always a bit more or less.

Yes, it seems 0.2.1 works better. Mediainfo reports 59fps.
I also realized I can force 60fps on kdenlive renders, but even then, 0.2.1 is still a bit smoother than master

Alright, we could add a flag to control this behavior. Thanks for reporting it.

Yes, it seems 0.2.1 works better. Mediainfo reports 59fps.
I also realized I can force 60fps on kdenlive renders, but even then, 0.2.1 is still a bit smoother than master
Wrong account, oops xd

You can use the new -D command line flag to make wf-recorder continuously request frames from the compositor, it should achieve (near-)maximal frame rate


Expo managed workflow compatibility?

Hello @Rapsssito
First of all, thank you for this great library, it has really proven to be an essential part of my app!
I'm using with it with great success in my react native project (CLI project), but with Expo SDK alongside it, i.e. the bare workflow. With the advent of Expo's custom development clients and config plugins, it has been possible to use Expo's managed workflow, while also being able to use the "unsupported" libraries.
I was wondering, have you had any intentions or thoughts about supporting Expo through this workflow? I tried adding  Android support on my own through a config plugin that basically does the manual configuration required by this library, but I got stuck when I actually attempted to run a background task. Basically, the task would start and at the same moment end, and I'd get a console warn saying No task registered for key: ...
Do you have any thoughts on this?
Thanks in advance!

@fobos531, thanks for the feedback! I am not planning on adding support for Expo. I am not an active user of Expo and I lack the capabilities to maintain it bug-free. However, if you are finally able to set it up, I would gladly accept your PR!

@Rapsssito what subdirectory would you like me to put the config plugin in? I've written one for a project I'm working on and would be happy to make a PR.

@contactsimonwilson, I don't know, actually. Do you know of other react-native library with the expo config plugin we can use as an example?

Sure do. Check the plugin directory of this repo.
https://github.com/includable/react-native-email-link

@contactsimonwilson, okay. I don't really like the naming of "plugin". Could you create a folder named "expo" and then inside place a folder named "plugin" with the necessary code?

@Rapsssito sure, will do.

@Rapsssito apologies for forgetting about this. Here's a branch with my changes
https://github.com/contactsimonwilson/react-native-background-actions/commit/5662a9ec5d0e63740af4c6a2b3aad2395af19402
At the moment I've published it as a standalone package. Do you want it that way or published independently or just contained within the existing package?

@contactsimonwilson, whatever you prefer. If you think it will be easy to integrate with the existing package, it will probably benefit more users. However, you will have to add a notice in the README for the instructions for Expo.

@Rapsssito will do. I'm just doing some verification of the version I've published temporarily for now then will make a PR once I'm happy it works as expected.

@1-AlenToma
This is the plugin code I've been using for the last year
import {
AndroidConfig,
ConfigPlugin,
createRunOncePlugin,
withInfoPlist,
withAndroidManifest,
} from "@expo/config-plugins";
const pkg = { name: "react-native-background-actions", version: "UNVERSIONED" }; //require('react-native-background-actions/package.json')
/**
 * Apply background actions native configuration.
 */
const withBackgroundActions: ConfigPlugin<void> = (config) => {
  // iOS
  config = withInfoPlist(config, (newConfig) => {
    if (!newConfig.modResults.BGTaskSchedulerPermittedIdentifiers) {
      newConfig.modResults.BGTaskSchedulerPermittedIdentifiers = [];
    }

    if (
      Array.isArray(newConfig.modResults.BGTaskSchedulerPermittedIdentifiers)
    ) {
      newConfig.modResults.BGTaskSchedulerPermittedIdentifiers.push(
        "$(PRODUCT_BUNDLE_IDENTIFIER)"
      );
    }

    if (!newConfig.modResults.UIBackgroundModes) {
      newConfig.modResults.UIBackgroundModes = [];
    }

    if (
      Array.isArray(newConfig.modResults.UIBackgroundModes)
    ) {
      newConfig.modResults.UIBackgroundModes.push(
        "processing"
      );
    }

    return newConfig;
  });

  // Android
  config = AndroidConfig.Permissions.withPermissions(config, [
    "android.permission.FOREGROUND_SERVICE",
    "android.permission.WAKE_LOCK",
  ]);

  config = withAndroidManifest(config, (newConfig) => {
    if (newConfig.modResults.manifest.application) {
      if (!newConfig.modResults.manifest.application[0].service) {
        newConfig.modResults.manifest.application[0].service = [];
      }

      newConfig.modResults.manifest.application[0].service.push({
        $: {
          "android:name":
            "com.asterinet.react.bgactions.RNBackgroundActionsTask",
        },
      });
    }
    return newConfig;
  });

  return config;
};

export default createRunOncePlugin(
  withBackgroundActions,
  pkg.name,
  pkg.version
);

@contactsimonwilson
I think I found the issue, I am developing this on my phone with termux and are not able to run:android command so the autolink is not working.
I run expo prebuild only but it is not helpng, will test the code above any way thx

Quien puede darme ayuda con un plugin para expo?


Move dependency reports to aggregate-reporting pipeline

Currently we apply a tag to pipeline runs which is then picked up by a release pipeline to publish dependency reports. With the move to push aggregate reporting operations onto a separate pipeline we will need to replumb this dependency reporting mechanism to work off the java - aggregate-reports pipeline.

Consolidating into a single pipeline is the next step.

is there another issues for that or did you do that work already? @chidozieononiwu was trying to do something similar for .NET and I wanted to try and be as consistent as possible.

Misdragged as I was triaging my board.

Still need to add those steps to get rid of the release pipeline. We are still at status quo.

I don't think this is an issue anymore?


Add functionality to _ftp_loader.py

-Created base class BaseFtpLoader
-Created classes FtpLoaderEnsemble and FTPLoaderNCBI inheriting from BaseFtpLoader
-Added pre-commit config
-Ran pre-commit on all files

One more change that just came to my mind is to update get_params() -> ftp_directory_gtf, ftp_directory_fasta, ftp_file_gtf, ftp_file_fasta to get_params(file_type) -> ftp_directory, ftp_file where the file_type is either "gtf" or "fasta". Then, the download_and_decompress function would just become download_and_decompress(self, ftp_link, file_type) and no need for download_gtf and download_fasta anymore. I find it ugly to put strings (you'd also need to check if file_type is correct, and accept lower and upper cases), but it helps in refactoring. If you don't want to add these changes, it's okay. Let me know, so I can merge.
Thanks!