Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=375373007
https://github.com/Azure/azure-cli-extensions/commit/2eda2edac1b472f8d8980c8ed645feb8452e5a71

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Removing Unnecessary Space from Equations within Custom Environments in thmtools

Please see my question in https://tex.stackexchange.com/questions/698750/removing-unnecessary-space-from-equations-within-custom-environments-in-thmtools.

@dfcheca Please see my answer to your StackExchange question. I think this issue can be closed.

Of course, thank you very much :D


Support selecting tuples (and array of tuples)

I like to use arrays of tuples to get related items in a single query
e.g. something like
select
  id,
  name,
  array(select (child_id, dob) from children where cats.id = children.parent_id) as children
from cats

Minimal query:
select array(
    select (1, 'a') union
    select (2, 'b') union
    select (3, 'c')
) as tuple_array;

p.s. I'm willing to help implement if you point me in the right direction :cat:

Hello! It sounds interesting,


(Another) The supplied role does not have the rights to perform the requested operation

I am attempting to perform the Customer samples -> Get Paged customers action and am receiving the error.
The output of the console window is:
Get Paged customers
--------------------------------------------------------------------------------

Authenticating user.....

Authenticated!

Querying customers.

Partner Exception:
Error Category: Forbidden
Service Error Payload: null
Context: Request Id: 21dd9fd0-db18-4fe6-8e54-cc06620604fa, Correlation Id: 6a42f4ee-f112-4081-8884-a7369f21ad60, Locale: en-US
Base Description: Microsoft.Store.PartnerCenter.Exceptions.PartnerException: The supplied role does not have the rights to perform the requested operation.
   at Microsoft.Store.PartnerCenter.PartnerService.SynchronousExecute[T](Func`1 operation)
   at Microsoft.Store.PartnerCenter.Customers.CustomerCollectionOperations.Query(IQuery customersQuery)
   at Microsoft.Store.PartnerCenter.Samples.Customers.GetPagedCustomers.RunScenario() in C:\Users\gbartley\Desktop\Partner-Center-SDK-Samples-master\Source\Partner Center SDK Samples\Customers\GetPagedCustomers.cs:line 42
   at Microsoft.Store.PartnerCenter.Samples.BasePartnerScenario.Run() in C:\Users\gbartley\Desktop\Partner-Center-SDK-Samples-master\Source\Partner Center SDK Samples\BasePartnerScenario.cs:line 78

Press Q return to the previous screen or R to repeat the current scenario:

I have created the native app registration in Azure AD with the following delegated permissions:

Windows Azure Active Directory

Access the directory as the signed-in user
Read all users' basic profiles
Sign in and read user profile

Microsoft Partner Center (SampleBECApp)

Access Partner Center

The app is registered in Partner Center as a native app using the "Register existing app" link and selected the app that was registered in Azure AD.
The user account I am using is a global admin in both Partner Center and Azure AD.
I have populated the ApplicationId, UserName, and Password values in the UserAuthentication section of App.config with the values from the Partner Center/Azure AD app registration.
However, in the AppAuthentication section of App.config, I am unsure of what to enter for the ApplicationId and ApplicationSecret fields.  The only way I have found to get a secret key is to create a web app registration in Partner Center.  I have been searching and experimenting for days to try to figure this portion out to no avail.  The only scenarios I have found that mention a key or secret is in regards to a Partner Center web app configuration.
Any help would be greatly appreciated!  And let me know if I left anything out that may be useful for debugging.
Thank you!

After more digging through forums, I figured out the issue.  As of the time of writing (2018-03-12), in the Partner Center user management, the user account needs to have:

[Checked] Manages your organization's account as: Global Admin
[Checked] Business profile admin
[Checked] Referrals admin
[Checked] Assists your customers as: Admin agent

Unfortunately, I couldn't find any official documentation stating these requirements.  I previously only had the "Manages your organization's account as" and "Assists your customers as" checkboxes checked with the corresponding admin values selected.

Hi @wgbartley,
I'm glad you found a solution to your issue. however, you need only the last role you mentioned to see customer profiles which are the "Admin Agent" the global admin, business profile admin or referral admin is not needed for this operation.
we will try to update the documentation to reflect this.
Thanks,
Ali


Add support for new devices

I'm starting a new issue to track the work being done in this branch:  https://github.com/raulgbcr/lednetwf_ble/tree/8none1/new_device
Goals
The primary goal is to modularise device support so that we can add support for new devices/protocols with less effort.  There are an increasing number of new Zengge-app based lights which have slightly different protocols and although they appear to be supported by this integration, they don't actually work.   The new code will hide unsupported devices from the users.  This is a difficult decision to make.  If they don't show up, we don't get to hear about them when they don't work  vs  getting bug reports for broken devices.  I think hiding them is the right choice, but it's easy enough to change.
A secondary goal is to add support for the new devices we have seen issues logged about.
Current state
I think it's pretty much ready.  It's certainly ready for testing.  I did have some problems getting notifications hooked up when using a dev container, but all of a sudden it's working again.
I did a bunch of work, then I went on a business trip to Mexico and now I'm back I've forgotten where I got to.  I'm getting back up to speed again now, and it's seems like everything is working.
There are a couple of improvements still to make, and a lot of debugging nonsense to remove.
Adding a new device
You need to add a new file to the models directory.  That file must be named model_0xnn.py where nn is the hex value of the first byte of the manufacturer data passed to us from Home Assistant.
This is picked up here:  https://github.com/raulgbcr/lednetwf_ble/blob/003ad946a382f8efa986f9fa6bfa4b47a56062f6/custom_components/lednetwf_ble/config_flow.py#L58-L59
You need to add a variable SUPPORTED_MODELS as a list containing the value of the first byte.  If your integration supports multiple models, add multiple values.  If you find a new device which is supported by an existing model you can just add the value to the list on the exiting model.
You then need to import the DefaultModelAbstraction from model_abstractions.  Then you need to implement the model specific code for setting effects, colours, brightness, speed etc and to handle notifications.  model_0x56.py is a fairly straightforward example that you can copy & paste.
Anticipated next steps
Lots of testing
We should encourage users to try the new version, but I don't know the best way.  I've sent a few people to the branch and had some success, but I was thinking now that we're in HACS proper - could we do a beta release?  I have no idea what's involved.
Make a release
It'd be cool if we could get this out before Christmas day and give those folks with lights up at home a nice surprise when they suddenly appear in HA. :smile:

@raulgbcr FYI ^
Any idea how to make a beta release?
Do you think we're ready for that yet?
I'd like probably the rest of the weekend to try and get things tidy before we do one.

I have no idea how to do a beta release yep, maybe a normal one with "beta" in the name?
I've also been pretty disconnected from this alltogether, don't really have the time at the moment to try and keep up with all the stuff happening in life right now. I will be happy to help test for sure though!
Also wanted to ask if transfering the repo is something you would like, since you are basically doing 99.99% of the work being done in here I don't really see the point on keeping it myself when you are crunching through it, I will be more than happy to do that!

I think I solved the beta thing.
No worries, I totally understand - you should focus on home life, not blikenlights :D
Re: transferring - sure.  I don't mind either way, but I think it makes sense.  I don't know what will happen to the old URL, and HACS integration but I guess we'll find out.  :)
Let's try it and see what happens!

Cool!!
I think I have initiated a transfer, but I have no idea how it works hehe


Changed View.propTypes to ViewPropTypes

In order to prevent Unhandled JS Exception: undefined is not an object (evaluating 'b.View.propTypes.style') on react-native 0.49.*

@SudoPlz merged


Invalid xref stream index

I am able to use many pdfs, but I have one that is giving me the error:
Invalid xref stream index: index says 1 objects, but space for 42

As the error suggests, there are 42 fields on the pdf form that should be fillable, but only the first one appears.  That first field is a "Clear All" action that appears as a checkbox in the demo fields area.  I can attach a link to the pdf in question if that helps.  Thanks!

The problem with xrefs is fixed in master already; I will prepare a release. In any case, I definitely need a copy of a the PDF file to reproduce the issues, so please do link to it.

The problem with xrefs is fixed in master already; I will prepare a release. In any case, I definitely need a copy of a the PDF file to reproduce the issues, so please do link to it.

I am excited about this repository and that you are still actively developing it!  https://s3-us-west-2.amazonaws.com/bering-reservations/Original+OSM.pdf should get you the pdf I've been working on.  Thanks!

I am experiencing this issue with the W9 form.


uploading as {FileName}.part

I have an issue. It's uploading like {FileName}.part .I've checked php.ini and nothing wrong. I guess there is a problem with :
if ($chunk == $chunks - 1) {                 $file = new UploadedFile($filePath, $originalName, 'blob', filesize($filePath), UPLOAD_ERR_OK, true);                 $result = $closure($file);                 @unlink($filePath);             }
I think UploadedFile is not working for some reason but I didn't understand. Can you help me ?

I don't have enough information to help you. Do you get an error in your laravel log? Do normal uploads work? How does to html look like...

I can't help you if you don't give any information, therefore i will close the issue.


test: update ava & nyc version

按照ava官方的建议，升级ava和nyc相应的版本 https://github.com/avajs/ava/issues/1800#issuecomment-389083915

修正版本更新后webpack自带的uglify插件报错问题

Coverage increased (+0.03%) to 75.079% when pulling bb5de3018db7fc2b0f32c5b8b59f2147ef03c184 on xtx1130:tb-fix-uglifyjs-bug into 92c18f12fd0a7575b9593c1359e160f2babe2bfc on lavas-project:feature-entry.

Coverage increased (+0.03%) to 75.079% when pulling bb5de3018db7fc2b0f32c5b8b59f2147ef03c184 on xtx1130:tb-fix-uglifyjs-bug into 92c18f12fd0a7575b9593c1359e160f2babe2bfc on lavas-project:feature-entry.


Mobile browser debugging demo, unable to connect to wallet

connectkit version: 1.2.2
I tried nextjs and vite, built the environment locally, and ran it on Android Google Browser
1: tap Connect Wallet.
2: tap MetaMask,Called up Metamask Dapp.
3: After entering Metamask, sometimes there is no response at all, and sometimes the following prompts appear in Metamask.

https://docs.family.co/connectkit/try-it-out
The example in the document can be connected to a wallet

Are you using Metamask on Chrome? The recent update has caused bugs with Metamask.
https://github.com/MetaMask/metamask-extension/issues/18453

Thanks for letting us know about that @sjunaiduk!
Closing this issue as this is a bug with MetaMask and not ConnectKit.


Added the ability to pass parameters to the function in stream_generator

Feature Summary and Justification
This feature provides the ability to pass parameter the generator function in the stream_generator helper.

Can you please provide an example of how you'd like this to be used?

I have a flair removal bot that could benefit from having this.
    If mod_action:
        do stuff
    else:
        continue

This would allow me to only get 'editflair' mod action instead of all of them.

@bboe Made all of those changes for ya.

@Pyprohly It's a precursor to the next pr I'd like to made. See: https://github.com/LilSpazJoekp/praw-1/tree/Moderation-Streams

Thanks for the PR, I'll take it from here to get it merged in!

Cleaned up and merged via #1049. Thanks for the PR! Looking forward to the next one.


Save image as indexed colors

Hello,
Is it possible to load the image that is in RGB and convert it into an indexed color image ?
Thank you;
Christophe

This does not do any processing on the image except resizing.


Feature Request: Exponential backoff

Would be nice to have an exponential backoff feature when a process fails and you would like to restart it, but then allow that exponential backoff to be reset when the process is "alive" for a certain amount of time. As a start, this could even be simply allowing restartDelay option to take a function instead of a number.
Example:

process fails -> immediate restart
process fails -> restart after 2 seconds
process fails -> restart after 4 seconds
process fails -> restart after 8 seconds
process "succeeds", where "success" is defined as "did not exit for 60 seconds after starting"
process fails -> immediate restart
process fails -> restart after 2 seconds

Hey @mscottnelson! This sounds like a nice feature indeed.
Making --restart-after accept exponential as a special keyword would be nice.

I see about putting together a pull request sometime this month.

🚢 This is now available in v9.0.0!
https://github.com/open-cli-tools/concurrently/releases/tag/v9.0.0


Added in profile to enable shims for SNAPSHOT releases

This fixes #602
I didn't update any of the Jenkins files because they either already use a profile for databricks that would disable the snapshot-shims profile or they have it enabled by default. I could update the premerge to try and have this off by default, but I would need to add a second one that has it enabled too, so we know if we are missing something.

build

so to clarify, this is active by default but if you specify another profile it disables this one? I would think we want this profile specified for everything except the release build.

so to clarify, this is active by default but if you specify another profile it disables this one?

Yes, specifying any other profile explicitly on the command-line will disable the snapshot-shims profile.

I would think we want this profile specified for everything except the release build.

The problem with that setup is we would never be regularly testing what we're planning to ship.
From a cursory glance, it appears the premerge CI is specifying some profiles which would turn this off (mirror-apache-to-urm, include-databricks).  Rather than the implicit behavior, we may want to make an explicit profile, either to include or exclude, so we don't get some surprising behaviors when someone activates a separate profile that has nothing to do with shims.
Also how would this interact with the spark*tests profiles?  If someone specifies the spark301tests profile, will it turn off the snapshot shims and then fail the tests against 3.0.1-SNAPSHOT because it cannot find the shim?

I agree that we should probably be specific about all of the profiles for the builds.
I missed the $MVN_URM_MIRROR having a profile in it too, so I'll try to make it clearer what is happening there.

Also how would this interact with the spark*tests profiles?
From my experience with maven there is no way to have one profile activate/deactivate another profile.  We could, however, have a property that activates multiple profiles. So they would both be independent of each other.

We could, however, have a property that activates multiple profiles

+1 for this.  That way we can ask for spark versions to test against with property settings, and those will enable both the test profile for a spark version along with the shim if that shim version happens to be a snapshot.

I would have to do some testing to see if we can make it work mixing properties and explicit setting of profiles.

build

if we want to keep integration testing nightly what we actually push, then we would need 2 separate jars - one with shims and one without, otherwise we aren't integration testing the shims which I think is a bad idea.
otherwise we push the version with all the shims and then just test the one without shims differently.  This doesn't seem high risk to me to have to test it on every premerge, I would rather just test nightly or something before a release.

build

@tgravescs I addressed your comments on the nightly deploy.


New-CsAutoAttendant Example 3 not valid

I think Example 3 in New-CsAutoAttendant is no longer valid.
https://github.com/MicrosoftDocs/office-docs-powershell/blob/master/skype/skype-ps/skype/New-CsAutoAttendant.md
When I try to create two Attendant who share the same Schedule I get this error message:
New-CsAutoAttendant: After hours schedules should not be shared by multiple auto attendants.

Hi @heintonny, thank you for your feedback.
The only error I found in example 3 is executing New-CsAutoAttendantMenu cmdlet:

I had to add the last parameter:
$dcfMenu = New-CsAutoAttendantMenu -Name "Default menu" -Prompts @($dcfMenuPrompt) -EnableDialByName -DirectorySearchMethod ByName
As you can see, both AA were assigned to the same schedule:

Are you using the latest version of the module? (3.1.1)


Difference between Hero6 and Hero7 data?

Hello and thanks again for making all this great work available.
I'm noticing that the quality of the gyro data in the GPMF varies from the Hero6 and the Hero7.  If you compare the two camera's gyro readings under a high amount of vibration (for example when attached to a drone), the Hero 6 gives higher quality data that matches the video more closely than the Hero 7 which will look much more noisy and error-filled.  I assume this isn't a problem with the gyro itself because the fantastic Hypersmooth stabilization of the hero 7 has no problem handling the same vibration of the drone.  Is there some sort of filtering that happens to the gyro samples before they are written to GPMF in the Hero 6 that is not active in the Hero 7?  It was my understanding the hardware of the two camera was identical with exception of more ram for performing the hypersmooth stuff.  Very curious about this.  Thanks!

I this will take some investigation time.  Yes, they should be the same.  I expect it has something to do with the new Hypersmooth stabilization which runs the Gyro at a much higher frequency than the data it stores -- all that sub-frame, rolling-shutter compensation, goodness comes from gyro data significantly faster than the 200Hz stored.  I'm guessing the HERO6 used IMU based hardware downsampling, but HERO7 might be doing it downsampling elsewhere (this is what I will try and determine.)

I have not found a good fix for this.  The IMU data stored with H7 is simply not a clean as H6.  I have reported the bug, and hopeful it does not reoccur in future cameras.

Thanks very much for your time on this!  Is there any chance this might be patched in the next firmware update?

I don't know that is can be, it might be a limitation of the IMU hardware configuration which was designed for the best results in Hypersmooth.

Thanks again for the info!  That's interesting.  From this teardown here https://gethypoxic.com/blogs/technical/gopro-hero7-teardown the author claims the only hardware changes from the Hero 6 to the Hero 7 are the Apple MFI, The 2GB of ram, and Pericom PI3USB9281 charging component.  If that's true, does't it seem possible that Hero 6 style of gyro recording may work on that configuration?

The IMU parts might be the same, but the wiring for the clocking is different. Something (beyond my understanding) was changed with the IMU to support Hypersmooth, it was more than just the increase in memory.

Also very interesting. Thanks!

Different wiring or different algorithm ?

Just wanted to ask one more thing before I give up.  I understand that "Something (beyond my understanding) was changed with the IMU to support Hypersmooth".  What if a firmware update was produced that only changed the shooting modes where hypersmooth is not active.  Would it be possible to use the Hero6 style gyro recording in only those modes?  Or is this a hardware thing that's underneath what the firmware can control?

I believe it is a hardware change beyond firmware control.

As far as I can tell, the HERO7 consumes all the gyro data and then adjusts
the "timestamp" before it passes to the EIS algorithm. The HERO6 doesn't do
this step. The hardware is the same but how the HERO6 and HERO7 consume the
gyro data is much different. To me it appears like a low pass filter or the
ODR is slower on the HERO7. David could compare
"drv_gyro_bmg250_get_data_samples" and tell us what is different.
On Thu, Mar 21, 2019 at 8:10 AM David Newman<EMAIL_ADDRESS>wrote:

I believe it is a hardware change beyond firmware control.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gopro/gpmf-parser/issues/47#issuecomment-475269321,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADLrrUuUUm4S5YVZqsylXQ4rVGwBsR5rks5vY6EAgaJpZM4ZbU-V
.

Any update on this out of curiosity? Since the GoPro itself is still getting all the data, is there any way it can be downsampled in the firmware before outputting it? Am I thinking about this the wrong way? I would think if Hypersmooth works as well as it does without funky vibration-dampening mounts it'd be possible to get some cleaner gyro data to use, maybe via a firmware update that adds some additional downsampling and/or filtering in non-stabilized modes. Would it be possible to just output gyro data at a higher frequency and do filtering afterwards? Just a thought, probably spewing nonsense.
I and many others would love to have a Hero 7 with usable gyro data out, I don't want to have to downgrade to a Hero 6.

So what's the final result  @dnewman-gpsw  , @hypoxic  , @tenten8401  , @kikislater  , @noobtoob4lyfe
I'm excited to hear some good news 😁

No go unfortunately. Ended up just buying an 8 :(
Oct 16, 2021 7:12:46 PM Moksh @.***>:

So what's the final result @dnewman-gpsw[https://github.com/dnewman-gpsw] , @hypoxic[https://github.com/hypoxic] , @tenten8401[https://github.com/tenten8401] , @kikislater[https://github.com/kikislater] , @noobtoob4lyfe[https://github.com/noobtoob4lyfe]
I'm excited to hear some good news 😁
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub[https://github.com/gopro/gpmf-parser/issues/47#issuecomment-945019585], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ABPDNBZ5BE5IDYXBU3BRANDUHIBF7ANCNFSM4GLNJ6KQ].
Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub].  [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAD8AAAA/CAYAAABXXxDfAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAmSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAAAAAAAAJwY+QwABivJx1AAAAABJRU5ErkJggg==###24x24:true###][Tracking image][https://github.com/notifications/beacon/ABPDNB5GDZW7HHC7LRZYACLUHIBF7A5CNFSM4GLNJ6K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHBJ5VQI.gif]

No go unfortunately. Ended up just buying an 8 :( Oct 16, 2021 7:12:46 PM Moksh @.***>:
…
So what's the final result @dnewman-gpsw[https://github.com/dnewman-gpsw] , @hypoxic[https://github.com/hypoxic] , @tenten8401[https://github.com/tenten8401] , @kikislater[https://github.com/kikislater] , @noobtoob4lyfe[https://github.com/noobtoob4lyfe] I'm excited to hear some good news 😁 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub[#47 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ABPDNBZ5BE5IDYXBU3BRANDUHIBF7ANCNFSM4GLNJ6KQ]. Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAD8AAAA/CAYAAABXXxDfAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAmSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAAAAAAAAJwY+QwABivJx1AAAAABJRU5ErkJggg==###24x24:true###][Tracking image][https://github.com/notifications/beacon/ABPDNB5GDZW7HHC7LRZYACLUHIBF7A5CNFSM4GLNJ6K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHBJ5VQI.gif]

What about change the gyro or make fw can do filter the gyro data as need rsgo then maybe it possible , right ?

The problem isn't filtering it, it's that there simply is not enough data.
GoPro is unwilling to fix this so there is nothing you can do. You have to
buy a 6 or an 8-10
On Wednesday, October 20, 2021 6:48:42 PM EDT Moksh wrote:

No go unfortunately. Ended up just buying an 8 :( Oct 16, 2021 7:12:46 PM
Moksh @.***>:
…
So what's the final result @dnewman-gpsw[https://github.com/dnewman-gpsw]
, @hypoxic[https://github.com/hypoxic] ,
@tenten8401[https://github.com/tenten8401] ,
@kikislater[https://github.com/kikislater] ,
@noobtoob4lyfe[https://github.com/noobtoob4lyfe] I'm excited to hear some
good news 😁 — You are receiving this because you were mentioned. Reply
to this email directly, view it on GitHub[[#47
(comment)](https://github.com/gopro/gpmf-parser/issues/47#issuecomment-94
5019585)], or
unsubscribe[https://github.com/notifications/unsubscribe-auth/ABPDNBZ5BE5
IDYXBU3BRANDUHIBF7ANCNFSM4GLNJ6KQ]. Triage notifications on the go with
GitHub Mobile for
iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-e
mail&mt=8&pt=524675] or
Android[https://play.google.com/store/apps/details?id=com.github.android&
referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_sour
ce%3Dgithub].
[data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAD8AAAA/CAYAAABXXxDfAAAAAX
NSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAmSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAA
AAAAAAAAAAAAJwY+QwABivJx1AAAAABJRU5ErkJggg==###24x24:true###][Tracking
image][https://github.com/notifications/beacon/ABPDNB5GDZW7HHC7LRZYACLUHI
BF7A5CNFSM4GLNJ6K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPW
SZGOHBJ5VQI.gif]

What about change the gyro or make fw can do filter the gyro data as need
rsgo then maybe it possible , right ?

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/gopro/gpmf-parser/issues/47#issuecomment-948093507

--
-Isaac

Yeppp thanks mat 🙂


taglib-extras: make taglib-extras work with taglib > 1.9

the current taglib_extras code uses STRLESS to compare versions, this fails because the current version 1.10 is STRLESS then the minimum version 1.6.
I replace the comparison with VERSION_LESS which works as intended.

Please report this bug upstream and encourage them to release a new version that fixes this issue. I believe it's fine to merge this patch here, but there should be a comment in the Nix code that points to an upstream Gibhub issue or some other ticket to make it easier for us to track whether that patch can be removed or not.

@peti I fixed the same error in multiple locations and added comments indicating upstream status.
Interesting that this was not catched by any build system?

@peti I think this PR fails the tests for unrelated reasons. Is there any way to restart the tests?


HAR file generation in Protractor/Phantom using netsniff.js

Hi,  I have been trying to get a HAR file generated for days now, I have been messing with netsniff.js (add on for Phantom) I can get this to work easily enough by calling it directly at the command prompt like this:
bin/phantomjs examples/netsniff.js http://www.google.co.uk > test.har
Is there a way of calling this from within my tests in Protractor, or setting it up some how in the on-prepare function?
Thanks,
Craig.

any update on this.
maybe using chrome-har-capturer


TS Function App QuickStart instructions in wrong order

Under https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-cli-typescript?tabs=azure-cli%2Cbrowser&pivots=nodejs-model-v4#create-a-local-function-project step 4, you ask us to add an storage account name but we don't create one until later in the guide.

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

ID: f63b9c7a-d8ed-dbc2-6e79-3d34ab9fb572
Version Independent ID: 3c24f05f-60b1-0d03-36e7-53503d2c493a
Content: Create a TypeScript function from the command line - Azure Functions
Content Source: articles/azure-functions/create-first-function-cli-typescript.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@smolattack
Thanks for your feedback! We will investigate and update as appropriate.


collection_merge

Updated the original script to include try/except statement when deleting the empty collection, added more test methods to the test script.

Thinking about long-term maintainability, and that this script makes significant database changes, I'd like to see better variable names (i.e. source_collection and destination_collection rather than collection1 and collection2). Similarly, create variables with informative names rather than rather than referring directly to items in a list (array[0]). I'll leave some comments on the code, too.

Awesome! Thanks! Much easier to follow, now.


Standardize on Cats, get rid of shims in monix-types

Whether we should standardize on Cats or not is an open question.
We have supported both Cats and Scalaz in Monix up until now, by providing a shims compatibility layer, similar with https://github.com/djspiewak/shims
However this approach is clumsy and prevents interoperability scenarios with other projects in the Typelevel community. Reasons:

conversion from monix.types.Monad[Task] whenever cats.Monad[Task] is needed is actually expensive, since a new instance gets created every time
users have to do import monix.cats._ by themselves
there will be scenarios in which users will have to do import monix.cats.reverse._, however both of these imports in the same scope don't work
if the Scala compiler will ever support some notion of  "coherent" type-classes (see proposal), then this approach will probably become incompatible, since coherence will most likely receive some protections against abuse, like requiring implementations to happen in the same compilation unit
the upcoming Iterant type would be much more useful if it used the Cats type-classes directly
I don't want to keep reinventing the wheel and if there are useful type-classes that are needed, I'd rather try and push those changes in Cats
currently we cannot use cats.Eval or other data types defined in Cats
Scalaz comes with its own Task implementation and with scalaz-stream - users still on Scalaz probably don't use Monix anyway, unless they are trapped with Scalaz, in which case a Cats-Scalaz bridge might make better sense

Moving forward, in the upcoming 3.0.0 I'd like to get rid of the shims in monix-types and standardize on cats-core as a dependency of monix-eval and monix-reactive. For Scalaz I think a Cats-Scalaz bridge would be better.
Expected problems:

Cats is not stable yet and this is a problem because of binary compatibility issues between minor versions (i.e. DLL hell)
those JAR files for cats-kernel and cats-core are actually big, bigger than Monix, however if a small artifact is needed (e.g. Android, Javascript) then solutions like Proguard / Google Closure are used for doing tree shaking anyway

Feedback appreciated.

Such a decision is premature. Postponing.


refine DerviedColumn method which is dependent on the core path of query

Changes proposed in this pull request:

refine method isDerivedColumn that it will reuse a same object for relative collection

The code readability may not increase during this pull request, cloud you consider about to redesign it?

This pr is intent to improve the performance of GC, consider that the original code will create ArrayList everytime.


[Feature Request] Supporting Scan Page for Scanning Machines

Is your feature request related to a problem? Please describe.
In Area 1, when using the current version of QR Code, the Machine will be stuck and it will be obvious that the ticket is a fake one.
Describe the solution you'd like
While scanning, it will show the fake ticket exactly.
Describe alternatives you've considered
After scanning, it will jump to a fake page and jump back after the next ticket was scanned.
Additional context
May be difficult?

Here is the scan page.


Git Naming Conventions

You might want to change your repo's name to hyphenated-lower-case. Helps with git clone and generally looks cleaner.

The name is not final.


fixed the contributors readme issue.

Added the workflow for fetching the contributors to readme

@Sapna127 did you make it by your own

@Sapna127 did you make it by your own

yes.. I refered this - https://github.com/marketplace/actions/contribute-list


Preview World Map without borders [Feature request]

There should be an option allowing you to view the map modes in the current Preview Map Mode without the black borders between the provinces, states, strategic regions, etc.

Feature supported in 0.4.4.


Just updating fork

Hi @jayhopeter, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;


Fix linting errors

What does this PR do and why?
Ran yarn lint:fix. Mostly moves some imports around.
Screenshots or screen recordings
N/A
Acceptance checklist

[x] I have evaluted the Approval Guidelines for this PR.

@peripheralist WDYT about updating fleek-ci to fail on any eslint warning? I'm guessing we have some config on Fleek somewhere. Alternatively we add a GitHub action specifically for linting (and other stuff in the future).

@peripheralist

I'm into the idea, though I'd prefer to have commits fail if we can (much less frustrating than committing, then having it fail a few minutes into CI)

Yeah, totally agree. Might look into having stricter eslint rules, perhaps.


Envoy v2 + v1alpha3 - Pending items

We have v1alpha3+v2 working with routing tests, basic reachability tests for http/tcp/grpc, and headless services.
Tracking main TODOs

[ ]  1. Need ingress gateway tests and external service tests (directly from sidecar, or via egress gateway using destrules, virt services) (cc @ijsnellf / @GregHanson )

[ ] 2. Enable RDS instead of static routes in LDS, using the existing config gen interfaces. We can refine these over time (cc @costinm )

[ ] 3. Need to enable ingress tests (requires merging multiple ingress resources into one virtual service spec) cc @ZackButcher

[ ] 4. Need to enable auth and mixer plugin - which unblocks auth and mixer e2e tests (cc @diemtvu @ostromart )

[ ] 5. RBAC (is it part of mixer?) e2e tests for v2 seem to fail with RBAC on (cc @liminw or whoever responsible)

[ ]  6. Figure out proper story for mixer checks on external services (cc @mandarjog)

[ ]  7. Auth adapter to automatically create external services (or make user specify them) to enable JWKS auth (cc @diemtvu and co)

[ ]  8. Helm magic to ensure proxyv2 gets deployed or has an option..

[ ]  9. One or more enhancements to DestinationRules, and VirtualServices (filters, etc.) to support specifying settings at server side (e.g., increase circuit breaker pool size, possibly specify faults, etc.) [ on me]

[ ]  10. Need port match in routing (on me)

[ ]  11. Per route fault injection in envoy to enable fault injection on client side (on me)

Do all the above while keeping circleci/e2e-pilot-noauth-v1alpha3-v2 green!
1 to 5 are blockers for 0.8
cc @louiscryan

MTLS testing

I don't think (2) is blocking unless we find bugs with the current route_configs - we'll probably still do it, but maybe treat it as P1.

add secure GRPC port - I think we'll do it in pilot directly.

port matching in routes completed (#4818 )

ingress/egress tests completed (#4819 )

cc @andraxylia / @hklai

(3) mTLS is done, testing remains.. mixer being worked on (#4829 )

@rshriram

Are we going to use v1alpha3 to document bookinfo stuff ?

You have already a section in istio Tasks https://istio.io/docs/tasks/traffic-management-v1alpha3/ .
Additional question is when we remove v1apha2 from istio.io.

This means we need to have bookinfo working with v1alpha3. I don’t think we have it yet.

(10) solved by https://github.com/istio/api/pull/450
(12) is in progress (https://github.com/envoyproxy/envoy/pull/3084)

(5) Submitted a PR https://github.com/istio/istio/pull/5049

(5) Submitted a PR https://github.com/istio/test-infra/pull/805

(3)

basic mixer telemetry is now functional with https://github.com/istio/istio/pull/5012
per route config per_filter_config format change now working, need merge: https://github.com/istio/istio/pull/5073
RBAC (mixer check) not working at first try, need to debug further

(5) Enabled prow/e2e-bookInfoTests-v1alpha3.sh, it is failing now, I will check it tomorrow.

Is it still true that only 1-4 are release blocking?
If so, what is the current status for 2-4 (/cc @ZackButcher, @diemtvu, @ostromart, @liminw)?

v2+authn e2e test works except for TestRoutes and TestGateway_HTTPIngress,
though it might be related to some gateway issues that Zack working on. My
desktop unfortunately dies after the move last weekend so I was unable to
check the status of those tests with the latest codebase yet.
Diem
On Tue, Apr 24, 2018 at 2:26 PM Martin Ostrowski<EMAIL_ADDRESS>wrote:

Last part of mixer filter (mixer client API changes for route filters) is
integrated in master and scheduled to go into release branch: #5170
https://github.com/istio/istio/pull/5170.
RBAC is enabled and passing in the e2e_pilot tests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/4791#issuecomment-384085369, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AX99cWGqyT0UXPau7I8vtd1khU-_KZUGks5tr5iCgaJpZM4TKMKi
.

--
Diem Vu | Software Engineer |<EMAIL_ADDRESS>| +1<PHONE_NUMBER>

@rshriram For item 8, do you mean providing authentication policy for external services?

No. This is for the existing jwks stuff. You cannot add clusters directly. You have to use service entry

@rshriram If I understand it correctly, this is the issue you refer to. It's already addressed in recent PR by Quanjie. The solution is to fetch public keys in Pilot, and send public keys to Envoy instead of sending jwksUri. This way, no cluster needs to be created.

E2e tests for v1alpha3?

e2e test for v2 was added in https://github.com/istio/istio/pull/5261
On Mon, Apr 30, 2018 at 3:05 PM Shriram Rajagopalan <
<EMAIL_ADDRESS>wrote:

E2e tests for v1alpha3?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/4791#issuecomment-385542850, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AX99cTv-LQTbg2MxLxfSOZmKPwhSRiyLks5tt4qfgaJpZM4TKMKi
.

--
Diem Vu | Software Engineer |<EMAIL_ADDRESS>| +1<PHONE_NUMBER>

@rshriram Thanks for listing the tasks. If we are to use tasks instead of epics with sub-issues, it would be good to know who does what and avoid 2 people working on the same time on the same thing.

I am a noob to zen hub. I can’t figure that thing out.  Please feel free to create all those thingies you talk about.

For 12 see #5055

thanks @rshriram ! If the organizing spirit gets the best of me, and it will :), I will create those issues and link them besides the checkboxes, so they are visible also to non-zenhub users.

Could someone provide an updated on "Need to enable ingress tests (requires merging multiple ingress resources into one virtual service spec)"? Is it still 0.8.0 blocking?
@ZackButcher or anyone?

Ingress gateway is sufficiently functional and now part of multiple targeted (in e2e_pilot) and indirect (e2e_bookinfo|mixer) tests. Merging multiple ingress resources is not blocking.

Thanks. All 0.8 blocking issues have been resolved.

Do we have mixer filter integrated with the ingress gateway? From my code
inspection it seemed like it's not using mixer filter in the ingress
gateway config.
On Thu, May 10, 2018 at 11:38 AM Andy Lai<EMAIL_ADDRESS>wrote:

Thanks. All 0.8 blocking issues have been resolved.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/4791#issuecomment-388145590, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxneb31h8H_sdUIgUKi0eqfaMEHOwks5txIk-gaJpZM4TKMKi
.

Yes, it's in https://github.com/istio/istio/pull/5417 which should merge today.

We need RDS to eliminate the 503s.

? We have a 503 test for gateways. And it passes without RDS.

Let me check again, it was not passing a week ago, and I suspected it was because of inlining the routes statically in the Listeners, and causing a Listener config change.


Feedback Panel: make backend call using Apollo client

This is a
[x] bug
[x] feature request
[ ] documentation change
[ ] build/deploy enhancement request
Description:
Use Apollo client to make GQL Mutation call to backend instead of React component making REST API call
Also fix the font styling issue to remove fb font size from tailwind config
Acceptance Criteria:
[x] Use Apollo client to make GQL Mutation call to backend instead of React component making REST API call
[x] Also fix the font styling issue to remove fb font size from tailwind config
[ ] Intergrate MSW to mock API calls

closing since WIT is already completed.


Migration from comprehensiveAdvice() to projectAdvice()

Hi, we're trying to update from 0.80.0 to 1.1.0 and we realized that comprehensiveAdvice was removed from AbstractPostProcessingTask
Is there any guide or documentation to migrate from comprehensiveAdvice to projectAdvice?

Here's the model for ProjectAdvice: https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/blob/main/src/main/kotlin/com/autonomousapps/model/ProjectAdvice.kt
It's basically the same. What exactly is the issue you see?

We used something like this in version 0.80.0:
`
import com.autonomousapps.advice.Advice
private fun AbstractPostProcessingTask.applyDependencyAdvices(
project: Project,
extension: DependencyAdviceApplierPluginExtension
) {
val comprehensiveAdvice = comprehensiveAdvice()
// apply advice
}
`
In the version 1.1.0:
`
import com.autonomousapps.model.Advice
private fun AbstractPostProcessingTask.applyDependencyAdvices(
project: Project,
extension: DependencyAdviceApplierPluginExtension
) {
// comprehensiveAdvice() was removed
// pprojectAdvice returns  com.autonomousapps.model.Advice and not longer com.autonomousapps.advice.Advice
val comprehensiveAdvice = projectAdvice()
// apply advice
}
`

I guess these two are very similar https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/blob/main/src/main/kotlin/com/autonomousapps/model/Advice.kt and https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/blob/main/src/main/kotlin/com/autonomousapps/advice/Advice.kt. But we use the latter for post processing, but projectAdvice() does not use it.

Yes, the latter still exists because it made it easier to migrate my tests without rewriting them. You should migrate to the former, which is the new model. I think they're basically identical, but just in different packages?

Btw, if you want an intermediate step between 0.80 and 1.1, take a look at this note in the readme: https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin#two-models


How do I pass the information about the provisioning profile path to the xcodebuild command ?

Question Checklist

[X] Updated fastlane to the latest version
[X] I read the Contribution Guidelines
[X] I read docs.fastlane.tools
[X] I searched for existing GitHub issues

Question Subject
I'm trying to set up a CI/CD system starting with a CMakeLists.txt.
This means, at not point my xcodeproj file get commited to source control.
I'm running into code siging issues: "No profiles for 'fr.OwlGames.CI' were found".
I'm using match, which retrieves and install the certificates and profiles properly.
As I understand it, xcode has no idea where to look for the profisioning profile.
It probably needs the -exportOptionsPlist with a proper plist file, but that doesn't show up in the generated gym command.
How do I pass the information about the provisioning profile path to the xcodebuild command ?
Question Description
Full log available here : https://travis-ci.org/gheaeckkseqrz/Cocos2d-x-CI/jobs/560214972
Relevant files are here : https://github.com/gheaeckkseqrz/Cocos2d-x-CI/tree/master/proj.ios_mac/fastlane
I have 148 tries, I guess I've tried every possible combination of arguments 😅

Could you please link a specific version of the Fastfile that belongs to a specific CI run? I just wasted some time typing a response until I realized that you change the Fastfile in the meantime, so my analysis of the problem was based on wrong information.


Fix department indexing inconsistency between admin and user dashboards

Resolved an issue where the department was stored as an index in the admin dashboard and as a string in the user dashboard.
Updated code to consistently handle the department using an integer index across both dashboards.
The department is now stored as the index in the database.

Lets store default as string and not as index


Fix web support

Everything works fine on native but on web I get this error:
Error: Assertion failed: file:/.../isolate_bloc-1.0.2/lib/src/common/isolate/isolated_bloc_manager.dart:94:7 _blocCreators.containsKey(blocType) ||        _registeredWrappers.containsKey(blocType)

That was a mistake due to I import dart:io in my isolateBlocInitialization function.


fixed typo in Scene.md

hello this text is actually generated from:https://github.com/BabylonJS/Babylon.js/blob/49bde9f67194ecc773c07a4ee0064fe836914b59/src/babylon.scene.ts#L1276

Thanks for the hint! :)


[UI/Frontend, v1.3.0] Parent taxonomy checkbox icon remains the same when child item(s) is selected

Describe the bug
In Label Studio 1.0,

when one of the child taxonomy is selected, the parent taxonomy has (‒)  icon

when all the children taxonomy are selected, the parent taxonomy has (🗸) icon and the parent is automatically selected

This really helps to see the current choices when reviewing the taxonomy labels as the parent icon is marked differently when the child is selected.
In Label Studio 1.3, the parent checkbox is unchanged if the child / all the child items are selected.

Also, when all the child items are selected, the parent is not automatically selected. In v1.0.0, the selection is collapsed to just the parent (since all the children are selected)

To Reproduce
Steps to reproduce the behavior:
Example labelling interface from https://labelstud.io/tags/taxonomy.html
<View>
  <Taxonomy name="media" toName="text">
    <Choice value="Online">
      <Choice value="UGC" />
      <Choice value="Free" />
      <Choice value="Paywall">
        <Choice value="NY Times" />
        <Choice value="The Wall Street Journal" />
      </Choice>
    </Choice>
    <Choice value="Offline" />
  </Taxonomy>
  <Text name="text" value="You'd never believe what he did to the country" />
</View>

Import any text
Select the child taxonomy label e.g "NY Times"
The checkbox icon for parent will remain the same.

Expected behavior
Parent checkbox should have different icon when the child / all child items are selected.
Environment (please complete the following information):

Browser: Chrome 94, Firefox 88
Label Studio Version 1.0, 1.3

Hi! That's fixed in our frontend library and will be released soon in LS. It's already available in the master branch.

Important note: we removed this "select all childs" behaviour because it's useless in taxonomy labeling, so parent node always in indeterminate state ("–") even if all the childs are selected.


[ROCKETMQ-323] Release semaphore after callback being finished for async invoke

What is the purpose of the change
Currently, the async semaphore will be released before invoking the callback, if the callback is a heavy task which is not recommended, lots of async requests will be queued in publicExecutor thread pool, may cause OOM or FGC.
Brief changelog
Adjust the release order between callback and response future, release semaphore after callback being finished for async invoke.
Verifying this change
Run the provided unit tests.
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ROCKETMQ-XXX] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.02%) to 39.241% when pulling 6c5a9507b4a2243c9a541bb325416502b2281dfb on zhouxinyu:ROCKETMQ-323 into 8c303104830afe53721fad231e671fc12670df8c on apache:develop.

LGTM~


hapd, ucentral-event: fix 802.1x with dynamic VLAN

This adds a workaround to fix an issue with 802.1x + DVLANs on platforms
where LAN ports are through an integrated switch (swconfig).
Netifd is tracking the wired ports as part of a bridge-vlan: either a
static one, or 4090 for the default untagged bridge.  When hostapd
authorizes the wired port, netifd is automatically adding this bridge
vlan as PVID untagged to the port.  The vlan_add event then adds the
dynamic VLAN as untagged to the same port.  The result is that the
port is operating on the PVID bridge vlan, and not the dynamic VLAN.
Fixing this in netifd is going to be complex and take time, so this
change includes a workaround.   When a wired client is authorized
using a dynamic VLAN, ucentral-event takes the following actions:

Remove the bridge VLAN from the port
bridge vlan del dev  vid
Modify the dynamic VLAN to PVID
bridge vlan add dev  vid  pvid untagged

merged, Thanks !


Improve experience in cf push world, multiple instances & no shared db

Environment..

cf push
multiple cf app instances
no shared db

cf push world uses sqlite instance per app instance
this means..

new registered endpoints will not be available in all instances & lost on instance restart/scale down
new features such as favourites also hit this issue

In v1 world we removed the dashboard page in cf push world & no shared db.

@richard-cox I think we did this?


`KeyError: 'x-goog-hash'

occasionally  get KeyError: 'x-goog-hash'  during a goblet deploy.
i believe this is due to an http error when trying to compre the existing google hash to the local hash to determine if code changes have occured.
I will add a try/catch and if x-goog-hash is missing then trigger a redeploy.

Haven't been able to recreate this issue and haven't run into it since so will close for now

if the source zip from the latest build was cleared from the bucket (in this case, lifecycle policy removed it) this line errors out


Install: admin user with special char in password not working

Gitea version (or commit ref): 1.1.0
Git version: 2.1.4
Operating system: Debian 8
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
When installing gitea I created a new admin user (name: master) via the web interface (:3000/install) and set a password containing an exclamation mark ("!"). The install page never redirected me to the main page, after a while I just opened the main page in another browser window and tried to log in. It always failed saying wrong username / password. I confirmed that the password was correct several times. I then changed install_lock to false, revisited /install and gave a password without special chars, this worked like a charm.
...
Screenshots

I had this issue, but even though it hung on the redirect, it still worked afterwards.

Sounds like we need more tests :trollface:

Yesterday I did an install of 1.1.1 and didn't use any special characters in the password (used something very similar to Password123) and didn't get redirected. When I navigated to the login page manually and try to log in I would get invalid username/password.
I looked into the database, and the user was actually not created, so as a workaround I created the user by command line of gitea-1.1.1-amd64...exe So it might not necessarily be the password?
The specs:
Gitea version (or commit ref): 1.1.1
Git version: git2.12.2.windows.2
Operating system: Windows 10
Database: MySQL

Specs:
Gitea version (or commit ref): 1.1.1
Git version: git2.12.2.windows.2
Operating system: Windows Server 2016 Standard
Database: MySQL
Did another install for reproducing another issue, and I've noticed that when you try to create a user called "admin" from the admin panel, it says "Username 'admin' is reserved." But this warning does not come up in the install page if you try to name the new user "admin". This should be the reason why I did not get the user created in my last post, because I named it admin.

Same here, tried to install 1.3.0 with postgres database backend on a separate db server, and create the admin user during the install with a special char in the password.
The redirect did not work and the user was not created. Creating the user as first user after refreshing the page worked.
It seems that the 'admin' name is with 1.3.0 also blocked when trying to register the first user. The 'admin' name did also not work during the setup process. Both ways a message appeared that the "Username 'admin' is reserved."


fix: insert missing forward-slash in instructions

inserted forward-slash in closing 'sup' tag in instructions section
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Hi @sjc5. Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝


bump next, react and use styled-jsx

Bump next to canary, react to 18 rc1
Change inline css to styled-jsx

📝 Changed routes:

/

(view full size)

Commit 0bf4eaeeac8091f6f07ae62bd5bdf4654b3554b7 (https://next-rsc-demo-1kbwj4vvr.vercel.sh).

global styled-jsx styles of main page are not matching between html and css 🤔
css: body.jsx-2e8c3a73a34d0f5c
html: <body style class="vsc-initialized">

Fixed


Convert student-finance-calculator to use ERB templates for questions

Looks good to me.

I've rebased this on master and force pushed in preparation for merging.


rcolonna/services check

Checks services that have binaries running outside of the normal locations

Chatted with rjcolonna and good with closing this out per opting to have it as a Yara rule instead


Better observability of performance and errors in Edge API

We had to remove Sentry from the Edge API stack in production, primarily because of the outage that they had shortly after we released it into the Edge API, but since then, we have also determined that it did noticeably increase the latency of the edge API for certain customers.
We could perhaps look into their relay product as a means to reduce latency / risks associated with their stability but we would need to consider how we would architect this for each of the Edge regions.
Initially, I think we should spend some time improving the monitoring / alerting in Cloudwatch to see if that would provide sufficient information.


shutdown refactor issues

there are issues that need to be fixed related to the shutdown refactor.

a stop method should be implemented that force-closes the socket to make sure it will not ne stuck in IO somewhere regardless if we are using select... for safety.

I would change the current close method to

def close
  @udp.close rescue nil
end

and add an identical stop method
def stop
  @udp.close rescue nil
end

note that with a proper stop the current close method is useless, unless we move the UDPSocket creation in the register method as proposed in #10 where we could have a situation where the plugin register method is called but not the run & stop and then only close, like in specs in which case both close and stop are required.

there is an error in the spec_helper.rb at https://github.com/logstash-plugins/logstash-input-udp/blob/12050767da47a63cf03b399847b8d38e7578765c/spec/spec_helper.rb#L17

plugin.stop should be rewritten as
plugin.do_stop
input_thread.join

otherwise the stop? method will never return true and there could be race conditions with the input thread.

good finding, I understand your points into moving the code into the register and good catch for the shared helpers.

+1 on on moving socket setup + ivar stuff into register.

+1 on the better close method but I don't understand the need to have stop close the socket. Every second select times out and we can check stop?
As to moving the code to register it will help make tests more deterministic, but otherwise improving the plugin itself (and there's tons to do) is out of scope for the shutdown refactoring, IMO

@jsvd I agree, we shouldn't need both. Even if we are programming defensively, IO.select should be enough, and if it's not, then something is reaaaaaly wrong with the system (major java/jruby/system bugs) and we can't save ourselves by closing a socket ;P

@colinsurprenant curious, why both IO.select and socket closing for interrupts?

@jsvd who is suggesting to «otherwise improving the plugin itself (and there's tons to do) » ?

@jordansissel because I have seen too many instances of select not working the way it was expected to work and adding a possible redundant stop to force close the socket is purely defensive, costs nothing to add and has zero risk.
also do not confuse stop and close purposes. In what I suggest it does make sense to have both IMO. but if we decide that we 100% trust select then, yes, stop is not required and we can cross fingers.

@colinsurprenant fair, though I think defensively programming against instabilities in the underlying platform really means we should fix the bugs in the underlying platform (jruby). I agree with you on the specific need for defensive programming against select() for now.

@colinsurprenant it's quite tempting to fix a lot of problems on this plugin, it's what I ended up doing in #10 so I guess I was trying to convince myself :D
I updated #10 to reflect your points.

@colinsurprenant having given the refactor a try, I ended up rewriting most of the plugin, for a few snowball reasons:

moving socket creation to register breaks the plugin behaviour of restarting itself so..
moving socket creation to a method that gets called in both register and during rescue implies changing the places where the @udp socket is closed/cleaned up/etc
that makes you realize that this plugin, upon restart, does not close the inputworker threads or ensure the @input_to_worker queue (by default holds up to 2000 events) is empty and overwrites it
(mind explodes).

The other possible route here is to keep it simple and dumb: implement stop/close as you said, but introduce a sleep in the spec suite to raise the odds of run binding the socket before the tests starts writing to it. thoughts?

Tried to reduce the scope of a pr to just fixing what's broken regarding the shutdown sequence. please review #12
I'll address the other concerns of #9 in another PR

Maybe we should close this issue and reopen a new one with what's missing? I am a bit lost on where we stand WRT #10 and #12


statusText returns NSString rather than Javascript string

Application code need to cast statusText explicitly into String for use in Javascript land. This can go unnoticed because log seems to cast everything into string. However JSON.stringify fails on NSString.
See: https://github.com/jasim/skpm_fetch_test/blob/master/src/my-command.js#L23
If you clone the repo and run it, you'll see {} where JSON.stringify is logged.
Casting to String() in https://github.com/skpm/sketch-polyfill-fetch/blob/master/lib/index.js#L25 should fix it

Ah yep, good catch 👍
Should be fixed in 0.4.6


gen-prost-serde: add missing pbjson-build options

Fixes #49
Literally my first time writing Rust code, so might be something obvious I've missed. Happy to fix any issues, if you point me in the right direction!

Sorry that I've been so far behind on these reviews. This looks great!
bors r+


Stop using old-style simd_shuffle

Found while fixing https://github.com/rust-lang/rust/issues/113500 (this PR is not necessary, but will allow us to make the compiler simpler)

Will be landing https://github.com/rust-lang/packed_simd/pull/352 first.

@oli-obk In the newly-introduced CI, the toolchain is pinned to a specific nightly. This PR should probably unpin it, unless there's some other inscrutable compiler error barring that. Note that I am happy to call this "passing" CI if we still have 26 successes and 7 failures on CI.

...hmm.

I swear I am going to set this repo on fire.

CI why are you like this.

Ah there we go.

Thank you! I will try to land some more CI fixes/PRs and then cut 3.9 soon!


upgrade to varcode 0.5.1 and necessary deps

Upgrading varcode and using varcode's union and intersection functions. This should pass on Travis once serializable==0.0.8 is released.

LGTM 💯

Coverage decreased (-0.1%) to 58.66% when pulling d843cab1d5260b9566f77d90dcd1096e6380ab85 on varcode-upgrade-merge into 5cc8be30970b88dd78e2c92b8d7bfcc5afda54ba on master.

Coverage decreased (-0.1%) to 58.66% when pulling d843cab1d5260b9566f77d90dcd1096e6380ab85 on varcode-upgrade-merge into 5cc8be30970b88dd78e2c92b8d7bfcc5afda54ba on master.


⚠ Bofrost.de has degraded performance

In d2a1ed6, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1108 ms

Resolved: Bofrost.de performance has improved in 3c1b63a after 43 minutes.


Fix Autocomplete Command Traversal

This PR fixes the autocomplete command traversal problem and replaces string arrays used in the command maps with IList to remove the unnecessary ToArray() method calls and give devs access to a variable sized container.

@quinchs sorry ive been busy this week and i couldnt thoroughly test this, i dont want to break anything in the live build. I just wanted to get this out there to inform people about whats in the pipeline rn.

appears to be running as intended.


Can't execute any of what's show on page 68-69 of your book

I updated the dependencies my project.clj file, ran lein deps.  I checked that it's in my ~/.m2/repository/ folder.
I tried requiring the project in the repl in multiple ways
(require '[com.backtype.def-datastores  :as dfs])
(require '[com.backtype.def-datastores.hadoop  :as hadoop])
(require '[com.backtype.def-datastores.hadoop.pail :as pail])
I keep getting this type of error:

Execution error (FileNotFoundException) at big-data.core/eval1560 (form-init14664829471889604774.clj:1).
Could not locate com/backtype/def_datastores__init.class, com/backtype/def_datastores.clj or com/backtype/def_datastores.cljc on classpath. Please check that namespaces with dashes use underscores in the Clojure file name.

What am I missing here?

correction that should read:
(require '[com.backtype.dfs-datastores :as dfs])


NonNullable isn't narrowing down object values' types for optional properties

TypeScript Version:  3.2.0-dev.20181106

Search Terms:
NonNullable object
NonNullable object values
Code
Run the following code via tsc --no-emit --strict test.ts:
interface P {
  color?: 'red' | 'green';
}

type RequiredP = {
  [K in keyof P]: NonNullable<P[K]>;
}

declare const p: RequiredP;
const color: 'red' | 'green' = p.color;

Expected behavior:
The resulting type should not allow undefined for the value at a property color.
Actual behavior:
undefined is still allowed. Using the NonNullable type doesn't seem to have any effect.
Playground Link: Note: you need to enable strictNullChecks manually!
https://www.typescriptlang.org/play/#src=interface P {
  color%3F%3A 'red' | 'green'%3B
}

type RequiredP %3D {
  [K in keyof P]%3A NonNullable<P[K]>%3B
}

declare const p%3A RequiredP%3B
const color%3A 'red' | 'green' %3D p.color%3B

Related Issues:

A workaround is to extract keyof P to a separate type first. It looks weird that it gives different result:
interface P {
  color?: 'red' | 'green';
}

type PKeys = keyof P;

type RequiredP = {
  [K in PKeys]: NonNullable<P[K]>;
}

declare const p: RequiredP;
const color: 'red' | 'green' = p.color;

https://www.typescriptlang.org/play/#src=interface P {
  color%3F%3A 'red' | 'green'%3B
}

type PKeys %3D keyof P%3B

type RequiredP %3D {
  [K in PKeys]%3A NonNullable<P[K]>%3B
}

declare const p%3A RequiredP%3B
const color%3A 'red' | 'green' %3D p.color%3B

The workaround from the previous comment doesn't work if the type is not known up front, e.g. in a function using generics. Example:
const makeRequired = <P extends {}>(props: P) => {
  type PKeys = keyof P;

  return props as {
    [Key in PKeys]: NonNullable<P[Key]>;
  };
};

interface Props {
  color?: 'red' | 'green';
}

declare const props: Props;

const enhancedProps = makeRequired(props);
const color: 'red' | 'green' = enhancedProps.color;

https://www.typescriptlang.org/play/#src=const makeRequired %3D <P extends {}>(props%3A P) %3D> {
  type PKeys %3D keyof P%3B

  return props as {
    [Key in PKeys]%3A NonNullable<P[Key]>%3B
  }%3B
}%3B

interface Props {
  color%3F%3A 'red' | 'green'%3B
}

declare const props%3A Props%3B

const enhancedProps %3D makeRequired(props)%3B
const color%3A 'red' | 'green' %3D enhancedProps.color%3B

using the syntax { key: type | undefined } instead of the optional property syntax using { key?: type } makes the construct work on typescript 3.5.1.

This is a pretty glaring issue; it's a rather basic piece of functionality that simply doesn't work.

@mgol I think this issue is just about the fact that your RequiredP is a homomorphic mapped type. This means that the optionality of the field is preserved in RequiredP If you use -? (added by this PR) you can remove the optional modifier explicitly and all will work as expected as far as I can tell:
interface P {
  color?: 'red' | 'green';
}

type RequiredP = {
  [K in keyof P]-?: NonNullable<P[K]>;
}

declare const p: RequiredP;
const color: 'red' | 'green' = p.color; // no error

play
Note: Mapped types are only homomorphic if they map over keyof T where T is any type or if they map over K where K is a type parameter extending keyof T. This is why your workarounds worked because they broke the pattern for homomorphic mapped types.

@dragomirtitian thanks very much for that incredibly informative comment.  I had never seen the -? syntax before, but that is definitely what's missing in this situation.  I've not encountered any docs for it before, but it does seem like a very niche/special-case feature built especially for this situation.
Thanks again for taking the time to explain that so well!

Here is the generic version:
type DeepNonNullable<T> = {
        [P in keyof T]-?: NonNullable<T[P]>;
}

There's already a type for this in lib.es5.d.ts:
/**
 * Make all properties in T required
 */
type Required<T> = {
    [P in keyof T]-?: T[P];
};

Not sure when it got added, but our long wait is over.

Required<T> allows the type null by default. It also allows the type undefined if you don't use questionmark on the filed (Look at the example 'var rb1 = ...'). So it does not provide the functionality we might expect from a NonNullable type. I think DeepNonNullable<T> implementation in the example below gives the expected results on object-and field-level;
Click for playground.
type DeepNonNullable<T> =
  { [P in keyof T]-?: NonNullable<T[P]>; } & NonNullable<T>
//wiht '?'
interface A {
  color?: 'red' | 'green' | undefined | null;
}
//wihtout '?'
interface B {
  color: 'red' | 'green' | undefined | null;
}
//wiht '?'
interface C {
  color?: DeepNonNullable<'red' | 'green' | undefined | null>
}
//wihtout '?'
interface D {
  color: DeepNonNullable<'red' | 'green' | undefined | null>
}
//wiht '?'
interface E {
  color?: NonNullable<'red' | 'green' | undefined | null>
}

//wihtout '?'
interface F {
  color: NonNullable<'red' | 'green' | undefined | null>
}

//wiht '?'
interface G {
  color?: Required<'red' | 'green' | undefined | null>
}

//wihtout '?'
interface H {
  color: Required<'red' | 'green' | undefined | null>
}

// first letter: type indicator
// d: object deepnonnullable
// r: object level required
//_d: field level deepnonnullable
//_n: field level nonnullable
//_r: field level required

// q: (as second letter) field wiht questionmark ({color?:...})

var dq0: DeepNonNullable<A> = { color: 'green' }  //OK
var dq2: DeepNonNullable<A> = { color: null }     //Type 'null' is not assignable
var dq1: DeepNonNullable<A> = { color: undefined }//Type 'undefined' is not assignable

var d0: DeepNonNullable<B> = { color: 'green' }  //OK
var d2: DeepNonNullable<B> = { color: null }     //Type 'null' is not assignable
var d1: DeepNonNullable<B> = { color: undefined }//Type 'undefined' is not assignable

var rq0: Required<A> = { color: 'green' }  //OK
var rq2: Required<A> = { color: null }     //OK
var rq1: Required<A> = { color: undefined }//Type 'undefined' is not assignable

var r0: Required<B> = { color: 'green' }  //OK
var r2: Required<B> = { color: null }     //OK
var r1: Required<B> = { color: undefined }//OK

var _dq0: C = { color: 'green' }           //OK
var _dq2: C = { color: null }              //Type 'null' is not assignable
var _dq1: C = { color: undefined }         //OK

var _d0: D = { color: 'green' }           //OK
var _d2: D = { color: null }              //Type 'null' is not assignable
var _d1: D = { color: undefined }         //Type 'undefined' is not assignable

var _nq0: E = { color: 'green' }           //OK
var _nq2: E = { color: null }              //Type 'null' is not assignable
var _nq1: E = { color: undefined }         //OK

var _n0: F = { color: 'green' }           //OK
var _n2: F = { color: null }              //Type 'null' is not assignable
var _n1: F = { color: undefined }         //Type 'undefined' is not assignable

var _rq0: G = { color: 'green' }           //OK
var _rq2: G = { color: null }              //OK
var _rq1: G = { color: undefined }         //OK

var _r0: H = { color: 'green' }           //OK
var _r2: H = { color: null }              //OK
var _r1: H = { color: undefined }         //OK

You can use required-properties package for this.
import { assertRequiredProperties } from "required-properties";

interface P {
  color: "red" | "green" | undefined;
  stillCanBeNullable: number | undefined | null;
}

declare const p: P;

assertRequiredProperties(p, ["color"]); // full autocomplete here

const color: "red" | "green" = p.color; // no error - color is required ✅

Benefits: 💡

You can select which properties are required (not all of them)
This package throws error at runtime if property is nullable
No need to declare new type - type of p gets infered automatically

Ts playground here
Note this doesn't work with optional property in your description. However you can solve it by defining it as  | undefined

Here is the generic version:
type DeepNonNullable<T> = {
  [P in keyof T]-?: NonNullable<T[P]>;
}

Here is a type guard version.
export const hasNoDeepNullable = <T extends Record<string, unknown>>(
  obj: T,
): obj is DeepNonNullable<typeof obj> => {
  for (const key of Object.keys(obj)) {
    if (obj[key] === null) return false;
  }
  return true;
};

If all of the nullable values exist, it simply applies the DeepNonNullable<> type to the object.


Cant install facebook-business or one of its dependencies

When doing
pip3 install facebook-business or facebook_business it errors at either installing the main package or one of its dependencies.
Collecting facebook-business==9.0.1   Downloading https://files.pythonhosted.org/packages/d4/87/8848716e1c5379547a57698c2625b41d9f1c41515eb639ae5c53a2efb3d6/facebook_business-9.0.1-py3-none-any.whl (1.0MB)     100% |████████████████████████████████| 1.0MB 1.2MB/s THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.     facebook-business==9.0.1 from https://files.pythonhosted.org/packages/d4/87/8848716e1c5379547a57698c2625b41d9f1c41515eb639ae5c53a2efb3d6/facebook_business-9.0.1-py3-none-any.whl#sha256=854e79cf8812cff403ff52d037b38e52d0381d316282de913cd2594f0d6ae12f:         Expected sha256 854e79cf8812cff403ff52d037b38e52d0381d316282de913cd2594f0d6ae12f              Got        751b1b2971b4dae84acc10a54bdbc05292c6f9f20b457985152e86583e8ff752
If I do:
curl -O https://files.pythonhosted.org/packages/d4/87/8848716e1c5379547a57698c2625b41d9f1c41515eb639ae5c53a2efb3d6/facebook_business-9.0.1-py3-none-any.whl
Then check that myself:
sha256sum facebook_business-9.0.1-py3-none-any.whl
854e79cf8812cff403ff52d037b38e52d0381d316282de913cd2594f0d6ae12f  facebook_business-9.0.1-py3-none-any.whl
I get the correct hash.
Here's the other failed hash:
ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.      pycountry>=19.8.18 from https://files.pythonhosted.org/packages/76/73/6f1a412f14f68c273feea29a6ea9b9f1e268177d32e0e69ad6790d306312/pycountry-20.7.3.tar.gz#sha256=81084a53d3454344c0292deebc20fcd0a1488c136d4900312cbd465cf552cb42 (from facebook_business):          Expected sha256 81084a53d3454344c0292deebc20fcd0a1488c136d4900312cbd465cf552cb42               Got        85a0ddbb7a5f883c92ef75583c7809d881ab36af6c40a0ed1595ae0cf02d279d
However with this, when I download the file and check the hash, I get a different value again:
curl -O https://files.pythonhosted.org/packages/76/73/6f1a412f14f68c273feea29a6ea9b9f1e268177d32e0e69ad6790d306312/pycountry-20.7.3.tar.gz
sha256sum pycountry-20.7.3.tar.gz
bc4881215c274fbc66a3748f4dc42a9c0a86be277a990149bb6b0b0346f4284d  pycountry-20.7.3.tar.gz

I just had same issue with boto3:
 ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.     botocore<1.20.0,>=1.19.39 from https://files.pythonhosted.org/packages/88/7a/44a3411ff1b4814210197e314ab5b63e7313fc01886bbb9f04b953cfccef/botocore-1.19.39-py2.py3-none-any.whl#sha256=449e4196160ff58ee27d2a626a7ce4cfff2640fe1806d7a279e73a30ad286347 (from boto3):         Expected sha256 449e4196160ff58ee27d2a626a7ce4cfff2640fe1806d7a279e73a30ad286347              Got        32dd307859f4fdd6e03d6b215ab00328e7c2786cdaf1e9864e8699eff9b61a56
When I download this and check myself, it matches.

Hello @datacubed, this repo is for the code behind pypi.org, your issue is related to pip, please open an issue there.


(#143) add endpoint for GetPost in ntrada async files

Let's see the effect of the Deploy to Cloud


feat(feature-card): enable color scheme selection

Related Ticket(s)
Closes #10306
Closes #10072
Closes #10073
Description
This PR scopes the current feature card styles under the inverse color scheme attribute and inherits the regular color scheme styles from the card component
note: currently testing with border-subtle-selected token due to the desired border-tile token being behind an upstream feature flag
Changelog
New

color scheme story knob

Changed

scoped v1 styles to color-scheme="inverse"

Hey @emyarod , still going through it but picked up a few things:

When feature card is using the inverse color-scheme, the icon should use $inverse-link. This applies to both sizes.

Noticed that feature card medium is flush with the column in WC, but in the specs they should extend halfway into the gutter. Is this just a Storybook issue, or is this baked into the component?

Current build:

Design specs:

For feature card large, the background token is set to $ui-background, but for v1 the token should be $ui-01 and in v2 should be $layer-01

For focus state, both size variants seem to be off in different ways. They should use the following: 2px $focus inside border, with a 1px $focus-inset border

Large (focus border is on the outside, and doesn't seem to have focus inset border)

Medium (has focus and focus inset border, but should replace tile border that's still showing in the build)

@RichKummer I believe I got everything! for the storybook grid overhang, you may have been looking at an older deploy preview since it was building/rebuilding a lot while I was making changes earlier. it should look like this now:

@emyarod Just took a quick look and it seems like the issues from my last comment are still showing. The commit messages seem to be addressing these but the preview's the same

it looks like there is now a regression where the focus state will hide the image... need to look more into this

@emyarod seeing the image come in fine 🎉 . A few other things:
Global

The Focus state seems to be resolved except there's an odd issue where focusing shifts the content around slightly (it's around a 1-2px shift). Seeing in both Medium and Large.

https://github.com/carbon-design-system/carbon-for-ibm-dotcom/assets/15643582/237e2e0d-19fd-47b6-859e-2b089f904678

When switching to the @sm breakpoint, the icon floats towards the middle of the card vertically – it should be appended to the bottom right. Seeing in both sizes.

Large

The side padding for the content card should be 32px when @xlg, right now it's 16px.

It looks like @md that the type token for the body copy isn't changing. For every breakpoint except @md, the body copy token should be $body-02 (@max – @lg, https://github.com/sm). For @md only, the token should be $body-01, but looks like it's coming in as $body-02.

Also @md, the component should maintain a 2:1 aspect ratio – right now the height goes a bit beyond that. I am seeing the truncation though!

Similarly for the heading token:, the type token should be $heading-04 from @max through @lg, then $heading-03 for @md and @sm. Currently not seeing a change at smaller breakpoints.

I'm still investigating the aspect ratio problem but these should be addressed:

the focus borders should no longer affect the content
the icons should be appended to the bottom right now
for the content, is there any guidance on what to put in the examples or is it ok if I just double the amount of lorem ipsum?
the content padding for large feature cards at @xlg breakpoints should be 32px now
the background-color for large feature cards should already be $layer-01 (https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/10744/files#diff-519d54bfe0dcb5b5a2ffe6549529b1257bd937add3e07ba3c0e90b9bc2f92904R270) is the value of the token not showing correctly?
the card copy should already be using body-01 at @md only (https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/10744/files#diff-519d54bfe0dcb5b5a2ffe6549529b1257bd937add3e07ba3c0e90b9bc2f92904R388-R389)

@emyarod checked through the last few bullets and almost everything looks great ✨
I know we're still talking about the aspect ratio/truncation, but when I looked at @md I wasn't seeing the body copy token update? Inspect is showing it at 1 rem across breakpoints. Visually, it doesn't look like the type size changes there.

@emyarod this looks so good! Focus and padding are solved. Some small details:

[ ] For large variant only, the icon seems to have a bit of extra space at the bottom:

[ ] For the large variant, I had the wrong info for the heading above. For the @lg breakpoint, the heading should be heading-03, the same as @md and @sm. That's my bad for mixing up the feedback!

[ ] For the body copy in the Storybook for feature card - large could you change it to something shorter. I clipped an example that meets the recommended character count here: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam.

@RichKummer everything should be good to go now!

@emyarod, this looks great! A few details and this should be set:
Large

[ ] The inverse color scheme has a hover on the card background, but the regular color scheme doesn't seem to change the background. The background type token should update to layer-01-hover. The image does darken correctly though.
[ ] At the bottom of the image container, there seems to be a few pixels of space between the container and the bottom. It may be the asset, though?

[ ] Messaged you about the body copy issue - crashing if I edit in Storybook. I'm not sure if this is a Storybook issue, though.

@RichKummer I believe everything is resolved now!


like counter im header must be visible how many likes left

i think this issue is currently not needed anymore, because we got a timer and like reset


Support for validation directives

Hi, just submitting for your consideration to add first class support fo https://github.com/graphql-java/graphql-java-extended-validation. I feel like it’s better to use the schema as much as possible for documentation.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Layout broken with Bootstrap v4 flexbox support enabled

I think its because of all the nested custom elements, e.g. <formly-field> etc

Try the demo with this as the CSS source:
https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0-alpha.5/css/bootstrap-flex.min.css

This might help, but perhaps there is a better way of fixing this...
http://codepen.io/anon/pen/JRgBZX
Using <template> to output the components directly to the DOM without the additional elements?

If you use flexbox, the column class element should be direct child of row class element.


March 7, 2022 Community Meeting

Please add a topic in this thread and add a link to the GitHub issue associated with the topic.
Please make sure you give folks enough time to review/discuss the topic offline on GitHub before coming into the meeting
(optional) Paste the image of an animal :smile_cat:

Validating Admission Webhook for Shipwright objects: https://github.com/shipwright-io/build/issues/596

My proposal for the next releases:

v0.9 "Easter release" in the week April 4th - 8th: we should be able to get some nice features wrapped up for the ships that were recently merged (buildrun cleanup, standalone buildrun)
v0.10 "cdCon release" end of May in the week May 23rd to 27th.

🐻

SHIPs that require a second approval from RedHat to get merged:

SHIP-0026: Introduce shipwright-managed push #53
SHIP-0027: Image Abstraction Layer #57

🐹

/close


New DP04 no wifi password

The new DP04 Pure Cool Purifying Fan doesn't have a wifi password (also confirmed with Dyson support).  It does have an eight digit (1234:5678) "access" number to add the device to the Dyson Link app manually if the linking process doesn't work.  Any thoughts on how to get it working with this homebridge plugin?

Same issue as I am having here: https://github.com/joe-ng/homebridge-dyson-link/issues/28
Hope we can figure out a solution. I also just found the eight digit access number within the filter housing on the device but that doesn't work as a password in the homebridge plugin unfortunately.

sorry, i don't have that device and am not sure how that works currently.
will need to spend some time to look into that

Well I’m not super technical, but if you provide instructions I can try stuff for you, etc. if it helps.
Eugene
On Apr 22, 2018, 7:47 AM -0400, joe-ng<EMAIL_ADDRESS>wrote:

sorry, i don't have that device and am not sure how that works currently.
will need to spend some time to look into that
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Same here, I have the new TP04 (Dyson Pure Cool Link Purifier).
Looking at the code, it looks like an initial problem is that you're verifying the format of the serial number with a regular expression, but my SN doesn't look like this DYSON-XXX-XX-XXXXXXXX-XXX its XXX-XX-XXXXXXXX
https://github.com/joe-ng/homebridge-dyson-link/blob/master/DysonLinkDevice.js#L19

I had this same issue, and after a couple changes to the code I was able to get the fan to connect properly.
Dyson made a few changes in the format of the messages, but those were pretty straightforward to adjust. E.g. The property "fmod" (mode) which had "AUTO" / "FAN" / "HEAT" options was replaced by "fpwr": "ON" / "OFF" and "auto": "ON"/ "OFF".
The trickier problem was getting the right credentials without the built-in wifi pass like the old models. I found a solution by looking into this python library (libpurecoollink) which allows users to login with their Dyson account to get the appropriate password for communicating with the fan.
I've got mine setup by storing the password hash from that program, but I can add in that functionality with the other necessary changes for supporting the TP04 model and submit a pull request.
If anyone wants to see an example of the messages from the TP04, I've added a few here.

#32 Pull request added!

Thanks a lot!
I just released v2.0 for this

Man, that was quick. Awesome! Thanks. Installed this morning. Set up config with my username/password, IP address, and serial. When restarting homebridge, the fan shows up as an occupancy sensor with the platform name. And when I manually turn on the fan, it doesn’t trip the occupancy sensor (thought maybe it would trigger if the fan was actively being used). Thoughts?

It works great for me with my TP04. Thank you so much, even Siri fully understands how to use the fan!

Wouldn’t see what/why, but wonder if it’s something different about the DP04.

Nevermind. My config was messed up. Got all sorts of Dyson options. Of course now all homebridge accessories give “no response”. Haha.

FYI the model for the DP04 is 520 instead of 438 (which I guess is the TP04).


MAINT: incorporate fix for AIX shared library support

xref https://github.com/numpy/numpy/issues/25244

Merging straight away so we can update the git submodule in the main numpy repo.


malloc$of$allocated$write.js:8-10: Implement...

The puzzle 3-1936dd25 from #3 has to be resolved:
https://github.com/objectionary/eo2js/blob/05f2c31c54ef4fff7087c74e6774a74ccefb1687/eo2js-runtime/src/objects/org/eolang/malloc$of$allocated$write.js#L8-L10
The puzzle was created by maxonfjvipon on 22-May-24.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 3-1936dd25 has disappeared from the source code, that's why I closed this issue.


Update mediaquery-text for node v6.

Coverage remained the same at 95.652% when pulling 23ecafe342f0c1c6564ced36b87f137d1e46b452 on fix-mediaquery-text into 9f04c590d4e5058dcb62949c433ed303b88a6026 on master.


Package Registration at Julia General Registry

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/98011
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 52b185f6a0e26c4f71a02aec4a938d95126bc709
git push origin v0.1.0


Deployment guide feedback

Section heading: Deployment steps
Documentation issue description:
The statement of "Deployment takes about 2 hours to complete" feels out of place. Maybe more suited to step 7
Also, as relocate is "no" by default, change the statement to 1 hour (or add a note of 1 hours without relocate and two with)

The statement of "Deployment takes about 2 hours to complete" feels out of place. Maybe more suited to step 7

@spagno, this is part of the boilerplate documentation template used in all Quick Start documentation, so changing this would require changing the documentation for all Quick Starts (once the submodule is bumped in each). If you still want to proceed, submit a PR to update https://github.com/aws-ia/aws-ia-documentation-base-common/blob/main/deployment_steps_cfn.adoc and then tag @DelfinGala in the comments.

Also, as relocate is "no" by default, change the statement to 1 hour (or add a note of 1 hours without relocate and two with)

Agreed. @aaronmeza and/or @satya-dillikar: do you approve?
@spagno: if either approves, this documentation variable is located here: https://github.com/aws-quickstart/quickstart-vmware-tanzu-application-platform/blob/doc-edits/docs/deployment_guide/partner_editable/_settings.adoc#L15. To update it, submit a PR to the doc-edits branch. Once either approve, then tag @DelfinGala to deploy. If you run into any issues, tag me. Alternatively, ask Satya for my contact info to reach out directly.

I approve.


improved docstring of to_netcdf (issue #7127)

[x] Closes #7127: docstring of to_netdcf()

Sorry for the delay here @vallirep . Thanks for the update!