text:
[BUG] Raise errors in models.nn if they can't make in-sample and some cases out-sample predictions

Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[x] Did you write any new necessary tests?
[x] Did you update the CHANGELOG?

Proposed Changes

Closing issues

closes #787

Codecov Report

Merging #813 (2cc0ddd) into master (41fcce4) will decrease coverage by 34.59%.
The diff coverage is 70.00%.

@@             Coverage Diff             @@
##           master     #813       +/-   ##
===========================================
- Coverage   84.05%   49.46%   -34.60%
===========================================
  Files         126      126
  Lines        7220     7236       +16
===========================================
- Hits         6069     3579     -2490
- Misses       1151     3657     +2506

Impacted Files
Coverage Δ

etna/models/nn/deepar.py
82.95% <70.00%> (-17.05%)
:arrow_down:

etna/models/nn/tft.py
71.69% <70.00%> (-28.31%)
:arrow_down:

etna/commands/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

etna/commands/backtest_command.py
0.00% <0.00%> (-97.06%)
:arrow_down:

etna/commands/forecast_command.py
0.00% <0.00%> (-94.88%)
:arrow_down:

etna/commands/__main__.py
0.00% <0.00%> (-87.50%)
:arrow_down:

etna/models/utils.py
14.28% <0.00%> (-85.72%)
:arrow_down:

etna/commands/resolvers.py
0.00% <0.00%> (-80.00%)
:arrow_down:

etna/analysis/outliers/density_outliers.py
22.44% <0.00%> (-75.52%)
:arrow_down:

etna/datasets/datasets_generation.py
27.02% <0.00%> (-72.98%)
:arrow_down:

... and 77 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

source: gharchive/pull-request

repo: tinkoff-ai/etna

license_type: permissive

license_source: github-api


text:
Add mesh and operators for spherical domain

Summary

Add (dimensionless?) spherical domain to mesh.py, independently of the existing Cartesian domain
Add grad and div operators (Finite Volumes) for the spherical domain

Mesh shall be unchanged. Will use if domain is "negative particle" or "positive particle" to determine when spherical operators should be used.

Closed by #142

source: gharchive/issue

repo: tinosulzer/PyBaMM


text:
move all reduces to the end in lazy

This is just an experiment.
I don't like how the reduce LazyOp doesn't specify the actual reduce operation. Neither new_shape nor axis list expresses it fully, but rather depends on what shape the input buffer has.
One idea is to have the arg just be the number of elements that are being reduced and move them to the end, but I'm not sure this is expressive enough for multireduce.

Oh I think this actually might work! The final permute isn't really a permute, it's a reshape of only 1s.

This is also already happening in the Linearizer

repo: tinygrad/tinygrad

license: MIT


text:
fix: start_server不支持windows启动flask的问题

What type of PR is this?
 enhancement
What does this PR do / why do we need it:
The start_server method in tinyms does not support running in the windows environment. It is a huge blow to the friends who use the windows environment to learn tinyms.
We have also seen that tinyms stated in the introduction that it supports the operation of the windows system, but it is a very uncomfortable thing that it cannot be used as one of its features.
Which issue(s) this PR fixes:

Fixes #65
Special notes for your reviewers:

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

在FlaskServer类中，linux_run_server方法中，有一行循环监听信号的代码，我给了一些注释，这个地方是我存疑的地方，希望你们看完谨慎合并

@lyd911 Please take a look, thanks!

authors: CLAassistant Mickls leonwanghui

repo: tinyms-ai/tinyms


text:
GMB Accounts

Multiple Accounts need to be present to implement data pulls through the Google My Business API (#7) for Locations (https://github.com/tipoff/locations/issues/42). This is also mentioned in this issue:

https://github.com/tipoff/locations/issues/50

https://developers.google.com/my-business/reference/rest/v4/accounts
https://support.google.com/business/answer/6085339?ref_topic=6085325

repo: tipoff/laravel-google-api


text:
fix: broken link to matrix example workflow

Why
Because the link was broken, I got 404.
It should be linked to this file → https://github.com/tj-actions/changed-files/blob/main/.github/workflows/matrix-example.yml

@all-contributors please add @KeisukeYamashita for docs

repo: tj-actions/changed-files


text:
[BUG] - Warning: Unexpected input(s) 'extensions',

Is there an existing issue for this?

[X] I have searched the existing issues

Does this issue exist in the latest version?

[X] I'm using the latest release

Describe the bug?
To eslint-changed-files maintainers,
First off, i would like to extend gratitude to the maintainers for creating this amazing workflow to automate the linting process.
This workflow has become a great help to our team to ensure code readability and code quality.
However, we found that there were some breaking changes from @v10 so we updated the package to @v11
after updating the latest v11, we have started to receive a warning that is blocking the github actions in the workflow
please see the following snippet:
14s
##[debug]Evaluating condition for step: 'Run ESLint on changed files'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Run ESLint on changed files
##[debug]Register post job cleanup for action: tj-actions/eslint-changed-files@v[1](https://github.com/fible/fible-app/runs/6603050516?check_suite_focus=true#step:6:1)1
##[debug]Loading inputs
##[debug]Evaluating: github.token
##[debug]Evaluating Index:
##[debug]..Evaluating github:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'token'
##[debug]=> '***'
##[debug]Result: '***'
Warning: Unexpected input(s) 'extensions', valid inputs are ['token', 'all_files', 'config_path', 'ignore_path', 'file_extensions', 'extra_args', 'skip_annotations', 'level', 'reporter', 'filter_mode', 'fail_on_error']
##[debug]Loading env
Run tj-actions/eslint-changed-files@v[11](https://github.com/fible/fible-app/runs/6603050516?check_suite_focus=true#step:6:11)
  with:
    config_path: .eslintrc.json
    extensions: js,jsx
    extra_args: --quiet
    token: ***
    all_files: false
    file_extensions: **/*.ts
  **/*.tsx
  **/*.js
  **/*.jsx

With that said, would there be something missing the configuration that's causing this issue? Thanks for accommodating me.
To Reproduce
This is how the github action is written
name: Run Linter

on:
  pull_request:
    branches:
      - '**'

jobs:
  run-linters:
    name: ESLint
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v1
        with:
          node-version: 12.x
      - name: Install Packages
        run: yarn install
      - name: Run Jest
        run: yarn test
      - name: Run ESLint on changed files
        uses: tj-actions/eslint-changed-files@v11
        with:
          config_path: ".eslintrc.json"
          extensions: "js,jsx"
          extra_args: "--quiet"

What OS are you seeing the problem on?
all
Expected behavior?
We are expecting the linter to run without warnings.
Relevant log output
14s
##[debug]Evaluating condition for step: 'Run ESLint on changed files'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Run ESLint on changed files
##[debug]Register post job cleanup for action: tj-actions/eslint-changed-files@v[1](https://github.com/fible/fible-app/runs/6603050516?check_suite_focus=true#step:6:1)1
##[debug]Loading inputs
##[debug]Evaluating: github.token
##[debug]Evaluating Index:
##[debug]..Evaluating github:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'token'
##[debug]=> '***'
##[debug]Result: '***'
Warning: Unexpected input(s) 'extensions', valid inputs are ['token', 'all_files', 'config_path', 'ignore_path', 'file_extensions', 'extra_args', 'skip_annotations', 'level', 'reporter', 'filter_mode', 'fail_on_error']
##[debug]Loading env
Run tj-actions/eslint-changed-files@v[11](https://github.com/fible/fible-app/runs/6603050516?check_suite_focus=true#step:6:11)
  with:
    config_path: .eslintrc.json
    extensions: js,jsx
    extra_args: --quiet
    token: ***
    all_files: false
    file_extensions: **/*.ts
  **/*.tsx
  **/*.js
  **/*.jsx

Anything else?
No response
Code of Conduct

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

@janzzen-tp I’ve added a Migration Guide to help you resolve the warning. Let me know if you need more information but a high-level description of the warning is the extension input is no longer supported and has now been renamed to file_extensions.

repo: tj-actions/eslint-changed-files


text:
🛑 ci.tjo.space is down

In 73f59a6, ci.tjo.space (https://ci.tjo.space) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ci.tjo.space is back up in abf20e7.

repo: tjo-space/status


text:
🛑 SITE_PIC is down

In 6f5f2f3, SITE_PIC ($SITE_PIC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SITE_PIC is back up in 0204f61.

repo: tjsky/upptime


text:
🛑 SITE_PIC is down

In e393903, SITE_PIC ($SITE_PIC) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SITE_PIC is back up in 834ae77.


text:
inline svg url not working with Franklin because changed by compression

On Franklin server everything just works, but when deploying to gitlab, my background heropatterns (svg images inlined into background-image: url(...)) just don't show up.
Inspecting the issue it turns out that something in the pipeline deleted the surrounding quotes. Unbelievable...
So on my local system I have
background-image: url("data:image/svg+xml,...");

which somehow ends up on gitlab pages as
background-image: url(data:image/svg+xml,...);

no surrounding quotes any longer.
Any help is highly appreciated, as this seems to be due to the standard Franklin gitlab pipeline.

Turning off minify fixed this issue as well.
See https://github.com/tlienart/Franklin.jl/issues/921#issuecomment-962938930
I would vote for turning off minify by default for everyone.

yes so as per other issue, minification will be turned off for everyone (prerendering as well btw even though it causes much fewer issues)

authors: schlichtanders tlienart


text:
Compilation warning about Kotlin's AnnotationTarget enum

The following warning occurs when compiling with basic-annotations in compileOnly scope:
warning: unknown enum constant AnnotationTarget.ANNOTATION_CLASS
  reason: class file for kotlin.annotation.AnnotationTarget not found

This happens e.g. when compiling sample-java-api subproject: https://travis-ci.com/tlinkowski/basic-annotations/builds/123617322#L278-L279
Caused by KT-33141.

I have the same problem

repo: tlinkowski/basic-annotations


text:
profiles: unexpected behavior in sigil color selection

When attempting to edit the sigil color field in the profile settings, it truncates leading zeroes and then pads out the last character. For example, I previously had my color set to 0000b2. After the upgrade, it had converted it to B22222. Attempting to change it back results in the same thing after a refresh. 1000b2 however works.

can confirm this

This is fixed in Groups and Talk, but the Grid still shows the incorrectly padded color.

authors: bazfum riblus-bandyr

repo: tloncorp/landscape-apps


text:
Added preferred_algorithms and packet_size config options

Adding two more config options that get passed to the underlying erlang ssh connect: preferred_algorithms and packet_size

Thank you for adding that!

@BrendonPierson Could you possibly also update config_test.exs to reflect those changes? Thank you.

Sure thing @tlux! Let me know if this looks ok

authors: BrendonPierson tlux


text:
After run build script, docbox css broken

Hi,
I'm new to docbox and i have a little problem. Every time i run npm run buildscript it always ends up with a broken CSS, i'm using the default provided CSS, and when i inspect it, i got this error:
Warning: Prop className did not match. Server: "fixed-top fixed-right space-left16" Client: "fixed-top fixed-right undefined"

Also, I found that revert the index.html file can solve this problem.

This would be a great opportunity for someone to help and fix and contribute a PR! I'd love to review and merge such a PR.

Can confirm that changing package.json
"react": "15.6.2",
"react-dom": "15.6.2",
resolves the build issue for me.

authors: aipsel jimlongo56 nubilfi tmcw

repo: tmcw/docbox

license: isc

license_source: bigquery


text:
sf コマンドがなくても、sf org display, sf org list  およびログインくらいは imori 独自にできないのか

これをやろうとおもったら、API経由での OAuthの方法を完全に理解した上で、さらにその情報を自前で管理するということをやらんといけなくなるだろう。ホームディレクトリに置くとして、さらにそれを暗号化しておくとして、Win・Unix両方で動かすとなると、まぁ色々手間がかかりそうではある。

秘匿情報をどうやって保持するかが非常に悩ましい

一つの案として、imori を起動したら必ずログイン、かなぁ〜。。。
データローダーが前回のログイン情報から自動的にアクセスを試みるようにしているが、あれと同じことができるか？

しかしここまで書いたところで、そこまでやるなら普通に CLI 経由で良くないか？
と思った。

repo: tmkw/imori


text:
Remove main

We never did anything interesting with main, and our calling of it was rather broken, so it's probably better to remove it. People can now write this instead:
let () = f x

This is closer to how other MLs handle it, which is always nice. We can also remove some pretty ugly code from the backend.
The main disadvantage here is that it breaks a large number of our codegen tests. We used to use main to inject opaque values. As this now has no special meaning, it'll be stripped and so the test won't emit anything!
For now, I've fixed this by calling main with a bottom : 'a value:
let main f = ...

external val bottom : 'a = "nil"
let () = bottom (main bottom)

This definitely is pretty ugly (and can generate some awful code), but I'm OK with this for now. Hopefully the backend rewrite (which is increasingly reaching the status of Urn's resolver rewrite) will clean up a lot of these.

Looks good to me™

authors: SquidDev zardyh

repo: tmpim/amulet


text:
No Release task

Hi,
I am using the Visual Studio Team Services and added your extension. Unfortunately I am not able to find the task when creating a new build sequence. Did I miss something ?
Thanks,
Fabian
Update:
BTW: Just saw that its clearly writtenin the description, shame on me...

Unfortunately the release task is also not there.

Fabian,
It's a task for Release Definitions, not Build Definitions.

Thanks for your fast reply, that make sense. But should I not see it then here ?

(Sorry for those dumb questions, just startet to take a look at the whole Team Services topic today)

Yes you should see it here if the extension is properly installed (the "Deploy" category):

Hmm unfortunately it does not. Any idea what I can do to resolve it ? I already uninstalled and installed it again without luck.

After uninstall/install again, the tasks now show up. Strange, but luckily sovled.

We noticed some temporary issue on VSTS or Azure on the extension page. I guess that was it..

authors: fabianre ygeelen-tb

license: mit


text:
Support for Vike/vite-plugin-ssr

It would be nice to have integration between create-relay-app and Vike/vite-plugin-ssr since create-relay-app currently works with Vite but not with Vike/vite-plugin-ssr

in relation to this, I think create-relay-app would fit nicely into the Bati.js scaffolder for new projects: https://github.com/batijs/bati

repo: tobias-tengler/create-relay-app


text:
Try giving a list of potential stars that are leading to a given frequency spike

Use the individual pixel periodograms to find likely locations and then use astroquery to search SIMBAD and find some likely candidates

Need to flip the way the pixels are read into the wcs...
if the argwhere returns [48, 62] what we need to put into the pixel_to_world is (62, 48)
If I do "tess_wcs.pixel_to_world(*np.fliplr(solutions[0])).icrs" I get the correct thing, but if there are multiple solutions and I do:
tess_wcs.pixel_to_world(*np.fliplr(solutions)).icrs
then its wrong again....

Ah gotcha so the (x, y) is just backwards? Perhaps we just need *query_pixels.T[::-1] in that case (which will reverse the x-y axes)

I tried that as well... but that reverses the entire array, not the individual pairs

authors: TomWagg tobin-wainer

repo: tobin-wainer/elk


text:
[Feat] 검색창에 상품검색 기능 구현

#146

[x]  신규 파일 생성: searchPage.js, search.js
[x]  수정 파일: header.js, router.js
[x]  검색어 입력후 엔터치면 검색어가 포함된 상품이 노출된다.

#165 반영완료 되었으므로 해당 PR을 close 하겠습니다.

#165 해당 PR 반영 완료

repo: today-zipsa/TodayZipsa


text:
Update sbt, scripted-plugin to 1.10.6

About this PR
📦 Updates

org.scala-sbt:sbt
org.scala-sbt:scripted-plugin

from 1.6.2 to 1.10.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #918.

repo: tofu-tf/typed-schema


text:
Document what priority/order is used for version selection

Right now, I cannot find clear documentation on which order version detection uses. There is a decent listing of which things can be looked at, but it's not immediately obvious which have priority.
It'd be great if the documentation have a section that clearly indicated that order.
If I've missed it feel free to clown on me 😄

It seems like the following order is used, but I've not tested thoroughly:

Project version file
Version file in Project Root (Possibly one anywhere in the tree above the project in order?)
Default system-wide version defined

Notably missing: the requirements listed in the TF files, which can be installed/used with latest-allowed and min-required but it doesn't seem like this is used automatically as a fallback?

Oh, awesome! I didn't see the version resolution order. That's precisely what I was looking for.
I would propose sending that information into a digestible section with version files, or perhaps it's own section.
Weary to make promises I may not deliver but I will probably take a stab at a PR with what I imagine (and I can try to clarify better, too).

repo: tofuutils/tenv


text:
Red border?

Had an idea,
Thought gathering some feedback before actually implementing it might make some sense. How about an option which could be enabled, that would add a red border around every page if you were timing? For some people this may be annoying, but I feel for others that it'd be a good reminder that they were still being tracked.
Open to ideas, and if you think this is terrible, be honest! I can take it.

I think it's too "In your face" to have red border on all the pages. I like the idea of always being aware that time is tracking, but I think the red border is too much. Right now the red color of the extension icon is indicating that timer is running.

authors: IndrekV oliverdunk

repo: toggl/toggl-button


text:
Ask users to who are on broken updater version to get latest update

Some users are on Macos version that has broken updater. Send them email to update to latest.
Broken updater version should be 7.2.150

This is probably outdated. Double check if anyone is still on this version and then close this.

No users on this ancient version.

repo: toggl/toggldesktop


text:
Handle cases where project is unsynced

💻 Environment
Platform: All (library)
📒 Description
In some cases, the project or any other item could be not synced and also not marked as "needs sync".
I saw this with an un-synced project that did not have an id (it was NULL), the project was visible in the autocomplete but selecting it would clear the project selection.

First of selecting a non-synced project should still work
Secondly, the project that is not synced should be marked as to be synced when loaded

I wonder that old implementation doesn't store any project_guid after creating, how it handles if the project remains unsync?
I don't see any complain about the unsync project in old code, it means that it always works, isn't it?
Ref: https://github.com/toggl/toggldesktop/blob/b5064ec91eafd104b1d1c7d6baab59da3fe5db42/src/ui/osx/TogglDesktop/TimeEntryEditViewController.m#L396-L421

authors: IndrekV NghiaTranUIT


text:
Todoist - Cannot Enter Project in Task View

OS version: macOS latest
Browser version: Chrome latest
Extension version: 3.0.14

Relevant integration (if any):
Todoist webapp
🐛 Describe the bug
User reports that they cannot type into the project window in Toggl when a Todoist task view window is open. Support team member can replicate as well.
Expected behaviour
Project window should be available for typing.
Other details or context
Slack convo
Intercom convo

Intercom convo listed above also contains screenshot video of bug in action

repo: toggl/track-extension


text:
Update for 2020?

Is the plan still to update for 2020's landscape, or is this repo inactive for the time being?

@tdardet I am currently interviewing with several companies.
My plan is to migrate and rewrite some parts in GitBooks towards the end of this year.

Ah awesome, Good luck!
Tomás Dardet
On Sun, Oct 11, 2020 at 1:22 PM togiberlin notifications@github.com wrote:

@tdardet https://github.com/tdardet I am currently interviewing with
several companies.
My plan is to migrate and rewrite some parts in GitBooks towards the end
of this year.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/togiberlin/ui-ux-designer-roadmap/issues/11#issuecomment-706737909,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEJ3RLVA44AVUML5XAP3A3SKHSWZANCNFSM4SF7HRKA
.

Hi! any chance that you could add in the future a Product Designer roadmap? Maybe not in 2020 but in any update after? Thanks!

Any update?

Any update?

Waiting for your approval

Waiting for your approval

Some updates ?

authors: LuanFMelo arbutt76 loubyl tdardet togiberlin uniAmir

repo: togiberlin/ui-ux-designer-roadmap


text:
Implement set and fromValues for mat2, mat2d, mat3, and mat4

Was surprised to find out that these did not already exist.
Let me know if there are any problems.

LGTM, thanks! And thanks for giving me something to test the new Travis CI config with! :D

authors: thomcc toji

repo: toji/gl-matrix


text:
Add *_unchecked methods

I'm using bytes in an application, where I'm repeatedly slicing to sub-parts of the bytes.
I do my own error-checking of bounds, and handle that out of the hot path.
The methods of (advance, split_off, split_to) do additional bound checking, completely trashing the register allocation.
It'd be nice to have the option to call *_unchecked methods that avoid the bound checking.

Have you been able to try those methods in your app, with a temporary fork? It'd be good to get some data.

authors: seanmonstar semtexzv

repo: tokio-rs/bytes


text:
docs: user guides

Write documentation on how to debug applications with the console, how to use it

#3 Would allow us to generate screenshots

repo: tokio-rs/console


text:
パスワード画面のレイアウト変更

パスワード画面のレイアウト変更
・ActionBarに直接閉じるボタン表示
・トップの幅のサイズを変更

実機テストしてみたけどアクションバーが表示されなかった

androidManifestとかbuild.gradle関係を俺が最初の頃さわってたから、そこに問題があると思う


text:
chore: Issue Template を分割

📝 関連issue

close #445

⛏ 変更内容

Issue Template をバグとそれ以外で分割

合わせて bug および improve(旧: 改善提案) ラベルが自動付与されるように
label 単位で簡単に絞り込めるように

📸 スクリーンショット

@halsk @yokinist
ひとまずこんな感じでどうでしょう？
ラベルが自動付与されることで、管理しやすくなるかとー。
https://help.github.com/ja/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository

@potato4d ありがとうございます！確実に管理しやすくなりますね。。賛成です！

おっと https://github.com/tokyo-metropolitan-gov/covid19/issues/new でテンプレートが出てこないので一旦revertします

おっと、ちょっとfork先で確認します :bow:
なんでだろう

@potato4d 自分も大丈夫かなと思っていたんですが、、、ご確認お願いします🙏


text:
port number error

hi~ In serviceDidResolve delegate method,
I saw the service data as follows
HHService[0x742E3580, MAC000E53290B23, _afpovertcp._tcp, local., MAC000E53290B23.local., (
"192.168.1.48:88"
), 1] - Resolved last address
and I try to print the port number
NSLog(@"service port number :%i",service.lastResolvedPort);
what I got is
service port number :22528
please help thx

Hi,
The lastResolvedPort property is an internal property containing a (temporary) port number expressed in network byte order, which is why you get a strange result when you attempt to print it out.
But I've actually just checked in an update to HHService in which I've added new convenience properties, for instance resolvedInetAddresses, which contains a list of resolved addresses on the form IP:PORT.

authors: furueili tolo

repo: tolo/HHServices


text:
[Bug] No Error, Just Fails

Describe the issue

How to reproduce the issue

Expected behavior

Screenshots

Software versions

Home Assistant version:
TrueNAS integration version:
TrueNAS version:

Diagnostics data

Traceback/Error logs

Additional context

I cant do anything without any info. Make sure to fill the issue template with as much info as there is.

Sorry about that.  There really isn't much information to tell.  I follow the instructions perfectly, and I get no error message.  It just times out or something.  What would be most useful to start troubleshooting this?  I'm not sure what makes it fail, but I'd love to get it working.

versions, screenshots, diagnostic data, HA log. just provide everything you can.

I just noticed the information isn't there on the bug report.  I put all that in when I created it...
Home Assistant 2022.11.2
TrueNAS Core 13.0-RELEASE
Integration v1.2.3
The integration installs, and I clicked add...

All I get is this...

I've tried all sorts of various combinations of SSL, https:// in the URL, etc...  Same result.  If I put "https:" in the URL i get a "No response from host" error.  My firewall logs don't show anything being blocked, but HASS shows connection errors...
======================================
This error originated from a custom integration.
Logger: custom_components.truenas.truenas_api
Source: custom_components/truenas/truenas_api.py:44
Integration: TrueNAS (documentation, issues)
First occurred: 12:15:53 PM (4 occurrences)
Last logged: 12:44:19 PM
TrueNAS 172.16.1.200 unable to fetch data "pool" (503)
TrueNAS https://172.16.1.200 unable to fetch data "pool" (no_response)
=======================================
This error originated from a custom integration.
Logger: custom_components.truenas.config_flow
Source: custom_components/truenas/config_flow.py:76
Integration: TrueNAS (documentation, issues)
First occurred: 12:15:53 PM (4 occurrences)
Last logged: 12:44:19 PM
TrueNAS connection error (503)
TrueNAS connection error (no_response)
=======================================
I'm still tinkering in the firewall, but I haven't found any rule which may be blocking this from connecting...
Thanks,
Steve

I have never tried it with 13.0 release version, there could have been some bug.
503 is service unavailable error. seems like there is something broken on truenas side.
I would recommend to actually update your truenas.

Good day,
That would not surprise me.  I have found there is another issue with a networking configuration I have reported to them.  It prevents me from updating at the moment.  My TrueNAS works fine on 13.0, but if I update beyond that all my jails lose internet connectivity.  Maybe I'm just special.  LOL
https://ixsystems.atlassian.net/browse/NAS-118026
Something under the hood with networking did change along the way with them.  The 503... is there a specific service your integration relies on being enabled on the TrueNAS side to check?
Steven

Do they really lose internet connectivity or just DNS? I had such issue with truenas.
Solved it by using resolv.conf syntax in configuration field:

Cant check the ticket, appearantly I dont have access to view it.
I'm accessing official API, I dont think you can control it in any way (officially).

Yeah, sorry.  DNS.

yea, you can try to put it into resolver like I did.
DNS server entries in jail configuration never worked for me, even on 12.0

authors: tomaae wormuths

repo: tomaae/homeassistant-truenas


text:
Initial JNI support

Feedback welcome!

Example code using these JNI bindings can be seen in https://github.com/tomaka/glutin/pull/822

Here's a gist @sfackler made demonstrating a high-level API for JNI stuff: https://gist.github.com/sfackler/5c036006f8d58a1d38887ba014759f74
It is licensed under MIT/Apache2 so we can copy some stuff.
As I said in the previous comment, this might be out of scope of this PR but I thought I'd leave it somewhere for reference.

Might also be worth depending on https://crates.io/crates/jni-sys to avoid needing to have a second copy in here. Happy to make any changes necessary on that end.

@tomaka, what is your view on using @sfackler's jni-sys crate?
I'd prefer not to re-implement anything that we can readily reuse, but I'm not sure if you're happy to be adding another dependency.
Before I start addressing other feedback, it would be nice to decide if using jni-sys is on the table, and if we should add higher level wrappers to android-rs-glue, jni-sys, or am intermediate crate that wraps raw jni-sys in a nice, safe, Rust-y API.
I agree that adding a higher level API (like JNIEnv's that automatically detach_thread(), or jobject's that automatically DeleteGlobalRef/DeleteLocalRef when dropped). Most of all, I'd like to get rid of the various explicit method calls based on types.
But I'm also not sure this should be part of android-rs-glue.

An alternative approach would be to remove the JNI API from the glue module, and simply using the four methods provided by this patch in injected-glue from jni-sys, guarded by some #![cfg(target_os = "android")].

In my opinion this is the ideal design:

The internal and the external glues both depend on jni-sys and communicate with each other to share the low-level objects (like you have done in your PR).
The external glue also depends on a new crate (named jni for example) that doesn't exist yet and that provides a high-level wrapper around the JNI.
The high-level wrappers are reexported in the external glue's API, but the low-level objects are not exposed.

I can agree with that. I'll look into making the adaptations over the weekend, probably.
The higher level JNI wrapper will probably take a longer time to complete.
@sfackler Are you interested in creating a repo for the higher level wrapper, or should I?

I probably don't have the time to build out the high level wrapper right now unfortunately, so you might want to get it started.

Just a note that I have started on reworking this, but haven't found the time to finish it yet (because life).

So ... what is the current state? The jni_sys crate is pretty mature now and it's been two years ...

Why can't the ffi module simply be exposed to the library user? This way the user can hook up the jni crate and from there on it's rather easy to interact with the JNI. I know about "API concerns", but .. something is better than nothing.

@tomaka ... why? What's wrong about the jni crate? I mean ... do you want to re-do all of the work they've done just to not depend on them - how would you then do this function, if not using jni?

Sorry, what I mean is that we should simply reexport the content of the jni-sys crate from our own crate, instead of exposing it in the API.

authors: fschutt sfackler tomaka wvdschel

repo: tomaka/android-rs-glue


text:
Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
GitHub Corrected URLs

Was
Now

https://github.com/tomaka/gl-init-rs
https://github.com/tomaka/glutin

HTTPS Corrected URLs

Was
Now

http://crates.io/config.html
https://crates.io/config.html

:tada: :fr:


text:
🛑 Saiyans Blog is down

In ea1ca92, Saiyans Blog (https://blog.saiyans.com.ve) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Saiyans Blog is back up in e91d09d after 28 minutes.


text:
Added an option to support spaces in tags.

I have added a piece of code that removes the spaces in the tags and therefore allows them to be configured as :  18:00 -> 20:00
In my case different projects are created with both formats (by different teams).
I think this can be of interest to several users of the script. 😃

Hi,
Excellent, that is a good idea, I will implement that.
Regards,
Tomas
From: Théo @.>
Sent: Wednesday, 22 March 2023 19:50
To: tomasrudh/AutoShutdownSchedule @.>
Cc: Subscribed @.***>
Subject: [tomasrudh/AutoShutdownSchedule] Added an option to support spaces in tags. (PR #22)
I have added a piece of code that removes the spaces in the tags and therefore allows them to be configured as : 18:00 -> 20:00
In my case different projects are created with both formats (by different teams).
I think this can be of interest to several users of the script. 😃

You can view, comment on, or merge this pull request online at:
https://u20788398.ct.sendgrid.net/ls/click?upn=27HVtNwUduq3wZxogItvUavRPk72rrR-2Flm3jQ4-2F0sysqz0HjrVfYKX41J30UjcPlQspbfwUIGXjvU6DWVCfBZaOHSoTGyuLymkfw-2B954F58-3D9eWa_U31jt5HgHBh7k3Grc5s4l7W8-2BrUaSFVJ-2FPm-2FoJf3gyme2sKQ9gxlD-2Bu4vDTlQGAyJPPhOQtaSfOOj2dGwh-2Fb9sjQklWlLCXjVhtFNdqh7yioNRYnDDS6wCIrYzcbYoCkODWmkH3DUw6AJTMpcISS0jult2r-2F2rdB19l9AxP9JMdpEyKgQ39s4-2F4J1myR6acxRfrf8yNFz3sKW3g5aK3OfP7LbYMuvCvjpuQRvkEaDW-2FCD-2BBXRPK0UvAAKzztLTiKgjDHgKTCg-2BZhk-2F609eN-2BkA-3D-3D
Commit Summary

ada82cc https://u20788398.ct.sendgrid.net/ls/click?upn=27HVtNwUduq3wZxogItvUavRPk72rrR-2Flm3jQ4-2F0sysqz0HjrVfYKX41J30UjcPlQspbfwUIGXjvU6DWVCfBZVF2mElskDjrXhDaFBB-2BhVMOzV1bmhri-2FISimKnvrwlHv3sx-2FeRlP-2F1YzE9qxQ5q6TJCjgpNU-2BBsjR-2Fc3rdYNZY-3D2Atr_U31jt5HgHBh7k3Grc5s4l7W8-2BrUaSFVJ-2FPm-2FoJf3gyme2sKQ9gxlD-2Bu4vDTlQGAyJPPhOQtaSfOOj2dGwh-2Fb9sjQklWlLCXjVhtFNdqh7yioNRYnDDS6wCIrYzcbYoCkDYTCCc3yzUqSjbhId4uSmd8enOZwdzdHuqVbMrrKv7UrTVJaoaHMS6ql71OQutz4-2FY5-2B7OhyPkmlS-2B9OjWvX2VtGDQegbHDD6mxEGMXXGKxyTR-2Fv0tRO-2FivF-2Bgdk4fyvY39Ta9jpR-2BllF8Zs5CBJBQ-3D-3D  Added an option to support spaces in tags.

File Changes
(1 https://u20788398.ct.sendgrid.net/ls/click?upn=27HVtNwUduq3wZxogItvUavRPk72rrR-2Flm3jQ4-2F0sysqz0HjrVfYKX41J30UjcPlQspbfwUIGXjvU6DWVCfBZddOrEhpeBvrw9YkKL-2FKzoE-3DdCYG_U31jt5HgHBh7k3Grc5s4l7W8-2BrUaSFVJ-2FPm-2FoJf3gyme2sKQ9gxlD-2Bu4vDTlQGAyJPPhOQtaSfOOj2dGwh-2Fb9sjQklWlLCXjVhtFNdqh7yioNRYnDDS6wCIrYzcbYoCk8DsNebJgyLkC2Fl7b0k4E-2FhXsCB1vLccS-2Fwp1TFIMEXZaeajKTrvsaR-2BzHKBv1m0HAFgfXmnOHQvTaniAiGnfxCDhdqkNMxbClCCAMkgk61gJw5rUlAZtQsFfJ5koZctNEWLF7tuPYjMyIpuj1uPfQ-3D-3D  file)

M AutoShutdownSchedule.ps1 https://u20788398.ct.sendgrid.net/ls/click?upn=27HVtNwUduq3wZxogItvUavRPk72rrR-2Flm3jQ4-2F0sysqz0HjrVfYKX41J30UjcPlQspbfwUIGXjvU6DWVCfBZQkwafEUWT2xbAx-2BzeanQvjWY3TDSKhjz0Kwgu0BtRdOrOKF4Gh0Fcn-2B3SbBx4Z6Mk2HuPgwnk-2B0-2FafdL6sgqzVcnDPj0XlbnOJdQJkgk03-2BFzpz_U31jt5HgHBh7k3Grc5s4l7W8-2BrUaSFVJ-2FPm-2FoJf3gyme2sKQ9gxlD-2Bu4vDTlQGAyJPPhOQtaSfOOj2dGwh-2Fb9sjQklWlLCXjVhtFNdqh7yioNRYnDDS6wCIrYzcbYoCkBCuNmjKGJTQpcINqCIDNXMzQuF3BFDmaqe8i-2BtE6tylJ7wiqkLDjx9aJ7MJnjGfhDLk-2Fsze9ZckqJgfWDDmheR-2BOqiV-2BjcD3B3N38fPY-2FlZ-2BfhFoT74lr-2FPZjHs-2BAVSv8r3tVEXuoNAYGEtvatTb-2BA-3D-3D  (2)

Patch Links:

https://u20788398.ct.sendgrid.net/ls/click?upn=27HVtNwUduq3wZxogItvUavRPk72rrR-2Flm3jQ4-2F0sysqz0HjrVfYKX41J30UjcPlQspbfwUIGXjvU6DWVCfBZTS0BwxOeuyLno-2FFonhst5o-3Dcb36_U31jt5HgHBh7k3Grc5s4l7W8-2BrUaSFVJ-2FPm-2FoJf3gyme2sKQ9gxlD-2Bu4vDTlQGAyJPPhOQtaSfOOj2dGwh-2Fb9sjQklWlLCXjVhtFNdqh7yioNRYnDDS6wCIrYzcbYoCkj7fjABfx4JihbmglQ-2BZgzTm4T1GwW7wj385964XA-2B9nL-2Bl7z2gk6uY8mBv-2FH-2Bas-2FvpFhgGO5TjmS5gfqg8N-2BNfEnUiwTSLG0saEciPS0XcWEha6OAkK7cRGv2NZiVgu5gW1n4F-2B4hNKJdktYa0vr8w-3D-3D
https://u20788398.ct.sendgrid.net/ls/click?upn=27HVtNwUduq3wZxogItvUavRPk72rrR-2Flm3jQ4-2F0sysqz0HjrVfYKX41J30UjcPlQspbfwUIGXjvU6DWVCfBZQSjDSX-2B3ZVQQl-2FtsSEu9oM-3DHb1I_U31jt5HgHBh7k3Grc5s4l7W8-2BrUaSFVJ-2FPm-2FoJf3gyme2sKQ9gxlD-2Bu4vDTlQGAyJPPhOQtaSfOOj2dGwh-2Fb9sjQklWlLCXjVhtFNdqh7yioNRYnDDS6wCIrYzcbYoCklN2sF2dPr3RmkhchZ1rX2nNcG2R3FD1uppn5Mjjc1QZk-2FnEDezmx-2FYPevhmgZiIprE-2FrRtLdf1FvZTZSAvYr9VwpvmpyZx0BGy58420ibfsqd7L28L0pWDA5lRsGwQPd78duJkvSvFnMDebxQ0BU-2Bg-3D-3D

—
Reply to this email directly, view it on GitHub https://u20788398.ct.sendgrid.net/ls/click?upn=27HVtNwUduq3wZxogItvUavRPk72rrR-2Flm3jQ4-2F0sysqz0HjrVfYKX41J30UjcPlQspbfwUIGXjvU6DWVCfBZb8T3z3kM3j-2Fpaigr3KchyE-3DrN0I_U31jt5HgHBh7k3Grc5s4l7W8-2BrUaSFVJ-2FPm-2FoJf3gyme2sKQ9gxlD-2Bu4vDTlQGAyJPPhOQtaSfOOj2dGwh-2Fb9sjQklWlLCXjVhtFNdqh7yioNRYnDDS6wCIrYzcbYoCkBuTjPB98a-2FGWxbyGH3WOB-2FLyIHSXboOhhwCOlLQI9Dhrb06M914HF-2F-2FYn7nIjl2Kz7azJXGRTaXBn7G2c7zwH376vTBaWmP2cmV3ZYYNFUFVgz28zLqoZsZqR-2BwPORjKgcn5PZ-2FLB88vZd01oylkvA-3D-3D , or unsubscribe https://u20788398.ct.sendgrid.net/ls/click?upn=27HVtNwUduq3wZxogItvUVgmFDSuRkRUP0hiwX-2BQZOpCh6EjzUnAHvTmZkOI0ibXSUbdLYTXr-2BnFr7nZWc5BaO-2F70Yg6MYLL4SOmCfUMgY-2BnrzH6jhpziAAtTVbygvNRGC-2FuErmCPhjMlWAX6bkh5g-3D-3DIkqv_U31jt5HgHBh7k3Grc5s4l7W8-2BrUaSFVJ-2FPm-2FoJf3gyme2sKQ9gxlD-2Bu4vDTlQGAyJPPhOQtaSfOOj2dGwh-2Fb9sjQklWlLCXjVhtFNdqh7yioNRYnDDS6wCIrYzcbYoCkp8vnqTaVYFmu6Yi0yAhJ11rvZWeYb4PNDuylJgLekXBvA-2B7C3X7qfB-2FKZzWltg1gCsOLR2BsLYkaumF48DCxnF8-2BjFxEtM6r8cAzYefGWVsJciuzN3lOrqY2j-2F6rbc14JPQiKVeGQs5fZVe0IUCOnA-3D-3D .
You are receiving this because you are subscribed to this thread.  https://u20788398.ct.sendgrid.net/ls/click?upn=27HVtNwUduq3wZxogItvUVgmFDSuRkRUP0hiwX-2BQZOqniRk4OQu-2FvcxQxftUVPZdPbcgNyiSDR5ZaKDJOEXc7usqhRMOS2tRoV6YqRXhsZymzyhMD3-2B-2BM8qzRnWLxc-2FL42IHNqLHHO3-2B806T6XLH3Yh-2BQTZhdP70vyAsHlCqu6mu5n2ceUNNQ5zuBU7dwMFGUVpByCvRTJHWuYFtvcvmyg-3D-3DxEPm_U31jt5HgHBh7k3Grc5s4l7W8-2BrUaSFVJ-2FPm-2FoJf3gyme2sKQ9gxlD-2Bu4vDTlQGAyJPPhOQtaSfOOj2dGwh-2Fb9sjQklWlLCXjVhtFNdqh7yioNRYnDDS6wCIrYzcbYoCkT8avG52l6EB0g8COqH3OAinsKs-2Bi2GSBUKFtuOhgM0luGWqJoUmOXq-2FAiW1HAJhGVa06JiUq9pvFFE4WArIU995XAfxl0sHcMHrOdpP4Cx1GrIQD74M0i-2BOngmuYuY-2BT1EdM9czC659lhOy3UJcDqw-3D-3D Message ID: @.*** @.***> >

authors: theoricher tomasrudh

repo: tomasrudh/AutoShutdownSchedule


text:
Cannot start server

Dear all,
I tried for several hours to get this image working and still have the same error:
docker log
docker-mailserver
Initializing setup
Checking configuration
Configuring mail server

No DKIM key provided. Check the documentation to find how to get your keys.
Starting Misc
Starting mail server
Error: Please fix your configuration. Exiting...

docker-compose.yml
version: '2'
services:
mail:
build: docker-mailserver
hostname: xxxxxx
domainname: xxxx.xx
container_name: mail
ports:
- "25:25"
- "143:143"
- "587:587"
- "993:993"
volumes:
- ./maildata/:/var/mail
- ./mailstate/:/var/mail-state
- ./letsencrtypt/:/etc/letsencrypt/
- ./config/:/tmp/docker-mailserver/
environment:
- ENABLE_SPAMASSASSIN=1
- ENABLE_CLAMAV=1
- ENABLE_FAIL2BAN=1
- ENABLE_POSTGREY=1
- ONE_DIR=1
- DMS_DEBUG=0
- SSL_TYPE=letsencrypt
cap_add:
- NET_ADMIN
volumes:
maildata:
driver: local
mailstate:
driver: local
The docker-mailserver directory contains the git clone of the project. Using the suggested image ( tvial/docker-mailserver:latest) yelds the same results.
Can you please help me start this image?
BR,
Alecs

Hi @alecsandruchirosca, to have more detail, use DMS_DEBUG=1, restart container and paste the console log.

`#

ENV

HOSTNAME=xxxxxx.xxxx.xx
DMS_DEBUG=1
VIRUSMAILS_DELETE_DELAY=7
ENABLE_CLAMAV=1
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ENABLE_FAIL2BAN=1
ENABLE_SPAMASSASSIN=1
PWD=/
SHLVL=1
HOME=/root
ONE_DIR=1
SSL_TYPE=letsencrypt
DEBIAN_FRONTEND=noninteractive
ENABLE_POSTGREY=1
_=/usr/bin/printenv

docker-mailserver

Initializing setup
Registering check,setup,fix,misc and start-daemons functions

_check_environment_variables() registered
_check_hostname() registered
_setup_default_vars() registered
_setup_dovecot() registered
_setup_dovecot_local_user() registered
_setup_postgrey() registered
_setup_dkim() registered
_setup_ssl() registered
_setup_docker_permit() registered
_setup_mailname() registered
_setup_amavis() registered
_setup_dmarc_hostname() registered
_setup_postfix_hostname() registered
_setup_dovecot_hostname() registered
_setup_postfix_sasl() registered
_setup_postfix_override_configuration() registered
_setup_postfix_sasl_password() registered
_setup_security_stack() registered
_setup_postfix_aliases() registered
_setup_postfix_vhost() registered
_setup_environment() registered
_fix_var_mail_permissions() registered
_fix_var_amavis_permissions() registered
_misc_save_states() registered
_start_daemons_cron() registered
_start_daemons_rsyslog() registered
_start_daemons_dovecot() registered
_start_daemons_opendkim() registered
_start_daemons_opendmarc() registered
_start_daemons_postgrey() registered
_start_daemons_postfix() registered
_start_daemons_fail2ban() registered
_start_daemons_clamav() registered
_start_daemons_amavis() registered
Checking configuration
Check that there are no conflicts with env variables [_check_environment_variables]
Check that hostname/domainname is provided or overidden (no default docker hostname/kubernetes) [_check_hostname]
Domain has been set to xxxx.xx
Hostname has been set to xxxxxx.xxxx.xx
Configuring mail server
Setting up default variables [_setup_default_vars]
Set ENABLE_LDAP=0
Set ENABLE_FETCHMAIL=0
Set OVERRIDE_HOSTNAME=
Set ENABLE_MANAGESIEVE=0
Set DMS_DEBUG=1
Set ENABLE_POP3=0
Set ENABLE_SASLAUTHD=0
Set ENABLE_CLAMAV=1
Set SMTP_ONLY=0
Set ENABLE_FAIL2BAN=1
Set ENABLE_SPAMASSASSIN=1
Set POSTGREY_DELAY=300
Set POSTGREY_TEXT=Delayed by postgrey
Set ENABLE_POSTGREY=1
Set POSTGREY_MAX_AGE=35
Setting up Dovecot
Setting up Dovecot Local User
'config/docker-mailserver/postfix-accounts.cf' is not provided. No mail account created.
Configuring postgrey
Setting up DKIM
No DKIM key provided. Check the documentation to find how to get your keys.
Setting up SSL
Setting up PERMIT_DOCKER Option
Adding container ip in my networks
Setting up Mailname
Creating /etc/mailname
Setting up Amavis
Applying hostname to /etc/amavis/conf.d/05-node_id
Setting up dmarc
Applying hostname to /etc/opendmarc.conf
Applying hostname and domainname to Postfix
Applying hostname to /etc/postfix/main.cf
Applying hostname to Dovecot
Applying hostname to /etc/dovecot/conf.d/15-lda.conf
Setting up Postfix Override configuration
No extra postfix settings loaded because optional '/tmp/docker-mailserver/postfix-main.cf' not provided.
Setting up Postfix SASL Password
Warning: 'SASL_PASSWD' is not provided. /etc/postfix/sasl_passwd not created.
Setting up Security Stack
Enabling and configuring spamassassin
Enabling clamav
Fail2ban enabled
Setting up Postfix Aliases
Warning 'config/postfix-virtual.cf' is not provided. No mail alias/forward created.
Setting up Postfix vhost
Setting up /etc/environment
Checking /var/mail permissions
Permissions in /var/mail look OK
Checking $amavis_state_dir permissions
Permissions in /var/mail-state/lib-amavis look OK
Starting Misc
Consolidating all state onto /var/mail-state
Destination /var/mail-state/spool-postfix exists, linking /var/spool/postfix to it
Destination /var/mail-state/lib-postfix exists, linking /var/lib/postfix to it
Destination /var/mail-state/lib-amavis exists, linking /var/lib/amavis to it
Destination /var/mail-state/lib-clamav exists, linking /var/lib/clamav to it
Destination /var/mail-state/lib-spamassasin exists, linking /var/lib/spamassasin to it
Destination /var/mail-state/lib-fail2ban exists, linking /var/lib/fail2ban to it
Destination /var/mail-state/lib-postgrey exists, linking /var/lib/postgrey to it
Starting mail server
Starting cron  [ OK ]
Starting rsyslog  [ OK ]
Starting dovecot services  [ OK ]
Starting opendkimfalse
[ FAILED ]
Error: Please fix your configuration. Exiting...
`

With DMS_DEBUG I got the above log (docker log mail ).
BR,
Alecs

Hi, i have exact the same failure.
if i downgrade to docker-mailserver 2.2, then opendkim will be started, but then the error comes during start of amavis.
Output is then:
...
Starting amavisfalse
[ FAILED ] Error: Please fix your configuration. Exiting...

I just upgraded a server to 2.3. No issue with DKIM so far. Only Postgrey was not running.

3 other error to solve:
May  6 12:36:14 mail postgrey[3623]: FATAL: ERROR: can't open lock file: /var/lib/postgrey/postgrey.lock#012

May  6 12:36:15 mail postfix[4414]: Postfix is running with backwards-compatible default settings
May  6 12:36:15 mail postfix[4414]: See http://www.postfix.org/COMPATIBILITY_README.html for details
May  6 12:36:15 mail postfix[4414]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"

May  6 12:36:15 mail postfix/master[4451]: fatal: open lock file /var/lib/postfix/master.lock: cannot create file exclusively: Permission denied

Tried manually (and had to disable ONE_DIRbut after that it worked well).
No idea yet yo a long term patch. Ideas welcome.

Maybe this also relates to #545.
Although it works for me just well, I also receive backwards-compatibility warnings in my logs.
Will have a look at this later.

Duplicates https://github.com/tomav/docker-mailserver/issues/545
Move this discussion there.

@alecsandruchirosca you had this error because no user account has been provided:
'config/docker-mailserver/postfix-accounts.cf' is not provided. No mail account created. is debug log.
I reproduced this issue today, I'll add a fix.

Here is the PR https://github.com/tomav/docker-mailserver/pull/612

:latest image available.

#491 & #621

authors: alecsandruchirosca grossmane kiliant tomav

repo: tomav/docker-mailserver


text:
Fix #526: fatal: no SASL authentication mechanisms

When using the container with SMTP_ONLY = 1,  the postfix process within the container fails
on ehlo because there is no valid sasl authentication mechanism available. This happens because sasl has been enabled within postfix/main.cf per default but sasl is not configured.
To fix this _setup_postfix_sasl does not depend anymore on ENABLE_SASLAUTHD and will check in it's logic, whether to enable or disable sasl explicit within postfix/main.cf.

I think you should add an integration test for that.

Added integration test

Just to be accurate on this issue, i just coverd the testing for this particular problem, checking whether sending an email is working or not. But i think we should cover more test cases for the mailserver state SMTP_ONLY use-cases.
Here some examples:

Check Mail send is working
Check SASL authentication is working
Check Relay is working
Check Relay with sasl authentication is working

Maybe we could create a section for this.

authors: alinmear tomav


text:
Listen markercluster click event

Its possible to acces clusterclick, without overlays??
My initial map:

//map initial
    angular.extend($scope, {
        center: {
            autoDiscover: true
        },
        defaults: {
            scrollWheelZoom: false
        },
        layers: {
            baselayers: {
                osm: {
                    name: 'OpenStreetMap',
                    url: 'http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png',
                    type: 'xyz'
                }
            }
        }
    });

And then i call my own service to fecth markers data:
    //on load map
    $scope.$on('leafletDirectiveMap.load', function(event){

       api.getMarkersByProximity(function(data){
             $scope.markers.push(data);
        });

       });

Now i have a map with markers and clusters.
With this event i can listen when a marker is clicked, but not a cluster:
$scope.$on("leafletDirectiveMarkersClick", function(event, args){
        console.log($scope.markers[args]);
    });

Its possible to do?? thanks
I don´t want when cluster marker is clicked to expand child markers... i want to get child markers data to do another thing.
On official Leaflet.markercluster docs says:
markers.on('clusterclick', function (a) {
    console.log('cluster ' + a.layer.getAllChildMarkers().length);
});

Is any event directive to listen?

@markitosgv, have you found a way to listen for cluster events?

Has anyone found any ways to listen besides dipping down into pure Leaflet (like @joeljeske did in #648)?

This issue was moved to angular-ui/ui-leaflet#31

I'm going to rework&redesign angular-leaflet-directive to be compatible with Leaflet v1.0. It will mantain almost all its functionality, and will be compatible with the current features of the directive, but I must start from a fresh point, so I'm going to close this issue. If you think it must be worked with the new version, please reopen it.

authors: joeljeske markitosgv nmccready rasmi tombatossals

repo: tombatossals/angular-leaflet-directive


text:
React 15.1.x Support

Is this on the horizon?

On second look, it's working excellently on the latest React!  (closing)

repo: tomchentw/react-google-maps


text:
Support creating machine readable diagnostics

Raised by Giannis @gnikit in https://fortran-lang.discourse.group/t/3949/2

Adding an option or slightly restructuring the diagnostic message to be easily parseable via regex. The message structure is already very good, but fetching the error message via regex would be hard. A good example of that is gfortran-11>= with the flag -fdiagnostic-plain-output. Having an such option would allow for code editors to parse the output of the linter to their Diagnostics console in VS Code PROBLEMS tab.

The current report interface turns an index of a token to a label object
https://github.com/toml-f/toml-f/blob/225174f7a858186507e7bd08c4252918dca9dee0/src/tomlf/de/context.f90#L87-L89
And creates a diagnostic object from it
https://github.com/toml-f/toml-f/blob/225174f7a858186507e7bd08c4252918dca9dee0/src/tomlf/de/context.f90#L92-L96
For the human facing output this is than turned into a string at
https://github.com/toml-f/toml-f/blob/225174f7a858186507e7bd08c4252918dca9dee0/src/tomlf/de/context.f90#L101
Note that the actual source code is only needed when creating the report string, the diagnostic object itself contains only position information from the label objects as well as the messages to display.

To support this without much effort on the user side, we could add a state in the context objects which describes whether the report should be optimized for humans or machines, default to human-friendly output. A tool which wants integrate its TOML Fortran usage for error reporting with the the VS Modern Fortran Extension can provide an option or environment variable to toggle this switch in the context object and make the error output automatically accessible for the Diagnostic console in VS Code.
The actual preferred format for the VS Modern Fortran Extension has to be defined first.

I think I might have been to quick to the current diagnostic message format is okay. I just whipped up a REGEX that should work with VS Code's problemmatcher https://regex101.com/r/q6duAL/4 and in any other tool that uses ECMAScript (Javascript) flavour for regex

The online limitation that I can think of with the current output format, is that the diagnostics are multiline and not all code editors/ linter plugins are able to capture multiline regexs. FYI VS Code is fine with that: https://code.visualstudio.com/Docs/editor/tasks#_defining-a-multiline-problem-matcher

I just whipped up a REGEX that should work with VS Code's problemmatcher regex101.com/r/q6duAL/4 and in any other tool that uses ECMAScript (Javascript) flavour for regex

The indent of the filename and line and column specifier is dependent on the line number, you have to match for multiple spaces there (https://regex101.com/r/9xImjz/2).

If I have understood correctly, this will eventually be present in/part of fpm. Let me know when that happens to add the problemmatcher in the fortran-lang vscode extension.
I think this might be a good opportunity to try the new GitHub projects that span the entire organisation as opposed to the individual repos.

Seems to be not an issue which is worth addressing at the moment.

authors: awvwgk gnikit

repo: toml-f/toml-f


text:
Issue in project opening

Class org.jetbrains.kotlin.idea.gradleTooling.KotlinGradleModel must not be requested from main classloader of org.jetbrains.kotlin plugin [Plugin: org.jetbrains.android]
when i open a new project desktop only with java version 21 and gradle version 8.5

It is fixed it is happend due to old kotlin plugin

Interesting, I'll try to update it in Liftoff if possible. I had an issue when launching Gradle with Java 21 and trying to build an Android APK from IDEA, but it wasn't the same bug you reported. The bug I hit was resolved by changing the setting in IDEA to run Gradle with Java 17. In case anyone finds this by searching, the error was:
> Task :android:compileReleaseJavaWithJavac FAILED

Execution failed for task ':android:compileReleaseJavaWithJavac'.
> Could not resolve all files for configuration ':android:androidJdkImage'.
   > Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for JdkImageTransform: C:\Users\tommy\AppData\Local\Android\Sdk\platforms\android-34\core-for-system-modules.jar.
         > Error while executing process C:\d\jvm\jdk21-hotspot\bin\jlink.exe with arguments {--module-path C:\Users\tommy\.gradle\caches\transforms-3\553ad13d8645437e7a391ae3ab1b8dbb\transformed\output\temp\jmod --add-modules java.base --output C:\Users\tommy\.gradle\caches\transforms-3\553ad13d8645437e7a391ae3ab1b8dbb\transformed\output\jdkImage --disable-plugin system-modules}

I've never seen this type of bug before, and I didn't know Android even used jlink...

Try ./gradlew clean
After that try building again It sometimes fixed the problem

repo: tommyettinger/gdx-liftoff


text:
admin displaying apps inconsistently

I'm seeing some unexpected results in the django admin. Specifically I'm seeing what are strictly tenant apps showing up in the global schema, and I'm seeing what is strictly a shared app not showing up in the global schema admin ("Not available for global schema").
I think this might be because I am using the verbose notation in my SHARED_APPS and  TENANT_APPS, e.g. 'polls.apps.PollsConfig', as proposed in the django tutorial. Whenever I switch to the short notation (e.g. 'polls') then the tenant apps only show up in the tenant admin. This is a pretty acceptable workaround, but I wanted you to know that there is some dissonance there.
The primary issue I'm facing is that there doesn't seem to be a way to obscure a shared app from tenants. Specifically, I would like to not show my tenant model to all of my tenants. Have I overlooked a method for making a table in the shared schema private (or for global admin purposes only)?

We also had inconsistencies in the django admin in our project.
I haven't had much time to dig into it to try to find what is happening.
In particular admin.site.register/unregister have been erratic.

The primary issue I'm facing is that there doesn't seem to be a way to obscure a shared app from tenants. Specifically, I would like to not show my tenant model to all of my tenants.

I worked around by implementing a seperate admin site for 'public'

If found out that the issue that we were having was due to having the INSTALLED_APPS like in this line:
https://github.com/tomturner/django-tenants/blob/5128d9e9d2409f3cd0b09c0bd574170ff657725d/examples/tenant_tutorial/tenant_tutorial/settings.py#L175
which was causing to the order of loaded apps to be randomize (set in python does not keep order).
We had an package that was registering in its admin.py, and we were unregistering in one of our apps. If the our app loaded first it would be registered, if the package loaded first, it would be unregistered.
I hope this helps.

I had the same issue use INSTALLED_APPS = list(SHARED_APPS) + [app for app in TENANT_APPS if app not in SHARED_APPS]

In our project, we are using django-configurations which have configurations classes instead a configuration file (one for production, one for development, etc).
Because the scope for list comprehension behave weirdly in a class body the code snippet that you posted won't work. The workaround was to use
INSTALLED_APPS = list(set(SHARED_APPS) - set(TENANT_APPS))+ TENANT_APPS  # keep the order of the TENANT_APPS
Since the order of TENANT_APPS that mattered. I failed to find a more elegant solution, but it works

authors: ArnWac marcoaaguiar thismatters tomturner

repo: tomturner/django-tenants


text:
Inconsistent podspec version in tags

Podspec version in 1.0.5-swift2 and 1.0.5 tags is still using 1.0.4.

I restructured the whole repository, deleted the separate swift-2 branch, made master compatible with Swift 2.0, so this is fixed now!

authors: saramroo tomvanzummeren

repo: tomvanzummeren/TZStackView


text:
sensible versus sensitive in risk messages

need to replace sensible for sensitive in risk associated with finding message.

Publicly accessible load balancers could expose sensible data to bad actors.
Vaults accessible to everyone could expose sensible data to bad actors

Thanks @fredski-github, just fixed it in branch 2.6.1 and will be in master as soon as I fix the other bug

authors: fredski-github toniblyx

repo: toniblyx/prowler


text:
Add docs example with p5.SVG

Pen plotters + p5 + Svelte would be a great example that some may find inspiring. That was one of the founding pieces of inspiration for starting this project and I was disappointed that p5.SVG didn't support ESM/instance mode so I couldn't get an SVG runtime for p5 working w/ p5-svelte.
In a recent release, p5.SVG added support for those pieces 🥳

Turns out that the instance mode does the thing where it's trying to mod p5 via accessing the window which Svelte no likey. This may not work, or may need a custom shim within p5-svelte in order to support


text:
Can't build example using esp-idf v4.1

Prerequisites

[x] I have written a descriptive issue title
[x] I have verified that I am using the latest version of esp32-wifi-manager
[x] I have searched open and closed issues to ensure it has not already been reported

Description
I'm facing the same issue similar #103 when working with ESP-IDF 4.1 on platformio.
 error: unknown type name 'esp_event_handler_instance_t'; did you mean 'esp_event_handler_t'?
Is there anyway to get around this build error while still using the 4.1 version?
Steps to Reproduce

install platformio extention on vscode
create a new project for esp32 using the esp-idf framework
create a components folder under the root of the project and copy the wifi-manager into it (tried master and other tags)
build

System Configuration

Debian 10 x64
vscode
platformio

Hello,
This is normal, this code only compile with 4.2 and up as per the requirements:
https://github.com/tonyp7/esp32-wifi-manager#requirements

Are you considering to support a stable release in the future? because v4.2 is only pre-release beta now contrary to v4.1 which will be supported until February 2023.

Definitely not. 4.2 should hit RC stage fairly soon and the master tree is already in 4.3. There’s no point holding back the codebase at this stage.


text:
How to build?

Which assembler must be used to build the sources?

Hi
Please use Kickassembler
http://theweb.dk/KickAssembler/Main.html#frontpage
Just assemble game.asm and that should give you game.prg, which you can run
straight away.
It can also be crunched with exomizer after that, which is what the
included ChopperCommand.prg file is
On Mon, 26 Aug 2019, 22:53 Ralph Möritz, notifications@github.com wrote:

Which assembler must be used to build the sources?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tonysavon/Chopper-Command-C64/issues/1?email_source=notifications&email_token=AMSYTCQYFLCIAY4IYXOW2T3QGQ7DNA5CNFSM4IPVWFEKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHPKN3A,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMSYTCUNNKSN36Z6QA6V7LLQGQ7DNANCNFSM4IPVWFEA
.

Thank you!

authors: rmoritz tonysavon


text:
MacOS build broken due to encapsulation

@Roberto-Gentili Any idea why this build is failing on macOS?:
Error: ROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy (injected-nexus-deploy) on project narcissus: Execution injected-nexus-deploy of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy failed: An API incompatibility was encountered while executing org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy: java.lang.ExceptionInInitializerError: null
Error: ROR] -----------------------------------------------------
Error: ROR] realm =    extension>org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8
Error: ROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[...]
Error: ROR] -----------------------------------------------------: Unable to make field private final java.util.Comparator java.util.TreeMap.comparator accessible: module java.base does not "opens java.util" to unnamed module @3681037

Building with JDK 7 fails with the error below: there appears to be an incompatible Maven plugin with this JDK. ave you updated any Maven plugins?
constituent[11]: file:/C:/Users/runneradmin/.m2/wrapper/dists/apache-maven-3.8.8-bin/67c30f74/apache-maven-3.8.8/lib/maven-compat-3.8.8.jar
	at org.apache.maven.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:53)
	at org.apache.maven.wrapper.WrapperExecutor.execute(WrapperExecutor.java:152)
	at org.apache.maven.wrapper.MavenWrapperMain.main(MavenWrapperMain.java:76)
	Caused by: java.lang.UnsupportedClassVersionError: com/fasterxml/jackson/databind/ObjectMapper: Unsupported major.minor version 52.0

@Roberto-Gentili Any idea why this build is failing on macOS?:
Error: ROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy (injected-nexus-deploy) on project narcissus: Execution injected-nexus-deploy of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy failed: An API incompatibility was encountered while executing org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy: java.lang.ExceptionInInitializerError: null
Error: ROR] -----------------------------------------------------
Error: ROR] realm =    extension>org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8
Error: ROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[...]
Error: ROR] -----------------------------------------------------: Unable to make field private final java.util.Comparator java.util.TreeMap.comparator accessible: module java.base does not "opens java.util" to unnamed module @3681037

It was already broken, so I tried updating all the Maven plugins to see if that would fix it...
It looks like the Maven wrapper version needs to be updated, or something?

It was already broken, so I tried updating all the Maven plugins to see if that would fix it...
It looks like the Maven wrapper version needs to be updated, or something?
Unfortunately I don't know: I abandoned the build test for JDK 7 due to too many problems even if I do the release build with the version parameter set for compatibility with JDK 7

It was already broken, so I tried updating all the Maven plugins to see if that would fix it...
It looks like the Maven wrapper version needs to be updated, or something?

Unfortunately I don't know: I abandoned the build test for JDK 7 due to too many problems even if I do the release build with the version parameter set for compatibility with JDK 7

@Roberto-Gentili @michael-simons OK, the build seems to be fixed. Thanks for your help! Pushing out 1.0.10.

It's interesting that this failed on JDK 7 :) I explicitly set the Maven Wrapper and Maven versions to work with 7. Seems to be an issue with nexus-staging-maven-plugin.
FWIW There's a way to define tool chains in Maven, so that you don't depend on the JDK that is being used to run Maven, but I never used them.
https://maven.apache.org/guides/mini/guide-using-toolchains.html

@Roberto-Gentili @michael-simons OK, the build seems to be fixed. Thanks for your help! Pushing out 1.0.10.

Great! I will release the new version of JVM-Driver as soon as it is available

Maven now requires a minimum JDK of 7, it seems (or maybe it is Maven-wrapper). I just removed the testing for JDK 7, since I don't have time to mess with this much more!

repo: toolfactory/narcissus


text:
Fix client singleton router ii

What kind of change does this PR introduce?
Replaces: https://github.com/toomuchdesign/next-page-tester/pull/161
Fixes: https://github.com/toomuchdesign/next-page-tester/issues/160
What is the current behaviour?
You can also link to an open issue here.
What is the new behaviour?
...
Does this PR introduce a breaking change?
What changes might users need to make in their application due to this PR?
Other information:
Please check if the PR fulfills these requirements:

[x] Tests for the changes have been added
[x] Docs have been added / updated

Coverage remained the same at 100.0% when pulling 187c984537ad68b359ee1f4cad8c5021f0c4e6b9 on fix-client-singleton-router-II into dad5cbb7ca4175290ad32820290575f3318fc263 on master.

authors: Meemaw coveralls

repo: toomuchdesign/next-page-tester


text:
bug in verify_code

https://github.com/toplan/laravel-sms/blob/master/src/Toplan/LaravelSms/validations.php#L16

当用户未点击发送短信按钮时，直接点击提交，这个时候因为没有存储状态到session/cache，那么这里获取attempts肯定会保异常。

repo: toplan/laravel-sms


text:
[PERFORMANCE]: avoid multiple redux.getState() calls in connect

I've simplified the callback workload to reduce the number of times we invoke redux.getState() in handleChange from 2x to 1x and also I've eliminated an unnecessary function (used previously in the shallowEqual days of connect). My hope is that we can achieve the same goal #41 set out to solve but without the tradeoff of holding state local in the component (and further -helping us avoid Ember.set / setProperties).
After the over notify problem was solved, the remaining "Problem Statement" back in #30 was that we call redux.getState() multiple times during re-render work and that could be expensive. This PR should solve a good chunk of that and I'm asking @dbashford to confirm we didn't break his app. In addition, I'm reaching out to @justinpark to confirm he won't run into a performance issue of any kind taking this new connect implementation.
Would you both have time this week to try out this updated connect function and report back?

@dustinfarris awesome! I'm hopeful it helps move us closer to the silver bullet while avoiding whatever it was that @dbashford ran into w/ the setProperties variation from last week. I'll wait until I hear from both of them that this is regression free/ solid before we get a v1.9.2 out the door

the remaining "Problem Statement" back in #30 was that we call redux.getState() multiple times during re-render work and that could be expensive.

I wonder how expensive redux.getState() really is?  I would guess under the hood the browser is just kicking around a pointer.  I'd be more interested in knowing how expensive the stateToProps function is for a non-trivial component.
in the computed prop:
defineProperty(component, name, computed(function() {
            return finalMapStateToComputed(redux.getState())[name];

I'd bet the finalMapStateToComputed which gets run on every single property is much more expensive than the redux.getState() part.
Anyway, probably discussion best saved for another issue/PR.

Looking good here!

All good here too!

authors: dbashford dustinfarris justinpark toranb

repo: toranb/ember-redux


text:
INTP-311 (MAPPDK_SERVER,204) Uninitialized data is used

I got fanucpy working well on my first CRX but on my second CRX I get this error message.   I've searched the threads and this message pops up for a variety of reasons with other socket based programs.   Was wondering if you had any troubleshooting tips.

Hi. Have you copied the latest fanuc driver files from https://github.com/torayeff/fanucpy/tree/main/src/fanuc-driver ?
Basically, you need to install the latest version of fanucpy (0.1.11) with the latest version of fanuc driver files.

i did this morning hoping to resolve the issue.   Some threads suggest it
might be a memory issue.
Will try again.
Sabri
BTW great job with integrating ChatGPT!
On Tue, Mar 21, 2023 at 12:06 PM Agajan Torayev @.***>
wrote:

Hi. Have you copied the latest fanuc driver files from
https://github.com/torayeff/fanucpy/tree/main/src/fanuc-driver ?
Basically, you need to install the latest version of fanucpy (0.1.11) with
the latest version of fanuc driver files.
—
Reply to this email directly, view it on GitHub
https://github.com/torayeff/fanucpy/issues/18#issuecomment-1478364315,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACV24LVMTW2QB4HU5K7IG3W5HUZXANCNFSM6AAAAAAWCZM5QM
.
You are receiving this because you authored the thread.Message ID:
@.***>

@sansoy Let me know how it goes. I will have a closer look at the issue on Thursday. Some far there were not any problems while testing using Roboguide.

I can confirm that v0.1.11 works with the latest .pc and .ls files. Please copy the new files from https://github.com/torayeff/fanucpy/tree/main/src/fanuc-driver

Thanks Agajan!  I was able to get it to run my CRX!
Great work!
Sabri
On Thu, Apr 6, 2023 at 7:08 AM Agajan Torayev @.***>
wrote:

Closed #18 https://github.com/torayeff/fanucpy/issues/18 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/torayeff/fanucpy/issues/18#event-8945813893, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACV24KURBH5IQNMKUKDQ5DW7253LANCNFSM6AAAAAAWCZM5QM
.
You are receiving this because you were mentioned.Message ID:
@.***>

authors: sansoy torayeff

repo: torayeff/fanucpy


text:
lena loading grace bug

When using image.display(image.lena()), it shows grace hopper. As a suggestion, possible creating a new image.grace() function would be better.

I was also curious about this. Is it a joke? :smile:

You can see https://github.com/torch/nn/issues/854.
"we've removed lena. we cant change the name because of breaking API"

repo: torch/image


text:
Navigation links not working on mobile

https://github.com/torchbox/wagtail-news-template/blob/main/templates/navigation/header.html#L124
a href was blank
should be:
href="{{ link.value.get_url }}"

@songproducer thank you for filing these issues. It is very useful. Feel free to submit pull requests with fixes to any issues you find and have time for

@zerolab Sorry I'm git illiterate, I gave it a shot but not sure if this is right.
https://github.com/songproducer/wagtail-news-template/pull/2

Hey @songproducer, no worries at all.
Perhaps https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork can help

Thanks! I was trying to make my life more difficult by trying to use command line. Pull request submitted!

authors: songproducer zerolab

repo: torchbox/wagtail-news-template


text:
Add that mn requires bindeps

Without this installing errors with:
error: failed to parse manifest at `mnemos/tools/manganese/Cargo.toml`

Caused by:
  `artifact = …` requires `-Z bindeps` (cargo-binutils)

Ah, I had not really considered the use case of installing mn using cargo install. Instead, I had assumed that it would always be run using the cargo mn alias defined in the workspace's .cargo/config.toml, which will always work fine because that file also explicitly enables the bindeps unstable feature.
I'm not sure whether or not we should include this in the README. On one hand, it does tell users how to avoid problems when installing mn using cargo install. On the other hand, I'm not actually sure if installing mn that way is a good idea. The advantage of only ever running it using cargo run is that it is potentially rebuilt whenever the Cargo.lock entries for its dependencies changes. This means that if you run mn using the alias that calls cargo run, you get whatever versions of the bindeps are currently in the lockfile. If those haven't changed, mn and its dependencies are not recompiled every time its run, but if the lockfile has changed, the cargo run command will build new versions of the bindeps. This ensures that everyone gets compatible versions of those dependencies whenever they use cargo mn.
On the other hand, if mn is cargo installed, it's built once, and every subsequent time you run cargo mn, you get the same thing, regardless of the mnemos repo's Cargo.lock. This is fine with regards to the actual mn binary, since it's very simple and won't change often. However, it also means that the versions of the bindeps that are downloaded and compiled are the versions you get when mn is cargo installed, and if the lockfile updates those dependencies, you still get the old ones. This means that if we later update the lockfile to depend on new versions of those tools, any contributors who have cargo installed mn will see their versions of the build dependencies begin to drift from what other contributors are using, potentially introducing compatibility issues with the various scripts run using mn.
Because of the version drift issue, I think it might be better to just have the README suggest that mn should not be cargo installed, and that it should instead always be used through cargo run --package manganese , or through the cargo mn alias defined in the workspace, which expands to that. What do you think?

Ok. I didn't actually know how to run it and assumed it was a normal cargo tool.  I didn't know you could define aliases in the workspace, and I work with a lot of different rust projects so this probably will be a tripping point for folks. Thanks for the quick response!

authors: LegNeato hawkw

repo: tosc-rs/mnemos


text:
🛑 TI-DHR is down

In 1da369b, TI-DHR (https://dhr.hanati.co.kr/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TI-DHR is back up in f837b87.

repo: touguy/uptime


text:
Adding support for boolean input types

Includes custom prompts for y/n, yes/no, true/false, and t/f. With uppercased default values and optional in/out types.
In/out types are configured with a '/'. "In" type controls the prompting, "out" type controls the string conversion. This allows prompting for "y/n" and outputting as "true/false", for one example.

Maybe in the future, instead of output types we could have some sort of casting use. i.e. %((bool):config:my_var). I'm not sure what the best format would be, but this would lend for greater flexibility.

repo: toumorokoshi/sprinter


text:
🛑 Silicon Valley Animal Control Authority is down

In 8982dfc, Silicon Valley Animal Control Authority (https://www.svaca.com) was down:

HTTP code: 503
Response time: 260 ms

Resolved: Silicon Valley Animal Control Authority is back up in e1bdaa5.

repo: touzesabine/uppdownn


text:
Paste on Mobile removes pasted content immediately

When tested on Apple and Android mobile devices (both on chrome so far) the paste function is not working. As far I can tell the function is being triggered (I extended the paste delay) but as soon as the delay is up it seems the content is not found in "view" and is removed.

https://github.com/tovic/rich-text-editor/commit/a330d78ed16cbfd8dded8a55aaf9d6ed2d39bde3

authors: justlikethisdesign tovic

repo: tovic/rich-text-editor


text:
op lazy training.

Signed-off-by: ChengZi chen.zhang@zilliz.com

/lgtm
/approve

repo: towhee-io/towhee


text:
Fix/style changes to cards

Changes to cards

Added the last updated in a footer, which is nice to see for events that are coming up soon, but my question on this is we have some events that haven't been updated in awhile, does it make things look stale?
Formatted the address so that it breaks at the right point
Changed the box around the address to a line
moved links to the lower right hand corner.

Added the last updated in a footer, which is nice to see for events that are coming up soon, but my question on this is we have some events that haven't been updated in awhile, does it make things look stale?
I assume these are ongoing events (regular office hours)? Maybe we lose the "last updated" for those types of events?
Other changes look solid. A couple questions:
-Do we want the Notes to be above the address? In the examples you used it works but occasionally the Notes can be very long (such as a long list of additional speakers or co-host organizations).
-The bar color is still connected to Party and the little icon/color is connected to the event type on our map? I'm wondering if there is a cleaner way to convey these (rather than blue on blue, with each blue signifying something different).

yeah we can switch notes and address.
The headers are only connected to the type of event. Blue is for in person, purple for staff etc

So the entire header color (including icon) are representing the same thing with two different color shades? We may have already discussed this but I wonder if it's a bit confusing (assuming that one is representing party).

yeah that's right. There's nothing that indicates party by color anymore.

Love the links on the bottom right!
May I make a suggestion about the header? Right now the MOC's name seems understated and the event type icon isn't very grokable.  What if we made them columns instead?  Something like:

yeah! do you have this styled already or did you do in with screen grabs? if you have the style can you just push it to this branch?

Screen grabs I'm afraid

authors: meganrm nathanmwilliams pdvorchik

repo: townhallproject/townHallProject


text:
Add step to readme

Hey!  It's me again.  So I had to setup this project on a new machine and ran into problems when I followed the README steps.  Specifically, the
<script src="node_modules/react/umd/react.development.js"></script>
<script src="node_modules/react-dom/umd/react-dom.development.js"></script>

lines in examples/index.html were breaking because it couldn't find the files.  This is because yarn doesn't install the dependencies for examples when you run yarn install from the root.  It's a small detail but cost me ~45 minutes of trying to find a bug in the webpack config or fiddling with the path in the script src.

Hi John, thank you for the PR, it is much appreciated!
I have been meaning to get back to this project and see it to completion, your interest and help is a great motivator.
Apologies for the 45 minutes of lost time.

authors: johnmarinelli toxicFork

repo: toxicFork/react-three-renderer-fiber


text:
Adapter stürzt immer wieder ab

Hallo,
leider stürzt der Adapter nach ein paar Minuten ab. Ich nutze nur die KM200
ems-esp.0 | 2023-07-13 15:04:12.460 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason
-- | -- | -- | --
ems-esp.0 | 2023-07-13 15:04:12.459 | info | terminating
ems-esp.0 | 2023-07-13 15:04:12.456 | error | Parameter "instanceName" needs to be of type "string" but type "undefined" has been passed
ems-esp.0 | 2023-07-13 15:04:12.454 | error | Error: Parameter "instanceName" needs to be of type "string" but type "undefined" has been passed at Validator.assertString (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/validator.js:168:19) at AdapterClass.sendTo (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5014:31) at enable_state (/opt/iobroker/node_modules/iobroker.ems-esp/main.js:121:10) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.ems-esp/main.js:330:38) at process.processImmediate (node:internal/timers:473:21)
ems-esp.0 | 2023-07-13 15:04:12.453 | error | uncaught exception: Parameter "instanceName" needs to be of type "string" but type "undefined" has been passed
ems-esp.0 | 2023-07-13 15:03:12.449 | info | km200:true 300 secs
ems-esp.0 | 2023-07-13 15:03:12.449 | info | end of initializing km200 states
ems-esp.0 | 2023-07-13 15:02:45.380 | info | start initializing km200 states
ems-esp.0 | 2023-07-13 15:02:45.379 | info | write km200 file:/opt/iobroker/iobroker-data//ems-esp/0/km200.csv
ems-esp.0 | 2023-07-13 15:02:45.379 | info | End reading km200 data-structure: 109 fields found
ems-esp.0 | 2023-07-13 15:02:12.397 | info | start reading km200 data-structure
ems-esp.0 | 2023-07-13 15:02:12.071 | info | starting. Version 1.31.0 in /opt/iobroker/node_modules/iobroker.ems-esp, node: v18.7.0, js-controller: 5.0.7

Vielen Dank und Grüße :)

Was soll ich sagen, ohne die Screenshots der Adapter Parameter ???

Nimm bitte die Datenbank raus

Statistiken gehen nur mit Datenbak wie in der Readme beschrieben ... dazu brauchst Du eine akltive DB-Instanz

Ich habe die Überprüfung im Adapter angepasst.


text:
License file

Would be nice to provide license file. This helps with distro adoption. Simple license file would be enough.

true

repo: tpope/vim-pathogen

license: Vim


text:
Use canonical Michelson parser implementation to generate JSON representations

#58 added a script which generates a JSON representation of a Michelson contract to facilitate idiomatic importing of contracts into a JavaScript project. This solution outsources Michelson parsing to the @taquito/michel-codec package. Unfortunately, this package often goes out of date with respect to the protocol, encountering parse errors on valid contracts. To mitigate this, we should use a canonical implementation like the tezos-client / RPC.

Closed via #75

repo: tqtezos/minter-sdk


text:
getting error while installing

error logs
/Users/../Documents/work/ReactNative/work/../node_modules/react-native-esc-pos-printer: Command failed.
Exit code: 1
Command: node ./scripts/movelib.js
Arguments:
Directory: /Users/../Documents/work/ReactNative/work/../node_modules/react-native-esc-pos-printer
Output:
internal/modules/cjs/loader.js:905
throw err;
^
Error: Cannot find module '/Users/../Documents/work/ReactNative/work/../node_modules/react-native-esc-pos-printer/scripts/movelib.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
at internal/main/run_main_module.js:17:47 {

Fixed in v1.7.1

hi @tr3v3r  what is the major difference in v1.5.0 between v1.7.1

@devudr the only difference is that SDK for iOS is moved to a separate repo.


text:
Update sbt-github-actions to 0.15.0

About this PR
📦 Updates com.codecommit:sbt-github-actions from 0.14.2 to 0.15.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (0.14.2).
You might want to review and update them manually.
project/Dependencies.scala

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.codecommit", artifactId = "sbt-github-actions" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.codecommit", artifactId = "sbt-github-actions" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, old-version-remains, commit-count:n:2

Superseded by #195.


text:
Update bundler

What?
Update bundler to remove warning "`DidYouMean::SPELL_CHECKERS.merge!(error_name => spell_checker)' has been deprecated.", which is present many times when running spec tests.
Why?
To stop using the deprecated method.

repo: trade-tariff/trade-tariff-frontend


text:
Add Filterer responseType option

What does this PR do?
This pull request adds a new FilterResponse class and adds a responseType option to the Filterer::filter function to allow an instance of this new class to be returned.
The default return is still an array, which means it is not backwards-breaking. Additionally, the FilterResponse object can be converted to the traditional array result with its toArray() function.
Example use:
$response = Filterer::filter($spec, $value, ['responseType' => Filterer::RESPONSE_TYPE_FILTER]);
if ($response->success === false) {
   throw new FilterException($response->errorMessage);
}

return $response->filteredValue;

Checklist

[X] Pull request contains a clear definition of changes
[X] Tests (either unit, integration, or acceptance) written and passing
[X] Relevant documentation produced and/or updated

Coverage decreased (-0.4%) to 97.26% when pulling 859e1caecc2cbd91906dc80584b516dfe77b30ae on jncarver:filter-response into cc04632ec167679e7b0309b50242dab53ab9879a on traderinteractive:master.

@jncarver What advantage is gained by adding the response object?

@chadicus I find it easier to use an object with explicit properties than an array of results that are in a specific order. It's also more compact, which is helpful with line length restrictions.
The biggest difference, however, is that the original array of errors are placed into the response object, so you can iterate through them if you need to. In the traditional array response, they are combined into a newline-delimited string which can be a pain if you're trying to do anything with the errors, like provide an error count.

authors: chadicus coveralls jncarver

repo: traderinteractive/filter-php


text:
支持在tweb平台上运行

根据: https://github.com/tradingAI/proto/tree/master/model 中的输入输出， 将结果转换成相应的proto文件存储到s3中
具体实现 trunner(>=1.0.1)中的upload方法

状态信息
https://github.com/tradingAI/tbase/pull/15

repo: tradingAI/tbase


text:
feat: badge cleanup

Description
Cleaning up badge component, NB: this applies no design system changes.
This will be done, hopefully in a future step.

added missing compoundVariants programatically
added all color variants in story programatically

default color variant (gray) is duplicated to make sure it's clear to the user

cleaned up theme file

Package changes

updated rollup-plugin-typescript2 from ^0.29.0 to ^0.30.0 due to a build issue

CI: https://github.com/traefik/faency/runs/4433331267?check_suite_focus=true
https://github.com/alexjoverm/typescript-library-starter/issues/310#issuecomment-811451090

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: seedy traefiker

repo: traefik/faency


text:
Having issues with Traefik v3.2.1's RFC2136 DNS challenge for automatic Let's Encrypt certificate generation.

Traefik RFC2136 DNS Challenge TSIG Authentication Failure
Description
Having issues with Traefik v3.2.1's RFC2136 DNS challenge for automatic Let's Encrypt certificate generation. DNS updates are failing with TSIG verification errors when attempting to add/remove TXT records for domain validation.
Environment

Traefik: v3.2.1
Container Runtime: Podman 5.3.0
DNS Server: BIND 9.18.28 (Extended Support Version)
Domains:

traefik.home.doemijdienamespacemaar.nl
gitlab-tst.home.doemijdienamespacemaar.nl

Environment Variables:

RFC2136_NAMESERVER=ns3.home.doemijdienamespacemaar.nl53
RFC2136_TSIG_ALGORITHM=hmac-sha256.
RFC2136_TSIG_KEY_NAME=tsig-key
RFC2136_TSIG_SECRET=[REDACTED]
LEGO_EXPERIMENTAL_CNAME_SUPPORT=true
LEGO_LOG_LEVEL=DEBUG

BIND TSIG Key:

key name: tsig-key
algorithm: hmac-sha256
secret: [REDACTED]

System Architecture
graph LR
    T[Traefik v3.2.1]
    B[ns3.home.doemijdienamespacemaar.nl]
    LE[Let's Encrypt]

    T -->|RFC2136 Provider| B
    B -->|TSIG hmac-sha256| B
    T -->|ACME| LE
    LE -->|Verify *.home.doemijdienamespacemaar.nl| B

    subgraph Flow
        1[Request Cert] --> 2[DNS-01 Challenge]
        2 -->|RFC2136| 3[Create TXT on ns3.home.doemijdienamespacemaar.nl]
        3 --> 4[Verify ZONE home.doemijdienamespacemaar.nl]
        4 --> 5[Issue Cert]
        5 -->|RFC2136| 6[Remove TXT]
    end

Problem

Manual DNS updates using nsupdate with the same TSIG key work successfully
Traefik/Lego DNS challenge fails with TSIG verification (BADKEY) errors
Unable to automatically obtain/renew Let's Encrypt certificates

Diagnostic Steps Performed

Verified BIND version and configuration
Tested manual DNS updates using nsupdate with identical TSIG key
Enabled debug logging in both Traefik and BIND
Verified network connectivity and DNS resolution
Confirmed TSIG key format and encoding

Findings

Manual DNS updates succeed, confirming basic TSIG key functionality
Traefik's RFC2136 provider fails to authenticate with the same TSIG key
Potential issue with TSIG algorithm format (trailing dot in configuration)
Network connectivity and DNS resolution working correctly

Potential Issues Identified

TSIG algorithm format includes trailing dot (hmac-sha256.) which may cause issues
Possible mismatch in key name or case sensitivity
Potential issue in how Traefik/Lego formats the TSIG authentication

Questions

Is the trailing dot in RFC2136_TSIG_ALGORITHM=hmac-sha256. causing authentication failures?
Are there any known issues with Traefik v3.2.1's RFC2136 provider implementation?
Could there be a case sensitivity issue with the TSIG key name?

Additional Information

Full debug logs available upon request
Manual nsupdate commands work successfully
Network connectivity verified between Traefik container and BIND server
DNS resolution working correctly for all domains

Possible Workarounds Attempted

Adjusted TSIG key format and encoding
Verified DNS server configuration
Tested with different delay settings
Confirmed network connectivity and DNS resolution

Next Steps
Would appreciate guidance on:

Correct format for TSIG algorithm string
Any known issues with RFC2136 provider in Traefik v3.2.1
Additional debugging steps or configuration changes to try

Technical Configuration Details
Traefik ACME Configuration (traefik.yaml)
certificatesResolvers:
  myresolver:
    acme:
      email: "[REDACTED]"
      storage: "/var/traefik/certs/acme.json"
      dnsChallenge:
        provider: rfc2136
        delayBeforeCheck: 60

logs
1. Traefik attempts DNS-01 challenge
[INFO] [traefik.home.doemijdienamespacemaar.nl] acme: Obtaining bundled SAN certificate
[INFO] [traefik.home.doemijdienamespacemaar.nl] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/2073916237/434830476007
[INFO] [traefik.home.doemijdienamespacemaar.nl] acme: Could not find solver for: tls-alpn-01
[INFO] [traefik.home.doemijdienamespacemaar.nl] acme: Could not find solver for: http-01
[INFO] [traefik.home.doemijdienamespacemaar.nl] acme: use dns-01 solver
[INFO] [traefik.home.doemijdienamespacemaar.nl] acme: Preparing to solve DNS-01
2. DNS update fails with REFUSED
[WARN] [traefik.home.doemijdienamespacemaar.nl] acme: cleaning up failed: rfc2136: failed to insert: DNS update failed: server replied: REFUSED
3. BIND server logs showing TSIG verification failures
24-Nov-2024 11:03:22.043 error: client @0x7f8525d1c0 192.168.33.110#59813: request has invalid signature: TSIG m3razwi/f61pvbyokiglfqnuvkzfezji25bl4qzomnm=: tsig verify failure (BADKEY)
4. Final error from Traefik
[ERR] Unable to obtain ACME certificate for domains error="unable to generate a certificate for the domains [traefik.home.doemijdienamespacemaar.nl]: error: one or more domains had a problem:
[traefik.home.doemijdienamespacemaar.nl] [traefik.home.doemijdienamespacemaar.nl] acme: error presenting token: rfc2136: failed to insert: DNS update failed: server replied: REFUSED"
5. Successful manual updates from same client IP nsupdate
24-Nov-2024 12:49:56.662 info: client @0x7f842062c0 192.168.33.110#34499/key tsig-key: updating zone 'home.doemijdienamespacemaar.nl/IN': adding an RR at '_acme-challenge.test.home.doemijdienamespacemaar.nl' TXT "test-manual-update"
6  Add TXT record
$ cat /tmp/test-add.txt
server ns3.home.doemijdienamespacemaar.nl
zone home.doemijdienamespacemaar.nl
update add _acme-challenge.test.home.doemijdienamespacemaar.nl. 60 IN TXT "nsupdate-verify-test"
send
$ nsupdate -k /tmp/tsig.key -v /tmp/test-add.txt
Outgoing update query:
;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0
;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
;; ZONE SECTION:
;home.doemijdienamespacemaar.nl. IN SOA
;; UPDATE SECTION:
_acme-challenge.test.home.doemijdienamespacemaar.nl. 60 IN TXT "nsupdate-verify-test"
7. Verify record was added
$ dig @ns3.home.doemijdienamespacemaar.nl _acme-challenge.test.home.doemijdienamespacemaar.nl TXT
; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> @ns3.home.doemijdienamespacemaar.nl _acme-challenge.test.home.doemijdienamespacemaar.nl TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33094
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; ANSWER SECTION:
_acme-challenge.test.home.doemijdienamespacemaar.nl. 60 IN TXT "nsupdate-verify-test"
8. Delete TXT record
$ cat /tmp/test-del.txt
server ns3.home.doemijdienamespacemaar.nl
zone home.doemijdienamespacemaar.nl
update delete _acme-challenge.test.home.doemijdienamespacemaar.nl. TXT
send
$ nsupdate -k /tmp/tsig.key -v /tmp/test-del.txt
Outgoing update query:
;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0
;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
;; ZONE SECTION:
;home.doemijdienamespacemaar.nl. IN SOA
;; UPDATE SECTION:
_acme-challenge.test.home.doemijdienamespacemaar.nl. 0 ANY TXT
4. Verify record was deleted
$ dig @ns3.home.doemijdienamespacemaar.nl _acme-challenge.test.home.doemijdienamespacemaar.nl TXT
; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> @ns3.home.doemijdienamespacemaar.nl _acme-challenge.test.home.doemijdienamespacemaar.nl TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62118
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; AUTHORITY SECTION:
home.doemijdienamespacemaar.nl. 7200 IN SOA ns3.home.doemijdienamespacemaar.nl. info.doemijdiemailmaar.nl. 50 43200 900 1814400 7200

Hello,
There is no specific implementation of this DNS challenge inside Traefik, I recommend opening an issue on the lego repository, I will answer you in this new issue.

authors: RobertWi ldez

repo: traefik/traefik