Add adaptive forward differencing option for bezier tessellation.

Caching paths is great, but sometimes your paths are changing often. In that case, you need the fastest tessellation algorithm possible.
In my app, Adaptive Forward Differencing (AFD) provides a 4x speedup over the existing De Casteljau subdivision algorithm. YMMV. Also, note that the existing algorithm does not handle certain (arguably degenerate) cases correctly, like collinear control points with the endpoints in the middle.
I've added a function to select between tessellation algorithms (nvgBezierTessellation), defaulted to the old algorithm, so this will not change the behavior of your existing code. Currently, AFD produces about twice the points (the flatness test could be improved), but GPUs are fast.
Add nvg__tesselateBezierAFD which implements the tessellation. Add nvgBezierTessellation to select tessellation algorithm.

I tested this alternative tessellation patch by cherry-picking it on top of (https://github.com/QUItCoding/nanovg) fork and using that in QNanoPainter (https://github.com/QUItCoding/qnanopainter). Based on my usage & testing, AFD was slower on both Macbook Pro & Nexus 6. Here's screenshots on macbook:

So with this torture test, fps drops from 19 to 11 while vertices count increases about 3x. Of course this is just one usage and like @wtholliday said, YMMV.

I also did a pressure test for my app on iPhone 6s+. It seems there is no difference in my case.
Original:

AFD:

@QUItCoding The AFD would benefit from a better flatness condition. How much time is your test spending on tessellation? (inside nvg__tesselateBezier or nvg__tesselateBezierAFD)
@olliwang How much time is your test spending on tessellation?

I tried this with a SVG drawing of the GhostscriptTiger, were tesselation was and still is a massive bottleneck and the speedup was significant.
I actually also think the quality is better. But wouldn't vouch for that :)

Caching paths is great, but sometimes your paths are changing often. In that case, you need the fastest tessellation algorithm possible.
In my app, Adaptive Forward Differencing (AFD) provides a 4x speedup over the existing De Casteljau subdivision algorithm. YMMV. Also, note that the existing algorithm does not handle certain (arguably degenerate) cases correctly, like collinear control points with the endpoints in the middle.
I've added a function to select between tessellation algorithms (nvgBezierTessellation), defaulted to the old algorithm, so this will not change the behavior of your existing code. Currently, AFD produces about twice the points (the flatness test could be improved), but GPUs are fast.
Add nvg__tesselateBezierAFD which implements the tessellation. Add nvgBezierTessellation to select tessellation algorithm.

Hi! I tried to read the paper you mentioned, but I cant exactly understand the algorithm. Besides, I analyze the time complexity of nvg__tesselateBezier and nvg__tesselateBezierAFD and I found if both algorithmThe time complexity of algorithm A is at most twice that of Bs generate the same number of vertices, the time complexity of nvg__tesselateBezier is at most twice that of nvg__tesselateBezierAFD. For nvg__tesselateBezier, its time compplexity is O(2^n) and generate 2^(n-1) vertices, so if nvg__tesselateBezierAFD also generates 2^(n-1) vertices, it will at least cost O(2^(n-1)).
I dont konw why you can got 4x sppedup by nvg__tesselateBezierAFD. And is there any other information about the algorithm besides the paper?

Hi! I tried to read the paper you mentioned, but I cant exactly understand the algorithm. Besides, I analyze the time complexity of nvg__tesselateBezier and nvg__tesselateBezierAFD and I found if both algorithmThe time complexity of algorithm A is at most twice that of Bs generate the same number of vertices, the time complexity of nvg__tesselateBezier is at most twice that of nvg__tesselateBezierAFD. For nvg__tesselateBezier, its time compplexity is O(2^n) and generate 2^(n-1) vertices, so if nvg__tesselateBezierAFD also generates 2^(n-1) vertices, it will at least cost O(2^(n-1)).
I dont konw why you can got 4x sppedup by nvg__tesselateBezierAFD. And is there any other information about the algorithm besides the paper?

Both algorithms are linear in number of output vertices. The difference comes from avoiding recursion, and is a constant factor, not an asymptotic difference. But I never got the flatness test to be good enough to minimize the number of output vertices.
I've since moved on to using implicit methods to render things, avoiding any tessellation. See http://GitHub.com/Audulus/vger

so, is this repo dead?


Adds support for handling responses from API+JSON APIs

For APIs that conform to the specification of jsonapi.org, responses are not being parsed.
"JSON API requires use of the JSON API media type (application/vnd.api+json) for exchanging data."
http://jsonapi.org/format/
This PR connects responses with the media type application/vdn.api+json to the JSON Parser.

Pull Request Test Coverage Report for Build 704

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

Totals

Change from base Build 701:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


Incorrect entity insertion

Given this file...
%[ask_phone_number]
    {what is/tell/display} your @[number_type] number

@[number_type]
    direct
    tel
    telephone

I get JSON with one of the entities marked at the wrong place. Here's one example...
      {
        "entities": [
          {
            "end": 3,
            "entity": "number_type",
            "start": 0,
            "value": "tel"
          }
        ],
        "intent": "ask_phone_number",
        "text": "tell your tel num"
      },

To ease diagnosing the issue, I've passed the generated JSON through rasa_nlu.convert to get markdown (which makes it more obvious)...
what is your [direct](number_type) number
what is your [tel](number_type) number
what is your [telephone](number_type) number
tell your [direct](number_type) number
[tel](number_type)l your tel number              <<< Erroneous output
tell your [telephone](number_type) number
display your [direct](number_type) number
display your [tel](number_type) number
display your [telephone](number_type) number

This seems to happen when one of the example entity strings under a slot definition occurs as a sub-string earlier in the generated text than the position that actually needs to be targeted.
Guessing that a \b might need adding to a regex somewhere to ensure any entity value substitutions happen on word boundaries.
Many thanks for your consideration.

That might happen indeed, I didn't think of that possibility when programming this. I'll fix that as soon as I can (I don't have much time at the moment sorry).
Thanks a lot for submitting a bug report :)

I just fixed this. It should work now in all cases (unless you use the string <<CHATETTE_ENTITY>> within your generated examples).
The fix is available on the branch dev and will be available on PyPI on the next release.
Thanks again for the report


Angular WordPress HTML5 mode true but url looking very bad and not work properly.

Hey there,
I am suffering with # in url. I used HTML5 mode true statement but whole site is not working properly. After removing that statement this site is running well.
By Using of HTML5 mode true statement, when i click on any menu the url is showing something like this.
http://orangemantra.co.in/dummy#%2Fportfolio
and showing an error in angularjs, that is:
"Error: $rootScope is not defined".
how we can overcome this issues.

This is better asked on stackoverflow since it looks like an implementation bug and not a bug in ui-router itself.
you are also probably trying to use $rootScope somewhere and you didn't include it in the dependency list


Becauses of cross join,I can't query anything.

Observed vs. expected behavior
select
    count(collection0_.id) as col_0_0_
from
    collection collection0_ cross
join
    project project1_ cross
join
    supply_demand supplydema2_
where
    collection0_.project_id=project1_.id
    and collection0_.supply_demand_id=supplydema2_.id

I used queryDsl to generate this SQL sentence,becauses of cross join,I can't query anything.
I want to know how to change JoinType?
can i use reflection to change something?(I changed something but it didn't work)
DefaultQueryMetadata defaultQueryMetadata = (DefaultQueryMetadata)jpaQuery.getMetadata()
Field fieldJoinType = defaultQueryMetadata.getClass().getDeclaredField("joinType")
fieldJoinType.setAccessible(true)
fieldJoinType.set(defaultQueryMetadata, JoinType.LEFTJOIN)

Environment
Querydsl version: 4.4.0
Database: MySQL 5.7
JDK: 8

You should use Querydsl 5

You should use Querydsl 5

query result always be 'join', but I expect that 'let join'


feat: support analyzeUpdate

Adds support for analyzeUpdate for DML statements, similarly to
analyzeQuery for DQL statements. Executing a DML statement in PLAN mode
only returns the query plan, but does not actually execute the
statement. Executing a DML statement in PROFILE mode executes the
statement and returns the query plan and execution statistics.
Fixes #1866

@rajatbhatta @ansh0l Friendly ping. Would you mind giving this a review? This feature is needed for the DescribeStatement message in PGAdapter.


how do i remove the previously created (mistakenly) campaign ?

Hello @jpca999
Thank you for contacting us.
Please check this link.
Delete a campaign


Detected and fixed an issue related to -0

I detected and fixed an issue with -0 by using property based tests.

first commit adds the fix and test for the value -0
second commit adds the test that discovered the issue.

I love the idea of fast-check, I'm so glad someone other than me got around to this finally! I'll look more into it and see how else I can better utilize it to test, especially around some of the more complex code possible (e.g. regexps and properties on objects).

Concerning the generation of regex, I wrote a snippet doing that few days ago: https://runkit.com/dubzzz/valid-regex-generator
It is still incomplete but it is a good start ^^
I will maybe include such generator in fast-check ;)


(WIP) Find a solution to the currentTarget/ownerTarget situtation

This is a work in progress. DO NOT MERGE.
Looking for a solution to properly change the currentTarget across browsers.

@TylorS can you try "refreshing" this PR? maybe resubmit

Still no luck.


eliminate backtracking - use choiceDispatchKey or occursCountKind 'expression'

This schema is old and pre-dates the introduction of DFDL features like choiceDispatchKey.
Presence indicators should be done via choiceDIspatchKey or occursCountKind 'expresion' to eliminate the overhead of backtracking.
It also makes this a better example of how to best handle presence flags in DFDL.

Presence bits no longer backtrack. Repeat bits do, but there is no getting around that.
Fixed in 3af6cbb7ea6e3dd48438a1ef5367b514c2688d1d


HTML

HTML
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find and read information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see hour boxes titled HTML, CSS, Git, and JavaScript with associated notes listed.

CSS
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I see a dark blue header and footer, and four


Use random tokens if undefined

My config looks like:
  route /auth* {
    auth_portal {
      local_backend /etc/caddy/auth/local/users.json
      jwt {
        token_name access_token
        token_secret 0e2fdcf8-6868-41a7-884b-7308795fc286
        token_issuer e1008f2d-ccfa-4e62-bbe6-c202ec2988cc
        token_lifetime 3600
      }
    }
  }

  @protected not path /favicon.ico /public* /tautulli/api*
  route @protected {
    jwt {
      primary yes
      trusted_tokens {
        static_secret {
          token_name access_token
          token_secret 0e2fdcf8-6868-41a7-884b-7308795fc286
          token_issuer e1008f2d-ccfa-4e62-bbe6-c202ec2988cc
        }
      }
    }
  }

What I'm wondering about is if there might be a way to eliminate the token settings from the config.  If they aren't defined then the plugins would use random values and somehow coordinate that between the jwt and portal plugins.  I believe the Caddy 1 plugins jwt and login did something like this, because I did not have to define tokens like this.
Do you think it's possible? Am I way off?

@xombiemp , let’s start with that you can safely remove token_issuer and token_name from the config. Next, by default token_lifetime is 15 minutes. You can remove this directive too if you are ok with this limit.
Token secret is the only thing that need to be present. Now, I suggest you don’t use static password, rather you could add
token_rsa_file Hz789bc303f0db /etc/gatekeeper/auth/jwt/sign_key.pem
See https://github.com/greenpau/caddy-auth-portal#jwt-tokens
If you don’t want specify any secrets and let the server auto-generate it, it is not an option an at the moment. Long story short ... portal and jwt are two separate plugins. Further each declaration/mention of a plugin in Caddyfile is a separate instance. Sharing data between the instances is something I was working to solve. There is no easy way to communicate between the instance. I would consider adding it as a feature.
Did I answer you question?

Also, I can probably create a few shortcuts related to “jwt”. Will add it tomorrow. Now, I going to 🛌 !

@greenpau I would definitely be interested in the plugins being able to communicate a generated secret as a feature request.
Thanks for the other tips given!
My config now looks like:
  route /auth* {
    auth_portal {
      local_backend /etc/caddy/auth/local/users.json
      jwt {
        token_rsa_file 1 /etc/caddy/auth/jwt/jwt_privatekey.pem
      }
    }
  }

  @protected not path /favicon.ico /public* /tautulli/api*
  route @protected {
    jwt {
      primary yes
      trusted_tokens {
        public_key {
          token_rsa_file 1 /etc/caddy/auth/jwt/jwt_publickey.pem
        }
      }
    }
  }

I am also very interested in any shortcuts you can create tomorrow. 😄

After my future release, the following snippet in jwt Caddyfile:
trusted_public_key 1 /etc/caddy/auth/jwt/jwt_publickey.pem

replaces the following:
      trusted_tokens {
        public_key {
          token_rsa_file 1 /etc/caddy/auth/jwt/jwt_publickey.pem
        }
      }

After my future release, the following snippet in portal Caddyfile:
    auth_portal {
      jwt_token_file 1 /etc/caddy/auth/jwt/jwt_privatekey.pem
      ...
    }

Replaces:
    auth_portal {
      jwt {
        token_rsa_file 1 /etc/caddy/auth/jwt/jwt_privatekey.pem
      }
      ...
    }

@xombiemp , please review https://github.com/greenpau/caddy-auth-portal#caddyfile-shortcuts. These changes are in https://github.com/greenpau/caddy-auth-portal/releases/tag/v1.2.11.
Please test.

@greenpau This is great! I just tested this config and it is working as expected:
  route /auth* {
    auth_portal {
      local_backend /etc/caddy/auth/local/users.json
      jwt_token_file 1 /etc/caddy/auth/jwt/jwt_privatekey.pem
    }
  }

  @protected not path /favicon.ico /public* /tautulli/api*
  route @protected {
    jwt {
      primary yes
      trusted_public_key 1 /etc/caddy/auth/jwt/jwt_publickey.pem
    }
  }

This looks about as compact as possible without the plugins being able to share a random secret. Thanks so much!

This is as good as it gets at the moment! :-)


Add "queen-attack" exercise

Add queen-attack
Add exercise to config.json

@clementi Thanks so much. Would you mind squashing your commits?

@kytrinyx I've never done a squash before. Did I do it correctly?

It doesn't look like the squash worked. When you've done it right you should end up with  "Commits (1)" at the top:

I'm totally happy to do this on my end if it gets frustrating (just let me know!)—meanwhile, here's a quick guide: http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request

@kytrinyx There we go. Commits squashed. Thanks for the help. :smiley:

Thank you so much for adding all of these exercises!
In the future, when you squash the commits, would you mind editing the commit message to be:
Implement EXERCISE_SLUG exercise

(I went ahead and made the change here—totally no big deal!)
Merged in 2649600ed2b7838e63753565101935d2b51a2fe3


Dockerfile

This PR builds on the work from #150 to create a Dockerfile for SmartRedis.  A couple of changes have been made from the original PR:

The include directories are copied to /usr/local/include along with the lib directory to /usr/local/lib
In the original PR, a sequential build was used, with the last image being a clean derivative of ubuntu:21.04.  In that derivative image, only the smartredis lib was copied over.  This leaves behind any pip install of the smartredis client as well as header files.  For now, the sequential build has been removed so that the installed smartredis python package and compiled client library are both accessible.

The final stage of the Dockerfile may need to be refiend to minimize image size and provide maximum extensibility for derivative images.

Codecov Report

Merging #180 (9ec4188) into develop (42c42fb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #180   +/-   ##
========================================
  Coverage    82.23%   82.23%
========================================
  Files           47       47
  Lines         2617     2617
========================================
  Hits          2152     2152
  Misses         465      465

For added context on container usage, the SmartRedis Dockerfile can be used to build a derivative containers such as:
FROM smartredis

COPY ./CMakeLists.txt /usr/local/src/DockerTest/
COPY ./test_docker.cpp /usr/local/src/DockerTest/
WORKDIR /usr/local/src/DockerTest
RUN mkdir build && cd build && cmake .. && make && cd ../

where test_docker.cpp is any C++ application using the SmartRedis client and CMakeLists.txt is the build file for the application:
#include "client.h"
#include <vector>
#include <string>

int main(int argc, char* argv[]) {

  SmartRedis::Client c(false);
  return 0;
}

project(DockerTester)

cmake_minimum_required(VERSION 3.10)

set(CMAKE_VERBOSE_MAKEFILE ON)
set(CMAKE_BUILD_TYPE DEBUG)
set(CMAKE_CXX_STANDARD 17)

find_library(SR_LIB smartredis)

include_directories(SYSTEM
    /usr/local/include/smartredis
)

# Build executables

add_executable(docker_test
	test_docker.cpp
)
target_link_libraries(docker_test ${SR_LIB} pthread)


Add Binder support for Java Notebooks

It will be of great utility if the students or other users of this project can directly access the code and notebooks without cloning the repo and setting up Jupyter locally on their machines.
This can be achieved by Binder. This is also currently being used in Dr. Norvig's Pytudes.

Yes, it's a great idea. I will look into the details and technicalities and try to add it as soon as possible.


Improve build binaries pipeline

Changes made:

build macOS arm and x86
rename architecture from amd64 to x86_64, which is much easier to distinct from arm
remove unnecessary step for self-hosted which is not being used anymore
create ARTIFACT_NAME env var, so it's much easier to read the code
remove unnecessary id
add trigger on PR that change the build binaries files

Results:  https://github.com/NethermindEth/juno/actions/runs/10718771544?pr=2121


Different result on determining first day for specific week

I implement the following statement for getting the start date for a specific week number (the starting date should be a monday):
moment().year(year).day('Monday').week(weekNumber).toDate();
Sample:
moment().year(2019).day('Monday').week(1).toDate();
Now I found an unexpected behaviour, because the statement delivers different result. The result depend on the current system time.
It is reproducible with the following statements:
- CORRECT result:
moment("20200101", "YYYYMMDD").year(2020).day('Monday').week(1).toDate()
--> Mon Dec 30 2019
- WRONG result:
moment("20191230", "YYYYMMDD").year(2020).day('Monday').week(1).toDate()
--> Mon Dec 28 2020
Is it a bug or is the usage wrong?
Thanks!

Oh my issue!
I fixed it with the following statement:
moment(year + '0101', 'YYYYMMDD').day('Monday').week(weekNumber).toDate();
Sample:
moment(2020 + '0101', 'YYYYMMDD').day('Monday').week(weekNumber).toDate();


Remove zne_mitigration options check

Summary
Disabling the zne_mitigation=True check in the client to let the server decide if it's compatible with the resilience level.
Jessie's comment
Details and comments
Fixes #1654

Also removed the options check for pec_mitigation. I don't think this was documented anywhere but I will add a release note.


Frontend tools UI and QOL improvements

Context
neurobagel/planning#35 gave us the essential annotation tool functionality we need. But our UI is still a bit rough around the edges, and there are some minor UX bugs we'd like to tackle now, because that will make the tool a lot better for little effort. Similarly the query tool is feature complete for a while, but could be improved a lot with some minor UI additions.
Why

Part of neurobagel/planning#49
to make the Annotation tool an appealing first encounter with Neurobagel (despite being under active development)
so we can go and ask people to use and give us feedback on the annotation tool
to make the "federation" and "sample-level" aspects of our query more self evident
to transparently show our current limitations as beta tools

Outcomes

[ ] The annotation tool has no obvious "debug mode" UI elements
[ ] The visual annotation workflows have minimal context
[ ] There is a little badge showing that the tools are in beta and will change
[ ] The query tool UI visually highlights federation and sample information
[ ] All frontend tools have logos (including the dash)

What
Annotation tool related

[ ] https://github.com/neurobagel/annotation_tool/issues/610
[ ] https://github.com/neurobagel/annotation_tool/issues/611
[ ] https://github.com/neurobagel/annotation_tool/issues/612
[ ] https://github.com/neurobagel/annotation_tool/issues/613
[ ] https://github.com/neurobagel/annotation_tool/issues/614
[ ] https://github.com/neurobagel/annotation_tool/issues/616
[ ] https://github.com/neurobagel/annotation_tool/issues/615

Query related

[ ] neurobagel/query-tool#265
[ ] https://github.com/neurobagel/federation-api/issues/13
[ ] https://github.com/neurobagel/query-tool/issues/265

Universal

[ ] neurobagel/planning#62
[ ] neurobagel/planning#61

@neurobagel/dev take a look, I think these are the main low hanging UI/UX fruits we can tackle for the most payoff. Let me know what you think, if any should be added, or if some of them have additional dependencies I missed

Hey @surchs, thanks for putting this together.
I created + added several issues to the annotation tool and query tool sections, and created new ones to discuss if we want to implemented.

Closing as completed 🎉


📢 Kairos release v3.1.0

🗺 What's left for release

[x] #2117
[x] https://github.com/kairos-io/kairos/issues/2200
[x] https://github.com/kairos-io/kairos/issues/2565
[x] https://github.com/kairos-io/kairos/issues/2429
[x] https://github.com/kairos-io/kairos/issues/2138
[x] https://github.com/kairos-io/kairos/issues/2217
[x] https://github.com/kairos-io/kairos/issues/2430
[x] https://github.com/kairos-io/kairos/issues/2048
[x] https://github.com/kairos-io/kairos/issues/2547
[x] https://github.com/kairos-io/kairos/issues/2586
[x] https://github.com/kairos-io/kairos/issues/2608

:bug:

[x] https://github.com/kairos-io/kairos/issues/2526
[x] https://github.com/kairos-io/kairos/issues/2212

Next release: https://github.com/kairos-io/kairos/issues/2052
🔦 Highlights

This is the last release with Ubuntu 23.10 (marked for deprecation)

✅ Release Checklist

[ ] Stage 0 - Finishing Touches

[ ] Check if Kairos-docs were updated and consider tagging them with the same version as Kairos
[ ] Check if osbuilder is in the wanted version/latest
[ ] Check if any kairos/packages was bumped and they were merged and repo updated (https://github.com/kairos-io/packages)
[ ] Check latest repository update was merged, otherwise trigger its job (https://github.com/kairos-io/kairos/actions/workflows/bump_repos.yml)
[ ] Make sure CI tests are passing.
[x] Consider cutting an rc, alpha, ... based on changes on the CI

[ ] Stage 1 - Manual testing

How: Using the assets from master, make sure that test scenarios not covered by automatic tests are passing, and that docs are still aligned

[ ] Fedora flavor install, and manual upgrade works
[ ] Any flavor interactive install
[ ] Any flavor recovery reset
[ ] ARM images (openSUSE, alpine) boots and manual upgrade works
[ ] ARM images passive and recovery booting
[ ] ARM images reset works
[ ] ARM images /oem exists

[ ] Stage 3 - Release

[ ] Tag the release on master.
[ ] Create a branch vX.Y.Z on the docs (not tagging), so the new release can be built and displayed on the menu. Ideally open a PR so we can review and add/remove some commits if needed (in case we have documented WIP which is not available on the given release)

[ ] Stage 4 - Announcement

[ ] Blog post announcement

We have to discuss internally if master does not have many breaking changes yet - in that case we will move out some of the items of 3.1.0 to 3.2.0, and leave 3.1.0 to be mostly bug-fixing with small feats in (Ubuntu 24) and get rid of tech debt around 3.0.
jfyi @antongisli

100%. Let's keep 3.1 as stable as possible and minimize breaking changes.

rc1 one on its way: https://github.com/kairos-io/kairos/releases/tag/v3.1.0-rc1

This should be addressed before we cut the "stable" one: https://www.qualys.com/regresshion-cve-2024-6387/
Let's check when the distros have a patch.

This should be addressed before we cut the "stable" one: https://www.qualys.com/regresshion-cve-2024-6387/ Let's check when the distros have a patch.

not a shipstopper - we can do patch releases.


Change image load folder

Hello,
I purchase Jodit OEM License. I want to change the folder where images are saved and where they are loaded (I want to be local: localhost/project/images)  and fail.
The interface returns 'Error on load list` (please look in printscreen)
Can you help me?
Thank you

You can to write your own connector on php, but you can use a free connector official Jodit PHP https://github.com/xdan/jodit-connectors
http://xdsoft.net/jodit/doc/tutorial-filebrowser-options.html

I built a connectors for nodejs. If I open source will you link it?

@damusix Oh sure. Yii expansion also wrote a separate developer

@xdan Just uploaded the connector last night https://github.com/damusix/jodit-node-connector

we are also facing same problem,, please provide me updated folder on my email id<EMAIL_ADDRESS>

We are solved this problem,  but it's very difficult! Please add in config folder destination for uploaded files and generated url with and without Url of project (when i working with local site and local url)


alarm-clock-applet: Remove

Last upstream update is from 2015, in 2020 it got abandoned by the
upstream maintainer.
The nixpkgs got a pending -fno-common fix, i.e. the package is
officially on life support.
This is unlikely to be revamped for GNOME3/GTK3, so better say goodbye.
See #39976.
@rasendubi

Now also with correct GNOME2 deprecation issue number.

The nixpkgs got a pending -fno-common fix, i.e. the package is
officially on life support.

That is nothing we should count because it is a common issues with all kinds of packages.


Adding generated supplementary-style-guide guide rules

fixes #27
Adds generated rules for every RH supplementary style guide word usage + related link to sections https://redhat-documentation.github.io/supplementary-style-guide/
All rules follow this pattern:
extends: substitution
message: "Use '%s' instead of '%s'."
link: https://redhat-documentation.github.io/supplementary-style-guide/#hard-code
ignorecase: true
level: error
action:
  name: replace
source: Red Hat
swap:
    hardcode : hard code

Preliminary python generation code is here: https://github.com/aireilly/supplementary-style-guide/blob/master/vale_rules/gen-vale-rules.py

Merging these as-is because they are part of the experimental SupplementaryStyleGuide style. As volunteer testers, we will download and use these new rules. Then, we will file issues and enhancement requests here: https://github.com/rolfedh/studious-fortnight/issues


Move optional documentation

This fixes the optional documentation indentation by moving it up

Thanks!
--
Keith Smiley

On Dec 26, 2017, at 23:15, Yonas Kolb<EMAIL_ADDRESS>wrote:
Merged #209.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Please clarify preference 'raw' service descriptions vs. 'class based'

Thanks for providing this project, loving it ... and making my own platforms :-)
But here's where I'm struggling: by looking at existing implementations I noticed there are two styles for coding services/accessories:

The "raw" method where the services are assembled manually as data structures (e.g. just like in the Hue platform implementation)
The class based method where the Service/Characteristic classes are used to define the service (e.g. as in the MiLight accessory)

I understand both probably yield similar results, but is there a preferred way for implementing new platforms, are there any advantages/disadvantages to either (better future compatibly?). I'd love to get your opinion on this.

The API method is absolutely preferable. See the Wiki page on migration
Regards
Raoul

Even better, see the roadmap, migration does only point to that.

Thanks, that's clear: I'll close the issue


Error when Running: GLIBC_xx not found

When I ran this in the GUI it did not work, so I tried the terminal and this was the error code.
/tmp/.mount_PrusaS1n0nzr/usr/bin/prusa-slicer: /lib/aarch64-linux-gnu/libm.so.6: version 'GLIBC_2.38' not found (required by /tmp/.mount_PrusaS1n0nzr/usr/bin/prusa-slicer) /tmp/.mount_PrusaS1n0nzr/usr/bin/prusa-slicer: /lib/aarch64-linux-gnu/libstdc++.so.6: version 'GLIBCXX_3.4.32' not found (required by /tmp/.mount_PrusaS1n0nzr/usr/bin/prusa-slicer) /tmp/.mount_PrusaS1n0nzr/usr/bin/prusa-slicer: /lib/aarch64-linux-gnu/libc.so.6: version 'GLIBC_2.38' not found (required by /tmp/.mount_PrusaS1n0nzr/usr/bin/prusa-slicer)
I am running the standard Raspberry Pi OS (Bookworm) in 64 bit.

Hello,
Appreciate the report, it looks like the GLIBC version on the build platform is a bit too recent. I've updated all the AppImages in the 2.8.1 release with one that should work with Bookworm.
Please pull down the latest images, these should resolve the issue

Thank you for your prompt response. The GLIBC error has been fixed. But now when I run the most recent AppImage (PrusaSlicer-version_2.8.1-aarch64-latestOS.AppImage) it shows this error:
(prusa-slicer:66720): Gtk-WARNING **: 10:35:30.686: Could not load a pixbuf from /org/gtk/libgtk/icons/16x16/actions/dialog-question.png.
This may indicate that pixbuf loaders or the mime database could not be found.

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:39.876: gtk_window_resize: assertion 'width > 0' failed

(prusa-slicer:66720): GLib-GObject-WARNING **: 10:35:40.025: invalid cast from 'wxPizza' to 'GtkCellLayout'

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.026: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(prusa-slicer:66720): GLib-GObject-WARNING **: 10:35:40.031: invalid cast from 'wxPizza' to 'GtkCellLayout'

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.031: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(prusa-slicer:66720): GLib-GObject-WARNING **: 10:35:40.048: invalid cast from 'wxPizza' to 'GtkCellLayout'

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.048: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(prusa-slicer:66720): GLib-GObject-WARNING **: 10:35:40.053: invalid cast from 'wxPizza' to 'GtkCellLayout'

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.053: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(prusa-slicer:66720): GLib-GObject-WARNING **: 10:35:40.082: invalid cast from 'wxPizza' to 'GtkCellLayout'

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.082: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(prusa-slicer:66720): GLib-GObject-WARNING **: 10:35:40.087: invalid cast from 'wxPizza' to 'GtkCellLayout'

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.088: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.283: gtk_widget_set_size_request: assertion 'width >= -1' failed

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.283: gtk_widget_set_size_request: assertion 'width >= -1' failed

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.285: gtk_widget_set_size_request: assertion 'width >= -1' failed

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.306: gtk_widget_set_size_request: assertion 'width >= -1' failed

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.306: gtk_widget_set_size_request: assertion 'width >= -1' failed

(prusa-slicer:66720): Gtk-CRITICAL **: 10:35:40.307: gtk_widget_set_size_request: assertion 'width >= -1' failed
[2024-09-24 10:35:40.894267] [0x0000007fa902a040] [error]   UserAccount: Failed to read token - no datafile found.

(prusa-slicer:66720): Gtk-WARNING **: 10:35:41.105: Could not find the icon 'user-home-symbolic-ltr'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
	http://icon-theme.freedesktop.org/releases
**
Gtk:ERROR:../../../gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../../../gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Aborted

Thank you again for your support and for making this software available to the Raspberry Pi community.

Thanks for following up, and am glad to hear that the GLIBC issue was resolved!
For the new issue; this has popped up in the past and may be related to the default fallback theme not being found.
Please try the following:

sudo apt-get install hicolor-icon-theme
sudo gtk-update-icon-cache /usr/share/icons/hicolor
Check that XDG_DATA_DIRS is set as well: echo $XDG_DATA_DIRS

I am unable to reproduce the issue on a new installation of Raspberry Pi OS, but hopefully these will get the AppImage working or narrow down the issue a bit further

Thank you very much. That fixed the issue.


Uvloop broken in 3.11

Hello
I tested this code almost 2 weeks ago and was everything ok, now something is broken.
The following code block is resulting in an error:
Error in Scraper._process(): TypeError: 'Task' object is not callable
def test_t1(self):
        a = Scraper(session=init_session())
        b = a.users(['elonmusk'])

Exception in callback <Task pending name='Task-1' coro=<Scraper._process() running at [PATH]/venv/lib/python3.11/site-packages/twitter/scraper.py:603> cb=[run_until_complete.<locals>.done_cb()]>
handle: <Handle <Task pending name='Task-1' coro=<Scraper._process() running at [PATH]/venv/lib/python3.11/site-packages/twitter/scraper.py:603> cb=[run_until_complete.<locals>.done_cb()]>>
Traceback (most recent call last):
 File "uvloop/cbhandles.pyx", line 61, in uvloop.loop.Handle._run
TypeError: 'Task' object is not callable

Removing uvloop.install() or placing asyncio.get_event_loop_policy().new_event_loop() before the rest of the code allows the test to pass.
However, these fixes are not working for my actual project, which is built around asyncio, where it still fails and throws another error: Can't patch loop of type <class 'uvloop.Loop'>.
how can i resolve this?
thank you

I have this same issue with Python 3.10.
It was working until about a week ago. I'm assuming some dependency somewhere got updated on my side.

removing uvloop code works for me for now


feat: support for go templates from an annotation

Description
Introduce support for specifying a go template inside an annotation to generate and replace the contents of a manifest's data field.
Please look at docs/howitworks.md to see how the feature works exactly.
My goal was to enable fully dynamic generation of secrets' contents. My problem was that I had to repeat myself every time I created a secret. First I had to create the secret in the vault and specify all the fields it should have. Then in the manifest I used the same field names for clarity. Then for every secret key in the manifest I had to specify the secret's path. Templates now allow me to specify all the fields in the Vault once and have the manifest be generated automatically.
This feature works similarly to Vault's agent injector.
Checklist
Please make sure that your PR fulfills the following requirements:

[x] Reviewed the guidelines for contributing to this repository
[x] The commit message follows the Conventional Commits Guidelines.
[x] Tests for the changes have been updated
[x] Docs have been added / updated
[ ] Optional. My organization is added to USERS.md.

Type of Change

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

Other information
I went ahead and implemented the functionality but did not talk to the maintainers to see if you'd be interested in introducing it. Would you like to add it or do you have different plans for this plugin?

 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.

Codecov Report

Merging #281 (e502529) into main (4cbcd37) will decrease coverage by 0.84%.
The diff coverage is 56.75%.

@@            Coverage Diff             @@
##             main     #281      +/-   ##
==========================================
- Coverage   75.35%   74.50%   -0.85%
==========================================
  Files          20       20
  Lines         775      812      +37
==========================================
+ Hits          584      605      +21
- Misses        121      130       +9
- Partials       70       77       +7

Impacted Files
Coverage Δ

pkg/kube/template.go
84.61% <33.33%> (-4.28%)
:arrow_down:

pkg/kube/util.go
81.81% <58.82%> (-6.52%)
:arrow_down:

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 4cbcd37...e502529. Read the comment docs.

The code looks great @hugodutka - I'm just a little confused on the use-case. I read the nice docs you wrote here, but if I want to generate a secret with all the keys of a particular Vault secret, why wouldn't I just use something like the agent injector, as I have no need to finely control where the keys of the secret get injected in the YAML via <placeholder>s?
Is the thinking here so that you can generate manifests that can be managed with Argo CD, unlike the agent injector which will just inject the secrets in pods? Or maybe that this would work with other backends besides Hashicorp Vault? I guess in theory it should, but has it been tested with any other?

Thanks again for the PR @hugodutka, after some discussions we decided not to include this feature. I think if we were going to do something like this, it would be to make Go templating a fully supported templating option that could be used instead of using the < > placeholders. That may be something we consider for a v2 of AVP but it will not be in our immediate backlog. Thanks again!


Native Libraries cannot be loaded with 11.0.4 on Mojave

Platform:
OSX Mojave
Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64
Architecture:
x86_64
Issue description
When attempting to load native libraries on the above platform with any of the 11.0.4 builds, I get an exception:
/private/var/folders/f6/c8gfypz56c5d9b66l6_1n30m0000gn/T/native-platform4313193693498570932dir/libnative-platform.dylib: code signature in (/private/var/folders/f6/c8gfypz56c5d9b66l6_1n30m0000gn/T/native-platform4313193693498570932dir/libnative-platform.dylib) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.

When running with 11.0.3, everything works as expected.
Reproducible test
There is a java app over here: https://bintray.com/beta/#/adammurdoch/maven/net.rubygrapefruit:native-platform-test/0.18?tab=files which tests various native calls.
If you download the zip, and unpack it, I get the following results:
11.0.3 (Good)
$ bin/native-platform-test

Select test to run:
  1) Show terminal details
  2) Show machine details
  3) Show file systems
  4) Test input handling
  5) Example prompts
> 6) Exit
Use the arrow keys to select an option and press enter

11.0.4 (Bad)
$ bin/native-platform-test
Exception in thread "main" net.rubygrapefruit.platform.NativeIntegrationLinkageException: Native library 'libnative-platform.dylib' could not be loaded for Mac OS X x86_64.
	at net.rubygrapefruit.platform.internal.NativeLibraryLoader.load(NativeLibraryLoader.java:61)
	at net.rubygrapefruit.platform.Native.init(Native.java:55)
	at net.rubygrapefruit.platform.Native.get(Native.java:80)
	at net.rubygrapefruit.platform.test.Main.terminals(Main.java:286)
	at net.rubygrapefruit.platform.test.Main.main(Main.java:109)
Caused by: java.lang.UnsatisfiedLinkError: /private/var/folders/f6/c8gfypz56c5d9b66l6_1n30m0000gn/T/native-platform4313193693498570932dir/libnative-platform.dylib: dlopen(/private/var/folders/f6/c8gfypz56c5d9b66l6_1n30m0000gn/T/native-platform4313193693498570932dir/libnative-platform.dylib, 1): no suitable image found.  Did find:
	/private/var/folders/f6/c8gfypz56c5d9b66l6_1n30m0000gn/T/native-platform4313193693498570932dir/libnative-platform.dylib: code signature in (/private/var/folders/f6/c8gfypz56c5d9b66l6_1n30m0000gn/T/native-platform4313193693498570932dir/libnative-platform.dylib) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.
	at java.base/java.lang.ClassLoader$NativeLibrary.load0(Native Method)
	at java.base/java.lang.ClassLoader$NativeLibrary.load(ClassLoader.java:2430)
	at java.base/java.lang.ClassLoader$NativeLibrary.loadLibrary(ClassLoader.java:2487)
	at java.base/java.lang.ClassLoader.loadLibrary0(ClassLoader.java:2684)
	at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2617)
	at java.base/java.lang.Runtime.load0(Runtime.java:767)
	at java.base/java.lang.System.load(System.java:1831)
	at net.rubygrapefruit.platform.internal.NativeLibraryLoader.load(NativeLibraryLoader.java:51)
	... 4 more

I suspect this is an OS X only thing, but I'm testing it on ubuntu to make sure

Tested on Ubuntu, and both version work as expected...
This seems to be just an OS X issue

I am also experiencing the same issue on macos with jdk-11.0.4+11.2, reverting to jdk-11.0.3+7 works.

@gdams likely related to the other issues you're working on...

@taubeklavs we have a fix in place for this and are in the process of creating a jdk-11.0.4+11.3 release. Apologies for the inconvenience

Awesome thanks! 😎👍
Not sure how I missed https://github.com/AdoptOpenJDK/openjdk-build/issues/1206 Sorry about that 😞

Doesn't look like that build is out yet and issue was blocking something I'm working on -- for anyone else in the same boat, you should be able to:
brew cask reinstall https://raw.githubusercontent.com/AdoptOpenJDK/homebrew-openjdk/c017a832eec4f940e11c139b6e7852eeb3b2aad8/Casks/adoptopenjdk11.rb

to get the adoptopenjdk11 cask to read out like so:
$ brew cask info adoptopenjdk11
adoptopenjdk11: 11,0.3:7
https://adoptopenjdk.net/
/usr/local/Caskroom/adoptopenjdk11/11,0.3:7 (181.4MB)
From: https://github.com/adoptopenjdk/homebrew-openjdk/blob/master/Casks/adoptopenjdk11.rb
==> Name
AdoptOpenJDK 11
==> Artifacts
OpenJDK11U-jdk_x64_mac_hotspot_11.0.3_7.pkg (Pkg)

Once the new build is published, simple brew cask upgrade should pick it up. :)

Save erroneous behavior occurs with
openjdk version "12.0.2" 2019-07-16
OpenJDK Runtime Environment AdoptOpenJDK (build 12.0.2+10)

I just downloaded jdk-12.0.2+10.2 and ran the native-platform-test. I got the "Bad" trace reported by OP.
Any hope to get a fixed build?

Hi, can confirm this also on the version 12.

Just checked the latest 11.0.5

openjdk version "11.0.5" 2019-10-15

And this all works on OS X 😎 🎉
Closing this
Thanks all!

I have this problem with 14.0.1 ...

@MRigal How did you install the binary - was it a PKG file via homebrew?

Both versions installed via homebrew. I also added the recommended symlinks
after the installation
Martijn Verburg<EMAIL_ADDRESS>schrieb am Fr., 1. Mai 2020,
14:37:

Reopened #1211 https://github.com/AdoptOpenJDK/openjdk-build/issues/1211
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AdoptOpenJDK/openjdk-build/issues/1211#event-3293067036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQWX55C4EBWQNP5G423COTRPK67VANCNFSM4IKS6X5Q
.

I'm still having this issue with adoptopenjdk12 and osx catalina
os: mac osx catalina 10.15.4
jdk: installed via
▶ brew tap adoptopenjdk/openjdk
▶ brew cask install adoptopenjdk --no-quarantine

brew installed the jdk under /Library/Java/JavaVirtualMachines/
▶ java --version
openjdk 12.0.2 2019-07-16
OpenJDK Runtime Environment AdoptOpenJDK (build 12.0.2+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 12.0.2+10, mixed mode)

sbt installed via:
▶ brew install sbt

▶ sbt sbtVersion
[info] 	1.3.10

Some people suggested that this is an issue with gatekeeper from osx but if I globally disable the gatekeeper the issue persists:
▶ sudo spctl --master-disable
▶ spctl --status
assessments disabled

# starting sbt will produce the same output (code signature in [...] not valid for use in process using Library Validation: mapped file has no cdhash)

▶ sudo spctl --master-enable
▶ spctl --status
assessments enabled

Checking the item shows that it is indeed not signed
▶ codesign -dv --verbose=4 ~/Library/Caches/JNA/temp/jna123.tmp
~/Library/Caches/JNA/temp/jna123.tmp: code object is not signed at all

Checking the /Library/Java/JavaVirtualMachines/adoptopenjdk-12.jdk/Contents/Info.plist I can see the following:
	<key>CFBundleSignature</key>
	<string>????</string>

This is apparently the default on initialisation of new xcode projects and has not been changed?!

@peter-gerhard There's no hardened runtime and notarization support on OpenJDK 12 and there won't be because it has reached its EOL.

Furthermore, I'm closing this issue because 11.0.7's PKG is fully notarized.

@aahlenst I found out the /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Info.plist does not have the bundle signature.
<key>CFBundleShortVersionString</key> 	<string>1.0</string> 	<key>CFBundleSignature</key> 	<string>????</string> 	<key>CFBundleVersion</key> 	<string>11.0.7</string>
Which version is currently code signed as I tried 11 and 12 version already

8u252.1, 11.0.7 and 14 are notarized. You need the PKG, however.

@aahlenst FYI this was not fixed in 11.0.7 nor in 11.0.8, but it is indeed fixed in 11.0.9

@aahlenst FYI this was not fixed in 11.0.7 nor in 11.0.8, but it is indeed fixed in 11.0.9

If anyone got to this thread due while trying to compile a KMM project, I was able to fix it by upgrading gradle version to 7.0.0-alpha09.

getting same issue on building apk with flutter 2.5.3.
It is strange that, there is error but my build is succeed. And apk works.


How to configure

Hi,
I was able to get all the IDs and stuff but I can't get the config right. Could you please instruct how to setup this custom component?
Simply adding the yaml code you have on your README won't work.
Thanks a lot

Figured it out...you didn't mention that it is just a sensor.
;-)
Now it works like a charm

Hi,
I Also figured it now out with install via HACS
And the Config (all the ID'S)
I'm still not sure how it works i have now a sensor
(blue bracket was a test with set)

The orange is really "Bio" but i can only get it from today
so if i scroll to the future there are no additional entries
Is this how it should work?

@Micha031982
The sensor has the next collection date for this waset type as it's state, so if its today, you'll see today, if it's in the future, you'll see that as the state.
I've just updated the README.


feat(ui): Theme BottomSheetDragHandleView

Refs: https://m3.material.io/components/bottom-sheets/specs

fine by me, or we go straight for https://github.com/nextcloud/android-common/pull/208/commits/a89c4bd9834c113ebe46520e4528bcc2dd909a2a and the PR #208 while with the new Google implementation there is no fixed/stored values anymore but they are continuously calculated upon requesting them. However Scheme is deprecated with DynamicScheme. So we could either merge it and later add a "caching" object inbetween. OR are fine with the dynamic calculation.
What do you think @stefan-niedermann  ?

I don't need it urgently, so I think I can rebase it after DynamicScheme has been merged :slightly_smiling_face:

@stefan-niedermann what is your point of view on merging dynamicScheme? I will calculate any color on each access of the color, so far I didn't see any performance impact from an experience perspective on the talk client so I'd be fine with merging and release that version as-is and in case performance becomes an issue add a way to cache the calculated colors, not sure though that is possible/easy given the dynamicScheme implementation of Google.

Released with 0.15.0 @stefan-niedermann, have fun 🚀


charging session not recorded

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I parked my car at ~20:43 with 74% battery left, I have a scheduled charging after midnight (00:15 am). The car was charged properly to 100%, but nothing was recorded by teslamate. The dashboard showed the car was sleeping throughout the night.
Expected Behavior
The charging session should be recorded by teslamate.
Steps To Reproduce
No response
Relevant log output
teslamate-teslamate-1  | 2023-08-17 20:38:57.779 [info] Start of drive initiated by: %TeslaApi.Stream.Data{time: ~U[2023-08-18 03:38:54.765Z], speed: 0, odometer: 544.6, soc: 74, elevation: -11, est_heading: 323, est_lat: 37.547971, est_lng: -122.275226, power: 1, shift_state: "R", range: 202, est_range: 178, heading: 344}
teslamate-teslamate-1  | 2023-08-17 20:38:57.779 car_id=1 [info] Driving / Start
teslamate-teslamate-1  | 2023-08-17 20:43:50.107 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (423.946 ms)
teslamate-teslamate-1  | 2023-08-17 20:43:50.554 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (443.415 ms)
teslamate-teslamate-1  | 2023-08-17 20:43:50.583 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 302, latitude: 37.53756, longitude: -122.276166, native_latitude: 37.53756, native_location_supported: 1, native_longitude: -122.276166, native_type: "wgs", power: 3, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>766}
teslamate-teslamate-1  | 2023-08-17 20:43:50.583 car_id=1 [info] Driving / Ended / 2 km – 5 min
teslamate-teslamate-1  | 2023-08-17 20:43:50.583 car_id=1 [info] Start / :online
teslamate-teslamate-1  | 2023-08-17 20:44:55.876 car_id=1 [info] Charging detected: -1 kW
teslamate-teslamate-1  | 2023-08-17 20:48:46.116 [info] GET /
teslamate-teslamate-1  | 2023-08-17 20:48:46.123 [info] Sent 200 in 7ms
teslamate-teslamate-1  | 2023-08-17 20:50:25.454 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053/vehicle_data -> 408 (9080.024 ms)
teslamate-teslamate-1  | 2023-08-17 20:50:25.454 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
teslamate-teslamate-1  | 2023-08-17 20:50:25.454 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-17 20:50:54.538 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053/vehicle_data -> 408 (9081.400 ms)
teslamate-teslamate-1  | 2023-08-17 20:50:54.538 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
teslamate-teslamate-1  | 2023-08-17 20:50:54.538 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-17 20:51:23.630 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053/vehicle_data -> 408 (9090.681 ms)
teslamate-teslamate-1  | 2023-08-17 20:51:23.630 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
teslamate-teslamate-1  | 2023-08-17 20:51:23.630 car_id=1 [error] Error / :unknown
...
...
teslamate-teslamate-1  | 2023-08-18 00:12:51.977 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:12:51.978 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:13:22.015 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (35.484 ms)
teslamate-teslamate-1  | 2023-08-18 00:13:22.015 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:13:22.015 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:13:52.057 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (40.477 ms)
teslamate-teslamate-1  | 2023-08-18 00:13:52.057 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:13:52.057 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:14:22.096 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (37.826 ms)
teslamate-teslamate-1  | 2023-08-18 00:14:22.096 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:14:22.096 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:14:52.155 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (57.105 ms)
teslamate-teslamate-1  | 2023-08-18 00:14:52.155 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:14:52.155 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:15:22.192 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (35.025 ms)
teslamate-teslamate-1  | 2023-08-18 00:15:22.192 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:15:22.192 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:15:52.238 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (43.834 ms)
teslamate-teslamate-1  | 2023-08-18 00:15:52.238 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:15:52.238 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:16:22.296 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (56.923 ms)
teslamate-teslamate-1  | 2023-08-18 00:16:22.296 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:16:22.296 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:16:52.353 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (54.973 ms)
teslamate-teslamate-1  | 2023-08-18 00:16:52.353 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:16:52.353 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:17:22.380 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (25.424 ms)
teslamate-teslamate-1  | 2023-08-18 00:17:22.380 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:17:22.381 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:17:52.440 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (57.655 ms)
teslamate-teslamate-1  | 2023-08-18 00:17:52.440 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:17:52.440 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:18:22.499 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (58.177 ms)
teslamate-teslamate-1  | 2023-08-18 00:18:22.499 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:18:22.500 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:18:52.560 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (59.149 ms)
teslamate-teslamate-1  | 2023-08-18 00:18:52.560 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:18:52.561 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:19:22.598 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (35.614 ms)
teslamate-teslamate-1  | 2023-08-18 00:19:22.598 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:19:22.598 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 00:19:52.658 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (58.208 ms)
teslamate-teslamate-1  | 2023-08-18 00:19:52.658 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 00:19:52.659 car_id=1 [error] Error / :unknown
...
...
teslamate-teslamate-1  | 2023-08-18 06:59:42.100 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (31.871 ms)
teslamate-teslamate-1  | 2023-08-18 06:59:42.100 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 06:59:42.100 car_id=1 [error] Error / :unknown
teslamate-teslamate-1  | 2023-08-18 07:00:12.239 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> 401 (137.655 ms)
teslamate-teslamate-1  | 2023-08-18 07:00:12.239 car_id=1 [error] Error / :unauthorized
teslamate-teslamate-1  | 2023-08-18 07:00:12.239 [info] Refreshing access token ...
teslamate-teslamate-1  | 2023-08-18 07:00:12.795 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (555.013 ms)
teslamate-teslamate-1  | 2023-08-18 07:00:12.821 [info] Scheduling token refresh in 6 h
teslamate-teslamate-1  | 2023-08-18 07:00:52.619 car_id=1 [info] Start / :online
teslamate-teslamate-1  | 2023-08-18 07:00:52.654 car_id=1 [info] Connecting ...
teslamate-teslamate-1  | 2023-08-18 07:00:52.662 car_id=1 [info] Suspending logging
teslamate-teslamate-1  | 2023-08-18 07:02:22.120 [notice]     :alarm_handler: {:clear, TeslaMate.Vehicles.Vehicle_1_api_error}
teslamate-teslamate-1  | 2023-08-18 07:17:41.111 car_id=1 [info] Fetching vehicle state ...
teslamate-teslamate-1  | 2023-08-18 07:17:41.153 [error] GET https://owner-api.teslamotors.com/api/1/vehicles/3744618709412053 -> error: "socket closed" (41.066 ms)
teslamate-teslamate-1  | 2023-08-18 07:17:41.153 [warning] TeslaApi.Error / socket closed
teslamate-teslamate-1  | 2023-08-18 07:17:41.153 car_id=1 [info] Unhandled fetch result: {:error, :unknown}
teslamate-teslamate-1  | 2023-08-18 07:22:43.305 car_id=1 [info] Fetching vehicle state ...
teslamate-teslamate-1  | 2023-08-18 07:22:43.517 car_id=1 [info] Start / :asleep
teslamate-teslamate-1  | 2023-08-18 07:22:43.543 car_id=1 [info] Disconnecting ...
teslamate-teslamate-1  | 2023-08-18 07:43:09.734 [info] GET /
teslamate-teslamate-1  | 2023-08-18 07:43:09.741 [info] Sent 200 in 7ms
teslamate-teslamate-1  | 2023-08-18 08:42:38.379 car_id=1 [info] Start / :online
teslamate-teslamate-1  | 2023-08-18 08:42:38.398 car_id=1 [info] Connecting ...
teslamate-teslamate-1  | 2023-08-18 08:43:18.946 [info] Start of drive initiated by: %TeslaApi.Stream.Data{time: ~U[2023-08-18 15:43:18.291Z], speed: 13, odometer: 546.0, soc: 100, elevation: -2, est_heading: 31, est_lat: 37.537652, est_lng: -122.276248, power: 16, shift_state: "D", range: 272, est_range: 234, heading: 328}
teslamate-teslamate-1  | 2023-08-18 08:43:18.947 car_id=1 [info] Driving / Start

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
1.27.3

I am having a similar issue. I am using the "Charge on solar" feature, and it looks like teslamate is no always seeing the transition from "online" to "charging". I watch the Tesla app and see it start to charge, and teslamate is not changing, even after 10 minutes. If I open the teslamate site (port 4000), it shows "falling asleep for xx minutes". If i click the "cancel sleep attempt" button on the bottom of the home page, all of the sudden it changes to "Charging".
This is not happening everytime, but happens more often than not. Since I'm using the charge on solar, the charging cycle can start and stop every few minutes, depending on clouds. ChargeHQ would not allow the charging to restart for 15 minutes minimum, be Tesla's app doesn't seem to care about the start, stops.
Hopefully this will help in finding out what's causing this. Please let me know if any data is needed to help. I will continue to see if I can pin down what causes it.
I am also on version 1.27.3

I just activated the charge on solar feature and am seeing the same issue where sleep attempts cause Teslamate to miss the resumption of charging. I saw some older docs that mentioned an ability to set the time before trying to sleep, but I don't see that option in the current version.
I also had several short charging sessions today that showed zero energy added, so they do not show up in Grafana on the Charges dashboard. I'm not sure if that is somehow related. In the database, in the charges table the 'charge_energy_added' is 0.00 for each row for those charging_process_ids, even though the charger_actual_current, charger_power, and charger_voltage are all non-zero.
Only one charge of the several short charges today is showing some energy added and is showing in Grafana.

@jfliu1 - Did Teslamate show the car as being offline when it was charging or just asleep?
I was having an issue for several months where about 80% of the time, my cars would go offline right when the scheduled charge began. They were showing offline in the Tesla app as well, so it was not a Teslamate issue.
I put in a service ticket and was told that it was a known bug in several versions of Tesla software, and that it would eventually be fixed on a future release. They didn't want to commit to exactly which version would have the fix. The cars were in fact dropping offline from the Tesla servers when charging began, so nothing in the app worked until they reconnected, which often wasn't until I opened a door to wake them.
I don't think I've seen it happen recently and both my cars are now on 2023.32.7, so I'm hopeful that it has been fixed in the latest software versions.

TeslaMate waited for your car falling asleep and did not pull any data. Your car did not fall asleep and started charging. TeslaMate was still waiting it to fall asleep.

Unfortunately, my understanding, this is a limitation with the Tesla API. If Teslamate where to keep polling the car, yes, we could get up-to-date data, but then the car would not go to sleep. And the streaming API - AFAIK - is restricted in the parameters it will stream (plugged in status/charging status is not one of them).
I make sure myself that on the occasion I plug the car in when it is probably trying to sleep, I cancel the sleep attempt. Which is annoying, but we are not in any position to make improvements to the Tesla API.
And I have also disabled trying to sleep while the car is unlocked. To ensure I do have time to plug in immediately after arriving home, even if there is lots of shopping to take inside first (for example).
This probably should be mentioned on a FAQ or something somewhere (if it isn't already).

The issue somehow magically resolved by itself a few weeks ago. Now every charging session gets recorded correctly. Not sure whether that's due to some changes on Tesla side.


Error for code?

Whether there is no indentation in line 21 of the time_add method of load_dataset

if indentation of day_init = day_init + 1 is right。Why is the result of day_init >6 holiday_init = 2 and not week_init>6？

Hello, thank you for your interest in our work. Here, 'day_init' represents time in day, and 'week_init' represents day in week, so the 'day_init' in line 21 does not need indentation. Since we do not use the 'holiday' element in our model, we overlooked this issue. When 'day_init' < 6, 'holiday_init' = 1, here 'day_init' should be corrected to 'week_init'. Thank you for pointing out this issue.


Boltdb Deleting Bucket?

I've started poking around in the bolt codebase, but it seems like, nondeterministically, though after a significant amount of changes within a single tx, calling Delete on a bucket can result in the entire bucket being deleted.
edit: it doesn't always drop the whole bucket. Sometimes calling delete will just drop 3/5 items. Maybe it's getting confused about a leaf node vs. root/branch node and dropping a bunch of children?
edit2: inside of Bucket.Delete, a call to c.node().del(key) is made. Seems like the failure only occurs when the index of the leaf is 0 and len(node.inodes) is 1. Further testing continues to confirm this trend.
Things I know about my code:

A lot is happening in a single tx. Probably on the order of thousands of reads and writes to the bucket.
The change that is causing the bucket to be emptied is not happening inside of a ForEach statement or a cursor.
The bucket seems most likely to wipe when there are only a few elements remaining. The stress test brings it up as high as 50 items, but it usually fails at 2 or 3 items. I haven't seen it fail with more than 6 items remaining in the bucket. (got it to drop from 18 to 10 items in a single delete operation by increasing the stress)
The failure is nondeterministic. Sometimes there won't be a failure, but I can get the failure happening again by adding printlns in arbitrary places in my code (the logic is not changed at all, but it can have an effect on whether the test fails or not)

    lenScoBucket(tx) // prints 3
    err := scoBucket.Delete(id[:]) // err is nil
    lenScoBucket(tx) // prints 0

My whole codebase is pretty complicated. It's completely possible that I'm doing something else incorrect somewhere but the error isn't showing up until this point. I will be digging through the bolt code, but was hoping someone had ideas.

Is the transaction shared across goroutines?  I ask because it's not safe to do that and you mentioned that you can cause the error by adding prints which changes timing characteristics and therefore smells like a race condition.
If you're deleting different IDs from different goroutines using the same transaction, the type of behavior you describe could certainly happen due to the fact Delete involves a seek which sets state in the transaction and a race there could end up with an incorrect node being deleted.

@davecgh thanks for dropping in.
The tx is happening as 1 goroutine. The program does spawn hundreds of goroutines but the tx is only active inside of 1 of them. I'll double check that though. Additionally, I have the race detector on, and it's not complaining at all.

The stress test brings it up as high as 50 items, but it usually fails at 2 or 3 items. I haven't seen it fail with more than 6 items remaining in the bucket.

I've now been able to get it to drop from 18 items to 10 items in a single delete operation.

Running tx.Check() is not turning up any errors either. Should tx.Check() be able to catch an error like this?

I was able to prevent the problem (even under extreme load) by periodically copying the bucket to memory, deleting it, and then repopulating it. Once the dataset is too large for this to be manageable, I imagine using a temporary bucket will work just as well.
I strongly suspect that there is an error somewhere in bolt's node/leaf logic. The fact that the failures are nondeterministic does suggest a race condition on my end, though I did my best to isolate any possibility of that. To the best of my knowledge, the problem is not from accessing the database using multiple gothreads.
I am able to reproduce the problem by disabling the 'bucket refreshing', and can assist with debugging if needed.

Can you share something that reproduces this behavior?

https://github.com/NebulousLabs/Sia/tree/bolt-narrowing
run make test to reproduce the issue. The whole repo is single threaded. I stripped out substantial portions of the code to keep things as simple as possible. A combination of View, Update, and ForEach are all used in the repo, but as far as I've seen I'm not misusing anything anywhere.
My next step is going to be trying to reproducing the error with just the calls to the database, none of the extra logic. I'll get the calls with some form of logging.

https://github.com/NebulousLabs/Sia/tree/bolt-narrowing
Stripped out as much logic as time allowed. I tried to reproduce the issues by making a boltdb instance that just copied the reads and writes, but I was unsuccessful. I was only managing the reads + writes for 1 bucket, as opposed to the whole database.
The entire repository runs on a single goroutine, but the failures are still nondeterministic. Would appreciate more guidance. I'm not sure how to continue.

Confirmed that this behavior still appears as early as 6903c7447bfb817c1f9995be283b3301c6c1fb5c

I realized why the failures are nondeterministic - the test inserts random data seeded by a timestamp. That behavior is fairly well buried, but I should have realized it sooner.

Further testing indicates that the deletions are probably happening correctly, but our code to check the number of entries is faulty. We are using ForEach to count the number of entries in the bucket, inside the same transaction in which the entries are deleted. My guess is that this is the real source of the discrepancy.
Is it safe to call ForEach on a bucket that has been modified within the same transaction?

Update: calling b.rebalance() after the c.node().del(key) call in bucket.Delete seems to resolve the problem. Again, I don't have a strong grasp of bolt's internals, so it will take me some time to find out why this works. At any rate, rebalancing after each delete incurs an acceptable cost for our purposes, so we may choose to vendor bolt and do it ourselves.

@benbjohnson can you provide your input? Can you think of a reason that this would be happening, why b.rebalance() would solve the problem, and whether our fix is something you would merge into master?


fix: fix build process

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


List of all countries data

Sortable table of all country data, shown in a modal.
Columns:

Cases
Deaths
Death Rate
Recoveries
Recovery Rate

✅


how to enable glowing effect for active tabs

the left-most tab is currently open

yep

well.. the active tab should be darker than the non active ones to differentiate it. weird that this isn't happening on your setup.

The coloured lines aren't the active tab, but Container Tabs which is a different feature.


[BUG] cudf_udf_test.py is flakey

All of the tests in cudf_udf_test.py fail periodically and need to be fixed.

Any log  and the error snip ? I guess it could be OOM error.

Marking as P2, @GaryShen2008 please confirm whether this test is required for the pandas cudf functionality.

reverting change with https://github.com/NVIDIA/spark-rapids/pull/813 due to tests failing in dev environment

also, even if these are off by default I would like to see proper documentation on how someone would run them as to what extra dependencies and commands are needed.

@firestarman It seems we only considered the docker environment and forgot the dev environment. May need more docs to explain how to run it or add some checking in test code.

@shotai is working on it


Tisnew 4109

PR for history view

Please fix the commit prefixes(should be 'feat' instead of feature)

Will do


Question on Usage with Default Template and other JSX Files

@yeojz -
Thanks for this awesome module.
I have been trying to read through the code to understand if I can setup my project in a certain way but haven't been able to find the right place to look or what to configure.
I am looking to setup a structure as such:
src/
    work/
        index.jsx
    index.jsx
    default.jsx

using the following configuration:
isStatic: true,
directory: './src',
defaultTemplate: 'default.jsx',
pattern: '**/*.jsx',

Ultimately, the idea is that default.jsx would be used as the template for any other jsx files processed (index.jsx and work/index.jsx).
Initially, I set {this.props.contents} in my default.jsx but that returns the file as a string.
Is there something I am missing configuration wise to have it transform the other jsx files and use it in default.jsx? Or is there any other way to do so? If not, I am willing to work on implementing it (if you think it fits) - would just need some guidance on where you think the best place to start is.

@borwahs
Thanks.
Metalsmith reads and parse the source files into a Buffer, which is subsequently converted into a string. As such, {this.props.contents} would be affected as it's no longer a module.
From your snippets, it would seem that your source and template directory is the same (I presume from the name of the folder), and as such, the files are subjected to the above when read.
I've taken a shot at a possible solution - https://github.com/yeojz/m-rt-issue-53
It makes use of node's module system to programmatically evaluate and create the module that is passed as {this.props.contents}.
Maybe take a look and let me know if that fits / works for you / have a better solution if inspiration hits from that 👍

@yeojz -
Thanks for the quick response! I really appreciate it.
Your solution makes total sense and should fit. I'm kicking myself for not thinking of converting the string back via module.
I'm going to play around with the solution tonight and will report back!

@yeojz -
The solution you provided above does solve what I was looking. It has given me enough to be able to take it a bit further and get a solution working that allows for importing/requiring JSX files with one another within the src/ directory (a bit hacky though).
Another avenue I plan to explore is setting up a partials/ directory such that the default.jsx template and any files in src/ could import them.
I'll report back here when I get all of that setup. Not sure if there is any interest on your side for this module but in case anyone else comes across this.
Thanks for your help and this module!

@borwahs
Glad that worked for you!
Sure. I think this is a good use case to support as core since metalsmith is not all about just markdown files. It can be an enhancement to the existing react strategy or even part of the documentation.
Maybe when you've got things ironed out we can see if this can fit into a more generic strategy or part of the documentation so that it is not only applicable for react, but others as well.
Thanks and Cheers!!


3868 docs spark uplevel

Adding Spark as a top-level category in our docs, right after quick start.
https://github.com/treeverse/lakeFS/issues/3868

 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.Adi Polak seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

I don't think Spark should be a top level element: it's a bit patchy to me. We can move it to be the first element of the Integrations section, and add links to it in other places - but it just doesn't make sense as a menu item of its own.

Added Spark as a top-level experiment

Pulling by adminiforce until Adi convinces GitHub she really is Adi (she did manage to convince me...)


SyntaxError: invalid syntax

Hi there.
When I try to download a Udemy course it is saying "SyntaxError: invalid syntax."
This was working before I updated to OS High Sierra but is now giving me this error.
MacBook-Pro-de-Joe:LGC Website Joe$ cd /Users/Joe/Desktop/WEBSITE\ BUILDING/TUTORIALS/UDEMY\ VIDEOS
MacBook-Pro-de-Joe:UDEMY VIDEOS Joe$ python3
Python 3.7.2 (v3.7.2:9a3ffc0492, Dec 24 2018, 02:44:43)
[Clang 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

python3 udemy-dl.py https://www.udemy.com/bootstrap-4-from-scratch-with-5-projects/
File "", line 1
python3 udemy-dl.py https://www.udemy.com/bootstrap-4-from-scratch-with-5-projects/
^
SyntaxError: invalid syntax

Would appreciate some help with this, thanks a lot.
 Just open terminal and run python3 udemy-dl.py courseURL right away.

@luloproductions its a command line tool, check out some tuts on how to run python code on terminal

looks like your problem is you're running python3 udemy-dl.py from within the Python interpreter.
i mean, don't run python3 before you run python3 udemy-dl.py. Just open terminal and run python3 udemy-dl.py courseURL right away.

Thanks brundidge!


net/http: Transport needs a limit on total connections (per host)

(go1.2rc4)

We're working on a reverse HTTP proxy that does some "stuff" (that's not
relevant) and proxies towards one or more backend HTTP servers. During testing I ran
into connection failures apparently due to running out of file descriptors. In narrowing
this down I reduced the problem to;

The "null" reverse proxy (doing nothing but proxying, using the
httputil.ReverseProxy):

http://play.golang.org/p/p1g4bpTZ_g

A trivial HTTP server acting as the backend behind the above proxy; it simply counts the
number of connections and responds successfully:

http://play.golang.org/p/F7W-vbXEUt

Running both of these, I have the proxy on :8080 forwarding to the server at :8090. To
test it, I use wrk (https://github.com/wg/wrk);

jb@jborg-mbp:~ $ wrk -c 1 -t 1 http://localhost:8080/
...

Granted, this isn't a super realistic reproduction of the real world since the latency
on localhost is minimal. I can't prove the same thing _can't_ happen in production
though.

Using one connection (-c 1) up to about three, this works perfectly. The server side
sees a bunch of requests over one to three connections, i.e. the number of backend
connections from the proxy matches the number of incoming connections. At around -c 4
and upwards, it blows up. The proxy doesn't manage to recycle connections quickly enough
and starts doing regular Dial:s at a rate of thousands per second, resulting in

...
2013/11/18 20:18:21 http: proxy error: dial tcp <IP_ADDRESS>:8090: can't assign requested
address
2013/11/18 20:18:21 http: proxy error: dial tcp <IP_ADDRESS>:8090: can't assign requested
address
2013/11/18 20:18:21 http: proxy error: dial tcp <IP_ADDRESS>:8090: can't assign requested
address
2013/11/18 20:18:21 http: proxy error: dial tcp <IP_ADDRESS>:8090: can't assign requested
address
...

from the proxy code and of course HTTP errors as seen by wrk.

My theory, after going through the http.Transport, is that when the number of requests/s
to the proxy goes up, the small amount of bookkeeping that is required to recycle a
connection (putIdleConn etc) starts taking just long enough that the next request in the
pipeline gets in before a connection is idle. The Transport starts Dial:ing, adding more
connections to take care of, and it explodes chaotically. I would prefer if it blocked
and awaited an idle connection instead of Dial:ing at some point.

Line 92, "// TODO: tunable on global max cached connections" seems relevant,
although in my case the tunable should probably be max connections per host instead of
globally.

I'll probably take a stab at implementing something like that to fix this (i.e.
rewriting Transport to limit connections), since I couldn't figure out a way around it
by just using the available API:s. Unless I seem to have misunderstood something
obvious...

//jb

Hit this issue in prod, blocking would definitely be preferable to exhausting sockets

Hitting this issue as well in production.

The persistConn objects used by the Transport object define a closech to listen for the closing of the underlying connections.
https://github.com/golang/go/blob/master/src/net/http/transport.go#L821
If this is reliable, it seems like you could use it as the basis for a release on a (per-host) semaphore that dialConn would need to aquire in order to create a new connection. As a start on a proposal for limiting total per-host connections, does this sound way off?

Related CL: https://go-review.googlesource.com/#/c/20485/

I am currently facing an issue similar one in this link https://groups.google.com/forum/#!topic/golang-nuts/LP6n02TFFh8. Using 1.4.3 version. I have increased the max connections per host to some higher value (@marbemac) and  it seems be working fine until now in Non Prod Env. But is this a proper fix? Will using go lang version 1.7 version resolve my issue without increasing the max connctions per host settings

I am using GoLang version 1.4.3 and got this issue. Will this be fixed if i upgrade the version to 1.6

@dkbalachandar, no.

Thanks @bradfitz. So do we have any workaround for this issue?. I have set the MaxIdleConnsPerHost  as 200 and tested it out. But the error got occurred again.

Call https://golang.org/pkg/net/http/#Transport.CloseIdleConnections occasionally, or set Transport. DisableKeepAlives. The Transport.MaxIdleConnsPerHost is not the setting you're looking for. The setting you're looking for doesn't exist (hence this bug).

Thanks @bradfitz, I will look for closing the Idle connections or set DisableKeepAlives.
Do you mean that MaxIdleConnsPerHost  is not exist? But i still find this setting in transport.go. I have set the http.DefaultTransport.(*http.Transport).MaxIdleConnsPerHost with 200.  I am thinking to increase it to a higher value, if nothing works. Let me know your thoughts

MaxIdleConnsPerHost exists. It just does something different than what you think it does. It's idle conns per host, not total.

Ok @bradfitz. Its a single host reverse proxy. So setting the MaxIdleConnsPerHost  is enough. Please let me know if my assumption is wrong.

@dkbalachandar, I don't have enough information to understand your problem.  GO app validates the browser cookie and creates a Proxy and serve the request if its a valid one. The error is happening during the load testing.  Initially we got the error similar like the one described in the issue description(http: proxy error: dial tcp HOSTNAME:PORT can't assign requested address)
Even after upgrading it to 1.6, the same issue is happening but GO App log shows the below error
"http: proxy error: net/http: request canceled"
I've enabled the DisableKeepAlives and performed the load testing and the same issue is happening, Now Go app shows the below errors.
http: proxy error: dial tcp HOSTNAME:PORT: i/o timeout
http: proxy error: net/http: request canceled
So we have to either call https://golang.org/pkg/net/http/#Transport.CloseIdleConnections or increase MaxIdleConnsPerHost to some higher value to fix this issue.
Let me know if you have any suggestions.

@dkbalachandar
(You should probably continue this conversation on the ML if you need more assistance)
Under the artificial environment of a load test, you can have problems recycling connection fast enough. There are a few related issues open, but if you sustain concurrency greater than MaxIdleConnsPerHost you are probably creating new connections too quickly.

@jbardin. Sure. Thanks

I got the similar error "dial tcp <IP_ADDRESS>:3308: connect: cannot assign requested address" when I use stmt.Exec() method to insert datas to mysql db. And google it to here, after reading the comments, I fixed it by setting db.SetMaxIdleConns(5).

Thanks all for your valuable suggestions. I tried all the solutions but nothing worked out. Then I reviewed the dependent system changes and got to know that their recent changes caused all these issues. So its nothing to do with the Go application.
Apologies for the confusion.

Sorry, didn't happen for Go 1.8.

I think I'm running into the same issue with a proxy lsof is showing hundreds of "ESTABLISHED" connections even when a response has been sent back to the client:
https://github.com/alexellis/faas/blob/master/watchdog/main.go
Can anyone confirm?

@alexellis don't you just need to add an r.Body.Close() to close the io.ReadCloser?  Sent you a PR: https://github.com/alexellis/faas/pull/13

@tleyden From the Go http docs:
https://golang.org/pkg/net/http/#Request
// The Server will close the request body. The ServeHTTP
// Handler does not need to.
Body io.ReadCloser

@tleyden @rogchap I added a Close call to both ends (client and server were both Golang) which fixed the issue.

@alexellis Yup, you have to call Close on the client. Glad you got it working.

Should I file a separate issue or is this the place to mention: I have code that does:
	ht := http.DefaultTransport.(*http.Transport)
	ht.MaxIdleConns = numConnections
	ht.MaxIdleConnsPerHost = numConnections

and then establishes numConnections simultaneous (go routines) back to back http connections (load testing tool)
if I check the number of sockets, it works as expected where I have numConnections established sockets for numConnections input with smaller numbers (1 and 9 or 10) but for 11 and up I have more sockets than the limit:
# with up to 10 it works
$ fortio -qps 0 -c 10 http://localhost:8080
$ netstat -na |awk ' $4 == "::1.8080" { print $0}'|wc -l
10
# with 16 there are more sockets:
$ echo `netstat -na |awk ' $4 == "::1.8080" { print $5}'| sort`
::1.56603 ::1.56604 ::1.56605 ::1.56606 ::1.56607 ::1.56608 ::1.56609 ::1.56610 ::1.56611 ::1.56612 ::1.56613 ::1.56615 ::1.56616 ::1.56617 ::1.56618 ::1.56619 ::1.56621 ::1.56622 ::1.56623 ::1.56624
$ netstat -na |awk ' $4 == "::1.8080" { print $0}'|wc -l
      20

this happens both on go version go1.8.3 darwin/amd64 and go version go1.8.1 linux/amd64
the full code to repro is go get istio.io/istio/devel/fortio/cmd/fortio (branch ldemailly-bench6 )
beside doing my own connection pooling is there a way to guarantee a maximum/exact number of socket used ? (and why do I get a few more than I ask for)

Given that this has been like this since Go 1.2 and still not fixed it seems likely we should just close it. But moving to Go 1.11 at least.

I don't want to close this. There are a number of related bugs I'd like to all address.

Looks like Transport.MaxConnsPerHost (new in Go1.11) addresses this.

Agree that Transport.MaxConnsPerHost fixes this.


📃: TextUtils project

:red_circle: Title : TextUtils
:red_circle: Aim : TextUtils is an application that helps manipulate the text (converting to uppercase or lowercase, copying the text to the clipboard, removing extra spaces, etc.)
:red_circle: Tech Stack Used : React.js, Bootstrap
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : Lakkaraju Nischala
What is your participant role?  GSSoC Extd 2024 Contributer

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Hello @LNischala ,
I am interested in contributing to the TextUtils project and have worked on a similar project in React.js before. Could you please assign this issue to me?
Name : Deepak Jain
Role : Contributer


Get loopback emulation test working with mixed-signal emulation models

Summary
This PR incorporates auto-generated emulation models for channel dynamics, ADCs, and PIs, and includes a working loopback emulation test that exercises the MM-CDR, FFE, PRBS checker, and JTAG interface.
Details
I thought it would be good to highlight changes in the chip_src folder since those files are used in synthesis of the real chip, and therefore should have a higher level of scrutiny:

vlog/chip_src/analog_core/analog_core.sv:

clk_div and clk_adc have special treatment for emulation, since clk_div is a bus of clock value signals (i.e. "regular" digital signals), while clk_adc is a true clock signal on the FPGA clock fabric (i.e. "special" digital signal).  In CPU simulation and ASIC synthesis, there is no such a distinction.
termination and biasgen are ifdef'd out for emulation, since Vivado doesn't do well with empty modules that are not black boxes (it is surprisingly hard to convince Vivado that we really want those modules to be empty)

vlog/chip_src/digital_core/digital_core.sv:

For emulation, the freq_divider block that drives clk_avg is replaced with an assignment of clk_avg to "0", since the generated clock clk_avg was causing hold time issues.  I think we should replace clk_avg with a clock enable signal in the future; this would be a good thing for both FPGA emulation and ASIC synthesis.  Then we would only have one clock signal in the digital core, which is clk_adc.
Vivado seems to have issues with slices of unpacked arrays (sets some signals to high-Z or X), so I used a generate statement to unpack the lower 16 values of adcout_unfolded into its own unpacked array, which is then passed to DSP and comparator blocks.
weight_manager and dsp_backend instances have some constants replaced by parameters from packages to make it easier to rescale the FFE and MLSD blocks.
I thought Vivado was not handling an assignment to a bus concatenation properly in the PRBS checker, so I moved those concatenations out of the PRBS checker instantiation.  In reality, the issue was likely due to something else, but I think the code is at least as readable in this new form (if a bit more verbose).

vlog/chip_src/jtag/jtag.sv

In one of the Markdown files, disable_product is set to a width of 10, but the width of ddbg_intf_i.disable_product may be 10 or 4 depending on whether we're running synthesis of the ASIC or FPGA emulator.  It was not clear to me that was a simple way to get that particular constant into the Markdown file, so I updated the way those signals are assigned from the raw JTAG interface to avoid a width mismatch.  (For FPGA emulation, the top 6 signals end up not being used for anything, but that is OK)

vlog/chip_src/weight_manager/wme_debug_intf.sv

Some fixed values were replaced with parameters, as in the digital core.  This made it easier to rescale the FFE and MLSD.

Codecov Report

Merging #104 into master will increase coverage by 0.41%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##           master     #104      +/-   ##
==========================================
+ Coverage   23.11%   23.53%   +0.41%
==========================================
  Files          32       32
  Lines        2059     2065       +6
==========================================
+ Hits          476      486      +10
+ Misses       1583     1579       -4

Impacted Files
Coverage Δ

dragonphy/fpga_models/chan_core.py
0.00% <0.00%> (ø)

dragonphy/fpga_models/clk_delay_core.py
0.00% <0.00%> (ø)

dragonphy/fpga_models/osc_model_core.py
0.00% <0.00%> (ø)

dragonphy/fpga_models/rx_adc_core.py
0.00% <0.00%> (ø)

dragonphy/fpga_models/tx_core.py
0.00% <0.00%> (ø)

dragonphy/views.py
80.37% <ø> (+0.93%)
:arrow_up:

dragonphy/adapt_fir.py
25.00% <50.00%> (+9.61%)
:arrow_up:

dragonphy/anasymod.py
86.56% <60.00%> (-4.82%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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