MigPlan stuck at Step 5 'Results':  Not handling  'the object has been modified; please apply your changes to the latest version and try again"'

I used the wizard and stepped through creating a migplan for 'robot-shop' and was stuck at waiting for for MigPlan to become ready.
Note, below is after I completed MigPlan wizard, I so I stepped through the wizard and left the choices as default value of copy but looks like ui hit a '409', UI attempted 3 times.
From ui console
PUT https://api.cluster-jwm0820ocp4a.jwm0820ocp4a.mg.dog8code.com:6443/apis/mig…on.openshift.io/v1alpha1/namespaces/openshift-migration/migplans/robot1133 409
Request
 {"apiVersion":"migration.openshift.io/v1alpha1","kind":"MigPlan","metadata":{"annotations":{"touch":"e8b3abef-b1cf-4632-a0d9-22c3c53fbc99"},"creationTimestamp":"2019-08-24T15:33:41Z","finalizers":["openshift.io/migration"],"generation":10,"name":"robot1133","namespace":"openshift-migration","resourceVersion":"1434536","selfLink":"/apis/migration.openshift.io/v1alpha1/namespaces/openshift-migration/migplans/robot1133","uid":"8cea03b1-c684-11e9-be0b-064b99644b87"},"spec":{"destMigClusterRef":{"name":"host","namespace":"openshift-migration"},"migStorageRef":{"name":"jwmminio","namespace":"openshift-migration"},"namespaces":["robot-shop"],"persistentVolumes":[{"capacity":"10Gi","name":"vol123","pvc":{"accessModes":["ReadWriteOnce"],"name":"mysql-scripts-volume-claim","namespace":"robot-shop"},"selection":{"storageClass":"gp2","action":"copy"},"supported":{"actions":["copy","move"]}},{"capacity":"10Gi","name":"vol55","pvc":{"accessModes":["ReadWriteOnce"],"name":"mongodb-volume-claim","namespace":"robot-shop"},"selection":{"storageClass":"gp2","action":"copy"},"supported":{"actions":["copy","move"]}},{"capacity":"10Gi","name":"vol71","pvc":{"accessModes":["ReadWriteOnce"],"name":"redis-volume-claim","namespace":"robot-shop"},"selection":{"storageClass":"gp2","action":"copy"},"supported":{"actions":["copy","move"]}},{"capacity":"10Gi","name":"vol9","pvc":{"accessModes":["ReadWriteOnce"],"name":"mysql-data-volume-claim","namespace":"robot-shop"},"selection":{"storageClass":"gp2","action":"copy"},"supported":{"actions":["copy","move"]}}],"srcMigClusterRef":{"name":"ocp3","namespace":"openshift-migration"}}}

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "Operation cannot be fulfilled on migplans.migration.openshift.io \"robot1133\": the object has been modified; please apply your changes to the latest version and try again",
  "reason": "Conflict",
  "details": {
    "name": "robot1133",
    "group": "migration.openshift.io",
    "kind": "migplans"
  },
  "code": 409
}

$ oc get migplan robot1133 -n openshift-migration -o yaml
apiVersion: migration.openshift.io/v1alpha1
kind: MigPlan
metadata:
  annotations:
    touch: 990c91f8-852e-4044-a2e8-8c1518913fcc
  creationTimestamp: "2019-08-24T15:33:41Z"
  finalizers:
  - openshift.io/migration
  generation: 15
  name: robot1133
  namespace: openshift-migration
  resourceVersion: "1434656"
  selfLink: /apis/migration.openshift.io/v1alpha1/namespaces/openshift-migration/migplans/robot1133
  uid: 8cea03b1-c684-11e9-be0b-064b99644b87
spec:
  destMigClusterRef:
    name: host
    namespace: openshift-migration
  migStorageRef:
    name: jwmminio
    namespace: openshift-migration
  namespaces:
  - robot-shop
  persistentVolumes:
  - capacity: 10Gi
    name: vol123
    pvc:
      accessModes:
      - ReadWriteOnce
      name: mysql-scripts-volume-claim
      namespace: robot-shop
    selection:
      storageClass: gp2
    supported:
      actions:
      - copy
      - move
  - capacity: 10Gi
    name: vol55
    pvc:
      accessModes:
      - ReadWriteOnce
      name: mongodb-volume-claim
      namespace: robot-shop
    selection:
      storageClass: gp2
    supported:
      actions:
      - copy
      - move
  - capacity: 10Gi
    name: vol71
    pvc:
      accessModes:
      - ReadWriteOnce
      name: redis-volume-claim
      namespace: robot-shop
    selection:
      storageClass: gp2
    supported:
      actions:
      - copy
      - move
  - capacity: 10Gi
    name: vol9
    pvc:
      accessModes:
      - ReadWriteOnce
      name: mysql-data-volume-claim
      namespace: robot-shop
    selection:
      storageClass: gp2
    supported:
      actions:
      - copy
      - move
  srcMigClusterRef:
    name: ocp3
    namespace: openshift-migration
status:
  conditions:
  - category: Required
    lastTransitionTime: "2019-08-24T15:33:41Z"
    message: The `persistentVolumes` list has been updated with discovered PVs.
    reason: Done
    status: "True"
    type: PvsDiscovered
  - category: Error
    lastTransitionTime: "2019-08-24T15:34:17Z"
    message: PV in `persistentVolumes` [vol123,vol55,vol71,vol9] has an unsupported
      `action`.
    reason: NotDone
    status: "True"
    type: PvInvalidAction
  - category: Required
    lastTransitionTime: "2019-08-24T15:33:42Z"
    message: The storage resources have been created.
    status: "True"
    type: StorageEnsured
  - category: Required
    lastTransitionTime: "2019-08-24T15:33:42Z"
    message: The migration registry resources have been created.
    status: "True"
    type: RegistriesEnsured

Deleted prior MigPlan, reloaded UI and recreated and MigPlan was created successfully
$ oc get migplan robot1145 -n openshift-migration -o yaml
apiVersion: migration.openshift.io/v1alpha1
kind: MigPlan
metadata:
  annotations:
    touch: f17dee40-b3f2-4d93-b93b-58522e2232ed
  creationTimestamp: "2019-08-24T15:46:05Z"
  finalizers:
  - openshift.io/migration
  generation: 11
  name: robot1145
  namespace: openshift-migration
  resourceVersion: "1437712"
  selfLink: /apis/migration.openshift.io/v1alpha1/namespaces/openshift-migration/migplans/robot1145
  uid: 4829b029-c686-11e9-be0b-064b99644b87
spec:
  destMigClusterRef:
    name: host
    namespace: openshift-migration
  migStorageRef:
    name: jwmminio
    namespace: openshift-migration
  namespaces:
  - robot-shop
  persistentVolumes:
  - capacity: 10Gi
    name: vol123
    pvc:
      accessModes:
      - ReadWriteOnce
      name: mysql-scripts-volume-claim
      namespace: robot-shop
    selection:
      action: copy
      storageClass: gp2
    supported:
      actions:
      - copy
      - move
  - capacity: 10Gi
    name: vol55
    pvc:
      accessModes:
      - ReadWriteOnce
      name: mongodb-volume-claim
      namespace: robot-shop
    selection:
      action: copy
      storageClass: gp2
    supported:
      actions:
      - copy
      - move
  - capacity: 10Gi
    name: vol71
    pvc:
      accessModes:
      - ReadWriteOnce
      name: redis-volume-claim
      namespace: robot-shop
    selection:
      action: copy
      storageClass: gp2
    supported:
      actions:
      - copy
      - move
  - capacity: 10Gi
    name: vol9
    pvc:
      accessModes:
      - ReadWriteOnce
      name: mysql-data-volume-claim
      namespace: robot-shop
    selection:
      action: copy
      storageClass: gp2
    supported:
      actions:
      - copy
      - move
  srcMigClusterRef:
    name: ocp3
    namespace: openshift-migration
status:
  conditions:
  - category: Required
    lastTransitionTime: "2019-08-24T15:46:16Z"
    message: The `persistentVolumes` list has been updated with discovered PVs.
    reason: Done
    status: "True"
    type: PvsDiscovered
  - category: Required
    lastTransitionTime: "2019-08-24T15:46:16Z"
    message: The storage resources have been created.
    status: "True"
    type: StorageEnsured
  - category: Required
    lastTransitionTime: "2019-08-24T15:46:16Z"
    message: The migration registry resources have been created.
    status: "True"
    type: RegistriesEnsured
  - category: Required
    lastTransitionTime: "2019-08-24T15:46:16Z"
    message: The migration plan is ready.
    status: "True"
    type: Ready


Waiting For The Android 10 Ver....

Since Weeb Gapps ended its support, Android 10 users CANNOT get a Magisk Gapps module which support Shamiko...

Please use MagiskGApps.com or the readme for more infomation. The MG Maker repo has merged with the main, so you can create your own MG file.


Eliminate or replace all Repo.all calls in controllers

We have a lot of places where we call Repo.all without thinking twice about the consequences.
We should start cleaning up all instances of these or replacing them with pagination or something that doesn't fetch every single record from the database.
Please make a separate issue for the one you're trying to remove or replace.

While we will want pagination on a lot of things, I should emphasize that Repo.all isn't the same as Model.all in Rails. It's actually more like Model.where, so it's not a big deal if we use it. We might continue to use it even with pagination added.

I believe Repo.all hits the database. You can think of it is Repo.execute_and_fetch_results


changes to hub-spoke and add sss

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference-architectures/hybrid-networking/hub-spoke.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/shared-securiity-stack.md
:white_check_mark:Succeeded
View

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.

@telmosampaio Since this is a change to a different content set than ACAG, consider using a separate branch, so we can review / publish it independently?

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference-architectures/hybrid-networking/hub-spoke.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/images/hub-spoke.png
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/images/shared-services.png
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/shared-services.md
:white_check_mark:Succeeded
View

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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference-architectures/hybrid-networking/hub-spoke.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/images/hub-spoke.png
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/images/shared-services.png
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/shared-services.md
:white_check_mark:Succeeded
View

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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference-architectures/hybrid-networking/hub-spoke.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/images/hub-spoke.png
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/images/shared-services.png
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/shared-services.md
:white_check_mark:Succeeded
View

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.

This PR was substituted by https://github.com/mspnp/architecture-center/pull/437


CreateFile with the right flags

We need FILE_SHARE_READ | FILE_SHARE_WRITE on both calls to CreateFile, so that we can properly watch the file for reloads.
Without these, when the file reloaded, we'd fail to open the file, think that it's because the file doesn't exist, create the default settings, and then we'd blow away the user's settings.
Fixes #1325

@msftbot merge this PR as soon as possible

@msftbot merge this pr in 1 minute

good bot


How to run kala permanantly in terminal

Here is an example systemd file: https://github.com/ajvb/kala/tree/master/deployment/systemd


Fix translation files

Fixed English referencing in translation files for Bitcoin, PayCoin and
Peercoin

Is there anything wrong with merging this PR? Changes are hopefully pretty self explanatory but any questions let me know.
If this can be merged I have further changes moving forward with translations and will be looking to assist the community by running a Transifex account with multiple translations and over time adding further languages and 100% complete translations. Just something I can do to help out more while letting the actual developers develop and not have to worry about this side of things. I have working local branches already :)

Looks like a good pull. If a dev agrees we will merge this.

All existing code references "Paycoin" rather than "PayCoin" (see bitcoinrpc.cpp for example) for consistency sake I'd say that's probably more appropriate. I've never really gotten the right info regarding trademark. @mgrav or @PaycoinMaster would know better on that one.
Furthermore the copyright data should be the current Paycoin copyright (2014-2015) rather than the old Peercoin copyright (as far as that particular message is concerned, obviously having all the copyrights in the comments at the top of the files is still preferred).
The code itself looks fine, I'd want to compile it just for giggles before merging though.

Thanks @IngCr3at1on
I was unsure myself so I went with "PayCoin" because at the end of the day it was a 50/50 guess. I asked the question on talk.paycoin.com and no one knew and even the paycoin.com website uses both formats throughout the website and also the emails they send. If we could get some consensus on this it would be nice. In the meantime, I will change to "Paycoin".
Sorry can you expand on the copyright. I am changing the about dialog box in the qt to stop showing:
Copyright © 2014 Paycoin Developers
Copyright © 2011-2014 Paycoin Developers
Copyright © 2009-2014 Bitcoin Developers
and instead show
Copyright © 2014 Paycoin Developers
Copyright © 2011-2014 Peercoin Developers
Copyright © 2009-2014 Bitcoin Developers
I wasn't focusing on the copyright years at the moment just that we referenced Paycoin twice (because someone had just done a Find/Replace for Peercoin to Paycoin).
Let me know what you think and I will make whatever necessary changes.

Yeah I mean if we want to change it to PayCoin personally I'm indifferent (definitely not something I would do on my own lol) but it needs to be changed everywhere.
In regards to the about dialog that's my mistake from reading just the commit and not the surrounding lines so that should be great.

We need to leave it as Paycoin please.  PayCoin (with the capital C) is trademarked by an outside organization.  Thank you!  :-)

@IngCr3at1on @xmk3 Thanks guys. Will make the necessary changes now

@IngCr3at1on @xmk3 Thanks guys, this is now done.

Looks good to me, I approve.

Thanks @BoXHocK. I actually did notice this but was going to let it get swept up in the actual translating of the English version but I see what you're saying, I may as well fix it now. Will get it done right now.

@BoXHocK @IngCr3at1on All done.

works for me, as I said I approve :D
@evanlucas @PaycoinMaster


fix: add addr validation

Description:
Add address validation checks on main code where we are using Addr::unchecked or not performing addr validation.
Commit Message
fix: add addr validation

see the guidelines for commit messages.
Changelog Entry
0.1.0 : Add address validation

Checklist:

[x] I have performed a self-review of my own code
[x] I have documented my code in accordance with the documentation guidelines
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have run the unit tests
[x] I only have one commit (if not, squash them into one commit).
[x] I have a descriptive commit message that adheres to the commit message guidelines

Please review the CONTRIBUTING.md file for detailed contributing guidelines.

Codecov Report

Merging #635 (5b4d4ec) into main (7da1f7b) will increase coverage by 0.04%.
Report is 1 commits behind head on main.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #635      +/-   ##
============================================
+ Coverage     69.02%   69.07%   +0.04%
  Complexity      408      408
============================================
  Files           151      151
  Lines         14016    14016
  Branches        294      294
============================================
+ Hits           9675     9681       +6
+ Misses         4185     4179       -6
  Partials        156      156

Flag
Coverage Δ

rust
67.22% <100.00%> (+0.04%)
:arrow_up:

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

Files Changed
Coverage Δ

...c-core/src/ics04_channel/packet/acknowledgement.rs
84.27% <100.00%> (ø)

...bc-core/src/ics04_channel/packet/receive_packet.rs
81.00% <100.00%> (ø)

...vm/cw-ibc-core/src/ics04_channel/packet/timeout.rs
79.20% <100.00%> (ø)

... and 1 file with indirect coverage changes


Module parse failed. Unexpected token

I'm building an app with react-native and react-native-web (to reuse react native component on web). But i got this problem when building
Uncaught Error: Module parse failed: Unexpected token (8:75)
You may need an appropriate loader to handle this file type.
| class Row extends Component {
|   render() {
|     const {data, style, widthArr, height, flexArr, textStyle, borderStyle, ...props} = this.props;
|     let widthNum = 0;
|     if (widthArr) {

"react-native": "0.51.0"
"react": "^16.3.2",
"react-art": "^16.3.2",
"react-dom": "^16.3.2",
"react-native-web": "^0.8.4",
"react-native-table-component": "^1.1.8",
If you need more detail, please let me know. Thanks.

The mistake has told you that the eighth lines have grammatical errors

yeah, this line, but can not find out
const {data, style, widthArr, height, flexArr, textStyle, borderStyle, ...props} = this.props;

never mind, i solved the problem. Close here.


No module named 'apiclient.discovery'

Traceback (most recent call last):
File "c:\Users\Cliente\Desktop\FINAL\YouTube-shorts-generator-main\YouTube-shorts-generator-main\main.py", lin
e 6, in
import upload
File "c:\Users\Cliente\Desktop\FINAL\YouTube-shorts-generator-main\YouTube-shorts-generator-main\upload.py", l
ine 4, in
from apiclient.discovery import build
ModuleNotFoundError: No module named 'apiclient.discovery'
I have apiclient installed

Try pip install --force-reinstall -v "apiclient==1.0.4". This should force reinstall apiclient to version 1.0.4.

pip install --upgrade google-api-python-client is fixed for me.


Replace websockets library with aiohttp library - Okex

See epic https://github.com/CoinAlpha/hummingbot/issues/3941 for the rationale of this task.
Definition of Done

[ ] Replace websockets library with aiohttp in Okex connector
[ ] Connector should be working without issues after the change

┆Issue is synchronized with this Clickup task by Unito

Closing this one since okx connector was updated here:
https://github.com/hummingbot/hummingbot/pull/5368
and original issue is not available on https://github.com/CoinAlpha/hummingbot/issues


Possible Typo in Documentation

Hi Pim,
In the documentation about Falco. Markup, https://www.falcoframework.com/docs/markup.html, I found a possible typo. In this code example (HTML ⇒ Merging Attributes):
// Template
let master (title : string) (content : XmlNode list) =
    Elem.html [ Attr.lang "en" ] [
        Elem.head [] [
            Elem.title [] [ Text.raw "Sample App" ]
        ]
        Elem.body [] content
    ]

[ Text.raw "Sample App" ] should probably be [ Text.raw title ].

Hey! Thanks for spotting this! Will correct!
On Sun., Oct. 2, 2022, 1:14 a.m. Stefan Rohlfing, @.***>
wrote:

Hi Pim,
In the documentation about Falco. Markup,
https://www.falcoframework.com/docs/markup.html, I found a possible typo.
In this code example (HTML ⇒ Merging Attributes):
// Template
let master (title : string) (content : XmlNode list) =
Elem.html [ Attr.lang "en" ] [

    Elem.head [] [

        Elem.title [] [ Text.raw "Sample App" ]

    ]

    Elem.body [] content

]

[ Text.raw "Sample App" ] should probably be [ Text.raw title ].
—
Reply to this email directly, view it on GitHub
https://github.com/pimbrouwers/Falco.Markup/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDB57P3OV52ITAEOMXU5KTWBEK2LANCNFSM6AAAAAAQ2XZ3GU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi Pim,
I just finished reading the documentation. Falco has such a beautiful and consistent API, I really like it!
I hope you don't mind listing a few other places that might have a typo:

https://www.falcoframework.com/docs/markup.html
HTML => Merging Attributes

// Template
let master (title : string) (content : XmlNode list) =
    Elem.html [ Attr.lang "en" ] [
        Elem.head [] [
            Elem.title [] [ Text.raw "Sample App" ]
        ]
        Elem.body [] content
    ]

This is the same code example I mentioned yesterday.

https://www.falcoframework.com/docs/host.html#host
Custom Services and Middleware => add_service

let connectToDb : HttpHandler =
This function doesn't have a body. At least to me, it looks like that.

For these links, the jump link doesn't work and the section “Other Operations” doesn't exist.
Keep up the good work!
Stefan

Reference: https://github.com/pimbrouwers/Falco/issues/100


Documentation - Link & Instructions

Updated a link on the main readme to point back to the correct link (https://cloud.google.com/kubernetes-engine/docs/how-to/kubemci)
Added instructions for installing kubemci itself in the example readme.

/retest

thanks for the PR! merging...

actually, can you please squash your 2 commits please?

Squashed :)


Update README.md

Add link to new project that uses TinyTuya - thanks for this project, it made life much easier.

Thanks @teejo75 !  Nice project.


Cmd-option + left/right are broken after latest upgrade (5.0)

Describe the bug
Hitting Cmd-option + left/right no longer moves the active tab up or down.
To Reproduce
Steps to reproduce the behavior:

Open franz with multiple tabs
Hit cmd+option+left
nothing happens..

Expected behavior
It should work like it did before the upgrade
Desktop (please complete the following information):

OS: mac OSX
Browser chrome
Version 72.0.3626.109

+1, also experiencing this issue on MacOS Mojave 10.14.3 (Franz 5.0.0 Release 4.0.4 / Darwin / x64)


Dell Flash Utility won't download

I have confirmed i have the latest flash utility from March 2020 (A04) but the new 6.4.8 version fails to confirm.  Could be that they changed a name of a file on Dells end?  here is from the log: Error: BIOS flash upgrade utility failed to download. Check log for more details.  The tool will find and grab the bios files but cannot create the package as it does not find the flash utility anymore.  Link to current dell flash utility:  https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=wcj0c  notice the zip file name appears to have changed.

Ditto.

Same

Fun fact, if you check the temp folder, it's actually downloaded! I just deleted the file and it download it again, but still say the same error (by the way, what log should I check for more details?).
Tried running as admin an didn'T worked.
But, something stranged just happened. I copied over the file in temp to the Flash64Utility on my share. I also selected only 1 device and started download again... and it worked! It said it unzip in the temp folder, then detected a new version, promoted new version and put old in legacy. Everything is created no error, but, when I check in the bios source folder (where SCCM get the package from), it contain the bios files, but not flash utils like the others.
Log file says everything ran fine, but it didn't. While the package is created, it's missing the flash util
Info: Found BIOS URL FOLDER06279152M/1/Latitude_5X01_Precision_3541_1.9.1.exe	DriverAutomationTool	2020-07-14 08:43:24	78844 (0x133FC) Info: Latest available BIOS version is 1.9.1	DriverAutomationTool	2020-07-14 08:43:25	78844 (0x133FC) Info: Checking ConfigMgr for existing BIOS release - 1.9.1	DriverAutomationTool	2020-07-14 08:43:25	78844 (0x133FC) Info: Comparing BIOS versions	DriverAutomationTool	2020-07-14 08:43:25	78844 (0x133FC) Info: New BIOS download available	DriverAutomationTool	2020-07-14 08:43:25	78844 (0x133FC) Info: BIOS Download URL Found: https://downloads.dell.com/FOLDER06279152M/1/Latitude_5X01_Precision_3541_1.9.1.exe	DriverAutomationTool	2020-07-14 08:43:25	78844 (0x133FC) Info: Downloading Latitude_5X01_Precision_3541_1.9.1.exe BIOS update file	DriverAutomationTool	2020-07-14 08:43:26	78844 (0x133FC) BitsTransfer: Checking BITS background job	DriverAutomationTool	2020-07-14 08:43:29	78844 (0x133FC) Info: Downloading Dell flash update utility	DriverAutomationTool	2020-07-14 08:43:30	78844 (0x133FC) BitsTransfer: Checking BITS background job	DriverAutomationTool	2020-07-14 08:43:31	78844 (0x133FC) Info: Unzipping latest Dell Flash64 EXE in C:\Program Files\MSEndpointMgr\Driver Automation Tool\Temp\Flash64W_ZPE.exe	DriverAutomationTool	2020-07-14 08:43:31	78844 (0x133FC) Info: New Dell Flash 64 EXE version is 	DriverAutomationTool	2020-07-14 08:43:32	78844 (0x133FC) Info: Latest Dell Flash 64 EXE is 3.3.6	DriverAutomationTool	2020-07-14 08:43:32	78844 (0x133FC) Info: Creating new/updated Dell Flash 64 source	DriverAutomationTool	2020-07-14 08:43:32	78844 (0x133FC) Info: Archiving legacy file	DriverAutomationTool	2020-07-14 08:43:32	78844 (0x133FC) Info: Promoting  release to production	DriverAutomationTool	2020-07-14 08:43:32	78844 (0x133FC) Info: Copying Dell Flash64Bit EXE To \\server\SCCM_Packages\Drivers\DAT\Dell\Latitude 5401\BIOS\1-9-1\	DriverAutomationTool	2020-07-14 08:43:33	78844 (0x133FC) ConfigMgr: Creating BIOS Package	DriverAutomationTool	2020-07-14 08:43:33	78844 (0x133FC) ConfigMgr: Enabling Binary Delta Replication	DriverAutomationTool	2020-07-14 08:43:34	78844 (0x133FC)

Ok, I fixed it. The log still say a new version is available and that it's copying it all over the place (which isn't happening), but at least now all packages are created properly.
Get the Flash64W_ZPE.exe from the temp folder and extract it.
Then copy flash64w.exe to the temp folder.
Next, copy both file to the destination folder (mine is something like share\Dell\FlashUtility)
Start package creation in DAT.

Fixed in the latest exe.

Thanks, does that also mean its fixed in the powershell script too?  I do not use the exe as it does not allow me the control I  like for package organization in the MECM console.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Maurice<EMAIL_ADDRESS>Sent: Wednesday, July 15, 2020 6:24 AM
To<EMAIL_ADDRESS>Cc: Roger<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [maurice-daly/DriverAutomationTool] Dell Flash Utility won't download (#64)
** CAUTION: External email, be careful with links and attachments. **
Fixed in the latest exe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_maurice-2Ddaly_DriverAutomationTool_issues_64-23issuecomment-2D658712393&d=DwMCaQ&c=tjPg1sbLxZ1bjgTYa5hhdw&r=mnsqbuHqdN52kSvGCm3c6IrWrg12mA3fXAkMHYhUBKM&m=GcM6yd5Z7Qpqx0jlEC9RZkLcerZkB_iH06zUrfIspmE&s=Itv_nD4P0g9gsrkh3IofdeDn-pEgdmOoA1mw1X1EKYY&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AJKBV4PHFJYAMYCILR3MJ33R3WGXBANCNFSM4OS5J4AQ&d=DwMCaQ&c=tjPg1sbLxZ1bjgTYa5hhdw&r=mnsqbuHqdN52kSvGCm3c6IrWrg12mA3fXAkMHYhUBKM&m=GcM6yd5Z7Qpqx0jlEC9RZkLcerZkB_iH06zUrfIspmE&s=DQTEyPzydWELauseyo-RqgsmI0doDLR-u2hf4r3tQZI&e=.

This email message may contain confidential or privileged information. If you are not the intended recipient, please delete the message and any attachments and notify the sender by return email. You should not retain, distribute, disclose or use any of the information in this message.


Gameplay: vehicle altitude and attack mission

Altitude and attack modes should work now.
Added basic vehicle attack mission, makes it follow the target.
Fixed vehicle accuracy value.

Still in TODO: evasive maneuvering, make attack modes matter, fix weapon range calculations.

Looks good to me! Thanks for your help.


Reduce fuzz timeouts due to codebuild timeout limits.

Fix Ubuntu test-dep installs.
Indentation.
Resolved issues:
resolves CI scheduled build error
Description of changes:
One scheduled build is failing because codebuild is timing out before the fuzz test stops.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Issue to investigate root cause: https://github.com/awslabs/s2n/issues/2593


Autofill checkbox choices

fixes #315

autofill checkbox for quiz and survey
update error message for checkbox
update helptext for checkbox

I assume this PR subsumes PRs #455 and #491, and so should fix Issues #315, #465, #389 and #358.
Before I can merge this, a few things need to be fixed:

[ ] When changing the Field type, all choice labels are erased (or replaced with false/true in the case of checkbox). Desired behavior: If something is already there, it shouldn't be touched.
[ ] Checkbox in survey with skip logic gives validation error: Skipping to end not allowed for checkbox and checkboxes./Skipping to question not allowed for checkbox and checkboxes.
[ ] Hint for polls should be updated from comma to pipe: "Comma separated list of choices. Only applicable in checkboxes, radio and dropdown."
[ ] When putting skip logic for a text field, if the user enters any value that is not covered by the skip logic crashes the page with "'answer' is not in list"
[ ] Skip logic choices aren't saved for input type 'number'
[ ] Conflicting migrations caused by merge commit 4b880bf

@geoo89 this PR builds on top of those PRs #455 and #491 but shouldn't be merged before those.
these are interdependent and should be merged in succession starting from #455, #491, and then this one.
Issues related to those PR will be addressed in those PR, so review could be easy.

[ ]  Hint for polls should be updated from comma to pipe: "Comma separated list of choices. Only applicable in checkboxes, radio and dropdown."

help text for poll choices field updated in #455 and as polls only have these 3 field types "checkboxes, radio and dropdown" so I think there is no need to mention them in help text too. Updated help text is just "Pipe (|) separated list of choices."

[ ]  Checkbox in survey with skip logic gives validation error: Skipping to end not allowed for checkbox and checkboxes./Skipping to question not allowed for checkbox and checkboxes.

addressed in #491

[ ]  Skip logic choices aren't saved for input type 'number'

addressed in #491

[ ]  When putting skip logic for a text field, if the user enters any value that is not covered by the skip logic crashes the page with "'answer' is not in list"

addressed in #491

[ ]  When changing the Field type, all choice labels are erased (or replaced with false/true in the case of checkbox). Desired behavior: If something is already there, it shouldn't be touched.

addressed in #493


Add docs HPA scaling delay

This PR adds some docs about the options for configuring the scaling delay for HPA. It is a very important feature not documented before.

This change is

This looks good to me, but we need a quick tech review.

@vishh @Random-Liu @tallclair @jszczepkowski Could one of you give tech approval for this? Thanks.

Ping @jszczepkowski

lgtm
I think tagging sig-autoscaling in addition to individual people would result in much faster review (@jszczepkowski is on a leave right now and other people in sig had no visibility of this PR).


Add delayer when hit detected on sensor

Added a delay after recording a hit which should stop the processor from recording further resonating hits within a 200 ms threshold.

Based on tonight might need to revert

From: Arius Alipour @.>
Sent: Tuesday, June 22, 2021 6:52:01 PM
To: BarneyMcgrew/BMG-Stop-Plate @.>
Cc: John Thompson @.>; Review requested @.>
Subject: Re: [BarneyMcgrew/BMG-Stop-Plate] Add delayer when hit detected on sensor (#5)
Merged #5https://github.com/BarneyMcgrew/BMG-Stop-Plate/pull/5 into main.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHubhttps://github.com/BarneyMcgrew/BMG-Stop-Plate/pull/5#event-4924333354, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFRXMZANPUAWPGL246SDXXTTUDEUDANCNFSM46YFGYQQ.


Minor bug fixes and simplifications

Made minor bug fixes and simplifications -
Changed config to take in EventHubCompatibleEndpoint, instead of needing the user to get the EventHubCompatibleNamespace
Made updates to handle running multiple instances simultaneously
Other minor bug fixes

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

It looks like you're a Microsoft contributor (Varun Puranik). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


vcpkg_from_github should not assume github.com

I cannot use vcpkg_from_github for my local github (enterprise) repositories because the url is hardcoded to github.com.  Please make it variable.

Ah, I see there is vcpkg_from_git which does take a url.  my bad :)


Unexpected token

/usr/local/lib/node_modules/react-native-create-library/lib.js:7
const { hasPrefix, createFile, createFolder } = require('./utils');
SyntaxError: Unexpected token {
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:374:25)
at Object.Module._extensions..js (module.js:417:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
at Object. (/usr/local/lib/node_modules/react-native-create-library/command.js:3:23)
at Module._compile (module.js:410:26)
at Object.Module._extensions..js (module.js:417:10)

Hi @abhitheawesomecoder, thanks for you the issue. Just to clarify and for future reference did you run into the issue in a Node < 6 environment?

yes right and its fixed and i have closed the issue
On Wed, Mar 8, 2017 at 4:28 AM, Johannes Stein<EMAIL_ADDRESS>wrote:

Hi @abhitheawesomecoder https://github.com/abhitheawesomecoder, thanks
for you the issue. Just to clarify and for future reference did you run
into the issue in a Node < 6 environment?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/frostney/react-native-create-library/issues/31#issuecomment-284888436,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADwwTgs5z1CZuH0PKUs4SKstdkC3D8cnks5rjeEFgaJpZM4MURru
.

--
Dev Abhi
Web Application Developer at Custom PHP Script
http://customphpscript.com
http://customphpscript.com http://customphpscript.com


Clarify angle units in documentation

The PR aims to clarify which angle unit functions use, since there are some that use radians and others that use degrees. Based on the current documentation alone, a new user may not be certain what the correct input/output should look like. After researching the topic and looking into the function definitions, I added notes on what angle unit was used for each related function.
The modified files are:

src/geometry/rotation_specialization.rs
src/geometry/rotation_specialization.rs
src/base/matrix.rs

Based on: https://github.com/dimforge/nalgebra/issues/1234

This seems to have a lot of modified files, can you clarify what this pull request does?

The PR aims to clarify which angle unit functions use, since there are some that use radians and others that use degrees. Based on the current documentation alone, a new user may not be certain what the correct input/output should look like. After researching the topic and looking into the function definitions, I added notes on what angle unit was used for each related function.
The modified files are:

src/geometry/rotation_specialization.rs
src/geometry/rotation_specialization.rs
src/base/matrix.rs

Please put the text in the pull request description.

I have made only 3 modifications (regarding the files mentioned in the description). The rest I believe are due to the UPB-CS-OpenSourceUpstream's repository being a few commits behind the main repository.

Please rebase your PR, I updated the repo.


trim trailing backslash if it exists - fixes #6628

Trim the trailing backslash from the Path to publish symbols.  This fixes #6628 .

@ericsciple , sorry to ping you regarding this PR as I'm not sure you're the right person to do the review, but the PR seems to have slipped through the cracks.  Can you get this to the right reviewer?

@arunkm Could you review?

@mitchdenny can you consider merging this PR?

@mitchdenny can you consider merging this PR?

The conflicts need to be resolved :) @stephenmichaelf what was the original issue? Would the symbol publish to a UNC share fail with a training slash?

@mitchdenny, yes.  The task would fail if the input had a trailing backslash.  I don't know if this is still an issue in the product; we're working around the issue by not putting a trailing backslash in our UNC paths.

Given there are work arounds and no one else has reported I suggest we close this.

@stephenmichaelf I'm OK with that. @MarkIannucci sorry this fell down. If you're able to resolve your PR conflicts I'm happy to re-open and get this merged in.

No worries.  We've moved from on-prem to the service, so now any adjustments we'd like to make will be far closer to the head and will be easier for all to merge.
A side note, I'm glad to see that even though it was lost for a little while, @stephenmichaelf resurrected the PR to see if it could be brought into the fold.


reenable highest stream offset metrics

Codecov Report

Merging #8372 (357918b) into master (98d7810) will decrease coverage by 49.84%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master    #8372       +/-   ##
=============================================
- Coverage     64.08%   14.24%   -49.85%
+ Complexity     4254       81     -4173
=============================================
  Files          1592     1594        +2
  Lines         83916    84041      +125
  Branches      12706    12719       +13
=============================================
- Hits          53779    11971    -41808
- Misses        26261    71173    +44912
+ Partials       3876      897     -2979

Flag
Coverage Δ

unittests1
?

unittests2
14.24% <0.00%> (+0.03%)
:arrow_up:

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

Impacted Files
Coverage Δ

...a/org/apache/pinot/common/metrics/ServerGauge.java
0.00% <ø> (-91.67%)
:arrow_down:

...manager/realtime/LLRealtimeSegmentDataManager.java
0.00% <0.00%> (-46.04%)
:arrow_down:

...ain/java/org/apache/pinot/core/data/table/Key.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/spi/utils/BooleanUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/core/data/table/Record.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/core/util/GroupByUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/config/table/FSTType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/data/MetricFieldSpec.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...va/org/apache/pinot/spi/utils/BigDecimalUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/common/tier/TierFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 1106 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 98d7810...357918b. Read the comment docs.


Update version to 1.0.91-1 on staging

Update version to 1.0.91-1

🚀 Deployed to production by @roryabraham in version: 1.0.92-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Provide Login feedback for users

Create feedback for users
Logging in

incorrect password
incorrect email
email/account doesn't exist

Signing up

email already exists
passwords don't match
password is too short

This issue is done when all of the above is completed. This feature should be worked on in the branch Login

I would recommend not specifying which item is incorrect when logging in. It provides information to bad actors that they don't need.
For the signup process you'll need to notify if the email exists. But for the log in process not so much.

Good point @HacDan!

we can say at the login "wecome back $username"
i think that is what alot of apps do

I believe this has already been merged, so maybe we should close this issue and continue in #64 for improvements?


Update README.md

Can we put this as third-party-programs.txt file instead of README. We need to put other landing page information in README.


Storage Class policy is not applied to Persistent Volume Claims generated from StatefulSets

Bug description
Storage Class policy is not applied to Persistent Volume Claims generated from StatefulSets. Only PVCs directly created by the user are subject to the policy. PVCs created from a StetefulSet template are not subject to the Storage Class policy defined at tenant level.
How to reproduce
As cluster admin, create a tenant with a StorageClass policy.
Login as tenant owner and:

create a PVC with not permitted Storage Class: the request is denied
create a STS with a PVC template using a not permitted Storage Class: the request is accepted and the PVC is created.

Expected behavior
STS having a PVC template with not permitted Storage Class should be denied
Logs
Additional context
capsule v0.0.1
kubernetes 1.19.2

Nice catch and this can be applied to any other Service Account, so applies also to Ingress Class.
We have to make the webhook logic more generalist and not relying just on the user ownership, got PR ready for this.


Can't extend FileLoggerTree constructor private (methods protected)

methods are protected which is great but constructor private. Cant extend FileLoggerTree

Tks,
It will be fixed in next version


VSCode still recommends Remote-WSL extension after I turn off WSL feature on Windows

Issue Type: Bug
One year ago I installed WSL on my Windows 10 machine. At that time VSCode detected that WSL was installed and recommended me to use the "Remote-WSL" extension.
Yesterday I tried to remove WSL on my Windows 10 machine by following three steps:

Uninstall all linux distro from Microsoft Store.
Turn off WSL feature as a whole from the 'Control Panel' -> 'Programs-Features' -> 'Turn on/off Windows features'.
Restart the machine.

Yet after the aforementioned steps, VSCode still somehow incorrectly detects that WSL is installed on the machine and recommends the "Remote-WSL" extension.
I wonder how VSCode internally detects the existence of WSL. Is it because VScode has error in its WSL-installation detection mechanism, or because I fail to remove WSL feature completely?
Thank you for any kind help and clarification.
VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:20.174Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz (4 x 2394)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.92GB (0.93GB free)

Process Argv
D:\Users\dell\Documents\Git-Repository@Work-In-Progress\Go playground

Screen Reader
no

VM
0%

I also wonder why.
Interestingly, “Remote - WSL” is recommended to me because it is installed. 😂

Additionally, if I recall correctly, recommendations are never dismissed until I click Ignore Recommendation.

The problem is solved. Turn out that it requires more than one restart to let the "remove WSL feature" complete it job.

Ok, cool. I tried to reproduce and it worked for me.
But what's strange is the label The extension is recommended because you have Remote - WSL installed. @sandy081 FYI.


[ISSUE-81] Fixed head of empty list issue on stem method

I'm sending a patch for an issue( #81 ) that I faced when stemming some contents.
Could you please take a look at this?

Thanks!!!!

Thanks too~^^


Implement API that takes the key value pairs of information necessary to inject a chaos instead of Passing a complete Manifest.

Implement API that takes the key value pairs of information necessary to inject a chaos instead of Passing a complete Manifest.
Current Approach
Currently we need to have a manifest file locally, and then convert it into a support format then pass the manifest as value to the API. This is complicated and error prone.
 "ChaosWorkFlowRequest": {
                "projectID": projectID,
                "clusterID": clusterID,
                "workflowManifest": "YOUR COMPLETE MANIFEST FILE HERE",
                "workflowName": chaos_specifications['CHAOS_EXP_NAME'],
                "cronSyntax": "",
                "workflowDescription": f'Chaos Workflow information: {chaos_specifications["DESCRIPTION"]}',
                "weightages": [
                ],
                "isCustomWorkflow": False
            }

Requested Feature
This sample approach eliminates the above complications and basically mimics the LitmusPortal UI's simplicity. As in the UI we don't write the manifest file but just enter some necessary values in the Chaos Config Form and click to start the chaos.
"ChaosWorkFlowConfig" : {
                "chaos_experiment_name": "pod-delete",
                "chaos_target_label": "app=ngnix",
                "chaos_target_appkind": "deployment",
                "total_chaos_duration": "120",
                "chaos_interval": "60",
                "pods_affected_perc": "100",

                "projectID": projectID,
                "clusterID": clusterID,
                "workflowName": chaos_specifications['CHAOS_EXP_NAME'],
                "cronSyntax": "",
                "workflowDescription": f'Chaos Workflow information: {chaos_specifications["DESCRIPTION"]}',
                "weightages": [
                ],
                "isCustomWorkflow": False
 }

Hi @spshuklaji , this is a good feature request. I would request you to join the Litmus contributors call, where you can pitch this idea to the team. We will decide on the same.


⚠ PrivateHD has degraded performance

In 8384d39, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2141 ms

Resolved: PrivateHD performance has improved in 9a3f786.


virtualRow.index is sometimes NaN

I can't seem to reproduce this consistently, but sometimes virtualRow.index is NaN, which causes my application to crash...

Having same issue on 2.2.4, going back to 2.2.1

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add 'prepublish' script in package.json, to convert to EOF line endings

Fix for #7 in future publishes. I usually publish from a windows machine, and it looks like the windows-style line endings cause problems. This will set the line endings to just LF prior to publishing.

Will republish in a bit after a few more fixes


php artisan vendor:publish - views modules

Hi,
Is there any way for when executing the "php artisan vendor:publish" command not to allow the view's modules to be copied to Laravel /resources/views/ folder? Or is this standard of laravel-modules?

Something else happened, the modules are missing from the listing, but their folders are there.

You can simply not register those views in the module service provider.
Look at the registerViews method in your module Service Provider. hint: the publishes call.

If they're not showing, might be because they don't have a module.json file.

I left the default, follows example:
/**
     * Register config.
     *
     * @return void
     */
    protected function registerConfig()
    {
        $this->publishes([
            __DIR__.'/../Config/config.php' => config_path('painel.php'),
        ], 'config');
        $this->mergeConfigFrom(
            __DIR__.'/../Config/config.php', 'painel'
        );
    }

    /**
     * Register views.
     *
     * @return void
     */
    public function registerViews()
    {
        $viewPath = base_path('resources/views/modules/painel');

        $sourcePath = __DIR__.'/../Resources/views';

        $this->publishes([
            $sourcePath => $viewPath
        ]);

        $this->loadViewsFrom(array_merge(array_map(function ($path) {
            return $path . '/modules/painel';
        }, \Config::get('view.paths')), [$sourcePath]), 'painel');
    }

Should I change this $viewPath variable?
Strange this issue of module listing, because the module.json file is at the root of each module. Configuration example:
{
    "name": "Painel",
    "alias": "painel",
    "description": "",
    "keywords": [],
    "active": 1,
    "order": 0,
    "providers": [
        "Modules\\Painel\\Providers\\PainelServiceProvider"
    ],
    "aliases": {},
    "files": [
        "start.php"
    ],
    "requires": []
}

p.s.: This happened after I had to run the "php artisan vendor:publish" command to configure the Zizaco/entrust package.

And in this default service provider, you can see it publishes the views, you don't want this to happen, so you can remove this call.
Don't know why your modules aren't listed. I would double check the modules.php config file, and make sure the module path is correct for your project.

my config/modules.php:
<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Module Namespace
    |--------------------------------------------------------------------------
    |
    | Default module namespace.
    |
    */

    'namespace' => 'Modules',

    /*
    |--------------------------------------------------------------------------
    | Module Stubs
    |--------------------------------------------------------------------------
    |
    | Default module stubs.
    |
    */

    'stubs' => [
        'enabled' => true,
        'path' => base_path() . '/stubs',
        'files' => [
            'start' => 'start.php',
            'routes' => 'Routes/routes.php',
            'json' => 'module.json',
            'views/index' => 'Resources/views/index.blade.php',
            //'views/master' => 'Resources/views/layouts/master.blade.php',
            'scaffold/config' => 'Config/config.php',
            'composer' => 'composer.json',
        ],
        'replacements' => [
            'start' => ['LOWER_NAME'],
            'routes' => ['LOWER_NAME', 'STUDLY_NAME', 'MODULE_NAMESPACE'],
            'json' => ['LOWER_NAME', 'STUDLY_NAME', 'MODULE_NAMESPACE'],
            'views/index' => ['LOWER_NAME'],
            //'views/master' => ['STUDLY_NAME'],
            'scaffold/config' => ['STUDLY_NAME'],
            'composer' => [
                'LOWER_NAME',
                'STUDLY_NAME',
                'VENDOR',
                'AUTHOR_NAME',
                'AUTHOR_EMAIL',
                'MODULE_NAMESPACE',
            ],
        ],
    ],
    'paths' => [
        /*
        |--------------------------------------------------------------------------
        | Modules path
        |--------------------------------------------------------------------------
        |
        | This path used for save the generated module. This path also will added
        | automatically to list of scanned folders.
        |
        */

        'modules' => base_path('app/Modules'),
        /*
        |--------------------------------------------------------------------------
        | Modules assets path
        |--------------------------------------------------------------------------
        |
        | Here you may update the modules assets path.
        |
        */

        'assets' => public_path('modules'),
        /*
        |--------------------------------------------------------------------------
        | The migrations path
        |--------------------------------------------------------------------------
        |
        | Where you run 'module:publish-migration' command, where do you publish the
        | the migration files?
        |
        */

        'migration' => base_path('database/migrations'),
        /*
        |--------------------------------------------------------------------------
        | Generator path
        |--------------------------------------------------------------------------
        |
        | Here you may update the modules generator path.
        |
        */

        'generator' => [
            //'assets'        => 'Assets',
            'config'        => 'Config',
            //'command'     => 'Console',
            'event'         => 'Events',
            'listener'      => 'Events/Handlers',
            'migration'     => 'Database/Migrations',
            'model'         => 'Models',
            'repository'    => 'Repositories',
            'routes'        => 'Routes',
            'seeder'        => 'Database/Seeders',
            'controller'    => 'Http/Controllers',
            'filter'        => 'Http/Middleware',
            'request'       => 'Http/Requests',
            'provider'      => 'Providers',
            'lang'          => 'Resources/lang',
            'views'         => 'Resources/views',
            'test'          => 'Tests',
            //'jobs'          => 'Jobs',
            'emails'        => 'Emails',
            'notifications' => 'Notifications',
        ],
    ],
    /*
    |--------------------------------------------------------------------------
    | Scan Path
    |--------------------------------------------------------------------------
    |
    | Here you define which folder will be scanned. By default will scan vendor
    | directory. This is useful if you host the package in packagist website.
    |
    */

    'scan' => [
        'enabled' => false,
        'paths' => [
            base_path('vendor/*/*'),
        ],
    ],
    /*
    |--------------------------------------------------------------------------
    | Composer File Template
    |--------------------------------------------------------------------------
    |
    | Here is the config for composer.json file, generated by this package
    |
    */

    'composer' => [
        'vendor' => 'teste',
        'author' => [
            'name' => 'test',
            'email' =><EMAIL_ADDRESS>        ],
    ],
    /*
    |--------------------------------------------------------------------------
    | Caching
    |--------------------------------------------------------------------------
    |
    | Here is the config for setting up caching feature.
    |
    */
    'cache' => [
        'enabled' => false,
        'key' => 'laravel-modules',
        'lifetime' => 60,
    ],
    /*
    |--------------------------------------------------------------------------
    | Choose what laravel-modules will register as custom namespaces.
    | Setting one to false will require to register that part
    | in your own Service Provider class.
    |--------------------------------------------------------------------------
    */
    'register' => [
        'translations' => true,
    ],
];

You don't have to link it to me, you need to check if the module path is correct. Only reason your modules aren't listed is most likely because it's not.

Ok, I'm going to do a "clean" test, I have a versioned code working here, I'll get the version that works and just run the "php artisan vendor:publish" command to check the changes. Then I post feedback.

Why can't you check if    'modules' => base_path('app/Modules'), is correct ?

do you tell the config that is in the "config/modules.php" folder? But it is correct. This is strange =S
And was working properly before the php artisan vendor:publish command.
'modules' => base_path('app/Modules'),

Hm ok so the path is correct.  Now the default option for the paths.modules configuration key is base_path('Modules') as you can see here: https://github.com/nWidart/laravel-modules/blob/master/config/config.php#L64 So you didn't just publish the configuration, you made a change to it.
Now you need to check why since that change the modules aren't loaded. Check the autoloading for instance.

Sorry, but where or what file do I check it?
I Tried:

I linked you a file, the one I mentioned in the previous posts.


[CERT-TEST-FAILURE] TC-LVL-1.1 - Test failed

Feature Area
Other
Test Case
TC-LVL-1.1
Reproduction steps
Step 1 : executed the below mentioned command to put DUT into a commissionable state
./chip-all-clusters-app
Step 2 : Once DUT reach the commissionable state sent below mentioned command on TH.
./chip-tool pairing onnetwork 1 20202021 Step 3 : TH reads the FeatureMap attribute from the DUT by sending mentioned command  ./chip-tool levelcontrol read feature-map 1 1
`
Expected value :
[1685961477.457760][42141:42143] CHIP:DMG: }
[1685961477.457832][42141:42143] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_FFFC DataVersion: 104404771
[1685961477.457863][42141:42143] CHIP:TOO:   FeatureMap: 7
[1685961477.457925][42141:42143] CHIP:EM: <<< [E:40457i S:16419 M:251039338 (Ack:116029204)] (S) Msg TX to 1:0000000000000001 [122F] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1685961477.457938][42141:42143] CHIP:IN: (S) Sending msg 251039338 on secure session with LSID: 16419

Actual value :
[1685961477.457760][42141:42143] CHIP:DMG: }
[1685961477.457832][42141:42143] CHIP:TOO: Endpoint: 1 Cluster: 0x0000_0008 Attribute 0x0000_FFFC DataVersion: 104404771
[1685961477.457863][42141:42143] CHIP:TOO:   FeatureMap: 3
[1685961477.457925][42141:42143] CHIP:EM: <<< [E:40457i S:16419 M:251039338 (Ack:116029204)] (S) Msg TX to 1:0000000000000001 [122F] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1685961477.457938][42141:42143] CHIP:IN: (S) Sending msg 251039338 on secure session with LSID: 16419

Bug prevalence
Everytime
GitHub hash of the SDK that was being used
5b4f8004662d00bdb111367fec7d3ea978c23372
Platform
raspi
Anything else?
As per the frequency feature implementation, the FeatureMap attribute value should be 7. But currently getting FeatureMap value as 3 in SDK.

test case has been removed from test-plan, hence closed this issue


Prebuilds break when two Electron majors share the same ABI version

It appears that using the ABI version to match Electron versions to prebuilds is fundamentally broken? Every time two Electron major releases share the same ABI  (10/11, 13/14 and 25/26) things break. Maybe it's time to ditch the ABI version for Electron prebuilds and always use the Electron version as identifier? Because after all Electron consists of more than just Node.js and it can break in other funny ways. Or am I misinterpreting this? It also appears that the native modules can work but they can also crash at runtime, making it way worse.
https://github.com/prebuild/prebuild/issues/275
https://github.com/serialport/node-serialport/issues/2191
https://github.com/WiseLibs/better-sqlite3/issues/1044
https://github.com/WiseLibs/better-sqlite3/issues/694

Does serialport still suffer from this? My understanding was that it now provides only prebuilt binaries for Node-API, which should work across multiple major versions of Electron and Node.js.

My understanding was that it now provides only prebuilt binaries for Node-API

@lovell In addition, they moved from prebuild to prebuildify quite a while ago.

@Prinzhorn It looks like better-sqlite3 is already considering a migration to Node-API and I highly recommend this approach as its API/ABI stability removes an entire class of error and reduces support overhead. There is some basic conversion tooling to partially convert source files.

@lovell thanks, I've posted this on the better-sqlite3 tracker to make them aware. I personally am not familiar with the whole native addon stack


Add LightBulb

https://github.com/Tyrrrz/LightBulb
LightBulb is an application that reduces eyestrain produced by staring at a computer screen when working late hours. As the day goes on, it continuously adjusts gamma, transitioning the display color temperature from cold blue in the afternoon to warm yellow during the night. Its primary objective is to match the color of the screen to the light sources of your surrounding environment - typically, sunlight during the day and artificial light during the night. LightBulb has minimal impact on performance and offers many customization options.
Microsoft Reviewers: Open in CodeFlow

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

Fixed: https://www.microsoft.com/en-us/wdsi/submission/940b27c3-6873-4af6-83df-16d9bee7d401


Add command-line paramter for ddtrace-run to specify config file

It would be helpful to have the option to specify the path of the Datadog Agent config file so it can be specified dynamically without having to resort purely to environment variables.
If there is already a way to do this, it should be documented in ddtrace-run --help or on the Agent Configuration Files documentation page.

👋  @nhooey, if you mean the ddtrace-run python tracer tool then please create an issue on the python tracer repo: https://github.com/DataDog/dd-trace-py

@nhooey are you trying to configure the Datadog agent or one of your Python APM services?
ddtrace-run is a Python specific command and we typically use environment variables to configure your Python APM services.


Zero-copy local cache

See original issue on GitLab
In GitLab by [Gitlab user @lle-bout] on Jul 1, 2020, 09:22
Background
Over at freedesktop-sdk, we noticed a major chunk of the build time is spent on either network I/O for remote caching, or disk I/O for copying back and forth with the local cache server.
Task description
(Suggested implementation choices, best would be https://virtio-fs.gitlab.io/ between Docker containers, as they are used by freedesktop-sdk and Gitlab CI, for a shared cache folder, and handle concurrent access to this cache folder with POSIX file system locking)

[ ] Make sure offset range fetch and write on cache remote API is supported
[ ] Create FUSE driver that consumes the cache remote API and fetches only chunks towards the requesting application without touching local disk more than once
[ ] Solve concurrent access problem by making sure the cache remains coherent
[ ] Study cache remote API performance especially for small repeated reads and writes from FUSE and try to optimize with memory caching or else (try to see if OS has mechanism to cache reads from FUSE already, also possible to fetch more bytes at offset than asked to anticipate sequential reads)

Acceptance Criteria
This is a relatively medium sized task that could be implemented short-mid term and provide huge build performance improvements for projects like freedesktop-sdk who make heavy continuous use of Buildstream.

In GitLab by [Gitlab user @lle-bout] on Jul 1, 2020, 09:29
changed the description

In GitLab by [Gitlab user @lle-bout] on Jul 1, 2020, 09:29
changed the description

In GitLab by [Gitlab user @lle-bout] on Jul 1, 2020, 09:29
changed the description

In GitLab by [Gitlab user @lle-bout] on Jul 1, 2020, 09:29
changed the description

In GitLab by [Gitlab user @lle-bout] on Jul 1, 2020, 09:35
It seems that there already was progress towards that goal here: https://gitlab.com/BuildGrid/buildbox/buildbox-fuse

In GitLab by [Gitlab user @lle-bout] on Jul 1, 2020, 09:35
It seems that there already was progress towards that goal here: https://gitlab.com/BuildGrid/buildbox/buildbox-fuse

In GitLab by [Gitlab user @sstriker] on Jul 3, 2020, 00:43
Personally I think this issue is proposing a solution a bit too quickly.

we noticed a major chunk of the build time is spent on either network I/O for remote caching, or disk I/O for copying back and forth with the local cache server.

[Gitlab user @lle-bout], thanks for reporting this issue.  Do you have any profiling data as to where/when time is being spent?
As you note there is buildbox-fuse that maybe be used by buildbox-casd if so configured for staging.  The current implementation in the master branch already uses buildbox-run that can leverage this functionality.
There will be other opportunities for optimization - please provide detailed data on the patterns you are seeing.

In GitLab by [Gitlab user @sstriker] on Jul 3, 2020, 00:43
Personally I think this issue is proposing a solution a bit too quickly.

we noticed a major chunk of the build time is spent on either network I/O for remote caching, or disk I/O for copying back and forth with the local cache server.

[Gitlab user @lle-bout], thanks for reporting this issue.  Do you have any profiling data as to where/when time is being spent?
As you note there is buildbox-fuse that maybe be used by buildbox-casd if so configured for staging.  The current implementation in the master branch already uses buildbox-run that can leverage this functionality.
There will be other opportunities for optimization - please provide detailed data on the patterns you are seeing.

In GitLab by [Gitlab user @lle-bout] on Aug 13, 2020, 21:53
[Gitlab user @sstriker] It's okay, I was just proposing something. I need to collect more precise data, but the current guesses based on monitoring tools such as netdata, iotop or htop - suggest that copying data back and forth in and out of a local cache server as well as a remote cache server is very expensive and wastes IOPS a lot. There's first, zero-copy local caching but there's also lazily fetching from caches, which isnt the case currently. Even if there's nothing to build, it has to copy all the caches (either from local or remote if local doesnt have it) to declare the build as success.

In GitLab by [Gitlab user @lle-bout] on Aug 13, 2020, 21:53
[Gitlab user @sstriker] It's okay, I was just proposing something. I need to collect more precise data, but the current guesses based on monitoring tools such as netdata, iotop or htop - suggest that copying data back and forth in and out of a local cache server as well as a remote cache server is very expensive and wastes IOPS a lot. There's first, zero-copy local caching but there's also lazily fetching from caches, which isnt the case currently. Even if there's nothing to build, it has to copy all the caches (either from local or remote if local doesnt have it) to declare the build as success.

In GitLab by [Gitlab user @sstriker] on Aug 14, 2020, 00:17
[Gitlab user @lle-bout] #1272, #1273, #1274, #1275 and actually only downloading blobs when necessary for the operation should help with this.
I've been aiming to have that be the default behavior in combination with RE.  That is, only deal with Trees, or file references if you will, and not with the actual file content itself when not executing the build locally.

In GitLab by [Gitlab user @sstriker] on Aug 14, 2020, 00:17
[Gitlab user @lle-bout] #1272, #1273, #1274, #1275 and actually only downloading blobs when necessary for the operation should help with this.
I've been aiming to have that be the default behavior in combination with RE.  That is, only deal with Trees, or file references if you will, and not with the actual file content itself when not executing the build locally.


Button to scroll to recent live chats (scroll to bottom)

PR Checklist

Please check all that apply to this PR using "x":

[X] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[ ] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[X] Bugfix
[X] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number: Closes #6009
What is the new behavior?

This only shows when it's not at the most recent comment right?

@tzarebczan now it does!


ConnectionReset, message: "Connection reset by peer"

I'm getting the below error while running oura in daemon mode for a long time. I'm guessing it's not handling a peer disconnection.
[2022-04-21T19:13:01Z ERROR pallas_multiplexer] Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }                  │
thread '<unnamed>' panicked at 'explicit panic', /cargo/registry/src/github.com-1ecc6299db9ec823/pallas-multiplexer-0.8.0/src/lib.rs:99:17    │
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace                                                                 │
[2022-04-21T19:13:01Z ERROR pallas_multiplexer] Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }                                     │
thread '<unnamed>' panicked at 'explicit panic', /cargo/registry/src/github.com-1ecc6299db9ec823/pallas-multiplexer-0.8.0/src/lib.rs:74:17    │
thread 'thread '<unnamed><unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: RecvError' panicked at '', called `Result::unw  │
thread 'main' panicked at 'error in pipeline thread: Any { .. }', src/bin/oura/daemon.rs:289:23                                               │
exec error: Error: Command failed: ./oura-1.3.1 daemon --config daemon.toml --cursor 911142,eb74846314f4389a12affc0c9bb664453dbb6013fcb62172  │
[2022-04-21T19:13:01Z ERROR pallas_multiplexer] Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }                  │
thread '<unnamed>' panicked at 'explicit panic', /cargo/registry/src/github.com-1ecc6299db9ec823/pallas-multiplexer-0.8.0/src/lib.rs:99:17    │
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace                                                                 │
[2022-04-21T19:13:01Z ERROR pallas_multiplexer] Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }                                     │
thread '<unnamed>' panicked at 'explicit panic', /cargo/registry/src/github.com-1ecc6299db9ec823/pallas-multiplexer-0.8.0/src/lib.rs:74:17    │
thread 'thread '<unnamed><unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: RecvError' panicked at '', called `Result::unw  │
thread 'main' panicked at 'error in pipeline thread: Any { .. }', src/bin/oura/daemon.rs:289:23

idk if we should handle this in pallas or oura

The other thing I was thinking in terms of error handling in oura, is it expected that it will eventually make it through to the sink target so it can handle it?

yes, this is tricky.
I usually run Oura as a Pod in a Kubernetes cluster. By panicking the process, the whole Pod restarts and I can control the retry / backoff policy using common k8s settings.
I understand that not every implementation will have an orchestration framework available to deal with these errors. One thing I'm certain, any retry mechanism needs to be configurable by the final user and not hidden as part of the implementation. The worst scenario is when you have a zombie process that isn't doing anything but not dying either.
Off the top of my head, I suggest:

a retry mechanism similar to the one we have during bootstrap, configurable via the daemon.toml file (with max retries and backoff delays).
treat this as an "Oura" concern (not Pallas) so that we can use the existing config / code artifacts.
add health metrics to the existing prometheus exporter so that we can monitor the state of the connection.

Adding a "disconnect" event is an option too. I thought about adding these type of "flow control" events for other use cases too (like stopping the pipeline), but I believe that we should wait until v2 so that we do it without adding complexity to the current event model.

I work at MLabs, and we would love to use Oura for our projects, but this is actually a major issue that's preventing us from committing to it wholesale. I would love to contribute to solving this problem if we could identify a good way to go about it, either here or in Pallas

I do, personally

I'm currently using N2N as it's easier to maintain. My current implementation is using NodeJS to control Oura and pass to the DB cluster. I'm in the process of implementing a "rapid" sync by running a dozen Oura instances and connect to 10+ cardano-node servers to then populate the DB from different block points. So for me N2N is the best way to do this.

FYI, almost done with this features, working draft in #332.
N2N done, still working on N2C.

@CyberCyclone @nalane the automatic retry is available since v1.5. Both N2N and N2C will attempt to reconnect (and handshake) if the bearer closes abruptly. The retry uses an exponential backoff delay (1s, 2s, 4s, etc).
There are two new config values that control the logic:
chainsync_max_retries: defines the amount of retry attempts before exiting the pipeline. Defaults to 50.
chainsync_max_backoff: the max amount of seconds to wait between retries. Defaults to 60s.


[cleanup][broker]remove methods no longer used in AdminResource #7

Motivation
org.apache.pulsar.broker.admin.AdminResource#fetchPartitionedTopicMetadataCheckAllowAutoCreation and org.apache.pulsar.broker.admin.AdminResource#fetchPartitionedTopicMetadata are no longer used.
Modifications
remove org.apache.pulsar.broker.admin.AdminResource#fetchPartitionedTopicMetadataCheckAllowAutoCreation and org.apache.pulsar.broker.admin.AdminResource#fetchPartitionedTopicMetadata.
Verifying this change

[x] Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/Pomelongan/pulsar/pull/7

Please check the unused import, such as import org.apache.pulsar.broker.PulsarService;

Please check the unused import, such as import org.apache.pulsar.broker.PulsarService;
I have updated it.PTAL @HQebupt


chore: Update the devcontainer used by the CI/CD workflow

This is required to enable the new Python setup to run the test correctly (schematic project)

Issue
The following error arises with the new devcontainer. It may be because a new version of git may be included in this container.
Error: Command failed: git rev-parse HEAD
fatal: detected dubious ownership in repository at '/__w/sage-monorepo/sage-monorepo'
To add an exception for this directory, call:

	git config --global --add safe.directory /__w/sage-monorepo/sage-monorepo

    at checkExecSyncError (node:child_process:885:11)
    at execSync (node:child_process:957:15)
    at /__w/_actions/nrwl/nx-set-shas/v3/dist/index.js:13735:20
    at /__w/_actions/nrwl/nx-set-shas/v3/dist/index.js:13771:3
    at /__w/_actions/nrwl/nx-set-shas/v3/dist/index.js:13846:3
    at Object.<anonymous> (/__w/_actions/nrwl/nx-set-shas/v3/dist/index.js:13849:12)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32) {
  status: 128,
  signal: null,
  output: [
    null,
    '',
    "fatal: detected dubious ownership in repository at '/__w/sage-monorepo/sage-monorepo'\n" +
      'To add an exception for this directory, call:\n' +
      '\n' +
      '\tgit config --global --add safe.directory /__w/sage-monorepo/sage-monorepo\n'
  ],
  pid: 120,
  stdout: '',
  stderr: "fatal: detected dubious ownership in repository at '/__w/sage-monorepo/sage-monorepo'\n" +
    'To add an exception for this directory, call:\n' +


Use of singletons, global variables with nodejs

Is this a BUG REPORT or FEATURE REQUEST?:
Feature request
What happened:
When creating a function we often want to initialize an object/variable just one time when the function is first executed.
In my example I would I am creating a connection to Redis and I would like to reuse the connection as there is a significant cost to create a connection for each execution of the function.
What you expected to happen:
If I initialize a variable/object outside of the module.exports definition I would expect that the object is initialized once, on the first execution.
How to reproduce it (as minimally and precisely as possible):
To test this I created a simple function that initializes a variable outside of the exported function and increments the variable inside the function. If the variable is always zero then the variable is being initialized on each execution of the function.
var i = 0;

module.exports = { main: async function (event, context) {
    console.log("val = " + i++);
    return "test"
}}

When I execute the function multiple times the variable 'i' is not incremented.
I also tried using a global variable but I get the same result
var global.i = 0;

module.exports = { main: async function (event, context) {
    console.log("val = " + global.i++);
    return "test"
}}

Anything else we need to know?:
I tried the same code with Azure functions and AWS Lambdas and the behaviour is different.  The variable is only initialized once on the first execution and incremented thereafter.
Environment:

Kubernetes version (use kubectl version): v1.10.3
Kubeless version (use kubeless version): v1.0.0-alpha.8
Cloud provider or physical cluster: minikube

Hi @brendandobbs, that behavior was removed intentionally. See the details here: https://github.com/kubeless/kubeless/issues/632. Basically there are some concerns because one function execution could infer in the result of a different call if it modifies global/env variables. That's why each call is sandboxed and executed independently.
Having said that, if that issue is a blocker for you, other runtimes like Python or Golang are less strict with the sandbox environment. Would that work for you? The other option would be for you to fork the NodeJS runtime to restore the previous behavior but that would require more work.

Thanks for the information @andresmgot. I understand the concern and the reason for sandboxing however without the possibility to use global variables to initialize an object that is expensive to create  just once (and reuse it), then we take a substantial performance hit that makes the kubeless nodejs runtime not suitable for many use cases.
My preference would be to support globals and let the developers use them wisely (or unwisely as the case maybe). This seems to be the approach used by Azure, AWS and Google functions.
Here you can even see what google is recommending as a best practice :  [Use global variables to reuse objects in future invocations ](https://cloud.google.com/functions/docs/bestpractices/tips

Hi @andresmgot,
I support the request from @brendandobbs . Especial if we connect an function to an database we should not initialize the DB connection on each function run. I guess using global is the right way to prevent fails. Do you have an idea how to get it working or should we have a look into it?

Hi,
I understand the use case (and we are using the same approach in other runtimes). Could you send a PR to check what fit best your needs? It was @cscheiber the one that implemented the last approach so he may be able to help with that.

Hi,
the sandbox covers only the main file. If you introduce a second js-file and require this from your main file, you will see that all globals in the second module survive.
Actually, this is not nice from sandbox point of view, but we could also call it a feature. For sure one needs a kind of cache for any client that opens a connection to db, messaging brokers or whatever. Even for OAuth-tokens one will probably try to avoid calling the token endpoint with each single function call.
BTW, the context object is also stable and reused within the POD for all function calls. If kubeless would add a Map object, called e.g.  cache to the context this could be an official solution as well.
Best regards
Christoph

Thanks Christoph. That's useful information about the context object. At least there is currently a way to cache objects between requests.
The issue I see with not allowing globals in the main js file is that it's going to be confusing for developers as it changes the behaviour of what they're used to when creating nodejs apps (e.g. express) and it's also different to how other FaaS providers handle globals.
I don't know enough about the issue for #632, but would it not be possible to support globals while still preventing the request, response, event, context etc from being visible globally?
Regards,
Brendan

Hi @brendandobbs
the initial design that I saw first was already based on the sandbox.  #632 was just a cleanup to hide kubeless runtime data from custom code. The sandbox stayed in use unchanged. And it is also the reason why globals are reset (only in main file === sandbox). An advantage of the sandbox is timeout and error handling. Probably, good reasons to keep it.
Nevertheless, I understand your points. But there will be different expectations from different users. Some may also expect the cleanup.
In examples that I implemented I often used a separate module anyways to split e.g. oauth or config data access from other parts. Hence, I did not really have problems here.
Best regards
Christoph

Thanks Christoph,
I think you're going to meet with my colleague Johannes to discuss the options so we can park this for now.
Best,
Brendan


Update mode.md

Fix Typo

Thanks for your contribution, unfortunately I was already fixed in https://github.com/webpack/webpack.js.org/pull/1937, please check for previous PRs before submitting yours.


Improve tx-processor testing

Wrote a new test while fixing #895

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.279%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5769

Relevant Lines:
6535

💛  - Coveralls

There is only included the test where is the fix?

There's no fix. Check the name of the PR 😉

Agree was to confirm.


feat: use EIP1559 txs

Checklist

[x] I have read the coding guide.
[x] I have added tests to cover my changes.
[x] I have filled out the description and linked the related issues.

Description

resolved merge conflicts from existing pr, code already written by @ralph-pichler at #3021
Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)

an existing pr has been hanging for a while now which has been resolved
Related Issue (Optional)

#3021
Screenshots (if appropriate):
https://ibb.co/GpvKrcb

This change is

We can even combine Send and SendWithBoost as one function where the boost value is ignore if it's zero.


Feat: continuing improvement based on Joseph's Google SSO implementation

Sorry I accidentally deleted my remote "proxy-sso-impl" and had to re-issue the pull request. Please refer back to https://github.com/fluid-project/personal-data-server/pull/11 for existing review comments.
This PR based off Joseph's SSO implementation at https://github.com/fluid-project/personal-data-server/pull/10 and replaces https://github.com/fluid-project/personal-data-server/pull/11.
It includes:

Refactor the code structure;
Replaced "node-fetch" library with "axios";
Broke dockerStartDatabase() function into 4 steps: start db docker container, create db, clear db, load data
Modified all tests to replace IoC testing framework with jqUnit;
Fix the hardcoded db environment variables in db connection script;
Write a single script to start the server including starting the backend database and loading data.
Get tests to run on CI.
Write documentation.

@amb26 all new comments have been addressed.

Thanks for the great work, @cindyli !


Tracking item views

I've always wanted to be able to track views of products on ecommerce sites similar to how Google AdWords tracks ad views in different positions on a page. I've thought about how this could work and I believe we would need to track the following parameters:

Area on page (e.g. category listing, similar products, recently viewed)
Product SKU
Position within area (e.g. 1, 2, 3 and so on)

If not passing it through events, I would imagine it could be tracked as follows and then deserialised during the ETL:
snaq.push(['trackOffers','category listing',{Array of SKUs in the order they are displayed in the area}]);
snaq.push(['trackOffers','recently viewed',{Array of SKUs in the order they are displayed in the area}]); // Count of ranking continues from previous area

This would be a killer of an analytics feature to be able to offer out of the box - particularly for product managers. You could look at a product's CTR and conversion rate alongside all of SnowPlow's other metrics.
Thoughts?
EDIT: Can also work for a news site / blog in terms of article link clickthrough rates.

Closing as this will be implemented in the JavaScript Tracker (doesn't require any updates to core).


Hover effects on footer made

Issue Title:  Footer hover effects improvement #447
closes #447
Type of change ☑
What sort of change have you made:

[X] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist: ☑

[X] My code follows the guidelines of this project.
[X] I have performed a self-review of my own code.
[ ] I have commented my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have added things that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

How Has This Been Tested? ⚙
Hover effects on footer have been modified. Previously it was leading to a darker color on hovering the links in the footer but now it has been modified to look good.

@0xabdulkhalid I have made the changes which were required Kindly have a look at it.

@singodiyashubham87 Kindly have a look at it.


Provide onBlur handler for when the Dropdown focus out

Description
There's no easy way to currently know when the Dropdown component did focus out. Flutter has no consistent concept of focus, so this is what I mean: when user press the button and the list of items appear, the component is focused. When the user choose one of the items or press/click outside the list (returning null), the component is focusing out, meaning a blur.
I'm sure a onFocus or onTap would be equally useful, but it may be subject of a separated issue/PR.
By searching a way of dealing with the need of knowing the focus out of a dropdown, I didn't found anything useful. This question on Stack Overflow, however, enlightened me a bit to the fact that this simply is not possible with the current API. Being so, I had to copy dropdown.dart into my project and made the changes I needed.
The major problem herer, is, however, that, although the real changes happen in less than a dozen of lines (as you can see in this commit), the final file (I called it blurrable_dropdown.dart) has more than a thousand lines. This happens because (1) I can't simply inherit DropdownButton; and (2) there's a lot of internal private dependencies that had to be kept on the code (_DropdownMenuPainter,  _DropdownScrollBehavior etc). As they are not public, I can't reuse them. Thus, it seems to be a good idea to include this in the core. It's simple and (almost if not virtually) costless.
I can't really prove that other people need this feature. In my specific case, I am developing a app where the forms validations happens per field, on blur. I.e., the user select the input and, after he leaves the field, it validates itself. This is a real use-case, although I don't know if common.
Related Issues
I did not openend a issue, but I can if necessary. Also, didn't found any previous related issue.
Tests
I added the following tests:
Replace this with a list of the tests that you added as part of this PR. A change in behaviour with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Hi @mateusfccp, take a look at https://github.com/flutter/flutter/pull/42811: this adds a focus node to the dropdown button, where you can pass in a FocusNode that you're listening to for focus changes.  That is more consistent with the rest of our API, and should provide the functionality you're interested in.

Hi @mateusfccp, take a look at #42811: this adds a focus node to the dropdown button, where you can pass in a FocusNode that you're listening to for focus changes. That is more consistent with the rest of our API, and should provide the functionality you're interested in.

Thanks, @gspencergoog. Didn't find anything related, but I think I may close now in favor of your solution.


Will WebHooks.Receivers.VSTS be ported to .NET Core / .NET Standard 2.0?

Are there plans to port the VSTS receiver from the old repo (AspNetWebHooks) to this one (WebHooks)?
Thanks,
--Neno

We have no such plans to support the VSTS receiver at this time.


Runs don't get flagged as downloaded (seemingly)

I have two computers that I have used this project with along with my 310xt successfully.  Unfortunately I've noticed that if I download a run on one computer and then initiate a download of a future run with a different computer the second computer downloads both runs.
If I download from just the first one twice then just one run is downloaded the second time.  It's almost as though the run doesn't get marked as downloaded on the watch.
Coming from an older 405 (and a different project: python-ant-downloader) this wasn't an issue for me, it seemed runs were marked as downloaded.

I'll do it.


Agent metadata clear to trigger re-register action for avoid restart agent when backend server metadata was mistakenly deleted

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[x] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

Coverage decreased (-0.009%) to 12.735% when pulling 0d650a796f6d7748e618befe2558f5c474ed162a on Liu-XinYuan:master-register into e727de96b288fba3102a2101bb2d61ca7fc5a60c on apache:master.

@wu-sheng I have completed the local test, please help me merge into.

I think the community will like #1973 more. I hope I could push this to beta release.

@Liu-XinYuan Add some documents about how to use it will be good.

@wu-sheng Yep, I'd be glad to test this feature that's very interesting to the user.

No any feedback from review 20days ago. I am closing this. @peng-yongsheng


RNN when CUDNN is disabled

Description
Current RNN ops are supported only when CUDNN is enabled. We should also add RNN support with CUDNN disabled.  The new stage added by #11470 will ignore these failures for CUDNN disabled for now.

@sandeep-krishnamurthy requesting this be labeled as cuda, rnn, and operator


http-types dependency seems unmaintained

Hi! Is it important for wiremock to use the http-types crate (from http-rs which unfortunately looks pretty dead as a whole) as opposed to the http crate (from hyperium)? It has not seen a release in almost two years and pulls in several unwanted dependencies ([old] serde_qs, old rand).

It isn't crucial, and I'd be open to removing it if somebody wants to put in the effort.

Well, I'll give it a try on this weekends:)


Any recommended best practices for upgrading cf-mgmt 0.91 to latest?

As a PCF operator, I'm going to be bumping our prod cf-mgmt configuration from 0.91 to the latest.
Do you have any recommended upgrade "path"? E.g., should I start with bumping the binary version without changing the pipeline? Should I make sure all orgs/spaces have all the proper configuration keys before I upgrade?... Or should I just destroy the cf-mgmt pipeline, upgrade everything to the best I can as if I were starting fresh from latest, and then re-create the cf-mgmt pipeline?
Any advice is welcome; thanks a ton

Latest SHOULD just work with existing pipelines.  Any new pipeline tasks have been added with feature flags to enable the capability.  If you pull the latest binary you can use the apply command (https://github.com/pivotalservices/cf-mgmt/tree/master/docs/apply) to simulate the pipeline running but enable the --peek flag to dry-run what would happen if you add the pipeline with your existing configuration.

In a similar situation right now. I started by bumping the docker image referenced, created my new template pipeline and I'm working on updating all existing configs to ensure I have any new keys in there. Once I get through the configs update I'll start updating my current pipelines to the new templates I've created.
I'd also be interested in others best practice upgrade path.

All new keys have defaults which maintain backward compatibility behaviour wise.  @aegershman @chrisfkell.  Previous comment should help get confidence with apply command + peek
\

Hey @calebwashburn can't thank you enough for making sure that peek works well, that's how I've been testing my new pipelines. Just trying to keep parity with my configs since I'm working to use some of the new features.
From what I've done so far everything looks fine backward compatibility wise. Thanks again.

Awesome. Thank you 👍


Handle kafka backward incompatible props

Earlier we were adding shaded prefix to some stream config properties such as PlainLoginModule in jaas, so that older kafka tables work properly.
However, now we need to do the opposite as well for some other prefixes because we have made substantial changes to shading in Pinot.

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

Project coverage is 0.00%. Comparing base (59551e4) to head (6a08785).
Report is 1325 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (6a08785). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (6a08785)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
0

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14446       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
?

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


should be able to close issue #4

looks great! so it supports java, javascript, python, and html comments?

I only used those because I wanted the gif to be short. However, it
supports  literally any modern programming language comments ( including
c++)
On Thu, Jun 11, 2020 at 6:11 PM Diana<EMAIL_ADDRESS>wrote:

looks great! so it supports java, javascript, python, and html comments?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MLH-Fellowship/howdoi/pull/18#issuecomment-642956713,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE6P4DC7264NCTW5OHE6UWLRWFI7NANCNFSM4N3ZEQ7Q
.

--
Cheers!
Fawziyah


initialize best tip coinbase metric to 1

This PR initializes the best tip coinbase metric to "1" so that the alert does not fire inaccurately when a node first starts up.

!approved-for-mainnet


YAML support

Ref #47

@marcelometal thanks, just need to fix merge conflict then this is good to go

hi @kevholditch, I've fixed the conflict, thks!