Css treeshaking not working

Describe the bug
We want to use the svelte kit library configuration to build a component library that we integrate into a svelte kit app. When we import components as modules. For example like this:
import { Heading } from "svelte-kit-library";

Then we get in the build files all css stylings of other components that are not used or imported in the application. If the components are imported explicitly, there are no unwanted stylings in the build files.
import Heading from "svelte-kit-library/Heading.svelte";

Reproduction
Checkout this example repository: https://github.com/tomolenet/svelte-kit-treeshaking
In packages/svelte-kit-app we use the packages/svelte-kit-library in src/routes/+page.svelte. First use the module import in line 7.
import { Heading } from "svelte-kit-library";

# build app
npm run build -w packages/svelte-kit-app

Now check the output packages/svelte-kit-app/.svelte-kit. If you search for .unwanted which is styling of the Unwanted component of packages/svelte-kit-library you realize that styling exists in the build result. However, we have not imported the component at any point in the project.
Now change the import statement and use explicit import in line 10.
import Heading from "svelte-kit-library/Heading.svelte";

# build app
npm run build -w packages/svelte-kit-app

Now the .unwanted class is no longer included in the build. It seems that the tree shaking does not work correctly at this point.
Logs
No response
System Info
System:
    OS: Linux 6.5 Manjaro Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
    Memory: 10.07 GB / 15.29 GB
    Container: Yes
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node
    npm: 10.1.0 - ~/.nvm/versions/node/v20.9.0/bin/npm
  Browsers:
    Chromium: 119.0.6045.199

Severity
serious, but I can work around it
Additional Information
For large component libraries that are used in applications that need to be very performant, this is a big problem as stylesheets are created that are far too large.

It looks like this is also expected behaviour here: https://github.com/sveltejs/svelte/issues/9501#issuecomment-2035835317


grafana: 8.3.1 -> 8.3.2, fix CVE-2021-43813, CVE-2021-43815

Motivation for this change
ChangeLog: https://github.com/grafana/grafana/releases/tag/v8.3.2
cc @vojta001 please check if you still have the problem as with 8.3.1. Unfortunately I'm having a hard time to find out whcih testcase exactly broke in your case.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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/)
22.05 Release Notes (or backporting 21.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

[x] Fits CONTRIBUTING.md.

nixpkgs-review happy on macos 10.15 nixos x86_64 & aarch64.

Patch for 21.05 (using Grafana 7.5.12) in https://github.com/NixOS/nixpkgs/pull/150466.


Close void tags with slashes to support XHTML

This fixes https://github.com/developit/preact-render-to-string/issues/24 by closing void element tags with a /. It updates relevant tests accordingly.

Silly question: do we care about adding a space before /? 😅

Hmm, I'd be surprised if it was ever an issue in practice but actually the specs (https://www.w3.org/TR/html5/syntax.html#void-elements, https://www.w3.org/TR/xhtml1/#guidelines) do call for it so probably best. I'll tweak that now.

Perfect, LGTM.


"could not find __ Joy-Con"

Not sure what I did wrong but when I get to the finding-Joy-Cons step, XJoy says "could not find left Joy-Con" (or right Joy-Con, depending). Both are connected/paired to Windows as "Joy-Con (L)" and "Joy-Con (R)" under "Mouse, keyboard, & pen."
Note a possible complicating factor: I'm running Windows on a Mac via KB Parallels virtual machine. I might be overlooking something as I'm not great with Windows.
Thanks.

That might be the source of your trouble. I would verify first that bluetooth devices work properly in Parallels (as in pair something like a keyboard or xbox controller and see if you can actually use it, not just pair it). My husband actually uses this same setup so I could try debugging if nothing else works.

It could be that they are coming in with a different product id. Is there a way you can check that?

My guess is this is a parallels specific issue. I don't have a mac, so I can't investigate any further.


Chatgpt  boot

Gd evening
Can you give me  reference of  this project۔

There is already a reference section on README.md

Send me reference if you are not busy
On Thu, 22 Jun, 2023, 11:44 pm Alamin Hossain, @.***>
wrote:

There is already a reference section on README.md
—
Reply to this email directly, view it on GitHub
https://github.com/linux-china/chatgpt-spring-boot-starter/issues/8#issuecomment-1603111609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6VLFHB2PWQRKMPJB6JG5ULXMSDPXANCNFSM6AAAAAAZQMSHAM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Send me reference if you are not busy
On Thu, 22 Jun, 2023, 11:44 pm Alamin Hossain, @.***>
wrote:

There is already a reference section on README.md
—
Reply to this email directly, view it on GitHub
https://github.com/linux-china/chatgpt-spring-boot-starter/issues/8#issuecomment-1603111609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6VLFHB2PWQRKMPJB6JG5ULXMSDPXANCNFSM6AAAAAAZQMSHAM
.
You are receiving this because you authored the thread.Message ID:
@.***>

References:

OpenAI chat API. Retrieved from https://platform.openai.com/docs/api-reference/chat

Spring Boot 3.0+. Retrieved from https://docs.spring.io/spring-boot/docs/current/reference/html/

Spring Boot Webflux. Retrieved from https://docs.spring.io/spring-framework/reference/web/webflux.html

Spring 6 HTTP interface. Retrieved from https://docs.spring.io/spring-framework/reference/integration/rest-clients.htm

l#rest-http-interface

Properties File Format. Retrieved from https://docs.oracle.com/cd/E23095_01/Platform.93/ATGProgGuide/html/s0204propertiesfileformat01.html

MessageFormat JavaDoc. Retrieved from https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/text/MessageFormat.html

Should I use this project as thesis
On Fri, 23 Jun, 2023, 8:18 am Alamin Hossain, @.***>
wrote:

References:

OpenAI chat API. Retrieved from
https://platform.openai.com/docs/api-reference/chat
Spring Boot 3.0+. Retrieved from
https://docs.spring.io/spring-boot/docs/current/reference/html/
Spring Boot Webflux. Retrieved from
https://docs.spring.io/spring-framework/reference/web/webflux.html
Spring 6 HTTP interface. Retrieved from
https://docs.spring.io/spring-framework/reference/integration/rest-clients.htm
l#rest-http-interface

Properties File Format. Retrieved from
https://docs.oracle.com/cd/E23095_01/Platform.93/ATGProgGuide/html/s0204propertiesfileformat01.html
MessageFormat JavaDoc. Retrieved from
https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/text/MessageFormat.html
—
Reply to this email directly, view it on GitHub
https://github.com/linux-china/chatgpt-spring-boot-starter/issues/8#issuecomment-1603613245,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6VLFHFTLE2DBB5NPO5SO33XMT7WLANCNFSM6AAAAAAZQMSHAM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Should I use this project as thesis
On Fri, 23 Jun, 2023, 9:45 am Mohammad abass, @.***> wrote:

Should I use this project as thesis
On Fri, 23 Jun, 2023, 8:18 am Alamin Hossain, @.***>
wrote:

References:

OpenAI chat API. Retrieved from
https://platform.openai.com/docs/api-reference/chat
Spring Boot 3.0+. Retrieved from
https://docs.spring.io/spring-boot/docs/current/reference/html/
Spring Boot Webflux. Retrieved from
https://docs.spring.io/spring-framework/reference/web/webflux.html
Spring 6 HTTP interface. Retrieved from
https://docs.spring.io/spring-framework/reference/integration/rest-clients.htm
l#rest-http-interface

Properties File Format. Retrieved from
https://docs.oracle.com/cd/E23095_01/Platform.93/ATGProgGuide/html/s0204propertiesfileformat01.html
MessageFormat JavaDoc. Retrieved from
https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/text/MessageFormat.html
—
Reply to this email directly, view it on GitHub
https://github.com/linux-china/chatgpt-spring-boot-starter/issues/8#issuecomment-1603613245,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6VLFHFTLE2DBB5NPO5SO33XMT7WLANCNFSM6AAAAAAZQMSHAM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Should I use this project as thesis
…
On Fri, 23 Jun, 2023, 9:45 am Mohammad abass, @.> wrote: Should I use this project as thesis On Fri, 23 Jun, 2023, 8:18 am Alamin Hossain, @.> wrote: > References: > > - > > OpenAI chat API. Retrieved from > https://platform.openai.com/docs/api-reference/chat > - > > Spring Boot 3.0+. Retrieved from > https://docs.spring.io/spring-boot/docs/current/reference/html/ > - > > Spring Boot Webflux. Retrieved from > https://docs.spring.io/spring-framework/reference/web/webflux.html > - > > Spring 6 HTTP interface. Retrieved from > https://docs.spring.io/spring-framework/reference/integration/rest-clients.htm > > l#rest-http-interface > > - > > Properties File Format. Retrieved from > https://docs.oracle.com/cd/E23095_01/Platform.93/ATGProgGuide/html/s0204propertiesfileformat01.html > - > > MessageFormat JavaDoc. Retrieved from > https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/text/MessageFormat.html > > — > Reply to this email directly, view it on GitHub > <#8 (comment)>, > or unsubscribe > https://github.com/notifications/unsubscribe-auth/A6VLFHFTLE2DBB5NPO5SO33XMT7WLANCNFSM6AAAAAAZQMSHAM > . > You are receiving this because you authored the thread.Message ID: > @.***> >

I am not sure but you should read their TERMS AND CONDITIONS, here is the link: https://github.com/linux-china/chatgpt-spring-boot-starter/blob/ea85127e78ecaca4e16ffa55a2a23cb634dcd06e/LICENSE.txt

Then after that how to use this project
I read all conditions in this project
Copyright, etc but sir you are not sure
How should I do it
On Fri, 23 Jun, 2023, 10:06 am Alamin Hossain, @.***>
wrote:

Should I use this project as thesis
… <#m_1260698991263587225_m_1736082721894934052_>
On Fri, 23 Jun, 2023, 9:45 am Mohammad abass, @.> wrote: Should I use
this project as thesis On Fri, 23 Jun, 2023, 8:18 am Alamin Hossain, @.>
wrote: > References: > > - > > OpenAI chat API. Retrieved from >
https://platform.openai.com/docs/api-reference/chat > - > > Spring Boot
3.0+. Retrieved from >
https://docs.spring.io/spring-boot/docs/current/reference/html/ > - > >
Spring Boot Webflux. Retrieved from >
https://docs.spring.io/spring-framework/reference/web/webflux.html > - >

Spring 6 HTTP interface. Retrieved from >
https://docs.spring.io/spring-framework/reference/integration/rest-clients.htm

l#rest-http-interface > > - > > Properties File Format. Retrieved from

https://docs.oracle.com/cd/E23095_01/Platform.93/ATGProgGuide/html/s0204propertiesfileformat01.html

MessageFormat JavaDoc. Retrieved from >
https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/text/MessageFormat.html

— > Reply to this email directly, view it on GitHub > <#8 (comment)
https://github.com/linux-china/chatgpt-spring-boot-starter/issues/8#issuecomment-1603613245>,
or unsubscribe >
https://github.com/notifications/unsubscribe-auth/A6VLFHFTLE2DBB5NPO5SO33XMT7WLANCNFSM6AAAAAAZQMSHAM
. > You are receiving this because you authored the thread.Message ID: >
@.***> >

I am not sure but you should read their TERMS AND CONDITIONS, here is the
link:
https://github.com/linux-china/chatgpt-spring-boot-starter/blob/ea85127e78ecaca4e16ffa55a2a23cb634dcd06e/LICENSE.txt
—
Reply to this email directly, view it on GitHub
https://github.com/linux-china/chatgpt-spring-boot-starter/issues/8#issuecomment-1603668866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6VLFHCRX4MVGED34KGJRGTXMUMLLANCNFSM6AAAAAAZQMSHAM
.
You are receiving this because you commented.Message ID:
@.***>

I am not the author of this repository, so I cannot give you more information about that.

Ok, thank you. You alloted to me in your precious time
On Fri, 23 Jun, 2023, 11:00 am Alamin Hossain, @.***>
wrote:

I am not the author of this repository, so I cannot give you more
information about that.
—
Reply to this email directly, view it on GitHub
https://github.com/linux-china/chatgpt-spring-boot-starter/issues/8#issuecomment-1603700982,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6VLFHFDJUDPUTRA4UVY4WLXMUSX7ANCNFSM6AAAAAAZQMSHAM
.
You are receiving this because you commented.Message ID:
@.***>

@abassdar chatgpt-spring-boot-starter is a open source project with Apache License 2.0, and you can use it in any project, even business projects.


Create a Calculation View with Differential Privacy in SAP HANA Cloud

Tutorials: https://developers.sap.com/tutorials/hana-cloud-calculation-view-differential-privacy.html
Write here how you think we can improve the tutorial ...
Hi Team,
The provided material is very good and helpful, But in the tool when I follwed the same process while creating the calculation view nothing is coming up it is like a blank screen which keeps on running as shown below.
Please help to update anything if we missed to add installation command for Creating Hana views ? Even I have seen the same thread which other user is also facing. Please find the attached link.
https://answers.sap.com/questions/13421902/calculation-view-editor-in-sap-business-applicatio.html?childToView=13422669
Expecting your valuble solution for the same to proceed further .

Thanks.
Regards,
jagadeesh.

This does not appear to be any issue with the steps in the tutorial itself. It would appear to be a problem in the Calculation View editor itself. For that we would suggest that you post your question in the SAP Community Q&A or open a support ticket for the Business Application Studio Calculation View editor itself.

Hi Thomas,
Thanks for your quick response. I was using the HANA Cloud BTP Trail platform. Could you please help me on the procedure how to raise a support ticket for the same . It wolud be very helpful if there is any specific document with steps to be followed for the trail edition.
Thanks.
Regards,
jagadeesh.


Give option to turn off “format-on-save” for specific file formats, like HTML

Because spaces MATTER in HTML.

Closing as a duplicate of #13547


[BUG] Startup on 3.1.0 consumes too much cpu

Environment
Self-Hosted (Docker)
System
Docker version 26.1.1, build 4cf5afa
Version
3.1.0
Describe the problem
After launching the container with switching to 3.1.0, the memory/cpu consumption starts going through the roof. I hadn't put constraints on this container (now I do :)) and it was taking over my VM:
6e8b003b68a1   dashy                       190.58%   739.2MiB / 1GiB       72.19%    8.11kB / 1.68kB   897kB / 24.6kB    212

it will cycle through very quickly to take all the available memory/cpu.
Additional info
No response
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

Hi
I can't seem to reproduce your issue, neither lissy I guess.
Could you share a bit more?
RAM usage on dashy container available ram, cpu usage.
Does it ever go down, or just the first build?

Same thing. Updated today and RAM & CPU overloaded

Could you provide more details?
Does dashy always consume such high amouts, just at start?
Can you share like some more info about ram and cpu usage of the container?
This can be viewed the easiest with portainer.

Same thing. Updated today and RAM & CPU overloaded

Could you provide more details?
Does dashy always consume such high amouts, just at start? Can you share like some more info about ram and cpu usage of the container? This can be viewed the easiest with portainer.

I just make repull to update dashy and right after start i see 4 processes "vue-cli-service build", that consume all avaible memory and CPU, so other containers were not avaible. Even console works with huge lags... Only hard reset helps and right after rebbot need to quick stop dashy

Please be more specific.
Does the usage go down after some time, like 5 min at max?
How much RAM exactly?
How much have you assigned?
The first build of dashy takes a bit more ressources, but there aren't any more rebuilds neccessary later on.

Please be more specific.
Does the usage go down after some time, like 5 min at max?
How much RAM exactly? How much have you assigned?
The first build of dashy takes a bit more ressources, but there aren't any more rebuilds neccessary later on.

I've waited about 30 mins, but as other contaniers doesn't working, i goes to hard reset Host 2 Gb RAM, 2 vCPU, all avaible for dashy.

@DerLokich
Just for testing, could you extend it to 3GB RAM ?
And would you mind sending a screenshot of the ressource usage from container start to like 10minutes?
After freshly pulling the image?
This can be done with portainer:
docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest

Thanks!

To @twsouthwick 1GB is way too less for dashy V3, it needs at least 2GB.
While I got it to work with a raspberrypi which only has 1GB of RAM memory management is compledtely different compared to like a VM or a big server running dashy.

@DerLokich
Just for testing, could you extend it to 3GB RAM ?
And would you mind sending a screenshot of the ressource usage from container start to like 10minutes? After freshly pulling the image?
This can be done with portainer:
docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest

Thanks!

Can't extend, it's VPS in another country :).
Just for testing i tried to take screenshot in portainer, but VM stuck after eating all resources...
Only last output of htop avaible now:

Waited till now, so it's about 90 min, no effect. Hard reset VM.

I've updated it to 3gb, and even with the resource constraints, my VM becomes unresponsive:
services:
  dashy:
    container_name: 'dashy'
    image: lissy93/dashy:3.1.0
    restart: no #unless-stopped
    deploy:
      resources:
        limits:
          cpus: '2'
          memory: 3gb

I'll try to gather some more details this weekendn

Out of curiosity, what is the value of rebuilding the dashboard in the container? Why not just ship a prebuilt component with the container? I think historically dashy needed the config as part of the build, but now it doesn't need it, right? It makes the dashboard a fairly heavyweight system as it is.

Out of curiosity, what is the value of rebuilding the dashboard in the container?

I think currently it needs to rebuild for other things like for example auth needs a rebuild, custom css, added files like icons, defaultView change and some other very specific things.
So in general file changes or additions not related to conf.yml still require a rebuild.
@Lissy93 Please correct me if I'm wrong.

I'll try to gather some more details this weekendn

Thanks, that'd  be awesome!
Because I really cannot reproduce this here and I think lissy has also never been able to reproduce this issue.

I've had the same issue as well. I thought it was my issue, so I rebuilt the container, but it just chewed up the CPU and memory again.

I'll look into this, as somethings definatley not right here, while Node (used for build) is a bit heavy, it shouldn't ever be consuming that amount of resources.
So far, haven't been able to reproduce.
@DerLokich - it looks like build is being run multiple times, which is weird because it is only needed once.

Looks like memory consumption isn't the issue - but it spikes to 20cpus and then the system sends a kill as it's taken all the cpus of the machine.

And the system sends a kill:
 WARN  A new version of sass-loader is available. Please upgrade for best experience.
error Command failed with signal "SIGKILL".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at target._send (node:internal/child_process:879:20)
    at target.send (node:internal/child_process:752:19)
    at callback (/app/node_modules/worker-farm/lib/child/index.js:32:17)
    at module.exports (/app/node_modules/terser-webpack-plugin/dist/worker.js:13:5)
    at handle (/app/node_modules/worker-farm/lib/child/index.js:44:8)
    at process.<anonymous> (/app/node_modules/worker-farm/lib/child/index.js:55:3)
    at process.emit (node:events:518:28)
    at emit (node:internal/child_process:951:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on process instance at:
    at node:internal/child_process:883:39
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

Node.js v20.11.1
node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at target._send (node:internal/child_process:879:20)
    at target.send (node:internal/child_process:752:19)
    at callback (/app/node_modules/worker-farm/lib/child/index.js:32:17)
    at module.exports (/app/node_modules/terser-webpack-plugin/dist/worker.js:13:5)
    at handle (/app/node_modules/worker-farm/lib/child/index.js:44:8)
    at process.<anonymous> (/app/node_modules/worker-farm/lib/child/index.js:55:3)
    at process.emit (node:events:518:28)
    at emit (node:internal/child_process:951:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on process instance at:
    at node:internal/child_process:883:39
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

I see logs and it looks like Dashy is building in docker while startup. It looks strange. It consumes almost all my VPS resources (I have a small VPS with 2 CPU and 2GB RAM. It also takes a lot of time, I've been waiting about 5 minutes and Dashy still doesn't start :(
Maybe I missunderstand the main idea, but I think any application should be built once, packaged once into docker-image. Once, not N-times during each (or first) startup. Or are there any reasons to perform build during container startup?
There is a part of my docker-compose with Dashy:
  dashy:
    image: lissy93/dashy
    container_name: dashy
    ports:
      - "4000:8080"
    # Set any environmental variables
    environment:
      - NODE_ENV=production
    # Specify your user ID and group ID. You can find this by running `id -u` and `id -g`
      - UID=1000
      - GID=1000
    restart: unless-stopped
    healthcheck:
      test: ['CMD', 'node', '/app/services/healthcheck']
      interval: 1m30s
      timeout: 10s
      retries: 3
      start_period: 40s

Guys, any news about this issue? :)

I have the same behavior. The app rebuilds on every update of the compose file:
Using Dashy V-3.1.1. Update Check Complete

✅ Dashy is Up-to-Date

-  Building for production...

 WARN  A new version of sass-loader is available. Please upgrade for best experience.

 DONE  Compiled successfully in 47128ms9:22:12 AM

I'm also kind of having this issue. I'm running v3.1.1 with Docker on a Raspberry 4, with 4GB of RAM. I am able to run one instance, CPU and RAM usage almost tops but it stabilizes after a couple of minutes. If I try to spin up a second container, the host freezes and I have to cut the power.
Prior to v3 I was able to run 3 instances at the same time whilst I was doing some tests. I wasn't usually letting them rebuild at the same time, the system froze, but it ended up working if I had patience enough. I mean I usually started them sequentially to avoid the total lack of response so I could keep working, but if I wanted to I could start all 3 go for a coffee and come back.
This is to say that I do notice a big change in behavior. Earlier I believe every rebuild took about 1GB RAM and around 40% CPU, so running two was fine, the third one was already pushing the limits. Now CPU is usually above 50% during build, with peaks over 90. And RAM usage went from 1,4 to 2,8GB peaking at 3,3GB.
I don't really see this as an issue with the app but probably with some framework. You were one of the reasons I started learning Vue and after my tiny personal project grew a bit I'm also seeing how the performance of the build process tanks. I love this project so I'm happy to help. Let me know if I can provide any specific details or logs.

The docker image should come with dashy already built, I have never seen a docker image doing building on "production"

This should be number one priority, because the way i see most of us cant use dashy, even though we want to we end up settling for something like homarr instead. The number one issue for user as advertised everywhere is it is easy to deploy. I have used docker and i have yet seen such a tough installation in my whole experience. Unless you dont want everyone to use dashy, why are you trapping everyone to believing that it is deployable on docker while it is not, and it is very frustrating to do so. This is sad to be honest. Let the open source society be if you cant add to it as you are expected to do so. Its useless to look at any dashy video review that says how amazing it is now.

Agree i was regular user i have almost stopped using it as it keeps going out of memory. Any other work is not of any use because product is not working at all.

which version works? anyone?

which version works? anyone?

I am running latest (v3.1.1) on a Raspberry 4 (4GB RAM). Previously I was running v2.1.0 for a year without issues. Tested both ARM and x86/64 architectures.
This issue is about it consuming too many resources during initial startup, not that it doesn't work at all.

The issue happens when it's building the /dist dir. I've attempted mounting that to a folder on the local system so that it doesn't need to rebuild it each time and haven't had much success going that route as of yet.
It takes up about 2.5G of RAM during the build, when it's completed, it returns to normal usage.

The docker image has the following command/CMD set: [yarn,build-and-start] which is then passed to the docker-entrypoint.sh that just executes that. The command should rather be server.js which then gets executed by the entrypoint.
So in this current state, the image is not unusable but it doesn't work with the default command.
This becomes a problem in the Helm chart (https://github.com/vyrtualsynthese/selfhosted-helmcharts/tree/main/charts/dashy) because there is no possibility to change the executed command.

@SimonWoidig
No #1559 did not bring up that issue.
Before V3 yarn build-and-start was the default command, to ensure when for example a user mapps files into the container, they get picked up and dashy rebuilds, on config changes, on display-view changes etc.
in V3 config loading got dynamic, so rebuilding was no longer needed, a user suggested to change it to start instead of build-and-start -> #1543
Then we kinda got flooded with issues, and due to lissy being invited to Github Accelerator a while ago she barely had time to look into this, so we decided temporarly reverting the command back to it's original yarn build-and-start, as it was before V3 is the best idea.
I have since not heard back from lissy.
Have you got anything to add @Lissy93

@SimonWoidig
No #1559 did not bring up that issue.
Before V3 yarn build-and-start was the default command, to ensure when for example a user mapps files into the container, they get picked up and dashy rebuilds, on config changes, on display-view changes etc.
in V3 config loading got dynamic, so rebuilding was no longer needed, a user suggested to change it to start instead of build-and-start -> #1543
Then we kinda got flooded with issues, and due to lissy being invited to Github Accelerator a while ago she barely had time to look into this, so we decided temporarly reverting the command back to it's original yarn build-and-start, as it was before V3 is the best idea.
I have since not heard back from lissy.
Have you got anything to add @Lissy93

Sorry if I misunderstood. I just used git blame to see, when the command was changed. I didn't know about the config rebuilding and such.
I really like this project and I just wanted to find the root cause.
Thank you for your work and I understand if life gets a bit too busy. I just hope, we can get this fixed. And I apologize if I came off a bit harsh.

Oh no, no worries at all!
Yeah hope for the same!

Mounting /app/dist/ does not work as a workaround because some script tries to remove it before the build.
I must also support @thegamerx1 I have never before seen a docker image that builds the fronted on start (let alone on every restart!). It should be included in the pre-build image.
Also, this is a Dashboard - it should not take up close to 2 GB of RAM (even during start).

I started slowly shifting away to alternatives, sadly ....
https://github.com/awesome-selfhosted/awesome-selfhosted?tab=readme-ov-file#personal-dashboards
I have a feeling, this won't get fixed that quickly.


Use correct announce-port directive

There is a typo in the sentinel configuration where the announce port is incorrectly being included as the announce IP.

@imnotjames sorry for the long delay here, I just recently started maintaining this cookbook. Thanks for finding and fixing this. I will merge and release this shortly.

released: https://supermarket.chef.io/cookbooks/redisio/versions/2.7.1


Refactor lib.sh with generic await function

PR for Issue #665. Consolidate scripts/lib.sh into a single generic await function, and standardise on four space indentation.

Codecov Report
Base: 64.22% // Head: 64.22% // No change to project coverage :thumbsup:

Coverage data is based on head (ea5c039) compared to base (561af43).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #942   +/-   ##
=======================================
  Coverage   64.22%   64.22%
=======================================
  Files         112      112
  Lines       16408    16408
=======================================
  Hits        10538    10538
  Misses       5870     5870

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Needs some work, as the await function is called in two different ways - with a command testing against exit code (which is working), and a known string comparison against a delayed execution that needs to re-eval per loop. I'll take another look when I have time.

The scripts/lib.sh has been refactored. I think this issue is outdated and can be closed.

I think the issue is still relevant, just nobody got around to finishing the PR and now it's too outdated. If someone wants to tackle #665 it's still an interesting starting point.


Update Rancher API integration to go-rancher client v2.

Update rancher api integration to go-rancher client v2. Set default service name and host rule to <service_name>.<stack_name>. on rancher integration

Description

Update rancher api integration to go-rancher client v2, to use stacks not environments.
Allow the use of labels to autogenerate endpoint, accesskey and secretkey with labels

io.rancher.container.agent.role: environment
io.rancher.container.create_agent: true

Set default service name and host rule to <service_name>.<stack_name>. on rancher integration (api and metadata), to match default dns rancher naming.

@rawmind0 Could you manage the vendor files?
https://github.com/containous/traefik/blob/master/CONTRIBUTING.md#setting-up-glide-and-glide-vc-for-dependency-management

@rawmind0 I will manage the glide part 😄

Thanks @ldez ...Tell me if you need anything else... :)

@rawmind0 could you allow maintainer to modify your branch (the checkbox in this PR)?

@rawmind0 done!

Thanks so much @ldez .. :)

This change is just generating default traefik frontend rule to Host: service.stack.domain instead of Host: stack.service.domain , to make it match with default rancher dns entries. You could test that default traefik rontend rule is generated like that.

ping @SantoDE

Isn't backward incompatible change? Going from stack.service.domain to service.stack.domain. Curious whether it should be behind a feature flag otherwise going from 1.4 to 1.5 will be painful. Another option is to mention it as a breaking change in changelog. I'd also love to see it as a backport to 1.4 branch to be better prepared. Great stuff!


Random swithing of pages because collision issue

I looked at the sample scene where switching pages is quite random. The reason is that the ray can collide accidentally with nearby collision boxes. Maybe if you use a player camera with a variable angle, this will not be a problem, but with the  book camera aimed at 90 degrees to the collision boxes is. Here is a simple method that I just tested to avoid this issue:
func _on_StaticBody_input_event(camera, event, position, normal, shape_idx):

if event is InputEventMouseButton :
		if(shape_idx == 0):
			turn_left()
		if(shape_idx == 1):
			turn_right()

Hi! Thanks for your input! :)
The thing with Interactive Book project is that it started as a "normal" 3D project, but I've made experiments with VR as well. I haven't touched this code for a while, but if I remember correctly, in VR you are supposed to move the camera, and in standard 3D you should be using arrow keys instead (left and right). I'm afraid the arrow keys are disabled in VR for some reason :(
So, to fix this properly, I need to provide a nice default 3D scene, probably the "normal" one, but make it clear that VR is also an option (or make a switch in the app itself). I will have to think this through :P
Thank you for pointing this out, I have neglected this project a bit, this might motivate me to polish it a bit more :D

I think that 3D book will be useful for education fragments. I will use it directly at current stage, however implementation as interactive item is a good idea. Also in-game camera is good idea too: https://usagishima.net/2021/03/18/devlog-1-in-game-camera-and-photo-album/
I tried it, however not like interactive object since there are not any option for dropping items from inventory.

Hi! I realized that my local copy of this repo has a lot of experimental changes, so I checked the clean version :smile:  The default scene starts in VR mode, and if it runs on a desktop computer, then the switching of pages is, indeed, random. I'm afraid checking the collision shape ID would not help here, because the raycast that aims directly ahead will still randomly pick one of them (each area has only one collision shape). Until I figure out how to clean up this project, I would suggest enabling the keyboard in this scene:
+       if Input.is_action_just_pressed("ui_left"):
+               turn_left()
+       if Input.is_action_just_pressed("ui_right"):
+               turn_right()

Of course, this will not work in VR (at least not on Android, where I test it :stuck_out_tongue: ) but it would make the pages work in desktop mode for now. Do you think this solution would solve your problem?

I've added that code to the repo, I hope it will help you :)  If you have other suggestions for improvements, please let me know!


Fix TS error in AddModelDialog.tsx

          Contains a workaround where the file AddModelDialog.tsx contains a commented out TS error on line 79. The UseEffect complains about how it is set up.

Originally posted by @mheggelund in https://github.com/equinor/pepm-ui/issues/116#issuecomment-1755237905

@mheggelund you can move the function (missing dependency) inside the useEffect to solve the issue, unless the function is used other places as well - then you can wrap the function in a useCallback, add it as a dependency and it should do the same trick. 😇


elasticsearch dies on Windows

Downloaded this repo, extracted to local path, ran docker-compose up. Everything appeared to start ok. Navigate to localhost:5601 and get redirected to http://localhost:5601/login?next=%2F with ERR_TOO_MANY_REDIRECTS
This repeats in the on-screen logs:
heartbeat_1         | 2017/06/01 16:42:09.412778 scheduler.go:294: INFO Scheduled job 'http@http://kibana:5601' already active.
heartbeat_1         | 2017/06/01 16:42:09.412802 scheduler.go:294: INFO Scheduled job 'icmp-host-ip@kibana' already active.
heartbeat_1         | 2017/06/01 16:42:09.412805 scheduler.go:294: INFO Scheduled job 'icmp-host-ip@elasticsearch' already active.
heartbeat_1         | 2017/06/01 16:42:09.412809 scheduler.go:294: INFO Scheduled job 'http@http://elasticsearch:9200' already active.
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:09Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:09Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
logstash_1          | [2017-06-01T16:42:10,286][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://logstash_system:xxxxxx@elasticsearch:9200/, :path=>"/"}
logstash_1          | [2017-06-01T16:42:10,288][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://logstash_system:xxxxxx@elasticsearch:9200/, :path=>"/"}
logstash_1          | [2017-06-01T16:42:10,288][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://elastic:xxxxxx@elasticsearch:9200/, :path=>"/"}
logstash_1          | [2017-06-01T16:42:10,291][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>#<URI::HTTP:0x3c6ad621 URL:http://logstash_system:xxxxxx@elasticsearch:9200/>, :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://logstash_system:xxxxxx@elasticsearch:9200/][Manticore::ResolutionFailure] elasticsearch"}
logstash_1          | [2017-06-01T16:42:10,291][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>#<URI::HTTP:0x8363560 URL:http://logstash_system:xxxxxx@elasticsearch:9200/>, :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://logstash_system:xxxxxx@elasticsearch:9200/][Manticore::ResolutionFailure] elasticsearch"}
logstash_1          | [2017-06-01T16:42:10,293][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>#<URI::HTTP:0x45e416c3 URL:http://elastic:xxxxxx@elasticsearch:9200/>, :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://elastic:xxxxxx@elasticsearch:9200/][Manticore::ResolutionFailure] elasticsearch"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:11Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:11Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:11Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:11Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:12Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:12Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:14Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:14Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:14Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1            | {"type":"log","@timestamp":"2017-06-01T16:42:14Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}

checked running containers
$docker ps
CONTAINER ID        IMAGE                                       COMMAND                  CREATED             STATUS              PORTS                      NAMES
ff485e736be5        docker.elastic.co/logstash/logstash:5.4.1   "/usr/local/bin/do..."   42 minutes ago      Up 42 minutes       5044/tcp, 9600/tcp         elasticstack_logstash_1
fd1c78457958        docker.elastic.co/kibana/kibana:5.4.1       "/bin/sh -c /usr/l..."      42 minutes ago      Up 42 minutes                                  elasticstack_packetbeat_1
8cf96cc725b6        docker.elastic.co/beats/heartbeat:5.4.1     "heartbeat -e"           42 minutes ago      Up 42 minutes                                  elasticstack_heartbeat_1
03c3d500fb0a        docker.elastic.co/beats/filebeat:5.4.1      "filebeat -e"            42 minutes ago      Up 42 minutes                                  elasticstack_filebeat_1
673508ac78f4        docker.elastic.co/beats/metricbeat:5.4.1    "metricbeat -e"          42 minutes ago      Up 42 minutes                                  elasticstack_metricbeat_1

no elasticsearch in the list, checking logs
docker logs elasticstack_elasticsearch_1
[2017-06-01T16:01:24,748][INFO ][o.e.n.Node               ] [] initializing ...
[2017-06-01T16:01:24,888][INFO ][o.e.e.NodeEnvironment    ] [3lDg5IK] using [1] data paths, mounts [[/ (overlay)]], net usable_space [48.8gb], net total_space [58.8gb], spins? [possibly], types [overlay]
[2017-06-01T16:01:24,889][INFO ][o.e.e.NodeEnvironment    ] [3lDg5IK] heap size [1.9gb], compressed ordinary object pointers [true]
[2017-06-01T16:01:24,890][INFO ][o.e.n.Node               ] node name [3lDg5IK] derived from node ID [3lDg5IKgS2mZmPIGQvudxw]; set [node.name] to override
[2017-06-01T16:01:24,891][INFO ][o.e.n.Node               ] version[5.4.1], pid[1], build[2cfe0df/2017-05-29T16:05:51.443Z], OS[Linux/4.9.30-moby/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_131/25.131-b12]
[2017-06-01T16:01:24,891][INFO ][o.e.n.Node               ] JVM arguments [-Xms2g, -Xmx2g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+DisableExplicitGC, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutOfMemoryError, -Des.cgroups.hierarchy.override=/, -Des.path.home=/usr/share/elasticsearch]
[2017-06-01T16:01:30,610][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [aggs-matrix-stats]
[2017-06-01T16:01:30,611][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [ingest-common]
[2017-06-01T16:01:30,611][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [lang-expression]
[2017-06-01T16:01:30,611][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [lang-groovy]
[2017-06-01T16:01:30,612][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [lang-mustache]
[2017-06-01T16:01:30,613][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [lang-painless]
[2017-06-01T16:01:30,613][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [percolator]
[2017-06-01T16:01:30,614][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [reindex]
[2017-06-01T16:01:30,614][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [transport-netty3]
[2017-06-01T16:01:30,614][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded module [transport-netty4]
[2017-06-01T16:01:30,619][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded plugin [ingest-geoip]
[2017-06-01T16:01:30,620][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded plugin [ingest-user-agent]
[2017-06-01T16:01:30,620][INFO ][o.e.p.PluginsService     ] [3lDg5IK] loaded plugin [x-pack]

I have similar issue when trying to run just elastic search docker image, it starts then dies, not seeing anything in the elastic logs that's giving me any clues.
$ docker version
Client:
 Version:      17.06.0-ce-rc1
 API version:  1.30
 Go version:   go1.8.1
 Git commit:   7f8486a
 Built:        Wed May 31 02:54:33 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.06.0-ce-rc1
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.1
 Git commit:   7f8486a
 Built:        Wed May 31 03:00:14 2017
 OS/Arch:      linux/amd64
 Experimental: true

$ docker-compose version
docker-compose version 1.13.0, build 1719ceb8
docker-py version: 2.2.1
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j  26 Sep 2016

Using Docker for Windows Edge as the stable channel doesn't support docker-compose 3.2.

Managed to capture on screen logs from startup
docker-compose up
Creating network "elasticstack_stack" with the default driver
Creating elasticstack_elasticsearch_1 ...
Creating elasticstack_elasticsearch_1 ... done
Creating elasticstack_logstash_1 ...
Creating elasticstack_kibana_1 ...
Creating elasticstack_heartbeat_1 ...
Creating elasticstack_metricbeat_1 ...
Creating elasticstack_filebeat_1 ...
Creating elasticstack_packetbeat_1 ...
Creating elasticstack_kibana_1
Creating elasticstack_logstash_1
Creating elasticstack_heartbeat_1
Creating elasticstack_metricbeat_1
Creating elasticstack_filebeat_1
Creating elasticstack_heartbeat_1 ... done
Creating elasticstack_logstash_1 ... done
Creating elasticstack_configure_kibana_1 ... done
Attaching to elasticstack_elasticsearch_1, elasticstack_packetbeat_1, elasticstack_metricbeat_1, elasticstack_kibana_1, elasticstack_filebeat_1, elasticstack_heartbeat_1, elasticstack_logstash_1, elasticstack_configure_kibana_1
packetbeat_1        | 2017/06/01 16:56:57.094036 beat.go:285: INFO Home path: [/usr/share/packetbeat] Config path: [/usr/share/packetbeat] Data path: [/usr/share/packetbeat/data] Logs path: [/usr/share/packetbeat/logs]
packetbeat_1        | 2017/06/01 16:56:57.094141 metrics.go:23: INFO Metrics logging every 30s
packetbeat_1        | 2017/06/01 16:56:57.094074 beat.go:186: INFO Setup Beat: packetbeat; Version: 5.4.1
metricbeat_1        | 2017/06/01 16:56:58.572080 beat.go:285: INFO Home path: [/usr/share/metricbeat] Config path: [/usr/share/metricbeat] Data path: [/usr/share/metricbeat/data] Logs path: [/usr/share/metricbeat/logs]
packetbeat_1        | 2017/06/01 16:56:57.095984 add_cloud_metadata.go:231: INFO add_cloud_metadata: hosting provider type not detected.
metricbeat_1        | 2017/06/01 16:56:58.573259 beat.go:186: INFO Setup Beat: metricbeat; Version: 5.4.1
packetbeat_1        | 2017/06/01 16:56:57.096086 output.go:258: INFO Loading template enabled. Reading template file: /usr/share/packetbeat/packetbeat.template.json
metricbeat_1        | 2017/06/01 16:56:58.572842 metrics.go:23: INFO Metrics logging every 30s
packetbeat_1        | 2017/06/01 16:56:57.099370 output.go:269: INFO Loading template enabled for Elasticsearch 2.x. Reading template file: /usr/share/packetbeat/packetbeat.template-es2x.json
metricbeat_1        | 2017/06/01 16:56:58.580567 add_cloud_metadata.go:231: INFO add_cloud_metadata: hosting provider type not detected.
packetbeat_1        | 2017/06/01 16:56:57.139597 output.go:281: INFO Loading template enabled for Elasticsearch 6.x. Reading template file: /usr/share/packetbeat/packetbeat.template-es6x.json
metricbeat_1        | 2017/06/01 16:56:58.581589 output.go:258: INFO Loading template enabled. Reading template file: /usr/share/metricbeat/metricbeat.template.json
filebeat_1          | 2017/06/01 16:56:59.519922 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
metricbeat_1        | 2017/06/01 16:56:58.584325 output.go:269: INFO Loading template enabled for Elasticsearch 2.x. Reading template file: /usr/share/metricbeat/metricbeat.template-es2x.json
packetbeat_1        | 2017/06/01 16:56:58.484159 client.go:123: INFO Elasticsearch url: http://localhost:9200
filebeat_1          | 2017/06/01 16:56:59.520258 beat.go:186: INFO Setup Beat: filebeat; Version: 5.4.1
metricbeat_1        | 2017/06/01 16:56:58.587292 output.go:281: INFO Loading template enabled for Elasticsearch 6.x. Reading template file: /usr/share/metricbeat/metricbeat.template-es6x.json
heartbeat_1         | 2017/06/01 16:57:00.544161 beat.go:285: INFO Home path: [/usr/share/heartbeat] Config path: [/usr/share/heartbeat] Data path: [/usr/share/heartbeat/data] Logs path: [/usr/share/heartbeat/logs]
packetbeat_1        | 2017/06/01 16:56:58.527429 outputs.go:108: INFO Activated elasticsearch as output plugin.
filebeat_1          | 2017/06/01 16:56:59.521852 metrics.go:23: INFO Metrics logging every 30s
metricbeat_1        | 2017/06/01 16:56:58.595529 client.go:123: INFO Elasticsearch url: http://elasticsearch:9200
heartbeat_1         | 2017/06/01 16:57:00.544646 beat.go:186: INFO Setup Beat: heartbeat; Version: 5.4.1
packetbeat_1        | 2017/06/01 16:56:58.532950 publish.go:295: INFO Publisher name: moby
metricbeat_1        | 2017/06/01 16:56:58.595575 outputs.go:108: INFO Activated elasticsearch as output plugin.
filebeat_1          | 2017/06/01 16:56:59.522286 add_cloud_metadata.go:231: INFO add_cloud_metadata: hosting provider type not detected.
heartbeat_1         | 2017/06/01 16:57:00.545109 metrics.go:23: INFO Metrics logging every 30s
packetbeat_1        | 2017/06/01 16:56:58.537661 async.go:63: INFO Flush Interval set to: 1s
metricbeat_1        | 2017/06/01 16:56:58.595922 publish.go:295: INFO Publisher name: a70d7bd01c7b
filebeat_1          | 2017/06/01 16:56:59.522421 output.go:258: INFO Loading template enabled. Reading template file: /usr/share/filebeat/filebeat.template.json
heartbeat_1         | 2017/06/01 16:57:00.556534 add_cloud_metadata.go:231: INFO add_cloud_metadata: hosting provider type not detected.
packetbeat_1        | 2017/06/01 16:56:58.537673 async.go:64: INFO Max Bulk Size set to: 50
metricbeat_1        | 2017/06/01 16:56:58.597996 async.go:63: INFO Flush Interval set to: 1s
heartbeat_1         | 2017/06/01 16:57:00.556700 output.go:258: INFO Loading template enabled. Reading template file: /usr/share/heartbeat/heartbeat.template.json
filebeat_1          | 2017/06/01 16:56:59.524180 output.go:269: INFO Loading template enabled for Elasticsearch 2.x. Reading template file: /usr/share/filebeat/filebeat.template-es2x.json
packetbeat_1        | 2017/06/01 16:56:58.541435 procs.go:79: INFO Process matching disabled
metricbeat_1        | 2017/06/01 16:56:58.598013 async.go:64: INFO Max Bulk Size set to: 50
heartbeat_1         | 2017/06/01 16:57:00.572049 output.go:269: INFO Loading template enabled for Elasticsearch 2.x. Reading template file: /usr/share/heartbeat/heartbeat.template-es2x.json
packetbeat_1        | 2017/06/01 16:56:58.544501 protos.go:89: INFO registered protocol plugin: cassandra
filebeat_1          | 2017/06/01 16:56:59.525397 output.go:281: INFO Loading template enabled for Elasticsearch 6.x. Reading template file: /usr/share/filebeat/filebeat.template-es6x.json
metricbeat_1        | 2017/06/01 16:56:58.598082 metricbeat.go:28: INFO Register [ModuleFactory:[docker, mongodb, mysql, postgresql, system], MetricSetFactory:[apache/status, ceph/cluster_disk, ceph/cluster_health, ceph/monitor_health, ceph/pool_disk, couchbase/bucket, couchbase/cluster, couchbase/node, docker/container, docker/cpu, docker/diskio, docker/healthcheck, docker/image, docker/info, docker/memory, docker/network, haproxy/info, haproxy/stat, jolokia/jmx, kafka/consumergroup, kafka/partition, mongodb/dbstats, mongodb/status, mysql/status, nginx/stubstatus, php_fpm/pool, postgresql/activity, postgresql/bgwriter, postgresql/database, prometheus/collector, prometheus/stats, redis/info, redis/keyspace, system/core, system/cpu, system/diskio, system/filesystem, system/fsstat, system/load, system/memory, system/network, system/process, system/socket, zookeeper/mntr]]
heartbeat_1         | 2017/06/01 16:57:00.580071 output.go:281: INFO Loading template enabled for Elasticsearch 6.x. Reading template file: /usr/share/heartbeat/heartbeat.template-es6x.json
packetbeat_1        | 2017/06/01 16:56:58.544512 protos.go:89: INFO registered protocol plugin: dns
filebeat_1          | 2017/06/01 16:56:59.526849 client.go:123: INFO Elasticsearch url: http://elasticsearch:9200
metricbeat_1        | 2017/06/01 16:56:58.599586 socket.go:64: INFO socket process info will only be available for metricbeat because the process is running as a non-root user
heartbeat_1         | 2017/06/01 16:57:00.580645 client.go:123: INFO Elasticsearch url: http://elasticsearch:9200
packetbeat_1        | 2017/06/01 16:56:58.544517 protos.go:89: INFO registered protocol plugin: memcache
metricbeat_1        | 2017/06/01 16:56:58.600160 beat.go:221: INFO metricbeat start running.
filebeat_1          | 2017/06/01 16:56:59.527188 outputs.go:108: INFO Activated elasticsearch as output plugin.
heartbeat_1         | 2017/06/01 16:57:00.580680 outputs.go:108: INFO Activated elasticsearch as output plugin.
packetbeat_1        | 2017/06/01 16:56:58.544520 protos.go:89: INFO registered protocol plugin: mysql
metricbeat_1        | 2017/06/01 16:56:59.621860 single.go:140: ERR Connecting error publishing events (retrying): Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: getsockopt: connection refused
heartbeat_1         | 2017/06/01 16:57:00.580778 publish.go:295: INFO Publisher name: f804b43344af
filebeat_1          | 2017/06/01 16:56:59.528247 publish.go:295: INFO Publisher name: 9cc51dc6a392
packetbeat_1        | 2017/06/01 16:56:58.544523 protos.go:89: INFO registered protocol plugin: redis
metricbeat_1        | 2017/06/01 16:57:00.625488 single.go:140: ERR Connecting error publishing events (retrying): Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: getsockopt: connection refused
heartbeat_1         | 2017/06/01 16:57:00.581316 async.go:63: INFO Flush Interval set to: 1s
filebeat_1          | 2017/06/01 16:56:59.530541 async.go:63: INFO Flush Interval set to: 1s
packetbeat_1        | 2017/06/01 16:56:58.544527 protos.go:89: INFO registered protocol plugin: thrift
heartbeat_1         | 2017/06/01 16:57:00.581332 async.go:64: INFO Max Bulk Size set to: 50
filebeat_1          | 2017/06/01 16:56:59.530579 async.go:64: INFO Max Bulk Size set to: 50
packetbeat_1        | 2017/06/01 16:56:58.544530 protos.go:89: INFO registered protocol plugin: amqp
filebeat_1          | 2017/06/01 16:56:59.539730 beat.go:221: INFO filebeat start running.
heartbeat_1         | 2017/06/01 16:57:00.581353 heartbeat.go:26: WARN Beta: Heartbeat is beta software
packetbeat_1        | 2017/06/01 16:56:58.544534 protos.go:89: INFO registered protocol plugin: mongodb
filebeat_1          | 2017/06/01 16:56:59.540002 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
heartbeat_1         | 2017/06/01 16:57:00.581394 manager.go:96: INFO Select (active) monitor http
packetbeat_1        | 2017/06/01 16:56:58.544537 protos.go:89: INFO registered protocol plugin: nfs
filebeat_1          | 2017/06/01 16:56:59.555972 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
heartbeat_1         | 2017/06/01 16:57:00.581411 manager.go:96: INFO Select (active) monitor icmp
packetbeat_1        | 2017/06/01 16:56:58.544540 protos.go:89: INFO registered protocol plugin: pgsql
filebeat_1          | 2017/06/01 16:56:59.556020 registrar.go:123: INFO States Loaded from registrar: 0
packetbeat_1        | 2017/06/01 16:56:58.544543 protos.go:89: INFO registered protocol plugin: http
heartbeat_1         | 2017/06/01 16:57:00.590337 beat.go:221: INFO heartbeat start running.
filebeat_1          | 2017/06/01 16:56:59.556082 crawler.go:38: INFO Loading Prospectors: 1
heartbeat_1         | 2017/06/01 16:57:00.590382 heartbeat.go:60: INFO heartbeat is running! Hit CTRL-C to stop it.
packetbeat_1        | 2017/06/01 16:56:58.616075 beat.go:221: INFO packetbeat start running.
filebeat_1          | 2017/06/01 16:56:59.556164 registrar.go:236: INFO Starting Registrar
filebeat_1          | 2017/06/01 16:56:59.556212 sync.go:41: INFO Start sending events to output
filebeat_1          | 2017/06/01 16:56:59.556313 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
filebeat_1          | 2017/06/01 16:56:59.556513 prospector_log.go:65: INFO Prospector with previous states loaded: 0
filebeat_1          | 2017/06/01 16:56:59.556583 prospector.go:124: INFO Starting prospector of type: log; id:<PHONE_NUMBER>696397032
filebeat_1          | 2017/06/01 16:56:59.556598 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
configure_kibana_1  | Waiting for Kibana...
metricbeat_1        | 2017/06/01 16:57:02.643796 single.go:140: ERR Connecting error publishing events (retrying): Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: getsockopt: connection refused
elasticsearch_1     | [2017-06-01T16:57:02,772][INFO ][o.e.n.Node               ] [] initializing ...
configure_kibana_1  | Waiting for Kibana...
elasticsearch_1     | [2017-06-01T16:57:03,024][INFO ][o.e.e.NodeEnvironment    ] [omiF3yP] using [1] data paths, mounts [[/ (overlay)]], net usable_space [48.7gb], net total_space [58.8gb], spins? [possibly], types [overlay]
elasticsearch_1     | [2017-06-01T16:57:03,025][INFO ][o.e.e.NodeEnvironment    ] [omiF3yP] heap size [1.9gb], compressed ordinary object pointers [true]
elasticsearch_1     | [2017-06-01T16:57:03,027][INFO ][o.e.n.Node               ] node name [omiF3yP] derived from node ID [omiF3yPaQ2ee-4CPmXL8ew]; set [node.name] to override
elasticsearch_1     | [2017-06-01T16:57:03,028][INFO ][o.e.n.Node               ] version[5.4.1], pid[1], build[2cfe0df/2017-05-29T16:05:51.443Z], OS[Linux/4.9.30-moby/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/1.8.0_131/25.131-b12]
elasticsearch_1     | [2017-06-01T16:57:03,028][INFO ][o.e.n.Node               ] JVM arguments [-Xms2g, -Xmx2g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+DisableExplicitGC, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutOfMemoryError, -Des.cgroups.hierarchy.override=/, -Des.path.home=/usr/share/elasticsearch]
configure_kibana_1  | Waiting for Kibana...
configure_kibana_1  | Waiting for Kibana...
configure_kibana_1  | Waiting for Kibana...
metricbeat_1        | 2017/06/01 16:57:07.195144 single.go:140: ERR Connecting error publishing events (retrying): Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: getsockopt: connection refused
heartbeat_1         | 2017/06/01 16:57:07.866834 single.go:140: ERR Connecting error publishing events (retrying): Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: getsockopt: connection refused
packetbeat_1        | 2017/06/01 16:57:08.001059 single.go:140: ERR Connecting error publishing events (retrying): Get http://localhost:9200: EOF
packetbeat_1        | 2017/06/01 16:57:10.440824 single.go:140: ERR Connecting error publishing events (retrying): Get http://localhost:9200: EOF
heartbeat_1         | 2017/06/01 16:57:10.620979 single.go:140: ERR Connecting error publishing events (retrying): Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: getsockopt: connection refused
packetbeat_1        | 2017/06/01 16:57:18.401728 single.go:140: ERR Connecting error publishing events (retrying): Get http://localhost:9200: EOF
metricbeat_1        | 2017/06/01 16:57:19.386005 single.go:140: ERR Connecting error publishing events (retrying): Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: getsockopt: connection refused
heartbeat_1         | 2017/06/01 16:57:21.102012 scheduler.go:294: INFO Scheduled job 'http@http://kibana:5601' already active.
heartbeat_1         | 2017/06/01 16:57:21.848938 scheduler.go:294: INFO Scheduled job 'http@http://elasticsearch:9200' already active.
heartbeat_1         | 2017/06/01 16:57:22.355407 scheduler.go:294: INFO Scheduled job 'icmp-host-ip@elasticsearch' already active.
heartbeat_1         | 2017/06/01 16:57:22.738618 single.go:140: ERR Connecting error publishing events (retrying): Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: getsockopt: connection refused
heartbeat_1         | 2017/06/01 16:57:22.864821 scheduler.go:294: INFO Scheduled job 'icmp-host-ip@kibana' already active.
heartbeat_1         | 2017/06/01 16:57:25.813805 scheduler.go:294: INFO Scheduled job 'http@http://kibana:5601' already active.
packetbeat_1        | 2017/06/01 16:57:26.358671 single.go:140: ERR Connecting error publishing events (retrying): Get http://localhost:9200: EOF
heartbeat_1         | 2017/06/01 16:57:26.172862 scheduler.go:294: INFO Scheduled job 'http@http://elasticsearch:9200' already active.
heartbeat_1         | 2017/06/01 16:57:26.522047 scheduler.go:294: INFO Scheduled job 'icmp-host-ip@elasticsearch' already active.
heartbeat_1         | 2017/06/01 16:57:26.948109 scheduler.go:294: INFO Scheduled job 'icmp-host-ip@kibana' already active.

This is happening a bunch:
Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: getsockopt: connection refused

Hello,
The most common cause of failures like this is not assigning enough memory to the Docker virtual machine. The default is only 2 gig, which is simply not enough to run Elasticsearch, Kibana, Logstash and all the Beats!
On Windows, I give my VM 6 gig:

Also, thanks for reminding me to test on Windows! I didn't realise that Compose was behind on that platform. I set the file version to "3", not "3.2" to deal with that.
I also found a bug where Git on Windows may introduce carriage returns into the shell script that configures Kibana, which completely freaks out Bash. That's now fixed too.

OMG, thank you, my shell was all kinds of wonky and I couldn't figure out why for the life of me, lol. I just increased my memory and cpus on my moby box. Testing now.

Wootness! I have an ELK stack!  Thanks for your help.

I can feel the wootness. :)

OMG. I had to resort to using my cloud instance of Elastic because at that time I couldn't find the source of this issue. I feel like there should be some disclaimer or warning on Elastic's image page because for most images that I've used, the memory is sufficient.

You mean like https://github.com/elastic/stack-docker#prerequisites ;-)?

@xeraa sorry I didn't specify. I didn't use this particular image, but the standalone official elastic image
but google led me to the issue page on this repo :)
On the official image's page it does not mention the higher than usual memory requirements.

That image is not from us and is also deprecated. https://www.docker.elastic.co is the right place to get our images. And if you are just running Elasticsearch you shouldn't need to change any memory settings; 1GB for the container and 0.5GB for the heap should be enough to get started. Hope that helps :)

My bad! I linked to the wrong one, but in my project I do pull from elastic's registry.
For my project, I do have other containers running simultaneously as well, I guess that was the reason why it would die on me at times (it was erratic).


DFM2PM Converter is in the wrong package

The DFM2PM converter (which is a very cryptic name), is not located in the conversion package.
This is weird, as it "converts" a given input into an output.

Hi,
I also felt a bit confusing when creating the package for it. Although the node looks like just converting one input to another. But in background, the discovery process is conducted. That's why I didn't put it in the conversion category.
I think, I will change the name  "DFM2PM Converter" to "DFM2PN Miner".
Regards
Kefang


[ML] fix(next-pylint): Resolve docstring-should-be-keyword, docstring-missing-param, docstring-missing-return, docstring-missing-rtype, docstring-missing-type

Description
This pull request is part of a effort to re-enable pylint in CI for the azure-ai-ml package, after a  bump to the versions of pylint and azure-pylint-guidelines-checker.
This pull request:

Resolves docstring-should-be-keyword, docstring-missing-param, docstring-missing-return, docstring-missing-rtype, docstring-missing-type from azure-pylint-guidelines-checker

Number of messages addressed

message id
occurrences

docstring-missing-rtype
503

docstring-missing-return
358

docstring-missing-param
310

docstring-missing-type
62

docstring-should-be-keyword
22

A small subset were silenced by applying pylint: disable

Improves/Corrects Type Hints relevant to the fixes in the first point
Makes some small refactors that remove unused code paths in internal code (see commits prefixed with chore: or refactor:)

Validated with:
pylint==2.15.8
azure-pylint-guidelines-checker=0.0.8
pylint --rcfile=../../../eng/pylintc --disable=all --enable=docstring-should-be-keyword,docstring-missing-param,docstring-missing-return,docstring-missing-type azure/
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml


[AST/Sema]  Introduce a new type that has associated location in source

This type is intended to be used to wrap compiler synthesized nodes
(i.e. variables) to make it easier for diagnostic to diagnose precise
failure locations.
Consider the situation like:
protocol P {}

extension Array: P where Element: P {}

func test<T: P>() -> T {
  $_a = ...
  $_b = ...
  return [$_a, $_b]
}

This is a common pattern with result builders.
In this case if one of the elements don't conform to P the best
user experience would be to attach diagnostic to the element otherwise
the developers would have to figure out where in result expression
the error occurred before attempting to fix it.
Resolves: rdar://139842210

@swift-ci please test

@swift-ci please build toolchain macOS

@swift-ci please smoke test


Rework getWalletCollateral to support KeyWallet

As part of #437, balanceTx handles adding wallet collateral in an ad-hoc fashion for each wallet. We could investigate modifying QueryM.getWalletCollateral to handle those cases by adding the parameters needed by KeyWallet's selectCollateral to it. Alternatively, we make getWalletCollateral clear that it's for CIP30 wallets.
Actually, I noticed in CIP30 that it specifies the getCollateral function should take an amount parameter, which would be useful for selectCollateral in KeyWallet too. However, it's hard to tell how one can calculate the required collateral before balancing

I have two ideas:

We may use a separate type here, something like CollateralizedKeyWallet, with a smart constructor consisting of sending a collateral Tx. But the problem is that the wallet must be provided before Contract is interpreted, but sending a Tx is a Contract action. FAIL
We can delegate creation of KeyWallets to PlutipM monad interpreter. It can just request one extra UTXO from plutip-server on initialization and provide a pre-funded KeyWallet with collateral already set.

Closed by #860


HDFS-15982. HTTP API to consider default value of skiptrash true (ADDENDUM)

2976

 Quality gate: Failed
34 Issues

 34 Code issues

Details

 Quality gate: Failed
34 Issues

 34 Code issues

Details


updating to use the correct context

PR Description
Use the correct context in circleci as the credentials have been changed

 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.


 These should be fixed.

Fixed maven warnings.


Test new markdown renderers in notebooks

Refs #116393

[x] Mac @jrieken
[ ] Linux @roblourens
[ ] Windows @RMacfarlane

Complexity: 5
Create Issue

Background
With #116393, we've made the markdown renderer in notebooks extensible so that we can add support for math and other markdown syntax. To enable this, we had to completely change how markdown is rendered in notebooks. The main change is that markdown cells are now rendered inside of the back layer webview instead of inside the main workbench dom
Testing
This is an exploratory test plan item to catch potential regressions caused by the changes.
Start by setting "notebook.experimental.useMarkdownRenderer": true to force the new markdown renderer to be used by default for all notebooks. You can confirm the new render is being used by entering :smile: in a markdown cell. With the new renderer, this should be rendered as 😄
Using both the GitHub issues and jupyter notebooks extensions, explore some of the following scenarios to see if there is any unexpected behavior or regression:

Basic editing. Make sure you can edit markdown cells

Keyboard navigation and keyboard shortcuts. Confirm you can still use

Cell drag and drop

Make sure the state is correctly restored after reloading the window and reopening the notebook

Accessibility. When screen reader mode is enabled, make sure the new renderer is NOT used

fyi and if that matters: I did all my testing with "webview.experimental.useIframes": true since my understand is that that's where we are heading at

Accessibility - do you mean editor.accessibilitySupport? The new renderer is still used when I set that to "on", although I don't actually have a screen reader installed on this linux machine.

@roblourens Yes I believe so. Make sure to restart after enabling it

Yeah, vscode prompted me to restart

Do we set this by typing it in settings.json?


Different profile for each feature in GeoJSON file

Hello, and congratulations for your good work with this plugin.
I wonder if there is any way to get a different profile for each line from a GeoJSON file. I currently have two different profiles, but they appear when the map is loaded instead of when a feature is clicked. Is there a better way to achieve this? Here's a JSFiddle of my work: http://jsfiddle.net/pufanalexandru/eaok0Lnz/4/
Thanks!

Thanks!
There is currently no better way to achieve multiple profiles than to add a new control for each dataset.

here is what I came up with: http://lucamoiana.github.io/maggiore/
Now I'd like to style profiles with different css, how do I do? If I set different themes they are used right just the first time, then it uses the same.

Looks nice!
You mean two different themes at the same time? That´s not possible with the ways the theme selectors work. The theme-identifier is appended to the body dom node as the profile is initialized. So the first profile to be launched should have the correct theming. The second one then overrides the first one. This means that the CSS selector wins which was evaluated last, respectively standing last in the CSS file.
To make this work the code needs to be changed to append the theme selector only to the according control dom node.


Fixed Travis CI image and link.

Old: https://travis-ci.org/opscode/vagrant-omnibus (404 Not Found)
New: https://travis-ci.org/chef/vagrant-omnibus (works)

Thanks


Can't connect with String().c_str()

I have a program that connect to mosquitto with auth. If I put the credential as literals in code, the program work correctly, but if I put the credentials inside a String that is readed from a file and try to convert to c_str() the connect fail with state -2
--- this work ---
String host="mqtt.example.dev";
String port="2122";
mqttclient.setServer( host.c_str() , port.toInt());
if (!mqttclient.connect("id", "user","password)) {
  Serial.print("failed with state ");
  Serial.println(mqttclient.state());
}

-- this don't work, never get connection ---
String host="mqtt.example.dev";
String port="2122";
String user="anyuser";
String pass="anormalpassword";

mqttclient.setServer( host.c_str() , port.toInt());
if (!mqttclient.connect("id", user.c_str(),pass.c_str())) {
  Serial.print("failed with state ");
  Serial.println(mqttclient.state());
}

Hi I'm facing the same problem with mqtt broker ip, how did you solve it?

Hello, I am facing the same problem did any one of you got out of it successfully. Kindly help me out also?
@davrodfer @GJGits
Thankyou

Same issue

Same issue, thanks for let me know c_str() problem!!

I ran into this same issue and was banging my head against the desk as to why it doesn't work.
You are going to want to do something like this, and it should work:
const char* brokerCString = strdup(broker.c_str());
Hope this helps


Can't install in Centos 7

Hello,
I got issue when install uWebsocket in Centos 7.
I tried install lasted version of uWebsocket and old version, all got same issue.
Issue: https://i.imgur.com/SlQ3tc3.png
Centos 7 use default glibc 2.17.
I tried upgrade glibc to 2.18 and it fail, my OS got issue too.
Have any idea run uWebsocket without upgrade glibc? It too risk.

Centos 8 works. Other than this, no, you can't cover every single (outdated) dist by default. This is not a real problem since we have Docker where any dist can be selected easily


Nuxt in production

HI
I am using nuxt for first time and probably first front end framework for me.
How can I deploy it in production. LIke when we create VUE app we have a index.html as entry point but in nuxt directory there is no such file.
So do you guys go with this ?
Thanks :)

It depends, do you want to run a node app or deploy a static generate website?

You can generate a static website with nuxt generate
You can generate a single page app with nuxt --spa
You can generate and start a node app with npm run build && npm start further info here https://nuxtjs.org/faq/heroku-deployment

☝ And for deployment, with the generate option, for example, you want to deploy the entirety of the dist dir that is generated. That is your whole app.
An easy way to start messing around and learning about deployments is to spin up a new repository on Github and use one of the nuxt template starters. Then open up a free https://www.netlify.com/ account, and create a site for that repo. Set your build directory to "dist", and your build command to whatever you set up for generations (like npm run generate). Then netlify will deploy a SSR version of the nuxt starter template.


Build: exclude certain modules from publishing

WHAT
Some modules should be excluded from publishing to MavenCentral. This includes all test modules.
The modules we use to generate Docker images (control plane, data plane) produce an ...-all.jar file ("fat/uber jar"), which we should also exclude.
WHY
They are not intended for public consumption.

@paullatzelsperger i think this is still something we should do or?


About my training

Hello, I would like to ask about my training progress on Task1. I have trained for several epochs, but the class_error has remained at 100.00. Is this normal?

Hi @Yzhongming,
No, it isn't - I attached a picture of the class error over a few runs with different hyperparameters. It drops pretty quickly in the beginning.

Best,
Orr


v 2.00 error for creating staging tables using md5 func on Databricks

/* {"app": "dbt", "dbt_version": "1.2.0", "dbt_databricks_version": "1.2.2", "databricks_sql_connector_version": "2.0.5", "profile_name": "profile", "target_name": "target", "node_id": "model.dbt_artifacts.stg_dbt__exposures"} */
create or replace view branch.stg_dbt__exposures

  as
    with base as (

    select *
    from branchsrc_dbt_artifacts.exposures

),

enhanced as (

    select
        md5(cast(coalesce(cast(command_invocation_id as string), ''), '-', coalesce(cast(node_id as string), '') as string)) as exposure_execution_id,
        command_invocation_id,
        node_id,
        run_started_at,
        name,
        type,
        owner,
        maturity,
        path,
        description,
        url,
        package_name,
        depends_on_nodes
    from base

)

select * from enhanced

Returns:
PARSE_SYNTAX_ERROR] Syntax error at or near 'as': extra input 'as'(line 16, pos 113)

== SQL ==
/* {"app": "dbt", "dbt_version": "1.2.0", "dbt_databricks_version": "1.2.2", "databricks_sql_connector_version": "2.0.5", "profile_name": "profile", "target_name": "dev", "node_id": "model.dbt_artifacts.stg_dbt__exposures"} */
create or replace view branch_dbt_artifacts.stg_dbt__exposures

as
with base as (

select *
from branch_src_dbt_artifacts.exposures

),

enhanced as (

select
md5(cast(coalesce(cast(command_invocation_id as string), ''), '-', coalesce(cast(node_id as string), '') as string)) as exposure_execution_id,
-----------------------------------------------------------------------------------------------------------------^^^
command_invocation_id,
node_id,
run_started_at,
name,
type,
owner,
maturity,
path,
description,
url,
package_name,
depends_on_nodes
from base

)

select * from enhanced

Have raised with dbt_utils here: https://github.com/dbt-labs/dbt-utils/issues/682

Raised with dbt-core here: https://github.com/dbt-labs/dbt-core/issues/5888

Resolved


Create style variables and replace colors on it

Checklist

[x] I have read the CONTRIBUTING guide
[x] Good naming, keep simple
[x] Tested desktop/mobile
[x] Tested bright/dark
[x] Tested en/ru
[x] Affects money; I checked the functionality once again
[x] I checked the PR once again

Video / screenshot proof
before

after

before

after

before

after

before

after

before

after

before

after

before

after

before

after

чето тени прямо очень много и они все жирные ппц, надо не так жирно особенно последний скрин смотри


make gossipInterval configurable

Right now gossipInterval is hard-coded to be 30 sec in mesh library. So every 30 sec there is topology update that is gossiped. Processing topology update received through gossip can get expensive when the number of nodes participating in the gossip increases.
Is there a reason to gossip periodically? Does sending the topology updated when there is topology change detected should be sufficient? If periodic gossip is required then is it desirable to increase the gossip interval to higher value.

cpu.pdf
Please find the attached CPU profile. 1/3 of time was send in processing topology gossip updates received from other peers. There is a topology update sent instantly when there is connections add/delete are detected by local peer. So its desirable to keep the interval less aggressive at least for topology gossip channel.


[DOC] abi.json details

What is the meaning of "ndk" entry in abi.json? Should it be 20, or 20.1.5948944 ?

It's the major version. Will follow up with a doc fix.

The underlying idea being that within a major version, binaries are compatible?

Yep. If they aren't, that's a pretty big bug IMO.

There is no any details about abi.json in https://google.github.io/prefab/, why not write the details?
by the way, I encountered following logs when running ./gradew aR:
> Task :app:configureCMakeRelWithDebInfo[x86_64]
C/C++: prefabcom.google.prefab.api.NoMatchingLibraryException: No compatible library found for //chinese-calendar/libchinese-calendar.so. Rejected the following libraries:
C/C++: prefabandroid.arm64-v8a: User is targeting x86_64 but library is for arm64-v8a
C/C++: prefabandroid.armeabi-v7a: User is targeting x86_64 but library is for armeabi-v7a
C/C++: prefabandroid.x86: User is targeting x86_64 but library is for x86
C/C++: prefabandroid.x86_64: User is using a static STL but library requires a shared STL

my abi.json as following:
{"api": 21,"abi": "x86_64","ndk": 21,"stl": "c++_shared","static":true}

I guess above logs are caused by stl, stl can be omitted. am I correct?

I changed c++_shared to none, above messages gone.

There is no any details about abi.json in https://google.github.io/prefab/, why not write the details?

They're here: https://google.github.io/prefab/platform-support.html#android
I'm forking the rest to a new bug because it's off-topic.

@DanAlbert Thank you!