text:
Garage Door Opener is showing as cover instead of switch and missing binary sensor

Describe the bug
Garage Door Opener is showing as cover instead of switch and missing binary sensor
Expected behavior
Garage Door Open is meant to have a switch and binary sensor
Screenshots

Home Assistant Version

e.g. 2021.11.0

Same as #659?

Same case, my Lomota Garage Door Opener is showed as cover and no binary sensor. It opens (down arrow) but don't close (up arrow) :( (Core 2021.11.0 but also on 2021.11.1)

I experience this same issue, my Lomota Garage Door Opener (Smart WiFi Garage Door Opener) is showed as cover and no binary sensor. It opens (down arrow) but doesn't close (up arrow) :( (Core 2021.11.0 but also on 2021.11.1)

I too have the same behaviour as @Xwandroid

Same exact issue as above. Wofea garage door controller

@sambarlick raised a feature request. Go vote: https://community.home-assistant.io/t/tuya-garage-door-opener-kogan-smart-wireless-garage-door-opener/355905

I can confirm that this is still an issue with HA 2022.3.8 for Smart Garage Door Opener using Tuya category=ckmkzq.  According to Supported Tuya Device Category that category is supported by Tuya integration (through Tuya IoT Platform).  The symptom is different in that the device is detected in HA but no entities are created.
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2022.3.8",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.9.9",
    "docker": true,
    "arch": "x86_64",
    "timezone": "America/Chicago",
    "os_name": "Linux",
    "os_version": "5.10.108",
    "supervisor": "2022.03.5",
    "host_os": "Home Assistant OS 7.6",
    "docker_version": "20.10.9",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {},
  "integration_manifest": {
    "domain": "tuya",
    "name": "Tuya",
    "documentation": "https://www.home-assistant.io/integrations/tuya",
    "requirements": [
      "tuya-iot-py-sdk==0.6.6"
    ],
...
  "data": {
    "endpoint": "https://openapi.tuyaus.com",
    "auth_type": 0,
    "country_code": "1",
    "app_type": "smartlife",
    "mqtt_connected": true,
    "disabled_by": null,
    "disabled_polling": false,
    "name": "Main Garage Door",
    "model": "GD801",
    "category": "ckmkzq",
    "product_id": "vPxZSdMT8rtymUjf",
    "product_name": "Smart Wi-Fi Garage Door Opener",
    "online": true,
    "sub": false,
    "time_zone": "-06:00",
    "active_time": "2022-03-26T19:08:46+00:00",
    "create_time": "2022-03-26T19:08:46+00:00",
    "update_time": "2022-03-26T19:09:44+00:00",
    "function": {},
    "status_range": {},
    "status": {},
    "home_assistant": {
      "name": "Main Garage Door",
      "name_by_user": null,
      "disabled": false,
      "disabled_by": null,
      "entities": []
    }
  }

Side note for @cralwalker : the feature request linked above IMO is not relevant to this bug because that is for Tuya product category "mc" which is clearly NOT listed on Supported Tuya Device Category .

repo: tuya/tuya-home-assistant


text:
Custom hightlight in right bar;

Hallo!
Our Company need the ability to create additional "highlights" in a right bar.
We are ready to consider a variant with payment.
Best wishes;

Hi @Hork190 ,
This repo is not maintained by the author at the moment.
I don't know what you meant by "highlights", but anything can be added and modified in the chart and of course, any toolbars can be added externally to the chart as well.

This is "HIGHTLIGHT" uderstand me?

source: gharchive/issue

repo: tvjsx/trading-vue-js

license: MIT

license_type: permissive

license_source: github-api


text:
Bootstrap icons in sass file not working !!

The issue is beacuse there need to be double colon(" ") or single colon(' ') on each icon code. Currently only first two icons have double colons.
stylesheets\bootstrap_glyphicons.scss

duplicate of #15780

@patrickhlauke ok thanks :) ...  didn't see that...

authors: adarshmahe patrickhlauke

repo: twbs/bootstrap


text:
input-group is too long when used in form-horizontal

When using a horizontal form, input groups end up being longer than their sibling fields. I've created https://jsfiddle.net/z0L72nn1/1/ to demonstrate on the latest 3.3.5 bootstrap.

Hi @chrisbloom7!
You appear to have posted a live example (https://fiddle.jshell.net/z0L72nn1/show/light/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 46, column 5: W012: .container or .container-fluid should be the first child inside of a .navbar
line 15, column 7: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.0.0
line 19, column 7: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.0.0

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

Revised - Switched to Bootstrap 3.3.4 to avoid bootlint errors. Removed wrapping .container
https://jsfiddle.net/z0L72nn1/2/

Hi @chrisbloom7!
You appear to have posted a live example (https://fiddle.jshell.net/z0L72nn1/2/show/light/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 45, column 3: E003: Found one or more .rows that were not children of a grid column or descendants of a .container or .container-fluid
line 56, column 9: E012: .input-group and .col-*-* cannot be used directly on the same element. Instead, nest the .input-group within the .col-*-*
line 68, column 9: E012: .input-group and .col-*-* cannot be used directly on the same element. Instead, nest the .input-group within the .col-*-*

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

.input-group and .col-- cannot be used directly on the same element

Oh, well, you should update your docs. Also, how can W012 and E003 both be true? It's what http://getbootstrap.com/examples/grid/ uses...

@chrisbloom7 not sure I follow you. W012 is .container or .container-fluid should be the first child inside of a .navbar and E003 is Found one or more .rows that were not children of a grid column or descendants of a .container or .container-fluid.
Both of those are followed in the example page. Individual examples of components are not representations of how they should be deployed in production (e.g. you shouldn't copy and paste the examples/grid page as your entire page and expect that to be correct). For fully accurate examples in context use the provided examples found here: http://getbootstrap.com/getting-started/#examples

.input-group and .col-- cannot be used directly on the same element

Oh, well, you should update your docs.

Guess what, we don't need to, because they already explicitly mention this: http://getbootstrap.com/components/#callout-inputgroup-dont-mix
Try reading more carefully in the future :smile:

@cvrebert, ah, thank you for pointing that out. I've got 3 bootstrap tabs open and I feel like I scoured them pretty thoroughly, as well as googled for the solution. Seems like I wasn't thorough enough. Consider me corrected.
@kkirsche The grid page is from the examples section, so i'm not sure what I should be using for reference if not that. The entire grid page is wrapped with a .container, and E003 says a .row must be in a .container, but W012 says .container is only valid as the first child inside of a .navbar. How can both be true? Additionally, http://getbootstrap.com/css/#grid-intro says "Rows must be placed within a .container (fixed-width) or .container-fluid". The linter seems to contradict this.
Secondarily, I first got a W013 error even though I was using 3.3.5, which is the latest according to http://getbootstrap.com/getting-started/#download, but the linter complained and I ended up having to downgrade to 3.3.4 in my example.

but W012 says .container is only valid as the first child inside of a .navbar

You have that a little backwards. The only valid first child of .navbar is a container. But containers have uses other than in navbars.
Perhaps we ought to rephrase W012 to clarify this.

Secondarily, I first got a W013 error even though I was using 3.3.5, which is the latest according to http://getbootstrap.com/getting-started/#download, but the linter complained and I ended up having to downgrade to 3.3.4 in my example.

Did you edit the GitHub issue description after you posted it? Your description currently mentions https://jsfiddle.net/z0L72nn1/1/ , but @twbs-lmvtfy's comment mentions  (https://fiddle.jshell.net/z0L72nn1/ . Note the lack of the trailing /1.

Hi @cvrebert!
You appear to have posted a live example (https://fiddle.jshell.net/z0L72nn1/show/light/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 46, column 5: W012: .container or .container-fluid should be the first child inside of a .navbar
line 15, column 7: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.0.0
line 19, column 7: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.0.0

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

Hi @cvrebert!
You appear to have posted a live example (https://fiddle.jshell.net/z0L72nn1/1/show/light/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 56, column 11: E012: .input-group and .col-*-* cannot be used directly on the same element. Instead, nest the .input-group within the .col-*-*
line 68, column 11: E012: .input-group and .col-*-* cannot be used directly on the same element. Instead, nest the .input-group within the .col-*-*

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

Did you edit the GitHub issue description after you posted it? Your description currently mentions https://jsfiddle.net/z0L72nn1/1/ , but @twbs-lmvtfy's comment mentions (https://fiddle.jshell.net/z0L72nn1/ . Note the lack of the trailing /1.

I'm a dolt. An angry, angry dolt. Yes, I originally submitted it with https://fiddle.jshell.net/z0L72nn1/, then realized it was showing some old code that I forked so I updated the jsfiddle and edited the issue to use the new link. It was only afterward that the @twbs-lmvtfy comment appeared, so I thought it was for the updated code.
Yes, I think rephrasing W012 is a good idea. Apologies to @kkirsche as well. This was all a tired-eyes user error, pebcak, RTFM, etc.

Hi @chrisbloom7!
You appear to have posted a live example (https://fiddle.jshell.net/z0L72nn1/1/show/light/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 56, column 11: E012: .input-group and .col-*-* cannot be used directly on the same element. Instead, nest the .input-group within the .col-*-*
line 68, column 11: E012: .input-group and .col-*-* cannot be used directly on the same element. Instead, nest the .input-group within the .col-*-*

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

Hi @chrisbloom7!
You appear to have posted a live example (https://fiddle.jshell.net/z0L72nn1/show/light/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 46, column 5: W012: .container or .container-fluid should be the first child inside of a .navbar
line 15, column 7: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.0.0
line 19, column 7: W013: Bootstrap version might be outdated. Latest version is at least 3.3.4 ; saw what appears to be usage of Bootstrap 3.0.0

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

authors: chrisbloom7 cvrebert kkirsche twbs-lmvtfy


text:
v4: Maybe the wrapper can be left out using card decks?

Hi, it seems like the card deck can be structured like this instead, saving one div wrapper:

        ...

In the docs there is a separate div for this. Maybe it can be left out? I might very well be overlooking a browser test or edge case here, sorry if I do! Just tested around a bit.
Here is a CodePen before and after the change.

I recall it being a browser thing, but will need to revisit to be sure.

Or maybe it was just a problem with a table having width: 100%, which would be problematic for the negative margins.

Done with the move to flexbox in #21403.

authors: mdo storafrid


text:
Popover/Tooltip placement logs tether error

I tried the auto placement like described in the documentation

When "auto" is specified, it will dynamically reorient the popover. For example, if placement is "auto left", the popover will display to the left when possible, otherwise it will display right.

After nothing happens I saw an error in the console.

Error: Tether Error: You must provide an attachment

On a bit debugging I found out that attachment is undefined in the tooltip.js what extends the popover.js cause the AttachmentMap does not provide any auto left
https://github.com/twbs/bootstrap/blob/v4-dev/js/src/tooltip.js#L282

A codepen to show the issue : http://codepen.io/Johann-S/pen/NbojYb

authors: Johann-S chapterjason


text:
Modal doesn't open without popper.min.js

Modal component doesn't  work without including popper.min.js before bootstrap.js, console shows the error "Bootstrap dropdown require Popper.js"
Bootstrap v4

Indeed Bootstrap depends on Popper.js for our Tooltips/Dropdown and Popovers plugins.
@XhmikosR what do you think about moving this test : https://github.com/twbs/bootstrap/blob/v4-dev/js/src/tooltip.js#L15-L21 in our plugins constructor ?
Because folks who don't need to use those components, should be able to do that without this error

@Johann-S: wouldn't then throw for people who don't want to use those components?
How about we have an extra global var like needsPopper and act accordingly in our constructor?

Nope people we'll only see this error if they are trying to use our Dropdowns/Tooltips or Popovers
seems a bit redundant because we can simply check if Popper is available or not

@Johann-S: please make a PR and CC me.

Finally it seems we have no solution here (see : https://github.com/twbs/bootstrap/pull/24306)
so @m01key you have to add Popper.js because 3 of our plugins use it or you can wait for our next release which will add a new dist file with Popper.js inside

Either we do what I suggested and throw in the constructor if a component which requires popper is used, or we leave it as it. Otherwise it will throw an error even though one might not use a popper descendant component.

Maybe I don't see how you'll do that but for me it wont change anything because our plugins are wrapped into IIFE ended with : })($, Popper)

True that. Not sure if there's another way to do things, but with our current implementation I don't think we can do a lot.

true, it's hard to add optional dep :worried:

Maybe instead of throwing an error we should just use console.warn ? @XhmikosR

authors: Johann-S XhmikosR m01key


text:
Close button is disabled, but hover effect still work

Close button is disabled, but hover effect still work
https://codepen.io/rpokrovskij/pen/gKaKrJ
True for 4.0 and 4.1

@patrickhlauke  thank you? patrick, is it real to ask bootstrap team to support close button inside budge? (that mean close button "size"and aligment) ?

file any new request/issue as a separate issue please :)

@patrickhlauke ok I will do it. but that what I get last time when I have requested "new feature":
https://github.com/twbs/bootstrap/issues/26412
It can be understand as bootstrap  team doesn't consider proposals for new features.

authors: patrickhlauke rpokrovskij


text:
invalid-feedback class changes input border and margin

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
Short and descriptive example bug report title
Having an element with the invalid-feedback class above an input element, changes the input elements top-left border, bottom-left border, and margin-left..
Example

  <form name="test_show_form" method="post">

123 already exists.

          <input type="number" required="required" class="form-control is-invalid" value="123">

  </form>

Expected result
No changes in border and margin for the given input element.
Reduced test cases
Codepen
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.1.3

Don't put the invalid feedback within the .input-group like that. Our selectors for it are rather difficult, but there's not much of a cleaner way to do things.

authors: ToshY mdo


text:
Add Wall of Browser Bugs entries for #15998

Closes #15998.

<3

source: gharchive/pull-request

authors: cvrebert mdo


text:
new feature: Adds ellipsis if text overflows

see feature request https://github.com/twbs/bootstrap/issues/19314

Just realized my PR was on Bootstrap 3 ... :/

Indeed, we're no longer accepting new features into Bootstrap 3; see https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#pull-requests
We'd consider such a pull request for Bootstrap 4 (branch v4-dev) though. Feel free to open a new PR for this for Bootstrap 4.

Thanks for the feedback. I'll send PR to V4 instead then.
Should the doc on https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#pull-requests be corrected though?
So instead of:

If you cloned a while ago, get the latest changes from upstream:

git checkout master
git pull upstream master

Rather:

git checkout v4-dev
git pull v4-dev v4-dev

--
And also change the point 5 to:
git pull [--rebase] v4-dev v4-dev

authors: adrien-be cvrebert


text:
Documentation tweaks

The .col-12 classes are redundant
Mention the xs infix is not used
Clarify the mobile first approach better

This should be backported to v4

Definitely better, thanks @midzer

I found a similar code in the document.
https://github.com/twbs/bootstrap/blob/c2fa74b65278415fb6ed545186f4dd6c23c575cf/site/content/docs/4.3/layout/grid.md#L306
https://github.com/twbs/bootstrap/blob/c2fa74b65278415fb6ed545186f4dd6c23c575cf/site/content/docs/4.3/layout/grid.md#L480

Just searched for more redundant appearances of .col-12 and removed those too

I believe this was a leftover from the old days. Still, I need @mdo's approval just to be safe.

@MartijnCuppens: I'm having trouble cherrypicking this, please have a look later (maybe redo this manually in my v4-dev-xmr-backports branch).

@MartijnCuppens: I'm having trouble cherrypicking this, please have a look later (maybe redo this manually in my v4-dev-xmr-backports branch).

authors: MartijnCuppens XhmikosR ysds


text:
Consistently use outline:0 rather than outline:none

just for code consistency, no actual effect on styling per se

damn sorry, missed the request for review from @mdo that @XhmikosR did. please revert if it turns out this was too hasty.

damn sorry, missed the request for review from @mdo that @XhmikosR did. please revert if it turns out this was too hasty.


text:
Make a form validation handler | handle form messages

A Javascript handler for form|fields messages.
As a developer, I have been several times, in the awkward position, needing  to implement custom code, that will co-operate with bs-form fields. So, many times I had the same thought. "What if bootstrap provided the base 'JS adapter' for its fields"
This PR tries to provide a Bootstrap component, that automatically handle browser validation messages, and in addition will give the opportunity to use custom, given feedback messages.
In advance, it contains JavaScript code, providing

on form component:

method  to clear these messages,
get FormData` (for ajax usage)
execute validation
access each formField instance
JS hook, through component configuration, where developers can use for Ajax submission (not provided by default) and/or attach any custom validation messages

per field methods:

clear appended feedbacks
append success | error | info  feedback messages

Needs:

[ ] Documentation
[ ] Tests
Feedback

Cons:
Adds a significant size as it  introduces two new classes :thinking:
Related #28414
close #28995
Preview : https://deploy-preview-34043--twbs-bootstrap.netlify.app/docs/5.1/forms/validation/#custom-styles

almost perfect. one annoying issue though: if the form field already has an aria-describedby to begin with (see for instance the "Username" control, which initially already references the element containing the "@" sign), then this is overwritten by the success or error message. instead, it should be concatenated (so that the aria-describedby shows what was there to begin with, a space, and the id of the error message) - see the server side static example later on.
also, not sure if this PR also touches on the tooltip case, but here the generated markup seems incorrect ... the actual valid/invalid tooltip sits outside of the
 that is referenced by the aria-describedby - so this references just an empty container, with the actual tooltip being a sibling of this.

After submitting with empty values, the username results in this structure

    Username

      @
      <input type="text" class="form-control" id="validationCustomUsername" aria-describedby="inputGroupPrepend" required="" data-bs-invalid="Please choose a username.">
Please choose a username.

note that this now gives both the  with the "@" and the invalid feedback
 the same id, which is invalid. and the end result is that the AT still only announces the latter.
what i meant above, which may not have been clear: the end result should be that the aria-describedby contains a reference to both the previous/existing value it had (pointing to the ) and to the validation
, as a space-separated value. so the end result should be something like

    Username

      @
      <input type="text" class="form-control" id="validationCustomUsername" aria-describedby="inputGroupPrepend validationCustomUsername-formTip" required="" data-bs-invalid="Please choose a username.">
Please choose a username.

also, the latest changes seem to have broken the tooltips case https://deploy-preview-34043--twbs-bootstrap.netlify.app/docs/5.0/forms/validation/#tooltips which now just show the browser default error handling rather than the custom tooltips

btw probably worth saying: it might look like i just come in here to point out what's wrong... but this is already a great way forward! if we can tweak these last few bits, it'll be wonderful to have validation properly addressed in BS.

btw probably worth saying: it might look like i just come in here to point out what's wrong... but this is already a great way forward! if we can tweak these last few bits, it'll be wonderful to have validation properly addressed in BS.

You are right on this. give me some minutes

note that this now gives both the  with the "@" and the invalid feedback  the same id, which is invalid. and the end result is that the AT still only announces the latter.

got it. Thanks

it's almost perfect now, thanks for indulging me there @GeoSot. the last aspect that would be good to address is potentially tricky.
if you try to submit an invalid/incomplete form, and you get the error messages...if you then go back and correct the errors, visually the error message disappears and the green success styling is shown. however, behind the scenes, the aria-describedby still points to the now hidden error message. and even if an error message is completely hidden using display:none, screen readers will still read/announce it when it's referenced by aria-describedby. this can then lead to confusing situation where the user corrects the form entry, it visually shows it's correct, but regardless it still announces the error.
i think the only way around this would be to watch for a change event on the form (or individual form controls themselves?), and then dynamically resetting aria-describedby to its initial value (e.g. in the case of "Username" only pointing to the @ container) / changing it to the success message id if present (and in the case of "Username", this would then need to point to BOTH the @ and the success message if it had one ... for this reason, will be good to keep a reference right at the start to whatever the aria-describedby value was before validation as well.)

i.e. after validation once the user does go back and edit, currently it visually then shows this

and the markup for that username input is
<input type="text" class="form-control" id="validationCustomUsername" aria-describedby="inputGroupPrepend validationCustomUsername-formTip" required="" data-bs-invalid="Please choose a username.">

i.e. note that aria-describedby now still points to inputGroupPrepend validationCustomUsername-formTip when it should just point to inputGroupPrepend

last outstanding aspect, if possible, is removing the reference to the error message in aria-describedby once a previously invalid field becomes valid (either right away when the user fulfills the validation requirement, or at least when they try to resubmit and the validation run happens again).
i.e. currently, even after filling in a previously empty field, and the field now not being valid, the error message is still associated/announced ... and with aria-describedby, even if the target referenced is display:none, it's still announced. see this animation (with NVDA speech viewer), and note that after filling in the "City" and then moving away and returning, it still announces as "City - please provide a valid city".

getting there :)
i see the aria-describedby is correctly updated if at first something was invalid, and you then go in to make it valid. great stuff.
however, doing multiple erroneous submissions results in error messages being multiplied...

in the case of the tooltip variant, visually there's only one tooltip, but the aria-describedby balloons out with multiple references...as a result, AT will announce the referenced tooltip multiple times too

lastly, in the "supported elements" case, the initial errors aren't associated with the form fields. and editing the form to then be valid, some of the errors remain visible (but still not announced) https://deploy-preview-34043--twbs-bootstrap.netlify.app/docs/5.0/forms/validation/#supported-elements

thank you @patrickhlauke :)
I was aware of duplicated feedback elements, but I wasn't sure how to solve it. Although, I think I have found a valid solution.

lastly, in the "supported elements" case

I didn't change something there (at least yet), as it is a fixed example that shows the classes usage. (it works the same way on our published docs)

In order to do our checks, the only changed sections are

Forms:

Custom styles
Tooltips

Examples:

Checkout
Checkout RTL

When we finish the basic tests, we can see more on documentation area, and js-code needs to be discussed|optimized with the help of the js team

I was aware of duplicated feedback elements, but I wasn't sure how to solve it. Although, I think I have found a valid solution.

conceptually, it likely needs to do a check of "if the relevant error is already shown/the aria-describedby already contains the reference, do nothing, otherwise show the error/add the reference to the aria-describedby".

I didn't change something there (at least yet), as it is a fixed example that shows the classes usage. (it works the same way on our published docs)

we probably need to make those dynamic as well (starting off with an already present error, but then following the same JS logic that removes any reference/hides the error message/etc once user interacts with it)

added a commit that normalises all ids used in the various form examples, and adds the relevant aria-describedby etc to the static examples, as a first step

i see the issue of multiple errors appearing when hitting submit multiple times has now been fixed. great stuff.
out of interest, how easy/hard would it be to hook up the validation script to https://deploy-preview-34043--twbs-bootstrap.netlify.app/docs/5.0/forms/validation/#supported-elements as well? as currently the CSS changes kick in (partially) and it leaves this in weird semi-states...

one other oddity i spotted (but likely no easy way around it) is that for the checkbox example, the generated error comes straight after the input, so ends up before the label

conceptually, it likely needs to do a check of "if the relevant error is already shown/the aria-describedby already contains the reference, do nothing, otherwise show the error/add the reference to the aria-describedby".

done

we probably need to make those dynamic as well (starting off with an already present error, but then following the same JS logic that removes any reference/hides the error message/etc once user interacts with it)

I think it will be a bit more interventional, than it should

out of interest, how easy/hard would it be to hook up the validation script to https://deploy-preview-34043--twbs-bootstrap.netlify.app/docs/5.0/forms/validation/#supported-elements as well? as currently the CSS changes kick in (partially) and it leaves this in weird semi-states...

It can be done, but  it is considerable better to make .is-valid & is-invalid to have more weight than pseudo-classes, as they are used as overrides

one other oddity i spotted (but likely no easy way around it) is that for the checkbox example, the generated error comes straight after the input, so ends up before the label

done

It can be done, but it is considerable better to make .is-valid & is-invalid to have more weight than pseudo-classes, as they are used as overrides

but without JS to remove the aria-describedby the error messages will still be announced even when display:none'd ... which is what led us down this path of using JS in the first place

Just for my own sanity (as I had lost track of where we were at with this), made a quick recording using Chrome/NVDA of how this all currently shakes out
https://user-images.githubusercontent.com/895831/169644477-cf5fc958-e5d9-4b62-8755-8b17e37b0efd.mp4

0:00 - 0:42 Custom styles: work great/as I'd expect/want them
0:42 - 1:27 Browser styles: work as expected by browser (with Chrome popping up the validation bubbles one at a time as you submit)
1:27 - 1:59 Server side: notice that only the errors are tied to the form fields. for consistency, probably makes sense to also tie the "Looks good" text to the form control, the same way that error messages are
1:59 - 2:18 Supported elements: no association between validation messages and their form fields - wonder if we can either automate this/run the script over it, or if we just manually add the aria-describedby here?
2:18 - 3:00 Tooltips: work as expected

@patrickhlauke for start, I want to really thank you for your patience and your help.
I saw the review above and :

1:27 - 1:59 Server side: notice that only the errors are tied to the form fields. for consistency, probably makes sense to also tie the "Looks good" text to the form control, the same way that error messages are

seems to be an issue of docs, because we are just indicating the proper markup in case of server validation, fixed in: 07240fedb72eadf739f94f6df59ee40081a3329d

1:59 - 2:18 Supported elements: no association between validation messages and their form fields - wonder if we can either automate this/run the script over it, or if we just manually add the aria-describedby here?

seems to be an issue of docs, which I handled, adding the aria-describedby attribute manually (we cannot use the js script as the submit btn is disabled ), fixed in: 07240fedb72eadf739f94f6df59ee40081a3329d

snuck in a tweak to the documentation text itself...

@GeoSot you'll probably also want to add a bullet point to the "how it works" section, to mention the extra scripting that ties the form control to its feedback/error message when it appears. just draft it up, happy to give it a read/tweak once there https://deploy-preview-34043--twbs-bootstrap.netlify.app/docs/5.2/forms/validation/#how-it-works

Thank you @patrickhlauke 🙂
I have it in my mind too, but I am holding myself, till I get some feedback from other @twbs/team members (or contributors), concerning the usefulness of this idea, and opinions over the JavaScript code.
(Just to minimize the process steps and avoid going back and forth on file changing)

authors: GeoSot patrickhlauke


text:
Fix space between popover's arrow and triggering element

This PR is a proposal to:

Fix the space between the popover's arrow and the triggering element.
Add --bs-popover-inner-border-radius as it is done for the dropdowns with --bs-dropdown-inner-border-radius

(Note: I can split the commits if needed)
Regarding the fix proposed here.
In https://github.com/twbs/bootstrap/commit/2e75ec3c41a54865caa48f46485a1c90b12b0de6 (and so in the main branch) we can observe this kind of modifications:
- bottom: subtract(-$popover-arrow-height, $popover-border-width);
+ bottom: calc((var(--#{$variable-prefix}popover-arrow-height)) * -1); // stylelint-disable-line function-disallowed-list

The substraction does not appear in the new calculation. So the rendering is slightly different:
Before
Preview: https://getbootstrap.com/docs/5.1/components/popovers/#four-directions

With the error (main branch)
Preview: https://twbs-bootstrap.netlify.app/docs/5.1/components/popovers/#four-directions
There is an extra spacing between the button and the arrow:

With the fix proposed in this PR
Preview: https://deploy-preview-35976--twbs-bootstrap.netlify.app/docs/5.1/components/popovers/#four-directions

I always used .25 increments but I don't think everyone else has been following that.

I always used .25 increments but I don't think everyone else has been following that.

Thanks for the rule, I've updated my .66 :smile: to .75 via https://github.com/twbs/bootstrap/pull/35976/commits/9b3407a59874b964099410b1c24364210c41077f

authors: XhmikosR julien-deramond


text:
AttributeError: 'NoneType' object has no attribute 'strip'

Problem with streaming on attributes of stream.filter(track=['#python'])

Is the error originating from streaming.py? Does it work if you remove the #?

Ok, i already found the problem: The twitter streaming API has been experiencing problems since the attack on DYN the 21st of October. These have been reported on the twitter developer forum, and twitter staff are aware of the issue: https://twittercommunity.com/t/issues-reported-with-streams-since-10-21/76429.

authors: Pescu xofeoj

repo: tweepy/tweepy

license: mit

license_source: bigquery


text:
Add models

This PR adds the models for Active Record
Please carefully check the validations, to ensure that all edge cases are covered!

This should not be merged until PR #8 is fully merged!

Close for fix up commit

repo: tweet-squared/Tweet-Squared-App


text:
TypeError: parseDomain is not a function

When doing npm run build, I'm getting lots and lots of errors that look like:
TypeError: parseDomain is not a function
    at Index.getLinkUrls (/home/aquarius/Programs/Others/tweetback/src/twitter.js:63:25)
    at Index.getAllLinks (/home/aquarius/Programs/Others/tweetback/index.11ty.js:166:26)
    at Index.render (/home/aquarius/Programs/Others/tweetback/index.11ty.js:254:20)
    at async Template._render (/home/aquarius/Programs/Others/tweetback/node_modules/@11ty/eleventy/src/TemplateContent.js:473:22)
    at async TemplateMap.populateContentDataInMap (/home/aquarius/Programs/Others/tweetback/node_modules/@11ty/eleventy/src/TemplateMap.js:495:13)
    at async TemplateMap.cache (/home/aquarius/Programs/Others/tweetback/node_modules/@11ty/eleventy/src/TemplateMap.js:370:5)
    at async TemplateWriter._createTemplateMap (/home/aquarius/Programs/Others/tweetback/node_modules/@11ty/eleventy/src/TemplateWriter.js:244:5)
    at async TemplateWriter.generateTemplates (/home/aquarius/Programs/Others/tweetback/node_modules/@11ty/eleventy/src/TemplateWriter.js:277:5)
    at async TemplateWriter.write (/home/aquarius/Programs/Others/tweetback/node_modules/@11ty/eleventy/src/TemplateWriter.js:324:23)
    at async Eleventy.executeBuild (/home/aquarius/Programs/Others/tweetback/node_modules/@11ty/eleventy/src/Eleventy.js:1121:13)

did I break something locally? https://github.com/tweetback/tweetback/issues/20 seems to reference parseDomain not handling stuff, but that's closed, and I'm not sure it's relevant.

@stuartlangridge did you update your version of tweetback? @zachleat changed something yesterday that might fix your issue:
https://github.com/tweetback/tweetback/commit/24d083ebfac080cecfc96e02017ad79a9946e952

@stuartlangridge great! 👍

authors: nhoizey stuartlangridge

repo: tweetback/tweetback


text:
infra:new is falling because of var file check

The command infra:new is triggering the pulumi stack ls which fails because no Pulumi.yaml exists. We need to remove the environment variable file check for this command.

:tada: This issue has been resolved in version 0.3.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: kaiquelupo vernig


text:
feat(pixels): add my new pixel (15, 32)

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

I guess more commits have been done and that's why I'm getting the issues. I'll be resolving the issues and will be giving a PR soon. Thank you.

repo: twilio-labs/open-pixel-art


text:
Update all dependencies

Summary
Provide a summary of the change...
Checklist

[ ] Tested changes end to end
[ ] Any config changes added to all environment files
[ ] For Flex features added, ensure the feature list on the README on the project root folder is updated
[ ] Completed README template for new features

[ ] Feature summary - high level summary of what the feature does
[ ] Flex User Experience with animations - animations with descriptions if necessary of the user experience in Flex
[ ] Setup and dependencies - description of any setup steps required for this feature
[ ] How does it work? - description of plumbing supporting feature

[ ] Added PR Label "ready-for-review"
[ ] Requested one or more reviewers for the PR

Successfully tested all CI workflows after updates.


text:
FastCell in production environment

Hello.
I am really interested in FastCell control, because I want to improve the performance in my app ListViews (too slow in Android).
But I have to say that this is for a customer project, and this code will be in production very soon.
Do you reccommend me to use it? In readme file you don't recommend to use this library for production...
Thanks!! :-)

you know what, you can give it a go.. I need to update the readme. Since I wrote that I’ve solved a couple of issues I had.

On 18 Jul 2015, at 10:35, fcogutierrez notifications@github.com wrote:
Hello.
I am really interested in FastCell control, because I want to improve the performance in my app ListViews (too slow in Android).
But I have to say that this is for a customer project, and this code will be in production very soon.
Do you reccommend me to use it? In readme file you don't recommend to use this library for production...
Thanks!! :-)
—
Reply to this email directly or view it on GitHub https://github.com/twintechs/TwinTechsFormsLib/issues/11.

Ok, will do :)

authors: fcogutierrez georgejecook

repo: twintechs/TwinTechsFormsLib


text:
Skip some rrsets

Fixes #45

Codecov Report

Merging #46 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #46      +/-   ##
==========================================
+ Coverage   96.25%   96.26%   +<.01%
==========================================
  Files          73       73
  Lines        8644     8664      +20
  Branches      604      605       +1
==========================================
+ Hits         8320     8340      +20
  Misses        202      202
  Partials      122      122

Impacted Files
Coverage Δ

txaws/route53/tests/test_route53.py
97.8% <100%> (+0.5%)
:white_check_mark:

txaws/route53/client.py
100% <100%> (ø)
:white_check_mark:

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 52d2685...2bc18f4. Read the comment docs.

authors: codecov-io exarkun

repo: twisted/txaws


text:
Incorrect datatype u8 vs char in opencv::videoio::VideoWriter::fourcc method

Before calling opencv::videoio::VideoWriter::new to create a new video file it is necessary to know what codecs should be used. The method opencv::videoio::VideoWriter::fourcc is supposed to take four chars and return the matching i32 codecs. An example in the rust opencv document shows videoio::VideoWriter::fourcc('M','J','P','G').
But in the rust method the four parameters are all defined as i8.
Compiling the following code clearly illustrates the problem:
use opencv::{
    prelude::*,
    videoio,
};

fn run() -> opencv::Result<()> {
    let vc_fourcc = videoio::VideoWriter::fourcc('M','J','P','G') ?;
    Ok(())
    }

fn main() {
    run().unwrap();
}
```   ```
Operating system:
Edition Windows 10 Pro
Version 21H2
Installed on 8/10/2022
OS build 19044.1889
Experience Windows Feature Experience Pack 120.2212.4180.0

Installation
Installed using the approach relying on [chocolatey](https://chocolatey.org/) described under 'Windows package'. I believe the install works correctly as many other opencv-related sample programs work just fine.

RUST_BACKTRACE=full cargo build -vv
       Fresh autocfg v1.1.0
       Fresh cfg-if v1.0.0
       Fresh once_cell v1.13.0
       Fresh scopeguard v1.1.0
       Fresh unicode-ident v1.0.3
       Fresh glob v0.3.0
       Fresh num_cpus v1.13.1
       Fresh adler v1.0.2
       Fresh adler32 v1.2.0
       Fresh regex-syntax v0.6.27
       Fresh dunce v1.0.2
       Fresh percent-encoding v2.1.0
       Fresh either v1.8.0
       Fresh jobserver v0.1.24
       Fresh maplit v1.0.2
       Fresh vcpkg v0.2.15
       Fresh futures-sink v0.3.23
       Fresh shlex v1.1.0
       Fresh weezl v0.1.7
       Fresh pkg-config v0.3.25
       Fresh half v1.8.2
       Fresh lebe v0.5.2
       Fresh bit_field v0.10.1
       Fresh rawpointer v0.2.1
       Fresh color_quant v1.1.0
       Fresh bitflags v1.3.2
       Fresh smallvec v1.9.0
       Fresh bytemuck v1.12.1
       Fresh scoped_threadpool v0.1.9
       Fresh byteorder v1.4.3
       Fresh getrandom v0.2.7
       Fresh miniz_oxide v0.5.3
       Fresh threadpool v1.8.1
       Fresh deflate v1.0.0
       Fresh inflate v0.4.5
       Fresh cc v1.0.73
       Fresh matrixmultiply v0.3.2
       Fresh gif v0.11.4
       Fresh crossbeam-utils v0.8.11
       Fresh winapi v0.3.9
       Fresh proc-macro2 v1.0.43
       Fresh memchr v2.5.0
       Fresh nanorand v0.7.0
       Fresh libc v0.2.129
       Fresh crc32fast v1.3.2
       Fresh futures-core v0.3.23
       Fresh semver v1.0.13
       Fresh memoffset v0.6.5
       Fresh num-traits v0.2.15
       Fresh crossbeam-channel v0.5.6
       Fresh lock_api v0.4.7
       Fresh libloading v0.7.3
       Fresh quote v1.0.21
       Fresh aho-corasick v0.7.18
       Fresh flate2 v1.0.24
       Fresh png v0.17.5
       Fresh crossbeam-epoch v0.9.10
       Fresh num-integer v0.1.45
       Fresh spin v0.9.4
       Fresh num-complex v0.4.2
       Fresh clang-sys v1.3.3
       Fresh syn v1.0.99
       Fresh regex v1.6.0
       Fresh crossbeam-deque v0.8.2
       Fresh num-rational v0.4.1
       Fresh pin-project-internal v1.0.12
       Fresh clang v2.0.0
       Fresh ndarray v0.15.6
       Fresh rayon-core v1.9.3
       Fresh opencv-binding-generator v0.45.0
       Fresh pin-project v1.0.12
       Fresh rayon v1.5.3
       Fresh flume v0.10.14
       Fresh jpeg-decoder v0.2.6
       Fresh exr v1.4.2
       Fresh tiff v0.7.3
       Fresh opencv v0.66.0
       Fresh image v0.24.3
   Compiling pxlit_opencv v0.1.0 (C:\Users\svenn\rust\pxlit_opencv)
     Running `set CARGO=\\?\C:\Users\svenn\.rustup\toolchains\stable-x86_64-pc-windows-msvc\bin\cargo.exe&& set CARGO_BIN_NAME=pxlit_opencv&& set CARGO_CRATE_NAME=pxlit_opencv&& set CARGO_MANIFEST_DIR=C:\Users\svenn\rust\pxlit_opencv&& set CARGO_PKG_AUTHORS=""&& set CARGO_PKG_DESCRIPTION=""&& set CARGO_PKG_HOMEPAGE=""&& set CARGO_PKG_LICENSE=""&& set CARGO_PKG_LICENSE_FILE=""&& set CARGO_PKG_NAME=pxlit_opencv&& set CARGO_PKG_REPOSITORY=""&& set CARGO_PKG_VERSION=0.1.0&& set CARGO_PKG_VERSION_MAJOR=0&& set CARGO_PKG_VERSION_MINOR=1&& set CARGO_PKG_VERSION_PATCH=0&& set CARGO_PKG_VERSION_PRE=""&& set CARGO_PRIMARY_PACKAGE=1&& set PATH="C:\Users\svenn\rust\pxlit_opencv\target\debug\deps;C:\Users\svenn\.rustup\toolchains\stable-x86_64-pc-windows-msvc\bin;C:\Users\svenn\.rustup\toolchains\stable-x86_64-pc-windows-msvc\bin;C:\Program Files\Dell\DW WLAN Card;;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\Microsoft VS Code\bin;C:\ProgramData\chocolatey\bin;C:\Program Files\LLVM\bin;C:\Users\svenn\.cargo\bin;C:\Users\svenn\AppData\Local\Microsoft\WindowsApps;"&& rustc --crate-name pxlit_opencv --edition=2021 src\main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=48943ec9e4d1a38f --out-dir C:\Users\svenn\rust\pxlit_opencv\target\debug\deps -C incremental=C:\Users\svenn\rust\pxlit_opencv\target\debug\incremental -L dependency=C:\Users\svenn\rust\pxlit_opencv\target\debug\deps --extern image=C:\Users\svenn\rust\pxlit_opencv\target\debug\deps\libimage-bd9c5d2de8a0ecf7.rlib --extern ndarray=C:\Users\svenn\rust\pxlit_opencv\target\debug\deps\libndarray-6af201cef50c369f.rlib --extern opencv=C:\Users\svenn\rust\pxlit_opencv\target\debug\deps\libopencv-984bef83365d79f6.rlib -L native=C:\Users\svenn\rust\pxlit_opencv\target\debug\build\opencv-e0385181a2a64e23\out -L C:\tools\opencv\build\x64\vc15\lib`
warning: unused import: `prelude::*`
 --> src\main.rs:2:5
  |
2 |     prelude::*,
  |     ^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

error[E0308]: mismatched types
 --> src\main.rs:8:50
  |
8 |     let vc_fourcc = videoio::VideoWriter::fourcc('M','J','P','G') ?;
  |                                                  ^^^ expected `i8`, found `char`

error[E0308]: mismatched types
 --> src\main.rs:8:54
  |
8 |     let vc_fourcc = videoio::VideoWriter::fourcc('M','J','P','G') ?;
  |                                                      ^^^ expected `i8`, found `char`

error[E0308]: mismatched types
 --> src\main.rs:8:58
  |
8 |     let vc_fourcc = videoio::VideoWriter::fourcc('M','J','P','G') ?;
  |                                                          ^^^ expected `i8`, found `char`

error[E0308]: mismatched types
 --> src\main.rs:8:62
  |
8 |     let vc_fourcc = videoio::VideoWriter::fourcc('M','J','P','G') ?;
  |                                                              ^^^ expected `i8`, found `char`

For more information about this error, try `rustc --explain E0308`.
warning: `pxlit_opencv` (bin "pxlit_opencv") generated 1 warning
error: could not compile `pxlit_opencv` due to 4 previous errors; 1 warning emitted

Caused by:
  process didn't exit successfully: `set CARGO=\\?\C:\Users\svenn\.rustup\toolchains\stable-x86_64-pc-windows-msvc\bin\cargo.exe&& set CARGO_BIN_NAME=pxlit_opencv&& set CARGO_CRATE_NAME=pxlit_opencv&& set CARGO_MANIFEST_DIR=C:\Users\svenn\rust\pxlit_opencv&& set CARGO_PKG_AUTHORS=""&& set CARGO_PKG_DESCRIPTION=""&& set CARGO_PKG_HOMEPAGE=""&& set CARGO_PKG_LICENSE=""&& set CARGO_PKG_LICENSE_FILE=""&& set CARGO_PKG_NAME=pxlit_opencv&& set CARGO_PKG_REPOSITORY=""&& set CARGO_PKG_VERSION=0.1.0&& set CARGO_PKG_VERSION_MAJOR=0&& set CARGO_PKG_VERSION_MINOR=1&& set CARGO_PKG_VERSION_PATCH=0&& set CARGO_PKG_VERSION_PRE=""&& set CARGO_PRIMARY_PACKAGE=1&& set PATH="C:\Users\svenn\rust\pxlit_opencv\target\debug\deps;C:\Users\svenn\.rustup\toolchains\stable-x86_64-pc-windows-msvc\bin;C:\Users\svenn\.rustup\toolchains\stable-x86_64-pc-windows-msvc\bin;C:\Program Files\Dell\DW WLAN Card;;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\Microsoft VS Code\bin;C:\ProgramData\chocolatey\bin;C:\Program Files\LLVM\bin;C:\Users\svenn\.cargo\bin;C:\Users\svenn\AppData\Local\Microsoft\WindowsApps;"&& rustc --crate-name pxlit_opencv --edition=2021 src\main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=48943ec9e4d1a38f --out-dir C:\Users\svenn\rust\pxlit_opencv\target\debug\deps -C incremental=C:\Users\svenn\rust\pxlit_opencv\target\debug\incremental -L dependency=C:\Users\svenn\rust\pxlit_opencv\target\debug\deps --extern image=C:\Users\svenn\rust\pxlit_opencv\target\debug\deps\libimage-bd9c5d2de8a0ecf7.rlib --extern ndarray=C:\Users\svenn\rust\pxlit_opencv\target\debug\deps\libndarray-6af201cef50c369f.rlib --extern opencv=C:\Users\svenn\rust\pxlit_opencv\target\debug\deps\libopencv-984bef83365d79f6.rlib -L native=C:\Users\svenn\rust\pxlit_opencv\target\debug\build\opencv-e0385181a2a64e23\out -L C:\tools\opencv\build\x64\vc15\lib` (exit code: 1)

As a workaround you can try casting with as i8, but I’ll try to come up with a more convenient solution

Thank you for the instantaneous feedback. It allows me to more forward :~)

Through this workaround I was able to get to call videoio::VideoWriter::new + videoio::VideoWriter::write + videoio::VideoWriter::release. The 'write' fails because the file new file isn't open - very similar to issue #359. Should I create a separate issue for that I would it be better to add this to #359?

In version 0.67 fourcc method now accepts char instead of i8

Thank you :~)
On Wed, Aug 31, 2022 at 7:42 AM twistedfall @.***>
wrote:

In version 0.67 fourcc method now accepts char instead of i8
—
Reply to this email directly, view it on GitHub
https://github.com/twistedfall/opencv-rust/issues/362#issuecomment-1232825759,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2S6DL2YUF7CLNCM3BKRWE3V35AKDANCNFSM57IVYG7Q
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

authors: svenne-juul twistedfall

repo: twistedfall/opencv-rust


text:
When authenticating requests to the Twitter API v2 endpoints, you must use keys and tokens from a Twitter developer App that is attached to a Project. You can create a project via the developer portal

tweets_endpoint_url :  https://api.twitter.com/2/users/#id/tweets
I am trying to fetch tweets but I am still getting issues with this "reason":"client-not-enrolled" Please help with this.i am testing with Python odoo framework.

me too
use sample code get 403
https://github.com/twitterdev/Twitter-API-v2-sample-code/blob/main/Usage Tweets/get_usage_tweets.py

authors: infovpcs nathonNot


text:
Packages for Mac/Ubuntu, New Icons

I was working on #7 and #2 , but I haven't had the time to finish them up. Not sure if I'll get around to it, but I figured I may as well merge it and see if someone wants to finish it off.
This definitely solves #7, and is a good step towards #2, especially for Mac OS X.

New icons!
Adjusted wording / arrangement of menus
Build files for Mac OS X, start of build files for Ubuntu/Debian
Tray icon uses template styling for proper Mac OS X display

You can build a distributable application package by running /build/build-darwin.sh on Mac OS X.
The build script for Ubuntu/Debian does the build, but doesn't package it yet.
I have done absolutely no testing on Windows

Wow, awesome. That's a lot of changes though, can we break this down into smaller PRs?

PR only for updating images
PR only for performing builds
PR only for text changes

Yeah, I'm sorry it was kind of all lumped together. I had all the changes as they were on my machine, but no time to work on them.
I'll see if I can find some time to break it into smaller PRs in the next few days, but my time is extremely limited.

I've split the icons off into PR #28.
Did you still want me to create one for the text & builds, or would you prefer holding off until either myself or someone else can make a more node-integrated process?

Awesome, thanks.
With respect to the text changes, we could break it but there we would need to make sure we cover all our bases with the renaming. Unfortunately, I don't currently have time to help with that =/
With respect to the builds, I will link to the relevant files on #2 for future reference to ourselves.
With respect to this PR, I'm going to close it now since it has been broken down.
Thanks again for all the work!

repo: twolfson/google-music-electron

license: unlicense


text:
Setting DEBUG from the environment

This is just a suggestion....
I've been using this for a couple of years now.  This also allows we to affect the level of debug, so that I can include/exclude debug_toolbar (because it adds a lot of overhead while testing).
DEBUG = int(os.environ.get('DJANGO_DEBUG', 0))

My workon alias will set DJANGO_DEBUG for me in my environment, but only on my local machine, not on production servers.
The optional toolbar part looks like:
# See: http://django-debug-toolbar.readthedocs.org/en/latest/installation.html#explicit-setup
if DEBUG > 1:
    INSTALLED_APPS += (
        'debug_toolbar',
    )

    MIDDLEWARE_CLASSES += (
        'debug_toolbar.middleware.DebugToolbarMiddleware',
    )

    DEBUG_TOOLBAR_PATCH_SETTINGS = False

    # http://django-debug-toolbar.readthedocs.org/en/latest/installation.html
    INTERNAL_IPS = ('127.0.0.1',)

When I want to run a test, I can turn off the toolbar with
DJANGO_DEBUG=0 manage test...

Not sure if it's okay to report an error here, but on page 449 of the Two Scoops 1.8 (Early Release Update 1) the DEBUG setting is listed as True in production and False in Development.

Hi @phinnaeus!
First off, I believe that is fixed in update 2, coming out later today.
Second, its better to report issues at https://github.com/twoscoops/two-scoops-of-django-1.8/issues/new.
Third, please identify each issue by chapter, section, and subsection numbers. Since the content shifts around, and the PDF pages numbers do not match up with the book's, page numbers are next to useless.
Thanks! :smile:

authors: mark0978 phinnaeus pydanny

repo: twoscoops/django-twoscoops-project


text:
fixes websocket connection for authentication disabled

Changes proposed in this PR

refactors websocket integration tests
skips authentication check in the upgrade request check (websocket-request-acceptor)
avoids the expectation that waiter-auth cookie will be present while handling websocket requests

Why are we making these changes?
Websocket requests should not require authentication if the token is configured to use authentication: disabled.

@dpo ready for another round of review.

Please get your handles straight. You guys keep pinging me.

Please get your handles straight. You guys keep pinging me.

My apologies :'(

authors: dpo shamsimam

repo: twosigma/waiter


text:
cookies的时间是24小时吗？

好像24小时后重新执行就会提示要扫描二维码，是cookies过期了吗？cookies的时间是24小时吗？

这样提示确实是cookie过期了，大概是一天的有效期，目前还没有开发好维持cookie在线的功能

@tychxn 直接添加用户名和密码也可以啊，反正你这个是开源的。

@tychxn 每天重新登录一次太频繁了，建议可以直接添加用户名和密码（相信开源），同时保留二维码登录。

曾经做了账号密码登录，但是京东更新后滑动验证码处理起来比较麻烦，就没有折腾

authors: PHCSJC tychxn

repo: tychxn/jd-assistant


text:
Test issue

Just a test issue, labeled as an enhancement.

Fixed with 27339fc831f8b95f05e4e343f3bf935ded8f0537


text:
Add support for sparse indexes

Proposed
When parsing entity indexes, allow for sparse indexes
I.e
for Index with sortKey: PUB_ID#${id} do not auto parse, when index is marked as sparse index
Implementation

[x] Add sparse index option on @Entity -> indexes (ideally isSparse: boolean)
[x] Allow optional values when parsing sparse marked key
[x] If parsing an sparse index and referenced variable is missing value, DO NOT ADD partition or sort key attributes for that index

Hi @whimzyLive
Just wanted to understand the exact behavior of isSparse
From documentation:
(property) isSparse?: boolean
DynamoDB only adds item to index if both Partition Key and Sort Key defined for any given GSI contains value

Indexes missing sort key value will not be added to index.

However, when I define false for a sparseIndex I expect undefined/optional values to be allowed for sort key
    GSI2: {
      partitionKey: 'COMPANY#{{companyId}}',
      sortKey: 'DEPT#{{deptId}}',
      type: INDEX_TYPE.GSI,
      isSparse: false,
    },

...
  @Attribute()
  companyId: string;

  @Attribute()
  deptId?: string;
...

This is not working though when I try to create a new user with companyId defined but deptId empty.
I get the following error:
"deptId" was referenced in DEPT#{
    {deptId
    }
} but it's value could not be resolved.

Additionally, if i define a default value for deptId, the same error occurs, so it appears as if the code here is running before default value is set.
  @Attribute({
    default: '',
  })
  deptId?: string;

So my question is what exactly is the expected behavior when isSparse: false?

As a followup to my previous comment, I observed the opposite behavior with the same entity but a different index:
    GSI3: {
      partitionKey: 'COMPANY#{{companyId}}',
      sortKey: {
        alias: 'officeStatus',
      },
      type: INDEX_TYPE.GSI,
    },

...
  @Attribute({
    default: OfficeStatus.REMOTE,
  })
  officeStatus: OfficeStatus;
...

When I create a user and leave officeStatus undefined it will create the default value for me and will not throw any error like the one from the previous comment. Querying then with PK = companyId and officeStatus = remote works and returns users

I'm running into the same issue as @michael-pont mentioned above. Please allow sort keys to be optional when defining GSIs on a table.

authors: michael-pont structurr whimzyLive

repo: typedorm/typedorm


text:
Add website deployment to GitHub pages

Changes
Describe the Pull Request here. Add any references and info to help reviewers understand your changes.

Added yaml file for GitHub action to deploy adapted from vitejs wesbite

Tests applied
What testing has been applied to validate changes are accurate and correct
Not applicable
Issue ticket number(s)
Enter the issue numbers resolved by this pull request

Resolves #50

Checklist

[ ] Documented
[ ] Linting tests successful
[x] merge updated prod branch into development branch

We should probably document this in the Wiki 😔

True. I guess a lot of the stuff left is for documentation improvements.

repo: typefaceoff/typefaceoff


text:
🛑 Monitor / init.php is down

In 292fb30, Monitor / init.php (https://tyrepharm.ru/local/api/Monitor/init) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Monitor / init.php is back up in 0e00258 after 56 minutes.

repo: tyrepharm/upptime


text:
Websocket client connection (feature request)

I see that your README explicitly states this library is intended as a server, but would it be possible to include a client implementation as well?

Personally I don't see any use for a client library? The browser is supposed to be the client as far as I understand, and even if you absolutely need a client there is no need to write yet another library as there already exists decent alternatives like WebSocket++ (this library is pretty damn efficient). WebSocket++ is terrible as the server since it consumes all memory in the universe, but works good as a client where you only need one, maybe two connections. That is how I see it at least, correct me if I'm wrong.

The browser is not the only client that you can have: You can have mobile app clients, server clients, etc.
I'd personally like to see a client counterpart to uWebsockets is pretty much for the reason of not having to install two separate packages, and being able to create clients with the existing uWebsockets' already highly efficient code base (parser, and etc.), because even though there usually won't be more than one/two connections at a time, there will definitely be connections with very high throughput that require a focus on performance, like uWebsockets provides.

Socket.io has many client libraries(android,iOS,etc).
Socket.io now has support for uWebSockets in engine.io (https://github.com/kapouer/engine.io)
So you can consider using that for now.

Note that engine.io is the server and engine.io-client is the client.

Yes and engine.o-client will work with engine.io same way socket.o-client will work with socket.io using uwebsockets as the websocket library in engine.io. The point is the old engine.io supported only ws as the websocket library on the server and now supports uWebsockets as well.

You can use the current engine.io-client with engine.io + uws, the same should also be valid for Socket.IO.

Yes, but I'm not using socket.io: I'm using usually either plain websockets, or my own websocket framework that I'm working on. My point is not having to use two different implementations, ws and uws to be the client and the server, respectively.

@SEAPUNK yes it may have sense, my comment was a response to @LordMajestros comment.

WS(https://github.com/websockets/ws) is used in the tests for engine.io + uws and currently passes all tests so they should work very well together

I actually think I have misread so ignore me :)

Guessed as much 👍

@SEAPUNK Is socketeer faster than ws, as client?

@alexhultman Oh, no, it's just a framework that wraps around ws, a bit like socket.io is. I just build on top of websockets to make some functions easier.
But it's an example: I'd want to use uws in some later version, but if uws only provides the server, I'd have to keep ws or another package that provides a WebSocket client alongside of uws so I'd have both a server and a client.

I'm not planning to create a client library. I'm closing this, I need to finish the server first of all. Then depending on how much time I will have I can see what to do about this.

I understand. This is an important feature to me, so with your permission I would like to submit a pull request for this. I imagine I can get to it in the next 1-2 weeks.

@jimmyt857 Sure, if you have anything that works I can take a look but you need to figure out how to modify the parser so that it works for server frames as well as client frames (currently the parser is optimized for receiving client frames only, they have 4 byte mask and masked messages).
Sending is easy, the tricky part is parsing the servers frames. I would start with this part. And I would just start by copying the current parser a la "koppy pasta" and change it. Parsing frames from the server will be easier than parsing frames from clients so you should end up with a simpler parser.
You see the flow - you get an event, you recv the data, you run the parser, you emit fragments, you append the fragments to the buffer, you emit the message event.

Would you prefer to have separate parsers? I don't think it will be very difficult to use the same one, since the only difference is the masking.

I think the best is to just copy the code, duplicate everything and make a separate library for clients. Then we can see what is common and merge it in.

Ok, sounds good. I'll let you know when I've got something working.

https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_client_applications
https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_servers
These are very useful IMO

OMG, never mind that one was about using the browsers implementation, rofl!

Haha thanks for the thought. Don't worry, I actually wrote a simple personal websockets library for myself in C# awhile ago so I have a pretty good handle on the protocol.
I guess I should mention though, I'm currently only planning to write a pull request for the C++ version of your project, and w/o wss or permessage-deflate.

I've finished my first draft of the code for this, but I am having trouble with some libuv functions because I still don't fully understand them. My basic procedure is the following:

Create a new tcp connection using the uv_tcp_t and uv_connect_t objects
In the connect callback, send off the first message using uv_write
In the write callback, create uv_poll_t around the same socket and wait for http response

However, I get seg faults from within libuv (in uv_poll_start), so I think something is wrong with the way I create the uv_poll_t handle. I'm using the same uv_poll_init_socket call that the server uses, is there anything I am missing?

You need to use Unix syscalls directly except for uv_poll_t which wraps the epolling. Uv_tcp_t is wah too heavyweight.

Hmmm, but the regular connect() call is blocking, wouldn't that go against the point of this library?

Wait, nevermind, I see you can set it to non-blocking mode, and I could have libuv wait on it for me Thanks. ;)

any updates on this ? it's cumbersome to have websocket++ for the client part and uWS for the server.

authors: LordMajestros SEAPUNK alexhultman jcelerier jimmyt857 lpinca

repo: uNetworking/uWebSockets


text:
When the user logs in, should show an indicator while the chat list is being loaded

Otherwise it can take up to 3 minutes to get all contacts and see the other contact(s) who have uProxy installed, and it feels like it is broken.

done https://github.com/uProxy/uproxy/pull/1003

authors: iislucas lucyhe

repo: uProxy/uproxy


text:
answer messages intermittently disappearing

What I'm seeing is that when A initiates a connection with B, A will receive no ANSWER message from B -- only candidates. Without an answer, no connection is possible.
I've been seeing this with cloud but since @salomegeo reports something very similar in terms of numbers of messages correlating with connection success, I'm thinking this is something more serious.

Solved, I think. Not seeing this anymore.


text:
Revamp call-to-action and swap column order on front page

Closes #66.
This PR:

Adds to, and improves, the call-to-action instructions on the front page
Moves the call-to-action column to the left, and map column to the right, to improve f-scan design
Makes the call-to-action and map click results text bigger to be consistent with the rest of the text in the add_text branch

To test, load the app and make sure the instructions on the front page are clear.

I made a few cosmetic changes:

Bold on the default placeholder text, + made that more self-explaining
Removed all-caps OR + replaced with or...   (OR wasn't parsing for me as a word fragment)

Craig, plz test in other browsers and if you think it looks OK merge.

authors: brucecrevensten cstephen

repo: ua-snap/serdp-fish-and-fire-webapp


text:
the CUB datasets has no .mat files now

Hi, I tried to download the CUB datasets and found the data are all images, not .mat files.
and there are no 'cachedir', so the given preprocessing file can't work.
raw_path = '../../../data/cub_raw/CUB_200_2011'
new_path = '../../../data/cub'

target_size = 128

train_anno = sio.loadmat(os.path.join(raw_path, 'cachedir', 'cub', 'data', '{}_cub_cleaned.mat'.format('train')), struct_as_record=False, squeeze_me=True)['images']
val_anno = sio.loadmat(os.path.join(raw_path, 'cachedir', 'cub', 'data', '{}_cub_cleaned.mat'.format('val')), struct_as_record=False, squeeze_me=True)['images']
test_anno = sio.loadmat(os.path.join(raw_path, 'cachedir', 'cub', 'data', '{}_cub_cleaned.mat'.format('test')), struct_as_record=False, squeeze_me=True)['images']

(base) kkk@amax:~/datasets/CUB_200_2011$ ls
attributes  bounding_boxes.txt  classes.txt  image_class_labels.txt  images  images.txt  parts  README  train_test_split.txt

so I don't know how to preprocess the CUB dataset.

I already found the solution. Thanks~
https://github.com/akanazawa/cmr/issues/3#issuecomment-451757610

repo: ubc-vision/StableKeypoints


text:
Dump all registered activities when activity not found

This commit modifies task handler in the client SDK to dump all activities registered when a workflow executes an activity whose name is not found, for example, due to a typo when specifying the activity by name.

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

Coverage decreased (-0.2%) to 60.783% when pulling 9a92843e45ae3a1d12aad15aa67ab858a976af4c on arthurguber:DumpActivityName into d9f51e86e9e3001c5e832e84627d9ae766003ef6 on uber-go:master.

authors: CLAassistant arthurguber coveralls

repo: uber-go/cadence-client


text:
[PiranhaJS] Fix dependabot alerts

Bump lodash from 4.17.19 to 4.17.21
Bumps glob-parent from 5.1.1 to 5.1.2.

Made changes to the package based on
https://github.com/uber/piranha/pull/138
https://github.com/uber/piranha/pull/130
This is likely due to the change in process with dependabot

repo: uber/piranha


text:
Y axis zoom

hi, I have successfully added zoom along the x-axis( using this https://uber.github.io/react-vis/examples/charts/zoomable-chart )but i want to zoom along the y-axis as well. any suggestions on how to do that? thank you

I have some old code laying around where I modified the existing example.
Clicking on the x or y axis results in a zoom along the selected axis. Clicking inside the graph results in a zoom on both axis at the same time. The code is available here: https://codesandbox.io/s/3ql7o7lyr6.
Be careful for bugs, this was some of the first work I did in Javascript and react...

I extended the highlight example to zoom X and Y and fixed the offset. Take a look : #858

The new highlight component addresses this!

authors: Domino987 jonnydodad mcnuttandrew thdhondt

repo: uber/react-vis


text:
Edit README.md

The code snippets should be American spelling. Can we rewrite the code so that works?
Do we want the build status to show?

@Raynos

do you we really have to rename licence to license :(

everything else lgtm.

:(
How many minutes would it take?
I'm thinking the rename will save time in the long run, since it'll be a
bit more intuitive (for most engineers) and match the documentation. But if
it's a huge project of rewriting, that might not be true.
On Tue, Nov 17, 2015 at 5:39 PM, Jake Verbaten notifications@github.com
wrote:

everything else lgtm.
—
Reply to this email directly or view it on GitHub
https://github.com/uber/uber-licence/pull/9#issuecomment-157569670.

+1
we are in SF

@Raynos hi! I just saw this is still open 😈
@macalinao I'm going to close this—not sure who still works on this—but hope someone with write access carries the license torch. 🔥

@Lupie thanks for cleanup. Hello from Seoul.

Seoul! Wonderful, hello!
I need to hit you up about some Node project too. 🤓

authors: Lupie Raynos simplyianm

repo: uber/uber-licence


text:
add JmesPathExtractor

Description
add json extractor which uses "io.burt.jmespath"
How Has This Been Tested?
Junit test

Peux-tu alimenter la documentation pour le composant ?
Voir component_reference.xml, la doc html est générée avec ant docs-site
Merci

Bonjour Philippe,
Je vais le faire toute de suite, merci.
Cordialement
Qianqian SHA
UBIK LOAD PACK notifications@github.com于2019年8月22日 周四15:32写道：

Peux-tu alimenter la documentation pour le composant ?
Voir component_reference.xml, la doc html est générée avec ant docs-site
Merci
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ubikloadpack/jmeter/pull/57?email_source=notifications&email_token=AFI7BD2DYEK5DKN73BRQXCLQF2IN7A5CNFSM4IIR2RN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD45DGAI#issuecomment-523907841,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFI7BD6XTODIRPWJWDWORF3QF2IN7ANCNFSM4IIR2RNQ
.

Bonjour Philippe,
J'ai fait le document pour JMES Path, pouvez-vous m'aider de regarder?
Cordialement
Qianqian SHA
shaqianqian sqq940814@gmail.com 于2019年8月22日周四 下午3:40写道：

Bonjour Philippe,
Je vais le faire toute de suite, merci.
Cordialement
Qianqian SHA
UBIK LOAD PACK notifications@github.com于2019年8月22日 周四15:32写道：

Peux-tu alimenter la documentation pour le composant ?
Voir component_reference.xml, la doc html est générée avec ant docs-site
Merci
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ubikloadpack/jmeter/pull/57?email_source=notifications&email_token=AFI7BD2DYEK5DKN73BRQXCLQF2IN7A5CNFSM4IIR2RN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD45DGAI#issuecomment-523907841,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFI7BD6XTODIRPWJWDWORF3QF2IN7ANCNFSM4IIR2RNQ
.

Merged with some adaptations into core through:
https://github.com/apache/jmeter/pull/489

authors: shaqianqian ubikloadpack

repo: ubikloadpack/jmeter


text:
Failed to initialize helm using microk8s helm init

After enabling helm using microk8s enable helm, trying to initialize helm using microk8s helm init fails with the following error message:
$ microk8s helm init
Creating /home/wyp/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Error: error initializing: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Failed to fetch https://kubernetes-charts.storage.googleapis.com/index.yaml : 403 Forbidden

Looks like a permissions issue?
If I click on the said link to index.yaml, it returns an XML document instead:
<Error>
  AccessDenied
  <Message>Access denied.</Message>
  Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object.
</Error>

Please run microk8s inspect and attach the generated tarball to this issue.
inspection-report-20220102_170233.tar.gz

Nvm, looks like I found the fix in this StackOverflow page
I modified it into
microk8s helm init --stable-repo-url https://charts.helm.sh/stable --service-account tiller


text:
remember why we're using 'script' to launch pytest

Add a comment in case we forget why script was needed here.

Thanks

authors: ktsakalozos kwmonroe


text:
Added vulnerability file to represent lack of SELinux prior to 4.4

At the moment this "vulnerability" is showing on the lists of vulnerabilities for each version. Do we want to keep it like that (in that it is a way of elevating privileges) or not (given that it was a design feature and was known about without being regarded as a vulnerability)?

I don't think we want to show it on the lists and we only want to display it on the graph if the "root" node already exists. Regrettably that is likely to be horrible to implement so it might be better to leave it as is at the moment and implement such things later if sufficiently useful?

repo: ucam-cl-dtg/android-vulnerabilities


text:
Introduce nb field for capabilities

Part of #11
https://github.com/ucan-wg/spec#241-nb-non-normative-fields

nb has been removed in 0.10.0. The capabilities are currently defined as:
{
    "att": [{ "with": "$RESOURCE", "can": "$ABILITY", "nb": "$UNUSED" }]
}

As of 0.10.0, att should be renamed to cap, with a structure like:
{
  "cap": {
    "$RESOURCE":  {
      "$ABILITY_1": [{}],
      "$ABILITY_2": [{ "foo": "bar" }]
    }
  }
}

authors: cdata jsantell

repo: ucan-wg/rs-ucan


text:
Has capability test

This PR adds some tests for the hasCapability method. These were things that I was curious about when I was looking at how to validate permissions via UCAN. There is still one question I had, about the originator field. I made a test that currently fails -- https://github.com/nichoth/ts-ucan/blob/f2fde61b72adcd0a434e5ce1ba91cfe1d834fba1/tests/attenuation.test.ts#L296 -- the question is how is originator used? It doesn't seem to affect the return value of hasCapability. I'm not sure if this is not implemented yet or if my test is wrong in some way.
Thanks. Hopefully this is helpful and not creating needless work 😬

Thanks, that's an amazing contribution.

the question is how is originator used? It doesn't seem to affect the return value of hasCapability. I'm not sure if this is not implemented yet or if my test is wrong in some way.

Yes, this is a bug. Whoops! hasCapability should check the originator to make sure it matches what's passed in and also check that the time bounds work out. All of that instead of running delegateCapabilityInfo... My bad.
Your contribution is amazing. You've created a failing test case. We'll use that to implement a fix for this.

@nichoth Any chance you can rebase this on main? It should only be two merge conflicts, because the path of ./emailCapabilities has changed to ./capabilities/email, and I changed emailCaps = Array.from( to be multiline.
Would love to get this in so we can fix hasCapability 🙏

I just fixed the type checking with the updates, however there is one type I wasn't sure about -- https://github.com/nichoth/ts-ucan/blob/hasCapability-test/tests/attenuation.test.ts#L234
It is telling me
Property 'email' does not exist on type 'Capability'.ts(2339)

@nichoth this PR is almost good to go. I proposed some changes to this PR in another PR (see the mention above this comment :point_up_2: ).
Once we've merged that PR, we can merge this PR :tada:

Looks good! 👏

authors: icidasset matheus23 nichoth

repo: ucan-wg/ts-ucan


text:
Server Side account validation?

At least check the percentages add up and are all positive?
And/Or validate when an invoice is created.

agree -- we should at least check that they all add up and are positive before saving either on the approval method or the change accounts method

authors: jSylvestre srkirkland

repo: ucdavis/Harvest


text:
Jcs/overbilled warning

Closes #774


text:
Add tips for accessible document creation

One big thing missing from our Accessibility recommendations are tips for creating accessible documents (PDF, Word docs, etc). I attended a webinar where I saw a few slides that discuss the process from different applications. These still have to be tested out, but I'm pretty sure they work. Not sure if the group would want to decide to include this type of recommendation, but if so, we could make accessible HTML versions of the text on these slides to help the campus create accessible documents.

Excellent.
Thanks Eric!
JAMES cOLón
WebMaster
University of California Education Abroad Program
805 893 7268 | eap.ucop.eduhttp://uc.eap.ucop.edu/
UCEAP Systemwide Office
6950 Hollister Avenue, Suite 200
Goleta CA 93117-5823
[http://vmoss-intra.uceap.local/Documents/brochures/Facebook_for_Office.png]https://www.facebook.com/UCEAP
[http://vmoss-intra.uceap.local/Documents/brochures/Twitter_for_Office.png]https://twitter.com/UCEAP
[http://vmoss-intra.uceap.local/Documents/brochures/Pinterest_for_Office.png]https://www.pinterest.com/uceapabroad/
[http://vmoss-intra.uceap.local/Documents/brochures/Youtube_for_Office.png]https://www.youtube.com/user/UCEAP
[http://vmoss-intra.uceap.local/Documents/brochures/Instagram_for_Office.png]https://instagram.com/uceap/
[http://vmoss-intra.uceap.local/Documents/brochures/Blog_for_Office.png]http://blog.eap.ucop.edu/
From: Eric Mayes [mailto:notifications@github.com]
Sent: Tuesday, July 07, 2015 3:09 PM
To: ucsb-wsg/ucsb-wsg.github.io
Subject: [ucsb-wsg.github.io] Add tips for accessible document creation (#57)
One big thing missing from our Accessibility recommendations are tips for creating accessible documents. I attended a webinar where I saw a few slides that discuss the process from different applications. These still have to be tested out, but I'm pretty sure they work. Not sure if the group would want to decide to include this type of recommendation, but if so, we could make accessible HTML versions of the text on these slides to help the campus create accessible documents.
[demystifying-wcag-20-an-intro-to-web-office-indesign-pdf-accessib]https://cloud.githubusercontent.com/assets/7233610/8558504/822ebdea-24b9-11e5-850e-6fe60247641e.jpg
[demystifying-wcag-20-an-intro-to-web-office-indesign-pdf-accessibility-55-638]https://cloud.githubusercontent.com/assets/7233610/8558506/823225e8-24b9-11e5-996c-c18701407ff2.jpg
[demystifying-wcag-20-an-intro-to-web-office-indesign-pdf-accessibility-56-638]https://cloud.githubusercontent.com/assets/7233610/8558505/82318f70-24b9-11e5-860c-19e475da53c2.jpg
[demystifying-wcag-20-an-intro-to-web-office-indesign-pdf-accessibility-57-638]https://cloud.githubusercontent.com/assets/7233610/8558508/82354dfe-24b9-11e5-9226-99952d3e5ceb.jpg
[demystifying-wcag-20-an-intro-to-web-office-indesign-pdf-accessibility-58-638]https://cloud.githubusercontent.com/assets/7233610/8558507/823337f8-24b9-11e5-80bb-dfce44a85163.jpg
—
Reply to this email directly or view it on GitHubhttps://github.com/ucsb-wsg/ucsb-wsg.github.io/issues/57.

I have created a Wiki page for Accessible Dcoument Tips in which I attempted to convert all this to HTML. Feel free to edit and correct the page as needed.
I added a section on like proper use of Word Processors.
An interesting side note is this only covers like PDF generation, not say providing a PowerPoint file to end-users, or a normal Word file which is what I created a section for. Also while an accessible PDF may want a 1st page of the document title -- few real world PDFs i've ever linked on a website for an event such as a Flyer or other promotional material ever do this. This seems like a recommendation for a course material pdf, lab workbook, etc.
The purpose of the 1st page would be (I suppose) to announce the title of the PDF so it just doesnt start on content -- but 1 could argue a proper filename on the PDF is just as expressive and useful (god I hate grad003-2015(4).pdf filenames).
Feedback appreciated.

Thanks for bringing this up @ericmayes! And thanks for moving this into the wiki, @tenken!
@tenken, I made a few (minor) revisions:
https://github.com/ucsb-wsg/ucsb-wsg.github.io/wiki/Accessible-Document-Tips/_compare/9d9a10f5b1e1d8047b9d1a46883778167d358ba2...660413c70072b0c0442dfcbb6efc272fc2a03b76
I think we're good to close this issue since @tenken did such a good job of moving over the content from the slides.
Did you want to create a separate issue for PDF accessibility issues, @tenken?

Are we good to close this, @tenken @ericmayes @UCEAP-JCOLON?

authors: UCEAP-JCOLON ericmayes loganfranken tenken


text:
Revisar y ajustar los codigo definidos por la norma de colombia compra eficiente

Se debe realizar la revisión y posterior ajuste para que a nivel de cliente al ingresar los código de los distintos niveles (grupo?, segmentos, familia y clase y el consecutivo del elemento  a registrar en la clase) tener en cuenta que cada nivel ocupa dos dígitos y se relacionan ejemplo:
14000000 Segmento : Materiales y Productos de Papel
14110000 Familia : Productos de papel
14111500 Clase : Papel de imprenta y papel de escribir
141115001: elemento1
141115002: elemento2
La issue debe cumplir con los siguientes requerimientos:

[x] Se debe bloquear en un nivel inferior los dígitos del código anterior pues el nivel superior ya cuenta con un código establecido

[x] Se debe ir construyendo el código automáticamente cuando se deciente de nivel

Se realiza la revisión y se realiza el despliegue en pruebas


text:
hi after wordpress 5.6 update WP-Stateless stops uploading images

it stops syncing and uploading, disconnecting everything works normal what can I do to fix it?

We cannot replicate that. Please, try deactivating all plugins except WP-Stateless and test again.

authors: DeividyRamires antonkorotkov

repo: udx/wp-stateless


text:
Add WP_STATELESS_SKIP_ACL_SET for skip ACL set for GCS

Hi there,
currently this plugin fails when GCS bucket created with uniform bucket-level access, that not support ACL. So plugin cannot insert legacy ACL for an object when uniform bucket-level access is enabled.
This PR add WP_STATELESS_SKIP_ACL_SET constant, that fix it.
Solve #521

Hello @vsychov
Thank you for your involving.
We are going to release this feature with new version of WP-Stateless.

authors: planv vsychov


text:
Possibility to show which dictionary does a word belong to ?

For example, with the cmp-path plugin, the type (file/folder) of each choice is displayed:

Is there any way to get the source dictionary in the same way ?
For example, I have two dictionary files: path/to/dic/EN and path/to/dic/FR. I would like, instead of the Text placeholder, have the corresponding file (EN/FR in my case) :

I don't have any dev experience in lua nor vim so I really don't know how feasible that would be based on your implementation.
Regardless, thank you for your time and efforts with this nice plugin 😃

That's a feature embedded in the main unit. As you can see here, what I can specify from the source are 25 enums (which are actually numbers) that correspond to LSP items, and the corresponding text is displayed. "Text" itself is not specified by this plugin (maybe).
https://github.com/hrsh7th/nvim-cmp/blob/286b9f78d1013d4f4d3a70efcc803d00912dfe35/lua/cmp/types/lsp.lua#L108

Oh, I asked hrsh7th about it, and it looks like it can be done, so I'll try it when I wake up (it's midnight in my country now, so I'm going to bed).

I have dictionary=/usr/share/dict/words, so it shows up like this. What do you think?

There's no reply, so I'll close it.

My apologies, I was incapacitated for the past few months.
This is indeed what I was looking for, thank you very much !

authors: uga-rosa vorban

repo: uga-rosa/cmp-dictionary


text:
[Plato imports] Proxies & Plato improvements

Draft, to be prioritised and refined
Algemene Plato epic: https://github.com/ugent-library/biblio-backoffice/issues/1348

Bugs
Encoding issues [secondary]
https://github.com/ugent-library/biblio-backoffice/issues/1642
Supervisor draft en withdrawn: zichtbaar in dashboard [not a bug but a decision]
https://github.com/ugent-library/biblio-backoffice/issues/1715

PR review nodig:
Removed suggestion
https://github.com/ugent-library/biblio-backoffice/issues/1728

Later:

Add search to proxy dashboard (later, now ctrl + f)

Miet only

fix title in header (more similar to overview?)
bib message read-only on different tabs
Hide biblio-rejected for researchers
https://github.com/ugent-library/biblio-backoffice/issues/1679

Plato:

Hide rejected suggestions for researchers when removed by librarian

Forms:

make 4 questions required

Restructured in other issues

repo: ugent-library/biblio-backoffice


text:
Net::HTTP::Request isn't thread safe (due to an apparent rakudo bug)

I was able to narrow down concurrency bugs I've been having with Net::HTTP to this issue: https://rt.perl.org/Public/Bug/Display.html?id=131985.
While this is definitely a bug in Rakudo, it'd be nice if Net::HTTP::Request worked around it in the short term (by removing {} interpolating from header2str, start-line and path.)
Reproducing the problem is straightforward:
#!/usr/bin/env perl6

use v6.c;

use Net::HTTP::Request;
use Net::HTTP::URL;

await((1 .. 5).map: -> $tid {
   start {
      for (1 .. 100) -> $index {
         my $request = Net::HTTP::Request.new(:url(Net::HTTP::URL.new("http://www.google.com/$tid/$index/")), :method('GET'), :body(), :header({
            'Tid'   => $tid,
            'Index' => $index,
         }));
         my $s = ~$request;
         say "GET /$tid/$index ???? $s" unless $s ~~ /GET\s\/$tid\/$index\//;
         say "Tid: $tid        ???? $s" unless $s ~~ /Tid\:\s$tid/;
         say "Index: $index    ???? $s" unless $s ~~ /Index\:\s$index/;
      }
   }
});

Thanks for discovering this as well as digging in to find the issue. I've added a test for this here

Excellent, thanks for the quick fix :)

@dlowe just as a heads up Cro was released for Perl 6 in the last few days, which contains a http/http2 client among other things. An example request.
Net::HTTP still may be what you want to use though. For one, Cro is asynchronous - and while this is usually a good thing (will scale infinitely-ish better) its probably easier for most to write things using blocking code. Additionally Net::HTTP has no dependencies (save for IO::Socket::SSL/OpenSSL if you visit https sites), while Cro has quite a few (some of which fail their tests; their site recommends installing with the --/test no test flag for what I presume is test failures resulting from optional features).
Ultimately Net::HTTP would do some things similarly, like returning a Response once the header is received and only blocking again if the response body is requested before the rest of the request is received (this simply wasn't possible until the 2017.07 release of moarvm, which allowed a socket to be read from a thread besides the one it originated from - a libuv limitation).

Thanks for the pointer. For now, Net::HTTP is a better match for my use case, but I will keep an eye on Cro :)

Fixed in rakudo with https://github.com/rakudo/rakudo/commit/59454b03cc3e12fd9236ecb980669f8712961141

authors: dlowe ugexe


text:
Does not match timestamp pattern in request body

Hi, first of all, thank you for the great work you do.
I'm using this server to stub an external service during tests. I use PactJVM to generate the pacts.
In request specification, I have a parameter of type timestamp:
pactDsl
  .uponReceiving(...)
  ...
  .body(newJsonBody(body -> body
    .timestamp("date", "YYYY-MM-dd'T'HH:mm:ss.SSSZZ")

The request is matched during consumer test with value 2018-12-08T12:05:00.000+01:00, and the relevant part of the pact looks like that:
"$.date": {
              "matchers": [
                {
                  "match": "timestamp",
                  "timestamp": "YYYY-MM-dd'T'HH:mm:ss.SSSZZ"
                }
              ],
              "combine": "AND"
           },

But, when I launch standalone server with this pact and send a request with the same date, the request is not matched, and here is what I get in the server logs:
[DEBUG] (5) pact_matching: --> Mismatches: ... mismatch: "Expected \'\"2018-12-08T12:05:00.000+01:00\"\' to match a timestamp format of \'YYYY-MM-dd\'T\'HH:mm:ss.SSSZZ\': Error(Code(CompleteStr(\":00\"), TakeWhileMN))" }]

I've totally overhauled the date-time matching in both Pact-JVM and Pact-Rust to use the format from Java DateTimeFormatter. You'll need to upgrade to Pact-JVM version 4.1.1 and use the format YYYY-MM-dd'T'HH:mm:ss.SSSXXX. The version 0.4.1 of the stub server will work.

authors: tsayen uglyog

repo: uglyog/pact-stub-server


text:
Could it be driven by hand?

Hi
I want to collect observation and action data generated by expert demonstration. So, How could I drive it manually?
Thanks very much!

Modify the menu Race - Practice - Configure Race - Select Drivers , deselect the sever1 and select player.

Hi how to save the camera/action information., modify the python or the C++ code ? any method in detail.
thanks

@CarbonGU
Hi, Could you tell me how to save the expert driving data in details? Cause I wanna  to adopt imitation learning for TORCS. Thanks very mcuh!

@wengchunlei
Hi, chunlei.
Did you know how to save the expert driving data? Any method in  details? Thank you very much!

@lkhit
You can take a look at YunzhuLi's work.

authors: CarbonGU lkhit shanjgit wengchunlei


text:
Unable to run wdi5 tests on FireFox

Describe the bug
I have wdi5 tests for my fiori app and they are not running on Firefox. I have tried running it locally on my FireFox browser through vscode but I keep receiving a dependency error. I have also tried running it on BAS using the "Headless Testing Framework" [ which uses firefox ],  and receive the statement "Required page not loaded".
To Reproduce
Steps to reproduce the behavior:
Locally:

Install FireFox browser
Install dependencies : geckodriver, wdio-geckodriver-service
Configure wdio.conf.js with capabilities : { [browserName:"firefox"]} and services: ["geckodriver", "ui5"]
Run the tests as usual

On BAS:

Create a workspace with the "Headless Testing Framework" enabled
Configure wdio.conf.js as mentioned in https://ui5-community.github.io/wdi5/#/usage?id=using-bas-with-wdi5
Run the tests as usual

Expected behavior
In both cases, the tests are expected to run on Firefox without any errors [ headless in BAS ].
Logs/Console Output
When run locally:
[0-0] [wdi5] successfully initialized wdio-ui5 bridge
[0-0] 2023-06-20T09:06:48.346Z ERROR webdriver: Request failed with status 500 due to javascript error: Error: Failed to resolve dependencies of 'sap/fe/test/ListReport.js'
[0-0]  -> 'sap/fe/test/TemplatePage.js'
[0-0]   -> 'sap/fe/test/api/DialogActions.js'
[0-0]    -> 'sap/fe/test/api/DialogAPI.js'
[0-0]     -> 'sap/fe/test/api/BaseAPI.js'
[0-0]      -> 'sap/m/p13n/BasePanel.js'
[0-0]       -> 'sap/m/VBox.js': failed to execute module factory for ''sap/m/VBox.js'': e is undefined
[0-0] javascript error in ""before all" hook in "{root}""
javascript error: Error: Failed to resolve dependencies of 'sap/fe/test/ListReport.js'
-> 'sap/fe/test/TemplatePage.js'
-> 'sap/fe/test/api/DialogActions.js'
-> 'sap/fe/test/api/DialogAPI.js'
-> 'sap/fe/test/api/BaseAPI.js'
-> 'sap/m/p13n/BasePanel.js'
-> 'sap/m/VBox.js': failed to execute module factory for ''sap/m/VBox.js'': e is undefined
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async loadFELibraries (/Users/I584814/Diya/ui-tests-bp-validation-ecc/cloud-cap-ecc-bp/app/BusinessPartners/node_modules/wdio-ui5-service/client-side-js/testLibrary.js:99:12)
[0-0] FAILED in firefox - /Users/I584814/Diya/ui-tests-bp-validation-ecc/cloud-cap-ecc-bp/tests/ui-tests/specs/list.spec.js
Spec Files:      0 passed, 1 failed, 1 total (100% completed) in 00:00:38
When run on BAS:

business-partners@0.0.1 wdi5
wdio run ./wdio.conf.js

Execution of 1 workers started at 2023-06-20T06:06:08.416Z
[0-0] RUNNING in firefox - /home/user/projects/cloud-cap-ecc-bp/tests/ui-tests/specs/list.spec.js
[0-0] [wdi5] creating internal control map
[0-0] [wdi5] setup complete
[0-0] [wdi5] browser script timeout set to 16000
[0-0] [wdi5] browser timeouts are {
[0-0]   "script": 16000,
[0-0]   "pageLoad": 300000,
[0-0]   "implicit": 0
[0-0] }
[0-0] Required page not loaded
[0-0] PASSED in firefox - /home/user/projects/cloud-cap-ecc-bp/tests/ui-tests/specs/list.spec.js
Spec Files:      1 passed, 1 total (100% completed) in 00:00:05
Runtime Env :

wdi5/wdio-ui5-service : 1.5.0
@ui5/cli : "1.13.0",
@wdio/cli: "7.31.1",
node : v18.14.0
OS: MacOS Ventura
Browser + Version : Firefox, Version : 114.0.1

Are you using the TestLibrary? It looks like you are not able to load the sap.fe.test library which is a prerequisite for using this TestLib

Yes I am making use of the TestLibrary since I am testing a Fiori app. I have integrated it as mentioned in https://ui5-community.github.io/wdi5/#/fe-testlib?id=how-to-integrate-the-test-library.
Also any idea why the tests would behave differently on BAS?

Additionally is there any reason as to why the sap.fe.test library isn't loading? And are there any ways to resolve this?

authors: Siolto diya-dhan