[Python] Reset_parameter not working for multiclass

Hello,
I think that there is an issue with reset_parameter callback in Python when doing multi-class classification.
It is easy to reproduce:
from sklearn import datasets
iris = datasets.load_iris()
iris_X = iris.data
iris_y = iris.target

param_algo = {
                'task': 'train',
                'boosting_type': 'gbdt',
                'objective': 'multiclass',
                'metric':{'multi_logloss'},
                'is_unbalance' : True,
                'num_class': 3,
                'num_leaves': 31,
                'min_data_in_leaf':1,
                'learning_rate':0.1,
            }

feature_name=['a', 'b', 'c', 'd']
lgb_train = lgb.Dataset(iris_X,
                        iris_y,
                        feature_name=feature_name)

gbm = lgb.train(param_algo,
                lgb_train,
                num_boost_round=6,
                feature_name=feature_name,
                callbacks=[lgb.reset_parameter(learning_rate=[0.1, 0.1, 0.01, 0.01, 0.01, 0.01])])

LightGBMError: b'Number of classes must be 1 for non-multiclass training'

It works as expected for binary classification and regression problems.
Thank you for the library and keep up the good work :)

@wxchan

look like reset parameters have bugs in all situation, the ObjectiveType and similar configs are set to default during reset.


New Misc Marker: Omega Radio

Name
Omega Radio
Type of Misc Marker
radio
Description
No response
Map
armada
Location Coordinates
[-166.0680266948917, 89.59375]
Any Other Info
No response

Checked, all ok


AuthFailure: AWS was not able to validate the provided access credentials

Steps to reproduce the bug:

Create a role in IAM section of AWS console.
Create a policy from the JSON document from the home page, attach a policy to a role.
Assign a role to the AWS instance.
Run awespottr on the instance.

Expected results:
awespottr should show the regions and prices (this was working in summer 2018).
Actual results:
awespottr prints access denied error. See the full text it prints below.
[18:52]:apl@adeaseweb:~:>awespottr c4.xlarge
Checking spot prices for c4.xlarge instance type.
{ AuthFailure: AWS was not able to validate the provided access credentials
at Request.extractError (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/services/ec2.js:50:35)
at Request.callListeners (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
at Request.emit (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
at Request.emit (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:683:14)
at Request.transition (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:685:12)
at Request.callListeners (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
message: 'AWS was not able to validate the provided access credentials',
code: 'AuthFailure',
time: 2019-01-16T23:53:05.198Z,
requestId: '3a4648cb-9b1c-4624-8fde-b4174359b09f',
statusCode: 401,
retryable: false,
retryDelay: 24.198964719436013 } 'AuthFailure: AWS was not able to validate the provided access credentials\n    at Request.extractError (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/services/ec2.js:50:35)\n    at Request.callListeners (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/sequential_executor.js:105:20)\n    at Request.emit (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/sequential_executor.js:77:10)\n    at Request.emit (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:683:14)\n    at Request.transition (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:22:10)\n    at AcceptorStateMachine.runTo (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/state_machine.js:14:12)\n    at /usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/state_machine.js:26:10\n    at Request. (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:38:9)\n    at Request. (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:685:12)\n    at Request.callListeners (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/sequential_executor.js:115:18)'
error { AuthFailure: AWS was not able to validate the provided access credentials
at Request.extractError (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/services/ec2.js:50:35)
at Request.callListeners (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
at Request.emit (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
at Request.emit (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:683:14)
at Request.transition (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/request.js:685:12)
at Request.callListeners (/usr/lib/node_modules/awespottr/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
message: 'AWS was not able to validate the provided access credentials',
code: 'AuthFailure',
time: 2019-01-16T23:53:05.198Z,
requestId: '3a4648cb-9b1c-4624-8fde-b4174359b09f',
statusCode: 401,
retryable: false,
retryDelay: 24.198964719436013 }
[18:53]:apl@adeaseweb:~:>

I've noticed this happening in certain regions (AP for instance). I've submitted a patch in #7 to address this.

Actually, I figured out the issue. It was caused by the system clock being off by several minutes. I am closing the issue.

I continue to run into this with the AP region not returning data when all the others will. That patch will address that situation by allowing data from everywhere else to be displayed even when one region errors.


Skip cover.spec files found in deps directory

This functionality was broken.
Adresses this issue - https://github.com/rebar/rebar/issues/480

If i'm not mistaken it appears that this issue has already been fixed in commit a83c80d4, do you mind checking if rebar 2.6.0 fixes your issue?

My bad, looks like it is working in 2.6.0. For some reason it didn't work for me first time.


QuickLook

Description of the new feature / enhancement
Hi everyone,
Is it possible to implement QuickLook feature into PowerToys?
Tnx!
Scenario when this would be used?
Every time using file explorer.
Supporting information
No response

/dup #80


[Feature Request] Pipe ledger file input to the bayesian predictor (instead of csv)

I started off 2021 trying to figure out how to automate my finances more (you get major credit for that in 2020 btw).
All my banks export QIF files to quicken which I can then get into ledger format via ledger tools' qif2ledger. Rather than use a csv file as the input for reckon, would it be possible to use a ledger file and then just write out a new ledger file based on the predictions the gem makes?
What I'm looking for is to be able to almost automate this pipeline eventually: script something that downloads all my bank files (though I doubt I can pull that off security wise), then do something like:
rbc_bank_MMYYYY.qif > qif2ledger | reckon -f ./file_name_to_convert.ledger --currency 'SGD ' -l ~/Documents/ledger/2021_perso.ledger -o file_name_to_convertMMYYYY.ledger --suffixed

I imagine since you're already using the ledger format it should not be that tricky, but the value to me of the reckon gem is really the classification rather than the csv conversion, so having another input format would be aces.
Happy New Year!

Please delete. Used wrong account.

Please delete. Used wrong account.


Add BUSCO to the annotation_statistics subworkflow

Add BUSCO to the annotations statistics subworkflow. To do this you can use the existing nf-core busco module https://nf-co.re/modules/busco/ and run BUSCO in proteins mode. You will need to pass it protein fasta files. Currently the sub-workflow only has a GFF file of the protein annotations, we can use this to produce the fasta files by using https://nf-co.re/modules/gffread/ and the genomic fasta file.
The BUSCO score should be added to the final file output by the subworkflow.

Closed by #142


mis-spelled package: ODK Services  org.opendatakit.database.utlities

"utilities" is mis-spelled (dropping first 'i') in ODK Services:
org.opendatakit.database.utlities
This might have been fat-fingered in other projects.

fixed. did a grep of other 2.0 tools did not find another occurence


Fix spacing in python-semantic.md

The spacing was off for the final cell of the python tutorial found here: https://learn.microsoft.com/en-us/azure/search/search-get-started-semantic?tabs=python

#sign-off  #please-sign-off


Added new API version 2022-03-01 to the Mobile Network service

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

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[X] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[X] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version

[X] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

This PR is not ready for review by ARM .. .Please note that the step 3 in the checklist is not fulfilled:
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Specifically , if you are adding a new api version then you must add the previous version as the first commit in the new folder , so that we are able to diff the changes between the versions. I have added "ARMChangesRequested" Tag , please remove the tag once you have fixed this issue.

This PR is not ready for review by ARM .. .Please note that the step 3 in the checklist is not fulfilled:
Adding a new API version -[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Specifically , if you are adding a new api version then you must add the previous version as the first commit in the new folder , so that we are able to diff the changes between the versions. I have added "ARMChangesRequested" Tag , please remove the tag once you have fixed this issue.

@raosuhas, Yes we have followed the manual process for new API version - https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/83/Manual-Process-Adding-new-API-version
Also the diff between the previous version 2022-01-01 and new version 2022-03-01 can be found in - https://github.com/Azure/azure-rest-api-specs/pull/18234/commits/a180e7ba91205a6ca632cd85fc6deeaf681e5931

This is incorrect , you need to update the new folder with the older api verison not the other way round I do not have any way to track latest changes made after the first update now.
From the link you pasted :
Please note that it is time-consuming to review the file line by line for every api-version. When you are creating the swagger specification for the new api-version, please copy the swagger specification from the previous version into the new api-versioned folder and commit it. After that overwrite it with the changes for the new api-version. This makes it easy for us to review the changes.
Can you please fix and let me know again by removing the tag ?

In reply to:<PHONE_NUMBER>

This is incorrect , you need to update the new folder with the older api verison not the other way round I do not have any way to track latest changes made after the first update now.
From the link you pasted : Please note that it is time-consuming to review the file line by line for every api-version. When you are creating the swagger specification for the new api-version, please copy the swagger specification from the previous version into the new api-versioned folder and commit it. After that overwrite it with the changes for the new api-version. This makes it easy for us to review the changes.
Can you please fix and let me know again by removing the tag ?
In reply to:<PHONE_NUMBER>

@raosuhas ,

We have reverted the Mobile Network API version 2022-03-01-preview
Added a new Mobile Network API version 2022-03-01-preview with previous version specs and examples
Updated the README files to refer the latest version
Updated the API version 2022-03-01-preview specs and examples with the latest changes - https://github.com/Azure/azure-rest-api-specs/pull/18234/commits/439e59dd4027b62f05cd79ddb225f048d84ef40f

/azp run

@raosuhas As mentioned in comment above, this new API version went through ARM review in PR 6496 when we merged it to RPSaaSMaster. Is there some way we can mark this so that you don't spend time doing a full review of something that has already been fully reviewed by the ARM review board?

Thank you @raosuhas.
@raych1 Could you please help us on merging this PR?

Approved


Guava upgrade to 30.1.1-jre

Fixed by:

https://github.com/vert-x3/vertx-grpc/pull/109
https://github.com/vert-x3/vertx-stack/pull/130
https://github.com/vert-x3/vertx-zookeeper/pull/123
https://github.com/vert-x3/vertx-http-service-factory/pull/14
https://github.com/vert-x3/vertx-service-discovery/pull/161
https://github.com/vert-x3/vertx-health-check/pull/37
https://github.com/vert-x3/vertx-maven-service-factory/pull/37
https://github.com/vert-x3/vertx-config/pull/140


Dockerise Limber

Closes #933
Changes proposed in this pull request:

Add Dockerfile and docker-compose files.
Set up so that docker build . only includes production dependencies.
Ensure local builds automatically generate the config on launch.
Add a health endpoint for healthcheck to function.
Ignore unnecessary files to reduce docker image size.

All changes here good, but I see missing a way of starting the required services for Limber and the README + commands to start and work with this.

Yes good point.  It was overlooked but I'll add it in now.


Ensure that metadata commit buttons are synced

Overview
We need to make sure that multi-component editors work together as expected

DONE in #162


Invalid range for float inclusive ranges a..=a

With proptest 1.2.0, the following application
use proptest::prelude::*;

proptest! {
    #[test]
    fn inclusive_floats(x in 0.0..=0.0) {}
}

panics with
thread 'inclusive_floats' panicked at 'invalid range', /home/andreas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/proptest-1.2.0/src/num/float_samplers.rs:463:1

Excerpt from the source:
            fn split_interval([low, high]: [$typ; 2]) -> IntervalCollection {
                    assert!(low.is_finite(), "low finite");
                    assert!(high.is_finite(), "high finite");
                    assert!(high - low > 0., "invalid range");

                    let min_abs = $typ::min(low.abs(), high.abs());
                    let max_abs = $typ::max(low.abs(), high.abs());
                    // .....

Apparently the splitting of the intervals assumes that high > low, but this is not a valid assumption for inclusive ranges.
This example might be contrived, but scenarios like these often happen in practice. For example, if you want to generate numbers $x, y, z \geq 0$ satisfying $x + y + z \leq 0$ by generating one number at a time and sampling the other numbers from a modified range, then you'll run into this case very quickly.

Thanks for the report and sorry for the delay. Triaging issues now and will get this on the backlog


Allow custom code-block lanugages

For Feature Requests
Desired Feature: have the possibility to modify the list of available languages within the code block.

Hi, is this coming soon? Would be awesome :) I write much C# for Unity and PHP it would be very helpful

Hi @fishheadcode,
Both of those file types are supported in code blocks right now. Are they not appearing as options for you?

OK i found it. But it woule be awesome if this command - and also all other shortcuts from this page: https://www.bookstackapp.com/docs/user/markdown-editor/ - wouldn´t just be a shortcut, but also an icon in the markdown editor. Just as idea :-)


OLS-86: Updated architecture diagram

Description
Updated architecture diagram:

added metrics part
added configuration part

Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[x] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[ ] CI configuration change
[ ] Konflux configuration change

Related Tickets & Documents

Related Issue #OLS-86

/lgtm

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.88%. Comparing base (32b78e7) to head (aabd8fb).
Report is 57 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1658      +/-   ##
==========================================
- Coverage   94.89%   94.88%   -0.01%
==========================================
  Files          60       60
  Lines        2685     2681       -4
==========================================
- Hits         2548     2544       -4
  Misses        137      137

Flag
Coverage Δ

94.88% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

/approve

/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"

/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"


docs(readme): fix json syntax error in example

Change single quotes to double quotes in the example for config.subjectPatternErrorMsg.

Current coverage is 100% (diff: 100%)

Merging #55 into master will not change coverage

@@           master   #55   diff @@
===================================
  Files           1     1
  Lines          90    90
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits           90    90
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 3386784...0dfa738

Would you like to add yourself to the contributors table? See the contributing guidelines for how.

@kentcdodds I ran into a few issues along the way.

stringstream was not installed by yarn
This threw Error: Cannot find module 'stringstream' when trying yarn run add-contributor.
+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   `-- UNMET DEPENDENCY<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>  `-- UNMET OPTIONAL DEPENDENCY<EMAIL_ADDRESS>
I had to manually install stringstream.

istanbul (?) error on yarn run validate
I haven't used istanbul so I don't know for sure, maybe it's a Windows issue. I'm on Windows as evidenced by the empty line thing apparently.
(function (exports, require, module, __filename, __dirname) { @IF EXIST "%~dp0\node.exe" (
                                                              ^
SyntaxError: Invalid or unexpected token

No emoji even though I selected Documentation. From what I understand it should have received :book:

I'll fix up what you've commented on.

huh, that's weird. If you have any more trouble, don't worry about it and I'll merge it as-is. Thanks!

Thanks!

No bigs, thanks man. All that for a couple double quotes :stuck_out_tongue_closed_eyes:

Yeah, sorry about that. It's worth it to me to recognize those who help with the project! Thanks!

Yep I didn't mean anything by that - it's cool that you have that recognition front and center, I appreciate that.

It's cool that you contributed to the project. I appreciate that.
😀 ❤


request library brings in tough-cookie that brings in a large psl package

Is it possible to just switch to something lightweight (and nicer API) with no deps like node-fetch to do your post()?

Fixed in 4.1.6


Migrate to annotation config for GUI support

Also extend all other config uses (proxies, etc).
Add config option to specifically handle the list of entities that need spacing fixes for Mo' Creatures:
currently the list is:
entity.mocreatures:blackbear.name
entity.mocreatures:grizzlybear.name
entity.mocreatures:komododragon.name
entity.mocreatures:petscorpion.name
entity.mocreatures:wildhorse.name
entity.mocreatures:wildpolarbear.name
This may be different in other localisations.

Include "horses" classes:
ZAWA {
    # Specify list of ZAWA classes that are considered rideable or horses.
    S:HorsesClasses <
        org.zawamod.entity.land.EntityAsianElephant
        org.zawamod.entity.land.EntityGaur
        org.zawamod.entity.land.EntityGrevysZebra
        org.zawamod.entity.land.EntityOkapi
        org.zawamod.entity.land.EntityReticulatedGiraffe
     >
}
Animania
    S:HorsesClasses <
        com.animania.common.entities.horses.EntityMareBase
        com.animania.common.entities.horses.EntityStallionBase
     >
Also with Animiania, the "OnlyNamed" option should get merged.
Potentially also options to disable override taming of unicorns spawned as tame with no owner, and potentially an option to disable the on-death-taming.


Disable cursorline in vim.diagnostic.open_float?

Just discovered this awesome plug-in today. It's been working great, but I did notice that a cursor line is showing the diagnostic window opened via vim.diagnostic.open_float(). In the image below, the first line of the diagnostic window ("Diagnostics:") has a cursor line showing:

Any suggestions on how to eliminate that? If I place the cursor in the popup and check the filetype it's the empty string "", so I'm stumped.

thanks for reporting this. Should be fixed

Thanks. It works like a charm!


(update) k8s versioning info

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: ________.   Add information about next gen, and issues where collision matters especially around Release name
Jira/GitHub Issue numbers (if any): _____.  https://harnesssupport.zendesk.com/agent/tickets/73790
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://673e5add3f71d987a8056960--harness-developer.netlify.app


Add Barcode Tracking

Hi there,
Is it possible to add barcode tracking using zxing-js? It should be similar to face tracking.

no plan for doing that.  AR.js have something similar to barcode, maybe you can check that out.


Use OpenXLA theming on website.

As has been announced, we'll be moving IREE into the OpenXLA project and GitHub organization (https://github.com/iree-org/iree/issues/12102). This starts to update our documentation (https://iree-org.github.io/iree/ for now, this will change) to more closely match the style of other OpenXLA projects.
As more of the broader OpenXLA project is developed, we'll be tweaking the website to tell a consistent story.

IREE will remain a modular underlying technology
Sections like the blog and user-journey documentation may move to other OpenXLA subdomain websites
Sections like API references may move in (we've had https://github.com/iree-org/iree/issues/5477 sitting for a while)

Demo for review: https://scotttodd.github.io/iree/
Most of these changes are adapted from the draft at https://github.com/iree-org/iree/compare/a420b8d179d39d9741893dd1a7792e75c1e9b083...scottamain:iree:site (demo here).

Accepted changes:

OpenXLA colors for light mode and dark mode
Warning -> Caution, per https://developers.google.com/style/notices#pick-a-notice-type
Use the right "permalink" icon
Style tweaks to mkdocs.yml
New font (Noto: https://fonts.google.com/noto)

Not yet implemented changes:

OpenXLA logo and "homepage" button

We probably want both a way to return to the IREE docs homepage and a way to visit the OpenXLA doc homepage/community page. Maybe two logos? Or a prominent location in the header/footer? Similar to how this TF page has one "home" button for TF and another under it for TFJS:

stackoverflow-[light,dark].css themes for highlightjs (I'm not sure how these should be set up and if we want them yet)
Navigation and page restructuring/reorganization. Some restructuring is needed, but I'm tempted to hold off until more of OpenXLA settles (we might be able to point elsewhere for "getting started with JAX", for example)
No custom header/footer overrides yet

Rejected changes:

"The IREE Authors" -> "The OpenXLA Authors" (IREE has its own AUTHORS file, copyright header, etc.)
Use the same icon for "dark mode -> light mode" and "light mode -> dark mode" (I like the icon showing what the current setting is)
Keeping the ghost emoji glow-on-hover easter egg :P

my 2c: since IREE isn't openxla but a part of it I think having the two logos that link back to each respective homepage makes sense - same with favicons - when you have 30 tabs open being able to quickly identify what's what is really useful

my 2c: since IREE isn't openxla but a part of it I think having the two logos that link back to each respective homepage makes sense - same with favicons - when you have 30 tabs open being able to quickly identify what's what is really useful (that is, if we have the same favicon but different content on our tld that's confusing, as would be clicking the openxla logo but going to the iree site - and they'll always be split as we aren't going to host our own project docs in another repo)

Agreed. Here's a page on the draft site:

The header doesn't say "IREE" at all or have a link to IREE's home
The tab title does have - IREE
The favicon is OpenXLA's

And here's the same page on the site today:

So I think we want to keep the ghost favicon and find some way to get the two logos / homepage links onto the header.

yeah, that'd be great - having consistent branding is good but not at the cost of usability :)

Had some offline discussions about the favicon / logo. Going to standardize on the OpenXLA favicon and logo, but I did add a second header link to IREE's homepage. We're also tweaking some of the favicon details and considering variants for each project.


∆+

https://github.com/ga-dc/curriculum/issues/373

https://github.com/ga-dc/curriculum/issues/374


[Front-End] Design a front-end implementation for a log-in page

We are designing a log-in page for the user to interact with.
Contemplating on what software to handle this rough sketch of a design.
If you have any ideas. Let me know! Otherwise, I will continue on research,

Svelte front end with a Rust backend api. new repo added:
https://github.com/SecurityLogMiner/log-collection-api


Add W&B tracing user guide

An updated form of https://github.com/AntonOsika/gpt-engineer/pull/701 where the tracing/debugging how to would be placed in the user guides

@ATheorell This is the new PR for the W&B user guide for debugging and tracing


Fix version construction for lmfit-c

Possibly with fix this issue.
attn @stuwilkins

Self-merging to see that the constantly appearing error message goes away.

It actually didn't help. Will attempt by updating the Docker image we use for building, see https://github.com/NSLS-II/debian-with-miniconda/pull/18.


VRCX not working

Recently get back to vrc and trying to open VRCX
It load a second but never show up
Tried old ver. still can't open

antivirus blocked it maybe..?

Closing because inactive.


On "Container Console", the underscore character is not visible (it's equal to a whitespace character)

Bug description
On "Container Console", the underscore character is not visible (it's equal to a whitespace character)
I'm using latest Google Chrome (v88). When I use the Container Console, all occurences of the underscore '_' character are shown the same as a whitespace.
Expected behavior
Correctly see the underscore character _
Steps to reproduce the issue:

Go to 'Container Console'
Open a console with some running container
Type some underscore characters
Whitespaces show instead of underscores

Technical details:

Portainer version: 2.1.1
Docker version (managed by Portainer): 20.2
Platform (windows/linux): Linux docker swarm over Debian 10
Browser: Google Chrome 88

Hi
I have a nginx container running, i could see _ in bash and sh
in bash

in sh

pl share the screenshots,

This is from a bash shell in Chrome:
[image: image.png]
I noticed that changing the browser zoom level to 110% makes the
character visible:
[image: image.png]
Maybe is a wrong terminal console font for that size or the console has a
scaled-down viewport?
Thanks
El lun, 15 mar 2021 a las 3:49, balasu @.***>)
escribió:

Hi
I have a nginx container running, i could see _ in bash and sh
in bash
[image: image]
https://user-images.githubusercontent.com/39425180/111097098-df090200-8566-11eb-9d54-ad6c580f5087.png
in sh
[image: image]
https://user-images.githubusercontent.com/39425180/111097117-ecbe8780-8566-11eb-9d5e-3f2bae844280.png
pl share the screenshots,
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/4827#issuecomment-799053449,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOXXWKQJ5X4XEXJQAI4IMLTDVYSZANCNFSM4XEV4HXA
.

--
Mario J. Barchéin Molina
Departamento de I+D+i
@.***
Madrid: +34 911 86 35 46
US: +1 (918) 856 - 3838
Granada: +34 958 07 70 70
――
intelligenia · Intelligent Engineering · Web & APP & Intranet
www.intelligenia.com  · @intelligenia http://twitter.com/intelligenia ·
fb.com/intelligenia · blog.intelligenia.com
Madrid · C/ de la Alameda 22, 28014, Madrid, Spain
https://maps.google.com/?q=C/+de+la+Alameda+22,+28014,+Madrid,+Spain&entry=gmail&source=g
Miami · 2153 Coral Way #400, Miami, FL, US, 33145
@.,-80.2315787,17z/data=!3m1!4b1!4m5!3m4!1s0x88d9b653aaafc4b5:0x6d8501a7341ef2fc!8m2!3d25.7508023!4d-80.22939>
Granada · C/ Luis Amador nº 24, 18014, Granada, Spain
@.,-3.6170297,17z/data=!3m1!4b1!4m5!3m4!1s0xd71fcfb965048e9:0x6849e1627f5b17fd!8m2!3d37.194735!4d-3.614841>
PROTECCIÓN DE DATOS: le informamos que los datos personales y dirección
de correo electrónico, recabados del propio interesado, serán tratados bajo
la responsabilidad de Intelligenia Soluciones Informáticas, S.L. para el
envío de comunicaciones sobre nuestros servicios y se conservarán mientras
exista un interés mutuo para ello. Los datos no serán comunicados a
terceros, salvo obligación legal. Le informamos que puede ejercer los
derechos de acceso, rectificación, portabilidad y supresión de sus datos y
los de limitación y oposición a su tratamiento dirigiéndose a C/ Luis
Amador (Centro de negocios Cámara) 24 , 18014 Granada. Si considera que el
tratamiento no se ajusta a la normativa vigente, podrá presentar una
reclamación ante la autoridad de control en aepd.es.
En cumplimiento de lo previsto en el artículo 21 de la Ley 34/2002 de
Servicios de la Sociedad de la Información y Comercio Electrónico (LSSICE),
si usted no desea recibir más información sobre nuestros  servicios, puede
darse de baja enviando un correo electrónico a @.***  indicando
en el *Asunto *"BAJA" o "NO ENVIAR".

Also, to add information, I'm using Portainer 2.1.1 on Chrome latest version in Linux (Debian buster) with KDE desktop environment. With Firefox on the same environment the underscore is displayed correctly.

Yes i tried on chrome too, I am using chrome Version 89.0.4389.82. could u try upgrading chrome version and try. also try on incognito

I'm already Chrome 89.0.4389.90 (Build oficial) (64 bits). On incognito mode the result is the same, underscore is not shown. I notice that the console font is very thin. On firefox the font is bolder.
Chrome (incognito mode):

Firefox:

its on chrome  89.0.4389.90

pl try clearing cache

Same result after clearing browser cache, underscore is not shown.

pl try a simple nginx container deployed from UI or from a different portainer setup

I am playing with the font settings from my system. I have found that the hinting settings change the visualization of the underscore character. With my previous setting "soft hinting" the problem was there, but changing it to "medium hinting" or "full hinting" solves the problem, so I think it's a combination of the election of the console font and the font hinting settings in my system. This is with full hinting:

The general readability of that font is not very good.
Should it be possible to select a different console font in the embedded terminal?

Sounds like an enhancement and not a bug report, I'll retag it.
We'd accept a contribution for that one!

It looks like changing the default theme it's possible:
https://github.com/xtermjs/xterm.js/issues/1534#issuecomment-404125484
I'll have a look at the contribution guide

Just replacing
term = new Terminal()

with
term = new Terminal({
  fontFamily: 'monospace'
});

at app/docker/views/containers/console/containerConsoleController.js:174 fixes the problem! This uses the default web browser monospaced font:

@deviantony  Is it possible to add this quick fix?

@mbarchein would you be able to open a PR for it?
Otherwise I can see to add it in our backlog but we've got our hands full at the moment.

It works for me :

Create a test container

Log in the console and create a file "demo_test" with underscore

Google Chrome Version : 89.0.4389.90 (Build officiel) (64 bits)

I have been checking my system font configuration. When I disable at the system level the "Courier New" font, the console shows correctly the underscore character at 100% zoom level (it uses some other 'monospace' font from my system). It looks like xterm.js tries to use "Courier New" font by default if it's installed in the system and then another monospaced font as a fallback.
In xterm.js:
src/common/services/OptionsService.ts:
...
fontFamily: 'courier-new, courier, monospace',
...
In Debian buster with KDE the "Courier New" font is very thin and causes this problem (tested on 2 different systems). I will disable it on my computer to fix the problem. This font was obtained from the ttf-mscorefonts-installer official Debian package.
Thanks for your time and support.


feature: French language support

Followed the guide from https://github.com/ntedgi/node-efficientnet/issues/37
Hope it's okay.

Thanks a lot for your contribution please meagre master and solve meagre conflicts


Support malilib 0.11+

Ran into an issue upgrading my mods, as it turns out Watson is pinned to malilib 0.10. Would be nice to see if it could be bumped.
I tried to update build.properties and rebuild myself but ran into Gradle errors I couldn't resolve in the dependency resolution phase.

Duplicate of #22 , i should be able to fix it this weekend since i will have my new pc ready for use again

please update ,to 1.18.1
please..

Watson already works for 1.18.1 @prestig9110 just not with the newest malilib but really soon it should, i need to let it test by some people later

Yes, I noticed that with the old one, as soon as malilib was updated, Watson stopped working for me.
I will be glad if it is updated as soon as possible.
Thanks for the answer

thank


Add keychain auth provider

Motivation:
Support keychain auth on macOS.
Modifications:

Add addOrUpdate API to AuthorizationProvider protocol
Implement KeychainAuthorizationProvider
Move NetrcAuthorizationProvider to Basics and update conformance
Add tests

rdar://83682028

@swift-ci please smoke test

@swift-ci please smoke test

one more thing to add here, or in a follow up PR is a MultiAuthorizationProvider (in lack of a better name) that has an underlying array of AuthorizationProviders and when you call authentication(for url: URL) loops and fetches the auth info from its underlying. And so this is what we can "feed" the workspace, collections which means they dont need to care which provider the auth info came from. wdyt?

one more thing to add here, or in a follow up PR is a MultiAuthorizationProvider (in lack of a better name) that has an underlying array of AuthorizationProviders and when you call authentication(for url: URL) loops and fetches the auth info from its underlying. And so this is what we can "feed" the workspace, collections which means they dont need to care which provider the auth info came from. wdyt?

First, bikeshedding the name... CompositeAuthorizationProvider?
My main concern would be how to handle conflicts. For example, if we have a login mona for github.com in the keychain with one password, and a different password in a .netrc file, which of the following happens?

Only the keychain is used
Only the .netrc file is used
Either the keychain or .netrc is used first, falling back on the other if that fails

If we do 1 or 2, a user could pass --no-keychain or --no-netrc (#3763), but that would be too coarse if credentials are spread equally across providers. If we do 3, we should provide the user a play-by-play with logging statements so that they can understand what's happening.
I also worry that automatically pulling entries in the keychain could be too convenient, and lead to unexpected failures in production / CI environments. It's a kind of invisible global state that, without sufficient logging, the user may not even be aware of its existence.

@tomerd @mattt I added CompositeAuthorizationProvider which takes an array of AuthorizationProviders as argument. If multiple providers have credentials for a given URL, the first one found based on array ordering wins.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


If you jump too high you fly out of the world and can never return

To Reproduce

Hit jump many times to go flying.
 It's possible you are even accelerating (or at least travelling) out into space.
It's like Charlie and the Great Glass Elevator, with the Vernicious Knids, but worse.

Expected behavior
You can't fly out of the world.  Presumably this is a combination of clip plane for the world, but also a bug where jumping suddenly gets stuck on somehow.
Chrome 102 on macOS 12

This should be fixed now. You can't double jump anymore. We will add a fly mode back in shortly.


restructed code to allow for mocks

added mocks

Current dependencies on/for this PR:

main

PR #9   👈

This comment was auto-generated by Graphite.


When there's no title in view scrollspy is disabled

It's working : http://i.imgur.com/mTIIIuh.png
As soon as there's no header, no headline of the scrollspy is shown but I would like the nearest title to be emphasized http://i.imgur.com/YGqNRqI.png

Can you post your code.

https://jsfiddle.net/NitroBAY/opL9axyh/ I don't know why but the table of content isn't  fixed tough

@acburst can you make table of content fixed on the top right ?

I updated my jsfiddle @acburst

You should be placing the scrollspy class on the entire container for which you want it to recognize. Placing them on the titles will end up with very small areas where the scrollspy is active.

Thanks


docs: Remove terraformrc setup obsoleted with Terraform 0.10

Terraform 0.10 doesn't require a custom terraformrc file and the example was removed in https://github.com/coreos/tectonic-installer/commit/16babc9c2dcb933d45a360092e20f0b4b0fd877e.
I didn't touch the metal docs because there's more setup required than terraform init.

@alexsomesan addressed comments (for cloud platforms) and rebased on master.


exit with code 1, signal null

I'm not sure how to get at additional information which will help diagnose the issue.
Happy to provide additional info if you can point me to how to get at it. I can reproduce this consistently.

this popped up for me earlier today as well. except mine is "signal SIGTRAP"


[video_player] Exposed Video URL in Network Requests (Security Concern)

Use case

Use the video_player package to play a video from a URL (e.g., an MP4 or HLS stream).
Inspect the network traffic using an HTTP proxy. (I use this https://apps.apple.com/th/app/webproxytool-inspect-requests/id1578538118)
The full video URL is visible in the request, making it easy for users to extract the URL and misuse it.

final videoPlayerController = VideoPlayerController.network(
    'https://example.com/sensitive_video.mp4'
);

await videoPlayerController.initialize();

Proposal
In the current implementation of the video_player package, video URLs are exposed in network requests, making it easy to extract the video URL using tools like HTTP proxies. This can pose a security risk, especially when streaming sensitive or restricted content.

@knottx
Is it only occuring with video_player plugin only. Can you try the same with native plugin to check if the url is exposed or not ?
Also, can you provide what solution are you proposing ?

@knottx Is it only occuring with video_player plugin only. Can you try the same with native plugin to check if the url is exposed or not ?
Also, can you provide what solution are you proposing ?

@darshankawar I’ve tried using AVPlayer natively on iOS, and the URL is also exposed.

Closing as there is no actionable request here, given that it is about the HTTP spec, which is not controlled by the Flutter team.

Proposal
In the current implementation of the video_player package, video URLs are exposed in network requests, making it easy to extract the video URL using tools like HTTP proxies.

In the future, please provide a proposal in the Proposal section; this is a description of how network requests work, rather than a proposed change or feature.
URLs are an inherent part of a network request; they are what identify the thing being requested. Please see the spec for HTTP requests if you are interested in learning more about the protocol.

This can pose a security risk, especially when streaming sensitive or restricted content.

For content to actually be restricted, that restriction must by definition be on the server side. video_player is client-side, so any system of controlling access to a server-side resource is not in scope.


Remove unneeded zoom style

gave a warning with firefox

Seems to be a leftover from the IE7 times, as per https://github.com/Leaflet/Leaflet/commit/59961216bb6f2a005fcf00b31639922993762569 . Also, see https://developer.mozilla.org/en-US/docs/Web/CSS/zoom and https://caniuse.com/#feat=css-zoom

Closing in favour of https://github.com/Leaflet/Leaflet/commit/0603741cf7322599a5bd4520eaf3ef90e00e9ada - the prefixed CSS property should still work in those super-rare-these-days IE8 browsers.


step timing out sets the reason to TaskRunTimeout instead of Failed

Expected Behavior
When a step of the task hits the timeout specified in that step, I expect the taskRun to exit with Failed reason and the appropriate message saying my-step exited because the step exceeded the specified timeout limit irrespective of whether taskRun timeout is specified or not.
Doc: https://github.com/tektoncd/pipeline/blob/main/docs/tasks.md#specifying-a-timeout
Actual Behavior
TaskRun exits with Failed when a step exceeds the timeout limit. The same step exits with a different reason and message, TaskRunTimeout when an extended timeout is specified in the taskRun  (taskRun timeout > step timeout).
Steps to Reproduce the Problem

Deploy Tekton Pipelines with the latest commit.
Apply TaskRuns to the cluster

kubectl create -f experimental/timeout/step-timeout-without-taskrun-timeout.yaml
taskrun.tekton.dev/step-timeout-without-taskrun-timeout-fhhw2 created

apiVersion: tekton.dev/v1beta1
kind: TaskRun
metadata:
  generateName: step-timeout-without-taskrun-timeout-
spec:
  taskSpec:
    steps:
      - name: sleeping-beauty
        image: bash:latest
        script: |
          #!/usr/bin/env bash
          echo "I am supposed to sleep for 10 second!"
          sleep 10
        timeout: 1s

kubectl create -f experimental/timeout/step-timeout-with-taskrun-timeout.yaml
taskrun.tekton.dev/step-timeout-with-taskrun-timeout-xrn5l created

apiVersion: tekton.dev/v1beta1
kind: TaskRun
metadata:
  generateName: step-timeout-with-taskrun-timeout-
spec:
  timeout: 5s
  taskSpec:
    steps:
      - name: sleeping-beauty
        image: bash:latest
        script: |
          #!/usr/bin/env bash
          echo "I am supposed to sleep for 10 second!"
          sleep 10
        timeout: 1s

Check the taskRuns status:

kubectl get tr step-timeout-without-taskrun-timeout-fhhw2 -o json | jq .status
{
  "completionTime": "2023-02-15T23:47:09Z",
  "conditions": [
    {
      "lastTransitionTime": "2023-02-15T23:47:09Z",
      "message": "\"step-sleeping-beauty\" exited because the step exceeded the specified timeout limit; for logs run: kubectl -n default logs step-timeout-without-taskrun-timeout-fhhw2-pod -c step-sleeping-beauty\n",
      "reason": "Failed",
      "status": "False",
      "type": "Succeeded"
    }
  ],
  "podName": "step-timeout-without-taskrun-timeout-fhhw2-pod",
  "startTime": "2023-02-15T23:47:02Z",
  "steps": [
    {
      "container": "step-sleeping-beauty",
      "imageID": "docker-pullable://bash@sha256:ad93c5cceb1a38ba5b089b6cb839b939a341efe872fbd4eefa027fbe59e95d5d",
      "name": "sleeping-beauty",
      "terminated": {
        "containerID": "docker://92a7266f7e25ee6964308a81c2df40f2daff0eb52eeb1d23cba05f6d3a2c9472",
        "exitCode": 1,
        "finishedAt": "2023-02-15T23:47:08Z",
        "reason": "Error",
        "startedAt": "2023-02-15T23:47:07Z"
      }
    }
  ],
  "taskSpec": {
    "steps": [
      {
        "computeResources": {},
        "image": "bash:latest",
        "name": "sleeping-beauty",
        "script": "#!/usr/bin/env bash\necho \"I am supposed to sleep for 10 second!\"\nsleep 10\n",
        "timeout": "1s"
      }
    ]
  }
}

 kubectl get tr step-timeout-with-taskrun-timeout-vfgrp -o json | jq .status
{
  "completionTime": "2023-02-16T00:14:28Z",
  "conditions": [
    {
      "lastTransitionTime": "2023-02-16T00:14:28Z",
      "message": "TaskRun \"step-timeout-with-taskrun-timeout-vfgrp\" failed to finish within \"5s\"",
      "reason": "TaskRunTimeout",
      "status": "False",
      "type": "Succeeded"
    }
  ],
  "podName": "step-timeout-with-taskrun-timeout-vfgrp-pod",
  "startTime": "2023-02-16T00:14:23Z",
  "steps": [
    {
      "container": "step-sleeping-beauty",
      "name": "sleeping-beauty",
      "terminated": {
        "exitCode": 1,
        "finishedAt": "2023-02-16T00:14:28Z",
        "reason": "TaskRunTimeout",
        "startedAt": null
      }
    }
  ],
  "taskSpec": {
    "steps": [
      {
        "computeResources": {},
        "image": "bash:latest",
        "name": "sleeping-beauty",
        "script": "#!/usr/bin/env bash\necho \"I am supposed to sleep for 10 second!\"\nsleep 10\n",
        "timeout": "1s"
      }
    ]
  }
}

Additional Info

Kubernetes version:
Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.14", GitCommit:"3321ffc07d2f046afdf613796f9032f4460de093", GitTreeState:"clean", BuildDate:"2022-11-09T13:40:19Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:09:57Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"}

Tekton Pipeline version:
Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'

Client version: 0.23.1
Pipeline version: devel

Note the two different conditions for the exact same failure (step timedout):
step-timeout-without-taskrun-timeout:
    {
      "message": "\"step-sleeping-beauty\" exited because the step exceeded the specified timeout limit; for logs run: kubectl -n default logs step-timeout-without-taskrun-timeout-fhhw2-pod -c step-sleeping-beauty\n",
      "reason": "Failed",
    }

step-timeout-with-taskrun-timeout:
    {
      "message": "TaskRun \"step-timeout-with-taskrun-timeout-vfgrp\" failed to finish within \"5s\"",
      "reason": "TaskRunTimeout",
    }

This becomes even more interesting for a task with multiple steps. For example, for a task with two steps, when a first step is expected to be successful and the second step is when the step timeout hits, both the steps have  non-zero exitCode instead of just the second step. But at least, the startedAt is initialized unlike the issue reported in #6174 but the finishedAt for both steps and the taskRun is set to the same value 🙃.
Example taskRun:
apiVersion: tekton.dev/v1beta1
kind: TaskRun
metadata:
  generateName: step-timeout-with-taskrun-timeout-
spec:
  timeout: 10s
  taskSpec:
    steps:
      - name: sleeping-beauty-1
        image: bash:latest
        script: |
          #!/usr/bin/env bash
          echo "I am supposed to sleep for 1 second!"
          sleep 1
        timeout: 3s
      - name: sleeping-beauty-2
        image: bash:latest
        script: |
          #!/usr/bin/env bash
          echo "I am supposed to sleep for 1 second!"
          sleep 1
        timeout: 1ms

In this sample taskRun, the first step should run just fine without any failures and the second step must exit with failure as the timeout is much more lower than the execution time. But the status has both steps marked as failure:
{
  "completionTime": "2023-02-16T20:04:16Z",
  "conditions": [
    {
      "lastTransitionTime": "2023-02-16T20:04:16Z",
      "message": "TaskRun \"step-timeout-with-taskrun-timeout-2gfbg\" failed to finish within \"10s\"",
      "reason": "TaskRunTimeout",
      "status": "False",
      "type": "Succeeded"
    }
  ],
  "podName": "step-timeout-with-taskrun-timeout-2gfbg-pod",
  "startTime": "2023-02-16T20:04:06Z",
  "steps": [
    {
      "container": "step-sleeping-beauty-1",
      "imageID": "docker-pullable://bash@sha256:ad93c5cceb1a38ba5b089b6cb839b939a341efe872fbd4eefa027fbe59e95d5d",
      "name": "sleeping-beauty-1",
      "terminated": {
        "exitCode": 1,
        "finishedAt": "2023-02-16T20:04:16Z",
        "reason": "TaskRunTimeout",
        "startedAt": "2023-02-16T20:04:11Z"
      }
    },
    {
      "container": "step-sleeping-beauty-2",
      "imageID": "docker-pullable://bash@sha256:ad93c5cceb1a38ba5b089b6cb839b939a341efe872fbd4eefa027fbe59e95d5d",
      "name": "sleeping-beauty-2",
      "terminated": {
        "exitCode": 1,
        "finishedAt": "2023-02-16T20:04:16Z",
        "reason": "TaskRunTimeout",
        "startedAt": "2023-02-16T20:04:12Z"
      }
    }
  ],
  "taskSpec": {
    "steps": [
      {
        "computeResources": {},
        "image": "bash:latest",
        "name": "sleeping-beauty-1",
        "script": "#!/usr/bin/env bash\necho \"I am supposed to sleep for 1 second!\"\nsleep 1\n",
        "timeout": "3s"
      },
      {
        "computeResources": {},
        "image": "bash:latest",
        "name": "sleeping-beauty-2",
        "script": "#!/usr/bin/env bash\necho \"I am supposed to sleep for 1 second!\"\nsleep 1\n",
        "timeout": "1ms"
      }
    ]
  }
}

The biggest disadvantage for the users hitting this failure is inability to diagnose since they are loosing the pod, all the containers are terminated and the pod is deleted 😞

This works as expected without taskRun.spec.timeout:
kubectl get tr step-timeout-without-taskrun-timeout-25bfq -o json | jq .status
{
  "completionTime": "2023-02-16T21:26:21Z",
  "conditions": [
    {
      "lastTransitionTime": "2023-02-16T21:26:21Z",
      "message": "\"step-sleeping-beauty-2\" exited because the step exceeded the specified timeout limit; for logs run: kubectl -n default logs step-timeout-without-taskrun-timeout-25bfq-pod -c step-sleeping-beauty-2\n",
      "reason": "Failed",
      "status": "False",
      "type": "Succeeded"
    }
  ],
  "podName": "step-timeout-without-taskrun-timeout-25bfq-pod",
  "startTime": "2023-02-16T21:26:12Z",
  "steps": [
    {
      "container": "step-sleeping-beauty-1",
      "imageID": "docker-pullable://bash@sha256:ad93c5cceb1a38ba5b089b6cb839b939a341efe872fbd4eefa027fbe59e95d5d",
      "name": "sleeping-beauty-1",
      "terminated": {
        "containerID": "docker://547b1f4d9a56a7c9323b519af0bfbaee1b5dfa13c6975d51819a3e6283e83fdc",
        "exitCode": 0,
        "finishedAt": "2023-02-16T21:26:20Z",
        "reason": "Completed",
        "startedAt": "2023-02-16T21:26:19Z"
      }
    },
    {
      "container": "step-sleeping-beauty-2",
      "imageID": "docker-pullable://bash@sha256:ad93c5cceb1a38ba5b089b6cb839b939a341efe872fbd4eefa027fbe59e95d5d",
      "name": "sleeping-beauty-2",
      "terminated": {
        "containerID": "docker://4f008777eecc623fba412f05fa22c52225170a9a4882a5fde96f9f20cdfd92be",
        "exitCode": 1,
        "finishedAt": "2023-02-16T21:26:20Z",
        "reason": "Error",
        "startedAt": "2023-02-16T21:26:20Z"
      }
    }
  ],
  "taskSpec": {
    "steps": [
      {
        "computeResources": {},
        "image": "bash:latest",
        "name": "sleeping-beauty-1",
        "script": "#!/usr/bin/env bash\necho \"I am supposed to sleep for 1 second!\"\nsleep 1\n",
        "timeout": "3s"
      },
      {
        "computeResources": {},
        "image": "bash:latest",
        "name": "sleeping-beauty-2",
        "script": "#!/usr/bin/env bash\necho \"I am supposed to sleep for 1 second!\"\nsleep 1\n",
        "timeout": "1ms"
      }
    ]
  }
}

Hey @EmmaMunley while we are waiting on the timeout https://github.com/tektoncd/community/pull/948, this is something you could try fixing 🙏

@pritidesai @EmmaMunley I am more interested in fixing this issue, can I try to fix it?

/assign


add restype and argtype definitions to libiperf library object.

add restype and argtype definitions to libiperf library object. …
This fixes issue #17

Coverage decreased (-0.8%) to 97.808% when pulling 5f353eb5e8dd7bef4d35a55cba6c7dac09914d25 on illu89:master into cba75c1d71ae0ea598df8179e8f2783c4aff6dc2 on thiezn:master.

For me it solves the issue of getting a segmentation fault also. It would be great to go back to the easy pip install that using @illu89 s fork. So please merge into master

ping ping!
lets get this merged, same issue :)


[Enhancement] Readme Template

Is your feature request related to a problem? Please describe.
When creating an API backend project, it would be useful to have a standardized base template of information we have across projects in the readme. This would take out some of the guess work and time spent by developers when starting a Hack Oregon Project and ensure that projects can be traced back to source datasets, and have clear setup/development documentation
Describe the solution you'd like
I propose we create a readme template within the project repo which would pull in appropriate variables
A non-inclusive list of some areas which should be included:

[ ] project name and description
[ ] hack oregon mission statement
[ ] install steps
[ ] requirements
[ ] data source links and provenance info
[ ] link to contribution guidelines
[ ] links to further documentation (pydocs, swagger, mkdocs, blog posts...)
[ ] link to hack oregon project which uses api
[ ]  badges for any integrations/checks, ie: travis, pypi version, codecov?
[ ] testing/deploy instructions?

Describe alternatives you've considered
Projects are left to organize readme without a clear guide. Information maybe missing or incomplete
Explain how this feature relates to your Hack Oregon project scope.
This adds to the strategic goal of standardized/maintainable APIs, and increases developer productivity

Link to a start of a draft one:
https://github.com/hackoregon/cookiecutter-hacko-backend/blob/v0.1.0/{{cookiecutter.repo_name}}/README.rst
The project i was using as a semi template had used rst, though I am not sure if there is a particular advantage to this:
https://github.com/pydanny/cookiecutter-django
vs just going to markdown?


Add tier 1 areas to local restrictions data

Trello

Add tier 1 restriction data to local_restrictions.yml.
Display 'No tier information' result page to user if a postcode is valid but the restriction is not defined within the YML data.

Tier 1 result

Tier 1 with future restrictions (please note... this is just test data)

No tier information

@leenagupte @kevindew ready for re-review!


-ContentDateFrom -ContentDateTo

what happened to -ContentDateFrom -ContentDateTo

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

ID: 5a6c085b-ef16-d0f6-fd86-dbde22bb5937
Version Independent ID: 3bfb96ec-7789-ce56-6062-df2076dca3b0
Content: New-CaseHoldRule (exchange)
Content Source: exchange/exchange-ps/exchange/policy-and-compliance-ediscovery/New-CaseHoldRule.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@spikedfuel see pull request 1466. Apparently, those parameters were removed.
From an email thread I was on:
I believe that adding a date range to a query-based hold isn’t going to create a time-based hold. It will merely place items that match the query on hold (for example, “hold items that were received between 1/1/2017 and 10/19/2017”). Those items will be placed on hold for as long as the hold is in effect. To remove the hold from those items, the hold needs to be deleted from the corresponding eDiscovery case or by closing or deleting the eDiscovery case. Holds associated with eDiscovery cased are intended to be relatively short-lived, that is for the duration of a legal case or an investigation. When the case/investigation is complete, the case is closed and holds are removed.
The only way to create a “time-based hold” in the Office 365 Security & Compliance Center is by using a retention policy.


Webpack 3 and other perks

This PR include:

webpack 3 upgrade, include scope hoisting in our client build and optimize module loader
remove unnecessary config value
other deps upgrade
fix security issue with font source being loaded from origin with prefix data:

Runs great. Going to merge this and update the Apollo PR with it.


Add Inside to Pointer events

Adds Inside to Pointer, which fires an event while the pointer is inside an entity. It is mostly the Over event, but instead of firing when it enters an entity, it just continues to fire.

This already exists as Move. 🙂

@aevyrie Thanks for the quick response! I created Inside as if you start with the pointer already in an entity, Move doesn't resister. An example is I had an entity follow the cursor on a plane. But, the system could be turned off. So, if turned back on and the pointer is inside the entity, Move doesn't fire an event. Adding Over and Move to do one piece of a whole seems a little verbose. I feel like this for this use case Inside is helpful but, your thoughts about this use case would be insightful!

Maybe an adjustment to how Move works would be better in this case though?

I'm trying to keep the events limited to the events available on the web, simply to keep the available events easy to learn, and prevent them ballooning in quantity. The way the plugin is built, you can add your own Pointer<Inside> event and use it inside your own apps. You could even publish your own crate that adds this behavior on top of this plugin. See the selection crate for example.

That makes sense. After thinking about it more, your take on this makes more sense as Inside offered very little and breaks away from web events. I did not know about adding custom pointer events, so thank you!


ci: Fixed deploy workflow

Pull Request Checklist

[X] Make sure to read the contributor guide here.
[X] Make sure you are making a pull request against the staging branch.
[X] Make sure your pull request title matches the requested format.
[X] Make sure to lint, type-check, and run unit and API tests.

Description
Fixed deploy workflow

:tada: This PR is included in version 2.0.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update overview-patch-os-runtime.md

The registry key to check for the .NET version installed is pointing to NDP\v4\CDF which is for Common Data Forms. The correct path per https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed#detect-net-framework-45-and-later-versions should be HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full.
This caused for one customer to open a support case because it was showing they were using .NET Framework 4.0 when they were really using 4.7 as NDP\v4\Full showed.
Also running 'powershell -command "gci 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full'"' doesn't show the value inside Full, only the values underneath but "reg query" does work, so changing the full command.

#sign-off


Build failure: grafana on aarch64-darwin

Steps To Reproduce
Steps to reproduce the behavior:

nix run nixpkgs#grafana on aarch64-darwin

Build log
$ nix run -L nixpkgs#grafana
grafana> unpacking sources
grafana> unpacking source archive /nix/store/0ncdnawnzfzllb291ci8khkkhrwh4vdv-source
grafana> source root is source
grafana> patching sources
grafana> updateAutotoolsGnuConfigScriptsPhase
grafana> configuring
grafana> building
grafana> wire: github.com/grafana/grafana/pkg/server: wrote /private/tmp/nix-build-grafana-10.2.2.drv-0/source/pkg/server/wire_gen.go
grafana> Building subPackage .
grafana> Building subPackage ./.github/workflows/scripts/kinds
grafana> Building subPackage ./kinds
grafana> package github.com/grafana/grafana/kinds: build constraints exclude all Go files in /private/tmp/nix-build-grafana-10.2.2.drv-0/source/kinds
grafana> Building subPackage ./pkg
grafana> package github.com/grafana/grafana/pkg: build constraints exclude all Go files in /private/tmp/nix-build-grafana-10.2.2.drv-0/source/pkg
grafana> Building subPackage ./pkg/api
grafana> pkg/tsdb/mssql/mssql.go:20:2: cannot find module providing package github.com/microsoft/go-mssqldb: import lookup disabled by -mod=vendor
grafana> pkg/tsdb/mssql/mssql.go:21:2: cannot find module providing package github.com/microsoft/go-mssqldb/azuread: import lookup disabled by -mod=vendor
error: builder for '/nix/store/acvann56zagva3jni5mg8yfwxrfn1vrf-grafana-10.2.2.drv' failed with exit code 1;
       last 17 log lines:
       > unpacking sources
       > unpacking source archive /nix/store/0ncdnawnzfzllb291ci8khkkhrwh4vdv-source
       > source root is source
       > patching sources
       > updateAutotoolsGnuConfigScriptsPhase
       > configuring
       > building
       > wire: github.com/grafana/grafana/pkg/server: wrote /private/tmp/nix-build-grafana-10.2.2.drv-0/source/pkg/server/wire_gen.go
       > Building subPackage .
       > Building subPackage ./.github/workflows/scripts/kinds
       > Building subPackage ./kinds
       > package github.com/grafana/grafana/kinds: build constraints exclude all Go files in /private/tmp/nix-build-grafana-10.2.2.drv-0/source/kinds
       > Building subPackage ./pkg
       > package github.com/grafana/grafana/pkg: build constraints exclude all Go files in /private/tmp/nix-build-grafana-10.2.2.drv-0/source/pkg
       > Building subPackage ./pkg/api
       > pkg/tsdb/mssql/mssql.go:20:2: cannot find module providing package github.com/microsoft/go-mssqldb: import lookup disabled by -mod=vendor
       > pkg/tsdb/mssql/mssql.go:21:2: cannot find module providing package github.com/microsoft/go-mssqldb/azuread: import lookup disabled by -mod=vendor
       For full logs, run 'nix log /nix/store/acvann56zagva3jni5mg8yfwxrfn1vrf-grafana-10.2.2.drv'.

Additional context
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"aarch64-darwin"`
 - host os: `Darwin 23.1.0, macOS 14.1.2`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.18.1`
 - channels(bouke): `""`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

I'm seeing the same error, nix-shell -p nix-info --run "nix-info -m" gives:
 - system: `"aarch64-darwin"`
 - host os: `Darwin 23.1.0, macOS 14.1.2`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

I'm also working in a flake environment rev 95d0067cc02182d7c98bb207ae84f571508382ba.
I attempted to build grafana.overrideAttrs { deleteVendor = true; } as well and it fails for the same reason.

I also confirmed in source that the vendor directories package github.com/microsoft/go-mssqldb and github.com/microsoft/go-mssqldb/azuread don't exist. Perhaps these need to be vendored prior to build?

Flipping back through commits where Grafana was changed, I can get it to compile at Nixpkgs cd723bf928f0b6c33c3d8e968b255074be3b4ce8. That's the parent of this commit which made changes to the grafana derivation
https://github.com/NixOS/nixpkgs/commit/bff4a3526bd871d868a487a008ae47eec8869b3f

@Ma27 I'd like to see if you have any thoughts as to what might have changed with your commit https://github.com/NixOS/nixpkgs/commit/bff4a3526bd871d868a487a008ae47eec8869b3f

Perhaps these need to be vendored prior to build?

The vendor directory will be created in a different derivation, the contents will be copied at the appropriate place before the Go compiler gets invoked. So AFAIU everything should(tm) be there at the time where the build fails according to your logs.
I don't really know about the state of aarch64-darwin support on Grafana upstream. Did you check the issues (and CI builds) there? I may be wrong, but to me this currently seems like an issue in the upstream codebase or one of its dependencies.

Thanks! That’s helpful to know.
I didn’t check upstream, I’m not super familiar with Grafana or Go. Was just doing a quick prototype and was able to get it working with nixpkgs just before your commit but not after.
We’re not moving forward with the prototype so I’m probably not going to keep looking on this issue.

@tel so I got around to taking a first look (sorry that it took me so long!)
One question: when you do nix-build -A grafana.goModules, do you also have a directory called github.com/microsoft~nix~case~hack~1 in your result directory? That's most likely the explanation for that.
Please confirm that I'm not off chasing a different issue. But if that's the case, then we probably found a Nix bug that needs to be reported upstream.

I'm on a flake-based system, so I ran nix build nixpkgs#grafana.goModules. Nevertheless, the path result/github.com/microsoft~nix~case~hack~1/go-mssqldb did get generated. Hopefully that's helpful!

I'm on a flake-based system, so I ran nix build nixpkgs#grafana.goModules

FWIW it doesn't matter whether or not you're using flakes (I'm too in fact), you can still use nix-build on local git checkouts.
Anyways, as I said, I'm pretty sure that this is a Nix bug. I'll open a bug over there.

I think this is probably triggered by the fact that some of the go modules grafana depends on use Microsoft and others 'microsoft' for the organization name: https://github.com/grafana/grafana/blob/b5d14d03d7388894bbee47a93f25707539ff1519/go.mod#L437

@Ma27 I got it building for both aarch64 and x86_64 darwin, see the override. To read more about how I got it to build, you can refer to comments, starting from here.

I am open to upstreaming it to nixpkgs, if that’s desired.

@shivaraj-bh would you mind checking if https://github.com/NixOS/nixpkgs/pull/292997 solves the core issue for you (you'll probably need to adjust yarn's supported systems locally, but other than that there shouldn't be much to do).
Because if that's the case, that'd be my preferred solution (and another argument in favor of that patch).

@Ma27 If I just add the darwin cache for yarn, it fails at:
 > Building subPackage ./pkg/cmd/grafana
       > pkg/tsdb/mssql/mssql.go:22:2: cannot find module providing package github.com/microsoft/go-mssqldb: import lookup disabled by -mod=vendor
       > pkg/tsdb/mssql/mssql.go:23:2: cannot find module providing package github.com/microsoft/go-mssqldb/azuread: import lookup disabled by -mod=vendor

Which is the same issue as reported by OP. To solve this, I had used proxyVendor = true;. When I use this the go-modules no longer have the github.com/microsoft\~nix\~case\~hack\~1 anymore, but there is github.com/microsoft and github.com/!microsoft.  I am guessing proxyVendor somehow works around the case-insensitivity problem.

This patch on your fork helps me build grafana on darwin:
diff --git a/pkgs/servers/monitoring/grafana/default.nix b/pkgs/servers/monitoring/grafana/default.nix
index 00688dc0aec8..f18e32296c20 100644
--- a/pkgs/servers/monitoring/grafana/default.nix
+++ b/pkgs/servers/monitoring/grafana/default.nix
@@ -36,6 +36,8 @@ buildGoModule rec {

   subPackages = [ "pkg/cmd/grafana" "pkg/cmd/grafana-server" "pkg/cmd/grafana-cli" ];

+  excludedPackages = [ "xorm" ];
+
   src = fetchFromGitHub {
     owner = "grafana";
     repo = "grafana";
@@ -58,7 +60,7 @@ buildGoModule rec {
       export HOME="$(mktemp -d)"
       yarn config set enableTelemetry 0
       yarn config set cacheFolder $out
-      yarn config set --json supportedArchitectures.os '[ "linux" ]'
+      yarn config set --json supportedArchitectures.os '[ "linux", "darwin" ]'
       yarn config set --json supportedArchitectures.cpu '["arm", "arm64", "ia32", "x64"]'
       yarn
       runHook postBuild
@@ -67,12 +69,14 @@ buildGoModule rec {
     dontInstall = true;
     dontFixup = true;
     outputHashMode = "recursive";
-    outputHash = "sha256-70eMa8E483f/Bz7iy+4Seap1EfIdjD5krnt6W9CUows=";
+    outputHash = "sha256-pqInPfZEg2tcp8BXg1nnMddRZ1yyZ6KQa2flWd4IZSU=";
   };

   disallowedRequisites = [ offlineCache ];

-  vendorHash = "sha256-nGv/DBNnQ4AOJtrsYIGLCrV1xNmBN0dDf6u46R3TAHo=";
+  proxyVendor = true;
+
+  vendorHash = "sha256-Ig7Vj3HzMVOjT6Tn8aS4W000uKGoPOCFh2yIfyEWn78=";

   nativeBuildInputs = [ wire yarn jq moreutils removeReferencesTo python3 ];

@@ -91,10 +95,6 @@ buildGoModule rec {
     GOARCH= CGO_ENABLED=0 go generate ./public/app/plugins/gen.go
     GOARCH= CGO_ENABLED=0 go generate ./pkg/kindsys/report.go

-    # Work around `main module (github.com/grafana/grafana) does not contain package github.com/grafana/grafana/pkg/util/xorm`.
-    # Apparently these files confuse the dependency resolution for the go builder implemented here.
-    rm pkg/util/xorm/go.{mod,sum}
-
     # The testcase makes an API call against grafana.com:
     #
     # [...]

rant: grafana check takes longer time than the build itself

Yeah, known issue.
https://github.com/NixOS/nixpkgs/pull/292997 is a potential fix (at the cost of skipping all tests).
See also https://github.com/NixOS/nixpkgs/issues/285362 & https://github.com/NixOS/nixpkgs/pull/284568

@shivaraj-bh would you mind rebasing your changes onto master and PR them? Grafana is now a little more pleasant to work with given that it builds way faster and I this should probably be fixed (with or without a proper fix in Nix).
Also, broken Darwin appears to have unintended side-effects for Hydra: https://github.com/NixOS/nixpkgs/pull/296193#issuecomment-2012141884

would you mind rebasing your changes onto master and PR them?

Will do

Well, grafana 0.4.0 received a lot of changes, so I had to fix a few more issues, but the PR is finally ready ^


sync nmdc.yaml with nmdc-metadata repo

The nmdc.yaml in the nmdc-metadata repo changed. Need to sync schemas.

See https://github.com/microbiomedata/nmdc-metadata/commit/6c4ed996d5507c60d74688679a3859c05b527dbc for changes made by @chienchi

Note: These definitions have now been moved to workflow_execution_activity.yaml in the nmdc-schema repo.


Empty commit_sig

Background
This looks a lot like #1127. I don't know what is the version of lnd but considering the node first appeared a month ago I suppose it should have the fix, so maybe this is something different?
Your environment

version of lnd: unknown, node is fairly.cheap 03cb7983dc247f9f81a0fa2dfa3ce1c255365f7279c8dd143e086ca333df10e278

Steps to reproduce
 eclair               lnd
   |                   |
   |        ...        |
   |                   |  <--- 4 cross-signed htlcs eclair->lnd
   |                   |
   |<----- ful-1 ------|
   |<------ sig -------|
   |<----- ful-2 ------|
   |<----- ful-3 ------|
   |<----- ful-4 ------|
   |------- rev ------>| <--- eclair acks ful-1
   |------- sig ------>| <--- eclair signs ful-1
   |<------ sig -------| <--- lnd signs ful-2 + full-3 + ful-4
   |------- rev ------>| <--- eclair acks ful-2 + full-3 + ful-4
   |------- sig ------>| <--- eclair signs ful-2 + full-3 + ful-4
   |<------ sig -------| <--- this signature doesn't include anything new
   |------- err ------>| <--- cannot sign without changes!
   |                   |

Not much we can go off here if we don't know which version the node was running on, as we've fixed issues similar to this in the past. Although, on the implementers call today, I think Rusty was saying that they found a version of lnd would still send them under stress tests? However, again there, we're not sure what version they were testing agaisnt.

It does look like we should've just sent a revoke there at the end though...there're generally some corner cases in the state machine w.r.t concurrent updates which we may not implement identically right now.


Missing SDK support and .Net framework version for OS Family 7

OS Family 7 misses supported SDK version (under the "SDK support" heading) and ".NET Framework installed" (under the "Family 7 releases" heading)

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

ID: d7e4add3-448c-8bd4-3a47-bb7ae25970db
Version Independent ID: 4fe15edb-81b7-6122-829b-7a321a72e3bf
Content: Learn about the latest Azure Guest OS Releases
Content Source: articles/cloud-services/cloud-services-guestos-update-matrix.md
Service: cloud-services
Sub-service: auto-os-updates
GitHub Login: @ibthampy
Microsoft Alias: ibthampy

@austvik Thank you for your feedback!  We will review this and update you shortly.

Thanks for providing feedback that helps improve our documentation. This issue has been resolved and we are closing the issue. #please-close


Share $app['query.parser'] before extending

Prevents breakage on Bolt 3.3

This PR needs some work. Hold off on merging, @xiaohutai :-)

#55 covers what this misses, this is correct.

@GawainLynch The two of them combined are confirmed working for me, too! 👍


WIP: Adding snapshot data tests for Grid Transmissibility.

Codecov Report

Merging #286 (eb76e56) into integration (a479cc1) will increase coverage by 0.39%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           integration     #286      +/-   ##
===============================================
+ Coverage        59.22%   59.61%   +0.39%
===============================================
  Files               59       59
  Lines            26339    26308      -31
===============================================
+ Hits             15598    15684      +86
+ Misses           10741    10624     -117

Impacted Files
Coverage Δ

resqpy/olio/simple_lines.py
40.65% <0.00%> (-0.48%)
:arrow_down:

resqpy/olio/wellspec_keywords.py
66.66% <0.00%> (-0.31%)
:arrow_down:

resqpy/olio/keyword_files.py
41.80% <0.00%> (-0.13%)
:arrow_down:

resqpy/olio/factors.py
97.14% <0.00%> (-0.08%)
:arrow_down:

resqpy/lines.py
70.22% <0.00%> (-0.04%)
:arrow_down:

resqpy/olio/triangulation.py
92.62% <0.00%> (-0.04%)
:arrow_down:

resqpy/grid_surface.py
80.55% <0.00%> (-0.03%)
:arrow_down:

resqpy/olio/vdb.py
10.60% <0.00%> (+0.01%)
:arrow_up:

resqpy/well.py
53.04% <0.00%> (+0.04%)
:arrow_up:

resqpy/fault.py
61.77% <0.00%> (+0.05%)
:arrow_up:

... and 7 more

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 a479cc1...eb76e56. Read the comment docs.


Dashboard: Feeds Types Chart

Description
Adjusted feeds types chart, now it shows all active honeypots
Related issues
close #95
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist

[x] I have read and understood the rules about how to Contribute to this project
[x] The pull request is for the branch develop
[ ] I have added documentation of the new features.
[ ] The tests gave 0 errors.
[x] Linters (Black, Flake, Isort) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
[ ] The commits were squashed into a single one (optional, they will be squashed anyway by the maintainer)
[ ] If changes were made to an existing model/serializer/view, the docs were updated and regenerated (check CONTRIBUTE.md).

Important Rules

If your changes decrease the overall tests coverage (you will know after the Codecov CI job is done), you should add the required tests to fix the problem
Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review

Edit: getRandomColorsArray is a function from the certego-ui, it's correct to not test it.


bump: scalafmt-core 3.0.8 (was 2.7.5)

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

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

labels: library-update, early-semver-major, semver-spec-major

This requires some scalafmt configuration updates.

Superseded by #155.


ci(publish): removed github job & installed dependency

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to simulate TLS 1.0 vulnerability breach on Azure storage account?

Yes, Everywhere we see recommendations to update the TLS version, However, it would be nice to see what can go wrong if Azure storage is set to TLS 1.0. This helps to understand the problem before upgrading to TLS to latest version
Reason: we have to provide a valid rationale to the operational team for upgrading the TLS version. Our storage account access is secured so why do we need to upgrade?

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

ID: 0d6c9dfa-cb51-8e98-ce3e-68cfeb50c9dd
Version Independent ID: 5364e068-0237-bbfd-e8a3-cb83ed210585
Content: Enforce a minimum required version of Transport Layer Security (TLS) for incoming requests - Azure Storage
Content Source: articles/storage/common/transport-layer-security-configure-minimum-version.md
Service: storage
Sub-service: common
GitHub Login: @jimmart-dev
Microsoft Alias: jammart

Thanks for the feedback! We are currently investigating and will update you shortly.

@kudlatiger Here is a Microsoft doc that explains issues with TLS1.0 version- https://docs.microsoft.com/en-us/security/engineering/solving-tls1-problem
Hope this helps. Please let us know if you have any further questions. Thank you!

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Add steps to fix common error to README.md

This is related to #472.
Just some extra information for new users so they don't have to do dig in issues.
Thanks for the help @RobinHirst11

Add a "FAQ" section below the "Configuration" section in README.md instead.

Done @ayn2op !!!


chore: fix deprecated IntegrationTest

IntegrationTest currently not working on my IDEA, It keeps complaining about NoClassFound.
After following the changes in the sbt release notes guidance, it works fine on my IDEA: https://eed3si9n.com/sbt-1.9.0

Any idea why the Check Code Style CI build is failing when it is looking for pekko-persistence-jdbc-core? This jar seems never to have been published before.


When setting to small window in mattermost, SENT video quality gets reduced

Mattermost Version - latest docker images
Plugin Version - 2.0.0
Describe the issue
When using jitsi from within mattermost in the full screen overlay, quality gets SENT at ~1024x550, when i shrink to using the corner overlay the SENT drops to ~300x200. I believe this is a bug and the send quality should stay the same but perhaps the receive quality should get lowered.

Yes, totally agree, the intention was to reduce the receive video quality instead of the sent video quality, I'll take a look into this and I think we can create a 2.0.1 release for that. Thanks for the feedback.

Now I see it, the video quality for receive/sent is set in the same call in the Jitsi external API, so is not possible to set the input video quality without setting the output video quality to the same value (from the external API perspective) I think the most sensible approach is to remove that change, and talk with Jitsi people to see if they can split that in the API or any other solution.

This is now fixed on master.

thanks, I have raised an issue in jitsi repository above


Resource creation failed

Setup:

DSC branch 386 on port 8080
UI branch DSC on port 8082 connected to 8080 backend

Creation of a resource failed
Log_UI.txt
DSC Log:
2021-07-15T21:53:04,914 [https-jsse-nio-8080-exec-4] WARN - Invalid input. [exception=(Cannot deserialize value of type java.net.URI from String "http://": not a valid textual representation, problem: Expected authority at index 7: http://\n at [Source: (PushbackInputStream); line: 1, column: 73] (through reference chain: io.dataspaceconnector.model.resource.OfferedResourceDesc["publisher"]))]

Failed because publisher was "http://" which is not a valid URL.
URL validation adjusted to require at least one character (not space) after the protocol.
Fixed in 43baf41


Overlapping location markers

We match different location types based on addresses, but some location types are not quite a match and would be difficult to match for in a programmatic and reliable way. For example:
Yakima County Courthouse Security Station
128 N 2nd St
Yakima WA 98901
Yakima County Auditor's Office
128 N 2nd St Rm 117
Yakima WA 98901
Here it's unclear whether it's even desirable to be consolidating the two locations because while they have almost exactly the same address they're likely distinct locations. The current functionality of the tool will classify these as separate locations.
When we use the Google Maps API to geocode the addresses in order to place the markers on the map, the geocoder will return the exact same coordinates for the two locations, so that when we place them on the map they'll be overlapping and one will be obscuring the other. You can see this on the live tool by entering EID 4100 and the address 412 S 35th Ave Yakima WA 98902. One of the location types overlaps the other so you can't see that there are actually two separate locations there, which is confusing to the user and obscure information.
One way we can solve this is by 'nudging' the markers by a small amount so that they're not obscured by each other but still represent an accurate enough location on the map. If we nudge a location a small enough amount so that it's no more than say 10-20 feet away from its geocoded location, we can allow users to see these non-matched locations. Additionally, this would go a long way in terms of insurance for the types of issues like #171, #169.
@acohen84 Let me know if you'd like to move forward with this.

Thanks Alex.  Can you explain nudging a little bit?  When would this be triggered and how far on the map would the nudge be?

Here's an example with nudging:

And without:

Because those two addresses are basically the same location, Google Maps will give us the exact same coordinates. When we nudge it we randomly add or subtract a very small amount (~0.000001) to the degrees of the latitude and longitude. I'm not a cartography expert but from what I've tried in different locations around the USA and what I've read from some GIS resources, it shouldn't be more than 10-20 feet. The degrees don't convert exactly to feet or miles so I can't give you a specific definite answer for that (I think because of the curvature of the Earth), but if you need it to be under a specific amount I can confirm that. From my initial tests the nudging would be triggered for every location, but we could also consider an option to just do it for locations within a certain distance to each other.
My apologies if that's a little vague, but I wanted to get your thoughts on this because I believe it would get us much closer to definitively resolving location display issues.

This is super helpful!  Is nudging done manually?  If not, how does the tool recognize when nudging is necessary.

@MariaBianchi

If it's interpreted by Google Maps as the same location (like the Yakima example above) their distance from each other will basically be 0 feet, so we could just check for that. Alternatively we could use a threshold (say < 20-50 feet or something like that).

I'd prefer to only implement if the distance is 0 ft.  Let's go that path.


Support chromecast streaming

https://www.npmjs.com/package/chromecast-api

Possible background color: https://github.com/davidkrantz/Colorfy

I've did a little research on this and https://www.npmjs.com/package/chromecast-api is not a browser version. It supports only pure node environment (needs tls and fs libs).
You could use https://www.npmjs.com/package/react-chromecast but:

it works only on chrome-based browsers
you need DEFAULT_MEDIA_RECEIVER_APP_ID

There is also an option to use Cast SDK https://developers.google.com/cast/docs/web_sender/integrate which is also available only for chrome-based browsers

Could you assign me to this task?


WIP Move websocket upgrade later in state machine

This allows for hooks to be applied to ws requests before upgrade

[approve ci autest]


Content generation (e.g., table) from data models (data class)

Had a conversation with @strogonoff and he thinks the term "internal registry" is confusing because it sounds like an ISO 19135 registry. Maybe "structured dataset"?


jps.txt and process-list.txt exposes keystorePass in plaintext

jps.txt and process-list.txt displays the commandline of all java processes includes the elasticsearch-support-diagnostics commandline which may include the --keystorePass argument. It needs to be scrubbed.

It's now a prompt on the command line like the standard password prompt.


error when accessing offset attribute of LocalDateTime

A LocalDateTime object should either supply a valid .offset or refuse access to this attribute. It reports, however, a missing microseconds attribute. Example:
In [1]: from whenever import LocalSystemDateTime
In [2]: now = LocalSystemDateTime.now()
In [3]: now.offset
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
...
File /tmp/venv-we/lib/python3.12/site-packages/whenever/__init__.py:1019, in TimeDelta.from_py_timedelta(cls, td)
...
AttributeError: 'NoneType' object has no attribute 'microseconds'

It's actually possible though to obtain the offset through “naive” conversions:
In [4]: now.naive() - now.as_utc().naive()
Out[4]: TimeDelta(02:00:00)

Which is what I would expect from .offset in the first place – or an AttributeError for .offset.

@detlefla thanks for reporting, this is most definitely a bug. I'll get around to fixing this ASAP

I've found the cause of the problem and a fix will be out shortly

@detlefla release 0.5.1 is now out with the fix. 🙏 thanks for reporting this!


feat(knxproject-explore): Added knxproject explorer

Added KNXProject Explorer
Changed html structure and CSS on info
Added progress spinner on info during loading from websocket

ATTENTION: Depends on https://github.com/home-assistant/core/pull/100676/

I did give this a quick try, here are my considerations:

the "Explore" tab should be hidden when there is no project uploaded yet
I think we should find a more concise name for the tab. In mobile view most of it is not visible 😬 Maybe just "Project", "Group Addresses", or something like this.

the highlight-color is too dark - the text is unreadable at mouseover

Just an idea for a future PR:

Maybe we can merge the "Info" tab and the new explorer tab in some way. Currently most of Info is project related and the rest is available as entities (connection and IA).

Regarding comments from @farmio:

[ ]  the "Explore" tab should be hidden when there is no project uploaded yet

I would lift KNXInfoData one level up on knx-router - we need to know already there if project is loaded - else we have to do the API call IMHO on every tab switch. --> If OK: Feature request for next PR.

[x]  I think we should find a more concise name for the tab. In mobile view most of it is not visible 😬 Maybe just "Project", "Group Addresses", or something like this.

Using "ETS Project" - renders also quite ok on mobile.

[x]  the highlight-color is too dark - the text is unreadable at mouseover

[ ]  it would be nice if we could show some more information about GAs - most of all DPT.

Fully agree --> styling and information density is far from where it should be --> again: next PR?

[x]  the Explore button on the Info / Project card is redundant with the tab above

Fixed --> removed the button.

it would be nice if we could show some more information about GAs - most of all DPT.

We should probably postpone this to a separate PR.

And thank you very much @mueli 👍


In-depth Component Guides

After https://github.com/PaperMC/docs/pull/145, there are more pages that should exist in the Component API category, diving into specific integrations between adventure and the paper api.
- [ ] Cover all adventure interfaces implemented by Paper API types
- [ ] Demonstrate the use of AsyncChatEvent, specifically the ChatRenderer
- [ ] Demonstrate the use of SignedMessage
- [ ] Demonstrate resolving Components (`PaperComponents#resolveWithContext`)
- [ ] Demonstrate BookMetaBuilder
- [ ] Demonstrate click event callbacks
- [ ] https://github.com/PaperMC/docs/pull/194

I think point 2 can be marked as done due to #264.


[CVP] [$250] Free trial of workspace mentioned in welcome message when user have no workspace

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

Version Number: 9.0.13-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1722036482639849
Action Performed:

Go to staging.new.expensify.com
Create a new account and select Track in onboarding
Click the global + > Track
Choose the Submit to someone actionable mention

Expected Result:
No mention about free trial workspace in concierge message
Actual Result:
Mentioned about workspace in the message even if the user not created a workspace
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos

https://github.com/user-attachments/assets/527eb864-77f2-427c-8a62-3721bebf7913
Add any screenshot/video evidence

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

Upwork Job URL: https://www.upwork.com/jobs/~01aa51c694d41de340
Upwork Job ID:<PHONE_NUMBER>692441626
Last Price Increase: 2024-08-06

Issue OwnerCurrent Issue Owner: @situchan

Awaiting proposals

I think it is a backend issue

I can only repro this in the Track > Submit someone flow:
https://github.com/user-attachments/assets/0647fd64-0e7a-4cb8-87bc-ab98e15adf29
Looks like we call OpenWorkspace in the ConvertedTrackedExpenseToRequest flow (logs for that API call), and I'm not sure why @thienlnam?
OpenWorkspace Logs
[<IP_ADDRESS>->/api.php] Malformed REQUEST: 'policyID' = '-1', ignoring (should match '[A-F0-9]+').

CC: @chiragsalian for visibility on free trial stuff.

This looks like an internal bug. Looks like jack's already got a PR for this.

Auth and Web PRs for this now merged, awaiting deploys.

Doe this still need to be open? It looks like they both merged above.

Yup, looks resolved now


feat(data-classes): Active MQ & Rabbit MQ as an event source for AWS Lambda

Issue #, if available:

#756

Description of changes:

[x] - add active mq data class
[x] - add rabbit mq data class
[x] - update docs
[x] - add fixtures
[x] - complete test coverage

Rabbit MQ example:
from typing import Dict

from aws_lambda_powertools import Logger
from aws_lambda_powertools.utilities.data_classes import event_source
from aws_lambda_powertools.utilities.data_classes.rabbit_mq_event import RabbitMQEvent

logger = Logger()

@event_source(data_class=RabbitMQEvent)
def lambda_handle(event: RabbitMQEvent, context):
    for queue_name, messages in event.rmq_messages_by_queue.items():
        logger.debug(f"Messages for queue: {queue_name}")
        for message in messages:
            logger.debug(f"MessageID: {message.basic_properties.message_id}")
            data: Dict = message.json_data
            logger.debug("Process json in base64 encoded data str", data)

Active MQ example:
from typing import Dict

from aws_lambda_powertools import Logger
from aws_lambda_powertools.utilities.data_classes import event_source
from aws_lambda_powertools.utilities.data_classes.active_mq_event import ActiveMQEvent

logger = Logger()

@event_source(data_class=ActiveMQEvent)
def lambda_handle(event: ActiveMQEvent, context):
    for message in event.messages:
        logger.debug(f"MessageID: {message.message_id}")
        data: Dict = message.json_data
        logger.debug("Process json in base64 encoded data str", data)

Checklist

[x] Meet tenets criteria
[x] Update tests
[x] Update docs
[x] PR title follows conventional commit semantics

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@heitorlessa  - this one is also good to go