GUI.Menu causes crash

Hi,
I recently updated to the latest Version of pebblejs and now I am having a big problem. My application  crashes when I try to display a GUI.Menu() with the following content.
{
    "sections": [
        {
            "title": "Controls",
            "data": {
                "type": "controls"
            },
            "items": [
                {
                    "title": "name",
                    "data": {
                        "type": "command",
                        "cmd": "cmd",
                        "icon": "icon"
                    }
                }
            ]
        }
    ],
    "fullscreen": true,
    "backgroundColor": "white",
    "textColor": "black",
    "highlightBackgroundColor": "black",
    "highlightTextColor": "white",
    "scrollable": false,
    "id": 2
}

The errormessage I am getting is:
[INFO    ] E ault_handling.c:78 App fault! {133215f0-ce20-4c05-997b-3c9be5a64e5b} PC: 0x806bdd2 LR: 0x8fd
[WARNING ]    Program Counter (PC):  0x806bdd2 ???
[WARNING ]      Link Register (LR):      0x8fd /Users/MyName/AnfFolder/MyApp/build/../src/simply/simply_menu.c:441
[INFO    ] JS: stopping app: 133215F0-CE20-4C05-997B-3C9BE5A64E5B MyApp

Does this have something to do with the default properties:

"backgroundColor": "white",
"textColor": "black",
"highlightBackgroundColor": "black",
"highlightTextColor": "white",
"scrollable": false,
"id": 2

Aha! Turns out the last our was wasted… ;-)
I agree. As soon as I want to open a UI.Menu, the app crashes. But only on the watch, not in the emulator. In there, everything is working fine.
I can even reproduce this with the Pebble.js "Hello World!" application.

As soon as I update handle_menu_props_packet (simply_menu.c) and comment out the following, everything (except colors, I guess :smirk:) works again:
  //menu_layer_set_highlight_colors(simply->menu->menu_layer.menu_layer,
  //                                gcolor8_get(packet->highlight_background_color),
  //                                gcolor8_get(packet->highlight_text_color));
  //menu_layer_set_normal_colors(simply->menu->menu_layer.menu_layer,
  //                             gcolor8_get(packet->background_color),
  //                             gcolor8_get(packet->text_color));

@FabianBeiner @idoodler Can you see if this issue persists in my fork? https://github.com/fletchto99/pebblejs
This issue should have been fixed in my pending pull request: #65

@fletchto99 Yes, works for me then. Red menu on my wrist, lovely. :smile:

Really sorry about this. I've looked into the issue and the problem has to do with the virtual window stack. In my attempt to make "show" and "hide" semantics simple, menu doubly "shows" itself when it shouldn't, since there is a brief period where the JS side thinks the menu is shown when it hasn't. It checks if it's at the top of the stack, but the check is moot since the window stack calls "show" after the WindowStack already modifies its stack. The fix in #65 is sufficient before I try refactoring how Menu interacts with WindowStack.
The emulator seems to be more lax with null pointers, which is another issue that'll have to be looked into, and why this was overlooked.
Thanks again @fletchto99 for fixing this!

@Meiguro I just updated to your latest commit and it did not fix my issue. With APP_LOG(APP_LOG_LEVEL_WARNING, "Made it!"); I checked if handle_menu_props_packet is executed and it was NOT. It crashes before this function.
The app crashes after window.show(), I can see this, because I have a console.log() after it.
Do you have another idea?

@Meiguro That would make more sense than my race condition idea. Though I wasn't fully sure what was causing it, other than at the point the packet was being handled that the menu layer was still null. It's odd that the emulator would allow these null pointers, thanks for looking into that one!
@idoodler I'll look into this later tonight. Does it still crash with the code you provided in the initial question? I might not be able to do much though because I've only got access to the emulator. My PT from the timeline challenge should be arriving soon and then I can test it out on the watch to ensure the issue is resolved.

@idoodler Hmm, I wasn't able to reproduce the issue on master with a Pebble Time and your code snippet. Did you make sure to build before installing? I know I forget to do this sometimes. Try also deleting the app from the Apps/Timeline tab before installing. Sometimes when an app fails to install, it loads the old version anyway. I also don't recommend setting your own window id since that's an internally managed number, but that is also not causing a crash for me.
Let me know if you're still having issues. We can try different things, such as having you try a prebuilt pbw.

@Meiguro I deleted my app from my PebbleTime, deleted the build folder with my IDE (Webstorm), then I build, installed the app and I also logged everything with this command: pebble build && pebble install --phone <IP_ADDRESS> && pebble logs --phone <IP_ADDRESS>.
Also I merged your changes manually with my repo.
There were changes in simpy_menu.c from line 437 to 447:
static void handle_menu_props_packet(Simply *simply, Packet *data) {
  MenuPropsPacket *packet = (MenuPropsPacket*) data;
  simply_menu_set_num_sections(simply->menu, packet->num_sections);
  window_set_background_color(simply->menu->window.window, gcolor8_get_or(packet->background_color, GColorWhite));
  if (!simply->menu->menu_layer.menu_layer) {
    return;
  }
  menu_layer_set_highlight_colors(simply->menu->menu_layer.menu_layer,
                                  gcolor8_get_or(packet->highlight_background_color, GColorBlack),
                                  gcolor8_get_or(packet->highlight_text_color, GColorWhite));
  menu_layer_set_normal_colors(simply->menu->menu_layer.menu_layer,
                               gcolor8_get_or(packet->background_color, GColorWhite),
                               gcolor8_get_or(packet->text_color, GColorBlack));
}

There were also smaller changes in simply_menu.c line 18, 98 and 222.
Also there were changes in /gui/menu.js from line 10-12 (Removing some changes)
I also may need to tell you that I build my own ViewManager, here are the relevant parts

Thanks for the detailed information! I decided to investigate what 0x806bdd2 is, and it turns out it's menu_layer_set_highlight_colors, which makes sense since that's before the merge. What line in C does your app crash after the merges?
From the looks of your description, it doesn't appear to be much different from pure pebble.js. Having a view manager that calls show and hide is safe since that still uses pebble.js' underlying window stack.
I would try to see if the crash still occurs without changes to the C side. If you have new C side features, I would create a minimal example that crashes that doesn't use the new C features and see if it still crashes on a pure pebble.js C platform. If it still occurs, you can paste the minimal example here. While JSON dump in the first post is minimal, it unfortunately doesn't cause a crash for me, but I'm still wary if there is an issue.
If it only crashes with the C side in your repo, however, I'm still happy to look into that, though you'd have to upload your repository and pbw. If you would like to do this privately, you can contact me via the email address available in the commit history.

@Meiguro Sorry, I can't upload you the pbw file or the repository, because it is under NDA. I am developing this for the company I am employed. I also have not done any C changes on my own, I just merged your changes.
I also don't get a crash report when my app crashes. It just quits, this is very odd to me...

Is it launching directly into the menu? You can use 'pebble build && pebble install --phone=<IP_ADDRESS> --logs' to initiate and keep the logs open before it loads the app, rather than using the logs command.

Here is the "screen timeline" from top to bottom:

Displayed Window
Condition

Pebble.js launching screen
No problem

Splashscreen
No Problem

UI.Menu
App crashes without an errormessage

Here are the last executed lines:
...
Utility.DEBUG && console.log("Pushing info...");
listItems.fullscreen = true;
var list = new UI.Menu(listItems);
VM.showWindow(list, true);
Utility.DEBUG && console.log('Working');
list.on('select', function(e) {
...

Then there is the select handling function starting with last line of the code above. After this block There is no other code that can be executed. The whole code from above is encapsulated in a try/catch, but it don't catches anything.
My guess now is, that the .show() function is called and then C code is executed asynchronously, so the Utility.DEBUG && console.log('Working');can still be executed. And then it crashes somewhere.
And here is my application log:
'build' finished successfully (0.210s)
[INFO    ] Enabling application logging...
[INFO    ] I ocess_manager.c:368 Heap Usage for App <Weather La: Total Size <60628B> Used <17208B> Still allocated <600B
[INFO    ] Installation successful
[INFO    ] JS: stopping app: 1F0B0701-CC8F-47EC-86E7-7181397F9A25 Weather Land
[INFO    ] Displaying logs ... Ctrl-C to interrupt.
[INFO    ] JS: starting app: 133215F0-CE20-4C05-997B-3C9BE5A64E5B MyApp
... <--- some JSON parsing logs...
[INFO    ] JS: MyApp: Pushing info...
[INFO    ] JS: MyApp: [+]
[INFO    ] JS: MyApp: (+) [menu 3] : [card 2],[menu 3]
[INFO    ] JS: MyApp: Working
[INFO    ] JS: stopping app: 133215F0-CE20-4C05-997B-3C9BE5A64E5B MyApp
[INFO    ] JS: starting app: 1F0B0701-CC8F-47EC-86E7-7181397F9A25 Weather Land

@Meiguro I successfully pinned down the error! It has something to do with displaying the Splashscreen icon property. The value is set to images/MyAppForPebble.png, here is the appinfo.json part:
      {
        "type": "png",
        "name": "IMAGE_APP_ICON",
        "file": "images/MyAppForPebble.png",
        "menuIcon": true
      }

Everything should be fine here, or am I missing something?

@idoodler I'm pretty sure the identifier should be IMAGE_MENU_ICON

@Meiguro No, thats not the case. I use the path as the identifier in my whole project. I can also use another image and it also crashes. But I am able to use other images in my Project, so I guess its just with UI.Card(). Are you able to display an icon?

Hmm, that's odd. Yes, displaying an icon should be fine, that's what the demo does, and it does so in Card and Menu with the menu icon. Thanks for figuring out to this point! If you can find out what's the difference with the demo and your usage, we may be able to figure out the exact issue. So your Card can't display any image as the icon, but other windows in the project can display the image? Is your Card displaying the image, and crashing on exit?
He may be referring to the name in appinfo.json, but the SDK knows that it's the menu icon with the flag "menuIcon", so your entry is fine. I do tend to use "IMAGE_MENU_ICON" in all my projects however.
Commands meant to be sent to the Pebble are scheduled to be sent to the watch in the next tick, so any command affecting state on the watch work asynchronously. Usually when an app stops without error, it exited itself, such as by having no more windows. You can add a log line to simply_deinit in src/simply/simply.c or the end of src/main.c to see if this is the case; if it doesn't get printed, then it likely silently crashed. Of course, it appears to be working without an image, but it's possible adding an image is causing the command order to pop all windows first.

@Meiguro simply_deinit() is not been called when my app crashes. And I can not use this specific image anywhere! The size is 28x28, its a 32-bit color PNG with a white background and a black icon on top, it is 792 Byte big. The compositing is set. The card has a title, subtitle, body and of course an icon, also I set isSplash: true, backgroundColor: "white" and fullscreen: true.
Have there been some changes to the image transition from Pebble.js to C? Did the image requirements change?

The images are not transferred from pebble.js to C unless you provide a http url. They are compiled into the app and converted by the native Pebble SDK. You'll know that they're compiled in if they load instantly without any visible flashes, much like the icon in the demo.
Does that mean you are able to use other images, just not that specific one? The Pebble SDK actually has changed its PNG conversion, so you may want to try it in a native Pebble app. For example, you can see if that specific image crashes if you try it in the "feature-image" example here https://github.com/pebble-examples/feature-image. If it crashes only in pebble.js, I would love to have the image or similar (maybe you could visually modify it yet still retain its crashing properties). If it crashes in the feature-image example app, I would actually still like the image or similar, but you would also want to forward it to devsupport (at) getpebble.com.
Related to the new PNG conversion, if you're using Photoshop to create the image, try using the "Save for web" feature instead of saving in the format of PNG; it seems to prefer that. If you have ImageMagick, you can use mogrify -type palette -colorspace sRGB -colors 64 -depth 2 image.png to convert it to a Pebble SDK compatible format.

@idoodler If you're still unable to get the image to display, let me know with a gist of an example app with the problem in a new issue and I'll be happy to assist. Closing this issue since the title issue, GUI.Menu crashing because of colors, shouldn't occur anymore.


README.md: fix typo

Q
A

Bug fix?
no

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
/

License
Apache 2.0

What's in this PR?

Small PR to correct a spelling mistake in the documentation.

Why?

Custom Resource Descriptions doesn't exist in Kubernetes. Custom Resource Definitions exist.

Checklist

[x] Code meets the Developer Guide

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


Token deployment UI finalize

Description (what needs to be done) / Expected Behavior
Token deployment UI finalize - update with the completed UI design attached in supporting information
Acceptance Criteria
Token deployment is user friendly and not missing any key functional pieces for the user.
Supporting information (Figma link, notes, etc)
https://www.figma.com/file/gXLZPoh1BchigOB5y9YkQZ/Tezos-Homebase---v2-UI?node-id=6432%3A2199&t=qODG9rfrDwEPXnq0-0
When finished, please add Link to the PR or completed Figma / design asset, as a comment to the ticket.

Change requests from design:
reduce space between logo and top of dao creator and token deployer
make padding on left nav (the numbers/steps) equal top and bottom of that box
buttons should be the same as the ones in the common components
title case buttons (not all caps)
Alana to send over consistent icons


VM size not available in East US region

Exercise 02: Create and configure network security groups
Create the network infrastructure for the exercise
4. Deploy the virtual machines required for this exercise.
PS /home/rob> $RGName = "RG1"
PS /home/rmontroy> New-AzResourceGroupDeployment -ResourceGroupName $RGName -TemplateUri https://raw.githubusercontent.com/MicrosoftLearning/Configure-secure-access-to-workloads-with-Azure-virtual-networking-services/main/Instructions/Labs/azuredeploy.json
New-AzResourceGroupDeployment: 5:45:11 PM - Error: Code=SkuNotAvailable; Message=The requested VM size for resource 'Following SKUs have failed for Capacity Restrictions: Standard_DS1_v2, Standard_DS1_v2' is currently not available in location 'eastus'. Please try another size or deploy to a different location or different zone. See https://aka.ms/azureskunotavailable for details.
New-AzResourceGroupDeployment: The deployment validation failed

Perhaps the template should have params for location and VM size.

Added a note to change the "location" value in the template if you receive a capacity restriction error.


Expose service to add/remove backends dynamically

This has so much more meta involved before it's relevant


states_rebuilder implementation

First of all, I would like to thank you for your efforts and contributions in making the flutter community better. I also appreciate being open to other state management solutions.
This is my contribution to your project. It consists of a states_rebuilder implementation.
It should be noted that:

I did not touch the core part. I took it as it is and just consume it.
By default, states_rebuilder tracks the state status and exposes six flags:
isIdle: after the state is first created and before any operation (virgin status).
isWaiting: When the state is waiting for an async task (Future or Stream).
hasError: If the state caught an exception.
hasData: when the state is mutated successfully with valid data
isDone: when the state's stream is done.
isActive: changed manually to mark whether the state is active or not.
If the sole purpose of using Freezed is to track one of the six state status, then it is no longer necessary to use it.
I do not use favouriteMovies that use RxDart. Instead, I combined two injected states.
All the functionalities of the app are tested.

@GIfatahTH thank you very much for this PR and apologies for the delay. Merged now.

@GIfatahTH When you get a chance could you make a new PR and migrate this implementation to null safety?


Fix typo in the docs, add links to MockMvc and RestAssured docs

The RestAssured framework mistakenly named RestEasy in the documentation. :-)

@xak2000 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@xak2000 Thank you for signing the Contributor License Agreement!


Doesn't sync the ethereum wallet on Android 9.0

After i updated my device to Android 9.0, the ethereum wallet doesn't sync anymore and i can't see any value even ERC20 tokens.

It seems to be fixed in the latest code push.. but can anyone tell how was it fixed ?

The user agent string was corrected in 3.7.0 (reference jira issue #1073).  @praxais, thank you for posting your solution!


Ensure "fields" config is optional

According to the documentation, the fields and fieldsMapper options should be optional. However, when excluded, the following error is given when attempting to run gatsby develop:
error Plugin gatsby-source-google-docs returned an error
  Error: source-google-docs: Cannot read property 'join' of undefined
  - gatsby-node.js:280 Object.exports.sourceNodes
    [gatsby-site]/[gatsby-source-google-docs]/gatsby-node.js:280:10

Tracing this error lead to line 203 of gatsby-node.js in src:
fields: `files(id, name, ${fields.join(", ")})`,

This code works great when the fields option is defined, but when the parameter is undefined, an error is thrown when attempting to use .join() on the undefined parameter.
To fix this, I simply suggest checking to see if fields is undefined (by checking its truthiness).
Originally, I tried this solution:
fields: `files(id, name, ${fields ? fields.join(", ") : ""})`,

However, this threw another error:
error Plugin gatsby-source-google-docs returned an error
  Error: source-google-docs: Invalid field selection files(id, name, )
  - gatsby-node.js:280 Object.exports.sourceNodes
    [gatsby-site]/[gatsby-source-google-docs]/gatsby-node.js:280:10

To resolve this error, I modified the line as such:
fields: `files(id, name${fields ? `, ${fields.join(", ")}` : ""})`,

This worked for me and removed the error. Please let me know how this works for you, @xuopled
If you have any questions, let me know. I only tested this with my scenario, so I think it would be good to test with other Gatsby examples.
Love this plugin by the way. Cheers and thanks!
— David

Thank you for your help @davidhartsough

I just published v1.0.1


Add withConverter and pass in a generic type

Feature request
Is your feature request related to a problem? Please describe.
Yeah sort of, this would refer to be as "boilerplate" code. Since we typically do that manually every time we fetch data.
// where response if the returned results from Supabase client
User.fromJson(response.data)

Describe the solution you'd like
Firestore has implemented this feature. So I'll just link up that from pub.dev changelog.
https://pub.dev/packages/cloud_firestore/changelog#200
Additional context

Should also be possible to implement this in a way that mirrors the supabase javascript API. We could pass the type in on the .from method and check to see if it inherits from a supabase abstract data type which requires fromJson/toJson methods. It's definitely not as flexible as the firebase implementation so that may still be better. Just suggesting it depending on how important it is that this library keeps in line with the official supabase documentation.

you can create an extension for this:
ex:
typedef FromSupabase<T> = T Function(
  dynamic data,
  PostgrestError error,
);

extension Converter<T> on Future<PostgrestResponse> {
  Future<T> withConverter<T>({
    FromSupabase<T> fromResponse,
  }) async {
    final data = await this;
    return fromResponse.call(data.data, data.error);
  }
}

not tested and was written entirely in my imagination.


arrow-body-style

Current dependencies on/for this PR:

main

PR #32   👈

This comment was auto-generated by Graphite.


treewide: Add meta.pkgConfigModules to a few packages

Description of changes
Picking up where https://github.com/NixOS/nixpkgs/pull/214304 left off.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

CC @growpotkin

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/adding-pkg-config-metadata-to-nixpkgs-packages/25281/1

validatePkgConfig is orthogonal to this; I rather not start adding yet as that will require lots of rebuilds. I rather get all these converted and then do validatePkgConfig on staging.
(I don't really like extra testing in the main build anyways because it adds latency for no good reason. Embrace parallelism; embrace finer-grained derivations.)


Wording

With reference to
"Option 2: Switch from federation to pass-through authentication by using Azure AD Connect and PowerShell"
Should this read "Option B:"?
So as not to confuse with Step 2 etc.

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

ID: 3b704969-b273-9466-6498-b259141bdd75
Version Independent ID: 19edc91e-3215-d43e-6d27-734d8354085e
Content: Azure AD Connect: Migrate from federation to PTA for Azure AD
Content Source: articles/active-directory/hybrid/plan-migrate-adfs-pass-through-authentication.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@AndrewMaisey Thanks for your comment. We are actively investigating and will get back to you shortly.

@AndrewMaisey Thanks for the suggestion. I have updated the doc accordingly and it will be reflected shortly.


showAd Method is Missing

Hi,
Please replace the documentation of showAd method with showBannerAd and showInterstitialAd as these methods are the ones we can find while coding.
Thanks and regards
Christophe

Hi Christophe,
Thanks! Corrected everywhere.
Regards,
Miquel


All UserAdd commands are failing due to REST timeout

All UserAdd commands in test_user.robot are failing due to ConnectionError. Manually ran the command and found that REST command is taking close to 30 secs to respond. At present, REST command output is set to be receive in 5 secs (read timeout=5.0) which in this case does not happen. So to always capture REST response we should increase REST time out to a higher value in our automation code.
09:32:34 Create and delete user with user group name :: GOOD PATH        URI:https://<IP_ADDRESS>/org/openbmc/UserManager/Groups/action/GroupAddUsr, method:Post, args:{u'data': {u'data': ['BGaYN8u9']}, u'headers': {u'Content-Type': u'application/json'}}
09:32:35 Response code:200, Content:{
09:32:35   "data": 0,
09:32:35   "message": "200 OK",
09:32:35   "status": "ok"
09:32:35 }
09:32:35 URI:https://<IP_ADDRESS>/org/openbmc/UserManager/Users/action/UserAdd, method:Post, args:{u'data': {u'data': ['fbZ65tLf', 'qvdeZMTd', 'BGaYN8u9', 'jsb9pTf7']}, u'headers': {u'Content-Type': u'application/json'}}
09:32:58
09:32:58 FFDC Collection Started 	: 2016-09-03 09:32:58,108453
09:33:09 FFDC Collection Completed 	: 2016-09-03 09:33:09,678948
09:33:09 | FAIL |
09:33:09 ConnectionError: HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Max retries exceeded with url: /org/openbmc/UserManager/Users/action/UserAdd (Caused by ReadTimeoutError("HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Read timed out. (read timeout=5.0)",))
rahulmah@rackspace:~$ curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST https://<IP_ADDRESS>/login -d "{"data": [ "root", "0penBmc" ] }"
{
"data": "User 'root' logged in",
"message": "200 OK",
"status": "ok"
}rahulmah@rackspace:~$ date
Sat Sep  3 14:16:45 CDT 2016
rahulmah@rackspace:~$ curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST -d "{"data": ["myuser", "bmcuser11", "abc11", "abc123"]}" https://<IP_ADDRESS>/org/openbmc/UserManager/Users/action/UserAdd
{
"data": {
"description": "Internal Server Error",
"exception": "DBusException('Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.',)",
"traceback": [
"Traceback (most recent call last):",
"  File "/usr/lib/python2.7/site-packages/bottle.py", line 858, in _handle",
"    route, args = self.router.match(environ)",
"  File "/usr/sbin/obmc-rest", line 746, in custom_router_match",
"    route.callback._setup(**args)",
"  File "/usr/sbin/obmc-rest", line 86, in _setup",
"    return self.setup(**kw)",
"  File "/usr/sbin/obmc-rest", line 209, in setup",
"    request.route_data['method'] = self.find(path, method)",
"  File "/usr/sbin/obmc-rest", line 202, in find",
"    m = self.find_method_on_bus(path, method, *items)",
"  File "/usr/sbin/obmc-rest", line 238, in find_method_on_bus",
"    data = iface.Introspect()",
"  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in call",
"    **keywords)",
"  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking",
"    message, timeout)",
"DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
]
},
"message": "500 Internal Server Error",
"status": "error"
}rahulmah@rackspace:~$ date
Sat Sep  3 14:17:15 CDT 2016
rahulmah@rackspace:~$
Above error response "DBusException: org.freedesktop.DBus.Error.NoReply" for useradd command needs to be figured out from dev.  For this I will open a separate issue in openbmc.

Code pushed for review. Increase timeout to always capture response in case of delay with REST.

Do we understand why adding a user takes 30 seconds?

@amboar : We should not be seeing 30 sec for REST command to reply back. But in case of user add it's happening which I believe is due to "DBusException: org.freedesktop.DBus.Error.NoReply" which we are seeing. I have opened issue for the same in openbmc.

I have opened below issue in openbmc to take care of delay part and error part in rest response. Code changes in test automation is not required. So closing the issue.
https://github.com/openbmc/openbmc/issues/543


add usage menu

caveat: it's just a placeholder for now
shorten check of quit option

Looks good! Thank you!


build tutlebot3 on ROS2, build error

ISSUE TEMPLATE ver. 0.4.0

Which TurtleBot3 platform do you use?

[x] Burger
[ ] Waffle
[ ] Waffle Pi

Which ROS is working with TurtleBot3?

[ ] ROS 1 Kinetic Kame
[ ] ROS 1 Melodic Morenia
[ ] ROS 1 Noetic Ninjemys
[ ] ROS 2 Dashing Diademata
[ ] ROS 2 Eloquent Elusor
[x] ROS 2 Foxy Fitzroy
[ ] etc (Please specify your ROS Version here)

Which SBC(Single Board Computer) is working on TurtleBot3?

[x] Intel Joule 570x
[ ] Raspberry Pi 3B+
[ ] Raspberry Pi 4
[ ] etc (Please specify your SBC here)

Which OS you installed on SBC?

[ ] Raspbian distributed by ROBOTIS
[x] Ubuntu MATE (16.04/18.04/20.04)
[ ] Ubuntu preinstalled server (18.04/20.04)
[ ] etc (Please specify your OS here)

Which OS you installed on Remote PC?

[ ] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[x] Ubuntu 20.04 LTS (Focal Fossa)
[ ] Windows 10
[ ] MAC OS X (Specify version)
[ ] etc (Please specify your OS here)

Specify the software and firmware version(Can be found from Bringup messages)

Software version: [2.1.3]
Firmware version: [x.x.x]

Specify the commands or instructions to reproduce the issue.

mkdir -p ~/tb3_ws/src
cd ~/tb3_ws
wget https://raw.githubusercontent.com/ROBOTIS-GIT/turtlebot3/ros2/turtlebot3.repos
vcs import src < turtlebot3.repos
colcon build --symlink-install

Copy and Paste the error messages on terminal.

Starting >>> turtlebot3_msgs
Starting >>> dynamixel_sdk
Starting >>> hls_lfcd_lds_driver
Starting >>> turtlebot3_description
Finished <<< turtlebot3_description [0.33s]
Starting >>> dynamixel_sdk_custom_interfaces
Finished <<< dynamixel_sdk [0.78s]
Starting >>> turtlebot3_cartographer
--- stderr: turtlebot3_msgs
CMake Error at /opt/ros/foxy/share/rosidl_generator_c/cmake/rosidl_generator_c_generate_interfaces.cmake:168 (find_package):
By not providing "Findament_cmake_cppcheck.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"ament_cmake_cppcheck", but CMake did not find one.
Could not find a package configuration file provided by
"ament_cmake_cppcheck" with any of the following names:
ament_cmake_cppcheckConfig.cmake
ament_cmake_cppcheck-config.cmake

Add the installation prefix of "ament_cmake_cppcheck" to CMAKE_PREFIX_PATH
or set "ament_cmake_cppcheck_DIR" to a directory containing one of the
above files.  If "ament_cmake_cppcheck" provides a separate development
package or SDK, be sure it has been installed.
Call Stack (most recent call first):
/opt/ros/foxy/share/ament_cmake_core/cmake/core/ament_execute_extensions.cmake:48 (include)
/opt/ros/foxy/share/rosidl_cmake/cmake/rosidl_generate_interfaces.cmake:286 (ament_execute_extensions)
CMakeLists.txt:45 (rosidl_generate_interfaces)

Failed   <<< turtlebot3_msgs [0.97s, exited with code 1]
Aborted  <<< turtlebot3_cartographer [0.87s]
Aborted  <<< dynamixel_sdk_custom_interfaces [1.72s]
Aborted  <<< hls_lfcd_lds_driver [3.86s]
Summary: 2 packages finished [4.16s]
1 package failed: turtlebot3_msgs
3 packages aborted: dynamixel_sdk_custom_interfaces hls_lfcd_lds_driver turtlebot3_cartographer
2 packages had stderr output: hls_lfcd_lds_driver turtlebot3_msgs
10 packages not processed

Please describe the issue in detail.

I just want to simulate turtlebot3 on my Ubuntu 20.04.

I find the old similar issue, but the link in that issue is invalid.:(

Hi @yuan-ge
When performing simulation on PC, you don't need to run the TurtleBot3 hardware.
Please refer to the eManual below and don't forget to select the ROS version at the top of the page.
https://emanual.robotis.com/docs/en/platform/turtlebot3/quick-start/#pc-setup
and the simulation instructions here
https://emanual.robotis.com/docs/en/platform/turtlebot3/simulation/
The Intel Joule had been discontinued a few years ago and not supported anymore so we won't be able to provide tech support for setting up with the latest version.
Thanks!

I just tried the tutorial in this page:  . And I do the steps listed below:

but the result is the same:

Starting >>> dynamixel_sdk
Starting >>> turtlebot3_msgs
Starting >>> turtlebot3_description
Starting >>> dynamixel_sdk_custom_interfaces
Finished <<< turtlebot3_description [0.43s]
Starting >>> turtlebot3_cartographer
--- stderr: turtlebot3_msgs
CMake Error at /opt/ros/foxy/share/rosidl_generator_c/cmake/rosidl_generator_c_generate_interfaces.cmake:168 (find_package):
By not providing "Findament_cmake_cppcheck.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"ament_cmake_cppcheck", but CMake did not find one.
Could not find a package configuration file provided by
"ament_cmake_cppcheck" with any of the following names:
ament_cmake_cppcheckConfig.cmake
ament_cmake_cppcheck-config.cmake

Add the installation prefix of "ament_cmake_cppcheck" to CMAKE_PREFIX_PATH
or set "ament_cmake_cppcheck_DIR" to a directory containing one of the
above files.  If "ament_cmake_cppcheck" provides a separate development
package or SDK, be sure it has been installed.
Call Stack (most recent call first):
/opt/ros/foxy/share/ament_cmake_core/cmake/core/ament_execute_extensions.cmake:48 (include)
/opt/ros/foxy/share/rosidl_cmake/cmake/rosidl_generate_interfaces.cmake:286 (ament_execute_extensions)
CMakeLists.txt:45 (rosidl_generate_interfaces)

Failed   <<< turtlebot3_msgs [0.94s, exited with code 1]
Aborted  <<< turtlebot3_cartographer [0.61s]
Aborted  <<< dynamixel_sdk [1.23s]
Aborted  <<< dynamixel_sdk_custom_interfaces [4.28s]
Summary: 1 package finished [4.48s]
1 package failed: turtlebot3_msgs
3 packages aborted: dynamixel_sdk dynamixel_sdk_custom_interfaces turtlebot3_cartographer
1 package had stderr output: turtlebot3_msgs
7 packages not processed

so annoying.  I tried use the deb to install tutlebot3. When I run the app, I find my ros2 has no command "launch". So, I reinstall the foxy on my PC.  It's all right up to now.
The source of the problem is ROS2, my god.

I was getting the same error but all of sudden I cleaned and rebuilt the workspace and its gone.!


Remove support for daemontools and bluepill

It's time to simplify this cookbook by supporting primarily OS default init systems.  Neither bluepill or daemontools gained widespread support and with systemd their need has mostly gone away.  We should remove the code necessary to support these init systems and further simplify this cookbook.

:+1: LGTM


66Create66

66

Looks like this was created by accident, closing. If needed, feel free to reopen with more details, thank you!


nixos/bind: allow specifying BIND package

Motivation for this change
This allows users of the bind module to specify an alternate BIND
package. For example, by overriding the source attribute to use a
different version of BIND.
Since the default value for services.bind.package is pkgs.bind,
this change is completely backwards compatible with the current
module.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Why are overlays a bad choice to replace the package?

@aanderse Overlays are a fine choice to replace the bind package.
This offers another choice that may be more terse or less complicated. There many other examples of using a package option already in NixOS and I figured this approach was relatively standard already.
One example I can think of where this might be better than overlays is if one wanted to use a different version of the bind server but leave the the dnsutils package unchanged.

I figured this approach was relatively standard already.

Very much so, but I always like to ask this question to make sure people know overlays can do this and then decide what they think is best, which you already have done :smile:. Thanks!


Docs: fix typo in theming guide

@googlebot I signed it!

Thanks for the heads-up @crisbeto. I've just changed the commit message


Make traced unet optional to allow for custom checkpoints

Fixed with https://github.com/riffusion/riffusion/commit/8349ccff5957f42d8ae7838b6d8218e3060ad1ee


ENDOC-373 customer-portal.md

This is a draft! Please pay special attention to structure and whether some of the information is redundant, too specific and/or not necessary.
Ignore the image sizes, not sure why some are really big when I tried to resize them.
Also ignore that a lot of the text that need to be highlighted, such as field names, are not yet done.

@jyunmitch Adding the left nav 2nd level option will help a lot but I feel like the overall structure needs to be a little more obvious to the user. Maybe this: (yes, I used a colon)

Installation

Prerequisites
Automatic Install via the Hub (TBD, this would be from the 7.0 AppBuilder itself)
Manual Install via ent cli (basically what you have now)

Configuration
Managing the Portal

Much of what you have now - adding users, customers, project, subs falls under this

Using the Portal

Maybe a short section on the other roles - customer, partner, suppo

Application Details (same name as Standard Demo? Or maybe Technical Details)
Resources


feat: Send transaction with "data" field and allow amount to be zero

[x] - Allows DOT holders to map Ethereum-DOT into ChainX-SDOT and get the PCX airdrop (see https://github.com/chainx-org/ChainX/issues/66) by sending a transaction with a "data" field value (their ChainX Address converted to hex)

Update Send transaction UI so "amount" field can be 0, since some users may want to just send some data (i.e. https://github.com/chainx-org/ChainX/issues/66)
Set the default amount value to be 0 and not required
Update Send transaction UI to support "data" field in hex (with 0x prefix)
Use a hard-coded Gas Limit of 200,000 when user provides hex "data" value
Remove logic that doesn't make sense (i.e. else if (amountBn.isZero()) {)
Update validation messages
Add support for Blockscout link when user using Goerli testnet
Update internationalisation
Use custom isHexString function instead of the ethereumjs-util's version. The ethereumjs-util's version is used by MyCrypto and doesn't work properly.
Tested on Goerli testnet by creating two accounts, requesting Goerli tokens, running with --chain goerli appended to the end (so you'll have to remove this if you want to use mainnet) otherwise it uses mainnet by default (i.e. "start": "cross-env ELECTRON_START_URL=http://localhost:3000 electron-webpack dev --chain goerli", in fether/packages/fether-electron/package.json), and sending a transaction with the high gas price, the hex data. For example, for ChainX convert your ChainX Address (UTF8 chars) into Hex code (i.e. for example if your ChainX Address was "0xhelloworld" then remove the "0x" prefix, then copy/paste the remainder at https://www.browserling.com/tools/utf8-to-hex, so "helloworld" becomes => \x68\x65\x6c\x6c\x6f\x20\x77\x6f\x72\x6c\x64, then remove the \x's, => 68656c6c6f20776f726c64 => then prepend 0x => 0x68656c6c6f20776f726c64 and add that as the "data" field value... p.s. there are less ugly ways to do this but i'll let others figure that out), then send the transaction, and when the transaction is successful go to the Blockscout link and you'll see under "Raw Input" ("Input Data" on Etherscan) that you can switch between viewing it in UTF8 or Hex, i.e. https://blockscout.com/eth/goerli/tx/0x7eaec61ce7753fd4c80aec4509c49942b53986585e4864e18134806bffb25f10/internal_transactions)

Verified that was able to get "Transaction ID binding complete" status on ChainX confirming that sending an Ethereum transaction using Fether from a DOT holder address to any other Ethereum account with 0 ETH and a "data" value containing the hex version of the ChainX Address works on mainnet
[ ] Fix it so that it doesn't error when an invalid amount is entered

Note: To use this PR in development prior to it being merged into master, run git fetch origin luke-data-field:luke-data-field; git checkout luke-data-field; yarn; yarn start you may first need to follow the steps in this PR https://github.com/paritytech/fether/pull/525 before running the yarn; yarn start step. if you can't sync with the chain, then try removing the chain from the relevant directory of your OS and resyncing from scratch, see https://wiki.parity.io/Fether-FAQ#where-is-the-light-client-blockchain-database-used-by-fether-stored

Note: I've left --chain goerli in the PR since users might want to play around using Goerli testnet first

Important Note I've put this on-ice since it's unlikely anyone else wants to use it other than me, and it's highly unlikely that it'll ever get merged. I'm also trying to focus on Rust. The only reason I've published this is because I needed this functionality to use ChainX and I thought I may as well share the code to help other ChainX users. It's also unlikely that I'll update Parity Signer to show the "data" field value (if it doesn't already) since it's not necessary, so this can be left for the community.

This use case seems super specific and it is very unlikely that we will add such functionality.

Closing this for now because it'll most likely never make it to master. I'll let the branch though from you to keep using it if you want.

I just using this branch to sending a transaction of 0 ETH with some text in the "data" field of the form, but when I click "Confirm Transaction", even though it's synced, it displays "No light peers who can serve the data".
Also, I encountered an error on the Send Transaction page, which I resolved by changing if (!values) { to if (!values || !values.amount) {

Here's an alternative to using the "data" field to demonstrate that you've signed a message https://wiki.polkadot.network/docs/en/kusama-claims


Breaking change with FCM Instance Id

Google has introduced a breaking change in the latest version of its cloud messaging package. The firebase instance id is no longer available where it used to be.

This results in a crash on startup on android as this instance ID is used by Emarsys

Fixed by upgrading to the latest version of the android Emarsys SDK


DatabaseManager forces UTC

JDBC connectors are finicky about dates, as they make assumptions
about dates' timezones both when they are stored and when they
are read. This patch forces the test harness database to use UTC.

Coverage remained the same at 100.0% when pulling 87e2d37d086add3eb68e8961330009d6fe22f55d on feature/db_tz into d25be17ddc04210d6f664daff8daa81f345a8a7d on develop.


MELD sent from Daedalus to Nami was reduced 1,000,000x

According to Daedalus, I received 1,359,057,087 MELD tokens.  Since MELD doesn't pair with Daedalus, I had to send it to the NAMI wallet.  When I did, I noticed that the NAMI wallet counted it only as 1,359.057087.  In other words, it apparently reduced the amount of MELD I had sent by 1/1,000,000.  I'm trying to figure out if my Daedalus or my Nami is actually the correct amount.

Nami shows the correct amount. In Daedelus you need to set the decimal amount to 6 as it's wrong by default.

Nami shows the correct amount. In Daedelus you need to set the decimal amount to 6 as it's wrong by default.

I appreciate the help!


exclude files from nix fmt

Get rid of the following warnings:
$ nix fmt
[...]
WARN no formatter for path: .env
WARN no formatter for path: LICENSE
WARN no formatter for path: renovate.json
[...]

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#103
#102
#101
#100
#99
#104  👈 (View in Graphite)
#98
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 12, 11:59 PM EST: A user started a stack merge that includes this pull request via Graphite.


Error after uploading too large files (504)

Hi Mr Wonderfall :)
after pulling the latest nextcloud image i get 502 error.
this is my compose.yml
nginx:
  image: wonderfall/nginx
  container_name: nginx
  links:
    - nextcloud:nextcloud
  ports:
    - "80:8002"
    - "443:8001"
  volumes:
    - /etc/localtime:/etc/localtime
    - /root/.nginx/sites-enabled:/sites-enabled
    - /root/.nginx/conf:/conf.d
    - /root/.nginx/log:/var/log/nginx
    - /root/.nginx/certs:/certs

nextcloud:
    image: wonderfall/nextcloud
    container_name: nextcloud
    links:
      - db_nextcloud:db_nextcloud
    environment:
      - UID=1000
      - GID=1000
    volumes:
      - /etc/localtime:/etc/localtime
      - /media/19ad4901-a651-4001-9306-425956e2c501/Cloud/data:/data
      - /media/19ad4901-a651-4001-9306-425956e2c501/Cloud/config:/config
      - /media/19ad4901-a651-4001-9306-425956e2c501/Cloud/apps:/apps2

db_nextcloud:
    image: mariadb:10
    volumes:
      - /media/19ad4901-a651-4001-9306-425956e2c501/Cloud_db:/var/lib/mysql
    container_name: db_nextcloud
    environment:
      - MYSQL_ROOT_PASSWORD=xxx
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_PASSWORD=xxx

collabora:
    image: collabora/code
    tty: true
    container_name: office_nextcloud
    ports:
      - "<IP_ADDRESS>:9980:9980"
    environment:
      - domain=nextcloud\.mydomain\.com
    cap_add:
      - MKNOD

this is my nginx reverseproxy conf
server {

  listen 8002;
  server_name nextcloud.mydomain.com;
  #rewrite ^ https://nextcloud.mydomain.com$request_uri? permanent;
  return 301 https://$host$request_uri;

}

server {

  listen 8001 ssl http2;
  server_name nextcloud.mydomain.com;
  client_max_body_size 40960M;
  ssl_certificate /certs/nextcloud/fullchain.pem;        # path to your cacert.pem
  ssl_certificate_key /certs/nextcloud/privkey.pem;      # path to your privkey.pem
  ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
  ssl_ciphers "ECDHE-RSA-CHACHA20-POLY1305:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA";
  ssl_prefer_server_ciphers on;
  ssl_ecdh_curve secp384r1;

  ssl_session_cache shared:SSL:10m;
  ssl_session_timeout 5m;
  ssl_session_tickets off;

  location / {
    proxy_pass http://nextcloud;
    include /conf.d/proxy-params.conf;
  }
}

what is wrong ?

Change the following code :
proxy_pass http://nextcloud; to proxy_pass http://nextcloud:8888;
I updated the Docker Hub description : https://hub.docker.com/r/wonderfall/nextcloud/
I had to change the listen port due to OS restrictions (non-root user cannot use port 80).

Great. That resolved it!

Nice to hear that!

Sorry for reposting here
but i found that big files are causing another issue
   19.09.16 23:12:10,                            06_Shared/xxx.dmg,/Volumes/Daten/Hannes/nextcloud,Error downloading https://nextcloud.mydomain.com/remote.php/webdav/06_Shared/xxx.dmg-chunking-2051989783-625-623 - server replied: Gateway Time-out
is it because of my nginx reverseproxy settings ?
Sorry - feeling that i am the only one that has questions. maybe i am to dumb ;P

Can you paste the content of the following files (in the container) ?

/tmp/ngx_error.log
/var/log/php7/error.log

Thanks!

php7/error.log is empty
ngx_error.log
cat /tmp/ngx_error.log
2016/09/20 08:32:37 [error] 18#0: *352 rewrite or internal redirection cycle while internally redirecting to "/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/apps/files/core/search/templates/part.results.html", client: <IP_ADDRESS>, server: , request: "GET /apps/files/core/search/templates/part.results.html HTTP/1.0", host: "nextcloud.mydomain.com"
2016/09/20 08:32:37 [error] 17#0: *364 rewrite or internal redirection cycle while internally redirecting to "/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/apps/files/core/img/actions/toggle-pictures.svg", client: <IP_ADDRESS>, server: , request: "GET /apps/files/core/img/actions/toggle-pictures.svg HTTP/1.0", host: "nextcloud.mydomain.com"
2016/09/20 08:32:37 [error] 17#0: *365 rewrite or internal redirection cycle while internally redirecting to "/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/apps/files/undefined/img/notifications.svg", client: <IP_ADDRESS>, server: , request: "GET /apps/files/undefined/img/notifications.svg HTTP/1.0", host: "nextcloud.mydomain.com"
2016/09/20 08:35:37 [error] 18#0: *833 rewrite or internal redirection cycle while internally redirecting to "/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/nextcloud/index.php/core/preview.png", client: <IP_ADDRESS>, server: , request: "GET /core/preview.png?file=%2FLokal%2FOS+X+El+Capitan+v10.11+%5BMAS%5D+%2815A284%29%2FOS_X_El_Capitan_15A284.dmg&c=6dc1ddfeb1e75e07d3bf50430fc457f4&x=32&y=32&forceIcon=0 HTTP/1.0", host: "nextcloud.mydomain.com"
2016/09/20 08:38:06 [error] 17#0: *1 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Doctrine\DBAL\DBALException: Failed to connect to the database: An exception occured in driver: SQLSTATE[HY000] [2003] Can't connect to MySQL server on 'db_nextcloud' (111 "Connection refused") in /nextcloud/lib/private/DB/Connection.php:59
Stack trace:
#0 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(429): OC\DB\Connection->connect()
#1 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(389): Doctrine\DBAL\Connection->getDatabasePlatformVersion()
#2 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(328): Doctrine\DBAL\Connection->detectDatabasePlatform()
#3 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(621): Doctrine\DBAL\Connection->getDatabasePlatform()
#4 /nextcloud/lib/private/DB/Connection.php(142): Doctrine\DBAL\Connection->setTransactionIsolation(2)
#5 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/DriverManager.php(172): OC\DB\Connection->__construct(Array, Object(Doctrine\DBAL\...
PHP message: PHP Fatal error:  Uncaught Doctrine\DBAL\DBALException: Failed to connect to the database: An exception occured in driver: SQLSTATE[HY000] [2003] Can't connect to MySQL server on 'db_nextcloud' (111 "Connection refused") in /nextcloud/lib/private/DB/Connection.php:59
Stack trace:
#0 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(429): OC\DB\Connection->connect()
#1 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(389): Doctrine\DBAL\Connection->getDatabasePlatformVersion()
#2 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(328): Doctrine\DBAL\Connection->detectDatabasePlatform()
#3 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(621): Doctrine\DBAL\Connection->getDatabasePlatform()
#4 /nextcloud/lib/private/DB/Connection.php(142): Doctrine\DBAL\Connection->setTransactionIsolation(2)
#5 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/DriverManager.php(172):
2016/09/20 08:38:06 [error] 17#0: *3 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Doctrine\DBAL\DBALException: Failed to connect to the database: An exception occured in driver: SQLSTATE[HY000] [2003] Can't connect to MySQL server on 'db_nextcloud' (111 "Connection refused") in /nextcloud/lib/private/DB/Connection.php:59
Stack trace:
#0 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(429): OC\DB\Connection->connect()
#1 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(389): Doctrine\DBAL\Connection->getDatabasePlatformVersion()
#2 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(328): Doctrine\DBAL\Connection->detectDatabasePlatform()
#3 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(621): Doctrine\DBAL\Connection->getDatabasePlatform()
#4 /nextcloud/lib/private/DB/Connection.php(142): Doctrine\DBAL\Connection->setTransactionIsolation(2)
#5 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/DriverManager.php(172): OC\DB\Connection->__construct(Array, Object(Doctrine\DBAL\...
PHP message: PHP Fatal error:  Uncaught Doctrine\DBAL\DBALException: Failed to connect to the database: An exception occured in driver: SQLSTATE[HY000] [2003] Can't connect to MySQL server on 'db_nextcloud' (111 "Connection refused") in /nextcloud/lib/private/DB/Connection.php:59
Stack trace:
#0 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(429): OC\DB\Connection->connect()
#1 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(389): Doctrine\DBAL\Connection->getDatabasePlatformVersion()
#2 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(328): Doctrine\DBAL\Connection->detectDatabasePlatform()
#3 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(621): Doctrine\DBAL\Connection->getDatabasePlatform()
#4 /nextcloud/lib/private/DB/Connection.php(142): Doctrine\DBAL\Connection->setTransactionIsolation(2)
#5 /nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/DriverManager.php(172):

The ngx_error.log looks like a database problem which should be fixed but I don't think it causes the problem with the download.
I guess it has more todo with a proxy and the php configuration. As "Gateway Timeout" says a process, maybe the php one, has taken too long time, so the webserver, nginx, thought it's broken because it took too long time.
I figured out that in the php configuration file the option request_terminate_timeout was set to 1200 which means 20 minutes.
But there's also max_execution_time set to 3 hours.
In the nginx config the same limit (of 20 minutes) is set.
Do you remember how long it took to upload the file or after which amount of time you got the response/error?

i setup a error log in my nginx conf
nginx nectcloud.error.log
i guess this makes more sense now
2016/09/20 10:34:23 [error] 13#13: *1 readv() failed (104: Connection reset by peer) while reading upstream, client: <IP_ADDRESS>, server: nextcloud.hannesmueller.com, request: "GET /remote.php/webdav/Lokal/XXX.dmg?downloadStartSecret=7yymfqws68j2a7kuefa5g66r HTTP/2.0", upstream: "http://<IP_ADDRESS>:8888/remote.php/webdav/Lokal/XXX.dmg?downloadStartSecret=7yymfqws68j2a7kuefa5g66r", host: "nextcloud.hannesmueller.com"
i guess it was approx 20min.

i'm now running a test with  increased fastcgi_read_timeout

Problem still persist with higher fastcgi_read_timeout

Increase both request_terminate_timeout (php-fpm.conf) and fastcgi_read_timeout (container + reverse proxy) and tell us if it works

Setting the php value to E_ALL would be helpfull, too.
Edit the php-fpm.conf and add:
php_admin_value[error_reporting] = E_ALL

Then check your /var/log/php7/error.log again after the upload fails.

okay. did everthing u said. no changes.
also i cant download files bigger than >1GB.
it stops exactly at 1024mb

Did you check /var/log/php7/error.log like @jdoubleu said? This can be helpful.

root@NAS:~/.nginx/htdocs# docker exec -it nextcloud sh
/ # nano /var/log/php7/error.log
sh: nano: not found
/ # cat /var/log/php7/error.log
[20-Sep-2016 08:32:29] NOTICE: fpm is running, pid 15
[20-Sep-2016 08:32:29] NOTICE: ready to handle connections
[20-Sep-2016 08:38:05] NOTICE: fpm is running, pid 16
[20-Sep-2016 08:38:05] NOTICE: ready to handle connections
[20-Sep-2016 08:39:57] NOTICE: fpm is running, pid 15
[20-Sep-2016 08:39:57] NOTICE: ready to handle connections
[20-Sep-2016 08:44:25] NOTICE: fpm is running, pid 16
[20-Sep-2016 08:44:25] NOTICE: ready to handle connections
[20-Sep-2016 11:27:41] NOTICE: fpm is running, pid 16
[20-Sep-2016 11:27:41] NOTICE: ready to handle connections
[20-Sep-2016 16:50:37] NOTICE: fpm is running, pid 14
[20-Sep-2016 16:50:37] NOTICE: ready to handle connections
[21-Sep-2016 07:59:22] NOTICE: fpm is running, pid 16
[21-Sep-2016 07:59:22] NOTICE: ready to handle connections

Hm okay, seems normal. I'm going to investigate this too at the end of the week.
Are there any other limitations which may cause the problems? For example your provider which blocks, for some reason, some connections via the firewall?

found this in my logs
Uncaught Error: Class 'OCP\Lock\ILockingProvider' not found in /nextcloud/lib/private/Files/View.php:1152 Stack trace: #0 [internal function]: OC\Files\View->OC\Files\{closure}() #1 /nextcloud/apps/files_external/3rdparty/icewind/streams/src/CallbackWrapper.php(109): call_user_func(Object(Closure)) #2 [internal function]: Icewind\Streams\CallbackWrapper->stream_close() #3 {main} thrown at /nextcloud/lib/private/Files/View.php#1152

i guess that has n omeaning :)
but i also get this at my nginx reverse proxy error.log
2016/09/25 13:33:40 [error] 14#14: *5 upstream prematurely closed connection while reading upstream, client: <IP_ADDRESS>, server: nextcloud.hannesmueller.com, request: "GET /remote.php/webdav/07_Studium/07_Bachelor/Praktisch.rar?downloadStartSecret=3elyzqbww05kyajkymd1ud6lxr HTTP/2.0", upstream: "http://<IP_ADDRESS>:8888/remote.php/webdav/07_Studium/07_Bachelor/Praktisch.rar?downloadStartSecret=3elyzqbww05kyajkymd1ud6lxr", host: "nextcloud.hannesmueller.com"

Okay I tested it but it seems to work.
I'm using the default php settings of this container.
The only thing I've set is the connection_pool_size  10G setting for my nginx reverse proxy.
So for me it looks like the problems lays at your reverse proxy setup, although its logs says that the backend closed the connection.
Are there any other limitations which may cause this behavior? Are you running the service behind a firewall or something else.
One thing I mentioned: I'm using different cipher suites. But I don't think this has something todo with it.
One last thing: Whats in your /conf.d/proxy-params.conf file of your reverse proxy?

i would like to test with different connection_pool_size in my nginx settings (sites-enabled)
but when i change - nginx docker doesnt start up and givey me this error
cat /sites-enabled/nginx.conf
server {
  listen 8000;
  server_name nextcloud.mydomain.com;
  #rewrite ^ https://nextcloud.mydomain.com$request_uri? permanent;
  return 301 https://$host$request_uri;
}

server {

  listen 4430 ssl http2;
  server_name nextcloud.mydomain.com;
  client_max_body_size 10240;
  connection_pool_size 10G;
  ssl_certificate /certs/nextcloud/fullchain.pem;        # path to your cacert.pem
  ssl_certificate_key /certs/nextcloud/privkey.pem;      # path to your privkey.pem

  include /conf.d/ssl_params.conf;
  include /conf.d/headers.conf;

  access_log      /var/log/nginx/nextcloud.access.log;
  error_log       /var/log/nginx/nextcloud.error.log;
  location / {
    proxy_pass http://nextcloud:8888;
    include /conf.d/proxy-params.conf;
    fastcgi_read_timeout 10800;
  }
}

i get this
root@NAS:~# docker restart nginx
nginx
root@NAS:~# docker logs nginx
nginx: [emerg] "connection_pool_size" directive invalid value in /sites-enabled/nginx.conf:13

where do i need to set the connection_pool_size 10G; ??
cat /conf.d/proxy-params.conf
proxy_set_header        Host                 $host;
proxy_set_header        X-Real-IP            $remote_addr;
proxy_set_header        X-Forwarded-For      $proxy_add_x_forwarded_for;
proxy_set_header        X-Remote-Port        $remote_port;
proxy_set_header        X-Forwarded-Proto    $scheme;
proxy_redirect          off;

As described in the official nginx documentation you can set it in server or http context.
I also thought this problem could be caused by some memory limits of the proxies, that they cannot  buffer large files due to limitations but the log files imply something different.

cat /var/log/nginx/error.log
2016/09/26 11:10:46 [alert] 10#10: unlink() "/var/run/nginx.pid" failed (13: Permission denied)
does this something to do with ?

i dont think its the nginx reverse_proxy.
other webservices (emby also as reverseproxy) are allowing downloading files bigger than >1gb

cat /var/log/nginx/error.log
2016/09/26 11:10:46 [alert] 10#10: unlink() "/var/run/nginx.pid" failed (13: Permission denied)
does this has something to do with ?

I can't try actually, but can you try add there parameters on Dockerfile :
--pid-path=/tmp/nginx.pid \
--lock-path=/tmp/nginx.lock \

I don't think it's related, and @hardware has already fixed the problem : https://github.com/Wonderfall/dockerfiles/commit/87b57a74f39d6400760c205538a9af2a281390e6

can someone please send his reverse_proxy nextcloud.conf for nginx ?
Maybe i am missing something ?

although this is my nextcloud.conf
server {
  listen 8000;
  server_name nextcloud.mydomain.com;
  return 301 https://$host$request_uri;
}

server {
  listen 4430 ssl http2;
  server_name nextcloud.mydomain.com;

  ssl_certificate /certs/nextcloud/fullchain.pem;
  ssl_certificate_key /certs/nextcloud/privkey.pem;

  include /conf.d/ssl_params.conf;
  include /conf.d/headers.conf;

  location / {
    proxy_pass http://nextcloud:8888;
    include /conf.d/proxy-params.conf;
    client_max_body_size 10G;
  }
}

and i get securitywarning in administration site
Der „X-XSS-Protection“-HTTP-Header ist nicht so konfiguriert, dass er „1; mode=block“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
Der „X-Content-Type-Options“-HTTP-Header ist nicht so konfiguriert, dass er „nosniff“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.
Der „X-Frame-Options“-HTTP-Header ist nicht so konfiguriert, dass er „SAMEORIGIN“ entspricht. Dies ist ein potentielles Sicherheitsrisiko und es wird empfohlen, diese Einstellung zu ändern.

As said in the README, you shouldn't add security headers as they're already included in Nextcloud. In other words, you can remove this line to get rid of the security warnings : include /conf.d/headers.conf;.
Otherwise your nextcloud.conf looks good to me.

jquery?
i get this error in Chrome Console when i inspect and reload the site
Failed to parse SourceMap: https://nextcloud.mydomain.com/core/vendor/jquery/dist/jquery.min.map

i guess i found the error
Error	PHP	Uncaught Error: Class 'OCP\Lock\ILockingProvider' not found in /nextcloud/lib/private/Files/View.php:1152 Stack trace: #0 [internal function]: OC\Files\View->OC\Files\{closure}() #1 /nextcloud/3rdparty/icewind/streams/src/CallbackWrapper.php(109): call_user_func(Object(Closure)) #2 [internal function]: Icewind\Streams\CallbackWrapper->stream_close() #3 {main} thrown at /nextcloud/lib/private/Files/View.php#1152	a few seconds ago

updated to daily - same problem

I played around with some variables and for me it works well. I also found this which might be helpful.
I'm using the default nginx config from this project.
Then I changed the php-fpm.conf:
[global]
daemonize = no

[www]
listen = /tmp/php-fpm.sock
pm = dynamic
pm.max_children = 10
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 3
chdir = /
request_terminate_timeout = 0
env[PATH] = /usr/local/bin:/usr/bin:/bin
php_admin_value[post_max_size] = 16400M
php_admin_value[upload_max_filesize] = 16G
php_admin_value[max_execution_time] = 10800
php_admin_value[max_input_time] = 3600

Note the request_terminate_timeout = 0 which deactivates it and the php_admin_value[post_max_size] = 16400M (instead of 16GB).
My nginx reverse proxy config of this host:
client_max_body_size 16400M;
sendfile on;
default_type  application/octet-stream;
keepalive_timeout 15;
keepalive_disable msie6;
keepalive_requests 100;
tcp_nopush on;
tcp_nodelay on;
server_tokens off;

proxy_set_header Authorization $http_authorization;
proxy_pass_header  Authorization;

I don't know which of those caused the problems but deactivating request_terminate_timeout is a good choice here I guess.
The increasing of the max_input_time should also be done for php because some people may have slower internet connections. For nginx or the proxy this isn't necessary because nextcloud sends heartbeat requests.

did everything u said. u know what - i backup my files and resetup from ground up.
Can you confirm that these are good compose-settings  ?
nginx:
  image: wonderfall/nginx
  container_name: nginx
  links:
    - nextcloud:nextcloud
    - php
  ports:
    - "80:8000"
    - "443:4430"
  volumes:
    - /etc/localtime:/etc/localtime
    - /root/.nginx/sites-enabled:/sites-enabled
    - /root/.nginx/conf:/conf.d
    - /root/.nginx/log:/var/log/nginx
    - /root/.nginx/certs:/certs
    - /root/.nginx/htdocs:/www

php:
    container_name: php
    image: php:7-fpm
    volumes:
      - /root/.nginx/htdocs:/www

nextcloud:
    image: wonderfall/nextcloud:daily
    container_name: nextcloud
    links:
      - db_nextcloud:db_nextcloud
    environment:
      - UID=1000
      - GID=1000
      - UPLOAD_MAX_SIZE=20G
      - APC_SHM_SIZE=256M
      - OPCACHE_MEM_SIZE=256
      - CRON_PERIOD=15m
    volumes:
      - /etc/localtime:/etc/localtime
      - /media/19ad4901-a651-4001-9306-425956e2c501/Cloud/data:/data
      - /media/19ad4901-a651-4001-9306-425956e2c501/Cloud/config:/config
      - /media/19ad4901-a651-4001-9306-425956e2c501/Cloud/apps:/apps2
      - /media/19ad4901-a651-4001-9306-425956e2c501/Cloud/extra_data:/extra_data

nextcloud_db:
    image: mariadb:10
    volumes:
      - /media/19ad4901-a651-4001-9306-425956e2c501/Cloud_db:/var/lib/mysql
    container_name: nextcloud_db
    environment:
      - MYSQL_ROOT_PASSWORD=secret
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_PASSWORD=secret

nextcloud_collabora:
    image: collabora/code
    tty: true
    container_name: nextcloud_collabora
    ports:
      - "<IP_ADDRESS>:9980:9980"
    environment:
      - domain=nextcloud\.mydomain\.com
    cap_add:
      - MKNOD

Why are you using a separate php-fpm container? And are there other sites running on your host? Because the Wonderfall/nextcloud container already ships a nginx webserver with a php-fpm backend.
Also your setup says nothing about the configuration of these components.

i have regular website stuff running on my host. thats why i have php running on a extra docker.
made complete reinstall.
deleted db and volumes. still the same issue :(

Okay, tested again for larger files (> 2GB) and it's going to break again.
The error pop up still says Gateway Timed Out but this time I followed the 504 error and the API responded with The upload path couldn't be set.
I would also suggest to change the title, e.g. Error after uploading too large files (504).

Yeah me too, can't test with big files with my actual connection...
I thought about memory_limit too.

I got the idea to test it locally (e.g. with the Docker Toolbox) where your internet connection doesn't matter.
I want to share some insights, while I'm still investigating.
I created a simple setup using this docker-compose.yml file:
version: '2'

services:
  nextcloud:
   image: wonderfall/nextcloud
   ports:
     - "8080:8888"
   volumes:
     - "$PWD/volumes/config:/config"
   links:
     - mysql:mysql
   environment:
     - UID=1000
     - GID=1000

  mysql:
    image: mariadb
    environment:
      - MYSQL_ROOT_PASSWORD=123456
      -  MYSQL_DATABASE=nextcloud

This is the basic setup as it is served by @Wonderfall. And it works!
I haven't overwritten the default limit of 10GB and so far a 2.1GB file works.
tbc (currently investigating)

May be nginx bug
https://github.com/nginx/nginx/commit/bdc0b779e50cd3003e488e939b7d8006c8f47fd6

Any update on this?

With the following docker containers (just the default settings, no modifications):

nginx
jwilder/docker-gen
jrcs/letsencrypt-nginx-proxy-companion
wonderfall/nextcloud

I've managed to fix my problem with uploading big files, i got the "Entity(?) to big" error in the webui.
Add the line:
client_max_body_size 0;
in  nginx.tmpl file right below the line(59):
proxy_http_version 1.1;
Then restarted the nginx, docker-gen and nextcloud container, and now i can successfully upload the test file with a size of 65 MB.

project version: https://github.com/Wonderfall/dockerfiles/commit/9709a8690635d2db61e5aa0acdee8b20a3740809
I ran into a similar problem having "server replies: Gateway Time-out" during syncing with the nextcloud client 2.3.2 with a slow connection for even the smallest files. I used the suggested nginx proxy configuration from Readme.md@14ab668 as the following
server {
  listen 8000;
  server_name example.com;
  return 301 https://$host$request_uri;
}

server {
  listen 4430 ssl http2;
  server_name example.com;

  ssl_certificate /certs/example.com.crt;
  ssl_certificate_key /certs/example.com.key;

  include /etc/nginx/conf/ssl_params.conf;

  client_max_body_size 10G; # change this value it according to $UPLOAD_MAX_SIZE

  location / {
    proxy_pass http://nextcloud:8888;
    include /etc/nginx/conf/proxy_params;
  }
}

I resolved the issue for myself by extending the location block using the information from https://blog.virtualweb.at/fehler-beheben-504-gateway-time-out-bei-nginx-2
proxy_connect_timeout       600;
proxy_send_timeout          600;
proxy_read_timeout          600;
send_timeout                600;

Thank you for your great work and effort folks.


Typo "a Azure Stack"→"an Azure Stack"

https://learn.microsoft.com/en-us/azure-stack/ruggedized/integration-overview
https://github.com/MicrosoftDocs/azure-stack-docs/blob/main/azure-stack/ruggedized/integration-overview.md
#PingMSFTDocs

@sethmanheim
Can you review the proposed changes? If this is also a typo in the UI, can you file a bug to fix that as well?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Completion issue - latest api version not showing up first (if mixed casing in available RTs and depending on how you type the RT before completion)

Looks like api versions are not getting sorted properly:

Expected:
2020-10-01 in the top of the list
Actual:
2017-04-01 shows up first
cc: @mumian, @alex-frankel, @puicchan

FWIW, I am not able to repro, but others in our triage were able to repro with v0.13. Would be good to identify root cause.

I suspect this may be the cause:

I can't repro, even tried version 0.8.2.  Debugged through code and looked through changes, don't see any reason for this to occur.  The casing difference also doesn't seem to be an issue (I verified the 2-step sort is stable).
[0]: {microsoft.insights/activityLogAlerts@2017-03-01-preview}
[1]: {microsoft.insights/activityLogAlerts@2017-04-01}
[2]: {Microsoft.Insights/activityLogAlerts@2020-10-01}

@bhsubra Can you still repro this?  Thx.

@bhsubra Can you still repro this? Thx.

@StephenWeatherford, I can still repro the issue with version v0.15.31:

Turns out to be caused by both the mixing of the casing in the resource types and also what the user typed beforehand.
I.e., we have these completion items:
sortIndex=0: Microsoft.Insights/activityLogAlerts@2020-10-01
sortIndex=1: microsoft.insights/activityLogAlerts@2017-03-01-preview
sortIndex=2: microsoft.insights/activityLogAlerts@2017-04-01
In spite of this sort indices being correct, if you type the following (note the casing):
resource test 'microsoft.insights/activityLogAlerts@

and then show completion items, VS Code assigns a greater score to the second two items because they match the casing of what you have already typed.  (I was starting out with Microsoft.Insights/activityLogAlerts, and always got 2020-10-01 as preferred match).

Another repro:

@majastrz Appears fixed as well.

But, see related https://github.com/Azure/bicep/issues/10175


Get Git trademark permission or change name

I'm not from the SFC or Git folks, but I know GIt is careful about their trademark. Rather than dealing with it once this is more well-known, far better to deal with this now and either get permission or choose a new name for the project.

But we are Gitea, not Git.

Your use of "Git" in "Gitea" does in fact refer to "Git". GitHub and Gitorious and GitLab all had to get trademark permission from Git, and the site that used to be called Gittip was contacted by them with a warning/complaint insisting that they not use that name.

That is not currently emphsis work for gitea since gitea is not well-known. Thank you for your advice. @wolftune

@lunny my point is that it would be best to deal with this before it is well-known so that you either have permission and are good or change the name now rather than deal with the awkwardness of changing a name after something is well-known. Hopefully, by asking up front, there will be no issues, they'll just give permission.

:+1: https://git-scm.com/trademark

Yes. I have read the trademark. @DDaems
Thanks a lot, @wolftune. This is an important thing we will resolve it - Request a permission or change our name. But it will spend me many time and the first release of gitea is still on struggle. So the most important thing for gitea is to complete the first release version. And we can consider this issue in v0.8 or later.

I have the same issue with GitMarket, we contact them for permission and they denied... they ask us to change name. -_-

@P4KM4N What's a pity! But gitea is dead in fact. So I don't worry it. Please use Gogs.


Ideally, I think we would like to measure % of contributed code tested, specifically *.py files within /src folder(?)
Grateful if anyone can help with this... Thanks.

Thanks both. @notZaki that looks a lot better!
We should be merging in more tests soon.


Minor tweaks to intro so readers don't need to know what sealevel is

Sealevel is great, but it's not necessary to understand Sealevel to use Anchor.
This PR takes the existing language in the intro 'build secure Solana programs quickly' and makes it the main tagline.

Thanks! Is there anything we need to do to make it show up on https://www.anchor-lang.com/?


Potentially wrong IDE type hint in Route facade

I've noticed that in src/Illuminate/Support/Facades/Route.php on line 24 there's a static keyword missing, which causes my IDE to give me an error:

Is this intentional?

Yes this is intentional. You can look at https://github.com/barryvdh/laravel-ide-helper. Also next time use the forums or the slack channel as this repo is for bug tracking.

Noted, sorry.


pvtFilterBox position

hi
The drop down menu position in the pivot table was not showing up correctly.
However, I've solved this problem and I'll share it in case anyone else needs help.
The solution is simple, you just need to fix some parts of your pivot.js file
Before
 triangleLink = $("<span>").addClass('pvtTriangle').html(" ▾").bind("click", function(e) {
            var left, ref2, top;
            ref2 = $(e.currentTarget).position(), left = ref2.left, top = ref2.top;
            return valueList.css({
              left: left + 10,
              top: top + 10
            }).show();
          });

After
triangleLink = $("<span>").addClass('pvtTriangle').html(" ▾").bind("click", function(e) {
            var left, ref2, top;
            ref2 = $(e.currentTarget).offset(), left = ref2.left, top = ref2.top;   // <--change
            return valueList.css({
              left: left + 10,
              top: top + $(e.currentTarget).outerHeight() + 10    // <--change
            }).show();
          });

Thanks for sharing that. I am not a JS developer expert so I can not help that much, however, it will be great if we try to get back live this repo again.

Thanks for the great library.


How to support ClickHouse source in branch 1.12 ?

ClickHouse Source is only supported by Flink 1.13(or higher) in your project, is there any way support ClickHouse Source in Flink 1.12?

Yes, but needs a little work.

Checkout branch release-1.13, then modify the flink dependency version to 1.12.x;
Execute the command mvn clean package -DskipTests to compile the project and fix compile error.
The compiled package is available under flink 1.12.x;

Yes, but needs a little work.

Checkout branch release-1.13, then modify the flink dependency version to 1.12.x;
Execute the command mvn clean package -DskipTests to compile the project and fix compile error.
The compiled package is available under flink 1.12.x;


Netlify failing on every PR

Describe the bug

Netlify: "Deploy did not complete for chef-automate" -- this message is being generated for every PR for some weeks now.

To Reproduce
Open a PR. Observe a failure notification posted in #a2-notify in slack.
Expected behavior
Process should run to completion.
Successful output of Netlify manifests as ?? (I think docs-team can supply this detail.)

The underlying issue is that Netlify won't make a build preview if there are no changes in components/docs-chef-io. Any build that isn't completed is classified as a failure and so we get the warning above. They do have a feature request in for changing notification, but who knows when that will happen.


Create "R" recipe button

Okay I made the R button.

Okay, sounds good. How do I see your work so I can add on to it?


Orchestration: In Volume provisioning page, there is no validation for destination host ip.

Orchestration: In Volume provisioning page, validation should be there for atleast IP, Size(it should not take string etc.), PORT etc.

@PravinRanjan10 Volume provisioning under the Volume tab in Resources?

Possible duplicate of #154


prompt dialogs for gtk

Added the prompt dialogs for gtk. Follows osdialog_message in gtk2 code and the osdialog_prompt implementation for Mac. Needed for cf's Label plugin and more plugins will allow user input when this is implemented on more than just Mac.

Thanks!


SAK-40605 Samigo class cast on update order button for published assessments

refactor to use generics to solve the class cast issue

@ern I've made some minor comments to improve the PR a bit, but looks good to me, I've approved it.
btw, THANKS A LOT @ern, I like this way, you've improved the overall quality of the files and this will help users in the future. I did the same in #6317 and offered a soft solution in #6316 so approvers can choose. If we can spend some time in this awful files and improve them, will help us in the future!


Dev

add:

CodeSnapshotViewport: related to #5, the CodeSnapshot frame will be containerized inside an indipendent Viewport. This will also improve the Snapshot image acquisition, just using the Viewport's texture and without calculating any offset / size.
Transparent background support: it is now possible to take snapshots with transparent background, just using a frame color with alpa = 0

use lines count as min size: new property added to let the plugin set a min vertical size for the frame, or make it customizable

add:

CodeSnapshotViewport: related to #5, the CodeSnapshot frame will be containerized inside an indipendent Viewport. This will also improve the Snapshot image acquisition, just using the Viewport's texture and without calculating any offset / size.
Transparent background support: it is now possible to take snapshots with transparent background, just using a frame color with alpa = 0

use lines count as min size: new property added to let the plugin set a min vertical size for the frame, or make it customizable

add:

CodeSnapshotViewport: related to #5, the CodeSnapshot frame will be containerized inside an indipendent Viewport. This will also improve the Snapshot image acquisition, just using the Viewport's texture and without calculating any offset / size.
Transparent background support: it is now possible to take snapshots with transparent background, just using a frame color with alpa = 0

use lines count as min size: new property added to let the plugin set a min vertical size for the frame, or make it customizable

add:

CodeSnapshotViewport: related to #5, the CodeSnapshot frame will be containerized inside an indipendent Viewport. This will also improve the Snapshot image acquisition, just using the Viewport's texture and without calculating any offset / size.
Transparent background support: it is now possible to take snapshots with transparent background, just using a frame color with alpa = 0

use lines count as min size: new property added to let the plugin set a min vertical size for the frame, or make it customizable


Allow using ai-binary for code generation only, not code fixing

Testing a model tuned for code generation.
I will improve the code later:

Separate code generation and code fixing models.
Allow users to customize code generation and code fixing models individually.

Should we instead expose this to a CLI argument and thread it from there to here?

Yes, that's the 'improve the code later' part : )
I was running some local experiments with this now and forgot to turn this into a draft.


extra space added to rendered html

Describe the bug
extra space added to rendered html
example writing

Welcome, User-1

actual output

Welcome, User - 1

expected output

Welcome, User-1

Leptos Dependencies
[package]
name = "gs-logviewer-leptos"
version = "0.1.0"
edition = "2021"

[lib]
crate-type = ["cdylib", "rlib"]

[dependencies]
leptos = { version = "0.7.0" }
leptos_router = { version = "0.7.0" }
axum = { version = "0.7", optional = true }
console_error_panic_hook = "0.1"
leptos_axum = { version = "0.7.0", optional = true }
leptos_meta = { version = "0.7.0" }
tokio = { version = "1", features = ["rt-multi-thread"], optional = true }
tower = { version = "0.4", optional = true }
tower-http = { version = "0.5", features = ["fs"], optional = true }
wasm-bindgen = "=0.2.96"
thiserror = "1"
tracing = { version = "0.1", optional = true }
http = "1"

[features]
hydrate = ["leptos/hydrate"]
ssr = [
  "dep:axum",
  "dep:tokio",
  "dep:tower",
  "dep:tower-http",
  "dep:leptos_axum",
  "leptos/ssr",
  "leptos_meta/ssr",
  "leptos_router/ssr",
  "dep:tracing",
]

# Defines a size-optimized profile for the WASM bundle in release mode
[profile.wasm-release]
inherits = "release"
opt-level = 'z'
lto = true
codegen-units = 1
panic = "abort"

[package.metadata.leptos]
# The name used by wasm-bindgen/cargo-leptos for the JS/WASM bundle. Defaults to the crate name
output-name = "gs-logviewer-leptos"

# The site root folder is where cargo-leptos generate all output. WARNING: all content of this folder will be erased on a rebuild. Use it in your server setup.
site-root = "target/site"

# The site-root relative folder where all compiled output (JS, WASM and CSS) is written
# Defaults to pkg
site-pkg-dir = "pkg"

# [Optional] The source CSS file. If it ends with .sass or .scss then it will be compiled by dart-sass into CSS. The CSS is optimized by Lightning CSS before being written to <site-root>/<site-pkg>/app.css
style-file = "style/main.scss"
# Assets source dir. All files found here will be copied and synchronized to site-root.
# The assets-dir cannot have a sub directory with the same name/path as site-pkg-dir.
#
# Optional. Env: LEPTOS_ASSETS_DIR.
assets-dir = "public"

# The IP and port (ex: <IP_ADDRESS>:3000) where the server serves the content. Use it in your server setup.
site-addr = "<IP_ADDRESS>:13000"

# The port to use for automatic reload monitoring
reload-port = 13001

# [Optional] Command to use when running end2end tests. It will run in the end2end dir.
#   [Windows] for non-WSL use "npx.cmd playwright test"
#   This binary name can be checked in Powershell with Get-Command npx
end2end-cmd = "npx playwright test"
end2end-dir = "end2end"

#  The browserlist query used for optimizing the CSS.
browserquery = "defaults"

# The environment Leptos will run in, usually either "DEV" or "PROD"
env = "DEV"

# The features to use when compiling the bin target
#
# Optional. Can be over-ridden with the command line parameter --bin-features
bin-features = ["ssr"]

# If the --no-default-features flag should be used when compiling the bin target
#
# Optional. Defaults to false.
bin-default-features = false

# The features to use when compiling the lib target
#
# Optional. Can be over-ridden with the command line parameter --lib-features
lib-features = ["hydrate"]

# If the --no-default-features flag should be used when compiling the lib target
#
# Optional. Defaults to false.
lib-default-features = false

# The profile to use for the lib target when compiling for release
#
# Optional. Defaults to "release".
lib-profile-release = "wasm-release"

To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

While there is some support for unquoted text nodes, it is not perfect, especially in cases that involve non-alphanumeric cases (like the -) in your example.
You should simply wrap the text node in quotations, which is the default and typically-documented way to use a string in the view macro:

"Welcome, User-1"

how if we need to write actual quote?
eg
let abc = "example"; // example-1

These are ordinary Rust string literals. Do you know how to escape a double-quote in an ordinary Rust string? You can do the same here. "let abc = \"example\"; // example-1"

Thanks for your help


Implement notification form confirmation

Summary of Changes
This PR adds notification confirmation to improve the user experience of sending a request for more metadata.
FlashMessage
This PR creates new common component FlashMessage, and styles it as closely as possible to the design specification for this component. It takes an iconClass for an optional icon, a message, and an onClose method that will get executed when the FlashMessage is dismissed.
RequestMetadataForm
Added a sendState to the notifications state. This is updated in the notifications reducer accordingly, and passed to RequestMedataForm.
RequestMetadataForm has support to render the FlashMessage based on the sendState. The user dismisses the FlashMessage by clicking on the x.

Tests
Added tests to cover component additions/changes. Modified tests to cover notification reducer modifications.
Documentation
N/A
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes, including screenshots of any UI changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes all tests documented in the developer guide

Codecov Report

Merging #289 into amundsen-notifications will increase coverage by 0.21%.
The diff coverage is 100%.

@@                    Coverage Diff                     @@
##           amundsen-notifications     #289      +/-   ##
==========================================================
+ Coverage                   70.87%   71.08%   +0.21%
==========================================================
  Files                         139      140       +1
  Lines                        3512     3538      +26
  Branches                      422      425       +3
==========================================================
+ Hits                         2489     2515      +26
  Misses                        989      989
  Partials                       34       34

Impacted Files
Coverage Δ

..._application/static/js/ducks/notification/types.ts
100% <ø> (ø)
:arrow_up:

...dsen_application/static/js/fixtures/globalState.ts
100% <ø> (ø)
:arrow_up:

...pplication/static/js/ducks/notification/reducer.ts
100% <100%> (ø)
:arrow_up:

...mponents/TableDetail/RequestMetadataForm/index.tsx
100% <100%> (ø)
:arrow_up:

...nents/TableDetail/RequestMetadataForm/constants.ts
100% <100%> (ø)
:arrow_up:

...static/js/components/common/FlashMessage/index.tsx
100% <100%> (ø)

..._application/static/js/ducks/notification/sagas.ts
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Switch to a more visually obvious button for the threadgate

Small but IMO useful for highlighting this feature.
EDIT: Video doesnt show -- I moved into the "keyboard sticky" region which therefore maintains consistent positioning when keyboard is open on mobile
https://github.com/bluesky-social/social-app/assets/1270099/cfb32f62-16e2-47c3-bb8f-6b86bfda9d1c
https://github.com/bluesky-social/social-app/assets/1270099/7163d692-93d4-42ed-9fb2-b380ecbef255
https://github.com/bluesky-social/social-app/assets/1270099/5c007113-2da2-4bd9-880d-22753297bc8a

Video doesnt show -- I moved into the "keyboard sticky" region which therefore maintains consistent positioning when keyboard is open on mobile


Integrate latest industry practices

Hi,
Great library.  But you know what would make it better?  Integrating Dagger2 for dependency injection, RxJava for awesome asynchronous behavior, some MVP code organization.  Are there any plans to use these in the works?
Thank you,
Igor

RxJava consists of 3k methods. Not every developer uses RxJava in his projects. Less dependencies = good for library users.

+1 for avoiding unnecessary dependencies.  When you start including the support and design libraries and Google Play services, it's really easy to hit the 65k method ceiling quickly.  Yes, there are ways around this, but all of them complicate and/or slow down the build process.


packagemanifests not created

Bug Report
What did you do?
trying to install operator by OLM
What did you expect to see?
packagemanifests created and  operator installed
What did you see instead? Under which circumstances?
can't find packagemanifests related

Environment

operator-lifecycle-manager version:

v0.16.1

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.3-tke.11", GitCommit:"43d7ff3fae76c311692393308feeca4ceb740ebc", GitTreeState:"clean", BuildDate:"2020-10-12T03:32:22Z", GoVersion:"go1.12.14", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.3-tke.11", GitCommit:"43d7ff3fae76c311692393308feeca4ceb740ebc", GitTreeState:"clean", BuildDate:"2020-10-12T03:37:10Z", GoVersion:"go1.12.14", Compiler:"gc", Platform:"linux/amd64"}

btw, I'm following this steps:   https://github.com/operator-framework/operator-registry#using-the-index-with-operator-lifecycle-manager

switch to bundle installation


[FSDE-11802] Added support of Brightspeed theme compilation

As a demo of the new theme compilation, I changed Checkbox component Checked state color to indigo in Brightspeed theme. So please open the PR instance Checkbox component page and change:
<link rel="stylesheet" href="/chi.css" id="chi-css">
to
<link rel="stylesheet" href="/chi-brightspeed.css" id="chi-css">
You should be able to see the checkbox checked state with the color indigo.

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-272/1/. :white_check_mark:

You can check this PRs instance in https://b80e3babab30058147199eb71e6c4fc743b2663b-chi-pr.enterprise.ctl.io (external) and in https://nginx-pr-272-ux-chi.kubeodc-test.corp.intranet/ (internal)

The CI pipeline did not run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-272/2/. :x:

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-272/3/. :white_check_mark:

You can check this PRs instance in https://b00a55a2cfd8e63cc6f0e94aa3eb1ddf7cd77c43-chi-pr.enterprise.ctl.io (external) and in https://nginx-pr-272-ux-chi.kubeodc-test.corp.intranet/ (internal)

@janibolkvadze , is there a way to update the documentation CSS file? I tried adding ?theme=Brightspeed to the URL but it didn't work. Apart from that, all the code looks good.

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-272/5/. :white_check_mark:

You can check this PRs instance in https://6b0cc57fb4aa0a9c4d9f32e3deb2d2c613c3fc45-chi-pr.enterprise.ctl.io (external) and in https://nginx-pr-272-ux-chi.kubeodc-test.corp.intranet/ (internal)

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-272/6/. :white_check_mark:

You can check this PRs instance in https://90d27796a0f91400689d2dd060b887c168d8d7c2-chi-pr.enterprise.ctl.io (external) and in https://nginx-pr-272-ux-chi.kubeodc-test.corp.intranet/ (internal)


Support groupChar for integer field type

fixes https://github.com/frictionlessdata/specs/issues/498
improves "default value" wording

Rationale
Group char character is often used with integers similar to numbers. There is no reason to have this property for numbers but not to have it for integers.

The wording "This property does not have a default value" seems odd. I'd say it's just an optional property.

@nichtich
Thanks for pointing it out! The problem is that all these properties are optional by definition. Initially, it has a remark that the default value is null, which is not fully correct (it's not defined but not null). So I'm not sure how to phrase it.
My idea that we will go through wording on the next iteration as the project has a separate "Improve technical language" task while, currently, we need to make principal change decisions which require attention of the whole WG

CONSIDERED by WG (3/9)
cc @sapetti9 if we need to clarify acceptance criteria after adding a "neutral" voting option

@pschumm
@khusmann
@ezwelty
@PietrH
@nichtich
@peterdesmet
Would you consider changing (or adding) your vote to yes as currently we can't accept this change with 3 votes are missing? In my opinion this feature is no-brainer and honestly must-have that was missing for some weird reasons as without group char for integers it's just not possible to have any number like 1,000, 1,200,000 etc which is pretty common for data publishing in many countries

@pschumm Would you consider changing (or adding) your vote to yes as currently we can't accept this change with 3 votes are missing?

Changed my vote to yes (not sure at the moment why I hadn't voted that way before on this). Agreed it's both necessary and consistent.

Thanks!
ACCEPTED by the WG (6/9)


Checklist for 2023.02

Improvements:

[ ] Make use of line directive information for compile time errors [6bc209fc] [89c23ddf]
[ ] Improve error message on "foo".Order [665375ba]
[ ] Try to be more explicit when exception reporting dies [45b19784]
[ ] Make X::Method::NotFound more resilient [eff02440]

Additions:

[x] Allow for .rakutest as extension of Rakudo test files [4a42b211] [0d49c2e7]
[x] Implement numeric coercers for Date/DateTime [72856df9]
[x] Allow * to be used as identity on classify|categorize [4b264b80]
[x] Introduce $*EXIT / $*EXCEPTION dynamic vars [50050866]
[x] Add In Memoriam for Ben Davies [ccbf9a09][3d2f8bd9]
[x] Add Complex.sign to v6.e [34cf82aa] (#4199)
[x] Add Unicode class to v6.c [db7ca2dd]
[x] Make log and sqrt handle negative values mathematically correct in v6.e [760e21c1]
[x] Make RakuAST:: classes available with use experimental :rakuast [c9cb334e]

note that commit IDs are for rakudo, not this repo

.rakutest mentioned in the intro perl6->raku section in d66241c3d, need to check remaining docs.

I think the "Improvements" section can all be checked.  Or am I missing something?

I think the "Improvements" section can all be checked. Or am I missing something?

Agreed; they don't seem relevant to user-facing docs.

Everything is checked, closing.


Error

I have a problem, in all the modes. When I would like to download, this appears :
Error: SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at getVideo (C:\Users\antob\Downloads\TikTok\tiktok-downloader\index.js:126:24)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async C:\Users\antob\Downloads\TikTok\tiktok-downloader\index.js:320:20
Response body:
C:\Users\antob\Downloads\TikTok\tiktok-downloader\index.js:133
if (res.aweme_list[0].aweme_id != idVideo) {
^
TypeError: Cannot read properties of undefined (reading 'aweme_list')
at getVideo (C:\Users\antob\Downloads\TikTok\tiktok-downloader\index.js:133:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async C:\Users\antob\Downloads\TikTok\tiktok-downloader\index.js:320:20

It's a tiktok endpoint API problem, it affects us all. See #50


Advantages of using Kubernetes

I read the guide of scaling SC.
It talks about two options: with or without Kubernetes.
But it does not mention why I would choose one over the other. There is no guidance or mention of any deciding factors.
Please elaborate and clarify the criteria for each of the two options.

It depends on if you want to automate your infrastructure or not.
If you have a very large production system with hundreds of machines then K8s would be very helpful.

@idibidiart We have 7 nodes in our production environment and I never got around to using Kubernetes... I wish I had. I've been meaning to go back and fix this mistake but I haven't got the time to take care of it. I would suggest you start with Kubernetes. I wrote a deploy script that works for now but I'm sure I would have been better off learning Kubernetes from the start.