undefined method sub for nil:NilClass

Getting the below error for a POST request which generates below event:
## EVENT
{"queryStringParameters"=>{}, "multiValueHeaders"=>{"host"=>["api.***.com"],
"content-type"=>["application/x-www-form-urlencoded"],
"x-amzn-trace-id"=>["Root=1-5ebd4017-2bac93a418a717c03d540fd8"],
"x-forwarded-port"=>["443"], "accept"=>["application/json"], "scope"=>["user"],
 "x-authenticated-userid"=>[" *******"], "x-forwarded-proto"=>["https", " https"],
"content-length"=>["233"], "x-forwarded-for"=>["<IP_ADDRESS>"], "authorization"=>["Bearer *******"], "x-consumer-id"=>["7386304e-f7bd-4815-a086-030cfb0237fd"], "x-consumer-custom-id"=>["authoring_platform"],
"x-consumer-username"=>["authoring_platform"], "x-authenticated-scope"=>["user"]}, "httpMethod"=>"POST", "pathParameters"=>{},
"path"=>"/industries/export_to_google_drive", "multiValueQueryStringParameters"=>{},
"headers"=>{"host"=>"api.****.com", "content-type"=>"application/x-www-form-urlencoded", "x-amzn-trace-id"=>"Root=1-5ebd4017-2bac93a418a717c03d540fd8", "x-forwarded-port"=>"443",
"x-authenticated-scope"=>"user", "x-consumer-username"=>"authoring_platform",
"x-authenticated-userid"=>"****", "x-forwarded-proto"=>"https", "content-length"=>"233",
"x-forwarded-for"=>"<IP_ADDRESS>", "x-consumer-custom-id"=>"authoring_platform",
"x-consumer-id"=>"7386304e-f7bd-4815-a086-030cfb0237fd", "authorization"=>"Bearer ****", "scope"=>"user", "accept"=>"application/json"}, "body"=>"X2NzcmY9eGw2cWJpcHUtM1VDanRteVBNb1h5QTg2UUN5alNId0J4V0tVJmluZHVzdHJ5JTVCZW1haWwlNUQ9cHJhc2hhbnQlNDBqb21iYXkuY29tJmluZHVzdHJ5JTVCZm9sZGVyJTVEJTVCdXJsJTVEPWh0dHBzJTNBJTJGJTJGZHJpdmUuZ29vZ2xlLmNvbSUyRmRyaXZlJTJGdSUyRjAlMkZmb2xkZXJzJTJGMEJ6Vjl6TjI1ak5XVlNXbHpkbVkzWjNsTVdFVSZjb250ZW50PWluZHVzdHJpZXMmYXV0aF90b2tlbj0=",
"isBase64Encoded"=>true}

Error Stacktrace
{
    "errorMessage": "undefined method `sub' for nil:NilClass",
    "errorType": "Function<NoMethodError>",
    "stackTrace": [
        "/var/task/vendor/bundle/ruby/2.7.0/gems/lamby-2.0.0/lib/lamby/rack_http.rb:58:in `path_info'",
        "/var/task/vendor/bundle/ruby/2.7.0/gems/lamby-2.0.0/lib/lamby/rack_http.rb:17:in `env_base'",
        "/var/task/vendor/bundle/ruby/2.7.0/gems/lamby-2.0.0/lib/lamby/rack.rb:19:in `env'",
        "/var/task/vendor/bundle/ruby/2.7.0/gems/lamby-2.0.0/lib/lamby/handler.rb:79:in `call_app'",
        "/var/task/vendor/bundle/ruby/2.7.0/gems/lamby-2.0.0/lib/lamby/handler.rb:42:in `call'",
        "/var/task/vendor/bundle/ruby/2.7.0/gems/lamby-2.0.0/lib/lamby/handler.rb:7:in `call'",
        "/var/task/vendor/bundle/ruby/2.7.0/gems/lamby-2.0.0/lib/lamby.rb:21:in `handler'",
        "/var/task/app.rb:22:in `handler'"
    ]
}

Lambda Handler
def handler(event:, context:)
  logger = Logger.new($stdout)
  logger.info('## ENVIRONMENT VARIABLES')
  logger.info(ENV.to_a)
  logger.info('## EVENT')
  logger.info(event)

  Rails.logger = logger
  Rails.application.config.logger = logger

  Lamby.handler $app, event, context, rack: :http
end

Hey and thanks for using Lamby! Sorry for the slow reply. I'm looking at your event and I can't tell what rack method it is. I'm comparing it to these fixtures (https://github.com/customink/lamby/tree/master/test/test_helper/events) and not finding a match. Like if it was HTTP v1 I'd expect to see some "version"=>"1.0", "resource"=>"$default"... properties. Likewise that 1.0 would be a 2.0 for version two. I'm thinking you are using the older REST API? If so,
Lamby.handler $app, event, context, rack: :rest

Would be what you need? Was there a reason you were not using HTTP API?

Hello Ken,
This request is generated by Kong's Serverless AWS Lambda plugin. It is a REST API Request. I am not sure what you mean by older REST API? Has anything changed significantly in the REST API recently?
Since changing the event structure was not possible for me, I forked the repo and changed just one line to fix it for my case:
My Fork

Has anything changed significantly in the REST API recently?
YES! Late last year AWS rebased a new integration for API Gateway called HTTP API (https://aws.amazon.com/blogs/compute/announcing-http-apis-for-amazon-api-gateway/) the formats for the even pay load are entirely different. I think your issue is that your handler has rack: :http which uses that new method. I think you want this.
Lamby.handler $app, event, context, rack: :rest

Which uses the older REST integration with API Gateway. Did you try that?

Will give it a try
Sent from my iPhone

On 19-May-2020, at 7:38 AM, Ken Collins<EMAIL_ADDRESS>wrote:

Has anything changed significantly in the REST API recently?
YES! Late last year AWS rebased a new integration for API Gateway called HTTP API (https://aws.amazon.com/blogs/compute/announcing-http-apis-for-amazon-api-gateway/) the formats for the even pay load are entirely different. I think your issue is that your handler has rack: :http which uses that new method. I think you want this.
Lamby.handler $app, event, context, rack: :rest
Which uses the older REST integration with API Gateway. Did you try that?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Closing for age. Let me know if you need to re-open. Thanks!

Setting rack: rest worked. Thanks!


Fixed Linux TypeStr() function input double quote

Please provide Issues links to:

Issues: #

Provide test code:

Description
...

 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.


Adjust occlusionquery according to Vulkan spec.

This moves vkCmdCopyQueryPoolResults outside of the Render Pass, as it
should be according to the Vulkan spec. This understandably looks
wrong for the first frame, but by doing this you avoid having to use two
render passes to get the occlusion result.

Thx for noticing :1 Taking a look at this I also noticed that I do a copy and a get of the results which is unnecessary too.

Good points, just saw that. So the CopyQueryPoolResults and it's accompanying buffer is not needed at all then.

This also fixed the example on my Ivybrdige-based Intel Ultrabook on Linux using the Mesa drivers. One more demo running on min. spec hardware :+1:


Openshift ansible rpm

Remove custom code for building the openshift-ansible package.  The package has been added to the oit group RPM list.
This should be accepted and tested in sync with https://github.com/openshift/enterprise-images/pull/298

rcm-guest-print-building-changelog-report.sh is still problematic. Sharing get_rpm_changelog(record_log, "openshift-ansible") in buildlib between build/ocp and build/ose can eliminate this script altogether.


Advanced Filters are now GA but not available in Azure PowerShell or a non-preview REST API

https://github.com/MicrosoftDocs/azure-docs/issues/29533 was closed because Advanced Filters were preview at the time. However, they are now GA according to https://azure.microsoft.com/en-us/blog/simplifying-event-driven-architectures-with-the-latest-updates-to-event-grid/. The latest REST API supports advanced filters, but the API version is marked as preview. Additionally, neither the latest Azure CLI nor Azure PowerShell contain the advanced filter options discussed in the docs.

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

ID: 0f3bb8be-4dce-4bb2-cf49-9f43982af478
Version Independent ID: 40c7e66c-3ab7-abd0-a07c-d1e12c2b3e0f
Content: How to filter events for Azure Event Grid
Content Source: articles/event-grid/how-to-filter-events.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

Thanks for the feedback! We are currently investigating and will update you shortly.

@MicahMcKittrick-MSFT - please assign the issue to @banisadr
Thanks.

Any update on this? Any thoughts on using New-AzResource in the meantime until the parameter gets added to the non-beta powershell module?

Looks like this was addressed in Az.EventGrid 1.2.0. Thanks!


empty output

giving empty output on running the following command :
tag -s "#markdown" ~/zettelkasten/

Hey, sorry for the late answer. Could you provide the content of a file that you'd expect to be matched?

tag version is 0.1.0
file is attached :
0b2d332b.md

with version 0.3.0, i am getting the following output :
Error: Error { depth: 0, inner: Io { path: Some("#markdown"), err: Os { code: 2, kind: NotFound, message: "No such file or directory" } } }

Okay, I think I know what the issues are. First of all, your tagline must be the first line of the document. In the file you provided, your first three lines are
---
date: 2020-11-10T13:32
---

Furthermore, you need brackets around your tagline (like this: tags: [#markdown #commandline #nodejs]). So your new file should look like this instead:
tags: [#markdown #commandline #nodejs]
---
date: 2020-11-10T13:32
---

# to-markdown-cli

 [fabianmoronzirfas/to-markdown-cli: a command line tool for turning html to markdown](https://github.com/fabianmoronzirfas/to-markdown-cli)

## Installation

    npm install -g to-markdown-cli

## Usage

    Usage: html2md [options]

    Options:
      -V, --version          output the version number
      -i, --input     path to the input file (if input is stdin) it will be ignored
      -o, --output    path to the output file
      -c, --clipboard        use only the clipboard for input and output
      -g, --gfm              use GitHub Flavored Markdown
      -h, --help             output usage information

         _   _   _   _   _   _   _
        / \ / \ / \ / \ / \ / \ / \
       ( h | t | m | l | 2 | m | d )
        \_/ \_/ \_/ \_/ \_/ \_/ \_/

        html2md turns html into markdown

        - if no input file is given it ueses the clipboard content
        - if no output file is given it logs the result to stdout
        - if there is input from stdin clipboard will be ignored for inputs

        Examples:
            $ html2md -i ./foo.html # output to stdout
            $ html2md -i ./foo.html -o out.md # output to out.md
            $ html2md -o out.md # clipboard to out.md
            $ html2md -c # clipboard to clipboard
            $ html2md # clipboard to stdout
            $ html2md -g # clipboard to stdout using GitHub flavored markdown
            $ echo "/[[[\/h1]]]foo[[[/h1]]]" | html2md # will output to stdout

        Acknowledgments:
            Build on these great modules:
            - https://github.com/domchristie/turndown
            - https://github.com/sindresorhus/clipboardy
            - https://github.com/tj/commander.js

For the last error you got, it seems like you entered the query instead of the path to search as the path argument. This is my fault since I had to swap the order of those two arguments, sorry for the confusion. If you want to search your current path, your command should look like this:
tag . "#markdown"

I hope this explains it :)


Mention cloning of repository in CONTRIBUTING.md

Q
A

Bug fix?
yes/no

Breaking change?
yes/no

New feature?
yes/no

Deprecations?
yes/no

Spec compliancy?
yes/no

Tests added/pass?
yes/no

Fixed tickets
comma-separated list of tickets fixed by the PR, if any

License
MIT

Newbies who see towards contributing.md should get a clear view how to get the project up and running locally. It is actually a small change but I think it should be there.

@xtuc  Should I remove '$' or will you take care of that?

Yes, go ahead :+1:

This is for 7.0, so we use yarn for install now, otherwise 👍

@hzoo  So do we need to update the full document now?

I got it thanks!


Pin netCDF4<1.6.1

Description

Pin netCDF4 < 1.6.1
See https://github.com/ESMValGroup/ESMValCore/issues/1723, https://github.com/ESMValGroup/ESMValTool/issues/2924, https://github.com/SciTools/iris/issues/5016

Before you get started

[x] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🛠 This pull request has a descriptive title
[x] 🛠 Code is written according to the code quality guidelines
[x] 🛠 Documentation is available
[x] 🛠 Tests run successfully
[x] 🛠 The list of authors is up to date
[x] 🛠 Any changed dependencies have been added or removed correctly
[x] 🛠 All checks below this pull request were successful

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

cheers @remi-kazeroni - as we discussed on the Slack channel together with @zklaus and @bouweandela we are just about to apply a repodata patch on to the iris package so that they have a solid cross-builds/versions pin on netCDF4 so I think we should not pin anymore ourselves. Let's keep this on the table until that gets done though :+1:

OK the iris repodata patch PR is now up (and looking decent too, might I add :grin: ) https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/358

This is no longer needed, see #2929


Export multiple tiddlers to multiple Markdown files

And would it be possible to export the filtered entries as a folder with a lot of small mmrmrakdown files instead of a whole extra large file? It would be better to save it that way.

Originally posted by @dongrentianyu in https://github.com/cdaven/tiddlywiki-stuff/issues/3#issuecomment-1496853653

@dongrentianyu, I extracted this to another issue. They are closely related, but would be implemented in different places.
I'm not sure it's possible to do this, but I can have a look.
Otherwise, I could probably suggest a script to split the Markdown file into multiple files after download.

You can split the "tiddlers.md" file into multiple tiddler files using this Python script:
https://github.com/cdaven/tiddlywiki-stuff/blob/main/markdown-export/split-tiddlers.py

The best solution for this would probably be to export a zip file with multiple Markdown files inside. I don't know how hard this would be, and I make no promises about when I can look into it.

FWIW I use the following script to export multiple Tiddlers to multiple Markdown files from the command line: https://gist.github.com/hissohathair/88f862d48335271474bb5f87e82e73d6


Inability to get Kits datasets

I am Assistant Professor Dr. Wafaa from DPU and I am working in the scientific research center of our university. my Msc. Student is working on kidney Tumor detection using Deep learning and she tried to download the datasets (Kits19, KiTs21 and Kits23) but she couldn't and she urgently need these datasets so, can you kindly help us to get these datasets.

My Msc. Student is working on kidney Tumor detection using Deep learning and she tried to download the datasets (Kits19, KiTs21 and Kits23) but she couldn't and she urgently need these datasets so, can you kindly help us to get these datasets.


net/http: TestTransportConcurrency crash

See https://build.golang.org/log/c6a86a0372c38c4287799eb323ce2a559a770315
ok  	net	1.862s
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0xffffffff addr=0x0 pc=0xca834]

goroutine 5245 [running]:
panic(0x5504c0, 0x10e18030)
	/tmp/workdir/go/src/runtime/panic.go:500 +0x720
net/http.send(0x1187c200, 0xb51100, 0x12e7c420, 0x10e1a500, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/tmp/workdir/go/src/net/http/client.go:243 +0x414
net/http.(*Client).send(0x11ccd080, 0x1187c200, 0x0, 0x0, 0x0, 0x0, 0x11fa2088, 0x0, 0x0, 0x2)
	/tmp/workdir/go/src/net/http/client.go:146 +0x1a0
net/http.(*Client).doFollowingRedirects(0x11ccd080, 0x1187c200, 0xa0f8b4, 0x24, 0x0, 0x0, 0x0, 0x0)
	/tmp/workdir/go/src/net/http/client.go:528 +0xd80
net/http.(*Client).Get(0x11ccd080, 0x12e160f0, 0x24, 0x5909ed, 0x7, 0x0, 0x0, 0x12cf1740)
	/tmp/workdir/go/src/net/http/client.go:418 +0xc0
net/http_test.TestTransportConcurrency.func3(0x11ffb600, 0x11ccd080, 0x11ffb5c0, 0x11acb080, 0x11fedf00, 0xa0f99c)
	/tmp/workdir/go/src/net/http/transport_test.go:1282 +0x140
created by net/http_test.TestTransportConcurrency
	/tmp/workdir/go/src/net/http/transport_test.go:1300 +0x500
FAIL	net/http	13.477s

Is this reproducible? I've never seen this.

I ran the test 500 times in both normal and race mode (which does random goroutine scheduling) and can't reproduce.
Closing until there's more to go on.


Guard against this._rootDOMNode === null

Fixes (probably): #157
I have the same issue as reported in that issue without using shallow render - I use storyshots where I have no control over the rendering.

Thanks for the PR! Should this be used instead?

Yeah, I just found it :D Was about to post a link. And it works
.
diff --git i/test/storyshots.test.js w/test/storyshots.test.js
index a600114..ad3ac35 100644
--- i/test/storyshots.test.js
+++ w/test/storyshots.test.js
@@ -5,12 +5,23 @@
-import initStoryshots from '@storybook/addon-storyshots';
+import initStoryshots, {
+    snapshotWithOptions,
+} from '@storybook/addon-storyshots';

+import TextareaAutosize from 'react-textarea-autosize';
+
 initStoryshots({
     configPath: path.resolve(
         __dirname,
         '../packages/troika-docs/storybook-config'
     ),
+    test: snapshotWithOptions({
+        createNodeMock: element => {
+            if (element.type === TextareaAutosize) {
+                return document.createElement('textarea');
+            }
+        },
+    }),
 });

So yes it works, but is there any reason to just check for undefined instead of falsy?

I think by making calculateNodeHeight unreachable with this should fix ur issue. This is not yet released but I'm going to prepare a new release in following days.


fix: remove mixin-order escape hatch

There's no way anymore to make Hops resolve mixins in the opposite order
than the configs. Mixins and configs will now always be resolved in the same
order and thus be consistent in the way they overwrite previous presets.
BREAKING CHANGE: the config option enableLegacyMixinSortOrder has been removed.

Bors merge bot cheat sheet
We are using bors-ng to automate merging of our pull requests. The following table provides a summary of commands that are available to reviewers (members of this repository with push access) and delegates (in case of bors delegate+ or bors delegate=[list]).

Syntax
Description

bors merge
Run the test suite and push to master if it passes. Short for "reviewed: looks good."

bors merge-
Cancel an r+, r=, merge, or merge=

bors try
Run the test suite without pushing to master.

bors try-
Cancel a try

bors delegate+
Allow the pull request author to merge their changes.

bors delegate=[list]
Allow the listed users to r+ this pull request's changes.

bors retry
Run the previous command a second time.

This is a short collection of opinionated commands. For a full list of the commands read the bors reference.

bors merge


add boost thread pool

Currently, every time a query session is created, a thread is spawned and detached. however, this is quite inefficient when processing massive number of transactions. We may use a thread pool that can reuse threads efficiently. Due to the lack of efficient thread pool, I added boost thread pool in this pr for future usage.

https://github.com/cmu-db/peloton/blob/master/src/backend/common/thread_manager.h

There are two kinds of thread-pool in the current code can be used: std:thread and pthread:https://github.com/cmu-db/peloton/blob/master/src/backend/common/thread_manager.h

@domino-succ I am aware of this thread manager. But boost thread pool is highly optimized, especially compared with self-implemented thread pools.

Optimized for ? Boost is a wrapper around pthreads, similar to the std::thread.

We should have a single-thread pool for workers.
Make sure you guys coordinate with @amaliujia on this. They have been working on multi-threaded queries.

I don't think multi-threaded queries have high performance requirements on thread pool, since single thread has heavy workload so overhead of context switch or thread scheduling should not matter that much.
But it is hard to tell. I can test different thread pools at the end when parallel implementation is fixed and use the data to see if thread pools matter.

Thread pool is not a bottleneck for OLAP processing, and it is probably not a bottleneck for processing OLTP benchmarks with only a small number of connections (i.e., number of terminals in oltpbench). However, when processing workloads with hundreds of connections, relying on OS to schedule hundreds of threads may not be a good idea, and it may also bring additional overhead to transaction processing, garbage collection, as well as database logging. That's why we may need to rewrite the multithreading model in Peloton.

My two cents: use Intel's TBB. It outperforms Boost and pulls in fewer
dependencies IIRC.  The less we need Boost, the better.
On Thursday, 7 April 2016, Yingjun Wu<EMAIL_ADDRESS>wrote:

Thread pool is not a bottleneck for OLAP processing, and it is probably
not a bottleneck for processing OLTP benchmarks with only a small number of
connections (i.e., number of terminals in oltpbench). However, when
processing workloads with hundreds of connections, relying on OS to
schedule hundreds of threads may not be a good idea, and it may also bring
additional overhead to transaction processing, garbage collection, as well
as database logging. That's why we may need to rewrite the multithreading
model in Peloton.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/cmu-db/peloton/pull/123#issuecomment-207158863

Doesn't TBB require us to build a dependency graph for each query plan? @jarulraj  originally wanted to use TBB over a year ago and I talked him out of it. I don't remember the details of our conversation but I remember convincing myself that it was a bad (beyond that it was GPL).
We don't need to come up with the perfect solution right now. @yingjunwu's just needs a simple worker pool with a configurable number of threads.

Actually, our ultimate goal (if possible) is to schedule concurrent threads at database level (i.e., use thread pool) instead of at OS level. Current implementation (https://github.com/cmu-db/peloton/blob/master/src/backend/common/thread_manager.h) adopts conditional variables and mutex to synchronize threads. However, such synchronization primitives are very expensive when processing OLTP transactions with dozens of cores. While there are many open-source thread pool implementations, after discussed with @jarulraj, we think that boost thread pool might be a good choice. In fact, we have also implemented our own thread pool with advanced synchronization mechanisms applied, but at current stage, we cannot guarantee the efficiency of our implementation, especially compared with industrial-level libraries, such as boost.
btw, please consider removing mutex if possible, as the incurred context switch is extremely costly when processing short-running OLTP transactions.
TBB is a good choice, but I am not sure whether we can use it (any license issue??). Using TBB can make our life much easier as it supports all kinds of concurrent data structures.

@MattPerron you may want to take a look

@jarulraj I have added comments on thread pool implementation.
Let me know if further changes are required. Thanks.

This is an important decision. Let's discuss it at Tuesday's meeting.


adding ProgressMeter iOS library

Project URL
https://github.com/khawajafarooq/ProgressMeter
Description
Following are the changes:

Adding category 'ProgressView' under UI section
Adding ProgressMeter iOS library under ProgressView section

Why it should be included to awesome-ios (optional)
Adding value to progress view with a meter like UI and custom annotations. Everything is enabled for iOS >=9.0 and Swift 4.0. The control supports autolayout.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Hi could you try again so that your pull request only has one commit?
Sent with GitHawk

Hi, just did that. Can you check?


ubuntu19.10 运行后不显示图形界面 version=<IP_ADDRESS>.deb 和 0.2.7.appimage, 无报错信息

Your os

The version of electron-ssr

What's the problem

App log here

I met the same problem as yours, but i use v0.2.7, could you share you've solved the problem?


Provide an example for GrainServices.

No longer relevant as grain services are going to stop being supported.


Move status to header

Description

Short description here *

closes #4342
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Code is clear and sufficiently documented
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

I suppose it's white now when all is good, and red when something's off?

Processing this pull request

Pull request rejected by merge tool. Multiple change entry files found (changelogs/unreleased/4342-status-improvement.yml,changelogs/unreleased/4598-dependabot.yml,changelogs/unreleased/4601-dependabot.yml). This may happen when a change entry was removed from the remote repository due to a reverted change. In that case, make sure the latest changes from origin/master are merged into issue/4342-status-improvement before triggering merge bot.

Processing this pull request

Merged into branches master, iso6 in 7585f0939a5dde21d2be9e2639c6a23df7e900c3


Account Nature Adjustments

Currently the account categories are: Asset,Bank,Liability,Equity,Revenue,Expense, to be added more to make the output financials look more than what it should be in the reality

add:

trade receivables, trade payables
deposit, prepayment
other receivables, payables
interest income

add abbr library to make the list easier and have it in order, this is the code to remove " and () and sort:
Remove quotes and sort the strings
sorted_strings = sorted(sample_strings)
Format them in brackets
result = '[' + ', '.join(sorted_strings) + ']'
Print the result
print(result)

++ othere revenue

deposit -> CA, to be removed in data validation
depreciation(dep) -> may change to expense for manual calculation, if yes, to be removed in data validation


docs: add next.js and pglite in example page

An example where using PGlite with Next.js for local/dev environment. An alternative to Docker, no need to run Docker to run Postgres.

Leverages drizzle's wrapper implementation. Looks legit ❤
https://github.com/ixartz/Next-js-Boilerplate/commit/1d725e8d280e1848e792aba7c8102371b3c038a8

Hey @samwillis
Thank you for getting back to me. I understand.
Should I create a new link for external projects and example? Do you have any idea about the name of the page? The appropriate name?


Complement function on Rangetools trait

Rangetools should have a .complement() function that returns the set complement of the range.

Added in 0.1.2 (with the RangeComplement trait).


Add warning in modules doc

Refers to #1578

Is this for next or should we backport?

@clayton-cornell it's relevant for all versions of Alloy (not the agent)


Update Django initial files for the setup

Merge remote-tracking branch 'origin/main' just comes from pycharm but it does not change anything (maybe) if changes so decline this request :)

Good work Nunthapop.

wdad


aspects will only have name now, so remove validation which tests for…

… presence of timeout attr

Coverage decreased (-0.005%) to 98.964% when pulling 61b9cef8c6d39924cb1991bc0c880a94dd6e18ef on aspect-validation into 4086e7843204bc65666f9af5ad9a8318db806fa0 on master.


config: Link platform:"…" JSON tags with protocol platform slugs

Spun off from here.
  The
meat is the one-liner in the last commit, and the bit I'm not sure
about (also discussed in the commit message ;) is whether we want to
rename the JSON tag from platform:"…" to protocol:"…" to
consolidate around the “protocol” term used in #527 to decouple
compliance from platforms.  For example, if we want to add
optional extensions (e.g. allowing Linux containers that use
namespacing but not cgroups), we could have a ‘linux’ protocol (with
the base stuff) and a ‘linux-cgroups’ protocol (with the cgroups stuff
and the base stuff).  Runtimes that implemented both would be
compliant with both ‘linux’ and ‘linux-cgroups’.

@wking Please break-out into separate PRs

I pushed the header normalization out into #650 and rebased the remaining two commits onto master with eb82bad → c987b8f, so this is now focused exclusively on slugging protocols and defining the Go binding's platform tag.

@wking Could your update and rebase since this PR has a v1.0.0 milestone, thanks.

On Wed, Feb 08, 2017 at 12:37:06AM -0800, Qiang Huang wrote:

@wking Could your update and rebase since this PR has a v1.0.0
milestone, thanks.

Rebased with “protocol” → “platform” (although I still think that's
unnecessarily restricting future platform/protocol choices 1) in
a78a538 → 4af0c72.  Despite that change, I think 4af0c72 is still a
step mostly-forward because it defines the semantics of the JSON tags.

LGTM

LGTM


try rbenv

This does not seem to work.
ruby-head is from http://rubies.travis-ci.org/.
It would seem it's not been updated recently.

I submitted https://github.com/travis-ci/travis-ci/issues/5308

The build is now green: https://travis-ci.org/ruby/rubyspec/builds/97220946


Using Sentry with Elixir Release eval commands

Environment

Elixir version (elixir -v): 1.10.2
Erlang/OTP version (erl): 22
Sentry version (mix deps): 7.2.3
Operating system: ubuntu

Description
Sentry is failing to capture errors that occur in a release task. We are using elixir releases for deployment. Before starting the application we are running a one off script (docs) to run migrations. If the migration throws an error there is no corresponding entry in Sentry.  Once app starts up, errors are logged in Sentry without issue.
Migration script.
bin/release_name eval "MyApp.Release.migrate"

defmodule MyApp.Release do
  @app :my_app

  def migrate do
    Application.ensure_all_started(@app) # This was added to make sure all apps were started
    for repo <- repos() do
      {:ok, _, _} = Ecto.Migrator.with_repo(repo, &Ecto.Migrator.run(&1, :up, all: true))
    end
  end

  def rollback(repo, version) do
    {:ok, _, _} = Ecto.Migrator.with_repo(repo, &Ecto.Migrator.run(&1, :down, to: version))
  end

  defp repos do
    Application.load(@app)
    Application.fetch_env!(@app, :ecto_repos)
  end
end

Expected Behavior
Raised error during migration alerts in Sentry.
Actual Behavior
No alert in Sentry
Steps to Reproduce

Thanks for opening a detailed issue!
I will definitely look into this next week 🙂

I think I found the issue. Sentry can capture crashed processes through Logger, and errors within Phoenix/Plug, but the release task doesn't fall into any of those.
The best way to capture would probably be a try/catch like:
defmodule MyApp.Release do
  def migrate do

    Application.ensure_all_started(@app)
    try do
      for repo <- repos() do
        {:ok, _, _} = Ecto.Migrator.with_repo(repo, &Ecto.Migrator.run(&1, :up, all: true))
      end
    rescue
      my_exception ->
        {:ok, _} =
          Sentry.capture_exception(my_exception, result: :sync, stacktrace: __STACKTRACE__)
    end
  end
end

The result: :sync is important as otherwise it will be asynchronous. If the migration crashes, there's no guarantee the request to Sentry will make it before the whole app goes down.

Thanks @mitchellhenke. I tried the above method and had the same result of no sentry error. For now I'm starting a genserver to run migrations at app startup. I'm not sure what it is about eval that prevents sentry from surfacing the errors, maybe something to do with the task that is firing the request?

Yeah, the other thing I messed with was using a GenServer/Task/spawn to allow Sentry.Logger to receive and send the event.
I tested the above and was able to receive an error in Sentry. Could you share the portions of the script where Sentry is involved? My other hunch was a config issue, but if you're receiving events via other methods, that can't be the case.

Closing for inactivity 🙂

@mitchellhenke Thank you, that worked!
I had to remove the {:ok, _} part, because Sentry.capture_exception might also return {:ignored, _}.
And I used ensure_all_started(:hackney), that seems to be the bare minimum that Sentry needs to send a request.


feat: added chainbound-artemis Client crate

Chainbound x Artemis integration
This PR adds a crate in the crates/clients path which adds the following components:

Fiber Collector: a low-latency mempool & new blocks stream powered by the fiber-rs gRPC client
Echo Executor: a feature-rich RPC option for sending mev bundles to multiple block builders

We implemented the crate following the Artemis core traits. The crate also includes an example usage script plus all the contextual links to help with integration.

opening on upstream


Check with jepsen

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

finish. https://github.com/shihuili1218/klein/pull/45


[Bug] Enable Trigger Happy triggers "button" not working 100%

The quick change button to enable/disable trigger happy triggers does not fire the onChange callback until hooked by opening the settings menu or creating/deleting a journal. trigger happy continues to have the same enableTriggers state setting until a hook is called.  this bug was introduced in v0.8.9
tested with only trigger happy installed.

Thanks for the heads up. It was the result of a merge that I did not adequately review.

Thanks for the quick update, as an additional note, the button seems to only disable the triggers for the GM. players can continue to trigger events in the journal even with triggers disabled. (testing with older versions also shows this is how its always been) is this intended?


Fixes #1004

Adds model "_TZE200_yvx5lh6k" to Tuya Air quality device with GPP

Codecov Report

Merging #1280 (8c8936a) into dev (9a14013) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1280   +/-   ##
=======================================
  Coverage   80.28%   80.28%
=======================================
  Files         207      207
  Lines        5696     5696
=======================================
  Hits         4573     4573
  Misses       1123     1123

Impacted Files
Coverage Δ

zhaquirks/tuya/air/ts0601_air_quality.py
100.00% <ø> (ø)

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 9a14013...8c8936a. Read the comment docs.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 80.284%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4573

Relevant Lines:
5696

💛  - Coveralls


Replace third party libraries with npm modules

This issue will serve as a task list for replacing third party modules with npm modules. Here is the task list (incomplete for now; I'll be updating this as we go).

[x] Create staging branch for npm changes - https://github.com/CesiumGS/cesium/tree/npm-third-party-staging
[x] Merge first pass PR into staging (https://github.com/CesiumGS/cesium/pull/9466/)
[ ] Move to npm; or other - see https://github.com/CesiumGS/engineering/issues/69#issue-834201104)

[x] sprintf (https://github.com/CesiumGS/cesium/pull/9476)
[x] bitmap-sdf.js (https://github.com/CesiumGS/cesium/pull/9688)
[ ] google-earth-dbroot-parser.js
[x] graphmesplitter.js (https://github.com/CesiumGS/cesium/pull/9688)
[x] jsep.js (https://github.com/CesiumGS/cesium/pull/9688)
[ ] ~knockout-3.5.1.js, knockout-es5.js, knockout.js~ (need longer term plan to get rid of knockout)
[x] LercDecode.js (https://github.com/CesiumGS/cesium/pull/9688)
[ ] measureText.js
[x] mersenne-twister.js (https://github.com/CesiumGS/cesium/pull/9688)
[x] NoSleep.js (https://github.com/CesiumGS/cesium/pull/9688)
[x] pako_inflate.js (https://github.com/CesiumGS/cesium/pull/9688)
[ ] protobuf-minimal.js
[x] purify.js (https://github.com/CesiumGS/cesium/pull/9688)
[ ] Uri.js
[ ] zip.js (https://github.com/CesiumGS/cesium/pull/9696)

[ ] Other files in Source/ThirdParty:

[ ] GltfPipeline
[ ] basis_transcoder.wasm
[ ] draco_decoder.wasm
[ ] FXAA3_11 in Source/ThirdParty/ Shaders/
[ ] Source/ThirdParty/ Workers/

[ ] compare built CesiumJS sizes
[ ] rename ThirdPartyNpm to ThirdParty
[ ] update CHANGES.md

@ebogo1 https://www.npmjs.com/package/ktx-parse should be added after https://github.com/CesiumGS/cesium/pull/9513 is merged

Just checking, does this task list account for third party libraries in cesium/ThirdParty and cesium/Sandcastle/ThirdParty?

By Cesium/ThirdParty/ do you mean codemirror-5.52.0, dojo-release-1.10.4, jasmine-2.20, and jslint-2.11.0? As for the ones in Sandcastle, I'm not sure what the plan is for those; I had a comment about it in the original post of #9688.

One more late breaking third party library to account for - meshopt. Added in https://github.com/CesiumGS/cesium/pull/9694.
Source/ThirdParty/meshopt_decode.js
Here's the npm library that we should try using instead: https://www.npmjs.com/package/meshoptimizer

Closing, as the original scope of this issue has been covered. Knockout.js, workers, and Sandcastle dependencies  will be a separate effort.


New version: Ipaper v0.1.3

Registering package: Ipaper
Repository: https://github.com/jl-spatial/Ipaper.jl
Created by: @kongdd
Version: v0.1.3
Commit: 7a96d6ca4b906d55deca5a0acd82e97917f0f922
Reviewed by: @kongdd
Reference: https://github.com/jl-spatial/Ipaper.jl/issues/1#issuecomment-1116863002
Description: Collection of functions for R users

[noblock]


Use base branch for the dapper Dockerfile

As in Shipyard, use an argument, so that stable branches consume the correct Shipyard version.
Signed-off-by: Mike Kolesnik<EMAIL_ADDRESS>

Backported as https://github.com/submariner-io/releases/pull/498


Mock storage

Would it make sense to provide a mock Storage that just saves to a StrMap for testing?

Sure - I don't see why not. I'd definitely accept a PR :-)

Do you want tests? Prefer a framework or none?

Tests would be awesome of course! I previously use purescript-assert for testing, but you can use what-ever framework you see fit. Thank you!


Data in oilabs, openintro -- open to some renaming/recoding?

I don't know how married you are to the current names and coding scheme, but I would love to see some changes:

Don't use 0/1 coding for things like male/female, or at least have an additional variable that doesn't use an arbitrary assignment like this.  (Perhaps using male or female as the 0/1 -- or better TRUE/FALSE -- code and sex coded with "male"/"female" or "M"/"F" or something similar.)

Don't skimp on characters.  Make things clearer by using a few more letters.  Examples: bdims -> BodyDims, hgt -> height, etc.

I love using capitalization for data frame names and lower case for variable names, but I realize that that many do not use that convention.  For teaching, I think it is very handy to have data sets clearly distinguished from variables.

Don't mask data sets from other packages -- especially not datasets.  datasts definitely has dibs.  So do other packages that have been on CRAN for a while.

Put data into a separate package from functions.  That makes maintenance easier and makes it easier for people to use your data sets in other contexts without having to put your functions on their search path.

I haven't done a check for consistent naming and coding, but if it is inconsistent, I recommend moving toward consistency unless there is a good reason not to do so.

@rpruim Might I recommend that you create a PR that fixes these issues so that the reviewers of the package can review changes instead of being the ones having to do the work to make these changes? In general, it is helpful for feature requests such as this to be attempted at implementation by the person creating the request instead of just making requests without seeing how challenging it might be to make these changes.
I am not an author of this package but have found this process to be much more beneficial for other packages I have contributed to and it also provides a higher likelihood of implementation in my experience.

@ismayc, I'm not going to invest time in this until I at least get a sense that it is wanted.  Notice the title of the issue -- my first question is whether there is even openness to the making these sorts of changes.  (The answer could vary by the change.)
I also don't have a good sense regarding where all these data sets are in use in the various Open Intro projects.  So I don't think I'm in a good position to do the implementing, or to size up how much work it would be.
As for my R programming time in the near future -- it is mostly committed to maintaining my own packages.  So aside from an exemplar or two, I'm not likely able to commit time to this.

@rpruim Since this isn't my package, I'll let the package authors reply as needed and keep myself out of this. It's clear we have very different styles of how to request changes to open source packages. I've let previous issues just sit unanswered but I thought it important that you see the viewpoints of other package authors today. A further discussion only further floods the inboxes of the package authors and I'd rather not do so as they have plenty to look at already today from all the issues created.

Much of these suggestions are now incorporated in the datasets that are moved from here to the openintro package.


Kubelet loops endlessly looking at run once pods

See this issue https://github.com/openshift/origin/issues/1656
This also causes the API to continually spam open websockets watching /pods.

@smarterclayton

To Dawn to triage.

IIUC, this is a performance optimization, rather than a bug? kubelet watches all pods with Spec.Host set to its node, and does periodical sync in addition to watch updates. It watches those pods, so that it knows that they are still alive (not deleted) and can respond to requests to check pod/container status and logs, etc. Potentially, it could also restart containers if the restart policy is updated to always.

I'm not sure that we should ever allow a pod to transition it's restart policy.  The reason I bring this is up is that I do not see this behavior before the kubelet is restarted.  It looks like on restart the kubelet is handling completed run once pods differently.

On Apr 9, 2015, at 8:44 PM, Yu-Ju Hong<EMAIL_ADDRESS>wrote:
IIUC, this is a performance optimization, rather than a bug? kubelet watches all pods with Spec.Host set to its node, and does periodical sync in addition to watch updates. It watches those pods, so that it knows that they are still alive (not deleted) and can respond to requests to check pod/container status and logs, etc. Potentially, it could also restart containers if the restart policy is updated to always.
—
Reply to this email directly or view it on GitHub.

Did your run once pods succeed or fail? I found a code that'd ignore failed pods even thought it wasn't intentional. In all cases, kubelet still watches all pods assigned to it though.
Agreed that transitioning restart policy may not be good, but we do allow it in the apiserver. We should explicitly disallow it if that's what we wanted.

I don't see where pods can change restart policy.  So at least we know they can't today.
These were successful run once pods.

@smarterclayton, you were right. We cannot update the restart policy. The update validation prevents it. We should the json description to match that.
For successful run once pods, kubelet continues looping on them in my local setup, with or without restart. This seems to be the normal behavior.

Somewhat related to this issue: #7301 filtered out terminated pods in SyncPods so that kubelet doesn't try to sync them, which involves examining dead containers. Kubelet would still watching all pods (including the terminated ones) though.

I think this issue can be closed now.
I did the following:
apiVersion: v1beta3
kind: Pod
metadata:
  name: valid-pod
spec:
  activeDeadlineSeconds: 30
  containers:
  - capabilities: {}
    image: nginx
    name: nginx
    resources:
      limits:
        cpu: "1"
        memory: 512Mi

Waited for the pod to be killed by the kubelet after it ran to completion.
Verified the kubelet killed the container on the minion.
Verified that once the Kubelet changed the status of a pod to terminated that its resource version was stable for the next 10 minutes.  Meaning that Kubelet was properly filtering out terminated status pods, and not constantly updating the status, which previously caused the resource version to appear to chain, which caused spams to our watch clients.
Closing since all is good here now.


Wallbox reboot 4 times a day due to possible memory leak?

Hello,
I have been using this HA integration for some time now. But recently noticed that while using it, the wallbox will reboot 4 times a day.
The log of the wallbox seems to suggest this is due to a memory issue. The reboots stop when I disable this integration.
I've been searching online for possible solutions, but I have only found several other people who report the same issue when using the integration.
I started noticed the reboots since I also started using the EVCC charge manager plugin for the wallbox. And annoyingly the reboots seem to mess up the charge logic of EVCC.
Any idea what could be causing this?
Thanks!
2023-01-29T23:44:20.960Z:RESET:application.c:353:========================================= 2023-01-29T23:44:20.972Z:INFO:application.c:361:build: Aug 15 2022 12:20:52 2023-01-29T23:44:20.980Z:INFO:application.c:362:version: 5.8.1-4123 2023-01-29T23:44:20.988Z:INFO:application.c:363:compiler: gcc 4.8.3 2023-01-29T23:44:20.996Z:INFO:application.c:216:fwu state inactive 2023-01-29T23:44:21.003Z:INFO:application.c:236:Bootloader version 0.1.6 2023-01-29T23:44:21.234Z:USER:taskCANopen.c:224:Persistent configuration retrieved, 243 items 2023-01-29T23:44:21.246Z:INFO:application.c:269:FLASH read protection 0xcc level 2 (permanent) 2023-01-29T23:44:21.269Z:WARNING:bspI2c.c:670:I2C slave not responding #-3 AUXBOARD@0x0028, attempting bus recovery 2023-01-29T23:44:21.285Z:WARNING:bspI2c.c:689:Device AUXBOARD@0x0028 not available 2023-01-29T23:44:21.292Z:USER:application.c:412:Using P1 port 2023-01-29T23:44:21.300Z:INFO:application.c:305:System boot #69, cause Watchdog reset 2023-01-29T23:44:21.308Z:ERROR:bspCrashDump.c:173: -- Crash details recovered.  2023-01-29T23:44:21.316Z:ERROR:bspCrashDump.c:192:Out of memory 2023-01-29T23:44:21.324Z:ERROR:bspCrashDump.c:192:free 3968 bytes,  lowest ever free 3352 bytes 2023-01-29T23:44:21.335Z:ERROR:bspCrashDump.c:192:fragmentation: 108240048.0% 2023-01-29T23:44:21.343Z:ERROR:bspCrashDump.c:192:fragmentation: 4K blocks -3.2% 2023-01-29T23:44:21.351Z:ERROR:bspCrashDump.c:192:# free blocks: 64 2023-01-29T23:44:21.359Z:ERROR:bspCrashDump.c:192:largest free: 6312 bytes 2023-01-29T23:44:21.367Z:ERROR:bspCrashDump.c:192: 2023-01-29T23:44:17.757Z SW Watchdog (fffe7e4e) triggered. 2023-01-29T23:44:21.378Z:ERROR:bspCrashDump.c:192:Missing: Modbus NFC  2023-01-29T23:44:21.382Z:ERROR:bspCrashDump.c:192:determining cpu hog... 2023-01-29T23:44:21.390Z:ERROR:bspCrashDump.c:192:Tmr Svc                  1    <1%  2023-01-29T23:44:21.402Z:ERROR:bspCrashDump.c:192:display              25155    97%  2023-01-29T23:44:21.410Z:ERROR:bspCrashDump.c:192:lwip                     0    <1%  2023-01-29T23:44:21.417Z:ERROR:bspCrashDump.c:192:WebClients               0    <1%  2023-01-29T23:44:21.425Z:ERROR:bspCrashDump.c:192:NFC                      0    <1%  2023-01-29T23:44:21.433Z:ERROR:bspCrashDump.c:192:Modbus                   0    <1%  2023-01-29T23:44:21.445Z:ERROR:bspCrashDump.c:192:PPP                      0    <1%  2023-01-29T23:44:21.453Z:ERROR:bspCrashDump.c:192:OCPP                     0    <1%  2023-01-29T23:44:21.460Z:ERROR:bspCrashDump.c:192:WebServer                0    <1%  2023-01-29T23:44:21.468Z:ERROR:bspCrashDump.c:192:CommandLine              0    <1%  2023-01-29T23:44:21.476Z:ERROR:bspCrashDump.c:192:IDLE                     0    <1%  2023-01-29T23:44:21.484Z:ERROR:bspCrashDump.c:192:Eth_if                   5    <1%  2023-01-29T23:44:21.496Z:ERROR:bspCrashDump.c:192:Modem                    2    <1%  2023-01-29T23:44:21.503Z:ERROR:bspCrashDump.c:192:ModbusTCPIPSlav          0    <1%  2023-01-29T23:44:21.511Z:ERROR:bspCrashDump.c:192:P1Meter                  2    <1%  2023-01-29T23:44:21.519Z:ERROR:bspCrashDump.c:192:CANopen                427    1%  2023-01-29T23:44:21.527Z:ERROR:bspCrashDump.c:192:ModbusTCPIPMast          0    <1%  2023-01-29T23:44:21.539Z:ERROR:bspCrashDump.c:192:Main                     0    <1%  2023-01-29T23:44:21.546Z:ERROR:bspCrashDump.c:192:TCP/IP                   0    <1%  2023-01-29T23:44:21.554Z:ERROR:bspCrashDump.c:192:Master                   0    <1%  2023-01-29T23:44:21.562Z:ERROR:bspCrashDump.c:197: -- End of crash details 2023-01-29T23:44:21.570Z:INFO:board_ng9xx.c:1475:Registered timeout getHardware 2023-01-29T23:44:21.593Z:WARNING:bspI2c.c:670:I2C slave not responding #-3 MMA8451@0x000d, attempting bus recovery 2023-01-29T23:44:21.609Z:WARNING:bspI2c.c:689:Device MMA8451@0x000d not available 2023-01-29T23:44:21.628Z:WARNING:bspI2c.c:670:I2C slave not responding #-3 BMA456Q@0x0000, attempting bus recovery 2023-01-29T23:44:21.644Z:WARNING:bspI2c.c:689:Device BMA456Q@0x0000 not available

I have the exact same issue, in my case the reboot happens each approx 2M seconds. Disabling the device in homeassistant solves the issue as well.

Same experience, seems to be a device issue unfortunately. Once over 2Ms the device reboots within 10 minutes of restarting the integration

I noticed the same behaviour. After some testing it seems like the wallbox is rebooting due to too many log file entries.. the logs quickly grow as there will be 3 log entries each time data is read or sent to the wallbox:

login request
Read or write data
Logout

ideally, these requests are not logged. Unfortunately I did not find a way to achieve this.

In Alfen.py if you increase
"MIN_TIME_BETWEEN_UPDATES = timedelta(seconds=120)"
It will extend the time between reboots but the longer update may not be suitable for some.
Also In the same yaml change the formula to
"self.uptime = max(0, prop['value'] / 1000000 / 3.565) "
To give the approx time in hours since last reboot

Since the service "Alfen Wallbox: reboot_wallbox" is available, an automated maintenance reboot might be a possible workaround, right?

It does work.ive just tested.
There will be a sweet spot between the refresh time and a reboot every 24hrs, though I guess you could reboot as often as you'd like.
I've not seen anyone on the v6 FW to see if alfen have actually resolved this issue either

It does work.ive just tested. There will be a sweet spot between the refresh time and a reboot every 24hrs, though I guess you could reboot as often as you'd like.
I've not seen anyone on the v6 FW to see if alfen have actually resolved this issue either

My Alfen is on >v6 FW and still crashes every 8 hours.

I don't see how a reboot due to a crash or a clean reboot on command should make a difference when solar charging with help from EVCC. Especially when switched to 1 phase charging due to not enough available surplus PV.

Strange that you have a reboot every 8 hours.
How long does a charge with evcc take? If a normal charge is less then 8 hours, a forced reboot can help you if you initiate this reboot before you start charging, or not?

I think the memory leak is linked to the logs created when using HA integrations to read the info. So extending the time as I suggested means fewer logs are generated so it takes longer to crash.
I'm not savy enough to know why the connection needs to be dropped and re-established so often or how this integration works under the bonnet.

Strange that you have a reboot every 8 hours. How long does a charge with evcc take? If a normal charge is less then 8 hours, a forced reboot can help you if you initiate this reboot before you start charging, or not?

As noted in the OP my wallbox seems to reboot 4 times a day. So one reboot every 8 hours.

The charge time with evcc depends on several things: 1. The amount of PV power available. When trying to only use PV surplus power and with the current sun hours in the Netherlands it can easily take more than 8 hours. 😑
2. My second EV (Opel Ampera-E) will only charge on 1 phase. And due to the usual power limitations in the Netherlands of 3x25a mains power. Which means a 20a breaker on the wallbox. A charge time of more than 8 hours also is a regular thing.
I'm going to try the suggestions of gizmoy2k as a workaround in the mean time. But I'm still hopefull a permanent solution is also possible.

Well with
MIN_TIME_BETWEEN_UPDATES = timedelta(seconds=300)
the reboots have stopped.
Currently at 83 hours uptime. I guess 300s is long enough not to overwork the log or there is a purge of some kind.
I still don't have my EV so not sure how practical 300s update time is when it comes to HA or any automations you may want to run

MIN_TIME_BETWEEN_UPDATES = timedelta(seconds=300)

Thanks for sharing this! I have changed this as well now, I'll report back with the results.

Thanks for sharing! I also changed this setting and had another reboot in 2 days :(

Hey guys, interesting use of the REST API. It was never meant for automation, but if it works... :-)
I'm willing to take a look at the issue. Based on the comments above it seems to be related to the time between requesting a bunch of properties from the REST API with GET requests. Sounds like a memory leak somewhere in the charger firware. If anyone has a week long log file with one or more reboots it would help in finding the issue. Log file can be downloaded using the ACE Service Installer. Probably using MyEve as well, but I'm not 100% sure.

I'm on holiday just now but when I return I can turn the time back down and send you the logs no problem.
107 hours is my best without a reboot so far

Hey guys, interesting use of the REST API. It was never meant for automation, but if it works... :-) I'm willing to take a look at the issue. Based on the comments above it seems to be related to the time between requesting a bunch of properties from the REST API with GET requests. Sounds like a memory leak somewhere in the charger firware. If anyone has a week long log file with one or more reboots it would help in finding the issue. Log file can be downloaded using the ACE Service Installer. Probably using MyEve as well, but I'm not 100% sure.

Here is a log file with 4 reboots
Line  3579: 2023-06-17T17:26:19.558Z:INFO:application.c:305:System boot #132, cause Watchdog reset
Line 18158: 2023-06-18T14:06:58.386Z:INFO:application.c:305:System boot #133, cause Watchdog reset
Line 43619: 2023-06-19T11:27:05.613Z:INFO:application.c:305:System boot #134, cause Watchdog reset
Line 47195: 2023-06-19T18:55:07.253Z:INFO:application.c:305:System boot #135, cause Watchdog reset
If there is a dump it is as follows
2023-06-17T17:26:19.558Z:INFO:application.c:305:System boot #132, cause Watchdog reset
2023-06-17T17:26:19.566Z:ERROR:bspCrashDump.c:173: -- Crash details recovered.
2023-06-17T17:26:19.578Z:ERROR:bspCrashDump.c:192:Out of memory
When the integration is running repetative entries of the following occur, I think this is linked to the crash
My timedelta is set to 60 seconds just now which ties up with the login:
2023-06-18T14:40:12.363Z:SE
Alfen Log.txt
CURITY:httpd_login.c:154:WebClient - connected (account: admin)
2023-06-18T14:40:27.527Z:WARNING:taskWebClient.c:223:Client (fd=2) disconnected (r: -0x7880)
2023-06-18T14:40:27.535Z:INFO:taskWebClient.c:155:Removing previously connected client
2023-06-18T14:41:12.417Z:SECURITY:httpd_login.c:154:WebClient - connected (account: admin)
2023-06-18T14:41:43.519Z:WARNING:taskWebClient.c:223:Client (fd=2) disconnected (r: -0x7880)
2023-06-18T14:41:43.527Z:INFO:taskWebClient.c:155:Removing previously connected client
Alfen Log.txt

Hey guys, interesting use of the REST API. It was never meant for automation, but if it works... :-) I'm willing to take a look at the issue. Based on the comments above it seems to be related to the time between requesting a bunch of properties from the REST API with GET requests. Sounds like a memory leak somewhere in the charger firware. If anyone has a week long log file with one or more reboots it would help in finding the issue. Log file can be downloaded using the ACE Service Installer. Probably using MyEve as well, but I'm not 100% sure.

Here is a log file with 4 reboots Line 3579: 2023-06-17T17:26:19.558Z:INFO:application.c:305:System boot #132, cause Watchdog reset Line 18158: 2023-06-18T14:06:58.386Z:INFO:application.c:305:System boot #133, cause Watchdog reset Line 43619: 2023-06-19T11:27:05.613Z:INFO:application.c:305:System boot #134, cause Watchdog reset Line 47195: 2023-06-19T18:55:07.253Z:INFO:application.c:305:System boot #135, cause Watchdog reset
If there is a dump it is as follows 2023-06-17T17:26:19.558Z:INFO:application.c:305:System boot #132, cause Watchdog reset 2023-06-17T17:26:19.566Z:ERROR:bspCrashDump.c:173: -- Crash details recovered. 2023-06-17T17:26:19.578Z:ERROR:bspCrashDump.c:192:Out of memory
When the integration is running repetative entries of the following occur, I think this is linked to the crash
My timedelta is set to 60 seconds just now which ties up with the login:
2023-06-18T14:40:12.363Z:SECURITY:httpd_login.c:154:WebClient - connected (account: admin) 2023-06-18T14:40:27.527Z:WARNING:taskWebClient.c:223:Client (fd=2) disconnected (r: -0x7880) 2023-06-18T14:40:27.535Z:INFO:taskWebClient.c:155:Removing previously connected client 2023-06-18T14:41:12.417Z:SECURITY:httpd_login.c:154:WebClient - connected (account: admin) 2023-06-18T14:41:43.519Z:WARNING:taskWebClient.c:223:Client (fd=2) disconnected (r: -0x7880) 2023-06-18T14:41:43.527Z:INFO:taskWebClient.c:155:Removing previously connected client
Alfen Log.txt
The mobile connection is poor in my area so the log is littered with the modem resetting trying to get a connection I cant work out how to get it connected to back office via a hardwired connection, if thats even possible

Hi, thanks for the information. Clearly some kind of memory leak. What I would like to see is if the out-of-memory issue occurs much less frequent if you change the REST API connection interval to a higher value such as 300 seconds, like @gizmoy2k did. If you can confirm that this stops/delays the out of memory issue, then we can try to internally reproduce this and look for a fix.
As for connection your station wired, as long as the back office is in your control or if the back office is accessible via Wired, then you can configure via the ACE Service Installer to have the station connect via Wired using the Connectivity tab.

Hi, thanks for the information. Clearly some kind of memory leak. What I would like to see is if the out-of-memory issue occurs much less frequent if you change the REST API connection interval to a higher value such as 300 seconds, like @gizmoy2k did. If you can confirm that this stops/delays the out of memory issue, then we can try to internally reproduce this and look for a fix.

Hi, I can confirm. If the connection interval increases to 300sec, the reboot occurs each 40M seconds approx. Currently I have it set to 30 seconds ( using this fork: https://github.com/leeyuentuen/alfen_wallbox ), and with this I have a reboot each 1.5-1.8M seconds. System Boot Reason: "Watchdog reset"

Hi, thanks for the information. Clearly some kind of memory leak. What I would like to see is if the out-of-memory issue occurs much less frequent if you change the REST API connection interval to a higher value such as 300 seconds, like @gizmoy2k did. If you can confirm that this stops/delays the out of memory issue, then we can try to internally reproduce this and look for a fix.

Hi, I can confirm. If the connection interval increases to 300sec, the reboot occurs each 40M seconds approx. Currently I have it set to 30 seconds ( using this fork: https://github.com/leeyuentuen/alfen_wallbox ), and with this I have a reboot each 1.5-1.8M seconds. System Boot Reason: "Watchdog reset"

I've had a local setup with 6.3.0 spamming logins/connections every 10 seconds for a while, but the memory statistics show no issues whatsoever (free memory remains stable). What actions are being done every time you connect to the wallbox? Are any settings being GET'd/POST'd? Then I can try to add that to my local setup.

Hi, thanks for the information. Clearly some kind of memory leak. What I would like to see is if the out-of-memory issue occurs much less frequent if you change the REST API connection interval to a higher value such as 300 seconds, like @gizmoy2k did. If you can confirm that this stops/delays the out of memory issue, then we can try to internally reproduce this and look for a fix.

Hi, I can confirm. If the connection interval increases to 300sec, the reboot occurs each 40M seconds approx. Currently I have it set to 30 seconds ( using this fork: https://github.com/leeyuentuen/alfen_wallbox ), and with this I have a reboot each 1.5-1.8M seconds. System Boot Reason: "Watchdog reset"
increase the interval,  will the value then not updated every 300 sec? so the data is about 300 sec old?

increase the interval, will the value then not updated every 300 sec? so the data is about 300 sec old?
Yes, but it's just for a test to see if the memory leak is directly related to REST API, which it seems to be seeing all the responses.

On my branch, you have every x time the following URLs:
* authentication (api/login)

* get data (32 id's): /api/prop?ids=2060_0,.....

* get the rest of the data: /api/prop?ids=2060_0,.....

* logout (api/logout)

I think you can get an overflow if you try to connect and another device is also trying to connect them. I think there is a limited of simultaneous API call to that device.

Device allows only 1 connection at a time. I verified just now that connecting a 2nd client will result in a connect/read time-out, so no overflow there.
Thanks for the API calls, I took the specifics from https://github.com/leeyuentuen/alfen_wallbox/blob/master/custom_components/alfen_wallbox/alfen.py#L74C18-L74C18 and added them into my local script. However I'm not sure what some of them are supposed to be doing, because 2070_2 does not map to any property (2070 is an unsigned 8, it has no sub-properties). Regardless of that, I've been running it and (sadly?) still don't see any issues with memory.
When changing the update interval in your tooling, does it only change the REST API call frequency or also something related to Modbus TCP/IP or literally anything else?
To be clear, I'm using the following minimal script to try to reproduce right now:
import requests
from urllib3.exceptions import InsecureRequestWarning
import time

station_ip = '<IP_ADDRESS>'
prop_string1 = '2060_0,2056_0,2221_3,2221_4,2221_5,2221_A,2221_B,2221_C,2221_16,2201_0,2501_2,2221_22,2129_0,2126_0,2068_0,2069_0,2062_0,2064_0,212B_0,212D_0,2185_0,2053_0,2067_0,212F_1,212F_2,212F_3,2100_0,2101_0,2102_0,2104_0,2105_0'
prop_string2 = '2057_0,2112_0,2071_1,2071_2,2072_1,2073_1,2074_1,2075_1,2076_0,2078_1,2078_2,2079_1,207A_1,207B_1,207C_1,207D_1,207E_1,207F_1,2080_1,2081_0,2082_0,2110_0,3280_1,3280_2,3280_3,3280_4'
timeout_s = 10
password = '<removed>'

def main():
    # Don't worry about any TLS errors for this script
    requests.packages.urllib3.disable_warnings(category=InsecureRequestWarning)

    try:
        while True:
            # Create persistent session so we are authorized upon each request following login
            with requests.Session() as persistent_session:
                try:
                    # Login
                    print('Sending login request...')
                    response = persistent_session.post(url='https://{}/api/login'.format(station_ip), json={'username':'admin', 'password':'{}'.format(password)}, verify=False, timeout=timeout_s)
                    print('Received response {}'.format(response))

                    # GET some properties
                    print('Getting properties..')
                    response = persistent_session.get(url='https://{}/api/prop?ids={}'.format(station_ip, prop_string1), verify=False, timeout=timeout_s)
                    print('Received response {}'.format(response))

                    # GET more properties
                    print('Getting more properties..')
                    response = persistent_session.get(url='https://{}/api/prop?ids={}'.format(station_ip, prop_string2), verify=False, timeout=timeout_s)
                    print('Received response {}'.format(response))

                    # Logout
                    print('Sending logout request...')
                    response = persistent_session.post(url='https://{}/api/logout'.format(station_ip), json={}, verify=False, timeout=timeout_s)
                    print('Received response {}'.format(response))
                except requests.exceptions.ReadTimeout:
                    print('Failed to connect/read..')
                    pass # Just try again later

            # Sleep until next attempt
            time.sleep(10.0)
    except KeyboardInterrupt:
        pass

if __name__ == '__main__':
    main()

2070_2 is suppose the date time from the device, but I didn't mapped them yet because I need to parse that date serial to an readable format.
but this should be not the issue, you can fetch more id's and you don't need to process them.

I think it should be better to look at the log of the device

https://{}/api/log?offset=1

replace the 1 with the page that you want to get.
i think maybe there we can find the reason why the watchdog is rebooting

2070_2 is suppose the date time from the device, but I didn't mapped them yet because I need to parse that date serial to an readable format.
but this should be not the issue, you can fetch more id's and you don't need to process them.

Nope, that should be 2059 (sysDateTime).

i think maybe there we can find the reason why the watchdog is rebooting

I already checked the provided logging, and it shows an out of memory error. That's why I'm trying to investigate that, since it seems to be the cause of the watchdog.

this morning, i've remove the mdns that redmer give. Just now running, don't know the result yet

Ok, not the right place to discuss maybe, but since the thread discussing the reboots is already here. The results below are with the release of https://github.com/leeyuentuen/alfen_wallbox
Is this maybe related, look at screenshot,

earlier release 30sec interval: each 1.7M sec a reboot
earlier release 60sec interval: reboot after 2.5M sec
latest release 30sec interval: reboot after 6.5M sec
I never had a better result!

I'll keep an eye on it

this morning, i've remove the mdns that redmer give. Just now running, don't know the result yet

Ok, not the right place to discuss maybe, but since the thread discussing the reboots is already here. The results below are with the release of https://github.com/leeyuentuen/alfen_wallbox
Is this maybe related, look at screenshot:

earlier release 30sec interval: each 1.7M sec a reboot
earlier release 60sec interval: reboot after 2.5M sec
latest release 30sec interval: reboot after 6.5M sec
I never had a better result!

I'll keep an eye on it

i'm still testing, but there is a 'dev' beta version where I'm rewriting them.
There are a  lot of changes, still testing, could be some issue on it. For stable version, keep using master branch
Also adding controls:

Great Work I just installed via HACS after previously manually installing and had to manually edit const.py to re-add my model, NG910-60577, which is not included by default.
Could this be written so that it asks the user what the model is or more models added to the list ?
All models listed in section 5, page 24 here https://www.free-instruction-manuals.com/pdf/pa_2988006.pdf
Thanks Again

I've added a list of missing models

Hi guys, unfortunately I haven't checked GitHub for a while but I'm glad that you found the issue. Thanks for the fix!


Fix borders around title and download button

For some reason, the borders around the title and download button cover the screen's width. Not sure why this is but when I tried to fix it, I wasn't able to do so without also breaking the centering. Will need to research the fix for this

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Fixed.
I had to incorporate display: flex; in a separate div container and use width: fit-content; for the border in CSS to be able to make it work


Change focal point on Live Preview is not affected

Is there any way to view the focal point in the Live Preview without saving?

Sorry that I didn't respond to the comment sooner, I'll look into it when I have the time. Thanks for the issue, it's a good point :)

It should be fixed now with the 1.0.6 release :)


playwright: init at 1.13.1

Motivation for this change
WIP
For now, only chromium is on the derivation, but I'd like to add firefox and webkit.
I'm not sure if that's is the right approach to create a playwright package, opening this PR to get feedback
I took some inspiration from https://github.com/ludios/nixos-playwright
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

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

[ ] Fits CONTRIBUTING.md.

Any progress on this?

@bbigras no, I don't have plans to work on it. If anyone wants to continue working on it, feel free to do it, I hope this PR can be used as a starting point

Closing in favor of #184511


Commented out unneccessary sections

Just commented out unused sections in Resume (Experience section) and removed sample text from 'joining college'
Closes #1

Hey @Ranger-NF,
Thanks for taking time to contribute to my personal portfolio. Your pull request has been merged.
Thanks
Rohan


Request: Support toggles prerequisites

Support pre-request toggles in GUI setting, and SDKs.

Finished in #187


particl-core: <IP_ADDRESS> -> <IP_ADDRESS>

Motivation for this change
Version bump
Things done

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

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

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

@grahamcofborg build particl-core

Success on x86_64-darwin (full log)
Attempted: particl-core
Partial log (click to expand)
 /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/mkdir -p '/nix/store/32q5a09si2ybxgjq7bps40hjcxlmyx9v-particl-core-<IP_ADDRESS>/lib/pkgconfig'
 /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/install -c -m 644 libparticlconsensus.pc '/nix/store/32q5a09si2ybxgjq7bps40hjcxlmyx9v-particl-core-<IP_ADDRESS>/lib/pkgconfig'
make[2]: Leaving directory '/private/tmp/nix-build-particl-core-<IP_ADDRESS>.drv-0/particl-core-<IP_ADDRESS>'
make[1]: Leaving directory '/private/tmp/nix-build-particl-core-<IP_ADDRESS>.drv-0/particl-core-<IP_ADDRESS>'
post-installation fixup
gzipping man pages under /nix/store/32q5a09si2ybxgjq7bps40hjcxlmyx9v-particl-core-<IP_ADDRESS>/share/man/
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/32q5a09si2ybxgjq7bps40hjcxlmyx9v-particl-core-<IP_ADDRESS>/lib  /nix/store/32q5a09si2ybxgjq7bps40hjcxlmyx9v-particl-core-<IP_ADDRESS>/bin
patching script interpreter paths in /nix/store/32q5a09si2ybxgjq7bps40hjcxlmyx9v-particl-core-<IP_ADDRESS>
/nix/store/32q5a09si2ybxgjq7bps40hjcxlmyx9v-particl-core-<IP_ADDRESS>

Success on x86_64-linux (full log)
Attempted: particl-core
Partial log (click to expand)
shrinking /nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>/bin/particld
shrinking /nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>/bin/bench_particl
shrinking /nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>/bin/particl-tx
shrinking /nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>/lib/libparticlconsensus.so.0.0.0
gzipping man pages under /nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>/lib  /nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>/bin
patching script interpreter paths in /nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>
checking for references to /build in /nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>...
/nix/store/hgz6vhs1had76rw1jgcj7v4s5adlqnms-particl-core-<IP_ADDRESS>

Failure on aarch64-linux (full log)
Attempted: particl-core
Partial log (click to expand)
  CXX      zmq/libparticl_zmq_a-zmqabstractnotifier.o
  CXX      zmq/libparticl_zmq_a-zmqnotificationinterface.o
  CXX      zmq/libparticl_zmq_a-zmqpublishnotifier.o
  AR       libparticl_zmq.a
  CXX      libparticl_consensus_a-arith_uint256.o
  CXX      consensus/libparticl_consensus_a-merkle.o
  CXX      libparticl_consensus_a-hash.o
  CXX      primitives/libparticl_consensus_a-block.o
building of '/nix/store/06w83lrj5dv26dc0kfahl8a18l2w17wk-particl-core-<IP_ADDRESS>.drv' timed out after 3600 seconds
error: build of '/nix/store/06w83lrj5dv26dc0kfahl8a18l2w17wk-particl-core-<IP_ADDRESS>.drv' failed


Content doesn't retain text formatting (Ulteura uregentooo !!!)

Added command "cat" with :
  /\_/\  (
 ( ^.^ ) _)
   \"/  (
 ( | | )
(__d b__)

and got this

Same with MarkDown : only Bold and Italic are saved. Newlines and list are not rendered

It's now fixed #10 (replace old add by a modal)


WIP: Outline for some points to be added to spec 1 description.

Add yourself as an author, since you are a co-author and we need to test that multiple authors work.

Add yourself as an author, since you are a co-author and we need to test that multiple authors work.

6c21aa5 experiments with using mermaid to generate charts to better visualize the minimum supported versions (a gantt chart in this case, which is not ideal but provides a basic demonstration).
Note that this PR depends on scientific-python/scientific-python.org#23 - that would have to be merged before the CI here will be able to render the chart.

6c21aa5 experiments with using mermaid to generate charts to better visualize the minimum supported versions (a gantt chart in this case, which is not ideal but provides a basic demonstration).
Note that this PR depends on scientific-python/scientific-python.org#23 - that would have to be merged before the CI here will be able to render the chart.


tenders, FreeBSD, tap: Ignore "up" variable to avoid compiler warning

The unused-but-set-variable warning was emitted for the variable "up", which is
not used on FreeBSD. To keep the code simple (not introducing further ifdefs),
just ignore it via an empty conditional. Fixes #519.

Thanks!


Replace 'read_sql' with 'read_sql_query'.

Fix the error caused by 'read_sql' in PostgreSQL -> Use 'read_sql_query' instead.
'read_sql' is a convenience wrapper around read_sql_table and read_sql_query.
In PostgreSQL, using read_sql can lead to an sqlalchemy.exc.DBAPIError. I think the driver of PostgreSQL might have compatibility issues with 'read_sql'.

@ddkang Could you please review this PR first?


Networking Demo

What does this refer to?
Now that the networking implementation is underway, some demos showing this feature off would be nice. The packeting system is a bit confusing at a glance.
What's wrong with it?
There are no current examples, demos, or documentation revolving the feature.
How can it be improved?
A simple server-client demo would be perfect. Even something simple like an echo server example would be more than enough to get people started.

Currently, a demo cannot be implemented until a client-side implementation is ready. As it stands, only the server-side is finished.


Destroy functionality broken when torrent running

It seems that destroying the torrent doesn't stop the DHT events from being emitted, resulting in actions on a destroyed torrent and an error thrown.
Running torrent.destroy() on a running torrent may cause the following error:
  if (self.destroyed) throw new Error('torrent is destroyed')
                      ^

Error: torrent is destroyed
    at Torrent.addPeer (/app/node_modules/webtorrent/lib/torrent.js:453:29)
    at emitOne (events.js:77:13)
    at Discovery.emit (events.js:169:7)
    at DHT.onPeer (/app/node_modules/torrent-discovery/index.js:66:10)
    at emitThree (events.js:102:20)
    at DHT.emit (events.js:175:7)
    at emit (/app/node_modules/bittorrent-dht/client.js:316:12)
    at onreply (/app/node_modules/bittorrent-dht/client.js:322:27)
    at onreply (/app/node_modules/bittorrent-dht/client.js:532:12)
    at Object.afterQuery [as callback] (/app/node_modules/k-rpc/index.js:272:18)
    at Socket.onmessage (/app/node_modules/k-rpc-socket/index.js:101:11)
    at emitTwo (events.js:87:13)
    at Socket.emit (events.js:172:7)
    at UDP.onMessage (dgram.js:480:8)

Thanks for the issue. I think I figured out the source of the error. It's the new version of bittorrent-dht. It was completely rewritten to be much faster, but there's going to be a few kinks like this until it gets some more usage ;)
PR sent upstream.

And just like that, it's fixed! Re-install webtorrent to get the fix.

Awesome, thanks!
On Thu, 28 Jan 2016 at 04:01, Feross Aboukhadijeh<EMAIL_ADDRESS>wrote:

Closed #589 https://github.com/feross/webtorrent/issues/589.
—
Reply to this email directly or view it on GitHub
https://github.com/feross/webtorrent/issues/589#event-529009360.


Nightly is borked

As a regular user of every nightly:
Image: https://cdn.discordapp.com/attachments/535790601308733460/553732228215996416/unknown.png

Cannot chat, enter just adds newline
Cannot view chats, they change to the other channel but never join
Ignores user's window-layout and shows above every time

I am using the portable functionality.

Same issue here, me in tears

PepeHands
Seems like only way is downgraded to commit ca14a76b

I have updated appveyor to not push new builds to the release until refactor is done, and I have updated the release manually with the working chatterino2.zip file


Ecdr at 25km use cd rv5 ancillary

This PR incorporates updates to the 25km polar stereo processing for use in CDR v05r00

Except for some more changes/updates to attributes in the netCDF files, this codebase is expected to product the data fields we want to publish as CDR v05r00.
The only other thing I plan to do before the next release is remove the NASA Team land spillover algorithm calls.  This includes removing the min_concentration field from the ancillary files.


this->validate() returns previous request on failed validation

Quote from

If validation passes, your code will keep executing normally. However, if validation fails, an Illuminate\Contracts\Validation\ValidationException will be thrown. This exception is automatically caught and a redirect is generated to the user's previous location. The validation errors are even automatically flashed to the session!

This is not the behavior we want.  And I spent 3 hours thinking I had seriously broke something when I kept getting a token back on random POST requests when the issue was that my JSON body was just invalid.

This is useful in the HTML form POST use case not the API server request.
Kristen is correct.

If you read the README, you'll note that I added a comment on this. This behavior occurs only from a browser context. From an AJAX/XmlHtttpRequest context, errors are simply dumped out in a JSON object.

Seeing as we NEVER want the browser context case can't we just disable this behavior altogether?

So what would happen if we had a <form method="POST" action="/api/v1/members"> with invalid data? Just dump the user at a screen with JSON output?
There's really no reason to spend time or effort on disabling a "feature" (I'd argue it's basic functionality) that we will never even touch. Let's focus our efforts elsewhere.
$.02 deposited.

@craigcabrey at least it's less mystifying than silently erroring and would indicate that we need to do something about it. Seeing as we're not hosting the front-end on the api server the redirect is actually misbehaving. If we want to redirect with errors in the GET request I'm okay with that but we shouldn't leave it the way it is because it promotes improper usage.
Looks like the solution is to override the response function in your FormRequest subclass:
https://github.com/laravel/framework/blob/master/src/Illuminate/Foundation/Http/FormRequest.php


Check that all structs/unions in public core headers have named types

I am going to close up grpc/grpc#12095 if you accept this as a sub-PR on grpc/grpc#12059; that way the whole thing can get merged in one piece

Already cherry-picked


Unable to install scikit-sparse

I'm trying to install scikit-sparse in Python 3.9.7 using pip (on a computer with macOS system) and have already installed the prerequisite packages, but still failed with the attached error messages. Do you know what the problem might be and how I can fix it? Thank you very much!
scikit-sparse_output.log

The log shows that you were unable to compile numpy (which for some reason it's building from source).
Do you have a compiler that can build numpy?
Can you verify you have Suite-sparse installed?


Issue#416 search bar in app bar

https://github.com/GlobalDigitalLibraryio/issues/issues/416

Closed in favor of https://github.com/GlobalDigitalLibraryio/gdl-frontend/pull/247


⚠ Bofrost.fr has degraded performance

In b3af861, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1102 ms

Resolved: Bofrost.fr performance has improved in 6d4e5f2 after 9 minutes.


Small fixes

This PR consists of small fixes and implementing RFC style.
Closes #1792.

Nice, thank you!


Explicitly declare the 'exported' attribute in the AndroidManifest for Android 12

Mandatory starting with Android 12:
https://developer.android.com/about/versions/12/behavior-changes-12#exported
'If your app targets Android 12 or higher and contains activities, services, or broadcast receivers that use intent filters, you must explicitly declare the android:exported attribute for these app components.'
Fixes runtime warning:
'W PackageManager: Failed to parse /vendor/priv-app/TimeKeep: /vendor/priv-app/TimeKeep/TimeKeep.apk (at Binary XML file line #7): com.sony.timekeep.TimeKeep: Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present'
Set to 'false' as it was the default in Android versions < 12.
Tested building on an A12 AOSP build system and flashing it on a device (MSM8998). It should be fine also with previous Android versions, but I did not test in those cases.

By the way, indenting log snippets and other code-related blocks with four spaces in your commit message makes them much easier to read in plaintext viewers, and automatically turns it into monospace codeblocks on GitHub (in the rendered commit and the PR description generated from it).

Have you tested this? According to https://developer.android.com/about/versions/12/behavior-changes-12#exported "most cases that do not use the LAUNCHER should set this to false", but I wonder if that allows our intent receiver to still receive/subscribe for these actions in the first place - perhaps the system (which delivers broadcasts) is exempt from exported in the way that other apps (such as a homescreen/launcher) would otherwise be unable to start this if set to false.

Yes, I tested it and it's working fine.
The 'exported' attribute is only used to allow or deny other applications to explicitly call the activity/service. From Google documentation
the activity is accessible to any app, and is launchable by its exact class name.
Intents are always received correctly :)

I find the <receiver> documentation more clear on this:

Whether the broadcast receiver can receive messages from non-system sources outside its application

(Emphasis mine)

Interesting, reading that it seems that you are correct. The app is still working fine on my device, probably because the messages are sent by the system, like you said.
Do you think we need to set it to true? I don't think we'll need to receive messages from other applications.

No it was a question, and as already suggested by the guessed self-answer to that question in the same comment this is probably working because these are system broadcasts. Indeed, that link confirms that is the case.
No action needed on your end besides fixing the indentation, see suggestion above.

Unfortunately moving the app to the system partition is not an option

True, I didn't even remember to have this pull request open. The latest commit was added here automatically by github.
Anyway there will be two options starting (probably) with Android 15:

the app is moved back to /system
the app is updated to not use the 'SystemProperties.set()' call

Otherwise, this error does not allow the build to complete:
error: TimeKeep: Specifies both LOCAL_SDK_VERSION (system_34) and LOCAL_PRIVATE_PLATFORM_APIS (true) but should specify only one
Without the 'LOCAL_PRIVATE_PLATFORM_APIS', the error is instead:
TimeKeep.java:68: error: cannot find symbol                 SystemProperties.set(TIMEADJ_PROP, Long.toString(seconds));
For my personal case, moving the app to system is acceptable. Like I said, it was not my intention to include the commit here :)

if you have time please update the app API to remove the need for PRIVATE_PLATFORM_APIS
PS. you should not use the master AOSP code
Thanks
Alin

PS. you should not use the master AOSP code
Thanks Alin

I use the main AOSP branch for testing, restrictions like these are pushed there way before they are included in a stable tag, but they eventually get there. So it's a way to get ready for new Android releases.

Thanks for the explanation.
It makes sense to use "master".
BR
Alin

Without the 'LOCAL_PRIVATE_PLATFORM_APIS', the error is instead: TimeKeep.java:68: error: cannot find symbol SystemProperties.set(TIMEADJ_PROP, Long.toString(seconds));

Looks like it's just using the wrong API to store a vendor property?


image/jpeg: encoding with RGB profile causing lots of image saturation

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.92
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
windows 10
What did you do?
I encoding a JPEG file with RGB profile, some how the encoding result look like not correct, I using gimp and it compress correctly, the output result show a bit darker then the original image.
here the code  from go playground
Original image

After encode

The images diff

What did you expect to see?

What did you see instead?

/cc @nigeltao @fogleman


Problems with Signals and AOT on iOS (Unity 5.5.1p4)

Hi,
I updated Zenject today to the latest version and I had to update all my Commands to Signals, all went well and I was able to run everything successfully in the Editor. But when I tried to run it on iOS I got the following error:

ExecutionEngineException: Attempting to call method 'Zenject.InstanceMethodSignalHandler2[[System.Boolean, mscorlib, Version=<IP_ADDRESS>, Culture=, PublicKeyToken=7cec85d7bea7798e],[BoolSignalHandler, Assembly-CSharp, Version=<IP_ADDRESS>, Culture=, PublicKeyToken=null]]::.ctor' for which no ahead of time (AOT) code was generated.   at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0    at Zenject.DiContainer.InstantiateInternal (System.Type concreteType, Boolean autoInject, Zenject.InjectArgs args) [0x00000] in <filename unknown>:0    at Zenject.TransientProvider+<GetAllInstancesWithInjectSplit>c__Iterator0.MoveNext () [0x00000] in <filename unknown>:0    at Zenject.CachedProvider+<GetAllInstancesWithInjectSplit>c__Iterator0.MoveNext () [0x00000] in <filename unknown>:0    at Zenject.IProviderExtensions.GetAllInstances (IProvider creator, Zenject.InjectContext context, System.Collections.Generic.List1 args) [0x00000] in :0
at Zenject.DiContainer.SafeGetInstances (Zenject.ProviderPair providerPair, Zenject.InjectContext context) [0x00000] in :0
at System.Linq.Enumerable+

I have omitted the full stack trace, because it is very long. So in order to test things out I made a very simple project, so I can isolate the problem. It comes from signals that have parameters and are bound to a Signal Handler.
Here is show I have setup everything.
In my Installer I have:
Container.Bind<SignalManager>().AsSingle();
Container.DeclareSignal<BoolSignal>();
Container.BindSignal<bool, BoolSignal>().To<BoolSignalHandler>( x => x.Run ).AsSingle();

My signal is declared like that:
public class BoolSignal : Signal<bool, BoolSignal> { }

The handler looks like this:
public class BoolSignalHandler  {
	public void Run(bool test) {
		Debug.Log( "Bool: "+test );
	}
}

Any ideas how to fix this or am I doing something wrong?
Signals without any params, works without any problems.

The problem seems to appear, if I use int or bool for parameters, string seems to work fine.

I am having the same problem. Any solution or workaround (besides turning bools/ints into strings) would be welcome.

A somewhat preferable workaround would be to encapsulate your int or bool parameters into a class. Classes work just fine, like strings.

Yeah, that will work.. I also converted my commands into services, subscribed to the Signal, so I don't change my logic. But still it will be cool, to fix this, if possible or just state that there is a problem in the documentation.

Finally had some time this weekend to take a look at this issue.  This code sums up the issue:
public class Foo<T1>
{
    [Preserve]
    public Foo()
    {
        Debug.Log("**** SUCCESS ****");
    }
}

public class Runner : MonoBehaviour
{
    static void _AotWorkaround()
    {
        // We need to uncomment this on AOT platforms for our button to work without errors
        //new Foo<int>();
    }

    public void OnGUI()
    {
        if (GUI.Button(new Rect(100, 100, 500, 100), "Attempt to Create Foo<int>"))
        {
            // Note that we have to use a generic argument here for the AOT issue to occur
            // If we instead do `CreateFoo(typeof(Foo<int>));` then we do not get
            // AOT errors (though I have no idea why)
            CreateFoo<Foo<int>>();

            // This works fine however
            //CreateFoo<Foo<string>>();
        }
    }

    void CreateFoo<T>()
    {
        // This line will fail on AOT platforms unless the above line is uncommented
        typeof(T).GetConstructors()
            .Where(x => x.GetParameters().Length == 0).Single().Invoke(new object[0]);
    }
}

If you create an new scene, add Runner, and then build and run on an IL2CPP platform, then click the button, you get the error.
I spent a bit of time digging into this and so far I haven't really found a workaround, other than must not using struct types.  So for now, I've changed signals to enforce this when on IL2CPP platforms.  So on IL2CPP platforms, you'll get compiler errors now due to generic constraints on the signal classes if you try to use value types.  If anyone has a better idea, I'd be happy to hear it.

You probably know all this, but from what I understand reading the Unity/iOS manuals, this is due to the fact that iOS doesn't do reflection, so Unity has to know what's going to be called a priori. There's no real workaround other than to create a dummy method which references Foo but is never called, like you've done in _AotWorkaround. See https://docs.unity3d.com/Manual/TroubleShootingIPhone.html, and look for "The game crashes with the error message “ExecutionEngineException: Attempting to JIT compile method ‘SometType`1:.ctor ()’ while running with –aot-only.”"

Fixed by #345


Directing index to home page.

Super small PR to attach the index buttons to our home page.

Covered in PR19


Build pipeline

merge master

 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.:x: enema17484 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

merge build-pipeline to master branch


[Feature][Python] Add workflow as code task type spark

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Add python api task type spark. sub task in #6407. we should cover all parameter from UI side and make it suitable for python.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Please assign it to me if no one does this. @zhongjiajie

Please assign it to me if no one does this. @zhongjiajie

Done, looking forward your contribution~


VMWare Logging Regression - vmware:esxlog:crond

I am unaware if this issue has been replicated by support.
SC4S v3.29.0 on OEL(RHEL) 7.9 on Docker and Podman
no PCAP
The issue is not believed to be related to external software.
Data is not lost due to the issue.
systems are 2-8 CPU, 8-32G mem
lastchance is available if needed
There are no customizations for the vmware sourcetypes.
All of the default indexes are created
We noticed last month when we ran the latest image that our vmware logs were misclassified as
index=osnix sourcetype=nix:syslog
Whereas before it was...
index=infraops sourcetype=vmware:esxlog:crond
This appears not to have impacted the other sourcetypes we have seen over the last 24 hours:
vmware:cb:protect
vmware:vgauthsvc.log
vmware-vmsvc-root
vmware-vmtools-root
We first noticed the issue when we were upgrading our sc4s images from v2->v3 a few months ago and believed it was related to 2390 so we downgraded all of our hosts to 2.46.0. We saw that 2390 merged with 2462 and was released with 2465 so we updated last night to the latest rev and the issue still occurred with the cron logs, which is why we wanted to file this report.
Some source data examples of the types of logs which had classifications change are:
- - CROND 22365 - [meta sequenceId="2267788"](syscheck) CMD (/usr/bin/system_check -q)
- - CROND 22366 - [meta sequenceId="2267695"](root) CMD (/usr/lib64/sa/sa1 1 1)
- - CROND 22364 - [meta sequenceId="2267681"](root) CMD (nice -n 19 ionice -c 3 /usr/sbin/logrotate -s /var/lib/logrotate-adm.status /etc/adm/adm_logrotate.conf)
- - CROND 22352 - [meta sequenceId="2271400"](root) MAIL (mailed 62 bytes of output but got status 0x0001
- - crond 2829 - [meta sequenceId="2271458"]sendmail: Cannot open localhost:25
- - CROND 23419 - [meta sequenceId="2369643"](root) CMD (run-parts /etc/cron.hourly)
- - CROND 23420 - [meta sequenceId="2369651"](root) CMD (/usr/bin/diskmonitor)
- - CROND 24630 - [meta sequenceId="2467463"](syscheck) CMD (/usr/bin/system_check -q)
- - CROND 26760 - [meta sequenceId="2658256"](syscheck) CMD (/usr/bin/system_check -q)
- - CROND 27785 - [meta sequenceId="2757280"](root) CMD (nice -n 19 ionice -c 3 /usr/sbin/logrotate -s /var/lib/logrotate-monitors.status /etc/monitors/monitors_logrotate.conf)
- - CROND 27787 - [meta sequenceId="2757391"](root) CMD (nice -n 19 ionice -c 3 /usr/share/ts/bin/asm_logrotate)
- - CROND 27789 - [meta sequenceId="2757393"](root) CMD (nice -n 19 ionice -c 3 /usr/sbin/logrotate -s /var/lib/logrotate-adm.status /etc/adm/adm_logrotate.conf)
- - CROND 27786 - [meta sequenceId="2757622"](root) CMD (nice -n 19 ionice -c 3 /usr/sbin/logrotate -s /var/lib/logrotate-bwafconf.status /etc/bwafconf/bwafconf_logrotate.conf)

To Reproduce
Steps to reproduce the behavior:

Go to /usr/lib/systemd/system/sc4s.service
Change
Environment="SC4S_IMAGE=ghcr.io/splunk/splunk-connect-for-syslog/container2:2.46.0"
to
Environment="SC4S_IMAGE=ghcr.io/splunk/splunk-connect-for-syslog/container3:latest"
Run searches for:
index=osnix sourcetype=nix:syslog
index=infraops sourcetype=vmware:esxlog:crond
Note the break in logs of the vmware:esxlog:crond logs and the new classification as nix:syslog

If it was some other odd sourcetype we could change it in the splunk_metadata.csv file, but we can't do that for nix:syslog as that is a common catchall.
Thanks!
-Tony

Please check this GitHub issue that was raised earlier. Since crond is a very generic program, we removed it earlier and also provided a custom local parser that can be used. Please refer to this comment.