Error: client quota exceeded

Hello,
I have tree yeelight lamps: 2x ceiling lamp, 1x meteorite. Today my ceiling lamp stop working with this error in console:
[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 2 after 400ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 3 after 800ms.
[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 3 after 800ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 4 after 1600ms.
[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: '[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 2 after 400ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 3 after 800ms.
[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 3 after 800ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 4 after 1600ms.
[2020-10-20 19:34:14] [Yeelight] { id: 211, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 4 after 1600ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 5 after 3200ms.
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed to send cmd 212 after 5 retries.' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007e92641: failed communication attempt 4 after 1600ms.
[2020-10-20 19:34:14] [Yeelight] { id: 212, error: { code: -1, message: 'client quota exceeded' } }
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed communication attempt 5 after 3200ms.
[2020-10-20 19:34:14] [Yeelight] 0x0000000007f84a20: failed to send cmd 212 after 5 retries.
could you help me to resolve? From Yeelight App all lamps working grate. Meteorite lamp works from HomeBridge and Yeelight app. Only ceiling lamps stops working from HomeBridge.

This might happen if you send a lot of commands per minute. It should resolve itself within a minute or so.
From Yeelight WiFi Light Inter-Operation Specification:

Yeelight WiFi smart device support up to 4 simultaneous TCP connections, any further connect attempt will be rejected. For each connection, there is a command message quota, that is 60 commands per minute. There is also a total quota for all the LAN commands: 144 commands per minute (4 × 60 × 60%).


Is it possible to create an array object from Go?

Hello!
Everything is in the question: what is the equivalent Go code for JS var obj = [10, 20, 30]?
Thanks!

If you mean native js array, then no. You can, however, pass a pointer to a []interface{} which will be represented as a host object similar to an array:
	vm := goja.New()
	a := []interface{}{10, 20, 30}
	vm.Set("a", &a)
	vm.RunString("a.push(40)")
	fmt.Println(a) // prints [10 20 30 40]

I hope this answers your question, @matwachich Feel free to open another ticket if you have any further questions.


Feature Request: Enable on self-hosted GitLab

We are running a self-hosted internal GitLab instance, on a custom domain.
This extension only seems to apply to the hosted, public GitLab instance at gitlab.com.
It would be great if we'd be able to configure this extension to also cover our use case.

This is related to #2
Once the functionality of entering custom domains is finished, the extension can apply to all private git servers.


Embeds: only revert to URL if there is one

Saw a burst of warnings like:
[08-Nov-2024 16:50:11 UTC] Warning: Undefined array key "url" in wp-content/plugins/activitypub/includes/transformer/class-post.php on line 1074

Although I couldn't replicate on the site in question, it's probably just an embed block with no URL set. This should stop that.

Makes sense!


How to set color of the dialog sheet background?

I can't find an answer to this question, is it possible to change the color of the background of the dialog sheet?

You can change the background color of the dialog with the following line of code:
.setBackgroundColor(Color.BLACK)
Or if you want to use a color resorce:
.setBackgroundColorRes(R.color.yourColor)


Error: spawn .bin\git.CMD ENOENT

As of a week ago, we started to see the below error from Bower in our build process when it installs packages. The error seems to occur regardless of the version of Bower, but does only happen when using NoGit's git.cmd (https://github.com/whyleee/nogit), not when using git.exe (note the two entries from where git below). This may be an issue with nogit, and if so I'll post there, but I can't tell. I do see that Bower has special handling for non-exe git, for #626, and my best guess is this is related to that issue. It does look like it's trying to spawn the cmd, which is wrong based on https://github.com/nodejs/node-v0.x-archive/issues/2318. I note that the extension ends up in all caps in the error, which seems wrong also, but I'm not sure what to make of it.
D:\{path}>where git
D:\{path}\.bin\git.cmd
C:\Program Files\Git\cmd\git.exe

D:\{path}>bower install
{ not-cached, resolve actions for other packages }
bower malihu-custom-scrollbar-plugin#3.1.3       not-cached https://github.com/malihu/malihu-custom-scrollbar-plugin.git#3.1.3
bower malihu-custom-scrollbar-plugin#3.1.3          resolve https://github.com/malihu/malihu-custom-scrollbar-plugin.git#3.1.3
{ not-cached, resolve, checkout actions for other packages }
bower malihu-custom-scrollbar-plugin#3.1.3         checkout 3.1.3
{ checkout actions for other packages }
bower malihu-custom-scrollbar-plugin#3.1.3           ENOENT spawn .bin\git.CMD ENOENT

Stack trace:
Error: spawn .bin\git.CMD ENOENT
    at exports._errnoException (util.js:855:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)

Console trace:
Error
    at StandardRenderer.error (C:\Users\{user}\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:81:37)
    at Logger.<anonymous> (C:\Users\{user}\AppData\Roaming\npm\node_modules\bower\lib\bin\bower.js:110:26)
    at emitOne (events.js:77:13)
    at Logger.emit (events.js:169:7)
    at Logger.emit (C:\Users\{user}\AppData\Roaming\npm\node_modules\bower\lib\node_modules\bower-logger\lib\Logger.js:29:39)
    at C:\Users\{user}\AppData\Roaming\npm\node_modules\bower\lib\commands\index.js:48:20
    at _rejected (C:\Users\{user}\AppData\Roaming\npm\node_modules\bower\lib\node_modules\q\q.js:844:24)
    at C:\Users\{user}\AppData\Roaming\npm\node_modules\bower\lib\node_modules\q\q.js:870:30
    at Promise.when (C:\Users\{user}\AppData\Roaming\npm\node_modules\bower\lib\node_modules\q\q.js:1122:31)
    at Promise.promise.promiseDispatch (C:\Users\{user}\AppData\Roaming\npm\node_modules\bower\lib\node_modules\q\q.js:788:41)
System info:
Bower version: 1.7.9
Node version: 5.3.0
OS: Windows_NT 10.0.10586 x64

Verbose stack trace:
Stack trace:
Error: spawn .bin\git.CMD ENOENT
    at exports._errnoException (util.js:855:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
From previous event:
    at executeCmd (C:\Users\Dbroad\AppData\Roaming\npm\node_modules\bower\lib\util\cmd.js:61:22)
    at PThrottler._processEntry (C:\Users\Dbroad\AppData\Roaming\npm\node_modules\bower\lib\node_modules\p-throttler\index.js:89:25)
    at PThrottler._processQueue (C:\Users\Dbroad\AppData\Roaming\npm\node_modules\bower\lib\node_modules\p-throttler\index.js:67:18)
    at Array.forEach (native)
    at PThrottler._onFulfill (C:\Users\Dbroad\AppData\Roaming\npm\node_modules\bower\lib\node_modules\p-throttler\index.js:121:17)

Found the cause of my issues, although it still seems there may be something Bower can do to make this work better.
I had specified the local git path for https://github.com/kmees/MSBuild.NodeTools as ".bin" because that was the location relative to where I was running Bower. Bower initially finds git and continues on. However, after checking out the projects I want to install and going to resolve them, it apparently tries to run git from another location, and can't find the ".bin" folder, then the ENOENT error is thrown because it can't find git.
If you ask me, this still somewhat indicates an issue, because if Bower is initially able to find git, it shouldn't fail to find it later on through its install process. My fix has been to specify the full path, which is something I'll do either way, but it seems to me that if Bower finds git initially, it shouldn't fail to find it halfway through its install packages process.

Hi !
I have exactly the same issue.
But i'm not using NodeTools, direct passing by command line.
(node version : 4.4.4)

This issue got stale. If this is still relevant, please create another one


Vehicle stopped beyond target point

Hi @evshary
I have encountered a problem, in the automatic driving mode, the vehicle will exceed the set target point every time it stops, how to solve this problem?

Hi @xiaoc88 Sorry for missing your messages. This is a known issue, but we don't have time to look into it yet.


Can't untoggle the top two toggles (CP) on Settings page

We should either decide we don't want this or implement it like it is on prod. I think it's important to implement; any arguments against?
@ncarazon commented on the notion issue:

we need to add a field on the BE to store these settings or do we want to just store it in local storage? Also, is there a spec on what each flag should do in the app?

Current behavior
These two are untoggleable:

Expected/desired behavior
“Show CP by default on open questions” is true by default; if false, the CP graphs are all blank (on the home page and if you click into the question). E.g. see screenshot.

“Show CP if you’ve predicted” is the same, but once you’ve made one prediction, the CP is revealed (appears as normal, on home page and question page). The point is some people don’t want to be anchored by the CP before they’ve thought about a question themself.
Also, if you’ve hidden them, you should get text under the graph on the question page like this, linking you to the settings page:

Ok, so basically:
1 option which is "hide CP"
and when the CP is hidden due to this option we show a button on the graph that says "Reveal CP" & Allows the user to temporarily do that.

New option added

CP time series is hidden (great!) on main feed and question page, but I can still see it under Make a Prediction, which kind of defeats the purpose.

(this is true of all question types; just showing continuous since I expect that's the hardest one to fix)
On prod
Fwiw I notice this doesn't really work on prod either (so maybe we can just let it be for now / not block release) -- only works for some question types, like:

But it does hide the CP under "Make a Prediction."

@hlibowski @lsabor I would love to make it so that you can't see the CP at all on the question page, like last screenshot above and https://www.metaculus.com/questions/28163/gas-price-at-end-of-sept-2024/:

How annoying would this be to implement.

@hlibowski is the toggle functioning properly?
If so - removing the cp column from that display should be extremely easy.

I have to correct myself, the method to reveal the CP is embedded in the graph component which would then have to talk with the forecast input component, which is not trivial and would require some refactoring.
I was expecting that when the CP is hidden we don't actually return populated CP values and we could just retrieve the values at will if we want to temporarily reveal it, but instead it looks like we have the data and hide it and so it will require some more complicated state management.

For now, I'm going to have the forecast maker respect the user's setting. Awkwardly, that means that the forecast maker won't respect the "temporarily reveal" button in the graph.

I've implemented and merged this. The drawback to my solution is (just as I suggested) that it doesn't respect the "temporary reaveal" button. A future refactor will be required, but this does allow users with the setting on to successfully hide it from themselves for now. Moving to medium priority for addressing the straggling issue as it's no longer blocking.
I'd still like to just not return the CP details at all with the setting on and never make any checks about displaying - there are too many locations to add the conditions.

On dev I still see the CP, e.g. here

and here

Closing this out since the toggle has an effect now...! and I'll make a new issue for respecting "temporarily reveal," which like @lsabor said will take significant effort and can wait until after launch.


(docs): add ngx-vest-forms

https://blog.simplified.courses/introducing-ngx-vest-forms/
https://github.com/simplifiedcourses/ngx-vest-forms

Thanks for the PR.


Sidebar - projects

As a user
I want to see my overall project details
So that I can view key information about my project and get to my other projects

Design
Tasks

[x] Create projects pane and add into the Sidebar component with correct icon
[ ] Move Your projects link button into the projects pane and make it a primary button
[x] Move Rename project input into the projects panel
[x] Extract and display project data (project type and date created)
[x] Move download button into projects pane and make it a secondary button

ACs

[ ] Project name can be edited by clicking on the pencil. Otherwise it is a read-only field.
[ ] Project details are visible and accurate
[ ] User can download from here (don't include share in this iteration)

@loiswells97 to refine

merged and closed


tests: Re-enable and flesh out InvalidUsageBits

Re-enable ifdef'ed usage test - check 3 paths, 2 image paths and a buffer path.

I've added the unlock.  The VkBool32 was staying consistent with other routines.  I can certainly call vkCmdCopyBufferTo Image a second time if that's cleaner.

Hey Tony, please add a TEST_DESCRIPTION to the test and go ahead and push it...

Done


[WSL 2] Can not save file on Linux fs from Windows emacs

Environment
Microsoft Windows [Version 10.0.19041.508]
Ubuntu 20.04 on WSL 2
Linux version 4.19.104-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Feb 19 06:37:35 UTC 2020
Steps to reproduce

Install Emacs for Windows from GNU
Create text file in WSL:

$ pwd
/home/rille

$ echo "Foo" > TEST

Open file with Windows Emacs:

$ /mnt/c/Program/Emacs/x86_64/bin/runemacs.exe TEST

Edit file, then try to save with Ctrl+X Ctrl-S. Produces error message:

Getting ACLs: Input/output error, //wsl$/Ubuntu-20.04/home/rille/TEST

If Emacs is started with the name of a non-existing file, it can be saved once.
With an earlier version of Emacs (26.1) the file would be written but any execute bits would be stripped.
Expected behavior
The file is saved.
Actual behavior
Emacs shows an error message and refuses to save the file.

Early guess, probably external (in other words recent emacs regress) like this. Not all Windows filesystems supports Windows ACLs, including our 9p.

I am running into this problem as well, on 2020-12-21, with this environment:
Windows 10 Version 1909 (OS Build 18363.1198)
Ubuntu 20.04 LTS on WSL 2
Linux PALN34691146A 4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
I also experienced that if I create a file that does not exist it can be saved, but any modification to an existing file gets this error.

Can confirm this is still an issue (OS Build 19042.1110, Emacs 27.2, using both WSL 1 and WSL 2).
Although this maybe should be reported to emacs-devel instead, I thought this might help some people when posted here: A very crude fix I came up with is to simply add advice around file-acl:
(when (eq system-type 'windows-nt)
    (defun fp/ignore-wsl-acls (orig-fun &rest args)
      "Ignore ACLs on WSL. WSL does not provide an ACL, but emacs
expects there to be one before saving any file. Without this
advice, files on WSL can not be saved."
      (if (string-match-p "^//wsl\$/" (car args))
          (progn (message "ignoring wsl acls") "")
        (apply orig-fun args)))

    (advice-add 'file-acl :around 'fp/ignore-wsl-acls))

So far I have not encountered any issues with this, although one should always be careful when writing advice for "low-level" functions like file-acl. Realistically, running emacs directly in wsl is a better option, but if you just want to make some quick edits in wsl while doing most of your work on the windows side of things, this might be a decent fix.

This is very strange. I have two files in the same directory, one of which generates this error, one of which doesn't.

Dominiksta's workaround continues to work for me; I have not checked recently to see if it is still required.
OS Win 10 21H2 build 19044.1526
WSL2; Emacs 27.2, build 1, x86_64-w64-mingw32 of 2021-03-26.
Linux-r:  <IP_ADDRESS>-microsoft-standard-WSL2
Linux-v: #1 SMP Fri Apr 2 22:23:49 UTC 2021
Thanks!

Can confirm this is still an issue (OS Build 19042.1110, Emacs 27.2, using both WSL 1 and WSL 2).
Although this maybe should be reported to emacs-devel instead, I thought this might help some people when posted here: A very crude fix I came up with is to simply add advice around file-acl:
(when (eq system-type 'windows-nt)
    (defun fp/ignore-wsl-acls (orig-fun &rest args)
      "Ignore ACLs on WSL. WSL does not provide an ACL, but emacs
expects there to be one before saving any file. Without this
advice, files on WSL can not be saved."
      (if (string-match-p "^//wsl\$/" (car args))
          (progn (message "ignoring wsl acls") "")
        (apply orig-fun args)))

    (advice-add 'file-acl :around 'fp/ignore-wsl-acls))

So far I have not encountered any issues with this, although one should always be careful when writing advice for "low-level" functions like file-acl. Realistically, running emacs directly in wsl is a better option, but if you just want to make some quick edits in wsl while doing most of your work on the windows side of things, this might be a decent fix.

Thank you @dominiksta for that excellent workaround.  I've updated it for my own situation when using rclone, and the filename doesn't necessarily tell you what the mount is.  It catches the error thrown by file-acl instead of preventing the function from running:
`(defun fp/ignore-acls (orig-fun &rest args)
"Ignore ACLs when not available.  OneDrive does not provide an ACL."
(condition-case nil
(orig-fun (car args))
(error "")))
(advice-add 'file-acl :around 'fp/ignore-acls)`
Hope others also find this useful


Permission name change on service provider authorizer

Noticed a use conflict with the serviceprovider.action.id - we have two uses for these prefixed permissions.
One is the ServiceProviderAwareDAO which adds a layer of filtering on DAO services allowing updating objects based on if the user has a variation of permission mentioned above (id replaced by service provider id). The other permits users to update read, remove service provider objects which is applied on the serviceProviderDAO authorizer.
It'd be a good idea to make a distinction on these so I've made a change to the service provider dao's authorizer string that constructs the permission.

are non-admin users supposed to have read access to ServiceProviderDAO for their own spid? if so, you might need to add serviceproviderdao.read.<spid> to ServiceProvider.inherentPermissions as well. if not then lgtm

the ServiceProviderAwareDAO which adds a layer of filtering on DAO services allowing updating objects based on spid if the user has the permission mentioned above

The "serviceprovider.update.id" check is only triggered when the user is trying to change/re-assign a different spid to the object. Otherwise, it check for "serviceprovider.read.id".

@noodlemoodle I'm fine with that, any ideas when a user needs the service provider object now? The service provider object doesn't hold information a regular user would care to know afaik.

@lchanmann ah yes, I should have made that clear since I referred to the update permission in my comment. Updated the PR summary.

IMO, "serviceproviderdao" permissions might not end up being used. The implication and impact of updating or removing a service provider at runtime hasn't been evaluated, we should not give "serviceproviderdao.update.id" or "serviceproviderdao.remove.id" permissions to anybody. Also not sure who might need "serviceproviderdao.read.id" permission. FYI @zahnno @jlhughes

they shouldn't need it, but we do have places were we call findspid for serviceprovideraware objects which calls the serviceproviderdao, which would probably cause side effects if the context user is non admin

for non-admin users the ServiceProvider.inherentPermissions should already give them access to find owned spid.

for non-admin users the ServiceProvider.inherentPermissions should already give them access to find owned spid.

inherentpermission only gives serviceprovider.read, with this we woul need serviceproviderdao.read to find it no?

So you wanted to differentiate between say "serviceprovider.remove.id" the permission to delete the service provider aware object eg. User as opposed to "serviceproviderdao.delete.id" the permission to delete the service provider the service provider itself?
If the user already have permission to delete object eg. "user.remove.id" why do they need "serviceprovider.remove.id" permission? and if someone has "serviceproviderdao.delete.id" permission then delete the service provider eg. "intuit", what should happen?
I am still hesitate on having "serviceproviderdao.action.id" permissions.

Rule.authorizeOnDelete() still uses "serviceprovider.update" permission, should it be updated?
Ref: https://github.com/kgrgreer/foam3/blob/6cca957a1fe875359cb83d32a6c25968b8f36104/src/foam/nanos/ruler/Rule.js#L481-L491


Mailer from does not match app configuration value

Ive configured FROM =<EMAIL_ADDRESS>in custom/conf/app.ini, but the notification email I received still shows the from section value is the issue owner's email address.
By the way, the page title for 应用配置管理 is misspelled as 用户管理.

Do you send and receive through gmail or google apps? Within google it seems to be always rewritten to the SMTP user email address, regardless what you have configured as a sender.

No, I'm using QQ domain mail to send through SMTP. Since it cannot deliver emails to Gmail at the time, I'm sending emails to a qq.com mail address, but the from value of these mails are always my primary email address, which is a gmail address.

I've turned to use Mailgun's SMTP server to send email notifications, but the from value is still the issue owner's email address.
Besides, the notification email lacks some basic information. Right now it's just come plain texts, I don't even know what email it is when I first look at it.

Thanks your feedback!
What is your version of Gogs?

By the way, the page title for 应用配置管理 is misspelled as 用户管理.

Good catch!

I'm using latest gogs binary downloaded from official site
On Sat, Sep 12, 2015, 19:24 无闻<EMAIL_ADDRESS>wrote:

By the way, the page title for 应用配置管理 is misspelled as 用户管理.
Good catch!
—
Reply to this email directly or view it on GitHub
https://github.com/gogits/gogs/issues/1628#issuecomment-139750067.

@JokerQyou OK, this is a issue claimed to be fixed in master branch: https://github.com/gogits/gogs/issues/1528


Language datatype is not found (because the class is not loaded before it is used?)

The Joke-class doesn't seem to be loaded by the module. Datatype "language" is not found. But if I dotsource jokes.ps1, it works

.

Do you get the same error if you import ./RandomJoke/RandomJoke.psd1?

It seems like it

(printscreen doesn't show -force on the last module load. Tried it, didn't help).

It seems like there is a feature (?) that prevents a class from being loaded in a script if it contains a data type that is not yet known when the script execution starts.


Error 404 in get_user -> register

I never used letsencrypt before and was hoping to let this take care of itself with the creation and updating of the certificate, but when trying to run the generated lambda function, I get this error:
START RequestId: f31cb3e2-339f-11e6-a2f7-139f7c45a328 Version: $LATEST
[INFO]	2016-06-16T08:54:36.788Z	f31cb3e2-339f-11e6-a2f7-139f7c45a328	No certificate exists for E2EDQ498I94TP2
[INFO]	2016-06-16T08:54:37.350Z	f31cb3e2-339f-11e6-a2f7-139f7c45a328	Creating user and key
HTTP Error 404: Not Found: HTTPError
Traceback (most recent call last):
  File "/var/task/lambda_function.py", line 570, in lambda_handler
    user = get_user()
  File "/var/task/lambda_function.py", line 80, in get_user
    user.register(cfg.EMAIL)
  File "/var/task/simple_acme.py", line 175, in register
    "mailto:{}".format(email)
  File "/var/task/simple_acme.py", line 46, in _send_signed_request
    LE_NONCE = urlopen(cfg.DIRECTORY_URL + "/directory").headers['Replay-Nonce']
  File "/usr/lib64/python2.7/urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/lib64/python2.7/urllib2.py", line 437, in open
    response = meth(req, response)
  File "/usr/lib64/python2.7/urllib2.py", line 550, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib64/python2.7/urllib2.py", line 475, in error
    return self._call_chain(*args)
  File "/usr/lib64/python2.7/urllib2.py", line 409, in _call_chain
    result = func(*args)
  File "/usr/lib64/python2.7/urllib2.py", line 558, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
HTTPError: HTTP Error 404: Not Found

END RequestId: f31cb3e2-339f-11e6-a2f7-139f7c45a328
REPORT RequestId: f31cb3e2-339f-11e6-a2f7-139f7c45a328	Duration: 3819.12 ms	Billed Duration: 3900 ms 	Memory Size: 128 MB	Max Memory Used: 72 MB

This is my configuration:
**Summary**
Notification Email:                              -------@------
S3 Config Bucket:                                ---.----.com (existing)
IAM Role Name:                                   lambda-letsencrypt (to be created)
Support HTTP Challenges:                         True
S3 HTTP Challenge Bucket:                        ---.----.com (existing)
Domains To Manage With Lets-Encrypt
    ---.----.com - []
CloudFront Distributions To Manage:
    E0000000000000 - [---.----.com]
Elastic Load Balancers to Manage:
> Are these settings correct[Y/n]? y

Making Requested Changes
Creating SNS Topic for Notifications ✓
Role doesn't exist, attempting to create
Creating Role 'lambda-letsencrypt-test-role'
Role Created
Role policy doesn't exist, attempting to create
Writing Configuration File ✓
Creating Zip File To Upload To Lambda
    Adding 'lambda_function.py'
    Adding 'simple_acme.py'
    Adding 'config.py'
Zip File Created Successfully
Configuring Lambda Function:
    IAM ARN: arn:aws:iam::000000000000:role/lambda-letsencrypt/lambda-letsencrypt-test-role
    Uploading Function ✓

Also I didn't find any new files in my S3 bucket. From what I understand I should find a letsencrypt file and a domain.example.com file.

This is actually fixed by #14 on https://github.com/ubergeek42/lambda-letsencrypt/pull/14/commits/d0b853517a0ac9f29a881279ba090214d3af493b#diff-0e0960a956201021301746e32c810686R2


Support GPUs for numba.stencil

The Stencil functions seem like a convenient entry point for CUDA acceleration.
My hope is that the constained nature of the user API would make the automatic generation of CUDA kernels somewhat more straightforward than in the fully general case.

Thanks for the suggestion. At present the CPU based stencil code gen relies on generating loop nests over the kernel, I guess this could be translated to GPU-like devices mapping the loop nests to grid/block/thread etc, exposing an API to do this would be interesting particularly from an efficiency view point.


Exercise scripts

For models/exercise/, it wasn't immediately clear where the scripts lay. In the README you say:

Open two_strain.py and plot_two_strain_ts.py and examine the code.

However, it's not clear where this code actually is. I'd suggest moving the exercise instructions to models/exercise/README.md and link out to the GitHub source code locations https://github.com/trvrb/sismid/blob/master/models/exercise/two_strain.py, etc...
Or just link to https://github.com/trvrb/sismid/tree/master/models/exercise near the beginning of the exercise instructions.

Agreed--the files there now are mostly placeholders, which I haven't
finished migrating and organizing.

Sarah Cobey, PhD
Assistant Professor
Ecology & Evolution
University of Chicago
(617) 756-7204 (cell)
sarahcobey (Skype)
cobeylab.uchicago.edu
On Sat, Jul 18, 2015 at 3:11 PM, Trevor Bedford<EMAIL_ADDRESS>wrote:

For models/exercise/, it wasn't immediately clear where the scripts lay.
In the README you say:
Open two_strain.py and plot_two_strain_ts.py and examine the code.
However, it's not clear where this actually code is. I'd suggest moving
the exercise instructions to models/exercise/README.md and link out to
the GitHub source code locations
https://github.com/trvrb/sismid/blob/master/models/exercise/two_strain.py,
etc...
—
Reply to this email directly or view it on GitHub
https://github.com/trvrb/sismid/issues/6.

Ah. Okay. Sounds great. I think this is all shaping out quite nicely.

Looks good.


Android package import is in MainApplication.java

Fixed a typo pointing out that the package import is in MainActivity.java - it's actually MainApplciation.java.

@adammcarth Thank you for the work. Could you please PR to dev branch instead of master? Please follow the CONTRIBUTING guide in the readme.
I'll close this.


Fix bottom tab highlight delay

Details
Modified the useActiveRoute hook to return a match for all bottom tab routes.
Renamed it useActiveBottomTabRoute
Modified files to use this hook instead of previous logic when information on the currently selected bottom tab is needed.
Fixed Issues
$ https://github.com/Expensify/App/issues/44587
PROPOSAL:https://github.com/Expensify/App/issues/44587#issuecomment-2201827887
Tests

Click on the Account bottom tab to select that route
Verify that the Account bottom tab has a green border around it.
Navigate to another tab, verify that tab is highlighted and the Account tab is not.

[x] Verify that no errors appear in the JS console

Offline tests

Click on the Account bottom tab to select that route
Verify that the Account bottom tab has a green border around it.
Navigate to another tab, verify that tab is highlighted and the Account tab is not.

QA Steps

Click on the Account bottom tab to select that route
Verify that the Account bottom tab has a green border around it.
Navigate to another tab, verify that tab is highlighted and the Account tab is not.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/72584987/1e411ed4-b1cb-4e7d-8295-b8a446904c9e

Android: mWeb Chrome
https://github.com/Expensify/App/assets/72584987/da557c52-180b-48d4-a5fd-be470dc431bd

iOS: Native
https://github.com/Expensify/App/assets/72584987/a24e64e8-627c-41e8-b550-972583942923

iOS: mWeb Safari
https://github.com/Expensify/App/assets/72584987/9aa871ac-f7aa-4f01-905f-4c6939b4a3a8

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/72584987/5bcba51b-e84a-4606-8a9c-dbf3de4ec0df

MacOS: Desktop
https://github.com/Expensify/App/assets/72584987/8c138eb0-1565-4819-93c1-1c1c454d826d

I have read the CLA Document and I hereby sign the CLA

recheck

@Zakpak0 Take you time, go through the checklist and once you ticked all the boxes and added videos testing the fix (given the Tests steps) for all platforms, proving that the PR fixes the issue -> then I will be able to start working on the reviewer checklist and move this PR a step closer to merge.
Note: For checkboxes where the PR code changes don't reach, simply tick them off without any actions. Example of checkbox given your PR: I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct), use your best judgement to decide when this is the case based on your PRs changes.

@ikevin127 Thanks for the advice!
I reviewed my PR and updated it appropriately.
I also fixed my merge conflict.
If there's anything else/any advice you might have I'm all ears!  ✅

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

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

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

We have conflicts. @adamgrzybowski would you mind reviewing this PR?

@Zakpak0 Can you please sync with main and solve the conflicts when you get a chance ? Additionally, please edit the PRs title to better reflect the issue that this is fixing since Zakpak0/bugfix issue #44587 is not specific enough.

Hi @ikevin127 I renamed the pull request to "Fix bottom tab highlight delay" following the style of one of @luacmartins PRs.
Does that work?
Additionally, I merged main into my branch and resolved any conflicts.

@Zakpak0 Thanks! We're awaiting a final review from @adamgrzybowski to sign-off on the code changes after which, if no changes are required / conflicts arise, the PR should get merged.

@WojtekBoman as you may have more context on the topic of useActiveRoute

[!note]
Some context from proposal review regarding useActiveRoute not working in narrow layout devices -> leading to the changes in this PR.

@Zakpak0 To fix the TS issues, you can run npm run typecheck while on the branch locally, once the command runs without errors you can push the fix.
Tip: If you move code around, it's good practice to run npm run prettier as well, for formatting (otherwise lint might fail).

@luacmartins  Fixed the type issues
Typescript didn't like the fact that search results could possibly be undefined. Which makes sense, because it doesn't seem like there are any handlers for that down the component tree.
So I added a guard to show the empty state if searchReults are undefined which OnyxEntry<T> defines as possible.
src/components/Search/index.tsx
    if (isLoadingItems) {
        return (
            <>
                <SearchPageHeader
                    query={query}
                    hash={hash}
                />
                <SearchRowSkeleton shouldAnimate />
            </>
        );
    }

    const shouldShowEmptyState = searchResults && SearchUtils.isSearchResultsEmpty(searchResults);

    if (shouldShowEmptyState || !searchResults) {
        return (
            <>
                <SearchPageHeader
                    query={query}
                    hash={hash}
                />
                <EmptySearchView />
            </>
        );
    }

@ikevin127 Thanks, formatted the code and run the tscheck!

@ikevin127 could you please review again given the recent changes? cc @WojtekBoman as well since you're familiar with this code

@luacmartins got it.
Synced with main
Linted, formatted, type checked and tested app.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.0.7-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/thienlnam in version: 9.0.7-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.7-8 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.8-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Blog post not appearing

Why does the blog post 00014-monal-internals-xml-query-language.md in staging not appear on our github pages branch when building the site? Other changes properly propagate to github pages an can be viewed at https://monal-im.github.io/monal-im.org/site/ (for example renaming FAQ to Wiki in our menu).

I got a notification via E-mail. I will check. 👍🏻 @tmolitor-stud-tu

Great, many thanks!! :)


Reworded localNumber docs to make more sense

For the Committer

[ ] I made sure that the site looks great and functions perfectly live
[ ] I ran splell check
[ ] I'm ready for these changes to be made live

For the Reviewer
General Review

[ ] All changes/updates requested were intentionally changed or added (no extraneous file or partial updates)
[ ] The live rendered page behaves and looks like intended.
[ ] All links work as intended. (click every link to make sure that it takes the user to the expected place).
[ ] The markdown was rendered to HTML as intended. (Tables look right, code samples are gated properly).
[ ] Any style or CSS changes are tested on multiple different pages to ensure nothing unexpected broke or changed.
[ ] I proof-read the live site (gitbook serve) and there are no oblivious splelling or grammer misteaks.

Gitbook Specific

[ ] Any new documentation pages have been added to the SUMMARY.md file so they are rendered to HTML.
[ ] Any links to other pages within this documentation use relative links ([read more about ...](guides/voice/voicemail.md)).
[ ] Gitbook can install and build the documentation (gitbook install & gitbook build)

Code Specific

[ ] All code has been tested against the live API.
[ ] All code can be run without throwing errors or new warnings.
[ ] All code is formatted correctly and consistently (spaces, tabs).
[ ] All code is legible and idiomatic to the language.
[ ] All code uses sensical method, function, and variable names.
[ ] All code samples use the appropriate syntax highlighting.
[ ] Any examples re-use same phone numbers, uuids, variable names, etc... throughout (IE don't have something like {from: '+19191231234', to: '+19191231234'} unless it's meant to show the same phone number calling/texting itself ).

TL;DR

[ ] I did these things
[ ] I'm ready for these changes to be made live

 Usabilla Feedback Item - Starting this documentation with "It is defined as" conflicts with the wording of the other documentation snippets. Also I think the wording overall could be slightly improved, maybe something like this: "The digits of a telephone number following an area code for filtering the results. Must be at least 3 digits and the areaCode field must be filled in the request."

Preview Changes at:
http://bw-apdocs-reword-localNumber-docs.s3-website-us-east-1.amazonaws.com/


[STORM-2637] fix ClassCastException in logviewer get-log-user-group-whitelist func…

In get-log-user-group-whitelist function, the getLogMetaDataFile function returns a File while the readYamlFile function requires a String.
see https://issues.apache.org/jira/browse/STORM-2637

Thanks for the patch. I just would like to see this patch against 1.x branch rather than master, given that we should review and apply #2204 to remove Clojure implementation.
Btw, if you had (or have) a chance to read logviewer clojure implementation, I would like to ask a favor with reviewing #2204.

Thanks. I will submit a patch against 1.x branch.  I am not very familiar with logviewer clojure implementation yet. But I will try and see what I can do.

Close this PR.


Authentication for push fails on MacOS

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
Description
[Add feature/bug description here]
How to reproduce

MacOS + Docker CE (current levels)
latest dockerfile-maven plugin (1.4.10)
Ensure logged in to docker (docker login) and can build/run images manually

Attempt to build/push an image using a pom utilizing this plugin:
Dockerfile builds ok
then...
[Add steps on how to reproduce this issue]
What do you expect
Dockerfile is pushed
[Describe what do you expect to happen]
What happened instead
Dockerfile is not pushed
[INFO] Successfully built planetf1/atlas-init-egeria:1.1-SNAPSHOT
[INFO]
[INFO] --- dockerfile-maven-plugin:1.4.10:push (default) @ open-metadata-docker ---
[INFO] The push refers to repository [docker.io/planetf1/atlas-init-egeria]
[INFO] Image 8ebf2c637a73: Preparing
[INFO] Image c961ebb25158: Preparing
[INFO] Image 4b7d93055d87: Preparing
[INFO] Image 663e8522d78b: Preparing
[INFO] Image 283fb404ea94: Preparing
[INFO] Image bebe7ce6215a: Preparing
[INFO] Image bebe7ce6215a: Waiting
[ERROR] denied: requested access to the resource is denied
[WARNING] An attempt failed, will retry 1 more times
org.apache.maven.plugin.MojoExecutionException: Could not push image
    at com.spotify.plugin.dockerfile.PushMojo.execute (PushMojo.java:90)
    at com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute (AbstractDockerMojo.java:265)
...
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Caused by: com.spotify.docker.client.exceptions.DockerException: denied: requested access to the resource is denied
    at com.spotify.plugin.dockerfile.LoggingProgressHandler.handleError (LoggingProgressHandler.java:105)
...
[INFO] The push refers to repository [docker.io/planetf1/atlas-init-egeria]
[INFO] Image 8ebf2c637a73: Preparing
[INFO] Image c961ebb25158: Preparing
[INFO] Image 4b7d93055d87: Preparing
[INFO] Image c961ebb25158: Waiting
[INFO] Image 663e8522d78b: Preparing
[INFO] Image 283fb404ea94: Preparing
[INFO] Image bebe7ce6215a: Preparing
[INFO] Image bebe7ce6215a: Waiting
[ERROR] denied: requested access to the resource is denied
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:44 min
[INFO] Finished at: 2019-02-21T15:58:44Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:push (default) on project open-metadata-docker: Could not push image: denied: requested access to the resource is denied -> [Help 1]
...

[Describe the actual results]
As above ... but note then that a manual push works fine:
15:58 $ docker images
REPOSITORY                           TAG                 IMAGE ID            CREATED             SIZE
planetf1/atlas-init-egeria           1.1-SNAPSHOT        066c93a04ac3        52 seconds ago      854MB
<none>                               <none>              ea3429a3a9f1        4 hours ago         854MB
ubuntu                               18.04               47b19964fb50        2 weeks ago         88.1MB
docker/kube-compose-controller       v0.4.18             47df7579c5fc        5 weeks ago         30.6MB
docker/kube-compose-api-server       v0.4.18             e73645df5dc6        5 weeks ago         47.8MB
k8s.gcr.io/kube-proxy                v1.13.0             8fa56d18961f        2 months ago        80.2MB
k8s.gcr.io/kube-controller-manager   v1.13.0             d82530ead066        2 months ago        146MB
k8s.gcr.io/kube-scheduler            v1.13.0             9508b7d8008d        2 months ago        79.6MB
k8s.gcr.io/kube-apiserver            v1.13.0             f1ff9b7e3d6e        2 months ago        181MB
k8s.gcr.io/coredns                   1.2.6               f59dcacceff4        3 months ago        40MB
k8s.gcr.io/etcd                      3.2.24              3cab8e1b9802        5 months ago        220MB
k8s.gcr.io/pause                     3.1                 da86e6ba6ca1        14 months ago       742kB
✔ ~/src/egeria/open-metadata-resources/open-metadata-deployment/docker/atlas-init [helm20|●2✚ 6⚑ 20]
15:59 $ docker push planetf1/atlas-init-egeria:1.1-SNAPSHOT
The push refers to repository [docker.io/planetf1/atlas-init-egeria]
8ebf2c637a73: Pushed
c961ebb25158: Pushed
4b7d93055d87: Mounted from library/ubuntu
663e8522d78b: Mounted from library/ubuntu
283fb404ea94: Mounted from library/ubuntu
bebe7ce6215a: Mounted from library/ubuntu
1.1-SNAPSHOT: digest: sha256:bb03dded79b4678e3aa69d4bc78a89052f67eb253fc7c7267224fbe9f061b3e6 size: 1571
✔ ~/src/egeria/open-metadata-resources/open-metadata-deployment/docker/atlas-init [helm20|●2✚ 6⚑ 20]

My docker configuration for auth includes:
16:04 $ cat ~/.docker/config.json
{
	"auths": {
		"https://index.docker.io/v1/": {}
	},
	"HttpHeaders": {
		"User-Agent": "Docker-Client/18.09.2 (darwin)"
	},
	"credsStore": "osxkeychain",
	"stackOrchestrator": "kubernetes"
}

which maybe where the error is caused.
Note that I recently raised #272 as I was originally trying to run docker remotely - which didn't work either.
Software:

docker version: [Add the output of docker version here, both client and server]

16:10 $ docker version
Client: Docker Engine - Community
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        6247962
 Built:             Sun Feb 10 04:12:39 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 04:13:06 2019
  OS/Arch:          linux/amd64
  Experimental:     true
 Kubernetes:
  Version:          Unknown
  StackAPI:         Unknown

Spotify's dockerfile-maven version: [Add dockerfile-maven version here]
1.4.10

Full backtrace
[Paste full backtrace here]

By removing
	"credsStore": "osxkeychain",

from ~/.docker/config.json, and the rerunning
docker login

The password is then stored base64 encoded instead.
I then reran the maven build, and this time the image was pushed correctly.
My conclusion is therefore that the plugin is not supportable the pluggable authentication - osx credential store here, which is in fact the default for MacOS, and quite typical for developers on this platform therefore.
Can I suggest

Some thought is given to whether this can be added into the readme as a caveat in the short term
Consideration as to whether the error message on push can be improved .include this as a possibility
looking at whether this default config can be supported (and check other platforms like windows too)

I suddenly got a similar problem but the plugin fails when building the image with the following message:
[WARNING] An attempt failed, will retry 1 more times org.apache.maven.plugin.MojoExecutionException: Could not build image     at com.spotify.plugin.dockerfile.BuildMojo.buildImage (BuildMojo.java:234) ... Caused by: com.spotify.docker.client.exceptions.DockerException: com.spotify.docker.client.shaded.com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'The': was expecting ('true', 'false' or 'null')  at [Source: (String)"The user name or passphrase you entered is not correct."; line: 1, column: 4]     at com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild (ConfigFileRegistryAuthSupplier.java:108)
After removing the "credsStore": "osxkeychain" line as proposed by planetf1, it works.

By removing
	"credsStore": "osxkeychain",

from ~/.docker/config.json, and the rerunning
docker login

The password is then stored base64 encoded instead.
I then reran the maven build, and this time the image was pushed correctly.
My conclusion is therefore that the plugin is not supportable the pluggable authentication - osx credential store here, which is in fact the default for MacOS, and quite typical for developers on this platform therefore.
Can I suggest

Some thought is given to whether this can be added into the readme as a caveat in the short term
Consideration as to whether the error message on push can be improved .include this as a possibility
looking at whether this default config can be supported (and check other platforms like windows too)

I'd just like to add that the same happened to me on Windows. Simply removing 'credsStore' property and its value, then logging in again worked flawlessly!


Currently selected tree marker doesn't look different from any other tree markers

Expected:
Currently tree selected tree should either be slightly bigger or have some sort of outline to show that this tree is selected. Open to other ideas of differentiating a selected tree
Actual:

I'm down to work on this! The circle just needs to grow correct?


Unusual capitalization of hex encoded ethereum address

I'm unclear whether the hex encoding with unusual capitalization is intended and important, or is just an unusual side-effect with no consequence.
Steps to reproduce:

navigate browser to https://www.myetherwallet.com/#view-wallet-info
select mnemonic phrase
enter abandon abandon ability
click unlock
see the first address is 0xe5815d5902Ad612d49283DEdEc02100Bd44C2772
note the unusual capitalization, eg 'DEdEc'

I would expect hex encoding would be all upper or all lower case. Is there a particular reason for the mixture of capitalization in the address string?

Capitalization simply means the address has a checksum. You should use the capitalization address because of this, but both will work.
https://github.com/ethereum/EIPs/issues/55


Up code coverage to 90%

https://codecov.io/gh/mxcl/PromiseKit/tree/83a9a93afc414ba00e653b575fae034b883d5eea/Sources

Code coverage is above 90% FYI.

Nice!


cert works but the ".well-known" folder not created...odd

I've been adding certs and noticed that the 4th site didn't have the "/.well-known" folder created but it did generate a cert properly. Seems like odd behavior. Perhaps I did something wrong but it looked like everything installed properly.

It must have been there at some point otherwise Let's Encrypt would not have issued the certificate. My theory is that LEWS deleted the folder after authorization, as it does when it detects that there are no other files in there. Nothing to worry about!


Tamil Translation Progress

Maintainer List

@pavinthan
@ratheeps
@majus28
@getCodePanda

For New Translators
To translate a page:

Check that no one else has claimed your page in the checklist and comments below.
Comment below with the name of the page you would like to translate. Please take only one page at a time.
Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find find that you can't commit any more, let the maintainers know so they can assign the page to someone else.
For Maintainers
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

[ ] Home Page (@tesseralis) #1

When PRs are merged, make sure to mark that page as completed!
Core Pages
To do before releasing as an "official" translation. Please translate these pages first.

[x] Home Page (@pavinthan)
[ ] Tutorial (@majus28)

Basics

[ ] Hello World (@sarvabowmen, @cvaijothi)
[ ] Introducing JSX (@sbkrish)
[ ] Rendering Elements (@Madhust)
[x] Components and Props (@Madhust)
[ ] State and Lifecycle (@Ananthakr)
[ ] Handling Events (@Pachiyappan)
[ ] Conditional Rendering (@dhirajsriram)
[ ] Lists and Keys (@puviz)
[x] Forms (@nivedha1)
[ ] Lifting State Up (@satheeshwaran)
[ ] Composition vs Inheritance (@mtamilcse92)
[ ] Thinking in React (@logesh-kumar)

API Reference

[ ] React
[ ] React.Component
[ ] ReactDOM
[ ] ReactDOMServer
[ ] DOM Elements
[ ] SyntheticEvent
[ ] Test Utilities
[ ] Shallow Renderer
[ ] Test Renderer
[ ] JS Environment Requirements
[ ] Glossary

Navigation
These are the navigation links that appears in the sidebar. Possibly wait until
the corresponding sections are translated to do these.

[ ] tutorial/nav.yml (@pavinthan)
[ ] docs/nav.yml (@pavinthan)

Next Steps
These are the next most important translations, ordered by importance:
Installation

[x] Getting Started (@cvaijothi)
[ ] Add React to a Website (@praveenscience)
[ ] Create a New React App (@praveenscience)
[x] CDN Links (@rajakvk)

Hooks
Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

[ ] Introducing Hooks (@klsv07)
[ ] Hooks at a Glance (@kasthuriraajan)
[ ] Using the State Hook (@KiruthikaThangamuthu)
[ ] Using the Effect Hook
[ ] Rules of Hooks (@mithelan)
[ ] Building Your Own Hooks (@mtamilcse92)
[ ] Hooks API Reference (@pradheepap)
[ ] Hooks FAQ

Warnings
These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.

[ ] dont-call-proptypes
[ ] invalid-aria-prop
[ ] invalid-hook-call-warning
[ ] legacy-factories
[ ] refs-must-have-owner
[ ] special-props
[ ] unknown-prop

Advanced Guides

[ ] Accessibility (@Elcomerz)
[ ] Code-Splitting
[ ] Context
[ ] Error Boundaries
[ ] Forwarding Refs
[ ] Fragments
[ ] Higher-Order Components (@saran-io)
[ ] Integrating with Other Libraries
[ ] JSX In Depth
[ ] Optimizing Performance
[ ] Portals
[ ] React Without ES6
[ ] React Without JSX
[ ] Reconciliation
[ ] Refs and the DOM
[ ] Render Props
[ ] Static Type Checking
[ ] Strict Mode
[ ] Typechecking With PropTypes
[ ] Uncontrolled Components
[ ] Web Components

FAQ

[ ] APIs and AJAX
[ ] Babel, JSX, and Build Steps
[ ] Passing Functions to Components
[ ] Component State
[ ] Styling and CSS
[ ] File Structure
[ ] Versioning Policy
[ ] Virtual DOM and Internals

Contributing
Priority: Low

[ ] How to Contribute
[ ] Codebase Overview
[ ] Implementation Notes
[ ] Design Principles

Components
Components in src/components that have some text in them.

[ ] CodeEditor
[ ] CodeExample
[ ] ErrorDecoder
[ ] LayoutFooter
[ ] LayoutHeader
[ ] MarkdownPage

Additional Translations
These are not the primary translation targets.

[ ] Blog
[ ] Community (@pavinthan)

@pavinthan, @ratheeps, @majus28, @GetCodePanda please use this issue to keep track of your progress! Let me know if you need any help or have any questions.

Sure @tesseralis and thank you for your support 🙏

Sure @tesseralis  Thank you for your support.

@pavinthan, @ratheeps, @majus28, @GetCodePanda how's it going? Have you started working on translating any of the pages? Please let me know if you need any help.

@tesseralis Yah, we are working on Home page content review for now, let you know once we done it and if any needs.

Hey guys, I would like to contribute, can i pick one?

@sarvabowmen go ahead and choose something under "core pages"

Thanks @sarvabowmen as @tesseralis suggested please select any of core pages and let us know, and please use https://react-translations.slack.com this slack workspace to keep in touch.

Very much interested to contribute. How to do i get access to the  slack board ?

@greensand please select any "Basics" pages to start contribute and Here's the link for the invitations: https://rt-slack.herokuapp.com

Sure
On Tue, Mar 5, 2019 at 3:41 PM Pavinthan<EMAIL_ADDRESS>wrote:

@greensand https://github.com/greensand please select any "Basics"
pages to start contribute and Here's the link for the invitations:
https://rt-slack.herokuapp.com
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/reactjs/ta.reactjs.org/issues/1#issuecomment-469728760,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ75uYC5NIfFtIpqiuO24q3JSKwDOli4ks5vTpA4gaJpZM4azO0g
.

@pavinthan @tesseralis i can take the home page, can you please update the list

@pavinthan @tesseralis i can take the Hello world, can you please update the list

@sarvabowmen The page is assigned to you.
Thanks.

Hi,
I would like to contribute to this translation effort. I can take the CDN Links page under Installation section as my first task.

@m-sureshraj sure go head with that please. thanks 🙏

Thanks
On Wed, Mar 6, 2019 at 2:28 AM majus28<EMAIL_ADDRESS>wrote:

@pavinthan https://github.com/pavinthan @tesseralis
https://github.com/tesseralis i can take the Hello world, can you
please update the list
@sarvabowmen https://github.com/sarvabowmen The page is assigned to you.
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/reactjs/ta.reactjs.org/issues/1#issuecomment-469941981,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ75uTUBz3EOP94tR0CFx_glmGP6K8IKks5vTyfJgaJpZM4azO0g
.

@pavinthan I would like to contribute. Could you please assign me the Basic -> Components and Props topic to me?

thanks @Madhust, go ahead with that please.

Hi @pavinthan ,
I would like to contribute in this process. How can I join with this community?
Thanks.

Hi @sbkrish
Please fork this repository, and update your changes, then create the pull request.
Thanks

Thanks @ratheeps , I would like to take Introducing JSX from Basics.

Thanks, @sbkrish,  go ahead with that, please.

Hi. I wish to contribute. I wish to take up Forms topic from Basics.

Hi @nivedha1
Thanks for your shown interesting, go ahead with that, please

Hi Team,
Very much interested to contribute, How to join this community.

Hey @velmuruganfrontend, thanks for your interest, could you please pick any unassigned items from the list and start to contribute.

Hi @tesseralis, I am interested and can start contributing to one of the pages. May I start with the following pages?

Add React to a Website
Create a New React App

Let me know. Also, I am Praveen Kumar Purushothaman. 😊

@praveenscience please go go ahead with your selections, thanks.

Hi, I am interested and would like to contribute.

@pavinthan Can you invite me to the React JS slack group?

@prasathbuilds  you could select any unassigned items from this issue description to start translate and let us know what is your choose to pin the item for you.
@praveenscience here's the link for the invitations: https://rt-slack.herokuapp.com
Thanks

@pavinthan I did try that, but it gave me this error:

SlackIn is a good alternative I suppose.

@tesseralis Please update the Add React to a Website to in progress. Will try to deliver both by Monday. 😇

@tesseralis Please update the Add React to a Website to in progress. Will try to deliver both by Monday. 😇
cc @pavinthan

Hey @praveenscience thanks It's already assigned to you. and will update the slack issue.

@praveenscience try this https://rt-slack-invite.herokuapp.com

Hi @pavinthan I would like to contribute to the topic Thinking in React.

Hi @logesh-kumar
Thanks for your shown interesting, go ahead with that, please

@pavinthan Please assign Rendering Elements to me.

Hey guys, I would like to contribute to the translation. Can I pick a segment?
Mass pannuvom (Let's rock in Tamil) :p

@dhirajsriram Sure, please pick anything unassigned item in the description list and let us know :)

@pavinthan Can I pick "Conditional Rendering" ?

Hi @dhirajsriram
Go ahead with that, please
Thanks.

Hi,
I would like to contribute as well. I like to take ' Introducing Hooks' first.
I'm unable to click the checkbox to assign.
Please let me know if u can take the same and assign it to me
Thanks,
Murali.

thanks @klsv07, please start to work on it, we will check once you done.

@pavinthan I would like to pick 'State and Lifecycle'.

Hi @Ananthakr
Thanks for your shown interesting,
Please start to work on "State and Lifecycle" and have updated the checklist.
Thanks

@pavinthan Can i Pick Composition vs Inheritance ?

@mtamilcse92 sure, thanks

Hey guys, I would like to contribute, Can i pick Handling Events ?

@Pachiyappan Yes please

@pavinthan Can i pick Building Your Own Hooks ?

@mtamilcse92 Yes please

@pavinthan I would like to pick React. Can i pick?

Yes, @Pachiyappan please

@pavinthan  @ratheeps @majus28  @GetCodePanda I would like to contribute, can I take up anything under Basics?

@satheeshwaran Yes, please pick anything under Basics and let us know, we will mark it for you.
thanks 🙂

@pavinthan Let me take Lifting State Up under basics.

Hi @satheeshwaran please take it, I will mark it for you.

Hi @pavinthan , @ratheeps , @tesseralis
I would like to contribute some translations so which one can I take?

Hi @kasthuriraajan,
Thanks for your shown interestingly.
Would you pick one under "API Reference"?
Once you picked let us know we will mark it for you.
Thanks.

Hi @ratheeps ,
I will take "Hooks at a Glance" under "Hooks". Could you please assign me to that task.
Thanks.

Hello @ratheeps,
I can pick up  Higher-Order Components under advance concepts. Could you put that under my bucket.

@saran-io Yes sure

@saran-io Yes sure

Thanks.

Hi all, I would like to contribute. Can I pick "Using the State Hook" under "Hooks"?

@KiruthikaThangamuthu Sure Please,
Thank you

Hi all, I would like to contribute, Can I pick "Hooks API Reference"?

Hi all, I would like to contribute, Can I pick "Hooks API Reference"?

Hi, I Would like to contribute to the Accessibility page in  Advanced Guides. Shall I?

Hi, I Would like to contribute to the Accessibility page in  Advanced Guides. Shall I?

Hi, would like to contribute, can i pick Rules of Hooks ?

@pradheepap @Elcomerz and @mithelan sure Please,

Hi all,
I would like to contribute to this translation effort

Yes we do

Yes we do
On Mon, Aug 1, 2022 at 11:43 AM Sanjaiyan Parthipan <
@.***> wrote:

Yes we do
#206 (comment)
https://github.com/reactjs/ta.reactjs.org/pull/206#issue-1323881604
—
Reply to this email directly, view it on GitHub
https://github.com/reactjs/ta.reactjs.org/issues/1#issuecomment-1200756449,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEZVBAZNYKDAN4FPVWTM5ALVW5TJDANCNFSM4GWM5UQA
.
You are receiving this because you were mentioned.Message ID: <reactjs/ta.
@.***>

Hi guys i would like to contribute in the glossary can you please assign me

It looks like this translation has stalled, and is now very outdated.
I'm going to archive this repo, but if someone wants to pick up, please start a new effort.


Fix logic corner case

When a PR with a lower ID than an already merged one is merged, it's considered a first PR

fixed


Added logging to list the top tables in the replication backlog

This will allow us to debug or improve issues with replication
by determining which tables are contributing most to the
backlog.
@gtanzillo @jrafanie

:+1:  Looks good!

:+1:

:cake:


Nuxt Programmatic: Renderer is loaded but not all resources are unavailable! Please check ...

Version
v2.6.2
Reproduction link
https://xxx.com
Steps to reproduce
Hey, bare server and running into this issue when running nuxt programmatically:
server.js
const { Nuxt, Builder } = require('nuxt'),
  config = require('./nuxt.config'),
  app = require('express')();

const nuxt = new Nuxt({...config, ...{ dev: !isProd }})
app.use(nuxt.render)
if (!isProd) {
  const builder = new Builder(nuxt)
  builder.build()
}
app.listen(3000)

I run nuxt build which results in entrypoint files: Entrypoint app = 32847580a74f1882ab1a.js<PHONE_NUMBER>05b2aff141.js ff5b142fabf2940dccee.js cb8be830c6794eb9ee84.js which.. are somewhat meaningless to me, I'm guessing they're handled internally (?).
I then run:
NODE_ENV=production node server.js, and try to navigate to localhost:3000/
The error occurs:
Renderer is loaded but not all resources are unavailable! Please check /.nuxt/dist/server existence.
I can confirm that a server folder exists. Am I doing anything obviously stupid? Thank you.
What is expected ?
The page should render.
What is actually happening?
An error is thrown.

This bug report is available on Nuxt community (#c9064)

Hi. Can you please share nuxt.config? Also please ensure 2.6.2 is installed by checking node_modules/nuxt/package.json

Heya, sure, I'm on 2.6.2
Here's the config:
require('app-module-path').addPath('./');
const session = require('express-session'),
  MongoStore = require('connect-mongo')(session),
  mongoose = require('mongoose'),
  routes = require('./routes'),
  path = require('path')

module.exports = {
  serverMiddleware: [
    session({
      secret: 'abc',
      cookie: { maxAge:<PHONE_NUMBER>, secure: process.env.NODE_ENV == 'production' },
      saveUninitialized: true,
      store: new MongoStore({
        mongooseConnection: mongoose.connection,
        autoRemove: 'interval',
        autoRemoveInterval: 3600000
        })
    }),
    { path: '/', handler: routes }
  ],
  head: {
    title: 'App',
    meta: [
      { charset: 'utf-8' },
      { name: 'viewport', content: 'width=device-width, initial-scale=1' },
      { hid: 'description', name: 'description', content: 'Nuxt.js project' }
    ],
    link: [
      { rel: 'stylesheet', href: "https://fonts.googleapis.com/css?family=Heebo:100,300,400,500,700,800,900"},
      { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' }
    ],
    script: []
  },
  plugins: ['~/plugins/color'],
  env: {
    nodeEnv: process.env.NODE_ENV || 'dev'
  },
  generate: {
  },
  build: {
    'html.minify': {
    },
    extend (config, { isDev, isClient }) {

      config.node = {

          net: 'empty',
          fs: "empty"
      };

    }
  }
}

Thanks for looking.

Is this problem solved? I also have the same problem.

Please ensure that no errors happen during nuxt build and also NODE_ENV detection is correct.
I've created a repository: https://github.com/pi0/nuxt-programatic-example
It is working fine against nuxt 2.6.x.

Same issue:

nvm v8.16.0
nuxt  2.4.0
firefbase 6.7.0

npm install -g firebase-tools
Lastest cloud-functions-emulator:
    "@google-cloud/functions-emulator": "git://github.com/GoogleCloudPlatform/cloud-functions-emulator.git#098e253188d8caa706da08350483468d60f0c049"

Error
info: IN New Nuxt Trial:
error:
15:32:29  ERROR  Renderer is loaded but not all resources are unavailable! Please check /Users/greg/code/perso/nuxt2-ssr-firebase/prod/server/nuxt/dist/server existence.

  at VueRenderer.renderRoute (node_modules/@nuxt/vue-renderer/dist/vue-renderer.js:2817:19)
  at Server.renderRoute (node_modules/@nuxt/server/dist/server.js:811:38)
  at nuxtMiddleware (node_modules/@nuxt/server/dist/server.js:124:26)
  at call (node_modules/connect/index.js:239:7)
  at next (node_modules/connect/index.js:183:5)
  at servePlaceholderMiddleware (node_modules/serve-placeholder/src/index.js:29:16)
  at call (node_modules/connect/index.js:239:7)
  at next (node_modules/connect/index.js:183:5)
  at next (node_modules/connect/index.js:161:14)
  at node_modules/@nuxt/server/dist/server.js:555:5

info: Execution took 4 ms, user function completed successfully```

Would love to maybe at least get some hints from the dev team as to what may lead to this error so I can try to debug.

After updating to the 2.6.* version I am having the exact same error message.

I think my problem may have been that I was using yarn install to add packages but then was using nuxt build rather than yarn build. It would be nice if there was an intelligible difference between these two commands or some disclaimers that using yarn for dependency management will lead to the nuxt command not working. These commands are commingled in the documents and it lends to a poor developer experience.

Other than that, great project!

Also, I get this error if the nuxt.builder runs after yarn build runs. Seems like nuxt.builder corrupts the production files.

I am having the same error.
I use Firebase and my ssr function is
const functions = require('firebase-functions');
const { Nuxt } = require('nuxt');
const express = require('express');
const app = express();

const config = {
  dev: false,
  buildDir: '.nuxt',
  build: {
    publicPath: '/assets/'
  }
};
const nuxt = new Nuxt(config);

function handleRequest(req, res) {
  res.set(
    'Cache-Control',
    `public, max-age=${365 * 24 * 60 * 60}, s-maxage=${365 * 24 * 60 * 60}`
  );
  return new Promise((resolve, reject) => {
    nuxt.render(req, res, promise => {
      promise.then(resolve).catch(reject);
    });
  });
}

app.use(handleRequest);
exports.ssr = functions.https.onRequest(app);

I am currently on 2.6.3 but the issue also occurred on 2.6.2
I use npm and not yarn.

I also encountered such problems. Is there any way to solve them now?

This error mostly happens when using a custom server.js does not match the configuration of nuxt.config.js. buildDir, if specified, should point to correct build dir and mode should not be set to spa from nuxt.config or using --spa.

having the same error

@nikkwong @yangfandashuaige @PatrickLumenus  @SinPP @conlywork Please provide the following information so we can help to fix your project otherwise we can't!

Nuxt version
Deployment target (AWS, Local, VPS, ..)
Custom server.js file

I have the same issue

Nuxt 2.6.2
Deployment target - GCP
Not a custom file

@pktippa how do you deploy on google cloud without custom? 🙈 Can you please share nuxt config and package.json?

nuxt.config.js
const pkg = require('./package')

module.exports = {
  mode: 'universal',

  /*
  ** Headers of the page
  */
  head: {
    title: pkg.name,
    meta: [
      { charset: 'utf-8' },
      { name: 'viewport', content: 'width=device-width, initial-scale=1' },
      { hid: 'description', name: 'description', content: pkg.description }
    ],
    link: [
      { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' },
      { rel: 'stylesheet', href: 'https://rsms.me/inter/inter.css' }
    ]
  },

  /*
  ** Customize the progress-bar color
  */
  loading: { color: '#fff' },

  /*
  ** Global CSS
  */
  css: [
    '~/assets/css/tailwind.css'
  ],

  /*
  ** Plugins to load before mounting the App
  */
  plugins: [
    {src: "~/plugins/vue2-google-maps.js"}
  ],

  /*
  ** Nuxt.js modules
  */
  modules: [
    // Doc: https://axios.nuxtjs.org/usage
    '@nuxtjs/axios'
  ],
  /*
  ** Axios module configuration
  */
  axios: {
    // See https://github.com/nuxt-community/axios-module#options
  },

  /*
  ** Build configuration
  */
  build: {
    /*
    ** You can extend webpack config here
    */
    extend(config, ctx) {
    },
  }
}

package.json
{
  "name": "xxx",
  "version": "1.0.0",
  "description": "XXX",
  "author": "XXX",
  "private": true,
  "scripts": {
    "dev": "cross-env NODE_ENV=development nodemon server/index.js --watch server",
    "build": "nuxt build",
    "start": "cross-env NODE_ENV=production node server/index.js",
    "generate": "nuxt generate"
  },
  "dependencies": {
    "@nuxtjs/axios": "^5.3.6",
    "chart.js": "^2.8.0",
    "cross-env": "^5.2.0",
    "express": "^4.16.4",
    "nuxt": "^2.4.0",
    "vue2-google-maps": "^0.10.6"
  },
  "devDependencies": {
    "autoprefixer": "^8.6.4",
    "nodemon": "^1.18.9",
    "tailwindcss": "^0.7.0"
  }
}

custom index.js
const express = require('express')
const consola = require('consola')
const { Nuxt, Builder } = require('nuxt')
const app = express()

// Import and Set Nuxt.js options
let config = require('../nuxt.config.js')
config.dev = !(process.env.NODE_ENV === 'production')

async function start() {
  // Init Nuxt.js
  const nuxt = new Nuxt(config)

  const { host, port } = nuxt.options.server

  // Build only in dev mode
  if (config.dev) {
    const builder = new Builder(nuxt)
    await builder.build()
  } else {
    await nuxt.ready()
  }

  // Give nuxt middleware to express
  app.use(nuxt.render)

  // Listen the server
  app.listen(port, host)
  consola.ready({
    message: `Server listening on http://${host}:${port}`,
    badge: true
  })
}
start()

@pi0 The issue is not because of nuxt, we are not running the build before deploying to GCP. After we ran "npm run build" and do a deploy it is working perfectly fine. thanks for time.

v2.8.1 seem fix this issue.

Closing here :relaxed:

I'm having this issue on 2.8.1 deploying to AWS ElasticBeanstalk. Did anyone figure out what the problem was?

I've had this issue with AWS Elastic Beanstalk. It looks like EB is not running npm build -- there could be a way to do this with the EB settings, but I have not figured it out yet. So what I did is to uncomment .nuxt within .gitigmore, run npm build, commit to git and then run eb deploy.  In effect, I'm deploying the app together with the .nuxt directory. It worked.

Experiencing this issue as well on heroku. I've been stuck on it for days.
@pi0 is correct that it may involve custom server - but any additional insights as to why would be super helpful.
@manniL could you please reopen this issue? I don't think v2.8.1 fixed it as I'm running v2.11.0
I can't imagine npm run dev is a wise solution for running on the server.

@shi11 It is definitely not an issue with nuxt but would be happy helping if you can share repo with me 😊

Thanks @pi0 however I just fixed it :) In my case, I was missing the heroku config var HOST=<IP_ADDRESS> which I discovered after rereading this: https://nuxtjs.org/faq/heroku-deployment/
...because I was missing that, the error messages made it seem like it was related to me setting rootDir=v2. When I changed rootDir='' it would build successfully but then I'd get the runtime error Renderer is loaded but...From there it became a spiral of trial and error. But now it's fixed and I'm glad I asked for help ;)

Ok wait, I fixed it but I see what's going on, perhaps you can help @pi0 ?

The server build fails when I set rootDir=v2
When I set rootDir=''the server build succeeds however then I get the "Renderer is loaded but..." error
With the server now built, I change rootDir back to rootDir=v2 and the app works.

Any suggestions? I guess I could change the  env var during preInstall and postInstall...

@shi11 With the provided information all can guess is that error is happening because rootDir when the running server is pointing to a wrong directory so the server fails to load resources. If you use a custom destination is a better idea to always provide rootDir

This is still an issue. Newly generated project from latest. npm run dev works, but npm start fails (after npm run build)

Same pb... ok in dev, error 500 in production...

I'm experiencing the same issue now.
It started with failing to load resources, both locally and in test-environment, and inspecting the resources in Network tab in devtools, some of the files were up to 1MB. Optimizing the chunks by extending the build solved the problem locally, but now I'm experiencing the same issues as described in this thread: I get a 500 error when loading the page-resource, and have traced the issue back to NuxtServerInit failing.
Please help, I have been scratching my head on this for three days now. Posting my nuxt-config.js and package.json below:
nuxt.config.js
`const pkg = require('./package');
const compute = require('./config-util');
const appConfig = compute.getAppConfig();
const basePath = compute.getBasePath(appConfig);
const nodeEnv = process.env.NODE_ENV;
const isDevelopment = nodeEnv === 'development';
console.log('Node environment ' + nodeEnv);
console.log('App type ' + process.env.appType);
console.log('Base path: ', basePath);
module.exports = {
mode: 'universal',
/*
** Headers of the page
*/
head: {
title: pkg.name,
htmlAttrs: {
lang: 'no'
},
meta: [
{
charset: 'utf-8'
},
{
name: 'viewport',
content: 'width=device-width, initial-scale=1, maximum-scale=1'
},
{
hid: 'description',
name: 'description',
content: pkg.description
}
],
link: [
{
rel: 'icon',
type: 'image/x-icon',
href: 'favicon.ico'
}
]
},
/*
** Customize the progress-bar color
*/
loading: '~/components/Loading.vue',
/*
** Global CSS
*/
css: [],
styleResources: { less: '~assets/vars/variables.less' },
devtool: 'source-map',
/*
** Plugins to load before mounting the App
*/
plugins: [
'~/plugins/ratel-plugin',
'~/plugins/axios-plugin',
'~/plugins/notification-plugin',
{
src: '~/plugins/touch-plugin',
ssr: false
},
// {
//   src: '~/plugins/tracking-plugin',
//   ssr: false
// },
'~/plugins/vue-xpf-plugin',
'~/plugins/modal-plugin',
{
src: '~/plugins/vue-rx-plugin',
ssr: false
}
],
/*
** Nuxt.js modules
/
modules: [
// Doc: https://axios.nuxtjs.org/usage
'@nuxtjs/axios',
'@nuxtjs/style-resources',
'@nuxtjs/svg',
'nuxt-device-detect'
],
/
** Axios module configuration
*/
axios: {
browserBaseURL: isDevelopment ? 'http://localhost' : basePath,
https: !isDevelopment
},
env: {
isDev: isDevelopment,
appName: appConfig.sys
},
/*
** render (preload & prefetch)
*/
render: {
bundleRenderer: {
shouldPrefetch: (file, type) => {
if (type === 'script') {
const ignoredRoutes = ['user'];
if (ignoredRoutes.some(r => file.includes(r))) {
return false;
}
}
return ['script', 'style', 'font'].includes(type);
}
}
},
router: {
base: basePath + '/'
// extendRoutes(routes, resolve) {
//   routes.push({
//     name: 'id',
//     path: '/:id',
//     component:
//       process.env.appType === 'v2'
//         ? resolve(__dirname, 'pages/v2/index.vue')
//         : resolve(__dirname, 'pages/v1/index.vue')
//   });
// }
},
/*
** Build configuration
/
build: {
/
** You can extend webpack config here
*/
extend(config, ctx) {
// Run ESLint on save
if (ctx.isDev && ctx.isClient) {
config.devtool = '#source-map';
config.module.rules.push({
enforce: 'pre',
test: /.(js|vue)$/,
loader: 'eslint-loader',
exclude: /(node_modules)/
});
}
  if (ctx.isDev) {
    config.devtool = ctx.isClient ? 'source-map' : 'inline-source-map';
  }
  config.output.publicPath = './_nuxt/';
  config.module.rules.push({
    test: /\.hbs$/,
    loader: 'handlebars-template-loader',
    query: {
      runtimePath: 'handlebars/runtime'
    }
  });
  const svgRule = config.module.rules.find(rule => rule.test.test('.svg'));
  svgRule.test = /\.(png|jpe?g|gif|webp)$/;
  if (ctx.isClient) {
    config.optimization.splitChunks.maxSize = 200000;
  }
},
postcss: {
  preset: {
    autoprefixer: {
      overrideBrowserslist: [
        'defaults',
        'ie >= 9',
        '> 5%',
        'last 2 versions'
      ],
      grid: true
    }
  }
},
transpile: ['@mtw/vue-xpf'],
cache: true,
hardSource: true

}
};
`
package.json
{   "name": "*****",   "engines": {     "node": ">=8"   },   "version": "1.0.0",   "description": "***",   "author": "***",   "private": true,   "scripts": {     "dev": "cross-env NODE_ENV=development nodemon --inspect --preserve-symlinks server/index.js --watch server --watch nuxt.config.js",     "dev-backup": "cross-env NODE_ENV=development USE_BACKUP=true nodemon --inspect --preserve-symlinks server/index.js --watch server --watch nuxt.config.js",     "take-backup": "cross-env NODE_ENV=development TAKE_BACKUP=true nodemon --inspect --preserve-symlinks server/index.js --watch server --watch nuxt.config.js",     "dev-v2": "cross-env NODE_ENV=development appType=v2 nodemon --inspect --preserve-symlinks server/index.js --watch server --watch nuxt.config.js",     "dev-v2-backup": "cross-env NODE_ENV=development USE_BACKUP=true appType=v2 nodemon --inspect --preserve-symlinks server/index.js --watch server --watch nuxt.config.js",     "v2-take-backup": "cross-env NODE_ENV=development TAKE_BACKUP=true appType=v2 nodemon --inspect --preserve-symlinks server/index.js --watch server --watch nuxt.config.js",     "build": "nuxt build --no-lock",     "build-v2": "cross-env appType=v2; nuxt build --no-lock",     "postinstall": "npm run build",     "start": "cross-env NODE_ENV=test node server/index.js",     "start-v2": "cross-env NODE_ENV=test appType=v2; node server/index.js",     "generate": "nuxt generate",     "lint": "eslint --ext .js,.vue --ignore-path .gitignore .",     "precommit": "npm run lint",     "dev-debug": "node --inspect node_modules/.bin/nuxt",     "port-forward": "bash ./elastic-port-forward.sh",     "port-forward-itest": "bash ./elastic-port-forward.sh itest"   },   "dependencies": {     "@***/apigee-axios": "^1.1.2",     "@***/config": "^1.0.2",     "@***/logger": "1.0.11",     "@***/vue-xpf": "^1.0.52",     "@***/zipkin-helper": "^2.0.2",     "@nuxtjs/auth": "^4.5.3",     "@nuxtjs/axios": "^5.3.6",     "@nuxtjs/style-resources": "^0.1.2",     "body-parser": "^1.18.3",     "cookie-parser": "^1.4.4",     "cors": "^2.8.5",     "cross-env": "^5.2.0",     "express": "^4.16.4",     "fluture": "^11.0.3",     "fluture-sanctuary-types": "^4.1.1",     "fuzzyset.js": "0.0.8",     "handlebars": "^4.1.0",     "handlebars-template-loader": "^1.0.0",     "nuxt": "^2.12.2",     "nuxt-device-detect": "^1.1.5",     "prometheus-api-metrics": "^2.2.2",     "ramda": "^0.26.1",     "rxjs": "^6.5.3",     "sanctuary": "^2.0.0",     "sanctuary-def": "^0.20.0",     "tn-xpf": "^4.1.505",     "vue-rx": "^6.2.0",     "vue-slide-up-down": "^1.7.2",     "vue2-touch-events": "^2.0.0"   },   "devDependencies": {     "@nuxtjs/eslint-config": "^0.0.1",     "@nuxtjs/svg": "^0.1.11",     "babel-eslint": "^8.2.1",     "eslint": "^5.0.1",     "eslint-config-prettier": "^3.1.0",     "eslint-config-standard": ">=12.0.0",     "eslint-loader": "^2.0.0",     "eslint-plugin-import": ">=2.14.0",     "eslint-plugin-jest": ">=21.24.1",     "eslint-plugin-node": ">=7.0.1",     "eslint-plugin-prettier": "2.6.2",     "eslint-plugin-promise": ">=4.0.1",     "eslint-plugin-standard": ">=4.0.0",     "eslint-plugin-vue": "^5.0.0",     "less": "^3.9.0",     "less-loader": "^4.1.0",     "nodemon": "^1.18.9",     "prettier": "1.14.3"   } }


unify property handling, fixes #16 - WARNING: breaks API

uses _parse_properties_element to parse tile properties. The properties are then stored as Properties object, no longer as List[Property], see #16 for reasoning.
As the type Property is no longer needed, it has been removed.

I will need some time to look this over, and I'll need to consult with @pvcraven about it, as he is the one who actually uses this thing these days (though I suddenly find myself much more available to work on this)

I'm closing this as the JSON version re-write has been merged into master and is being released as version 1.0.0 so this is completely incompatible now anyways.


definition file for angular-load

Hi,
Thanks for your great library.
Would it be possible to supply a typescript definition file for this library?
This would be great :+1:
There is currently a repository of definition files at:
https://github.com/DefinitelyTyped/DefinitelyTyped
Thanks,
David

Hi, thanks for the kind words :-)
You are invited to create one and send a PR
Thanks!

Hi Uri,
Here is the definition file
/// <reference path="../angularjs/angular.d.ts" />

declare module angular.load {

    interface IAngularLoadService {
        loadScript(url:string): ng.IPromise<any>;
        loadCss(url:string): ng.IPromise<any>;
    }

}

It works when under the typings directory we make a library angular-load.
I would prefer not to commit it directly to definitelytyped because this means that every time the project api is changed, i will have to update it there.
What do you think?
Thanks :-)

Hi David,
Feel free to send a PR to definitely-typed. If the API will ever change, I will be able to submit a PR and explain that I am the project maintainer, so no worries :)
Thanks!

Hi,
Here is the pull request https://github.com/DefinitelyTyped/DefinitelyTyped/pull/8316
Yom Tov,
David

Wonderful, thanks!


Add missing init files

Reference Issues/PRs
Related to #1661
What does this implement/fix? Explain your changes.

add missing init files identified via: find sktime -type d '!' -exec test -e "{}/__init__.py" ";" -not -path "**/__pycache__" -not -path "**/datasets/data*" -print

This is failing as expected because these tests weren't picked up previously.

Should be good to go now since #1661 has been merged

find sktime -type d '!' -exec test -e "{}/__init__.py" ";" -not -path "**/__pycache__" -not -path "**/datasets/data*" -print

Excellent! Could we also add this as a CI check? I.e., that there are no missing init files? A check based on this line should work?
FYI @lmmentel

Can we wait before we merge to see if #1699 fails without the init files?

of course

merged, since #1699 failed as expected.


replace manual return with req lib for get_item

Hey - did you test this and whether you can use the return values as JSON? I don't remember exactly, but in some cases I've had to do string replaces to fix JSON (the .replace parts)

Hey - did you test this and whether you can use the return values as JSON? I don't remember exactly, but in some cases I've had to do string replaces to fix JSON (the .replace parts)

I found some problems with old code because it can't use json.loads() for parsing data
ex. Parse error: Expecting value: line 1 column 133 (char 132)
if I replaces it to ret.text it can resolve that problem.
However, thehive4py always return json format and other function in thehive app return ret.text too.


[ISSUE #11900] part1 init dubbo-wasm-rpc-api module

What is the purpose of the change
see #11900 , this is part1, if it's ok, I will try other SPI interface.
Brief changelog
Verifying this change
see dubbo-wasm/dubbo-wasm-rpc-api/src/test/README.md and org.apache.dubbo.wasm.rpc.AbstractWasmFilterTest

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Please move this implementation to dubbo-spi-extensions


feat(Examples): I2S_DMA_Target example added to the MAX32690 examples

I2S DMA example project for the MAX32690, utilizing MAX9867 codec on the EV-Kit

Waiting on https://github.com/analogdevicesinc/msdk/pull/1065 first