Support ARM syscalls in QEMU

Checking BIL using the concrete executor revealed incorrect register values in QIRA following syscalls on ARM. In the QEMU mods, I found the code that handles this on x86 and extended it using the same technique (checking the translation buffer helper function to know when an interrupt is raised).
@geohot While this fixed the bug I experienced (registers are correct following syscalls now), I have a couple of questions that might make this patch more complete.
Snippet 1:
#ifdef R_EAX
    if (flags & IS_SYSCALL) {
      // replay all the syscalls?
      // skip reads
      if (pchange.address == FAKE_SYSCALL_LOADSEG) {
        //printf("LOAD_SEG!\n");
        helper_load_seg(env, pchange.data >> 32, pchange.data & 0xFFFFFFFF);
      } else if (pchange.address != 3) {
        env->regs[R_EAX] = do_syscall(env, env->regs[R_EAX], env->regs[R_EBX], env->regs[R_ECX], env->regs[R_EDX], env->regs[R_ESI], env->regs[R_EDI], env->regs[R_EBP], 0, 0);
      }
    }
#endif

Snippet 2:
#ifdef R_EAX
            struct change *a = NULL;

            if ((void*)t0 == helper_load_seg) {
              if (GLOBAL_logstate->is_filtered == 1) {
                commit_pending_changes();
              }
              a = track_syscall_begin(env, FAKE_SYSCALL_LOADSEG);
              a->data = a1<<32 | a2;
              //printf("LOAD SEG %x %x %x %x\n", a0, a1, a2, a3);
            } else if ((void*)t0 == helper_raise_interrupt) {
              if (GLOBAL_logstate->is_filtered == 1) {
                commit_pending_changes();
                // syscalls always get a change?
                /*GLOBAL_logstate->changelist_number++;
                add_change(tb->pc, tb->size, IS_START);*/
              }
              a = track_syscall_begin(env, env->regs[R_EAX]);
              GLOBAL_last_was_syscall = 1;
            }
#endif
#ifdef TARGET_ARM
            struct change *a = NULL;
            if ((void*)t0 == helper_exception_with_syndrome) {
              if (GLOBAL_logstate->is_filtered == 1) {
                commit_pending_changes();
              }
              a = track_syscall_begin(env, env->regs[0]);
              GLOBAL_last_was_syscall = 1;
            }
#endif

You can see that I've added the case for ARM in the second snippet for tracking syscalls. In both snippets there seems to be code related to segment loading, but I'm not sure what it's doing. Could you enlighten me? I might as well handle these while I'm at it in this pull request if it's relevant.
Sorry that there's a bit of noise in the patch due to how my diff got generated (diffing a diff, yo dawg).

If the QEMU op "helper_load_seg" is called, I treat it like a syscall. Note this has nothing to do with ELF segments, it's for x86 segment registers, it's prototype is "void helper_load_seg (CPUX86State *env, int seg_reg, int selector)" So on ARM you shouldn't have to worry about this.

Ok, I thought it was x86-specific but I wanted to be sure. This change should be safe to merge then as I tested over most of our ARM coreutils corpus and it didn't seem to introduce any regressions.


WFLY-18024 CacheIdentity and IdentityContainer instances are replicating unnecessarily

https://issues.redhat.com/browse/WFLY-18024

@rhusar if you can please give this a review I may be able to include it in the next batch of merges


Option oneauthor does not work

Option one author does not work. Even after changing the doc-class.tex file to include an option to use it, the .tex file generates an empty Author field, meaning no author shows up.

So I found the error in title.tex file: The author if condition is working but it is not actually inputting the author when it is only one. Fixed it with a for loop although I am not sure if it is the correct way of implementing it.


dictator's output is empty.

hi,
I have tried to generate a dictionary for a web html file, but the result is empty as you can see the size of out file is 0 byte.  Does anyone knows why? Plus, I have another question, can the dictionary generated (if success) be used in brotli? thanks.
$ go run dictator.go -in src.html.orig -out src.html.dict
100%
Total incompressible strings found:  0
$ ls -l
total 72
1403 5月  19 15:56 dictator.go
0 5月  19 16:08 src.html.dict
65889 5月  19 15:50 src.html.orig

Hi,

go run dictator.go -in src.html.orig -out src.html.dict

You have to specify a folder, not a single file. If you must generate a dictionary for one file, create a directory that contains that file.

can the dictionary generated (if success) be used in brotli? thanks.

No, it is incompatible with brotli, and brotli contains a built in dictionary. This dictionary is only for deflate.

The dictionaries generated actually work reasonably well for brotli although they're not optimal.

Great thanks. Vkrasnov. It did work after I put it in a folder.

hi hatstand,
The dictionary in brotli looks like a hash  table, which is quite different with this script generated. Do you have any suggestion about how to use it?

It's not a hash table, it's just a bunch of bytes, the same as the output of dictator.


Adding x-terminal to atom

https://github.com/bus-stop/x-terminal/issues/108

[ ] Merge the open pull requests:

[ ] Use editor font for terminal
[ ] detect the best shell

https://github.com/bus-stop/x-terminal/pulls

[ ] Bundle X-terminal using Rollup or Parcel. This will improve performance, as well as making the integration easy (Electron link doesn't need to do anything).

[ ] set up a syncronized fork if they did not merge the changes.

Are we gonna do this or no (e.g. keep it as a separate package)

We're going to add Terminal:
https://github.com/atom-community/terminal


Remove runtime requirements on nose, mock, flake8

This library currently lists runtime requirements on testing libraries like nose, mock, and flake8 in requirements.txt.  Are these libraries necessary for using kazoo or are they only necessary for testing?  If the latter then you may prefer to not list them as installation requirements.  This can cause some bloat for downstream users, especially those in constrained environments like docker containers.

After looking at this a little, I'm confused. Typically, installation requirements for a library are defined in setup.py, and any requirements.txt is typically only used when hacking on the library.
Currently setup.py only lists six as a dependency: https://github.com/python-zk/kazoo/blob/master/setup.py#L20
Requirements.txt lists those extra dependencies because it's used for dev/testing purposes, where you would want those libs.
Do I miss something?

OK, my mistake.  Closing.b


Add Makefile

This PR provides a self-documenting Makefile for handling all low-level operations such as:

Building the docs
Building the distribution files
Running code checks (linting, type checking, security)
Running unit tests and calculating test coverage

New Features

New Makefile added --> Type make to view the documentation

Updates to Database schemas
N/A
Specific Feedback Requested
N/A bar module
Jira Tickets
N/A
Linked to
Closes #4

Codecov Report

Merging #14 (621e76f) into develop (b3126da) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           develop       #14   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            5         5
=========================================
  Hits             5         5

Continue to review full report at Codecov.

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


readyForStable.js: log url next to adaptername

solves: https://github.com/ioBroker/ioBroker.repositories/issues/2338


Escapse % and _ in sql

Fixes #1079 .

LGTM, let's hold on till the build on travis has recovered.

Changes Unknown when pulling fac6b244af1553870b15b4c30584fb419316e28c on ywk253100:161116_sql_wildcard into ** on vmware:dev**.

Changes Unknown when pulling 1b01a693dd14281afbc8168f4e4c43043677390c on ywk253100:161116_sql_wildcard into ** on vmware:dev**.

Coverage decreased (-24.01%) to 27.183% when pulling 157cbd0fbd8510d2d0371f3b76887eb55f404c09 on ywk253100:161116_sql_wildcard into f867ff42a06783d05862cd38447c56289faf3915 on vmware:dev.

Coverage increased (+0.03%) to 51.231% when pulling a64891103df883015435ff247c62c9e584ae6405 on ywk253100:161116_sql_wildcard into 05e9a17d5a7819751b70849817dba2959d78b3a1 on vmware:dev.

LGTM, thanks.


Getting "no main packages" error

I have two projects with main package, etc
I do
 go-callvis gitlab.my.service/server-side/project
or
 go-callvis gitlab.my.service/server-side/another
One of projects uses cobra package and another one does not.
I get error

no main packages

What can I do to fix it?

My main package was not in a root dir of a project. I should call it like
o-callvis gitlab.my.service/server-side/project/cmd


Fix cheatsheet for conditionals

I was writing a scenario with some conditionals, and noticed that the cheatsheet docs for conditionals weren't quite right:

No entry for doIfEquals
The parameters for doIf in the cheatsheet are (actual, expected), but it should be a single expression parameter (or something which can be implicitly converted to one)

I've fixed those in this pull request. I've tried to stick with the conventions in the existing cheatsheet entries, which give a quick summary of the usage without going into all the possibilities provided by implicit conversion.

@suzannehamilton Thanks a lot!
cherry-picked as fdf5a8f06a9fa0fe59194f949c96a2ecf7b1dee7


Pin the version for current operators

/hold

/ok-to-test

/ok-to-test

Test is currently failing as it is the installPlanApproval is Manual.
The CSV is not being created or approved, which is currently blocking the test from moving on.
If we'd like to set the installPlanApproval to Manual, we can potentially update the test logic to wait for and approve the installplans, rather than expecting the installPlan to automatically be approved.

Temp close this PR, after done the upgrade test.


Testing

Running presubmits at https://istio-testing.appspot.com/job/istio-testing/job/pr-master/1/ ...

istio-testing/pr-master passed. Details at https://istio-testing.appspot.com/job/istio-testing/job/pr-master/1/.

Running presubmits at https://istio-testing.appspot.com/job/istio-testing/job/pr-master/3/ ...

istio-testing/pr-master passed. Details at https://istio-testing.appspot.com/job/istio-testing/job/pr-master/3/.


cuDNN v8.8.0 for aarch64 + CUDA 12 is not consumable by recipe maintainers

When working on https://github.com/conda-forge/cupy-feedstock/pull/199 I noticed I kept hitting this mysterious error:
586 Mamba failed to solve:
587 - cython >=0.29.22,<3
588 - pip
589 - libcufft-dev
590 - fastrlock >=0.5
591 - cudnn >=7.6
592 - libcublas-dev
593 - cutensor >=1.4,<2
594 - libcusparse-dev
595 - cuda-cccl_linux-aarch64
596 - python 3.10.* *_cpython
597 - libcusolver-dev
598 - cuda-profiler-api
599 - libcurand-dev
600 - cuda-nvrtc-dev
601 - cuda-version 12.0.*
602 - cuda-driver-dev
603 - setuptools
604 - cuda-cudart-dev
605 - python
606 - cuda-nvtx-dev
607
608with channels:
609
610The reported errors are:
611- Encountered problems while solving:
612-   - package libcurand-dev-<IP_ADDRESS>-ha21bd82_0 requires cuda-version >=12.0.0,<12.1.0a0, but none of the providers can be installed
613-
614
615Leaving build/test directories:
616  Work:
617 /home/conda/feedstock_root/build_artifacts/work
618  Test:
619 /home/conda/feedstock_root/build_artifacts/test_tmp
620Leaving build/test environments:
621  Test:
622source activate  /home/conda/feedstock_root/build_artifacts/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_
623  Build:
624source activate  /home/conda/feedstock_root/build_artifacts/_build_env
625
626
627Traceback (most recent call last):
628  File "/opt/conda/lib/python3.10/site-packages/boa/cli/mambabuild.py", line 141, in mamba_get_install_actions
629    solution = solver.solve_for_action(_specs, prefix)
630  File "/opt/conda/lib/python3.10/site-packages/boa/core/solver.py", line 230, in solve_for_action
631    t = self.solve(specs)
632  File "/opt/conda/lib/python3.10/site-packages/boa/core/solver.py", line 220, in solve
633    raise RuntimeError("Solver could not find solution." + error_string)
634RuntimeError: Solver could not find solution.Mamba failed to solve:
635 - cython >=0.29.22,<3
636 - pip
637 - libcufft-dev
638 - fastrlock >=0.5
639 - cudnn >=7.6
640 - libcublas-dev
641 - cutensor >=1.4,<2
642 - libcusparse-dev
643 - cuda-cccl_linux-aarch64
644 - python 3.10.* *_cpython
645 - libcusolver-dev
646 - cuda-profiler-api
647 - libcurand-dev
648 - cuda-nvrtc-dev
649 - cuda-version 12.0.*
650 - cuda-driver-dev
651 - setuptools
652 - cuda-cudart-dev
653 - python
654 - cuda-nvtx-dev
655
656with channels:
657
658The reported errors are:
659- Encountered problems while solving:
660-   - package libcurand-dev-<IP_ADDRESS>-ha21bd82_0 requires cuda-version >=12.0.0,<12.1.0a0, but none of the providers can be installed
661-
662
663During handling of the above exception, another exception occurred:
664
665Traceback (most recent call last):
666  File "/opt/conda/bin/conda-mambabuild", line 10, in <module>
667    sys.exit(main())
668  File "/opt/conda/lib/python3.10/site-packages/boa/cli/mambabuild.py", line 256, in main
669    call_conda_build(action, config)
670  File "/opt/conda/lib/python3.10/site-packages/boa/cli/mambabuild.py", line 228, in call_conda_build
671    result = api.build(
672  File "/opt/conda/lib/python3.10/site-packages/conda_build/api.py", line 180, in build
673    return build_tree(
674  File "/opt/conda/lib/python3.10/site-packages/conda_build/build.py", line 3078, in build_tree
675    packages_from_this = build(metadata, stats,
676  File "/opt/conda/lib/python3.10/site-packages/conda_build/build.py", line 2038, in build
677    output_metas = expand_outputs([(m, need_source_download, need_reparse_in_env)])
678  File "/opt/conda/lib/python3.10/site-packages/conda_build/render.py", line 787, in expand_outputs
679    for (output_dict, m) in deepcopy(_m).get_output_metadata_set(permit_unsatisfiable_variants=False):
680  File "/opt/conda/lib/python3.10/site-packages/conda_build/metadata.py", line 2524, in get_output_metadata_set
681    conda_packages = finalize_outputs_pass(
682  File "/opt/conda/lib/python3.10/site-packages/conda_build/metadata.py", line 879, in finalize_outputs_pass
683    parent_metadata.parse_until_resolved()
684  File "/opt/conda/lib/python3.10/site-packages/conda_build/metadata.py", line 1270, in parse_until_resolved
685    self.parse_again(
686  File "/opt/conda/lib/python3.10/site-packages/conda_build/metadata.py", line 1167, in parse_again
687    self._get_contents(
688  File "/opt/conda/lib/python3.10/site-packages/conda_build/metadata.py", line 1872, in _get_contents
689    rendered = template.render(environment=env)
690  File "/opt/conda/lib/python3.10/site-packages/jinja2/environment.py", line 1301, in render
691    self.environment.handle_exception()
692  File "/opt/conda/lib/python3.10/site-packages/jinja2/environment.py", line 936, in handle_exception
693    raise rewrite_traceback_stack(source=source)
694  File "/home/conda/recipe_root/meta.yaml", line 105, in top-level template code
695    - pip
696  File "/opt/conda/lib/python3.10/site-packages/conda_build/jinja_context.py", line 234, in pin_compatible
697    pins, _, _ = get_env_dependencies(m, 'host', m.config.variant)
698  File "/opt/conda/lib/python3.10/site-packages/conda_build/render.py", line 131, in get_env_dependencies
699    actions = environ.get_install_actions(tmpdir, tuple(dependencies), env,
700  File "/opt/conda/lib/python3.10/site-packages/boa/cli/mambabuild.py", line 150, in mamba_get_install_actions
701    raise err
702conda_build.exceptions.DependencyNeedsBuildingError: Unsatisfiable dependencies for platform linux-aarch64: {MatchSpec("cuda-version[version='>=12.0.0,<12.1.0a0']"), MatchSpec("libcurand-dev==<IP_ADDRESS>=ha21bd82_0")}
703The command "if [[ ${PLATFORM} =~ .*linux.* ]]; then CONDA_FORGE_DOCKER_RUN_ARGS="--network=host --security-opt=seccomp=unconfined" travis_wait 120 ./.scripts/run_docker_build.sh; fi" exited with 1.

After some digging it turns out to be a cudnn issue. @jakirkham came up with the idea, and I confirmed locally, that it's due to the glibc requirement, which was worked around in #56 by using a newer docker image, but this workaround does not propagate to downstream recipes. Apparently, the solver got confused and did not complain about glibc, but instead mistakenly complained about something irrelevant.

xref: https://github.com/conda-forge/cupy-feedstock/pull/223#issuecomment-1699359837

@conda-forge-admin , please re-render


Highlight doesn't work on Github properly

Steps:

Open https://github.com/raindropio/app
Highlight this text: "Mono repo for Raindrop.io web app, browser extension and desktop app"
Highlight this text: "Be sure to run npm i before calling any commands below"
Reload page just to make sure

Expected:
Both texts to be highlighted
Actual:
Even though both highlights are saved only the second text is highlighted

This is just an example and this issue happens on big chunk of Github.

Even though as far as I can see you don't welcome development contributions, I'm still offering it in case you change your mind.

Fixed


[feature request] analyze command

It would be nice to have a command that compiles the models with an analyze so that we can see Redshift query plans, either for the whole project or scoped to given models. Even better would be if it could return some kind of stats or warnings about queries with performance issues.

I love this idea -- it looks like Snowflake has something like an explain as well. Not sure if there's an equivalent for big query.
I think coming up with stats or warnings might be tough in the generic case -- though with redshift you could sum up the number of DS_DIST_BOTH s. Not sure what the equivalents would be for non-Redshift warehouses.
At least getting the feature out to generate the plans would be great, then we can figure out how to analyze them in the future.


window.open() method returning a null object in IE

window.open() method returning a null object in IE but in crome, mozila, safari it returning a object
due to this opened popup window is not closing after successful login. I think this is because CORS
is there any workaround to get it working in IE also?

I think this must be related. In IE, when trying to authenticate with code below:
function authenticate() {
			$auth.authenticate('identityServerForMyProject')
				.then(function () {
					console.log('You have successfully signed in with identityServerForMyProject!');
					$state.go('stateThatGoesAfterLogin');
				})
				.catch(function (error) {
					if (error.message) {
						console.log('Error message: ' + error.message);
					} else if (error.data) {
						console.log('Error message: ' + error.data.message, error.status);
					} else {
						console.log('Error message: ' + error);
					}
				});
		}

When redirectUri is set to a valid page i get the following output immediately after the popup opens: Error message: The popup window was closed
When redirectUri is set to something that will return 404, there'll be no output, and after logging in, the popup window won't close.
This is on Angluar 1.5.8 & Satellizer 0.15.4


scitail evaluator and dummy data

@tusharkhot, here's an initial pass at a SciTail evaluator. I made up some IDs for each sentence pair; that can be changed easily. The data/README.md file should be updated to explain how it was made.

@tusharkhot i moved some things around. Have a look.

I like the new re-org. I will test predictions from one of my models to catch any potential issues.


Cannot close tab in latest bracket

MAC OS, every time I try to close the tab with the x button in the tab, it will open a new tab. It has been after I upgraded to
Release 1.6 build 1.6.0-16680 (release 3df0ac6fa)
build timestamp: Tue Jan 12 2016 05:35:00 GMT-0800

Is this a bug report for Atom? Or Brackets? This is the repository for the Atom editor. Our build information doesn't look like that.

I'm going to assume this is Brackets since their 1.6.0 version was released on January 12 as commit adobe/brackets@3df0ac6fa18b1ccfc34f6d234da2aa8c43643a93, which conveniently matches with the release info @oeichenwei reported.
@oeichenwei please report this instead to https://github.com/adobe/brackets/issues.  Thanks!


[ADAP-954] [Bug] Missing container package for dbt-bigquery-1.6.7

Is this a new bug in dbt-bigquery?

[X] I believe this is a new bug in dbt-bigquery
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
The last package in the container registry is for dbt-bigquery-1.6.6. Since dbt-bigquery-1.6.7 was released on October 9, which fixes the labels issue , our team was upgrading it on a high priority. If this image can be pushed to the container registry, it will  unblock our update process.
Expected Behavior
I expect to be able to use the latest container image (dbt-bigquery-1.6.7) for in Cloud run on GCP and update our CI/CD pipeline.
Steps To Reproduce
My cloud build.yaml
steps:
  - name: 'ghcr.io/dbt-labs/dbt-bigquery:1.6.7'
    args:
      - docs
      - generate
      - '--target-path'
      - .
      - '--project-dir'
      - ../../environment/development/team/
      - '--profiles-dir'
      - ../../environment/development/team/
    dir: docs/data_systems/
    entrypoint: dbt
options:
  logging: CLOUD_LOGGING_ONLY

Relevant log output
No response
Environment
- OS:
- Python:
- dbt-core:
- dbt-bigquery:

Additional Context
No response

Thanks for pointing out the miss here, 1.6.7 should be available now


[WIP / Prototype] Use TextMate themes for syntax highlighting

I'm curious how this performs compared to Vim syntax highlighting? Did you consider creating an at-startup-time conversion from a textmate theme to a Vim highlighting scheme as opposed to the more dynamic version?

Unfortunately, Vim syntax highlighting doesn't quite match parity-wise with TextMate's tokenization. Vim syntax highlighting makes some tradeoffs such that it doesn't need to parse the entire file (which makes it faster!) but also more limited. TextMate's tokenization allows carrying a rulestack for each token which gives a semblance of what scopes are available - the VSCode team has a great write-up here: https://code.visualstudio.com/blogs/2017/02/08/syntax-highlighting-optimizations
In other words, AFAIK, there unfortunately isn't a lossless conversion of TextMate tokenization -> vim syntax highlighting.
There are a couple other things I plan on using this for (besides just coloring):

Querying to see what scope a particular token is in - this is important for things like auto-pairs - maybe we don't want a particular character enabled in comments, for example. It's not straightforward at the moment to ask what syntax a particular character has. Also, we might not want to show hover in comments, for example.
Alternative visualizations of the code (like a minimap view)

The degenerate case for performance is the bottom of a large file - since you need to evaluate the ruleStack for all previous lines, at least the first time you navigate to the bottom. The parsing is relatively quick (vscode-textmate is great, and bundles a native parser called oniguruma!), but it is synchronous and for large amount of lines it can add up. Batching is possible - but in the worst case you end up with a brief FOUC (well, in this case, it'd be 'flash of partially styled content' - we'd use the vim syntax theme as a base, and only style additional elements on top of that), but better than hurting the responsiveness. This current implementation isn't fully optimized yet.
Some discussion in Neovim too here: https://github.com/neovim/neovim/issues/6052 (about natively supporting it, and limitations of the current model).


Unable to complete rFOX Bridge

Overview
When attempting to stake FOX on Ethereum via the rFOX page the bridge step never completes.
References and additional details
Se Jam for a reproduction: https://jam.dev/c/87551814-3dec-4425-a25e-a3cb6038d158
Error thrown, which is possibly related: No retryable data found in error at L1ToL2MessageGasEstimator.populateFunctionParams

Acceptance Criteria
Can successfully bridge FOX from Ethereum to Arbitrum via the rFOX stake workflow.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

This is not actually an issue - I suspect the ops testing just didn't wait long enough for the Arb-side TX to complete.
It works just fine in production:

This is not actually an issue - I suspect the ops testing just didn't wait long enough for the Arb-side TX to complete.
It works just fine in production:

@0xApotheosis indeed, that error is expected! Though we could probably swallow it.
re: bridge taking 5-15mn, those kind of spotted bugs that actually aren't are usually the symptom of a confusing behavior: if ops are confused, users would definitely be.
@twblack88 how about we add some lil explainer there that things may take some time to complete? (Usually 7 minutes from all my testing but can be up to 15 technically)


Fixing minor typo

@AlecPapierniak,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

@AlecPapierniak, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, .NET Foundation Pull Request Bot

@AlecPapierniak, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, .NET Foundation Pull Request Bot


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/44882

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63162


Try Code Inspector

Description
Related links

https://frontend.code-inspector.com/home

https://frontend.code-inspector.com/project/11254/dashboard

Close


Add zero-amount Receive Chain Swap

Fixes #519
Open questions:

[x] Proper way to show fees during prepare/pay: "X sat + Y% of the sent amount" ?
[x] Include min/max in prepare_response? How else to communicate them to caller, as they are now essential?

Also: it's important they exactly match the ones for the pair hash used in creating the swap

[ ] Should such a (refundable) swap require user interaction to "try to claim"?

Or should the SDK try to claim automatically when a lockup is detected (or on lockupFailed event)?

[ ] How to reflect in DB: set payer_amount_sat to 0 for zero-amount swaps? Or NULL (DB migration)?

Should such a (refundable) swap require user interaction to "try to claim"?

Or should the SDK try to claim automatically when a lockup is detected (or on lockupFailed event)?

The SDK user has to provide a fee rate for these refunds, so they need to be manually handled

It's not about refunds per se. The zero-amount swaps get the TransactionLockupFailed event when the user locks up funds. At this point, it would be indistinguishable from a refundable.
However it will not become an actual refundable when the user locks up funds, because when the zero-amount swap gets this event, we are getting and confirming the so-called quote from Boltz. By confirming it, we tell Boltz they should proceed with this swap (e.g. create the server lockup tx, etc). My question above was about this "getting and confirming" the quote. However we clarified in an earlier call that no user interaction should be needed to claim, so therefore we get and auto-confirm the quote.
Hopefully this clarifies the confusion.


Remove outdated instructions to integrate the bundle with Monolog

The instructions in the README that explain how to integrate the bundle with Monolog are outdated: we could fix them without too much effort, but I would rather remove them and make the official documentation the only source of truth for this kind of things like it's done in the core SDK (no instructions at all besides how to install the package in the repo). This will also reduce the burden of maintenance because there is just one place that has to be kept up-to-date with the changes

@ste93cry I'm curious where this is documented now? I think currently the correct way would be:
sentry:
    register_error_listener: false # Disables the ErrorListener
    dsn: "%env(SENTRY_DSN)%"

# monolog configuration for sentry
# see also: https://github.com/getsentry/sentry-symfony/blob/3.5.3/README.md#optional-use-monolog-handler-provided-by-sentrysentry-available-since-320
monolog:
    handlers:
        sentry:
            type: service
            id: Sentry\Monolog\Handler

services:
    Monolog\Processor\PsrLogMessageProcessor:
        tags: { name: monolog.processor, handler: sentry }

    Sentry\Monolog\Handler:
        arguments:
            $hub: Sentry\State\HubInterface
            $level: error

but I'm not 100% sure 🙈

I'm curious where this is documented now

It's not, we still have to update the official documentation, I'm sorry!

I think currently the correct way would be

You can find an example in the UPGRADE-4.0.md file, but generally speaking yes, how you did it should be fine 😉

@ste93cry Thank you for the response. I created a PR to the docs hope its the correct place: https://github.com/getsentry/sentry-docs/pull/3137/files


'import DOT' is missing from the ReadMe example

Title says is all !?
PS : really enjoying this project

Thanks for pointing this out, @maxwacker. Apologies for any confusion or inconvenience. I plan to merge this into a single module in a future release.


Ensure atom names are unique after construction

This PR adds a Molecule._validate() method that is called after all molecule construction events as a way to run any code required to standardize or otherwise validate the constructed Molecule object.
This PR also fixes #460 by ensuring that unique atom names are generated at this time if the specified atom names are not unique. Note that this may cause atom names to change if some were defined, but not all were unique.
This is done via addition of Molecule.has_unique_atom_names property and a Molecule.generate_unique_atom_names() public method.
There are some alternative strategies discussed in #460, but as https://github.com/openforcefield/openforcefield/issues/460#issuecomment-559136868 points out, if we're going to be standardizing on SDF files (which lack atom names), we need to do something to ensure unique atom names are generated by the time we need to use them.
Additionally, two tests were added:

A SMILES round-trip test, which discovered that it is impossible to do this for molecules that are perceived as lacking stereochemistry
A test for all new added methods

[x] Tag issue being addressed
[x] Add tests
[x] Update docstrings/documentation, if applicable
[x] Update changelog

The failing test here also involves a phosphorous containing molecule ([H]C([H])([H])P(=O)([H])[O-]) suggesting #467 extends to phosphorous as well.

Correction: The minidrugbank phosphorous-containing molecule actually has a stereocenter because its substituents are different:
With the RDKit backend:
>>> Molecule.from_smiles('[H]C([H])([H])P(=O)([H])[O-]')
---------------------------------------------------------------------------
UndefinedStereochemistryError             Traceback (most recent call last)
<ipython-input-14-9e8e428709fa> in <module>
----> 1 Molecule.from_smiles('[H]C([H])([H])P(=O)([H])[O-]')

~/miniconda/lib/python3.7/site-packages/openforcefield/topology/molecule.py in from_smiles(smiles, hydrogens_are_explicit, toolkit_registry, allow_undefined_stereo)

~/miniconda/lib/python3.7/site-packages/openforcefield/utils/toolkits.py in call(self, method_name, *args, **kwargs)

~/miniconda/lib/python3.7/site-packages/openforcefield/utils/toolkits.py in from_smiles(self, smiles, hydrogens_are_explicit, allow_undefined_stereo)

~/miniconda/lib/python3.7/site-packages/openforcefield/utils/toolkits.py in _detect_undefined_stereo(cls, rdmol, err_msg_prefix, raise_warning)

UndefinedStereochemistryError: Unable to make OFFMol from RDMol: Unable to make OFFMol from SMILES: RDMol has unspecified stereochemistry. Undefined chiral centers are:
 - Atom P (index 4)

Perhaps we shouldn't be using minidrugbank, or we should filter out the compounds that contain unspecified stereochemistry?

The remaining test failures appear to be due to the SMILES round-trip tests failing because we have some molecules in minidrugbank that have unspecified stereochemistry, yet we load them all in for testing.
What approach should we take with these? Should we skip molecules with unspecified stereochemistry in our round-trip tests?

I think that making the user call it manually is more in line with our philosophy

I'm worried that our philosophy is trending toward "annoy the hell out of the user by preventing them from ever doing anything easily with lots of small molecules". As it is right now, the user cannot use our tools to, say,

Process a bunch of SMILES strings that might contain undefined stereochemistry, or even any trivalent sulfur atoms because of presumed stereochemistry atoms
Process any SDF files because these lack atom names, even though we have standardized on SDF files
Process a bunch of molecules from OpenEye or RDKit that may not have unique atom names

I agree that the philosophy of "raise an informative Exception subclass object for each error type that the user must correct" can be an effective way to make sure the user is informed of each and every criteria their molecules must meet to be properly processed, but I can guarantee that this is going to cause a great deal of frustration.
Is there some way we can provide both a "paranoid mode" (where we ensure that we are typing exactly the molecule the user wants) and some sort of "just process these molecules mode" where molecules that don't pass our strict criteria are either transformed into a processable form or are dropped from the list?
Even dropping may be problematic, because---as was pointed out previously---we are standardizing on SDF files, which do not have atom names, which I believe makes it impossible to transform the resulting system to AMBER/gromacs with ParmEd.
If we were following the "principle of least surprise", I'd probably suggest the behavior where missing atom names are filled in silently with unique atom names that do not collide with any existing atom names, but an exception is raised if two user-specified atom names are identical. That would allow processing of molecules without issue in a manner that would not change any atom names the user specified, but would raise an exception if the user-specified atom names caused a problem. Otherwise, they'd be filled in so things just work.

I noted this above, but it's important enough to state again here:
Once we ditch ParmEd, it will no longer be necessary to generate unique atom names. But until we replace it, we're stick with the need to do so if we want our parameters to be deliverable to different molecular simulation packages.
That means that this needs to either happen to all molecules we load into the toolkit, or it means we need to create more code to manage the transformation to other packages that does this silently behind the scenes. That may be an alternative to this approach that is workable!

I wrote a lot, but it boils down to this:

If we were following the "principle of least surprise", I'd probably suggest the behavior where missing atom names are filled in silently with unique atom names that do not collide with any existing atom names, but an exception is raised if two user-specified atom names are identical. That would allow processing of molecules without issue in a manner that would not change any atom names the user specified, but would raise an exception if the user-specified atom names caused a problem. Otherwise, they'd be filled in so things just work.

We do this, at the time of system creation.
So, either we

make a new function, create_parmed_structure, which runs your quoted algorithm after create_openmm_system to make the resulting system parmed-friendly; or
we do this by default in create_openmm_system, since I don't think atom names have a functional effect in OpenMM, so no harm done.

To be a little less brief on my reasoning: I think we need to keep our internal data structures clear of ParmEd's influence. The above discussion was driving us to choose a group of users to lose. Either:

People who want to export to ParmEd inconveniently need to run offmol.generate_atom_names; or
A person who uses OFFTK to generate conformers for alanine dipeptide puts in a molecule with two CAs and gets back conformers with C2 and C5 in their place

When really, we can just push this battle outside our borders -- Make the users identify where these parameters are going, and apply naming that works for ParmEd if that's the destination.
And maybe the second option doesn't seem too bad, but the slope toward ParmEd-ness becomes no less steep if we accept that behavior.  We just get into the "if you give a moose a muffin" situation -- If we rename the alanine atoms above, users will say "well, they're just in different residues, OFFTK should allow that". Then we'll be pushed to enforce some system of rules around atom names and residue names/numbers, in a toolkit made specifically not to care about atom types or topological residues. People will make workflows assuming the atom names we assign, and contort their inputs to satisfy the residue rules we enforce, and then we'll have this large set of expected behaviors causing friction on further developments (do virtual sites also need unique names? do we support chains?).
On a separate note:
I agree that the undefined stereochemistry thing is ugly and awkward. It may not be worth it on some fronts. I'd be open to arguments that we should just drop it for trivalent nitrogen and sulfur -- We could say stereochemistry that exchanges more frequently than once per millisecond is not stereochemistry at all for the purposes of atomistic simulation. This will be made easier by breaking out a OFF-core package, where we can keep all the rules that define our complicated stereochemistry definition in one consistent place.

@j-wags : I like your suggestions in https://github.com/openforcefield/openforcefield/pull/469#issuecomment-565669245! I'd be fine with this, but don't have the bandwidth to re-work this PR anytime soon. Should be an easy fix, though!
The only thing I'd caution about is that the wider the separation between doing the thing that triggers an error (converting a molecule with defective atom names) and the error (creating a system), the harder it is for our users to identify where the error was actually committed! So we have to help them along as much as possible by being maximally informative in our error messages.

I agree that the undefined stereochemistry thing is ugly and awkward. It may not be worth it on some fronts. I'd be open to arguments that we should just drop it for trivalent nitrogen and sulfur -- We could say stereochemistry that exchanges more frequently than once per millisecond is not stereochemistry at all for the purposes of atomistic simulation. This will be made easier by breaking out a OFF-core package, where we can keep all the code that enforces our specific stereochemistry definition in one single place.

I still like the idea of an openforcefield-core package!
Another approach that would make our lives easier is to just say we're not going to care about stereochemistry in charge models, and that any model we ultimately adopt would have to somehow average over all possible stereochemical configurations. That would make the cheminformatics easy, but it may ultimately limit accuracy.

@j-wags: How should we proceed here?
We're not going to be able to use SDF files and ParmEd to convert to other packages unless we implement something like this now, and I'd love to get this finished before the master branch diverges too much.

@j-wags: How should we proceed here?

@j-wags: How should we proceed here?

I'll:

[ ] change create_openmm_system to assign atom names, using your algorithm in this PR
[ ] disable validation for all molecules, but keep Molecule.generate_unique_atom_names and Molecule.has_unique_atom_names  and their tests.
[ ] cherry pick https://github.com/openforcefield/openforcefield/pull/486/commits/14c1d2f3b21b695f95acd96e85f5bb0e11ce71f9 to get the SMILES roundtrip tests working

Oh, OpenMM Systems don't have atom names. Only OpenMM Topologys do. So a to-do item is

[ ] add kwarg ensure_unique_atom_names to Topology.to_openmm, using your algorithm in this PR

Codecov Report

Merging #469 into master will not change coverage.
The diff coverage is n/a.


Added "Resolution" section

Added "Resolution" section with the first analysis step.

@tedhudek - This PR is ready to go live when you have a minute.


feat: add ready-to-test command and independent container registry

We introduce a new behaviour in this commit:
1.- The commits now can run in the forked repo, using the external
user registry to push the image and the run the E2E.
2.- A new command ready-to-test that use the pull_request_target
event to run the test and run the E2E test on the PR, this will
allow the forked repo to run test from the PR when a user allows it.
Previously we were not able to run the E2E on PR from forked repo
due to the fixed use of the cloudnative-pg repo and since the
pull_request event doesn't provide a GitHub token with write permissions
for packages.
We still allow running E2E test from internal branch only when the test
command is used, since it will trigger the event dispatch with the client
payload and is used to verify that comes from the internal repo.
Closes #426
Signed-off-by: Jonathan Gonzalez V<EMAIL_ADDRESS>

/test

/ok-to-merge


Add new worker to back of fifo queue

Observed situation where worker crashes and next client process gets the new worker. Unfortunately the new worker might be busy asynchronously starting, for example when the worker is setting up a tcp connection. If there is another worker it would be nice for the client to get that worker as it is more likely to be ready. Using the fifo strategy fits nicely with the existing options to help solve this as other workers will be checked out before the new worker - if there are any.
This fix is also useful to avoid the problem that can occur when using lifo queues where a client times out on a call and the worker gets checked back in. If the next client gets the "slow" worker it is also likely to timeout. This can lead to a grouping of timeouts until the worker catches up or crashes. This patch allows to isolate that timeout as much as possible by using a combination of fifo queue and gen_server:stop/3 or exit/2 before checking in the worker because the replacement worker is put at the back of the worker queue.

/cc @pdilyard


Add folder name and size success message

Just to check - does this show the message when you use the Browse button? Are you going to update it to show the message when you do the drag-and-drop in a later PR? (That's fine - just want to make sure it doesn't get missed.)

Just to check - does this show the message when you use the Browse button? Are you going to update it to show the message when you do the drag-and-drop in a later PR? (That's fine - just want to make sure it doesn't get missed.)

Yes, when you click the browse button and select your folder. It seems as though these two (clicking the browse button and drag and drop) are in fact one in the same (I need to show you on a call), so the code should work the same way regardless (hopefully).

Cheers. Give me a shout when you want to pair on this. 👍


"block" structure not detected

BRIEF: the language server fails to detect the "block" structure.
VERSION: 0.6.2
example file:
program blockTest
  implicit none
  real, parameter :: x=1.1
  block
    integer, parameter :: x=2
  end block
end program blockTest

The language server raises an error "Variable "x" declared twice in this scope".

I have just merged in an update, which should fix this issue in the next release. However, note that you will still get a warning (not an error) for the example you gave since the variable defined in the block and parent program have the same name. This variable masking can cause issues so I provide a warning in those cases.


Set O_CLOEXEC when opening a network namespace

Set O_CLOEXEC when opening a network namespace
Fix: moby/moby/issues/41136
the container‘s netns fds leak, causing the container netns to not clean up successfully after the container stop
Signed-off-by: fanjiyun<EMAIL_ADDRESS>

@vishvananda PTAL

@vishvananda @tklauser ptal

FWIW, ip netns sets O_CLOEXEC too: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/ip/ipnetns.c?id=d0b645a51e5b5315e14ae2f5538e1e9df6c9f419#n940

@aboch can you help out getting this merged?

@thaJeztah  @tklauser  @aboch  is there anything I need to do for this PR? thanks.

ping @vishvananda

Also, @vishvananda are you interested in having more maintainers added to this repository to help out? If so, I can look for some people to help on that.

this looks good. Pull requests are so rare to this repo i haven't been paying attention. I could add @aboch to have a backup

Thanks! Yes, looks like it's fairly stable/low maintenance. Having @aboch added (if he's interested 🤗) would be appreciated


Adding soviet linux support

Description
Only fill in the fields below if relevant.
Features
Support for OUR distro , Soviet linux
Issues
TODO
Maybe find a better logo

Deleting the whole neofetch and upload the whole neofetch don't look very good in git history

Yea you’re right

You can try to fix it using:
# Undo the last 2 commits, preserving the changes
git reset HEAD~2
# Commit the changes in one commit
git commit -am "Add soviet linux support"

Thank se , i'll do it


django.utils.importlib will be removed in Django 1.9

Using this lib with Django 1.8 will fire deprecation warning. Django-loginas should use importlib from standard Python library instead of deprecated Django version.

Fixed in 38b177e255a6d947350f73fb974f113cdef3c2ec.


Maintenance warning

Hi.
It seems this repo. stopped being maintained in favor of https://github.com/alertlogic/rebar_raw_resource. Would it be possible to:

archive it?
have a notice in the README stating that the new repo should be preferred?

There's 3 PRs:

https://github.com/basho/rebar_raw_resource/pull/3 is equivalent to https://github.com/alertlogic/rebar_raw_resource/pull/1,
https://github.com/basho/rebar_raw_resource/pull/6 is equivalent to https://github.com/alertlogic/rebar_raw_resource/pull/2,
https://github.com/basho/rebar_raw_resource/pull/2 wasn't ported over, but it's an easy fix.

Thanks.

Yeah, so this didn't go anywhere 😄. Closing as unacknowledged for 29 days already.


Add option to see crawlers/bots only stats

There is very useful option --ignore-crawlers. However, I would like to request another option which is just opposite of above --crawlers-only.
I am trying to investigate sudden increase in bots/crawlers traffic for for a web server and it seems currently there is no way to check bots only stats.
And thank you for this great piece of software. Works really great.

I agree on this. I'll add this option. Thanks!

The option --crawlers-only has been added. It will be pushed out in the upcoming version.
Thanks!


⚠ Jenkins Plugins Artifactory has degraded performance

In 79fce50, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1435 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 8acc692 after 1 hour, 4 minutes.


Problem: the Nix-built image does not work

...due at least to #1082, so this issue is blocked on that.

This is the error we get when trying to run the docker image built against 5d8a6adc
docker run --rm -it mina-indexer:5d8a6adc mina-indexer server start
thread 'main' panicked at src/block/genesis.rs:18:9:
Genesis block does not exist at /build/source/rust/tests/data/genesis_blocks/mainnet-1-3NKeMoncuHab5ScarV5ViyF16cJPT4taWNSaTLS64Dp67wuXigPZ.json
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Right, because it's looking for the genesis block at a directory (/build/source) that only exists at build time, not at run time. This is due to how set that path (using 'env!').

Blocked by #1082

The blocker has been resolved. https://github.com/Granola-Team/mina-indexer/issues/1082

Confirmed. I will re-add the image build to the tier-2 testing.


Portal Options Changed | Need to Change Screenshots

[Hello Team,
As we aware that there are changes made to the Azure portal. Now we have Size + Performance option instead Configuration hence requesting to update the screenshots in document.
Thank you 👍 ]

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

ID: ccc58c74-7913-f1f6-8681-1823bbd8f050
Version Independent ID: c11bab28-a82a-29a1-84bf-fb3dfb9a5cb2
Content: Expand the OS drive of a Windows VM in an Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/expand-os-disk.md
Service: virtual-machines-windows
Sub-service: disks
GitHub Login: @kirpasingh
Microsoft Alias: kirpas

@ShivaUdari Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate. We will update you accordingly.

@kirpasingh Can you please check and add your comments on this doc update request as applicable

@ShivaUdari Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate. We will update you accordingly.

Thank you Preeti :)

Thanks for providing feedback that helps improve our documentation. This issue has been resolved and we are closing the issue. #please-close
Investigating/working on this in AB#1958451


@commonName@ certificate?

Trying to implement the SSL certificates for the mailserver with lots of problems.
_I have re-read the docs 4x times but it fails every time. The certificate recieved by the mail client is invalid and has @commonname@ in the title. With thunderbird im able to view the certificate:
_
What Did I miss? How to resolve this and create a 'real certificate'
Anyone can please suggest how this could be resolved?
I had some DNS acme records added previously which i now have removed.
Followed the instructions in the wiki

Create certificate for mail.domain.ltd
/server/letcencrypt is my folder to store letsencrypt in.

   docker run --rm -ti -v $PWD/log/:/var/log/letsencrypt/ -v $PWD/etc/:/etc/letsencrypt/ -p 80:80 deliverous/certbot certonly --standalone -d mail.domain.ltd

This correctly it seems write to /server/letsencrypt/etc/live/domain.ltd

Booting up the containers and linking volumes

    docker run --detach \
        --name nginx-proxy \
        --restart always \
        --publish 80:80 \
        --publish 443:443 \
        --volume /server/letsencrypt/etc:/etc/nginx/certs:ro \
        --volume /etc/nginx/vhost.d \
        --volume /usr/share/nginx/html \
        --volume /var/run/docker.sock:/tmp/docker.sock:ro \
        jwilder/nginx-proxy

    docker run --detach \
      --name nginx-proxy-letsencrypt \
      --restart always \
      --volume /server/letsencrypt/etc:/etc/nginx/certs:rw \
      --volumes-from nginx-proxy \
      --volume /var/run/docker.sock:/var/run/docker.sock:ro \
      jrcs/letsencrypt-nginx-proxy-companion

    docker run --detach \
      --name webmail \
      --restart always \
      --env "VIRTUAL_HOST=mail.domain.ltd" \
      --env "LETSENCRYPT_HOST=mail.domain.ltd" \
      --env<EMAIL_ADDRESS>\
      nginx

CheckTLS.com gives below output:
Trying TLS on domain.ltd[<IP_ADDRESS>:25] (10):

seconds		test stage and result
[000.081]		Connected to server
[000.718]	<-- 	220-mail.domain.ltd ESMTP Postfix (Debian)
220 mail.domain.ltd ESMTP Postfix (Debian)
[000.718]		We are allowed to connect
[000.718]	 -->	EHLO www6.CheckTLS.com
[000.798]	<-- 	250-mail.domain.ltd
250-PIPELINING
250-SIZE 10240000
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 SMTPUTF8
[000.799]		We can use this server
[000.799]		TLS is an option on this server
[000.799]	 -->	STARTTLS
[000.879]	<-- 	220 2.0.0 Ready to start TLS
[000.879]		STARTTLS command works on this server
[001.053]		Connection converted to SSL
SSLVersion in use: TLSv1_2
Cipher in use: ECDHE-RSA-AES256-GCM-SHA384
**Certificate 1 of 1 in chain: Cert VALIDATION ERROR(S): self signed certificate
So email is encrypted but the recipient domain is not verified
Cert Hostname DOES NOT VERIFY (domain.ltd != ff4a106323a4 | DNS:ff4a106323a4)
So email is encrypted but the host is not verified**
cert not revoked by CRL
cert not revoked by OCSP
serialNumber=a3:65:23:37:17:62:70:20
subject= /CN=ff4a106323a4
issuer= /CN=ff4a106323a4
[001.054]	 ~~>	EHLO www6.CheckTLS.com
[001.136]	<~~ 	250-mail.domain.ltd
250-PIPELINING
250-SIZE 10240000
250-ETRN
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 SMTPUTF8
[001.136]		TLS successfully started on this server
[001.136]	 ~~>	MAIL<EMAIL_ADDRESS>[001.227]	<~~ 	250 2.1.0 Ok
[001.228]		Sender is OK
[001.228]	 ~~>	QUIT
[001.308]	<~~ 	221 2.0.0 Bye

Using Thunderbird to view the certificate
mail.domain.ltd it gives a valid certificcate
mail.domain.ltd:143 gives @commonname@ invalid certificate.

Did you read the wiki about how to set this up?
https://github.com/tomav/docker-mailserver/wiki/Configure-SSL

@johansmitsnl
Yes I followed the instructions there, my docker commands are from the nginx-proxy so they differ a little bit ( more clean syntax but they basically do the same if im correct).
I also tried it with exactly the same commands to create the docker containers from the wiki page which result in the same error.

Also mail.domain.ltd is running correctly the nginx browser showing a 'welcome to nginx'
reallly lost on this, i have some basic knowledge of linux administration but this one i have been unable to resolve so far.

I will try to setup mail on windows tomorrow see of it works there.
Still unresolved :(
After all the work i might need to consider another mail docker for testing. Really need my mailbox to be up if updates to this container break mailbox is not something i can afford.
Anyone of the "core team" can investigate this?
Can i get an older docker container of say a few releases back ? That way we can pinpoint if the cause is because how the mailserver behaves or if the problem lies within the letsencrypt cert creation.

The problemen is not the docker container. I do maintain the project. Your issue is the certificate.
Send me a message on gitter.

Hi Jonathan,
Thank you for your reply.
How do I reach you on Gitter?
Kind regards
On Wed, Feb 20, 2019 at 7:34 AM Johan Smits<EMAIL_ADDRESS>wrote:

The problemen is not the docker container. I do maintain the project. Your
issue is the certificate.
Send me a message on gitter.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tomav/docker-mailserver/issues/1130#issuecomment-465444333,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ag-ebI2OCfjWRkTdhs2duWREFdzFIG6Bks5vPOxrgaJpZM4a_2GE
.

With the help of Johan I was able to resolve this issue.
For future reference the issue was inside my docker-compose.yml

/server/letsencrypt:/etc/letsencrypt/
had to become
- /server/letsencrypt/etc:/etc/letsencrypt/live

Same Here. I got this error in my gmail client. SSL certificate generated by letsencrypt shows this error:
Certificate Not Trusted
Subject: @commonName@
Issuer: @commonName@


nonce too small and etc api error

I have the bot running on my Raspi and it works great.
I was experimenting with my Mac and I notice that when I run the bot I frequently receive:
2017-09-26 15:26:53 Error API Error 400: {"message":"Nonce is too small."} Requesting https://api.bitfinex.com/v1/credits
Caught API Error 400: {"message":"Nonce is too small."} Requesting https://api.bitfinex.com/v1/credits reading from exchange API, ignoring.

it doesn't seem to bother the bot too much, sometimes the data goes away or it takes longer to update than normal. I also receive this:
2017-09-26 15:25:45 Error API Error 520: The web server reported a bad gateway or gateway timeout error. Requesting https://api.bitfinex.com/v1/credits
Caught API Error 520: The web server reported a bad gateway or gateway timeout error. Requesting https://api.bitfinex.com/v1/credits reading from exchange API, ignoring.

Which I'm guessing also contributes.
This isn't a huge deal and doesn't seem to be impacting the bot very much but I thought I'd bring it up. May just be my end.
UPDATE: this also happens with my Raspi

Are you running the latest source @chriscrutt ? I put a fix in for this recently.


"hostname does not match the server certificate" error when sending mail

When trying to send a mail via huginn on my (personal) mail server, i always get this error:
/usr/lib/ruby/1.9.1/openssl/ssl-internal.rb:129:in `post_connection_check'
/usr/lib/ruby/1.9.1/net/smtp.rb:585:in `tlsconnect'
/usr/lib/ruby/1.9.1/net/smtp.rb:560:in `do_start'
/usr/lib/ruby/1.9.1/net/smtp.rb:519:in `start'
/var/lib/gems/1.9.1/gems/mail-2.6.3/lib/mail/network/delivery_methods/smtp.rb:112:in `deliver!'
/var/lib/gems/1.9.1/gems/mail-2.6.3/lib/mail/message.rb:2141:in `do_delivery'
/var/lib/gems/1.9.1/gems/mail-2.6.3/lib/mail/message.rb:236:in `block in deliver'
/var/lib/gems/1.9.1/gems/actionmailer-4.2.1/lib/action_mailer/base.rb:543:in `block in deliver_mail'
/var/lib/gems/1.9.1/gems/activesupport-4.2.1/lib/active_support/notifications.rb:164:in `block in instrument'
/var/lib/gems/1.9.1/gems/activesupport-4.2.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/lib/gems/1.9.1/gems/activesupport-4.2.1/lib/active_support/notifications.rb:164:in `instrument'
/var/lib/gems/1.9.1/gems/actionmailer-4.2.1/lib/action_mailer/base.rb:541:in `deliver_mail'
/var/lib/gems/1.9.1/gems/mail-2.6.3/lib/mail/message.rb:236:in `deliver'
/var/lib/gems/1.9.1/gems/actionmailer-4.2.1/lib/action_mailer/message_delivery.rb:85:in `deliver_now'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/performable_mailer.rb:7:in `perform'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/backend/base.rb:94:in `block in invoke_job'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/backend/base.rb:91:in `invoke_job'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:204:in `block (2 levels) in run'
/usr/lib/ruby/1.9.1/timeout.rb:68:in `timeout'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:204:in `block in run'
/usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:203:in `run'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:280:in `block in reserve_and_run_one_job'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:280:in `reserve_and_run_one_job'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:187:in `block in work_off'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:186:in `times'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:186:in `work_off'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:150:in `block (4 levels) in start'
/usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:149:in `block (3 levels) in start'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:148:in `block (2 levels) in start'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:147:in `loop'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:147:in `block in start'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:7:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in <class:ClearLocks>'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block in add'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/var/lib/gems/1.9.1/gems/delayed_job-4.0.6/lib/delayed/worker.rb:146:in `start'
bin/threaded.rb:46:in `block (2 levels) in <top (required)>'
bin/threaded.rb:16:in `safely'
bin/threaded.rb:43:in `block in <top (required)>'```

I checked my mail server for an error in the configuration and didn't find anything.
I checked with www.checktls.com and everything seems ok.

Any suggestion about what I did wrong?

Here is the SMTP_AUTHENTICATION part of my .env
SMTP_DOMAIN=geekmachine.info
SMTP_USER_NAME=huginn
SMTP_PASSWORD=*******
SMTP_SERVER=mail.geekmachine.info
SMTP_ENABLE_STARTTLS_AUTO=false
SMTP_PORT=25
SMTP_AUTHENTICATION=plain

That's odd, can you try to set SMTP_DOMAIN to mail.geekmachine.info?

I tried it and the result is the same.

Does running openssl s_client -connect mail.geekmachine.info:25 -starttls smtp on your huginn server output Verify return code: 0 (ok)?

Good pick. The output is Verify return code: 20 (unable to get local issuer certificate)
Any idea what I should do?

Which unix distribution are you using? Debian derivatives have a ca-certificates package which you might need to upgrade.

I'm on a Debian. And my ca-certificates package is up to date.
28 avril 2015 14:06 "Dominik Sander"  a écrit:
Which unix distribution are you using? Debian derivatives have a ca-certificates package which you might need to upgrade.
—

Reply to this email directly or view it on GitHub (https://github.com/cantino/huginn/issues/810#issuecomment-97037643).

First I tested it from OSX which worked, but I am getting the same result like you do on an ubuntu server. The problem seems to be the missing the intermediate certificate. If you do not have control over the mailserver you can change the smtp.yml file and add
openssl_verify_mode: none

I just tried to add openssl_verify_mode: none and it doesn't work. I've got the same error message.
I tried to add the missing intermediate certificate to my mail server and the error message keep happening.

I am now getting 21 (unable to verify the first certificate), it's strange that the òpenssl_verify_mode` setting does not work.

Seems like it would work -- https://github.com/rails/docrails/commit/a1639ad7524127be0a9e9398dc2ccc8c6629adee -- unless there error is in the mail server?

The problem is more than probably in the mail server. I'm trying to reconfigurate it from scratch to find my mistake.

Just for information: i tried to send via smtp.gmail.com and I have the same error message.
I can't find anything wrong.

Oh weird.  Perhaps something odd with your system...?  But setting openssl_verify_mode: none in all sections of the yaml really should work.

Thank you for your help. I found a workaround (a php webservice to send email). I'll try to resolve the problem when I'll have more time for it. For now, the problem is "solved"


Split docs added, merge docs changes

merge documentation enrichment, split documentation added

Unit.md doesn't exists

Thanks!


Failed to register Lambda Converter for specific type.

At ver 2.3.5.
It is failed to register Lambda Converter for specific type.
Converter<String, Email> converter = context -> {
        String[] address = context.getSource().split("@");
        return new Email(address[0], address[1]);
    };
modelMapper.addConverter(converter);

mapper.getTypeMaps().forEach(typeMap -> {
    System.out.println(typeMap);                // -> TypeMap[Unknown -> Email]
    System.out.println(typeMap.getConverter()); // -> $$Lambda$432/480402503@6865c751
});

I want to register the converter [String -> Email], but actually registered [UNKNOWN -> Email]...
It seems ModelMapper#addConverter could not get the correct Source Type from Converter because TypeResolver#resolveRawArguments not support lambda generic type. This is related jhalterman/typetools#41.
I hope to fix this. Regards.

Resolve using AbstractConverter. but Abstract class can not used as functional interface.

I was just about to create an issue to complain about that 😀
I was sure that lambda expressions were equivalent to their old counterparts, but it seems that it's not the case.
Thank you


Need to check Case 9.6 in 9.FinishRsp

According to Table 61 - FINISH request message format, DSP0274, Param2 is reserved, if Param1 is not set.
Param2 is descrived like below.

SlotID. Only valid if Param1 = 0x01, otherwise reserved.

In Case 9.6, I think it needs to change the 'Param1.Sig' from 0 to 1 to get InvalidRequest. If Param1.sig is 0 like Case 9.6 currently, I think the responder has to response a correct FINISH_RSP.
Could you check what I wrote above?

There are two Case 9.6 in 9.FinishRsp. What you mentioned is next to Case 9.3. It has incorrect number. What I mentioned is "Description: SPDM responder shall return ERROR(InvalidRequest), if it receives a FINISH with invalid field." and it is next to Case 9.5.

Ah, I think you are right.


node_modules directory is not preserved on save & reload

Describe the bug
When creating a directory called node_modules, it is not preserved.
Link to the blitz that caused the error
https://stackblitz.com/edit/node-vkssor?file=index.ts
Steps to reproduce

Start a project
Create a node_modules directory
Click save
Reload

Expected behavior
For any work I save to be saved.
Or at least display a warning that node_module changes are not saved.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 103
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 95327612,
  "usedJSHeapSize": 58922676,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = bff91798029e1af88e01551d056a592b2882b9ac

Additional context
I wanted to use Stackblitz to create a minimal reproduction demonstrating how TypeScript resolves export maps in dependencies. I created a node_modules directory with a random test package but it kept getting deleted.
File structure:
node_modules
└── test-package
    ├── index.ts
    └── package.json

node_modules/test/package.json
{
	"exports": "./index.js"
}

node_modules/test/index.ts
export default 1234;

Hi @privatenumber. Yes this is correct, the node_modules folder will not be preserved as we assume all of those packages come from npm anyways (which is normally the case). If we had to store all the node_modules, we would have to store a lot of duplicate data.
In this situation, you could just create a directory (outside node_modules) with a package.json and index.ts file and use a relative import.
project
├── index.ts
└── test-package
    ├── index.ts
    └── package.json

And then in index.ts, do an import of ./test-package. I believe that should work 🤔 .
If that doesn't work, another alternative would be to symlink the test-package directory to node_modules on startup by using .stackblitzrc. Here's an example https://stackblitz.com/edit/node-3sdzvr.
Kind regards
Sam

This is mainly a DX issue for me because I unexpectedly lost work.
I recommend at least showing a warning that changes in node_modules will not be saved when manual changes are detected.


When only on the desktop, generateComposeResClass cannot generate Res.drawable

Describe the bug
The application I developed only needs to support the desktop, so there is no dependency on mobile platforms such as Android. The directory structure of composeResources is as follows:

The generated Res.kt is as follows
@file:OptIn(
  org.jetbrains.compose.resources.InternalResourceApi::class,
  org.jetbrains.compose.resources.ExperimentalResourceApi::class,
)

package portview.composeapp.generated.resources

import kotlin.ByteArray
import kotlin.OptIn
import kotlin.String
import org.jetbrains.compose.resources.ExperimentalResourceApi
import org.jetbrains.compose.resources.readResourceBytes

@ExperimentalResourceApi
internal object Res {
  /**
   * Reads the content of the resource file at the specified path and returns it as a byte array.
   *
   * Example: `val bytes = Res.readBytes("files/key.bin")`
   *
   * @param path The path of the file to read in the compose resource's directory.
   * @return The content of the file as a byte array.
   */
  public suspend fun readBytes(path: String): ByteArray = readResourceBytes(path)
}

There is no relevant code for Res.drawable, but when I built multiple platforms (including Android and other mobile devices), it was successful.
@file:OptIn(
  org.jetbrains.compose.resources.InternalResourceApi::class,
  org.jetbrains.compose.resources.ExperimentalResourceApi::class,
)

package timeline.composeapp.generated.resources

import kotlin.ByteArray
import kotlin.OptIn
import kotlin.String
import org.jetbrains.compose.resources.DrawableResource
import org.jetbrains.compose.resources.ExperimentalResourceApi
import org.jetbrains.compose.resources.readResourceBytes

@ExperimentalResourceApi
internal object Res {
  /**
   * Reads the content of the resource file at the specified path and returns it as a byte array.
   *
   * Example: `val bytes = Res.readBytes("files/key.bin")`
   *
   * @param path The path of the file to read in the compose resource's directory.
   * @return The content of the file as a byte array.
   */
  public suspend fun readBytes(path: String): ByteArray = readResourceBytes(path)

  public object drawable {
    public val icon: DrawableResource = get_icon()

    public val loading: DrawableResource = get_loading()

    public val logo_ghost: DrawableResource = get_logo_ghost()
  }
}

private fun get_icon(): DrawableResource = org.jetbrains.compose.resources.DrawableResource(
  "drawable:icon",
    setOf(
      org.jetbrains.compose.resources.ResourceItem(setOf(), "drawable/icon.png"),
    )
)

private fun get_loading(): DrawableResource = org.jetbrains.compose.resources.DrawableResource(
  "drawable:loading",
    setOf(
      org.jetbrains.compose.resources.ResourceItem(setOf(), "drawable/loading.png"),
    )
)

private fun get_logo_ghost(): DrawableResource = org.jetbrains.compose.resources.DrawableResource(
  "drawable:logo_ghost",
    setOf(
      org.jetbrains.compose.resources.ResourceItem(setOf(), "drawable/logo-ghost.png"),
    )
)

How to generate it when there are only desktop related dependencies?
Affected platforms

Desktop

Versions

Kotlin version*:  1.9.22
Compose Multiplatform version*:  1.6.0-beta02
OS version(s)* (required for Desktop and iOS issues):  Windows 11
OS architecture (x86 or arm64):  x86
JDK (for desktop issues):  17

To Reproduce

Go to https://kmp.jetbrains.com/ genernate only desktop project.
Upgrade kotlin and  compose multiplatform version.
Add composeResources/drawable dir and image files.
run ./gradlew generateComposeResClass.
Generate Res.kt but not include Res.drawable.

Expected behavior
Generate Res.kt and include Res.drawable for desktop platform.

you are suppose to place your resources in src/commonMain/composeResources directory when you apply the Kotlin Multiplatform Gradle plugin. It doesn't matter how many targets you have.

If you want to develop a JVM only app, you can use the Kotlin Jvm Gradle plugin instead.
then composeResources may be in src/main/composeResources

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


sound

Hello everyone!!
I don't know where to write about the plugin, but I'll write here.
The plugin seems to work after the update, but not correctly, when you drive in the truck cabin, the sound is as if you are standing in a tunnel or under a bridge, but when you drive away from a third person, the plugin sound works more or less, but not as in the previous version of the plugin.
Maybe someone will help this and solve this problem.
Thanks...

download master bank from version 1.49 and replace it with the one you got.Problem will be fixed


Support common oauth logins through configuration?

More companies are using corporate email as an account system.
Eg: google, github, gitlab, ms, aliyun, tencent, dingding,.......

Sounds like a good idea, any suggestion?

https://github.com/justauth/JustAuth
similar?

There are 2 aspects:

login with all kinds of providers
implement UserService for all kinds of providers

@nobodyiam
This process can be simplified by using components like JustAuth, for which only one userservice needs to be implemented.
E.g: Spring Boot 快速集成第三方登录功能.
I am not familiar with the world of java, maybe you have better suggestions.

I think with JustAuth, login is easy with all kinds of providers. But I don't see how we could implement UserService for all kinds of providers, e.g. search users


docs: clarify the meaning of VoteExtensionsEnableHeight == 0

It means disabled, but the documentation and code comments (that also play the role of documentation, for instance for protobufs) do not make this information clear enough.

we have some information here, but agree that we could clarify the implications of having a 0 value
https://docs.cometbft.com/v1.0/spec/abci/abci++_app_requirements#featureparamsvoteextensionsenableheight

-1 or something might have been clearer [instead of 0 as disabled value]

Not possible, as the disabled value needs to be the golang zero value.


Feature request: Authorship assignment

At the moment is not possible to reassign the authorship of a post within Wagtail's dashboard.
The only way to do it is to go into the database directly and changed the owner.
It would be a useful feature to have, considering some might have web editors that need to assign articles to contributors and such.
Thanks

Have now merged #3581, which makes it possible to add the 'page owner' field to the displayed panels on a per-page-type basis. This now raises the question of whether to make it available by default: it probably makes sense to do that (especially since we plan to do the same for the "first published at" field: #3498), but if we do, we need to ensure that the resulting form widget is not just a dropdown of all users on the system (since this could include front-end users too, and there could be thousands of them). Logically, it should probably be a selector of all users who have add or edit permission over the current page or one of its ancestors.

Another consideration we'll need to account for if we add this (or any other field) to the default panels list of Page - we'll need to make sure that any existing apps (e.g. Puput) that explicitly add the field by doing:
settings_panels = Page.settings_panels = [
    FieldPanel('owner')
]

continue to work, and don't get tripped up by the duplicate field. (I guess we need to check for duplicates, and if any are found, output a warning and ignore the second one...)

Good point @gasman! I'll think about it.

@ginestra could you expand on your use-case?
I think it's sensible to assume that the 'page owner' is not the same as the page author from the websites users perspective.
I presume you're talking about your editorial workflow. Could you explain what you're trying to achieve in a little more detail please?

Hi @tmsndrs,
Thanks for following up on this.
The use case has to do with authors changing and the need to reassign authorship of their content to others, or admins publishing on behalf of others and not being able to re-assign when appropriate.
Also and maybe more importantly: when an import happens, whoever does the import is recorder as the page owner which is usually not the case for all the pages.
I hope this makes sense.
Thanks

@gasman, I wasn't knowing about these feature.

As of #11359, we now have a filter for page owners, so I believe "now" will be a good time to decide whether it makes sense to allow re-assigning ownership.


Any document?

Any document?

The package docs are visible at http://godoc.org/github.com/golang/leveldb but this project also isn't finished yet.


fix: Reject bid after delete should collect larger penalty

Description
Fixes #91
Checklist:

[x] My commit message follows the Conventional Commits specification
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have tested my code
[x] My changes generate no new warnings
[x] My PR is rebased off the most recent main or appropriate feature branch
[x] My PR is opened against the main or appropriate feature branch

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

20 of 21 (95.24%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 88.317%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/pco-license/libraries/LibCFAPenaltyBid.sol
20
21
95.24%

Files with Coverage Reduction
New Missed Lines
%

contracts/pco-license/libraries/LibCFAPenaltyBid.sol
1
87.39%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
523

Relevant Lines:
569

💛  - Coveralls

@gravenp As I've gone through the test cases, I think there is a different way to do this. Instead of having the payer pay more than the penalty, we could just no longer allow rejecting a bid if the payer deletes their flow. The bid period would immediately end and anyone can trigger a transfer.
So deleting your flow while there is a bid outstanding is the same as accepting the bid. Once it is deleted though, the depleting amount is taken from the for sale price the payer would receive.
Thoughts?

@gravenp As I've gone through the test cases, I think there is a different way to do this. Instead of having the payer pay more than the penalty, we could just no longer allow rejecting a bid if the payer deletes their flow. The bid period would immediately end and anyone can trigger a transfer.
So deleting your flow while there is a bid outstanding is the same as accepting the bid. Once it is deleted though, the depleting amount is taken from the for sale price the payer would receive.
Thoughts?

If you're able to treat flow deletion effectively the same as a bid rejection window passing, that would simplify the accounting perspective for sure. Would we need to update the logic for the Needs Transfer window to look for something different?  We'd still want to add the messaging about the reduction of sales proceeds for the intervening Network Fees regardless.
From a user perspective, I don't think it's unfair/unexpected that you'd lose your right to reject a bid if your stream is stopped.

Yes, I think that logic would need to be updated.

We'd still want to add the messaging about the reduction of sales proceeds for the intervening Network Fees regardless.

Are you talking about https://github.com/Geo-Web-Project/cadastre/issues/242? They could be prompted to trigger a transfer if their stream is closed which will immediately stop the bleeding of their for sale price.
Another case here is if the user deletes their flow and then reopens it. I think we should still not allow them to reject if they reopen. There could be some vulnerabilities here where they can take funds from the bidder.

Yeah that ticket wouldn't fully apply anymore, so I'd modify it to add the appropriate text on the screen with the Transfer Parcel button rather than the screen with the Accept +(disabled) Reject buttons.
As for reopening the stream, agreed. Once a stream has been cancelled, the ship has sailed. The user has forfeited their right to keep the parcel uninterrupted.


[Windows] Add .NET 6.0 as LTS

Description
With the release of .NET 7.0, the content of our images has changed from our software support policy. Let's add .NET 6.0 as a permanent component of the build.
Related issue:
#6577
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run windows2019,windows2022


Add code coverage report to java build

JaCoCo I assume.  I'll add this shortly

I've implemented this, but I didn't until now understand that most tests are executed via the test harness, and so code coverage reports are limited.  I've only implemented it from maven poms.  It would probably be a good idea to make it work as part of the test harness, but this was beyond what I had planned to do.  No dramas if this pull request is rejected.


macos pdo_sqlsrv_db_handle_factory: Unknown exception caught

PHP Driver version or file name
pdo sqlsrv 5.3.0
SQL Server version
Client operating system
mac os Mojave 10.14.1 (18B75)
PHP version
PHP 7.2.13
This issue is very similar to #161
it worked fine until today when I rebooted my local machine.
The error I'm getting when trying to connect to any MSSQL Database is: pdo_sqlsrv_db_handle_factory: Unknown exception caught
I've tried clearing all php installations and configs and reinstalling:

php 7.2 (homebrew)
sudo pecl install pdo_sqlsrv
sudo pecl install sqlsrv
brew install --no-sandbox msodbcsql mssql-tools

Now i'm getting pdo_sqlsrv_db_handle_factory: Unknown exception caught.
Looking at #161, I've added export LC_ALL=en_US.UTF-8 and export LANG=en_US.UTF-8 to my .zshrc file. In the console, I can connect successfuly, but running PHP through Apache, I get the above error.
I've tried setting Env Vars from Apache to PHP, using
SetEnv LC_ALL "en_US.UTF-8"
SetEnv LANG "en_US.UTF-8"

And it has been set successfully, but I still get the same error.
Any help with this, please?

Thanks for the explanation and i am also caught up in the same issue. how did you add this to php environment ? i was able to add this only to apache environment.


Move formula files to Formula/ subdir

Let's move all the formula files to a Formula/ subdir to keep things tidy, since we also have a cmd/ dir and some documentation files in the root dir.
Will require tweaks to brew-boneyard (https://github.com/Homebrew/homebrew-dev-tools/pull/4) and the upcoming brew-boneyard-pr (https://github.com/Homebrew/brew/pull/53). Shouldn't affect usefulness of the git history.

(I posted this earlier in the team chat, but it probably got lost.) The main downside to moving formulae into a different location is that brew update is currently not prepared to handle this, thus will list all moved formulae as new formulae (for those who have that tap installed). For, e.g., homebrew/versions this would look something like:
$ brew update
Updated 1 tap (homebrew/versions).
==> New Formulae
homebrew/versions/allegro4
homebrew/versions/android-ndk-r10d
homebrew/versions/android-ndk-r10e
homebrew/versions/ansible14
homebrew/versions/ansible18
homebrew/versions/ansible19
homebrew/versions/antlr2
homebrew/versions/antlr3
homebrew/versions/apache-spark141
homebrew/versions/apache-spark15
homebrew/versions/appledoc20
homebrew/versions/appledoc21
homebrew/versions/appledoc22
homebrew/versions/astyle204
homebrew/versions/autoconf213
homebrew/versions/autoconf264
homebrew/versions/automake112
homebrew/versions/bash-completion2
homebrew/versions/bind99
[…]

Obviously, something similar would happen if this was done in this repository. Another command that won't work well after such a change is brew audit when walking the commit history of a formula, though that is less of a concern for this repository. (Maybe there are also other commands that work with the Git history and would get confused, though I cannot think of any other right now.)

Yeah, per Martin's point and echoing what I said in chat the other day I'm quite reluctant to go through with this sort of thing until brew update can hide the misleading messages.

That makes sense. Closing this until brew update handles it better.
Posted it as a brew issue https://github.com/Homebrew/brew/issues/87 so that's not overlooked again.


The gripper tip is just touching the ground block.

Turns out for 13 and 33, the gripper tip is just touching the ground block.

Option 1 : Model the gound pillow block to be slightly smaller
Option 2: Change Grasp to another location such that they don't exactly kiss the pillow block
Option 3: Change the gripper jaw hardware and thus the collision model can be smaller. (Not ideal)

Probably will go with Option 1.

Originally posted by @yck011522 in https://github.com/gramaziokohler/integral_timber_joints/issues/123#issuecomment-937818495

This is no longer the case with new model.


next: Pattern for reusable forms

as commented here https://github.com/prometheusresearch/react-forms/commit/2b31b0dba261d75984245869cc378f43fa359e24
The example is not working, and seems like the schema is not structured properly. Though I tried with a nested object schema, the keypath is setting incorrect and the value has wrong structure. I couldn't see the default values set either. So, what is the correct schema, field structure for this example.
Uncaught Error: {"mother":{"type":"object","properties":{"firstName":{"type":"string"},"lastName":{"type":"string"}}},"father":{"type":"object","properties":{"firstName":{"type":"string"},"lastName":{"type":"string"}}}} mother_select @ Schema.js:90
select @ Schema.js:59
ValueLeaf @ Value.js:11
select @ Value.js:18
_createClass.get @ Component.js:68
getChildContext @ Component.js:40

I tried with following schema
let schema = {
  type: 'object',
  properties: {
    mother: IndividualFieldset.schema,
    father: IndividualFieldset.schema
  }
};

but resulted in

this seems work.
since IndividualFieldset is extending Fieldset, having a Fieldset inside the render method causes to apply double selector. Let me know if this below is the intended behavior.
'use strict';

import React from 'react';
import {Field, Fieldset, Value} from 'react-forms';

class IndividualFieldset extends Fieldset {

  static schema = {
    type: 'object',
    properties: {
      firstName: {type: 'string'},
      lastName: {type: 'string'}
    }
  }

  static value = {
    firstName: 'John',
    lastName: 'Doe'
  }

  render() {
    let {label, ...props} = this.props;
    return (
      <div {...props}>
        <label>{label}</label>
        <Field
          select="firstName"
          label="First name"
          />
        <Field
          select="lastName"
          label="Last name"
          />
      </div>
    );
  }
}

let schema = {
  type: 'object',
  properties: {
    mother: IndividualFieldset.schema,
    father: IndividualFieldset.schema
  }
};

// let schema = {
//   mother: IndividualFieldset.schema,
//   father: IndividualFieldset.schema
// };

let value = {
  mother: IndividualFieldset.value,
  father: IndividualFieldset.value
};

export default class FamilyForm extends React.Component {

  constructor(props) {
    super(props);
    this.state = {formValue: Value(schema, value, this.onChange)};
  }

  onChange = (nextFormValue) => {
    console.log('form value', nextFormValue.value);
    this.setState({formValue: nextFormValue});
  }

  render() {
    return (
      <Fieldset formValue={this.state.formValue}>
        <IndividualFieldset
          select="mother"
          label="Mother"
          />
        <IndividualFieldset
          select="father"
          label="Father"
          />
      </Fieldset>
    );
  }
}