text:
AudioKit playgrounds throw build errors

Watched aure's intro video on the homepage and I've tried the steps there.  I can't seem to get these to run from a repo clone as of today.  I've tried cleaning/building not sure what I'm doing wrong.
Playground execution failed: error: Introduction and Hello World.xcplaygroundpage:9:8: error: no such module 'AudioKit'
import AudioKit
^
error: Introduction and Hello World.xcplaygroundpage:10:8: error: cannot load underlying module for 'AudioKitPlaygrounds'
import AudioKitPlaygrounds
^

thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1

frame #0: 0x000000010c721360 com.apple.dt.Xcode.PlaygroundStub-macosxexecutePlayground frame #1: 0x000000010c71f22a com.apple.dt.Xcode.PlaygroundStub-macosx-[PlaygroundViewBridgeService execute] + 90
frame #2: 0x00007fffae030c3c CoreFoundation__invoking___ + 140 frame #3: 0x00007fffae030ac1 CoreFoundation-[NSInvocation invoke] + 289
frame #4: 0x00007fffae04a246 CoreFoundation-[NSInvocation invokeWithTarget:] + 54 frame #5: 0x00007fffc1920502 ViewBridge68-[NSVB_ViewServiceImplicitAnimationDecodingProxy forwardInvocation:]block_invoke + 47
frame #6: 0x00007fffc193f119 ViewBridge__runAnimationGroup_block_invoke + 21 frame #7: 0x00007fffac47d8b6 AppKit+[NSAnimationContext runAnimationGroup:] + 58
frame #8: 0x00007fffabb45fba AppKit+[NSAnimationContext runAnimationGroup:completionHandler:] + 85 frame #9: 0x00007fffc193f0f5 ViewBridgerunAnimationGroup + 303
frame #10: 0x00007fffc1920009 ViewBridge+[NSVB_View _animateWithAttributes:animations:completion:] + 507 frame #11: 0x00007fffc1920484 ViewBridge-[NSVB_ViewServiceImplicitAnimationDecodingProxy forwardInvocation:] + 156
frame #12: 0x00007fffae02f5fa CoreFoundation___forwarding___ + 538 frame #13: 0x00007fffae02f358 CoreFoundationforwarding_prep_0 + 120
frame #14: 0x00007fffae030c3c CoreFoundation__invoking___ + 140 frame #15: 0x00007fffae030ac1 CoreFoundation-[NSInvocation invoke] + 289
frame #16: 0x00007fffae04a246 CoreFoundation-[NSInvocation invokeWithTarget:] + 54 frame #17: 0x00007fffc18eebc2 ViewBridge-[NSVB_QueueingProxy forwardInvocation:] + 327
frame #18: 0x00007fffae02f5fa CoreFoundation___forwarding___ + 538 frame #19: 0x00007fffae02f358 CoreFoundationforwarding_prep_0 + 120
frame #20: 0x00007fffae030c3c CoreFoundation__invoking___ + 140 frame #21: 0x00007fffae030ac1 CoreFoundation-[NSInvocation invoke] + 289
frame #22: 0x00007fffae04a246 CoreFoundation-[NSInvocation invokeWithTarget:] + 54 frame #23: 0x00007fffae02f5fa CoreFoundationforwarding + 538
frame #24: 0x00007fffae02f358 CoreFoundation__forwarding_prep_0___ + 120 frame #25: 0x00007fffae030c3c CoreFoundationinvoking + 140
frame #26: 0x00007fffae030ac1 CoreFoundation-[NSInvocation invoke] + 289 frame #27: 0x00007fffae04a246 CoreFoundation-[NSInvocation invokeWithTarget:] + 54
frame #28: 0x00007fffae02f5fa CoreFoundation___forwarding___ + 538 frame #29: 0x00007fffae02f358 CoreFoundationforwarding_prep_0_ + 120
frame #30: 0x00007fffae030c3c CoreFoundation__invoking___ + 140 frame #31: 0x00007fffae030ac1 CoreFoundation-[NSInvocation invoke] + 289
frame #32: 0x00007fffc19436a9 ViewBridgewithHintInProgress + 487 frame #33: 0x00007fffc19433e0 ViewBridge__deferNSXPCInvocationOntoMainThread_block_invoke_2 + 233
frame #34: 0x00007fffc18c7779 ViewBridge+[NSViewServiceApplication withHostPID:invoke:] + 46 frame #35: 0x00007fffc19432a3 ViewBridge__deferNSXPCInvocationOntoMainThread_block_invoke + 179
frame #36: 0x00007fffc1942e97 ViewBridge__deferBlockOntoMainThread_block_invoke_2 + 544 frame #37: 0x00007fffae05321c CoreFoundationCFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK + 12
frame #38: 0x00007fffae034034 CoreFoundation__CFRunLoopDoBlocks + 356 frame #39: 0x00007fffae033b76 CoreFoundation__CFRunLoopRun + 1878
frame #40: 0x00007fffae0331c4 CoreFoundationCFRunLoopRunSpecific + 420 frame #41: 0x00007fffad594ebc HIToolboxRunCurrentEventLoopInMode + 240
frame #42: 0x00007fffad594cf1 HIToolboxReceiveNextEventCommon + 432 frame #43: 0x00007fffad594b26 HIToolbox_BlockUntilNextEventMatchingListInModeWithFilter + 71
frame #44: 0x00007fffabb2fe24 AppKit_DPSNextEvent + 1120 frame #45: 0x00007fffac2ab85e AppKit-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2796
frame #46: 0x00007fffc18c8948 ViewBridge-[NSViewServiceApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 100 frame #47: 0x00007fffabb247ab AppKit-[NSApplication run] + 926
frame #48: 0x00007fffabaef1de AppKitNSApplicationMain + 1237 frame #49: 0x00007fffc39ef8c7 libxpc.dylib_xpc_objc_main + 775
frame #50: 0x00007fffc39ee2e4 libxpc.dylibxpc_main + 494 frame #51: 0x00007fffc18f2fa5 ViewBridge-[NSXPCSharedListener resume] + 16
frame #52: 0x00007fffc18cd636 ViewBridgeNSViewServiceApplicationMain + 2985 frame #53: 0x000000010c7213a2 com.apple.dt.Xcode.PlaygroundStub-macosxmain + 34
frame #54: 0x00007fffc3796235 libdyld.dylib`start + 1

It's mostly likely because you cloned the repo instead of downloaded the AudioKit project directly.  To use your repo, go in to Frameworks and run ./build_frameworks.sh  and then when that's done, try the AudioKitPlayground project again.

I have the same error after running the shell script.

This is also repro'ed in the 3.6 and playground releases from the downloads page.

The video was created from the current version, so the process is up to date.  The fact that you're getting the same error from both the downloaded playground zip and the cloned repo is suspect.  Are you able to do a screenshare?  I can invite you to screenhero with an email address and name, just email me at aure at audiokit dot io.

authors: aure openloop

repo: audiokit/AudioKit


text:
Add current date

How to add current date as option?

Hi @artemnovichkov! 👋
You can insert the current date and time using jinja2-time, which comes with cookiecutter.
{% now 'utc', '%Y' %}

Check out this example.

@hackebrot, thank you! I used {% now 'local', '%d/%m/%Y' %} for similar date format.

source: gharchive/issue

authors: artemnovichkov hackebrot

repo: audreyr/cookiecutter

license_type: permissive

license_source: bigquery


text:
menu (side-nav) doesn't work in FF

The components side-nav's categories is empty in firefox.
It is built from a nested repeat.for:

          ${ cat.title }

              ${ ctrl.title }

The inner
 is empty:

      Javascript

In Chrome and IE, the content of the inner repeat.for is injected where  is displayed, as expected.

The issue seems to be with: if.bind="!!ctrl.link".
When deleting that part, it works in FF.

Confirmed..
Here's a plunk: http://plnkr.co/edit/CM3oX9r7g3gJGp3hePIQ?p=preview
The result in Chrome:

The result in FF:

It's not an Aurelia problem.
https://github.com/aurelia/templating-resources/issues/111#issuecomment-171031562
Basically

You can't place two TemplateControllers on the same element. In this case if and repeat. They are both trying to control the creation of the th. It works in Chrome...accidentally...somehow.

license: mit


text:
Dialog open in activate does not work on first load with router.

I'm submitting a bug report

Library Version:
1.0.0-beta.3.0.1

Please tell us about your environment:

Operating System:
Linux fedora 23

Node Version:
6.2.2

NPM Version:
3.9.5

JSPM OR Webpack AND Version
webpack 2.1.0-beta.22

Browser:
Chrome 53

Language:
TypeScript 2.0.0

Current behavior:
I am calling this.dialogService.open from an activate method.
When I first go to the page or refresh the page so the constructor is called the dialog open does not result in the dialog being displayed.
However, if I click on another entry in the top level menu provided by the router and then naviagate back to the original page the dialog displays fine. In ther later case the constructor is not called.
The only difference I can is is hasActiveDialog is true when the dialog displays but false when it does not work at the point open is called.
Expected/desired behavior:

Can't create a gistrun with aurelia-dialog so have made a repository at
https://github.com/glennpierce/test/tree/master/src
Go to any page and do a refresh and the dialog fails to display. Clinking between toplevel menu items will display the doalog.

What is the expected behavior?

The dialog should display of first load.

What is the motivation / use case for changing the behavior?

To display a dialog :)

I'll have time to check it as early as tomorrow. If you want you can chain a .catch to the .open method and see the error, if any.

Not sure if I'm doing anything wrong but I can't get a catch handler to trigger.

@glennpierce It's strange that the catch doesn't work. Also I'm not much into webpack, but in the webpack.config.js I don't see anything about the dialog, is it normal? I'll first try it on the sample app first

So I tried it with the skeleton-navigation/skeleton-esnext and it worked. When I try to run your sample I get TypeError: webpack.validateSchema is not a function after running npm start.

I just used npm install aurelia-dialog --save like in the install instructions.
Don't think I needed to edit webpack.config.js
I have updated the source to solve the validateSchema error.
I had to use a different version of webpack
ie

"webpack": "2.1.0-beta.22",
"webpack-dev-server": ">=2.1.0-beta.0 || ^2.1.0"

"webpack": "^2.1.0-beta.22",
"webpack-dev-server": "^1.16.2"

Ok, so I manged to run it and got Unhandled rejection Error: Cannot find module './77.html'.. Check #231 and #213. I'll look though where the promise chain breaks and the rejection is not propagated to the .open() method.

If it helps stepping through the code slowly the dialog does display when returning the promise from the showDialog function but then something closes it. However, I can't seem to capture what does that.

@glennpierce Found it, sorry for the delay. Using this webpack setup threw me off. The problem is that the modal container is put in the body, also aurelia-app="main" is put on the body, so when navigation completes(after activate settles), the content of the body is replaced. You can try to add a div and put aurelia-app="main" on it. Then the dialog will be visible after the navigation completes.

No worries about the delay. Thanks a lot for helping.
I did your suggestion of putting aurelia-app="main" in a div and it works great. It may be worth added a note in the docs as I would think it may be a common mistake.
Again thanks for the help.

@glennpierce @StrahilKazlachev Is this an issue with the dialog that needs a note or with WebPack?

@PWKad I would say neither, it's just how Aurelia works. But it doesn't hurt to add note.

Gotcha, sounded specific to WebPack (presumably the plugin is loaded before the app is replaced?) but if it is cross-loaders than I think we can add a quick note.

@StrahilKazlachev so I'm moving the discussion about webpack + dialog startup here.
I think that the <body> think is a gotcha and not a great experience for users. It also happens that you don't want a <div> at the root (happened to me before).
The cause here is that Webpack resolves everything very quickly and synchronously. This can result in a different execution sequence from what you might have been used to with AMD (or others).
I can offer you two suggestions to remedy the situation.

@niieani encountered similar issue with tests failing with Webpack at first.
We fixed the Aurelia booting sequence (there were unobserved Promises...) and exposed a Promise to reflect the boot status (there was an event but if you haven't subscribed when it fires then it's useless).

Now you can easily and reliably execute code after Aurelia has started by using the starting Promise exported by aurelia-bootstrapper. It resolves when all Aurelia application on the page have started.
import { starting } from "aurelia-bootstrapper";
starting.then(() => {
  // Do stuff you need to do when Aurelia has started
});

It would be even better if you did not modify the DOM at startup.
I am not sure what you insert in DOM at first, I suspect a backdrop <div>?
In my own dialog library, we insert and remove the backgroup (and the rest) each time a dialog is shown/hidden.
Lazily modifying the DOM has several advantages:

faster startup
smaller DOM at runtime
less interferences with other code

@jods4 I think there is some misunderstanding, I'll try to explain what happens.

the dialog does no DOM modifications at startup
the dialog modifies the DOM only when a dialog is being open, when it is being attached to the DOM tree(for now)
starting is too early
the issue comes from Aurelia replacing the content of the aurelia-app marked element

this issue was about opening a dialog in the .activate hook of the route VM on first app load

the dialog gets open(placed in the body) during the navigation
when the navigation completes the content of the aurelia-app(body) element gets replaced, but the dialog is already in the body, so it gets removed

I still think this is not Webpack specific.

will address it in the docs

I'm only not sure why the contents of app.html are not rendered before/while navigating(the route content do go in the router-view), hence replacing the aurelia-app content early on.

authors: PWKad StrahilKazlachev glennpierce jods4

repo: aurelia/dialog


text:
http-client 0.10.2 missing index.js file: causing undefined error on import

When I try to import the http-client in code, with version 0.10.2, I get an error saying that the HttpClient is undefined. I believe this is because the index.js file is missing from the src directory. Can someone help to confirm this? I want to see if others are running into the same issue before I issue a pull request for this.

Try updating to the latest. We did releases last night and we know we had an issue with http client, so we fixed it then. The community member was then able to use it successfully.

Still having trouble. I did the following:
Jedds-MBP:kali-web jahyoung$ jspm uninstall aurelia-http-client
Clearing configuration for github:aurelia/http-client@0.10.2
Clearing configuration for github:aurelia/http-client@0.9.1
Removing package files for github:aurelia/http-client@0.10.2
Removing package files for github:aurelia/http-client@0.9.1
Removing package files for github:aurelia/path@0.7.0
ok   Uninstall complete.

Jedds-MBP:kali-web jahyoung$
Jedds-MBP:kali-web jahyoung$ jspm install aurelia-http-client
     Updating registry cache...
     Looking up github:aurelia/http-client
     Looking up npm:core-js
     Looking up github:aurelia/path

warn core-js is installed in the config file, but is not a dependency in the package.json. It is advisable to add it to the package.json file.
     Looking up github:systemjs/plugin-json
     Looking up github:jspm/nodelibs-fs
     Looking up github:jspm/nodelibs-process
     Looking up npm:process
ok   Installed aurelia-http-client as github:aurelia/http-client@^0.10.2 (0.10.2)
     Installed Forks

                        github:aurelia/path 0.6.1 0.8.1
              github:pwkad/aurelia-bs-modal master 0.2.1
                             npm:babel-core 5.2.2 5.8.14
                                  npm:bn.js 2.2.0 3.1.1
                                npm:process 0.10.1 0.11.1

     To inspect individual package constraints, use jspm inspect endpoint:name.

ok   Install complete.

And I'm getting the following error:
Error: Error instantiating AuthenticationService.
------------------------------------------------
inner error: Error: key cannot be null or undefined.
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:117:19)
    at Container.invoke (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:195:30)
    at Array.<anonymous> (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:78:48)
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:141:26)
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:135:32)
    at Container.invoke (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:195:30)
    at Array.<anonymous> (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:78:48)
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:131:28)
    at http://localhost:9000/jspm_packages/github/aurelia/templating@0.11.2/composition-engine.js:108:79
    at run (http://localhost:9000/jspm_packages/npm/core-js@0.9.18/modules/es6.promise.js:91:43)
------------------------------------------------
inner error: Error: key cannot be null or undefined.
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:117:19)
    at Container.invoke (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:195:30)
    at Array.<anonymous> (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:78:48)
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:141:26)
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:135:32)
    at Container.invoke (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:195:30)
    at Array.<anonymous> (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:78:48)
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:131:28)
    at http://localhost:9000/jspm_packages/github/aurelia/templating@0.11.2/composition-engine.js:108:79
    at run (http://localhost:9000/jspm_packages/npm/core-js@0.9.18/modules/es6.promise.js:91:43)
    at AggregateError (http://localhost:9000/jspm_packages/github/aurelia/logging@0.4.0/index.js:24:15)
    at Container.invoke (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:200:19)
    at Array.<anonymous> (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:78:48)
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:141:26)
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:135:32)
    at Container.invoke (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:195:30)
    at Array.<anonymous> (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:78:48)
    at Container.get (http://localhost:9000/jspm_packages/github/aurelia/dependency-injection@0.7.1/container.js:131:28)
    at http://localhost:9000/jspm_packages/github/aurelia/templating@0.11.2/composition-engine.js:108:79
    at run (http://localhost:9000/jspm_packages/npm/core-js@0.9.18/modules/es6.promise.js:91:43)

When I console.log HttpClient (the import), I get "undefined". If I roll back to 0.9.1 I don't run into this error.

Try updating all your aurelia deps with an install command. You've got old versions of things lying around. I can see it in the error log. There may be something going wrong there.

Tried an install and then an update. From what I'm reading, JSPM update may only update within the semver range, which may be my problem; I started this project using a copy of the contacts-app.
Installed Versions
                     github:aurelia/binding 0.6.1
                github:aurelia/bootstrapper 0.12.0
        github:aurelia/dependency-injection 0.7.1
            github:aurelia/event-aggregator 0.4.0
                   github:aurelia/framework 0.11.0
                     github:aurelia/history 0.4.0
             github:aurelia/history-browser 0.4.0
       github:aurelia/html-template-element 0.2.0
                 github:aurelia/http-client 0.10.2
                      github:aurelia/loader 0.6.0
              github:aurelia/loader-default 0.7.0
                     github:aurelia/logging 0.4.0
             github:aurelia/logging-console 0.4.0
                    github:aurelia/metadata 0.5.0
                        github:aurelia/path 0.6.1 0.8.1
            github:aurelia/route-recognizer 0.4.0
                      github:aurelia/router 0.8.1
                  github:aurelia/task-queue 0.4.0
                  github:aurelia/templating 0.11.2
          github:aurelia/templating-binding 0.11.0
        github:aurelia/templating-resources 0.11.1
           github:aurelia/templating-router 0.12.0
                   github:components/jquery 2.1.4
                github:jspm/nodelibs-assert 0.1.0
                github:jspm/nodelibs-buffer 0.1.0
         github:jspm/nodelibs-child_process 0.1.0
             github:jspm/nodelibs-constants 0.1.0
                github:jspm/nodelibs-crypto 0.1.0
                github:jspm/nodelibs-events 0.1.1
                    github:jspm/nodelibs-fs 0.1.2
                  github:jspm/nodelibs-http 1.7.1
                github:jspm/nodelibs-module 0.1.0
                   github:jspm/nodelibs-net 0.1.2
                  github:jspm/nodelibs-path 0.1.0
               github:jspm/nodelibs-process 0.1.1
                github:jspm/nodelibs-stream 0.1.0
        github:jspm/nodelibs-string_decoder 0.1.0
                github:jspm/nodelibs-timers 0.1.0
                   github:jspm/nodelibs-tty 0.1.0
                   github:jspm/nodelibs-url 0.1.0
                  github:jspm/nodelibs-util 0.1.0
                    github:jspm/nodelibs-vm 0.1.0
              github:pwkad/aurelia-bs-modal master 0.2.1
                  github:rstacruz/nprogress 0.1.6
                 github:systemjs/plugin-css 0.1.13
                github:systemjs/plugin-json 0.1.0
                      github:twbs/bootstrap 3.3.5
       github:webcomponents/webcomponentsjs 0.6.3
                                 npm:Base64 0.2.1
                                npm:asn1.js 2.1.3
                                 npm:assert 1.3.0
                             npm:babel-core 5.2.2 5.8.19
                          npm:babel-runtime 5.2.2
                              npm:base64-js 0.0.8
                                  npm:bn.js 2.2.0 3.1.1
                                npm:brorand 1.0.5
                         npm:browserify-aes 1.0.2
                         npm:browserify-rsa 2.0.1
                        npm:browserify-sign 3.0.2
                                 npm:buffer 3.3.1
                             npm:buffer-xor 1.0.2
                   npm:constants-browserify 0.0.1
                                npm:core-js 0.9.18
                           npm:core-util-is 1.0.1
                            npm:create-ecdh 2.0.1
                            npm:create-hash 1.1.1
                            npm:create-hmac 1.1.3
                      npm:crypto-browserify 3.9.14
                         npm:diffie-hellman 3.0.2
                               npm:elliptic 3.1.0
                                 npm:events 1.0.2
                           npm:font-awesome 4.4.0
                                npm:hash.js 1.0.3
                                npm:ieee754 1.1.6
                                npm:indexof 0.0.1
                               npm:inherits 2.0.1
                               npm:is-array 1.0.1
                                npm:isarray 0.0.1
                           npm:miller-rabin 2.1.0
                    npm:minimalistic-assert 1.0.0
                             npm:parse-asn1 3.0.1
                        npm:path-browserify 0.0.0
                                 npm:pbkdf2 3.0.4
                                npm:process 0.10.1 0.11.1
                         npm:public-encrypt 2.0.1
                               npm:punycode 1.3.2
                            npm:querystring 0.2.0
                            npm:randombytes 2.0.1
                        npm:readable-stream 1.1.13
                              npm:ripemd160 1.0.1
                                 npm:sha.js 2.4.2
                      npm:stream-browserify 1.0.0
                         npm:string_decoder 0.10.31
                      npm:timers-browserify 1.4.1
                         npm:tty-browserify 0.0.0
                                    npm:url 0.10.3
                                   npm:util 0.10.3
                          npm:vm-browserify 0.0.4

     To inspect individual package constraints, use jspm inspect endpoint:name.

Yes, because in a pre 1.0 version, changes to the minor version are considered breaking changes, therefor jspm will not update those unless you specifically re-install them. This will get much simpler after we go 1.0 where the changes for a long period of time will be just minor and path -  non breaking.
Yep, your Aurelia stuff is way out of date. Here's a quick script that should update all of it:
jspm install aurelia-animator-css aurelia-binding aurelia-bootstrapper aurelia-dependency-injection aurelia-framework aurelia-http-client aurelia-router aurelia-event-aggregator aurelia-history-browser aurelia-loader-default aurelia-loader aurelia-metadata aurelia-route-recognizer aurelia-templating-binding aurelia-templating-resources aurelia-templating-router aurelia-templating aurelia-logging aurelia-task-queue aurelia-history aurelia-path

authors: EisenbergEffect jedd-ahyoung

repo: aurelia/http-client


text:
fix(ci): update deps, jspm deps, test deps, ci

@EisenbergEffect @fkleuver

@bigopon Could you resolve you conflict? New PR's are blocked by a failing build due to incorrect CircleCI config.

Merged changes into #368 and resolved package-lock conflict. @EisenbergEffect @fkleuver

source: gharchive/pull-request

repo: aurelia/templating-resources


text:
instructions to build/run sample are incorrect

The readme indicates you should simply need to cd sample && npm install && jspm install && gulp start, however there are no gulp tasks in that directory

https://github.com/aurelia/validatejs/blob/master/build/tasks/watch.js#L15 <~~~ serves the sample app up - and gulp should find it properly.  Just double-checked and it looked good for me so you would need to let me know what is not working and I can look at it.

@PWKad Two issues here:

There is no build task for start as indicated in the README

Instead of checking visually, please just try to follow the instructions in the README itself - they do not work:

first of all, "running the sample" requires (presumably) that you have run npm install on the top level directory. If you do a raw clone and just follow the "Running the sample" instructions you will result in the following error:  Local gulp not found in ~/Development/aurelia/validatejs

secondly, once you get the top level node modules installed, there is no gulp task for start. Presumably the suggested task is watch but the watch task defined in the top level build directory is for building a plugin - not the sample app. So a gulp watch from the sample directory results in this:

mbroadst@retinoid:sample (master=)$ gulp watch
[09:33:34] Working directory changed to ~/Development/aurelia/validatejs
[09:33:35] Using gulpfile ~/Development/aurelia/validatejs/gulpfile.js
[09:33:35] Starting 'build'...
[09:33:35] Starting 'clean'...
[09:33:35] Finished 'clean' after 43 ms
[09:33:35] Starting 'build-es2015'...
[09:33:35] Starting 'build-commonjs'...
[09:33:35] Starting 'build-amd'...
[09:33:35] Starting 'build-system'...
[09:33:38] Finished 'build-amd' after 2.7 s
[09:33:38] Finished 'build-commonjs' after 2.7 s
[09:33:38] Finished 'build-es2015' after 2.71 s
[09:33:38] Finished 'build-system' after 2.7 s
[09:33:38] Finished 'build' after 2.76 s
[09:33:38] Starting 'serve'...
[BS] Access URLs:
 --------------------------------------
       Local: http://localhost:3001
    External: http://192.168.11.55:3001
 --------------------------------------
          UI: http://localhost:3002
 UI External: http://192.168.11.55:3002
 --------------------------------------
[BS] Serving files from: sample
[09:33:38] Finished 'serve' after 150 ms
[09:33:38] Starting 'watch'...
[09:33:38] Finished 'watch' after 128 ms

Which has then just built your sample app in amd/commonjs/requirejs/etc and not loading your app where you think you're loading it.
So I guess I just think the issue should be reopened because there is no current way to run this app. I think the sample folder needs (at very least) its own gulpfile and set of build tasks.
HTH

https://github.com/aurelia/validatejs/commit/c77f3693587a607393e73a90f01f5c39f53084f6 <~~
I'll add a note to run build-sample as well, thanks for helping to point this out.

There was a problem with JSPM trying to incorrectly load one of the package paths that only exists in this scenario, not in a real app, that was fixed in there as well.

Alright readme updated with working instructions.

Not working for me on master as of 5 minutes ago:
git clone https://github.com/aurelia/validatejs.git
cd validatejs
npm install
cd sample
npm install
jspm install
gulp build-sample
gulp watch

Then http://localhost:3000/
Uncaught (in promise) Error: Error: XHR error (404 Not Found) loading http://localhost:3000/jspm_packages/npm/aurelia-validation@0.8.0.js
    Error loading http://localhost:3000/jspm_packages/npm/aurelia-validation@0.8.0.js as
"aurelia-validation" from http://localhost:3000/aurelia-validatejs/index.js

authors: PWKad aivins mbroadst

repo: aurelia/validatejs


text:
Make Pausable use Acl for authorization

Previously the Pausable plugin required a contract to be Ownable to manage authorization of (un)pausing features and to define exemptions via except. This PR makes Pausable use AccessControllable instead of Ownable.
Overview

Developers specify which Acl role(s) can pause and unpause features.
When using except with #[pause] or #[if_paused], developers can specify Acl role(s) which are exempted.

Examples
Files in examples/pausable-examples/ have not been updated, for now. I'd propose to remove the contracts there and instead add a test contract in /near-plugins/tests/contracts/pausable, see #48.
I suggest we first decide if this is a reasonable approach before updating examples.

As discussed offline, merging now without modifying examples/pausable-examples. In a follow up PR I'll deduplicate and update examples and tests as described in #48.

repo: aurora-is-near/near-plugins

license_source: github-api


text:
Custom fields not shown on record details

I have configured a custom field on Netbox-DNS record objects: it works ok when editing and listing/filtering records... but the custom field is not shown on the detail view of single record!
FYI I have created such a custom field in order to associate records with internal ticket requests... but a generic "Description" field as requested in #206 would be useful as well 😄
Regards.

Records have a very specific custom template, and it may well be that I missed custom fields when I created it. I will look at it as soon as possible.
As for descriptions, PR #207 already added them (not merged to main yet, but it should work fine). Status is still in the queue, though.

Should be fine with PR #209 ... just a very trivial change.

Thanks. Do you know when is the fix expected to be merged and released?

authors: fabricat peteeckel

repo: auroraresearchlab/netbox-dns

license: MIT


text:
Tests failing in current main branch

While testing the changes for PR #35, I noticed that some of the tests for netbox_dns fail:
(netbox) [root@dns netbox-dns]# /opt/netbox/netbox/manage.py test netbox_dns
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
......................................F....F......................F....F......................F....F....
======================================================================
FAIL: test_get_object_anonymous (netbox_dns.tests.test_views.NameServerTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/netbox/lib/python3.8/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
  File "/opt/netbox/netbox/utilities/testing/views.py", line 62, in test_get_object_anonymous
    self.assertHttpStatus(response, 200)
  File "/opt/netbox/netbox/utilities/testing/base.py", line 68, in assertHttpStatus
    self.assertEqual(response.status_code, expected_status, err_message)
AssertionError: 302 != 200 : Expected HTTP status 200; received 302: No data

======================================================================
FAIL: test_list_objects_anonymous (netbox_dns.tests.test_views.NameServerTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/netbox/lib/python3.8/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
  File "/opt/netbox/netbox/utilities/testing/views.py", line 401, in test_list_objects_anonymous
    self.assertHttpStatus(response, 200)
  File "/opt/netbox/netbox/utilities/testing/base.py", line 68, in assertHttpStatus
    self.assertEqual(response.status_code, expected_status, err_message)
AssertionError: 302 != 200 : Expected HTTP status 200; received 302: No data

======================================================================
FAIL: test_get_object_anonymous (netbox_dns.tests.test_views.RecordTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/netbox/lib/python3.8/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
  File "/opt/netbox/netbox/utilities/testing/views.py", line 62, in test_get_object_anonymous
    self.assertHttpStatus(response, 200)
  File "/opt/netbox/netbox/utilities/testing/base.py", line 68, in assertHttpStatus
    self.assertEqual(response.status_code, expected_status, err_message)
AssertionError: 302 != 200 : Expected HTTP status 200; received 302: No data

======================================================================
FAIL: test_list_objects_anonymous (netbox_dns.tests.test_views.RecordTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/netbox/lib/python3.8/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
  File "/opt/netbox/netbox/utilities/testing/views.py", line 401, in test_list_objects_anonymous
    self.assertHttpStatus(response, 200)
  File "/opt/netbox/netbox/utilities/testing/base.py", line 68, in assertHttpStatus
    self.assertEqual(response.status_code, expected_status, err_message)
AssertionError: 302 != 200 : Expected HTTP status 200; received 302: No data

======================================================================
FAIL: test_get_object_anonymous (netbox_dns.tests.test_views.ZoneTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/netbox/lib/python3.8/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
  File "/opt/netbox/netbox/utilities/testing/views.py", line 62, in test_get_object_anonymous
    self.assertHttpStatus(response, 200)
  File "/opt/netbox/netbox/utilities/testing/base.py", line 68, in assertHttpStatus
    self.assertEqual(response.status_code, expected_status, err_message)
AssertionError: 302 != 200 : Expected HTTP status 200; received 302: No data

======================================================================
FAIL: test_list_objects_anonymous (netbox_dns.tests.test_views.ZoneTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/netbox/lib/python3.8/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
  File "/opt/netbox/netbox/utilities/testing/views.py", line 401, in test_list_objects_anonymous
    self.assertHttpStatus(response, 200)
  File "/opt/netbox/netbox/utilities/testing/base.py", line 68, in assertHttpStatus
    self.assertEqual(response.status_code, expected_status, err_message)
AssertionError: 302 != 200 : Expected HTTP status 200; received 302: No data

----------------------------------------------------------------------
Ran 104 tests in 5.102s

FAILED (failures=6)
Destroying test database for alias 'default'...

Unfortunately, it took me a while to find out that this was not due to my changes, but the tests also fail for the current main branch in exactly the same way.
This seems to be because the Netbox ViewTestCases "GetObjectViewTestCase" and "ListObjectsViewTestCase" fail for anonymous access, possibly because the views return an HTTP response code 302 instead of 200 in this case. I haven't dug any deeper yet, but will investigate when I find the time.

Interesting question ... I get exactly the same results when I run the full test suite against netbox (currently on version 3.0.7) itself. So it doesn't seem to be an issue with netbox-dns after all.
I also noticed that tests are not failing in the CI in Github. So there must be something done differently from just running manage.py test. But what?
======================================================================
FAIL: test_get_object_anonymous (circuits.tests.test_views.CircuitTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/netbox/lib/python3.8/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
  File "/vagrant/netbox/utilities/testing/views.py", line 68, in test_get_object_anonymous
    self.assertHttpStatus(response, 200)
  File "/vagrant/netbox/utilities/testing/base.py", line 68, in assertHttpStatus
    self.assertEqual(response.status_code, expected_status, err_message)
AssertionError: 302 != 200 : Expected HTTP status 200; received 302: No data

======================================================================
FAIL: test_list_objects_anonymous (circuits.tests.test_views.CircuitTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/netbox/lib/python3.8/site-packages/django/test/utils.py", line 387, in inner
    return func(*args, **kwargs)
  File "/vagrant/netbox/utilities/testing/views.py", line 407, in test_list_objects_anonymous
    self.assertHttpStatus(response, 200)
  File "/vagrant/netbox/utilities/testing/base.py", line 68, in assertHttpStatus
    self.assertEqual(response.status_code, expected_status, err_message)
AssertionError: 302 != 200 : Expected HTTP status 200; received 302: No data

I just opened an issue in netbox-community/netbox for this.
https://github.com/netbox-community/netbox/issues/7747


text:
SyntaxError: Unexpected token <

Hi @chenkie
Trying to use angular2-jwt and received a Unexpected token error.
My boot.ts
///<reference path="../node_modules/angular2/typings/browser.d.ts"/>
import {bootstrap} from 'angular2/platform/browser';
import {ROUTER_PROVIDERS} from 'angular2/router';
import {AppComponent} from './app.component';
import { Http, HTTP_PROVIDERS } from 'angular2/http';
import {provide} from 'angular2/core';
import { AuthConfig, AuthHttp} from 'angular2-jwt';

bootstrap(AppComponent, [
    ROUTER_PROVIDERS,
    HTTP_PROVIDERS,
    provide(AuthHttp, {
        useFactory: (http) => {
            return new AuthHttp(new AuthConfig({
                tokenName: 'jwt'
            }), http);
        },
        deps: [Http]
    })
]);

index.html

    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>My Website</title>
    <link rel="icon" href="assets/images/favicon.ico">

    <link href="css/bootstrap.css" rel="stylesheet" />
    <link href="css/styles.min.css" rel="stylesheet" />

    <link href='https://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,400italic,600,600italic' rel='stylesheet' type='text/css'>
    <base href="/" />

    <my-app>

Loading...</my-app>

my gulpfile.js (portion)
gulp.task('moveToLibs', function (done) {
    gulp.src([
      'node_modules/angular2/bundles/js',
      'node_modules/angular2/bundles/angular2.*.js*',
      'node_modules/angular2/bundles/angular2-polyfills.js',
      'node_modules/angular2/bundles/http.*.js*',
      'node_modules/angular2/bundles/router.*.js*',
      'node_modules/angular2-jwt/angular2-jwt.js*',
      'node_modules/es6-shim/es6-shim.min.js*',
      'node_modules/angular2/es6/dev/src/testing/shims_for_IE.js',
      'node_modules/systemjs/dist/*.*',
      'node_modules/jquery/dist/jquery.*js',
      'node_modules/bootstrap/dist/js/bootstrap*.js',
      'node_modules/ang-google-maps/index.js',
      'node_modules/rxjs/bundles/Rx.js',
      'node_modules/ng2-translate/bundles/ng2-translate.js',
      'node_modules/ng2-translate/src/translate.parser.js',
      'node_modules/ng2-translate/src/translate.pipe.js',
      'node_modules/ng2-translate/src/translate.service.js'
    ]).pipe(gulp.dest('./wwwroot/libs/'));

    gulp.src([
       'node_modules/rxjs/**/*.js'
    ]).pipe(gulp.dest('./wwwroot/libs/rxjs'));

    gulp.src([
      'node_modules/bootstrap/dist/css/bootstrap.css',
      'node_modules/components-font-awesome/css/font-awesome.css',
    ]).pipe(gulp.dest('./wwwroot/css'));

    gulp.src([
        'scripts/*.css',
        'scripts/*/*.css',
    ])
    // Combine all CSS files found inside the src directory
    .pipe(concatenate('styles.min.css'))
    // Minify the stylesheet
    .pipe(minify())
    // Report the task-execution time in the command line
    .pipe(duration('Execution Time: '))
    // Write the minified file in the css directory
    .pipe(gulp.dest('./wwwroot/css'));

    gulp.src([
        'node_modules/bootstrap/fonts/glyphicons-halflings-regular.eot',
        'node_modules/bootstrap/fonts/glyphicons-halflings-regular.svg',
        'node_modules/bootstrap/fonts/glyphicons-halflings-regular.ttf',
        'node_modules/bootstrap/fonts/glyphicons-halflings-regular.woff',
        'node_modules/bootstrap/fonts/glyphicons-halflings-regular.woff2',
        'node_modules/components-font-awesome/fonts/FontAwesome.otf',
        'node_modules/components-font-awesome/fonts/fontawesome-webfont.eot',
        'node_modules/components-font-awesome/fonts/fontawesome-webfont.svg',
        'node_modules/components-font-awesome/fonts/fontawesome-webfont.ttf',
        'node_modules/components-font-awesome/fonts/fontawesome-webfont.woff',
        'node_modules/components-font-awesome/fonts/fontawesome-webfont.woff2',
    ]).pipe(gulp.dest('./wwwroot/fonts'));

    gulp.src([
        'scripts/*/*/*.html',
        'scripts/*/*.html',
        'scripts/*.html'
    ]).pipe(gulp.dest('./wwwroot/app'));

});

The error that I'm getting:
SyntaxError: Unexpected token <                                                 angular2-polyfills.js:390
	Evaluating http://localhost:49142/angular2/platform/browser.js
	Evaluating http://localhost:49142/app/boot.js
	Error loading http://localhost:49142/app/boot.js
    at SystemJSLoader.__exec (http://localhost:49142/libs/system.src.js:1395:16)
    at entry.execute (http://localhost:49142/libs/system.src.js:3521:16)
    at linkDynamicModule (http://localhost:49142/libs/system.src.js:3126:32)
    at getModule (http://localhost:49142/libs/system.src.js:3094:9)
    at http://localhost:49142/libs/system.src.js:3130:16
    at require (http://localhost:49142/libs/system.src.js:3740:29)
    at Object.eval (http://localhost:49142/app/boot.js:2:17)
    at eval (http://localhost:49142/app/boot.js:25:4)
    at SystemJSLoader.__exec (http://localhost:49142/libs/system.src.js:1395:16)
    at entry.execute (http://localhost:49142/libs/system.src.js:3767:18)

I've tried various things such as

changing the "angular2-jwt" path in boot.ts
import { AuthConfig, AuthHttp} from 'angular2-jwt/angular2-jwt';

Received a similar error:
SyntaxError: Unexpected token <                                         angular2-polyfills.js:390
	Evaluating http://localhost:49142/angular2-jwt
	Evaluating http://localhost:49142/app/boot.js
	Error loading http://localhost:49142/app/boot.js
    at SystemJSLoader.__exec (http://localhost:49142/libs/system.src.js:1395:16)
    at entry.execute (http://localhost:49142/libs/system.src.js:3521:16)
    at linkDynamicModule (http://localhost:49142/libs/system.src.js:3126:32)
    at getModule (http://localhost:49142/libs/system.src.js:3094:9)
    at http://localhost:49142/libs/system.src.js:3130:16
    at require (http://localhost:49142/libs/system.src.js:3740:29)
    at Object.eval (http://localhost:49142/app/boot.js:8:22)
    at eval (http://localhost:49142/app/boot.js:25:4)
    at SystemJSLoader.__exec (http://localhost:49142/libs/system.src.js:1395:16)
    at entry.execute (http://localhost:49142/libs/system.src.js:3767:18)

I also tried to modify the map config to:

map: {
                    "es6-shim": "node_modules/es6-shim",
                    "angular2-jwt": "node_modules/angular2-jwt/angular2-jwt.js"
                },

Also tried both system.src.js and system.js reference the

and

Note: I made sure that cleared the cached images & files in Chrome.  I'm using Gulp to move my the 3rd party js libraries, fonts, css via Gulp.  I'm using VS 2015.
Any other things i should try to get it to work?

sorry i submitted this at the wrong place.


text:
Any way to create or list database connections from the CLI?

Describe the problem you'd like to have solved
It seems I should be able to create a new database connection from CLI. Maybe I am missing details in the documentation?
Describe the ideal solution
auth0 dbconnection create
auth0 dbconnection list
auth0 dbconnection delete
Alternatives and current work-arounds
na
Additional context
na

Hi @stephan-erickson, thanks for raising this. The Auth0 CLI does not currently support database connection CRUD.

Just wanted to come and give this issue a bump for visibility. Adding this feature to the CLI would be very helpful!
Would a PR from the community implementing this feature be accepted?

cc @sergiughf ^

Hey @mstallmo, @stephan-erickson, appreciate you folks raising visibility around this. We don't currently plan on adding this feature to the cli right now, but contributions are more than welcome. We'll review them together and collaborate on getting them to the finish line:) so please feel free to give it a try.

Hey folks 👋🏻 ,
We recently added a new command 🧰 auth0 api <method> <url-path> [flags] that is able to make authenticated requests against the management API (https://auth0.com/docs/api/management/v2).
:octocat: This command is available with https://github.com/auth0/auth0-cli/releases/tag/v0.13.0.
📖 Docs for this command: https://auth0.github.io/auth0-cli/auth0_api.html
Although it doesn't offer first class support for managing database connections, you could use it as an alternative to manage database connections through the cli until we have a more dedicated command for them.
For example to create a database connection: auth0 api post connections  --data "{\"strategy\":\"auth0\", etc...}"
Feedback is much appreciate for this new command 🙏🏻 Let us know if you encounter any issues with it.
We'll keep this issue open however until we are able to add a dedicated first class command to manage db connections.
Thanks for your patience! ❤

authors: Widcket mstallmo sergiughf sergiught stephan-erickson


text:
performance tuning

This pull request improves the speed of the JWT implementation.
The apache commons-codec base64 is replaced by the jdk base64 implementation and the jackson JSON processing by the boon JSON processing. There are only minimal changes of the code (Map instead of JsonNode,…). JDK1.8 is required!
There is benchmark to compare the performance of base64, JSON and JWT coding and a test to check the compatibility of the new implementation. Gradle was only added to support the separation of the compatibility/benchmark code from the core in src/main/java. maven still works.
Everything under src/jmh, src/legacy and all gradle stuff may be deleted after the pull request is realized and the code changes are checked and validated.
Execute
git clone https://github.com/sibay/java-jwt.git
cd java-jwt/
git checkout perf-tuning
./gradlew compatibilityTest jmh

to start benchmark and compatibility test.
Some results (13'' MacBook Pro late 2011, 8 GB RAM):
Benchmark                                      Mode  Samples        Score        Error  Units
c.a.j.b.Base64Benchmark.roundtripApache       thrpt        5   408846,548 ± 117238,928  ops/s
c.a.j.b.Base64Benchmark.roundtripJdk          thrpt        5  1044641,820 ±  96118,064  ops/s
c.a.j.b.Base64Benchmark.roundtripUrlApache    thrpt        5   474469,542 ±  38925,918  ops/s
c.a.j.b.Base64Benchmark.roundtripUrlJdk       thrpt        5  1089964,163 ± 152541,130  ops/s
c.a.j.b.JsonBenchmark.boonMapToString         thrpt        5  1181898,791 ± 126738,815  ops/s
c.a.j.b.JsonBenchmark.boonStringToMap         thrpt        5   863035,316 ±  83484,058  ops/s
c.a.j.b.JsonBenchmark.jacksonMapToString      thrpt        5  1043453,914 ±  52579,598  ops/s
c.a.j.b.JsonBenchmark.jacksonStringToMap      thrpt        5   479966,758 ±  34300,377  ops/s
c.a.j.b.JwtBenchmark.roundtripNew             thrpt        5    38194,193 ±   2768,742  ops/s
c.a.j.b.JwtBenchmark.roundtripOld             thrpt        5     7499,823 ±  11935,364  ops/s
c.a.j.b.JwtBenchmark.signNew                  thrpt        5    81092,272 ±   1753,141  ops/s
c.a.j.b.JwtBenchmark.signOld                  thrpt        5    21568,942 ±  22657,818  ops/s
c.a.j.b.JwtBenchmark.signerReuseNew           thrpt        5   125545,807 ±  17323,092  ops/s
c.a.j.b.JwtBenchmark.signerReuseOld           thrpt        5    21542,093 ±  20246,830  ops/s
c.a.j.b.JwtBenchmark.verifyNew                thrpt        5    77811,134 ±  49528,543  ops/s
c.a.j.b.JwtBenchmark.verifyOld                thrpt        5    15288,083 ±  17814,746  ops/s

Any reason for closing the pr?

@sibay - we shall not be restricting the library to Java 1.8+ and we are not going to maintain multiple concurrent instances of the library. Really value your input, and it may influence our thinking when we (re-)write the library in a future major release - but this PR will not be merged, and has been open for almost 1 year now. Thank you again for the good quality input.

@arcseldon - thanks for the info. I expected that jdk8 is the stopper.
I have to thank you for the good JWT library.

authors: arcseldon sibay


text:
🛑 Andreas Iten is down

In bbf31ce, Andreas Iten (https://www.andreasiten.ch) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Andreas Iten is back up in 5b2e594.

repo: authentiqdigital/upptime


text:
introduces new merge behavior for claims

In order to allow "refresh userinfo data on demand" #877 merging claims must be adapted in way way that we can do it multiple times.
Changing the type of string to array by default (to preserve the previous different value) seems not a good idea. In case this is needed by some authz servers, we could add a special settings to have this behavior back (see #881#issuecomment-1425834324). mergeClaimsStrategy=["replace", "append"]

@Badisi I will take the code from @marcoreni without the legacy fallback as a starting point for v3. See https://github.com/authts/oidc-client-ts/pull/881/files#diff-f13fa4d03ace5bba3b296851ab7dde13eafcc8e3643928cf369dd465af004d29R94

repo: authts/oidc-client-ts


text:
🛑 Geoserver § geoserver1.prahounakole.cz is down

In 1f84da3, Geoserver § geoserver1.prahounakole.cz (https://geoserver1.prahounakole.cz) was down:

HTTP code: 502
Response time: 3788 ms

Resolved: Geoserver § geoserver1.prahounakole.cz is back up in 73c0420 after 9 minutes.

repo: auto-mat/automat-statuspage


text:
🛑 Automat eshop § obchod.auto-mat.cz is down

In 6f699e1, Automat eshop § obchod.auto-mat.cz (https://obchod.auto-mat.cz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Automat eshop § obchod.auto-mat.cz is back up in 59b2a6c.


text:
rpi-dnp3-gpio will not build with the make command

pi@raspberrypi:~/rpi-dnp3-gpio/build $ CXX=g++-4.8 cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr
-- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.8.4
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/g++-4.8
-- Check for working CXX compiler: /usr/bin/g++-4.8 -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/pi/rpi-dnp3-gpio/build
pi@raspberrypi:~/rpi-dnp3-gpio/build $ make
Scanning dependencies of target rpi-dnp3-gpio
[ 20%] Building C object CMakeFiles/rpi-dnp3-gpio.dir/deps/inih/ini.c.o
[ 40%] Building CXX object CMakeFiles/rpi-dnp3-gpio.dir/src/Config.cpp.o
[ 60%] Building CXX object CMakeFiles/rpi-dnp3-gpio.dir/src/main.cpp.o
/home/pi/rpi-dnp3-gpio/src/main.cpp: In function âint main(int, char**)â:
/home/pi/rpi-dnp3-gpio/src/main.cpp:63:10: error: âclass asiodnp3::DNP3Managerâ has no member named âAddLogSubscriberâ
manager.AddLogSubscriber(ConsoleLogger::Instance());
^
/home/pi/rpi-dnp3-gpio/src/main.cpp:63:27: error: âInstanceâ is not a member of âasiodnp3::ConsoleLoggerâ
manager.AddLogSubscriber(ConsoleLogger::Instance());
^
CMakeFiles/rpi-dnp3-gpio.dir/build.make:110: recipe for target 'CMakeFiles/rpi-dnp3-gpio.dir/src/main.cpp.o' failed
make[2]: *** [CMakeFiles/rpi-dnp3-gpio.dir/src/main.cpp.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/rpi-dnp3-gpio.dir/all' failed
make[1]: *** [CMakeFiles/rpi-dnp3-gpio.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
pi@raspberrypi:~/rpi-dnp3-gpio/build $

It's due to API changes between releases of opendnp3. I'll upgrade the usages to the 2.1.0 release.

Ok, small fix. Updated README to also mention 2.1.0 version of opendnp3.

authors: geyseran jadamcrain


text:
Update Firefox versions for api.HTMLElement.change_event

17375

 Quality gate: NA
Details

 Quality gate: NA
Details


text:
[Refactor] Use the backend implementation from automl common

Moves the backend and login to the common automl codebase from here: https://github.com/automl/automl_common

Hey this PR looks good and unifying the common components would help in keeping them up to date.  For me it can be merged once the tests pass. Also, I would like to add a reference to issue #186 as this PR also addresses it partially

I also checked the PR and looks good to me.

authors: franchuterivera nabenabe0928 ravinkohli

repo: automl/Auto-PyTorch


text:
Use asm-relocated 9.6.0.0.

Resolves https://github.com/autonomousapps/dependency-analysis-gradle-plugin/issues/965.

Build failed


text:
Add planetary restrictions to planetary processors under schematics

Like the old site did:

https://github.com/autonomouslogic/eve-ref/pull/543

repo: autonomouslogic/eve-ref


text:
support multiple unique key (composite primary key)

Hi,
I encounter this issue when execute dbt-dry-run to a table that has multiple unique key or composite primary key:
nodes -> model.dbt_re_data_test.table_name -> config -> unique_key
  str type expected (type=type_error.str)

need support to be able to include list type for multiple column unique_key

Hey @imfaridz,
Thanks for raising an issue. Looks like support for this was added in dbt-core 1.1 in this PR

Setting unique_key as a list is only supported for incremental tables so this issue will be fairly easy to fix as  only the snapshot_runner
 uses unique_key when validating the model config.
I will raise a PR to update our pydantic model schema

Will do a patch release for this sometime this week now the PR is merged

thanks for the support @connor-charles !

authors: connor-charles imfaridz

repo: autotraderuk/dbt-dry-run


text:
feat: add behavior_path_planner package

Related Issue
https://github.com/autowarefoundation/autoware.universe/issues/1
This PR depends on

https://github.com/autowarefoundation/autoware.universe/pull/4
https://github.com/autowarefoundation/autoware.universe/pull/7
https://github.com/autowarefoundation/autoware.universe/pull/8
https://github.com/autowarefoundation/autoware.universe/pull/24
https://github.com/autowarefoundation/autoware.universe/pull/26

Description
Addbehavior_path_planner  packages from https://github.com/tier4/AutowareArchitectureProposal.iv
How to review
Check the following item

Readme
Launch file

https://github.com/autowarefoundation/autoware.universe/issues/118


text:
Enable RISC-V platform

Open autoware with open RiSC-V chip may be a good idea.

Could you write a bit more detailed description?
For example:

How can we support it?
What ECUs can we use?
etc.

Also, since this isn't a bug but just an idea, I'll convert this to a discussion.

authors: kenji-miyake xczhanjun

repo: autowarefoundation/autoware


text:
docs(README.md): fix sample launch code example

Modify readme to follow the change in https://github.com/autowarefoundation/autoware/pull/63

Can I leave this as a draft since I'll remove it as I mentioned?

@kenji-miyake thanks!

authors: TakaHoribe kenji-miyake


text:
Segment-based dataset

It's quite common in audio datasets to have annotations on the segment level, usually denoted by some start and end time and the label(s). To address that, we need to introduce a new DatasetWrapper. I have a hacky draft I am using in an internal project, I'll post it here for reference, but I'll clean it up before integration
class CustomWrapper(DatasetWrapper):
    def __init__(self, **kwargs):
        super().__init__(**kwargs)
        self.df["new_file_name"] = (
            self.df[self.index_column]
            .apply(lambda x: os.path.splitext(x)[0])
            + "__" + self.df["start"].astype(str)
            + "__" + self.df["end"].astype(str)
            + ".wav"
        )
        self._index_column = self.index_column
        self.index_column = "new_file_name"

    def __getitem__(
        self,
        item: int,
    ) -> Tuple[torch.Tensor, Union[int, torch.Tensor], int]:
        """Get item from the dataset.

        Args:
            item: Index of the item.

        Returns:
            Tuple containing the data, target and item index.
        """
        index = self.df.index[item]
        if isinstance(self.file_handler, AudioFileHandler):
            item_path = self.df.loc[index, self._index_column]
            try:
                data = audiofile.read(
                    item_path,
                    offset=self.df.loc[index, "start"],
                    duration=self.df.loc[index, "end"] - self.df.loc[index, "start"],
                    always_2d=True
                )[0]
            except Exception as e:
                print(f"Crashed with {e} at {item_path}")
                exit()
            data = torch.from_numpy(data)
        else:
            item_path = self.df.loc[index, self.index_column].replace(".wav", f".{self.file_type}")
            data = self.file_handler.load(item_path)

        target = self.df.loc[index, self.target_column]
        if isinstance(target, pd.Series):
            target = torch.Tensor(target.to_list())

        if self.transform is not None:
            data = self.transform(data, index=item).float()

        if self.target_transform is not None:
            target = self.target_transform(target)

        return data, target, item

How would we handle preprocessing if a dataset uses segments of audio files?
You idea is to create our own naming schema we can refer to (new_file_name) and in the preprocessed "land" we can again treat the datasets as usual?

authors: ATriantafyllopoulos ramppdev

repo: autrainer/autrainer


text:
Polymorphic type mapping failing to include stringJsonAdapter

Hi, I just started trying the library, so I apologize if I missed a step somewhere. The following code is producing an adapter that does not compile:
@Json
@Json.SubType(type = MoveAccuracy.Unavoidable.class, name="UNAVOIDABLE")
@Json.SubType(type = MoveAccuracy.Avoidable.class, name="AVOIDABLE")
public sealed interface MoveAccuracy {
    record Unavoidable() implements MoveAccuracy {}
    record Avoidable(int percentToHit) implements MoveAccuracy {}
}

The error is symbol:   variable stringJsonAdapter in MoveAccuracyJsonAdapter. Here's the generated class:
@Generated
public final class MoveAccuracyJsonAdapter implements JsonAdapter<MoveAccuracy> {

  // naming convention Match
  // percentToHit [int] name:percentToHit ERROR?? no constructor, setter and not a public field? subTypes [com.pwinckles.cassette.common.model.MoveAccuracy.Avoidable]

  private final JsonAdapter<Integer> pintJsonAdapter;
  private final PropertyNames names;

  public MoveAccuracyJsonAdapter(Jsonb jsonb) {
    this.pintJsonAdapter = jsonb.adapter(Integer.TYPE);
    this.names = jsonb.properties("@type", "percentToHit");
  }

  @Override
  public void toJson(JsonWriter writer, MoveAccuracy moveAccuracy) {
    writer.beginObject(names);
    if (moveAccuracy instanceof final MoveAccuracy.Unavoidable sub) {
      writer.name(0);
      stringJsonAdapter.toJson(writer, "UNAVOIDABLE");
    }
    else if (moveAccuracy instanceof final MoveAccuracy.Avoidable sub) {
      writer.name(0);
      stringJsonAdapter.toJson(writer, "AVOIDABLE");
      writer.name(1);
      pintJsonAdapter.toJson(writer, sub.percentToHit());
    }
    writer.endObject();
  }

  @Override
  public MoveAccuracy fromJson(JsonReader reader) {
    // variables to read json values into, constructor params don't need _set$ flags
    int        _val$percentToHit = 0; boolean _set$percentToHit = false;

    String type = null;

    // read json
    reader.beginObject(names);
    while (reader.hasNextField()) {
      final String fieldName = reader.nextField();
      switch (fieldName) {
        case "@type":
          type = stringJsonAdapter.fromJson(reader);
          break;
        case "percentToHit":
          _val$percentToHit = pintJsonAdapter.fromJson(reader);
          _set$percentToHit = true;
          break;

        default:
          reader.unmappedField(fieldName);
          reader.skipValue();
      }
    }
    reader.endObject();

    if (type == null) {
      throw new IllegalStateException("Missing Required @type property that determines deserialization type");
    }
    if ("UNAVOIDABLE".equals(type)) {
      MoveAccuracy.Unavoidable _$unavoidable = new MoveAccuracy.Unavoidable();
      return _$unavoidable;
    }
    if ("AVOIDABLE".equals(type)) {
      MoveAccuracy.Avoidable _$avoidable = new MoveAccuracy.Avoidable(_val$percentToHit);
      return _$avoidable;
    }
    throw new IllegalStateException("Unknown value for @type property " + type);
  }
}

To my eye, this code looks correct, except that it's missing a private final JsonAdapter<String> stringJsonAdapter field.
I get the same error in 1.5 and 1.6-RC4.

nice catch, it seems this part was overlooked. While I'm fixing it, you can add a string field to one of the types and it'll work.

Fixed in version 1.6-RC5 which I am releasing now.
I'm keen to add support for #109 and then release 1.6

authors: SentryMan pwinckles rob-bygrave

repo: avaje/avaje-jsonb


text:
Added navigation guard to the router

Added navigation guard to the router, which will route to a 404 page if the query parameters in the URL are invalid.

For now, following are the allowed query parameters:
[
 "sessionId",
 "purpose",
 "subPurpose",
 "redirectTo",
 "redirectID",
 "group",
];

Why redirectID and sessionId. Pick one :)

authors: pritamps sudheshna-donthineni

repo: avantifellows/Portal


text:
power domain / management

Will it be easy to get into and wake from deep sleep via RTCs, and GPIO via both edge and level change etc.?
what will the sleep/deep sleep current demands be for power from LiPo input  etc. etc.

@ElectronicBattle
Good day,

I don't have information directly from myself on this but maybe look at: https://www.nxp.com/docs/en/application-note/AN12085.pdf

**We don't have an dedicated RTC coin cell battery connector, instead the lipo battery can be used to power the board incise their is no USB

Best estimate for the RT1060's low power mode is less than 150ma for lipo. (I would need to test this)

Thanks

authors: ElectronicBattle avencan

repo: avencan/Aventen-Formosa-Sync


text:
Quiz Application GUI

Hello, I am a GSSoC '21 participant, I would like to contribute to this repository.
Aim
Quiz Application GUI with Tkinter
Description
The user will be allowed to choose between multiple categories, as well as difficulty levels. The score is calculated and displayed at the end.

@soumyavemuri Updates on this?

Working on this right now. Will make a PR by tomorrow for sure.

authors: kaustubhgupta soumyavemuri

repo: avinashkranjan/Amazing-Python-Scripts


text:
CKD Added

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #1836

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My documentation follows Template for README.md

Category:

[x] AI/ML

Title: Chronic Kidney Disease
Folder: Chronic Kidney Diseases Prediction/
Script: Chronic Kidney Diseases Prediction.ipynb
Contributor: ayush-09
Description: Chronic Kidney Disease Prediction

@Yashbhadiyadra Please review this PR and tell me what should i have to change.
If everything allright merge this and provide relevant tags.

@Yashbhadiyadra @avinashkranjan Please merge it with all relevant tag if everything will be alright.


text:
Created script for arranging files in a directory as per their extensions into different sub directories.

Description
Added script script_dirs.py, README.md and output images for the script.
I have put the location of the images as per the master branch of the origin not as per mine.
So the images won't show up on readme file now but they can be seen in img folder
They will show up once the PR is merged.
Fixes #210
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

@all-contributors please add @Rahul555-droid  for code and documentation

@all-contributors please add @Rahul555-droid  for code and documentation


text:
It doesn't converse faster when I set the parameter(batch_size) to a number greater than one.

Describe the bug
It doesn't converse faster when I set the parameter(batch_size) to a number greater than one.
To Reproduce
Steps to reproduce the behavior:
e.g.

Run cells in video_to_slomo.py
Set batch_size to a number greater than one.
Error/Abnormal behavior: It uses more memory of cuda but doesn't converse faster.

Expected behavior
It can really converse faster.
Interpolated results/error output
Add frames or terminal output as applicable.
Desktop (please complete the following information):

OS:  Windows
Device Used GPU
Setup Info [e.g. PyTorch 0.4.1, Python 3.6, ]

Additional context
The utilization rate of the gpu <10%.(with Quadro P6000)

I have not tested that feature yet. Also, though I am not sure but when you use GPU, saving the image might become a bottleneck as I have to save every image one by one.

repo: avinashpaliwal/Super-SloMo


text:
Remove the implementation that set showsVerticalScrollIndicator

Summary

showsVerticalScrollIndicatorをセットしている部分の削除
→ インジケーターが表示されないのを確認

AWAの仕様として「スクロールインジケータは基本表示しない」というものを 本Repository にも適用するならば、そもそも showsVerticalScrollIndicator へ値を設定している箇所をすべて消すという対応でも良いと思いました！

AWAに適応することを考えると、わざわざfalseにしなくても確かに良いと思ったのでこちらで修正しました！
マージする前に、コミットメッセージも修正します
https://github.com/awa/PanModal/pull/2/commits/5a7c3751b24a628bf4fea0f5b8da49858b4c02ef

@naoto0n2 こちらお手すきで確認お願いします🙏🏻

レビューありがとうございました！修正コミットまとめてからマージします🙋🏻

repo: awa/PanModal


text:
🛑 Site IFRS is down

In 0624668, Site IFRS (https://ifrs.edu.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Site IFRS is back up in 887415d.

repo: aweiand/status-ifrs-osorio


text:
composition + deferred models [MRO]

On class composition between any other abstract models classes and shop deferred models, the deferred has to be the most right ancestor otherwise the deferred fields will not materialized.
I'm not sure if this is a bug. I suggest to add this to documentation.
class FooModel(BarModel, AnyShopDeferredModel): is good
class FooModel(AnyShopDeferredModel, BarModel): is not good.

I never intended to allow model mixins, therefore your code is not a use-case I expected.
Anyway, I assume that if BarModel is abstract too, then your code is correct. I'll add a note to the docs.

Yes, it's abstract. 👍

repo: awesto/django-shop


text:
AWS Amplify Project Auto Deployment: Build failed with Python backend Lambda function on CLI version 12.1.0

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.1.0
What operating system are you using?
Amazon Linux:2
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Amplify.yml:
backend:
  phases:
    build:
      commands:
        - ln -fs /usr/local/bin/pip3.8 /usr/bin/pip3
        - ln -fs /usr/local/bin/python3.8 /usr/bin/python3
        - pip3 install --user pipenv==2023.5.19
        - pipenv --version
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple

Describe the bug
I had an AWS Amplify project with Auto-deployment enabled. It was working fine until today when a new commit triggering the Auto build, it keeps failing. The new commit was mainly on React one to two line change without any change on Python Lambda and config files.
I extracted some of build error logs from AWS Amplify Console:

Installing pipenv:

2023-06-14T11:02:22.804Z [INFO]: Installing collected packages: virtualenv-clone, setuptools, distlib, platformdirs, filelock, virtualenv, pipenv
2023-06-14T11:02:24.955Z [INFO]: Successfully installed distlib-0.3.6 filelock-3.12.2 pipenv-2023.5.19 platformdirs-3.5.3 setuptools-67.8.0 virtualenv-20.23.0 virtualenv-clone-0.5.7
2023-06-14T11:02:25.338Z [WARNING]: WARNING: You are using pip version 19.2.3, however version 23.1.2 is available.
                                    You should consider upgrading via the 'pip install --upgrade pip' command.
2023-06-14T11:02:25.374Z [INFO]: # Executing command: pipenv --version
2023-06-14T11:02:25.975Z [INFO]: pipenv, version 2023.5.19

In the middle, all GraphQL related builds were fine
Then, error:

2023-06-14T11:03:13.292Z [WARNING]: ✖ There was an error initializing your environment.
2023-06-14T11:03:13.294Z [INFO]: 🛑 Received error [Error: Command failed with exit code 1: pipenv --venv
                                 No virtualenv has been created for this project(/codebuild/output/src189xxxxxx/src/XXXXXX/amplify/backend/function/XXXXXXbackendfn) yet!
                                 Aborted!] running command [pipenv --venv]
                                 Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Tried different ways but I don't know how to troubleshoot further. Ultimately, I saw the Amplify CLI had been upgraded to 12.1.0 lately, I decided to force the Amplify Image Build Setting back to 12.0.3:

And then I re-run the failed auto build, now it works.
Expected behavior
The auto build should complete without error using latest as Amplify CLI image build setting
Reproduction steps
Not sure exactly, the structure of the project:

Amplify React App (Javascript Website)
Backend Lambda function using Python language
Amplify push
Auto deployment to build

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Same issue here, with the same amplify.yml and same error about virtualenv not being created.
version: 0.1
backend:
  phases:
    preBuild:
      commands:
        - nvm install $VERSION_NODE_16
    build:
      commands:
        - '# Make sure we prefetch needed packages'
        - set -xe
        - yarn install
        - '# Change the current version of python'
        - ln -fs /usr/local/bin/pip3.8 /usr/bin/pip3 || exit 1
        - ln -fs /usr/local/bin/python3.8 /usr/bin/python3
        - pip3 install pipenv
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple

Currently workaround is to fix the Amplify CLI version to 12.0.3
It was so disturbing especially in prod environment with auto deployment!

Was able to reproduce the issue using the following steps
Upgrade to latest version of cli 12.1.0

create a new app
add a python function
push
add the project to git
connect the git CICD build

Observe the build fail.

marking as bug

Reproduction steps:

amplify init
amplify add function -> add lambda function - example: nodejs
amplify push
then add a empty line in nodeJs function (amplify status should show as update on the function)
amplify add function -> then create a python function (amplify status should show one update and one create on the functions)
then amplify push

related: https://github.com/aws-amplify/amplify-cli/issues/12720

This issue should be fixed in 12.1.1

authors: fkwfung lazpavel pm98zz-c ykethan

repo: aws-amplify/amplify-cli


text:
Aws amplify Appsync update schema

Note: If your question is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

** Which Category is your question related to? **
AWS Amplify appsync
** What AWS Services are you utilizing? **
Appsync dynamodb
** Provide additional details e.g. code snippets **
Hi all, i first created schema as
type User @model{
      id: ID!
      userId: ID!
}

later when i change userId: String! I am getting following error in cloud formation.
CloudFormation cannot update a stack when a custom-named resource requires replacing. Rename and update the stack again

This does look like an issue with your @model declaration. Do you have any stacks in your stacks/ directory and if so did you change them at all?

Nope

@achutkiran We weren't able to reproduce this issue. Could you please try adding a new API and do the same changes and see if the push succeeds? Also, what's the CLI version that you're using? Are you deploying it to the Amplify Console?

amplify version is 1.6.3. I'll try to create new api and update you

@achutkiran Were you able to reproduce this?

Hi, I tried by adding new api and I am unable to reproduce this issue


text:
"There was an error adding the datasource" .BadRequestException: Access denied for user, 'admin'@'10.1.13.10' (using password: YES)

Hello team,
I m facing this error while adding the datasource in my amplify project. I have check my amplify and its already to a latest version.
I m adding the data source by running amplify api add-graphql-datasource
Output
Provide the region in which your cluster is located: us-east-1
? Select the Aurora Serverless cluster that will be used as the data source for
your API: ampify-datastoredb
⠙ Fetching Aurora Serverless cluster...BadRequestException: Access denied for user 'admin'@'10.1.13.10' (using password: YES)
    at Object.extractError (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/json.js:51:27)
    at Request.extractError (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/rest_json.js:55:8)
    at Request.callListeners (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
There was an error adding the datasource
⠹ Fetching Aurora Serverless cluster...

Expected behaviour
The database cluster should be added successfully.
Please guide on this.

@parthsoni42 what version of the cli are you using and can you check the credentials of IAM user?

@parthsoni42 what version of the cli are you using and can you check the credentials of IAM user?

@ammarkarachi My cli version is 4.19.0.
I have check my version by running amplify --v command. I have also check for the version update by running npm install -g @aws-amplify/cli command.
It always install the version 4.19.0 so its a latest version right?

The latest version would be 4.21.0 also can you check the credentials for the IAM user?

@parthsoni42 We are going to mark this as a bug but so that we could have a more graceful failure when access is denied

The latest version would be 4.21.0 also can you check the credentials for the IAM user?

@ammarkarachi thanks for your reply.
I have update my amplify version and its now 4.21.0. Also my IAM user have admin access for rds and other permissions but still I am not able to connect with my aurora serverless datasource.
Here is my amplify version. (I have check my current version by running amplify --v)
admin-168@admin168:/mnt/7159d57f-c9cb-4fd4-b5f1-a04f7bb9a8ae/Projects/Dinal/Demo/AmplifyDemo$ amplify --v
Scanning for plugins...
Plugin scan successful
4.21.0
Please check the below logs for adding datasource:
admin-168@admin168:/mnt/7159d57f-c9cb-4fd4-b5f1-a04f7bb9a8ae/Projects/Dinal/Demo/AmplifyDemo$ amplify api add-graphql-datasource
Using datasource: Aurora Serverless, provided by: awscloudformation
? Provide the region in which your cluster is located: us-east-1
? Select the Aurora Serverless cluster that will be used as the data source for
your API: ampify-datastoredb
Fetching Aurora Serverless cluster...BadRequestException: Access denied for user 'admin'@'10.1.13.10' (using password: YES)
at Object.extractError (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/json.js:51:27)
at Request.extractError (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/rest_json.js:55:8)
at Request.callListeners (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
at Request.transition (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
There was an error adding the datasource

I can confirm I have having an identical error.
I have created multiple secrets now, some with DefaultEncryptionKey otherwise with every entry selected for permissions just to see if I could get it working.
Using datasource: Aurora Serverless, provided by: awscloudformation
? Provide the region in which your cluster is located: eu-west-2
? Select the Aurora Serverless cluster that will be used as the data source for your API: unsal
? Select the secret used to access your Aurora Serverless cluster: hutber
⠴ Fetching Aurora Serverless cluster...BadRequestException: Access denied for user 'jamie@hutber.com'@'10.1.6.36' (using password: YES)
    at Object.extractError (/home/hutber/.nvm/versions/node/v13.8.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/json.js:52:27)
    at Request.extractError (/home/hutber/.nvm/versions/node/v13.8.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/rest_json.js:55:8)
    at Request.callListeners (/home/hutber/.nvm/versions/node/v13.8.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)

Was anyone able to resolve this? I'm having the same problem

Any updates on this? I'm having the same issue here with cli version 4.34.0 while trying to connect to Aurora MySQL instance.

Any updates as to when this may be fixed? Having same issue, checked user permissions, and also updated cli version to latest.

Same issue here using 4.41.2 with Aurora PostgreSQL Serverless.
Has someone a workaround maybe?
ec2-user:~/environment/test $ amplify api add-graphql-datasource
Using datasource: Aurora Serverless, provided by: awscloudformation
? Provide the region in which your cluster is located: eu-central-1
? Select the Aurora Serverless cluster that will be used as the data source for your API: amplify
⠹ Fetching Aurora Serverless cluster...BadRequestException: FATAL: password authentication failed for user "test"
    at Object.extractError (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/json.js:52:27)
    at Request.extractError (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/rest_json.js:55:8)
    at Request.callListeners (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:688:14)
    at Request.transition (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:690:12)
There was an error adding the datasource
⠧ Fetching Aurora Serverless cluster...^Aborted!```

Same issue here using 4.41.2 with Aurora PostgreSQL Serverless.
Has someone a workaround maybe?
ec2-user:~/environment/test $ amplify api add-graphql-datasource
Using datasource: Aurora Serverless, provided by: awscloudformation
? Provide the region in which your cluster is located: eu-central-1
? Select the Aurora Serverless cluster that will be used as the data source for your API: amplify
⠹ Fetching Aurora Serverless cluster...BadRequestException: FATAL: password authentication failed for user "test"
    at Object.extractError (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/json.js:52:27)
    at Request.extractError (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/rest_json.js:55:8)
    at Request.callListeners (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:688:14)
    at Request.transition (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/home/ec2-user/.nvm/versions/node/v10.23.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:690:12)
There was an error adding the datasource
⠧ Fetching Aurora Serverless cluster...^Aborted!```

If you are encountering this error, please double check the values in the secret you created to access the Aurora cluster. Aurora Serverless v1 does not support IAM database authentication. From my own testing, the issue was solved by using the cluster's username and password (not any IAM credentials) in the secret.

This has been addressed in the latest version of the CLI

authors: Theduud Tporkka ammarkarachi cjihrig edwardfoyle hutber mattcech parthsoni42 steve-hb


text:
Lambda storage triggers that write S3 data - are they unsupported, or is this a bug?

Which Category is your question related to?
Storage & Functions
Amplify CLI Version
6.0.0
What AWS Services are you utilizing?
S3 / Lambda
Provide additional details e.g. code snippets
I can't figure out the 'supported' way of achieving this.

Adding storage 'write' permissions to a lambda that is also a trigger results in cyclic dependencies (see Scenario A and scenario B). I understand why you might block that - given you could end up infinitely recursive.
I could fix this by using prefixes on the lambda trigger - but this doesn't appear to be a configuration option, and the above would block me anyway.
I could write to a secondary bucket to avoid the infinite recursion risk entirely, but you only support one bucket.

Are there any alternatives, beyond manually creating stuff in AWS outside of the scope of Amplify?

Scenario A:

Creating a lambda function via add function
Adding permissions to access Storage
Adding as a trigger via update storage
then I get

✅ Successfully updated resource BucketNameTrigger8ba9f268 locally
🛑 Cannot add BucketName due to a cyclic dependency
✅ Successfully updated resource
Scenario B:

Creating a lambda function via add function
Adding as a trigger via update storage
Adding permissions to access Storage via update function

then I get
Error: Cannot add S3Trigger8ba9f268 due to a cyclic dependency
    at checkForCyclicDependencies (/Users/jcrowley/.nvm/versions/node/v12.17.0/lib/node_modules/@aws-amplify/cli/lib/extensions/amplify-helpers/update-amplify-meta.js:224:15)
    at AmplifyToolkit.updateamplifyMetaAfterResourceUpdate [as _updateamplifyMetaAfterResourceUpdate] (/Users/jcrowley/.nvm/versions/node/v12.17.0/lib/node_modules/@aws-amplify/cli/lib/extensions/amplify-helpers/update-amplify-meta.js:132:9)
    at updateFunctionResource (/Users/jcrowley/.nvm/versions/node/v12.17.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/lib/provider-utils/awscloudformation/index.js:150:29)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Object.executeAmplifyCommand (/Users/jcrowley/.nvm/versions/node/v12.17.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/lib/index.js:254:5)
    at async executePluginModuleCommand (/Users/jcrowley/.nvm/versions/node/v12.17.0/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:164:5)
    at async Object.executeCommand (/Users/jcrowley/.nvm/versions/node/v12.17.0/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:35:9)
    at async Object.run (/Users/jcrowley/.nvm/versions/node/v12.17.0/lib/node_modules/@aws-amplify/cli/lib/index.js:162:9)

@jamescrowley cyclic dependency resolution is behind a feature flag what you can find here, enabling it would make it possible to create the triggers.
About the infinite loop problem you are right, there is no way around it, coming from the nature of what you try to achieve, official documentation also suggests 2 buckets or use of prefixes.
As of Today you cannot create multiple S3 buckets within the same amplify project through add storage, but it is an active feature request we are tracking.
What you could do is create the additional bucket through our custom resource support by adding your own CFN stack to the amplify project.
About prefixes you can customize the NotificationConfiguration.LambdaConfigurations with prefixes/suffixes if you like after add storage then it will be pushed and preserved until you run update storage and changing the inputs for the given bucket.
Let me know if I answered all your questions

@attilah thanks for all the info, very useful. The feature flag you mention seems to be specifically for auth triggers, as opposed to storage though?

Yes that is correct, that's for triggers + circular dependency (chicken-egg)
Closing the issue as the question has been answered.

@attilah understood - was just making the point the feature flag you mentioned doesn't actually resolve my scenario, which is using a storage trigger rather than an auth trigger (at least it didn't seem to make any difference in my testing)

authors: attilah jamescrowley


text:
"Template error: instance of Fn::GetAtt references undefined resource" when using AdminUI/Studio for changes on Auth.

Before opening, please confirm:

[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d34ljddyp2gbsz
Region
us-east-1
Environment name
Staging
Amplify CLI Version
7.6.3
If applicable, what version of Node.js are you using?
v17.0.1
What operating system are you using?
Ubuntu through Windows Linux Subsystem
Browser type?
Google Chrome
Describe the bug
I deployed a very very rudimentary Authentication setup using the AdminUI/Studio. Later I wanted to update the authentication signup flow, so I clicked "Reset all authentication settings and users", with the hopes of updating the sign up flow after.
When the Admin Studio tries to run the deploy to delete the existing auth settings and users, it results in a deployment failure.
These are the logs:
Command failed with exit code 1: amplify push --yes --allow-destructive-graphql-schema-updates - Fetching updates to backend environment: staging from the cloud. - Building resource api/Backend ✔ Successfully pulled backend environment staging from the cloud. - Building resource api/Backend - Updating resources in the cloud. This may take a few minutes... ✖ An error occurred when pushing the resources to the cloud ⚠ Amplify command hooks are disabled in the current execution environment. ⚠ See https://docs.amplify.aws/cli/usage/command-hooks/ for more information. GraphQL schema compiled successfully. Edit your schema at /tmp/amplify-d5867ac5-4ff1-4cf1-9d46-188c7b4aa5a7/amplify/backend/api/Backend/schema.graphql or place .graphql files in a directory at /tmp/amplify-d5867ac5-4ff1-4cf1-9d46-188c7b4aa5a7/amplify/backend/api/Backend/schema   Current Environment: staging   ┌──────────┬───────────────┬───────────┬───────────────────┐ │ Category │ Resource name │ Operation │ Provider plugin │ ├──────────┼───────────────┼───────────┼───────────────────┤ │ Auth │ Backend │ Delete │ awscloudformation │ ├──────────┼───────────────┼───────────┼───────────────────┤ │ Api │ Backend │ No Change │ awscloudformation │ └──────────┴───────────────┴───────────┴───────────────────┘ GraphQL schema compiled successfully. Edit your schema at /tmp/amplify-d5867ac5-4ff1-4cf1-9d46-188c7b4aa5a7/amplify/backend/api/Backend/schema.graphql or place .graphql files in a directory at /tmp/amplify-d5867ac5-4ff1-4cf1-9d46-188c7b4aa5a7/amplify/backend/api/Backend/schema 🛑 An error occurred during the push operation: Template error: instance of Fn::GetAtt references undefined resource authBackend.
When I try to do this operation using amplify remove auth and then amplify push,
I get the same final error:

Building resource api/BackendGraphQL schema compiled successfully.
Edit your schema at /mnt/c/Users/Parth/Documents/project/amplify/backend/api/Backend/schema.graphql or place .graphql files in a directory at /mnt/c/Users/Parth/Documents/project/amplify/backend/api/Backend/schema
✖ An error occurred when pushing the resources to the cloud
🛑 An error occurred during the push operation: Template error: instance of Fn::GetAtt references undefined resource authBackend

Expected behavior
The deployment would complete properly and Amplify AdminUI would delete all users and previous settings, allowing me to revamp my auth flow.
Reproduction steps

Go to Amplify AdminUI/Studio
Click Authentication
Scroll to the bottom and click "Reset all authentication settings and users"
Click confirm.

Additional information
No response

@Parth220
To unblock yourself, please do the following with the CLI:

amplify remove auth
amplify update api
Select GraphQL
Select a setting to edit:  Authorization modes
Choose the default authorization type for the API: choose either API key or IAM depending on your GraphQL schema
When you get to Configure additional auth types?, enter yes (that you want to edit these)
When given the choice of additional auth types, unselect Amazon Cognito User Pool and press enter

You should now be able to push your updates and remove the Auth resource. However, do this only if your GraphQL schema does not actually depend on the Cognito User Pool auth type (i.e. if none of the auth directives in your schema contain {allow: private})


text:
fix(amplify-codegen): use Java Long for AWSTimestamp

Issue #, if available:
#3593
Description of changes:
Use Java object Long instead of primitive long so that it can be set to null.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9da0872). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #3615   +/-   ##
=========================================
  Coverage          ?   60.16%
=========================================
  Files             ?      279
  Lines             ?    13101
  Branches          ?     2643
=========================================
  Hits              ?     7882
  Misses            ?     4795
  Partials          ?      424

Impacted Files
Coverage Δ

...-codegen-appsync-model-plugin/src/scalars/index.ts
100% <ø> (ø)

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 9da0872...3dbcfed. Read the comment docs.

authors: codecov-io edwardfoyle


text:
Introduce a Ready Condition

We currently have the ACK.ResourceSynced Condition that informs the Kubernetes user whether the desired state of a resource matches the latest observed state of the resource.
The ACK.ResourceSynced Condition is very much useful for both the ACK controllers as well as Kubernetes users, however this Condition does NOT represent the "readiness" of a particular AWS resource. By "readiness", I refer to the Kubernetes concept of readiness probes which allow a Kubernetes user to determine if a Pod is ready to accept incoming traffic/connections.
I believe we should have an ACK.Ready Condition that mimics this behaviour.

What would be the readiness for a static resource like an S3 bucket? Also for something stateful, like an RDS DBInstance, would ACK.Ready just imply the resource is in an accessible state (like Active) or something more?

What would be the readiness for a static resource like an S3 bucket?

For those kinds of resources, ResourceSynced and Ready would essentially be the same thing.

Also for something stateful, like an RDS DBInstance, would ACK.Ready just imply the resource is in an accessible state (like Active) or something more?

Precisely. When a DBInstance is in available state it would be Ready=True.

/lifecycle frozen

authors: RedbackThomson jaypipes vijtrip2


text:
Add missing environment variables to build-controller.sh

Issue N/A
Description of changes:
Merge build-controller.sh and Makefile changes from https://github.com/aws-controllers-k8s/code-generator/commit/92458ababbeb0cd0f00b93e149ccc6b4e42f2835:

Add missing environment variables AWS_SDK_GO_VERSION and TEMPLATES_DIR  to build-controller.sh script
Add -tags=codegen arg to the go install ack-generate command
Remove build-ack-generate step from build-controller step

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@surajkota Once this PR is merged you will be able to specify AWS_SDK_GO_VERSION when building a service controller from the community repo