[mesheryctl] New command exp environment

See mesheryctl Command Tracker for current status of commands.
Desired Behavior
Develop an experimental command to manage environments within the system. Refer to the Environment documentation for more details about environments.
Tasks to be Completed:

[ ] Implement command to list existing environments
[ ] Implement command to create new environments
[ ] Implement command to delete existing environments
[ ] Implement command to view details of a specific environment
[ ] Develop comprehensive test cases to validate the functionality of the environment command

Contributor Resources

⌨ mesheryctl Contributing Guide
Beginner's guide to contributing to Meshery and mesheryctl
mesheryctl Command Tracker
Meshery CLI Commands and Documentation
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

@RipulHandoo  can this be assigned to me?

@luigimorel Certainly, it's great to see your interest in contributing! At the moment, I've already started working on this particular feature. However, I appreciate your willingness to help. There are some other issues similar to this. I'll mention them below:
https://github.com/meshery/meshery/issues/10585
https://github.com/meshery/meshery/issues/10582


Index URIs in Sinopia search

A user can perform an exact match search of a Sinopia resource URI in Sinopia search.

The existing Load by URI can be removed.

start by indexing just the base Sinopia URI

To be determined if this should be implemented by hitting Sinopia server or indexing in ES.


Missing Voyager IMQ files

Starting from a fresh search, go to the browse tab and choose an image of Jupiter, add it to the cart, and try to download it. The server will log the following kind of error:
[Sat Feb 03 14:41:17.442377 2018] [wsgi:error] [pid 17792:tid<PHONE_NUMBER>37568] [03/Feb/2018 14:41:17] ERROR [downloads.views:256] [Errno 2] No such file or directory: '/volumes/pdsdata-server2/holdings/volumes/VG_0xxx/VGISS_5101/JUPITER/C1462XXX/C1462321.IMQ'

Per Mark, all IMQ and IRQ files have been removed from the files, file_sizes, and files_not_found tables on both dev and tools.


jsdelivr support

Wasm npm imports on client side after page load?
I can't tell if this issue is supposed to be a feature request for something missing, or a call for attention to something provided that I can't track down the details of.
I'm creating a tool that is meant to be used for browser based datascience. At the moment there is existing support for importing libraries like those hosted on cdnjs and certain npm libraries that work with jsdelivr.
I'm curious if wasm-pack (probably the build step) can be configured in such a way that the output will lend itself to these inclusion by script source url methods. Thanks for all the work so far, and if this is just not possible for reasons that I'm unaware of we can close this issue out.

hey! i'm not 100% sure what that would require but i'm very happy to do the research! thanks for filing :) i'll follow up when i know more

hey @DevinBayly - apologies for the Extreme Delay in response. i'm still interested in exploring this. can you share if there's any further work we can do to enable this? potentially some documentation work? please let me know!

not to worry! I took a break from the wasm-ndarray stuff so I haven't thought about this much recently. I am still writing wasm tools, but I'll need a moment to recall what I wanted to do here. Thanks for getting back to me though!


Report problems applying changes

Strictly keep track of the accumulating $retval from calls to various
functions that apply changes.
Use new function print_apply_result_box() to print a suitable message
in a suitable severity based on $retval

Notes:

I have tested a few samples, I will do more testing and report back (there are 50+ places in the GUI to make a change, press save, apply and see that at least the success message comes out)
status_monitoring.php in the ports repo should also be updated to the new scheme (although get_std_save_message() is quite backward-compatible - status_monitoring should not actually break)

All working for me after fixing up the system_syslogd_start and vpn_ipsec_settings bits in the 2 commits above.


TV Studio pro 4k

Hi,
I have a Blackmagic TV Studio pro 4k device
When I try to connect to the TVS studio pro 4k, I get an error.
When I select as device a TV Studio HD (while the hardware is a TVS pro 4k) it does connect without error and works
Could you fix this?

This has been long fixed in the beta builds.

When are these beta builds released as mature.
Is a module automatically updated within companion?
regardss Henk Levels
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
03/19/21,
05:29:33 PM
Op vr 19 mrt. 2021 om 17:20 schreef Julian Waller @.***

:

This has been long fixed in the beta builds.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-bmd-atem/issues/126#issuecomment-802951729,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APLMQVMGFSI4VDFFNOV5RMDTEN2V5ANCNFSM4ZO7RCHQ
.


[WIP] Feature/markdown it

Purpose

Replace wiki rendering with markdown-it
Includes view, edit, and widget

Changes

Added markdown-it
Added truncate
Remove Pagedown rendering
Move Pagedown package into wiki static

Side effects

No more python rendering displayed
Slight change in wiki length due to truncation method (easily configurable)

These changes are included in https://github.com/CenterForOpenScience/osf.io/pull/1833


error: the example provided by xiSPEC cannot be used (ncvqnv6pn3c28bkm8jfjnbsv5i_1678176426.log)

Hello, today, xiSPEC has been reporting an error, even with the example provided by xiSPEC , there will still be an error of sequence of ncvqnv6pn3c28bkm8jfjnbsv5i_1678176426.log , I sincerely hope that you can help me to solve this problem.

Thank you for reporting this. I'm looking into it. It seems like there is a problem with reading/writing the files on the server


sciond: sciond API should have a way to inform the client about errors

For example the SVCInfoRequestHandler.Handle (in go/sciond/internal/servers/handlers.go) method has no way to tell the client that an invalid ServiceType was sent in the request.

We're getting this for free as part of #3347. Closing as duplicate.


feat: Add support for new select menus components

Description
Implements new options for select menus.
Resolves #61
TODO: Tests
Connected issues & potential other potential problems

https://github.com/nyxx-discord/nyxx/pull/380

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] Ran dart analyze or make analyze and fixed all issues
[x] Ran dart format --set-exit-if-changed -l 160 ./lib or make format and fixed all issues
[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 made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my changes haven't lowered code coverage

As a question, should we cache reslut of resolved entries?

JIC the received channels/users/members/roles from the payload are not in the cache

ah you mean that. Yeah sure, maybe we should do that. It should respect CacheOptions thing we have


If the last commit is a merge commit, prompt to confirm for "undo last commit"

Several developers in our team have encountered problem because of accidentally undoing last merge commit. I think it would be nice to prompt if the last commit is a merge commit.

Works great, but it might be good to make it a modal dialog since action is required.

@alexr00 I like that https://github.com/microsoft/vscode/commit/32a529d1cad8a35fd9786f2afc7e283fabe1f3eb


Okhttp exception: [java.io.IOException: gzip finished without exhausting source]

I know similar exception issue has been submitted, but, this is different.
java.io.IOException: gzip finished without exhausting source
    at okio.GzipSource.read(GzipSource.java:100)
    at okio.Buffer.writeAll(Buffer.java:1005)
    at okio.RealBufferedSource.readString(RealBufferedSource.java:190)
    at okhttp3.ResponseBody.string(ResponseBody.java:175)
    at com.test.testokhttp.PostExampleActivity$2.onResponse(PostExampleActivity.java:99)
    at okhttp3.RealCall$AsyncCall.execute(RealCall.java:141)
    at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
    at java.lang.Thread.run(Thread.java:761)

My source code is like this:
String url = "http://api.kdniao.cc/Ebusiness/EbusinessOrderHandle.aspx";
String key1 = "RequestData";
String key2 = "EBusinessID";
String key3 = "RequestType";
String key4 = "DataSign";
String key5 = "DataType";

String val1 = "%7B%27OrderCode%27%3A%27%27%2C%27ShipperCode%27%3A%27STO%27%2C%27LogisticCode%27%3A%27402581441844%27%7D";
String val2 = "1293539";
String val3 = "1002";
String val4 = "OWNiNzUxODEyMmEzN2E5NWY0NDAwYTJlY2QxZWVmNWY%3D";
String val5 = "2";

public void simplePostClick(View view) {
	OkHttpClient okHttpClient = new OkHttpClient();
	RequestBody requestBody = new FormBody.Builder()
		.add(key1, val1)
		.add(key2, val2)
		.add(key3, val3)
		.add(key4, val4)
		.add(key5, val5)
		.build();
	Request request = new Request.Builder()
		.url(url)
		.post(requestBody)
		.build();
	okHttpClient.newCall(request).enqueue(callback);
}

private Callback callback = new Callback() {
	@Override
	public void onFailure(Call call, IOException e) {
		setResult(e.getMessage(), false);
	}

	@Override
	public void onResponse(Call call, Response response) throws IOException {
		setResult(response.body().string(), true);
	}
};

private void setResult(final String msg, final boolean success) {
	runOnUiThread(new Runnable() {
		@Override
		public void run() {
			Log.e("okhttp", msg);
			resultTextView.setText(msg);
		}
	});
}

Run this code will always get the exception. There is no problem with the server. But HttpURLConnection will get the right result

Response body gzip format is malformed. It more of a newline character.Why the server append 0x10 character in the end? In addition, the HttpClient decode compatible with the situation using GzipInputStream

Looks like a bug in whichever server is serving this data; possibly api.kdniao.cc. You should fix it there.
We could fix OkHttp to ignore unexpected data at the end of the gzip stream, but there’s lots of bad consequences for that. For example, there might be security consequences! Instead it’s best to fix the problem with the offending server.


Highlighting and log path missing

@thwpike : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


[Feature] Implement some out of the box waits in SHAFT to handle certain cases

Implement some out of the box waits in SHAFT to handle certain cases like waiting an element to be invisible and other cases that can't be handled by SHAFT built-in waits with the actions automatically.

I think this is covered with the waitForElementToBePresent method enhancements, right?
I don't think of any waits needed now. Let's close this and We can reopen it when needed.
What do you think @MohabMohie ?

Agreed


Deprecated Warnings when using planck

Version
[rewrite-clj/rewrite-clj "1.0.605-alpha"]
Platform
Operating System: [macOS Big Sur]
Clojure version: [org.clojure/clojure "1.10.3"]
JDK vendor and version: [openjdk version "1.8.0_275"
OpenJDK Runtime Environment (Zulu <IP_ADDRESS>7-CA-macos-aarch64) (build 1.8.0_275-b01)
OpenJDK 64-Bit Server VM (Zulu <IP_ADDRESS>7-CA-macos-aarch64) (build 25.275-b01, mixed mode)]
ClojureScript

version: [ClojureScript 1.10.597]
tooling: [planck]
host: [ planck -V 2.25.0]

Symptom
I get a lot of Warnings when I load zprint into planck, both as a REPL and when running my cljs tests.
Reproduction
At the top level of the zprint repo, this is what I get when running planck by hand:
√ projects/zprint % rm -rf .planck_cache
√ projects/zprint % planck -K -c `lein classpath` -r
ClojureScript 1.10.597
cljs.user=> (require 'zprint.core :reload)
WARNING: rewrite-clj.node.protocols/value is deprecated at line 207 rewrite_clj/node.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-space is deprecated at line 106 rewrite_clj/zip/whitespace.cljc
WARNING: rewrite-clj.zip.whitespace/append-space is deprecated at line 113 rewrite_clj/zip/whitespace.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-newline is deprecated at line 120 rewrite_clj/zip/whitespace.cljc
WARNING: rewrite-clj.zip.whitespace/append-newline is deprecated at line 127 rewrite_clj/zip/whitespace.cljc
WARNING: rewrite-clj.node.protocols/value is deprecated at line 88 rewrite_clj/zip/base.cljc
WARNING: rewrite-clj.zip.base/value is deprecated at line 253 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.base/->string is deprecated at line 273 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.base/->root-string is deprecated at line 283 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-space is deprecated at line 886 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-space is deprecated at line 887 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/append-space is deprecated at line 892 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/append-space is deprecated at line 893 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-newline is deprecated at line 898 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-newline is deprecated at line 899 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/append-newline is deprecated at line 904 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/append-newline is deprecated at line 905 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.base/value is deprecated at line 253 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.base/->string is deprecated at line 273 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.base/->root-string is deprecated at line 283 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-space is deprecated at line 886 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-space is deprecated at line 887 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/append-space is deprecated at line 892 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/append-space is deprecated at line 893 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-newline is deprecated at line 898 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/prepend-newline is deprecated at line 899 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/append-newline is deprecated at line 904 rewrite_clj/zip.cljc
WARNING: rewrite-clj.zip.whitespace/append-newline is deprecated at line 905 rewrite_clj/zip.cljc
nil
cljs.user=>

If I disable warnings for "deprecated functions", these warning go away:
√ projects/zprint % rm -rf .planck_cache
√ projects/zprint % planck --compile-opts '{:warnings {:fn-deprecated false}}' -K -c `lein classpath` -r
ClojureScript 1.10.597
cljs.user=> (require 'zprint.core :reload)
nil
cljs.user=>

Actual behavior
I would not expect warnings for functions that I didn't call.  Which is maybe more of a self-hosted Clojurescript issue than a rewrite-clj issue, I suppose.
The reason I submitted this issue is that this is certainly a change from rewrite-cljs to rewrite-clj when using planck.
Expected behavior
I would expect to see no warnings since I didn't see any with rewrite-cljs.
Diagnosis
Other than figuring out how to turn it off in planck, I haven't taken it any further.
Action
I can figure out how to turn these warnings off for my tests, so I don't have to look at them, so this won't continue to bother me.
I'm wondering, though, if maybe there is a better answer?  For instance, I noticed that at least a few were deprecated in 0.4.0, so maybe in this new, major release, they might want to even go away?  Maybe not, since you are trying to make upgrading easy for all of us users.
An alternative would be to note this somewhere in the "how to upgrade to rewrite-clj v1 from rewrite-cljs", and maybe tell people (briefly) how to turn off the new warnings?
But I wanted you to know about this in case you didn't already, though I expect the zprint 1.1.1 tests did the same thing as well.

Thanks for raising @kkinnear, this is fixed by #153 (on main branch, not yet released at the time of this writing).
Interesting side note: the JVM ClojureScript compiler does support turning off deprecated warnings via :fn-deprecated, but I don't think the bootstrap (self-hosted) compiler, which planck uses, supports this option yet.

Thanks for the info, I didn't think to look in the closed issues, or I just missed it altogether.  I did look at the open issues, because I learned that rewrite-clj uses are a lot in the tests from an old issue, and I needed some good examples of the use of are for some of my testing.  Anyway, thanks for dealing with this.
For what it is worth, planck lets me turn these warning off with :fn-deprecated as well.
Thanks again!

No problemo!  Thanks for raising (I don't care at all that it ended up being a dupe, you are the 3rd person I know of affected by this issue, so there must be more!).
Also thanks for the planck tip on :fn-deprecated - for some reason I did not get this working for the rewrite-clj test suite, I'll take another stab at it sometime.
Also FWIW, some people really dislike are. I am not one of them - yet, anyway!

In case this helps, here is what I'm doing with planck:
 % more dooopts.edn
{:debug false :paths {:planck "planck --compile-opts planckopts.edn"}}
% more planckopts.edn
{:warnings {:private-var-access false :fn-deprecated false}}

Cheers!


[Fix #5498] Correct Heredoc message when using '<<~' with invalid ind…

This commit addresses using <<~ with Heredoc but using an invalid indentation which results in this message, Use 2 spaces for indentation in a heredoc by using <<~ instead of <<~.
The message logic was modified where it can address both the operator and the indenation or only the indentation to avoid any confusion.
fixes #5498
As mentioned in #5498 using an invalid indentation with the operator <<~ results in a weird message which causes confusion.

Modified the message to mention the operator only when the user is using a wrong operator such as <<.
Modified the existing tests where the message has been modified.
Added a new test to validate the modification and prevent anyone from breaking it again.

[x]  Wrote good commit messages.
[x]  Commit message starts with [Fix #issue-number] (if the related issue exists).
[x]  Feature branch is up-to-date with master (if not - rebase it).
[x]  Squashed related commits together.
[x]  Added tests.
[x]  Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x]  The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x]  Run rake default or rake parallel. It executes all tests and RuboCop for itself, and generates the documentation.

Thanks for working on this! I really appreciate it! 🙇


Chore/bump 0.13.1

This PR bumps<EMAIL_ADDRESS>

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (8aa6246) 87.63% compared to head (94d80f1) 87.61%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #225      +/-   ##
==========================================
- Coverage   87.63%   87.61%   -0.02%
==========================================
  Files          68       68
  Lines        5118     5126       +8
==========================================
+ Hits         4485     4491       +6
- Misses        633      635       +2

Flag
Coverage Δ

unittests
87.61% <63.63%> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

...ckages/elcollectooorr/contracts/basket/contract.py
50.82% <100.00%> (+0.27%)
:arrow_up:

...lcollectooorr/contracts/basket_factory/contract.py
83.78% <100.00%> (+0.45%)
:arrow_up:

...lcollectooorr/contracts/token_settings/contract.py
95.71% <100.00%> (+0.06%)
:arrow_up:

...rr/contracts/token_settings/tests/test_contract.py
100.00% <ø> (ø)

...s/elcollectooorr/contracts/token_vault/contract.py
84.34% <100.00%> (+0.13%)
:arrow_up:

...ges/elcollectooorr/contracts/artblocks/contract.py
30.35% <0.00%> (-0.28%)
:arrow_down:

...ectooorr/contracts/token_vault_factory/contract.py
85.88% <33.33%> (-0.45%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


update near-sdk in integration tests to pre-released version

This should effectively match the state it was in before ABI PRs were merged in. But with the version update.

We're nearly there. I suppose the only blocker for that is finalizing https://github.com/near/near-sdk-rs/pull/891.
For now, the use of the abi feature gives access to the NearSchema derive. And since cargo-near can't do anything without those derives, it requires that feature flag.
But once NearSchema gets merged in, we can remove the abi feature.

We're nearly there. I suppose the only blocker for that is finalizing near/near-sdk-rs#891.
For now, the use of the abi feature gives access to the NearSchema derive. And since cargo-near can't do anything without those derives, it requires that feature flag.
But once NearSchema gets merged in, we can remove the abi feature.

Not necessarily, because you don't need the derive if all interface types already implement the schema types. Also, you could just not use the NearSchema convenience derive, that's optional, is it not?


Updated documentation for Che 7 with NFS as persistent volume

Also updated instructions to deploy Microk8s/Kubernetes 1.20 which allows us to define a dns directly from the microk8s.enable dns instead of having to edit the config map. Also updated cert-manager to the latest stable version.

Wait, gotta think about this some more. I realized I made a bad assumption with the ssh nodeports.

We're good to go. The SSH nodeport issue is fixed with a change in the eclipse che code.


Update sovereignLandingZone.parameters.json

Overview/Summary
New description for parameter parCustomerPolicySets based on information in docs folder.
This PR fixes/adds/changes/removes

Change parameter description (Fix #9)

Documentation
https://github.com/Azure/sovereign-landing-zone/blob/main/docs/07-Deployment-Parameters.md

@SimonWahlin addressed in #13.

Thanks @ugreg
Does this mean that you are not currently accepting PRs to this repository?

Thanks @ugreg! Does this mean that you are currently not accepting PRs to this repo?


Add UPB University

Universidad Politécnica del Bicentenario

@AlacranBlanco First stage of verification passed, official domain for Universidad Politécnica del Bicentenario is upbicentenario.edu.mx as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@AlacranBlanco Thank you for your patience while waiting for a review and processing your request. Pull request merged.


crashing test hangs pytest

I'm observing the pytest process itself seemingly breaking as a result of a segmentation fault observed in a test.
Here is the relevant part of the log:
../python/tests/ctk/simulator/test_simple.py::test_battery Fatal Python error: Segmentation fault

Current thread 0x00007f412136e700 (most recent call first):
<no Python frame>

Thread 0x00007f4181d75780 (most recent call first):
  File "/home/user/.local/lib/python3.8/site-packages/py/_process/forkedfunc.py", line 76 in _child
  File "/home/user/.local/lib/python3.8/site-packages/py/_process/forkedfunc.py", line 50 in __init__
  File "/home/user/.local/lib/python3.8/site-packages/pytest_forked/__init__.py", line 67 in forked_run_report
  File "/home/user/.local/lib/python3.8/site-packages/pytest_forked/__init__.py", line 46 in pytest_runtest_protocol
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/main.py", line 348 in pytest_runtestloop
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/main.py", line 323 in _main
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/main.py", line 269 in wrap_session
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/main.py", line 316 in pytest_cmdline_main
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/config/__init__.py", line 162 in main
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/config/__init__.py", line 185 in console_main
  File "/home/user/.local/bin/py.test", line 8 in <module>
Fatal Python error: Aborted

Current thread 0x00007f412136e700 (most recent call first):
<no Python frame>

Thread 0x00007f4181d75780 (most recent call first):
  File "/home/user/.local/lib/python3.8/site-packages/py/_process/forkedfunc.py", line 76 in _child
  File "/home/user/.local/lib/python3.8/site-packages/py/_process/forkedfunc.py", line 50 in __init__
  File "/home/user/.local/lib/python3.8/site-packages/pytest_forked/__init__.py", line 67 in forked_run_report
  File "/home/user/.local/lib/python3.8/site-packages/pytest_forked/__init__.py", line 46 in pytest_runtest_protocol
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/main.py", line 348 in pytest_runtestloop
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/main.py", line 323 in _main
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/main.py", line 269 in wrap_session
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/main.py", line 316 in pytest_cmdline_main
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/home/user/.local/lib/python3.8/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/config/__init__.py", line 162 in main
  File "/home/user/.local/lib/python3.8/site-packages/_pytest/config/__init__.py", line 185 in console_main
  File "/home/user/.local/bin/py.test", line 8 in <module>

Any idea how this might happen ? Is this a pytest bug ?

I just had a realization: The pytest-forked code runs the actual test in a sub-process, but not the fixtures, correct ?
In my code the python-wrapped C++ application that is being tested is created and destroyed within fixtures, and I have strong suspicions that the crash actually happens in the teardown phase.
Assuming all of the above is true, how hard is it to run fixtures (at least all the ones that run per test rather than per session) within the forked process as well ?

That makes sense, but we try to run the entire setup/call/teardown in a subprocess:
https://github.com/pytest-dev/pytest-forked/blob/759912b731b6ba227dc274421f3be534184574bd/src/pytest_forked/__init__.py#L53-L75
Not sure how that plays with the fixture cache though.

...and I have yet to be able to build a minimal test case where a segfault in either setup, test, or teardown results in an error similar to what I reported earlier.

I have been able to trace this back to an incorrectly written signal handler in my own code. Sorry for the noise !

@stefanseefeld thanks for the followup


Consider using mybinder

See https://beta.mybinder.org/

Currently building of the binder is failing due to #276

If I recall, binder is not maintained anymore.
Cc: @thewtex

It's not currently working for me (constant spinning logo and server error
in the browser console).
On Mon, Jul 17, 2017 at 1:17 PM, Jean-Christophe Fillion-Robin <
<EMAIL_ADDRESS>wrote:

If I recall, binder is not maintained anymore.
Cc: @thewtex https://github.com/thewtex
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Radiomics/pyradiomics/issues/275#issuecomment-315820126,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHsfd-8KRqP-GoXt3WjZjJPbfiQcRSUks5sO5cggaJpZM4OaQOp
.

If you check the status, it is down: http://mybinder.org/status
@thewtex should be able to confirm, but if i recall they run out of funding. The model was not sustainable ( to be confirmed)

See the URL I included in the initial post ;-)

cc: @yuvipanda

Working example: https://github.com/minrk/ligo-binder and direct binder url https://beta.mybinder.org/v2/gh/minrk/ligo-binder/master?filepath=index.ipynb

Indeed, there are mybinder.org and beta.mybinder.org
I just wonder what is backing up beta.mybinder.org.
On Jul 17, 2017 1:24 PM, "Andrey Fedorov"<EMAIL_ADDRESS>wrote:

See the URL I included in the initial post ;-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Radiomics/pyradiomics/issues/275#issuecomment-315822107,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANXo_3NgancuNeqK6Idy6JR9v4jyT-0ks5sO5i8gaJpZM4OaQOp
.

@fedorov your original post didn't link to a working example!

indeed. What I meant to imply in an awkward manner is that I was not referring to http://mybinder.org. https://beta.mybinder.org/ can presumably be used for any repo that has a python notebook, so I was not sure what exactly was not working and timed out from https://beta.mybinder.org/.

Heya! Me and @choldgraf and others from the Jupyter Project have started assisting mybinder, and rewrote it to run on top of JupyterHub. beta.mybinder.org is the newer version, and should be a lot more stable (and we're committed to supporting it, and have structural support to doing so). The long term hope is that we make it really easy for institutions, publications and organizations to set up their own binder install, so people can use the same compatible repositories on any of them.
Am happy to help answer any other questions!

Thanks for the info @yuvipanda!  This will be very helpful.

@yuvipanda That is fantastic to hear! For organizations that do not have the resources to set up their own JupyterHub instance, how many resources are available and how long will they be available for?

+1 to what Yuvi said!
To @thewtex's question, Binder is a space that's evolving relatively rapidly right now so it's hard to say exactly what resources etc are available. That said, there's definitely a lot of interest in making the platform as easy as possible to deploy on other servers etc, and also a lot of interest in keeping the public mybinder.org service running as a public good. Feel free to open an issue over on the binderhub repo if there's a specific configuration setup you're concerned about (https://github.com/jupyterhub/binderhub)

Using the branch from #285, I was able to build and launch using MyBinder.
This required some changes to the dockerfile, as 3 notebooks are run as part of the build process, which assume a certain structure of the files and folders.

This is the link to the image.

just a quick thought - Binder now supports new features of repo2docker, including the ability to run shell scripts prior to generating the Docker image. So if you'd like to handle pre-build stuff with scripts instead of a Dockerfile, that should be possible now!

link to the image build upon radiomics/pyradiomics/master

FYI another free cloud-based notebook hosting platform: https://notebooks.azure.com
Disadvantages:

need to have a login and an account to run a notebook (since it first has to be cloned)
no support for Dockerfile for configuration

Advantages:

new features seem to be added regularly, seems to be actively supported: https://notebooks.azure.com/new
may be more robust than beta.mybinder, since it has MS/Azure back-end

FWIW, Binder is actively supported as well ;-)  (this wasn't true 9 months ago but it's a jupyter project now)
Also I'm curious what you mean by "more robust"?
(full disclosure: I'm on the jupyter team and working on the binder project :-) )

@choldgraf sorry, I didn't mean to offend you! I have a lot of respect to Binder, and it has some significant advantages!
What I meant by "actively supported" is that is has Microsoft and Azure backing it, so there is a clear entity with deep pockets paying for the cloud cycles. I also liked that there is a timeline with updates which seems to be updated quite often. With Binder, documentation seems to be quite dispersed, it is not clear how to do things beyond the example binders, and what is going on with the development. It was also confusing to me as a beginner to find my way around (I have not tried very hard, I admit) the soup of terms "binder", "beta binder", "jupyter hub", "docker2repo" - it is quite hard to understand how to navigate this and what is going on. BUT (and that's a HUGE "but"!!!) once I get something that "just works" - I am pretty happy - as long as it works - and I don't care that much how and why it works.
About robustness - I was referring to the discussion we had on gitter with @minrk. Yesterday I had a mysterious failure to launch, with no error messages, which you guys seemed to have traced down to github throttling due to lack of OAuth integration. @minrk seemed to suggest that with the Azure Notebooks there would be no problems loading (and that's understandable given how much resources MS has).

absolutely not offended :-) just trying to figure out where binder isn't meeting expectations so that we can figure out if/how we should try to improve things!
I totally agree about all the issues you just noted - some of them are just because the tech behind Binder is definitely still in a beta state...this stuff didn't exist in its current form > 4 months ago :-)  if there's something in particular that's confusing etc in the documentation, don't hesitate to open an issue in the binder or binderhub repos. One of our next focuses is to build up the documentation.

@choldgraf I think a good start would be to add a link to the documentation / "getting started" / examples to the front page: https://beta.mybinder.org/. It is quite confusing that the front page does not have any pointer to the documentation!

that's a good point! I agree that should be posted there...
FWIW, here are the docs we'll iterate on for the beta deployment: http://mybinder.readthedocs.io/en/latest/


Toolchain resolution seemingly failing and falling back to /usr/bin/gcc in some cases

I'm having trouble with the bazel-embedded rules in some cases. In a plain Ubuntu host, I can build my target with --platforms=@bazel_embedded//platforms:cortex_m7_fpu and it works fine and invokes external/bazel_embedded/toolchains/gcc_arm_none_eabi/gcc_wrappers/nix/gcc
(cd /home/parallels/.cache/bazel/_bazel_parallels/14af9fa9524e44cf06682e101a7eaa03/execroot/haystack && \
  exec env - \
    PATH=/home/parallels/.cache/bazelisk/downloads/bazelbuild/bazel-4.2.1-linux-x86_64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/parallels/go/bin:/home/parallels/gcc/gcc-arm-none-eabi-10-2020-q4-major/bin:/home/parallels/.gem/ruby/2.7.0/bin \
    PWD=/proc/self/cwd \
  external/bazel_embedded/toolchains/gcc_arm_none_eabi/gcc_wrappers/nix/gcc

However when I run the same thing in a docker environment (based on Ubuntu) it attempts to use /usr/bin/gcc and fails because -mthumb doesn't exist.
(cd /root/.cache/bazel/_bazel_root/18e8352205c71478753c3b63796033c0/execroot/haystack && \
  exec env - \
    PATH=/root/.cache/bazelisk/downloads/bazelbuild/bazel-4.2.1-linux-x86_64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
    PWD=/proc/self/cwd \
  /usr/bin/gcc ...

I used the --toolchain_resolution_debug flag and interestingly, in both the working and non-working case it output the exact same thing (I diff'd and they were exactly the same):
Starting local Bazel server and connecting to it...
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @bazel_embedded//platforms:cortex_m7_fpu: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv6-m_none; mismatching values: armv6-m, none
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @bazel_embedded//platforms:cortex_m7_fpu: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7-m_none; mismatching values: armv7-m, none
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @bazel_embedded//platforms:cortex_m7_fpu: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv4-sp-d16; mismatching values: fpv4-sp-d16
INFO: ToolchainResolution:   Type @bazel_tools//tools/cpp:toolchain_type: target platform @bazel_embedded//platforms:cortex_m7_fpu: execution @local_config_platform//:host: Selected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:cortex_m: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:cortex_m0: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:cortex_m1: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:cortex_m3: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:cortex_m4: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:cortex_m4_fpu: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:cortex_m7: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:cortex_m7_fpu: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:stm32f2xx: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:stm32f3xx: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:stm32f4xx: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:stm32f7xx: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:stm32g4xx: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @bazel_embedded//platforms:stm32h7xx: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16; mismatching values: x86_64
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @bazel_embedded//platforms:cortex_m7_fpu: Rejected toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_none; mismatching values: none
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @bazel_embedded//platforms:cortex_m7_fpu: Rejected toolchain @local_config_cc//:cc-compiler-armeabi-v7a; mismatching values: arm, android
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @bazel_embedded//platforms:cortex_m7_fpu: Rejected toolchain @local_config_cc//:cc-compiler-k8; mismatching values: x86_64, linux
INFO: ToolchainResolution: Target platform @bazel_embedded//platforms:cortex_m7_fpu: Selected execution platform @local_config_platform//:host, type @bazel_tools//tools/cpp:toolchain_type -> toolchain @bazel_embedded//toolchains/gcc_arm_none_eabi:arm_none_eabi_armv7e-m_fpv5-d16
INFO: ToolchainResolution: Target platform @bazel_embedded//platforms:cortex_m7_fpu: Selected execution platform @local_config_platform//:host,
INFO: ToolchainResolution: Target platform @local_config_platform//:host: Selected execution platform @local_config_platform//:host,
INFO: ToolchainResolution: Target platform @local_config_platform//:host: Selected execution platform @local_config_platform//:host,

More info:
Here's the bazel version I'm using: bazel 4.2.1
Here's the working case I have so far:

Regular user in Ubuntu VM

Here's the non-working cases I have found so far:

root user (via sudo command) in Ubuntu VM
docker environment (as root)
docker environment (as regular user with UID 1000)

Perhaps this is relevant: https://github.com/bazelbuild/bazel/issues/12712

I have run into this once or twice, but haven't really been able to zero in on it and reproduce it once it starts working again.

Here's the working case I have so far:
Regular user in Ubuntu VM

What version of ubuntu are you running?

Here's the non-working cases I have found so far:

root user (via sudo command) in Ubuntu VM
docker environment (as root)

This should work, but I would recommend against using root for you builds for security reasons.
Just as a hunch I would guess that this is something to do with how your bazelrc is being resolved with different users. Do you have a .bazelrc file in your workspace or in your home directory? The first thing I would try is to ensure that you have a .bazelrc in your workspace and that it is present in your Docker container. It should contain at least the following;
# Enable toolchain resolution with cc
build --incompatible_enable_cc_toolchain_resolution

Or alternatively, just add --incompatible_enable_cc_toolchain_resolution to your command line.
If debugging the .bazelrc doesn't work would you mind posting a minimal set of steps to reproduce the problem i.e. basic workspace + Dockerfile etc? If the project is open source a URL should suffice.

Ahh everything makes sense now...
You were right... I inadvertently had a .bazelrc in my home directory in addition to my workspace. I had that --incompatible_enable_cc_toolchain_resolution flag there hence why it worked in one of the four scenarios I listed.
It's still interesting the --toolchain_resolution_debug didn't help pinpoint the issue.
Anyway, I'll go ahead and close this one out.


Matplotlib 2.0 Compatibility

I tried running flowcal with matplotlib 2.0 and received the following error. Downgrading to 1.5 stopped this from happening. This was done in 1.0.0
Beads ID RP20170128b_001...
Loading file "RP20170128b_001.fcs"...
Performing data transformation...
Performing gating...
Plotting density plot and histogram...
Traceback (most recent call last):
  File "C:\Anaconda2\lib\runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "C:\Anaconda2\lib\runpy.py", line 72, in _run_code
    exec code in run_globals
  File "build\bdist.win32\egg\FlowCal\excel_ui.py", line 1435, in <module>
  File "build\bdist.win32\egg\FlowCal\excel_ui.py", line 1350, in run
  File "build\bdist.win32\egg\FlowCal\excel_ui.py", line 431, in process_beads_table
  File "build\bdist.win32\egg\FlowCal\plot.py", line 1507, in density_and_hist
  File "build\bdist.win32\egg\FlowCal\plot.py", line 1012, in density2d
  File "C:\Anaconda2\lib\site-packages\matplotlib\axes\_base.py", line 2948, in set_xscale
    ax.xaxis._set_scale(value, **kwargs)
  File "C:\Anaconda2\lib\site-packages\matplotlib\axis.py", line 710, in _set_scale
    self._scale.set_default_locators_and_formatters(self)
  File "build\bdist.win32\egg\FlowCal\plot.py", line 545, in set_default_locators_and_formatters
  File "C:\Anaconda2\lib\site-packages\matplotlib\ticker.py", line 2067, in __init__
    self._linthresh = transform.linthresh
AttributeError: '_LogicleTransform' object has no attribute 'linthresh'
Press [Enter] to finish...

I'm gonna close this in favor in #233, since it has more detail (like library versions) and is using the most recent version.
Also, version 1.0.0 (which you are claiming you used) would not have produced this error, since it doesn't have logicle scaling.


Duplicate articles?

There seem to be two copies of the article ENTOMOLOGY with extremely minor differences. Any idea why?

https://raw.githubusercontent.com/TU-plogan/KnowledgeProject/main/eb07/TXT/e9/kp-eb0709-005901-0069-v1.txt
https://raw.githubusercontent.com/TU-plogan/KnowledgeProject/main/eb07/TXT/e9/kp-eb0709-005901-6025-v1.txt

Good catch, Ben. We had to substitute better images for the first 10 pages or so, and in the TEI, I left the old version in by mistake. (The TEI includes links to the original images.)


Make simpler the way of getting rowsAffected for a Promise

When using promises, it is cumbersome to keep a reference around to the sql.Request so that I can get the rowsAffected. Perhaps there is a better place to store the rowsAffected.

I definetely agree. Suggestions are welcome.

@tomkel thanks for making the issue. I was trying to get to request.rowsAffected and the example within readme doesn't show it. I could have thought about it being on request, but as this is my first time working with mssql, I thought my procedure was wrongly defined on the MSSQL server side.

Implemented in v4 alpha. Promises are now resolved with a result object that contains every important information about the server response including the rowsAffected variable.

Nice! Thanks @patriksimek . Glad to see development active on this project.


I cannot get it to work for me

ImportError: cannot import name 'clear_chat_log' from 'modules.chat' (A:\text-generation-webui-main\modules\chat.py)
is the error i get any time i use the "python bot.py" start command
Any ideas what I might be doing wrong? please help!

I haven't been maintaining this unfortunately. The last working version of oobabooga was 19f7868


?deposit in to bank ?

https://github.com/Ubeswap/ubeswap-farming/issues/2

Convert in to usd and deposit into account crescent city coast central credit union


Can't have a custom injected field's name

@pacu This is the "sequel" issue of #66.
The diagnosed issue is about generating two entities having a relationship between them so that if entity B is not the owner of this relationship but A is AND A's injected field from B doesn't have the same name as B (for instance B is ExerciseTip but the injected field is only tip), it fails.

I might be wrong, but I don't think JHipster supports this...
I just tried with this example, and I changed the question/answer flow by answering like this:
? What is the name of this relationship in the other entity? carDriver

@andidev, @CarlKlagba maybe you guys can hopefuly prove me wrong, I might lose my mind over this!

I need someone from the JHipster team to confim this ASAP. I won't be able to work next week, and I want to get this closed ASAP too.

Not sure if I understand the issue. Maybe it gets more clearer  if you provide a jdl file for the issue.

Okey if we look at the Car Driver example from the doc, I can  confirm that setting the name of the relationship in the other entity to carDriver will only work if you also change the relationship name in the other entity to exactly the same name.
At least this is how it is designed to work.

In other words only changing to carDriver will should not work.

I'm very sorry Anders if I didn't give any JDL or flow, I assumed #66 would be clear enough... Guess I couldn't be wronger, my bad. Anyway, many thanks for having looked into this.
It should only be a field name... I don't get it, why does it make my tests fail?

I'll have a quick look into it

Does the test fail in Jhipster or Jhipster UML?

JHipster

By the way, I didn't use JHipster-UML to generate my .json files. I first tried the usual Q&A just to be sure...

Okey, if I use JDL should this one recreate the issue?
/**
  Abstract Exercise type. All exercise types have to extend this class
*/
entity Exercise {
  name String required,
  description String required,
  totalScore Integer required min(0)

}

entity ExerciseTip {
  /** the tip itself **/
  hint String required,

  /** further description of the tip itself **/
  tipDetail String

}
relationship ManyToMany {

  Exercise{tip} to ExerciseTip{exercise}
}

It should. I've tweaked the parser and the entity creator, but you should be able to reproduce the issue.

Should I use the master version?

Yes

Okey so I am a bit confused here I must say,
I'm using the jdl mentioned earlier with no comments:
entity Exercise {
  name String required,
  description String required,
  totalScore Integer required min(0)

}

entity ExerciseTip {
  hint String required,
  tipDetail String

}
relationship ManyToMany {
  Exercise{tip} to ExerciseTip{exercise}
}

and I get the following entity json files generated in the .jhipster folder:
Exercise.json
...

  "relationships": [
    {
      "relationshipId": 1,
      "relationshipName": "exerciseTip",
      "otherEntityName": "exerciseTip",
      "relationshipType": "many-to-many",
      "otherEntityField": "id",
      "ownerSide": true
    }
  ],
...

and
ExerciseTip.json
  "relationships": [
    {
      "relationshipId": 1,
      "relationshipName": "exercise",
      "otherEntityName": "exercise",
      "relationshipType": "many-to-many",
      "ownerSide": false,
      "otherEntityRelationshipName": "exerciseTip"
    }
  ],

Shouldn't the result be
Exercise.json
...

  "relationships": [
    {
      "relationshipId": 1,
      "relationshipName": "tip",
      "otherEntityName": "exerciseTip",
      "relationshipType": "many-to-many",
      "otherEntityField": "id",
      "ownerSide": true
    }
  ],
...

and
ExerciseTip.json
  "relationships": [
    {
      "relationshipId": 1,
      "relationshipName": "exercise",
      "otherEntityName": "exercise",
      "relationshipType": "many-to-many",
      "ownerSide": false,
      "otherEntityRelationshipName": "tip"
    }
  ],

or I'm I too tired or missing something?

I think the result should be for Exercise.json:
...

 "relationships": [
    {
      "relationshipId": 1,
      "relationshipName": "exerciseTip",
      "otherEntityName": "exerciseTip",
      "relationshipType": "many-to-many",
      "otherEntityField": "id",
      "ownerSide": true
    }
  ],
...

I think I know why, the JHipster-UML parser does have the code to generate the issue, but I commented it out because I wanted to find if I created this issue in the first place or not.
I've just created a branch for you called "issue77" (the tests for this branch don't pass, it's normal).
Try to create the entities with the questions... I don't think the JHipster-UML code is not reliable to find this issue.

Are you sure "relationshipName": "exerciseTip" should'n be "relationshipName": "tip" in * Exercise.json* when using the the following jdl relation?
relationship ManyToMany {
  Exercise{tip} to ExerciseTip{exercise}
}

This makes me really confused :confused:
I'll try creating it with Jhipster then.
I tried the issue 77 branch and it looks a bit better but still i dont like the "relationshipName": "exerciseTip" in it =)

This is how I would answer the questions asked by jhipster entity generator if I would try to model the following jdl relationship
relationship ManyToMany {
  Exercise{tip} to ExerciseTip{exercise}
}

Entity generation in jhipster:
$ jhe ExerciseTip
The entity ExerciseTip is being created.
Generating field #1
? Do you want to add a field to your entity? No
=================ExerciseTip=================
Generating relationships with other entities
? Do you want to add a relationship to another entity? Yes
? What is the name of the other entity? Exercise
? What is the name of the relationship? exercise
? What is the type of the relationship? many-to-many
? Is this entity the owner of the relationship? No
? What is the name of this relationship in the other entity? tip

$ jhe Exercise
The entity Exercise is being created.
Generating field #1
? Do you want to add a field to your entity? No
=================Exercise=================
Generating relationships with other entities
? Do you want to add a relationship to another entity? Yes
? What is the name of the other entity? ExerciseTip
? What is the name of the relationship? tip
? What is the type of the relationship? many-to-many
? Is this entity the owner of the relationship? Yes
? When you display this relationship with AngularJS, which field from 'ExerciseTip' do you want to use? id

and this sets "relationshipName" to "tip" in the "Exercise.json" entity.
Though when running mvn test it fails. This seems to be a JHipster 2.23.0 issue.

The same issue is there in JHipster 2.22.0
@jdubois
Has the generation of the relationship type mentioned in my last comment ever worked in JHipster?

Unless I'm wrong, the only mention of "tip" in the JSON files is in ExerciceTip.json, in otherEntityRelationshipName. That's what I noticed when answering the questions. Might be wrong though, but your answers do seem valid too. It would be nice to have a doc about it =)


Add entrypoint extraction to AppYaml parser

part of #840
also fixes some naming in tests.
NOTE: build is broken because of #841

rebased, this should be ready for review


Update AppVeyor config with ~faster npm install

Only test against stable and LTS versions of node since AppVeyor goes pretty slow.
@bcoe I noticed that after dropping the Travis build times to 1/4th of what they were on Travis in #251, AppVeyor's build takes even longer... so this is an attempt to streamline it by using the version of npm that comes with each node distro and only going for stable and LTS versions. Thoughts?

@JaKXz this seems to be failing, kicked off the build twice. Perhaps try adding back the npm update, and see if this helps; if not, we might not be able to pull in 6.x yet.

@bcoe I don't think the npm update is what's broken here, since node@6 comes with a version that I'm pretty sure npm install -g npm@latest would install [at time of writing] - see the AppVeyor logs around line 507:
node --version
v6.1.0
npm --version
3.8.6

Though I'm not sure why it would pass on Travis and not AppVeyor with node@6.

@JaKXz I think we'll need to spin up a Windows VM to test this one out.

Probably related to:
https://github.com/sindresorhus/ava/issues/814

whoa it's passing now... 🎱

Yes. Node 6.2.0 reverted a regression that almost certainly affected this.

0.12 remains in LTS mode through the end of the year. We should not drop it yet.

@JaKXz interesting that it started working, maybe the version of 6 was updated.


[WSL-332] Allowing WSL Azure CI to be used outside the Ubuntu organization

Raison d'etre
Reusable actions that are self-hosted cannot be used across different organizations. This means we need to re-think our approach.
Basic structure
The only reason we had to use a reusable action was that we need the RDP and "Main" jobs to run concurrently. Hence, workflows will use three actions:

vm-setup: This action starts the Azure VM and connects to the machine via RDP.
Your main job goes here. This job runs concurrently to vm-setup so as to use the RDP session. You can use the "convenience actions" explained later.
vm-stop stops the virtual machine. It runs after your main job, and concurrently to vm-setup, thereby killing the RDP session.

Convenience actions
These actions have been created because I believe they have grat reusability potential. They are all prefixed with "wsl-" and I would continue this pattern should we develop any new ones.

wsl-install installs or updates WSL and a distro of your choice (if any).
wsl-checkout clones your repo into WSL.
wsl-bash runs an arbitrary bash script within WSL (circumventing session 0 issues by piggybacking on the RDP session).
wsl-powershell runs an arbitrary powershell script in Windows where WSL is allowed (circumventing session 0 issues by piggybacking on the RDP session).

Customization
Users with heavier workloads may want to customize the start-stop cycle of their VMs. They can do that and still use the convenience actions which are our main contribution.
Examples
See it in use here:

Example usage: wsl-example.yaml
Real usage: https://github.com/EduardGomezEscandell/GoWSL/pull/10.

Pending improvements

wsl-install should be converted from a "composite" action to a "javascript" one. This would allow us to create a cleanup action that would uninstall and unregister the distro.
wsl-checkout should be converted from a "composite" action to a "javascript" one. This would allow us to remove the repo in the cleanup.
wsl-powershell has a problem with the its $env:Path, as it does not inherit the path of the runner. I mitagated this appending one path to the other, but there are two options:
$env:Path=$env:Path;${runnerEnvPath}: Avoids overriding values. I used this one.
$env:Path=${runnerEnvPath};$env:Path: Fixes things like Python not working due to being shadowed by an alias that prompts you to install it. This may happen to other software.

There is one inconvenience:
When you use an action such as actions/setup-go@v3, Go is added to the path. However, if you connect via PsExec, this is not in the path for some reason (investigation pending).
Hence, you have to manually find the Go executable; or more simply have it installed in the machine already. This will be true for any setup-* action (think Go, Flutter, Python, etc.).

I realize you are still working on this, but let's check those questions before proceeding.
I'm working on ironing out the last few details, last changes will be very small so feel free to review.

Example test run: https://github.com/EduardGomezEscandell/GoWSL/actions/runs/3892827764/jobs/6644724193

Example CI run:
https://github.com/EduardGomezEscandell/GoWSL/actions/runs/3894111684/jobs/6647673914
This is an expected failure.
For an example success, see either of these:

https://github.com/ubuntu/WSL/actions/runs/3894059716/jobs/6647613467

Sometimes Example action using WSL will be auto-cancelled if  End-to-End Tests is already running because they share the same concurrency group. There is no way to wait instead of cancel, and it seems to be a race condition in our case.
Info on why it cancels: https://stackoverflow.com/a/74994502

Yeah seems like the rootfs download is timing out. Will keep retrying for now.
We should soon implement some sort of caching, it takes too long anyways.


Electron 1.1.0 for Windows needs vcruntime140.dll

electron-packager, under Windows, is linking against msvcp140.dll, whereas electron 1.1.0 needs msvcp140.dll and vcruntime140.dll. This causes all built apps to not run on Windows if using electron 1.1.0 (which is currently the latest version).
This issue can be fixed by manually placing msvcp140.dll and vcruntime140.dll, obtained via the Visual C++ Redistributable for Visual Studio 2015 , in the root directory of the built Electron application.

Which version of electron-packager are you using?

7.0.1.

What version of Electron are you building with?

1.1.0.

What is the host platform are you running electron-packager on?

Windows 10 x64.

What target platform(s)/architecture(s) are you building for?

Windows 10 x64.

https://github.com/electron/electron/pull/5538 1.1.0 electron is broken.

As @develar mentioned, this is not an electron-packager bug, but rather an upstream Electron bug. However, I'm going to keep this open until Electron releases a new version.

@malept Wise move.

@kaepora whoa just realized cryptocat is using this, awesome!

@maxogden :smiley: Yes, I'm very satisfied with, and a big fan of, Electron and Cryptocat is doing very well since adopting the framework.

Electron 1.1.1 was released 6 days ago, so I'm closing this.


Brownfield deployment support: add "dummy" resource creation

An initial idea for brownfield support: allow users to create a "dummy" resource which already has its network parameters (subnet, IP, etc.). As long as the network's address space is non overlapping with anything else in the deployment, the controller can take this network info and then perform other Paraglider requests (like creating VPN connections) on the network. Alternatively (or in addition), this dummy resource could be the network itself rather than a specific resource within it.

Triage: We don't think that this is a necessary stepping stone to get #170, but something we can do in addition to it.

@smcclure20 do you think this is in the correct milestone? It's vnet, but perhaps it should be backlog?

Maybe we can even close this. I think Julian's project is somewhat an alternative to this.

Let's chat about it on our next chance. Marking as needs discussion/vnext.


logo?

I made a logo for mercury a while back, but it doesn't look like it'll get adopted (3 months, no replies from maintainers); so if we like it and want it we could totally use it for virtual-app.
Not that we need a logo, but it might be fun.


How do I add new properties to hiveobject

class Person extends HiveObject {
@HiveField(0)
String? name;
@HiveField(1)
int? age;
}
class PersonAdapter extends TypeAdapter {
@override
final int typeId = 0;
@override
Person read(BinaryReader reader) {
return Person(
name: reader.readString(),
age: reader.readInt()
);
}
@override
void write(BinaryWriter writer, obj) {
writer.writeString(obj.name ?? '');
writer.writeString(obj.age ?? 0);
}
}
// like this, if i want to add "address" on Person class, what should I do
// an error will be reported if I add "address: reader.readString()," to PersonAdapter.read method --- Unhandled Exception: RangeError: Not enough bytes available.
// can u tell me what I should do，thank u, orz

I have the same problem


How to disable the background when ng-progressbar is enabled?

how can i make the background inactive when ng-progressbar is enabled?

@sajeetharan what do you mean by make the background inactive, which background?

@MurhafSousli  i meant to behave it like a modal window, anyway i found the solution

@MurhafSousli What is the solution? please give the solution.


Fix robot helpers delegation to adapter and events

Robot 'send', 'reply', 'messageRoom' methods delegate invocations to
adapter but using as 'this' the robot while they should be using the adapter.
Robot 'on', 'emit' methods delegate invocations to events but using as
'this' the robot but they should be using the events.
The original CoffeeScript code from release 2.19.0 uses simple delegation, i.e. send, reply, messageRoom, on, emit. This PR should address #1386.

is there any ETA for these fixes to be released as part of a new version? 3.0.1 is unusable because of this.

Yeah, it took me sometime to realize this merge from September last year isn't published. Scripts are blowing up because of it 😕


Compatibility Issue on Apple Silicon Mac - Simulator Build Fails with RxSwift or AdyenCard Modules

I am encountering a compatibility issue when using the mobile_scanner package on an Apple Silicon Mac. The project builds and runs fine on a real device, but it fails on the simulator with the following error:
Swift Compiler Error (Xcode): Could not find module 'RxSwift' for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator
Steps to Reproduce:

Add the mobile_scanner package to the pubspec.yaml:

dependencies:
  mobile_scanner: ^5.1.1

Open xcode and add rxswift https://github.com/reactivex/rxswift

Attempt to build and run the project on the iOS simulator.

Observed Behavior:

The build fails with a Swift Compiler Error indicating that the RxSwift  module is not found for the x86_64 architecture, but is found for arm64.
Rxswift, AdyenCard and other dependencies are compatible and were working fine before adding mobile_scanner
The issue does not occur when building for a real device
The issue does not occur when building on simulator in Rosetta
The issue does not occur when building on Intel Macbook

Removing the mobile_scanner package resolves the issue, but I need to use this package in my project.
Modules

Build Settings

I have tried playing with the Architecture no success.
Any insights or fixes would be greatly appreciated.
Thank you for your assistance!

We do have https://github.com/juliansteenbakker/mobile_scanner/issues/1018 as well, which indicates that we have issues with Apple Silicon Macs when compiling. However, I do not have access to an Apple Silicon Mac to debug this just yet.

@bashcious We have preliminary support for the Vision API in version 7.0.0-beta.1, which restores support for building on the iOS Simulator. Testing the scanner on the Simulator won't work as it has no camera.
Can you retest this with that beta version? (do bear in mind that not everything in version 7.0.0 is working yet)


Must not exit 0 when git command fails

When there is no git repository, we get:
fatal: not a git repository (or any of the parent directories): .git

but exit code is 0.

hi @teohhanhui !
Thanks for report, but can you describe scenario when you got such an error?

As I've mentioned, when the current directory (and its parents) is not a git repository.

why it would not be a repo?

Run the tool in any directory that's not a git repo. It should not exit with 0 status, but it does. That's what this bug is about.

i understand what you are saying, still wondering why to run it on non-repo dir

I ran into this bug in a CI environment where I did not do a git clone, but the build was passing because of this bug.

Sometimes it could be because you're in the wrong directory, but you wouldn't notice your build is not working as intended if it passes.

ref #261


doc: document approach to eventual consistency

There is probably a better place for this documentation but we'd like to move
this elsewhere than a github issue. We can move this to a more appropriate
location with the documentation effort.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>Closes #146
cc @moxiegirl

@stevvooe Understood.  If you want to merge this I'll sort it out.

LGTM

you rock :metal:

@stevvooe at the office, picture shot last week :)


Separate file with versions

I am implementing electron support directly in Browserslist. And to reduce Browserslist file size, I need to separated electron-to-chromium/versions with just short versions.
/cc @Kilian

Sure, no problem :) Would doing an import { versions } from 'electron-to-chromium'; also not be transpiled down to just versions, or does it keep the entire file around?
I'll have to figure out how so allow for that type of import. I'll also need to consider if keeping the electronToBrowserList(); function is then still useful to keep around. Any tips or thoughts?

import { versions } from 'electron-to-chromium' is not a solution, because it will import whole electron-to-chromium/index.js to Browserslist on client side ;).
Just move var versions = { to versions.js and import it in index.js:
var versions = require('./versions')

just pushed to this branch:
https://github.com/Kilian/electron-to-chromium/tree/separate-version-file
Will merge it in tomorrow (so I can check if my automated update script works tonight). Anything you wanna add?

@Kilian you are fast :) Looks great.
I finished integration (all electron <= 10 queries will work too). Will release Browserslist and Autoprefixer just after your release.
Also what is your Twitter name?

Thanks! Twitter name is @kilianvalkhof.

Ping :). Browserslist and Autoprefixer releases are waiting ;)

1.2.0 is ready for you! :)

Thanks :)


iOS negative keyboard height

Hi, first of all great project this is really useful! However I have stumbled across an issue on iOS.
https://user-images.githubusercontent.com/88309205/153897931-f4adb041-9d8c-4691-9d6c-bca15838f3e2.mov
It seems that the updateKeyboardDimensions function in<EMAIL_ADDRESS>is calculating a negative keyboard height of -174 when the keyboard closes which is different to it's original state where keyboard height is 0.
I've managed to solve this issue myself by using Math.max in this calculation, although I'm not sure if this is going to cause issues elsewhere!

This could also be solved by adding the 'keyboardDidHide' listener to ios, resetting the value to 0 when it closes.

Hi! This behaviour is now included in RN 0.68 and you don't need this library anymore. Refer to https://github.com/facebook/react-native/pull/31402. Thanks!


Upgrade dropbox to v16.3.27

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

@reitermarkus this is a beta build - the stable build is still 15.4.22.
Note that this update was previously not merged.


Support neovim

Great work, thanks! It seems that you are using VIM 8 APIs (e.g. popup_create) but it would be great to support neovim as well, since many other floating window based plugins operate both on vim and neovim.

Really looking forward to this. Thank you @AndrewRadev

This is significantly more complicated than I expected it to be. I created a branch named neovim-support that sort of works, but with a lot of issues:

No border -- Neovim doesn't support that yet, but that seems like not much of a problem
The first time the popup is opened, it always throws an error, failing to enter it. I can't understand why, other than some weird combination of the quickfix window and popups. What I'm doing is catching the error and ignoring it -- moving the cursor shows the popup successfully.
There's an annoying redraw flicker when moving the cursor that is not there with Vim. I can't think of a way to solve it. I imagine Neovim's floating windows are "heavier" than Vim's popups, since they're more featureful? I considered reusing the same window and changing its buffer (instead of deleting and recreating), but I couldn't find any API to do that. Maybe there's the option to enter it and :bufnr the target buffer, but this issue is still not the worst one.
Occasionally, some preview will not get syntax highlighting. This is not Neovim-specific, exactly, because I had this happening in Vim as well. However, in Vim, I worked around the issue by running the "show popup" function with a timer: call timer_start(1, {-> s:ShowPopup()}). This doesn't seem to work in Neovim at all. Moreover, with Vim, even if the buffers weren't syntax highlighted, pressing <enter> would open them normally. In Neovim, pressing <enter> on a line with a non-syntax-highlighted preview would open the buffer in the quickfix window instead.

The quickfix window seems to load buffers in a very odd way in both Vim and Neovim, and it seems like this is causing some really strange issues. With Vim, I could find workarounds, but I can't figure anything out for Neovim. If you'd like, try the branch out, but to me, it seems practically unusable :/. I might try opening issues to Neovim, but I need to figure out how to describe the issue and reproduce them with some test code.


⚠ Bofrost.be has degraded performance

In 3f3b702, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1270 ms

Resolved: Bofrost.be performance has improved in 8c56d92 after 28 minutes.


Update ghcr.io/autobrr/autobrr Docker tag to v1.42.0

This PR contains the following updates:

Package
Update
Change

ghcr.io/autobrr/autobrr
minor
v1.40.1 -> v1.42.0

Release Notes

autobrr/autobrr (ghcr.io/autobrr/autobrr)
v1.42.0
Compare Source
Changelog
New Features

56ef3a5: feat(actions): qBittorrent add first-last piece priority (#1517) (@s0up4200)
f8715c1: feat(auth): improved error handling during login (#1523) (@s0up4200)
0016228: feat(indexers): add External Identifier to map with ARR indexers (#1534) (@zze0s)
28172cf: feat(indexers): add HD-Only (#1525) (@s0up4200)
3202c60: feat(indexers): update release baseurl on update (#1532) (@zze0s)
19e129e: feat(releases): delete based on age/indexer/status (#1522) (@s0up4200)
3dab295: feat(web): add theme toggle to navbar (#1540) (@s0up4200)
190994c: feat(web): set Safari window colors (#1543) (@s0up4200)

Bug fixes

8120c33: fix(auth): cookie expiry and renewal (#1527) (@martylukyy)
56aa7dd: fix(feeds): parse magnet URI from enclosure (#1514) (@zze0s)
d558db2: fix(filters): export not working with Safari (#1505) (@zze0s)
9832076: fix(indexers): irc baseurl override for links (#1537) (@zze0s)
3e7c436: fix(indexers): new IPT announce bot name (#1548) (@martylukyy)
9d08f14: fix(web): disable pnpm strict version check (#1519) (@s0up4200)
9c8c4a9: fix(web): disable autocomplete on APIKeyAddForm and FilterAddForm (#1546) (@s0up4200)
5945b51: fix(web): qbittorrent action rules spacing (#1544) (@martylukyy)
5bae500: fix(web): responsive account settings (#1545) (@martylukyy)
7134e06: fix(web): root pending component placement (#1547) (@martylukyy)

Other work

ad6ef22: build(deps): bump CatChen/eslint-suggestion-action from 3 to 4 in the github group (#1536) (@dependabot[bot])
f820060: build(deps): bump the golang group with 6 updates (#1528) (@dependabot[bot])
575944d: chore(database): remove unused test func (#1465) (@kenstir)
ccff369: chore(indexers): danishbytes remove unused url (#1526) (@kbhsn4)
ce17292: chore: add missing license headers (#1512) (@martylukyy)
7b9993b: chore: bump pnpm to 9.0.2 (#1515) (@chenrui333)
4311341: docs: add macos homebrew installation (#1518) (@s0up4200)
2f9b82c: refactor(apiclient): simplify query in release delete method (#1538) (@s0up4200)

Full Changelog: https://github.com/autobrr/autobrr/compare/v1.41.0...v1.42.0
Docker images

docker pull ghcr.io/autobrr/autobrr:v1.42.0

What to do next?

Read the documentation
Join our Discord server

v1.41.0
Compare Source
Changelog
New Features

da53230: feat(filters): validate existence of external exec cmd (#1501) (@zze0s)
facb5b2: feat(indexers): Nyaa add trusted, remake and batch tags (#1482) (@Flupster)
7cd5d99: feat(indexers): add KeepFRDS (#1484) (@KyokoMiki)
b181231: feat(macros): add Artists (#1493) (@martylukyy)
3c3b47f: feat(macros): add IndexerName (#1511) (@zze0s)
c43e2c7: feat(notifications): add support for custom Telegram api url (#1508) (@KyokoMiki)
72ca7a8: feat(releases): replace misc info in incognito mode (#1509) (@s0up4200)
f1b4214: feat(web): auto refresh dashboard stats (#1490) (@martylukyy)

Bug fixes

f26c33a: fix(indexers): STC parse resolution (#1489) (@martylukyy)
b58ead7: fix(logger): properly SetGlobalLevel on all levels (#1504) (@s0up4200)
5857945: fix(user): change username (#1502) (@zze0s)

Other work

1b02add: build(deps): bump rls to v0.5.12 (#1506) (@s0up4200)
83f6d78: build(deps): bump the golang group with 4 updates (#1485) (@dependabot[bot])
5077829: build(deps): bump the npm group in /web with 23 updates (#1486) (@dependabot[bot])
b44d55e: chore: add missing license headers (#1499) (@martylukyy)

Full Changelog: https://github.com/autobrr/autobrr/compare/v1.40.1...v1.41.0
Docker images

docker pull ghcr.io/autobrr/autobrr:v1.41.0

What to do next?

Read the documentation
Join our Discord server

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (v1.42.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


fix: automatically add namespace when needed

fixes: #590

:tada: This PR is included in version 2.13.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: Handle release through workflow

Description
In this PR, we're creating a GitHub workflow that automates the release process. Instead of manually creating the release, the workflow will retrieve the tag from the commit and create a draft release, including the changelog for the latest commits.
Related Issues
Closes #25
Checklist

[X] I have tested this code.

Have updated the destination branch of this PR to test this feature

Hey @aswath-s-tw how did it go? btw, can you add the hacktoberfest-accepted label to this PR


CUFFT_INTERNAL_ERROR when running HorNet

{RuntimeError}cuFFT error: CUFFT_INTERNAL_ERROR at "HorNet.py", line 64, in forward
x2 = torch.fft.rfft2(x2, dim=(2, 3), norm='ortho')
Hello, Did you ever come across this error about HorNet?

Hi, thanks for your interest in our work!
We didn't encounter such error about HorNet under our env. What's your pytorch version and nvcc version?


Atom Beautify Does not work and Does not uninstall

Description
The package area on setings shows aton-beautify but in the menu bar it does not show, I tried to uninstall but didn't work either.
Checklist
I have:

[x] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[x] Reloaded (or restarted) Atom to ensure it is not a caching issue
[x] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[ ] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ ] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

after a long time I figure out that int the folder of atom-beauify only have some folders inside and any files. So I think that is all ok for now


Allow the Django Sites package to be optional

It would be a lovely addition if there was no longer a need for the Django Sites package.
The current Sitemaps package has a brilliant fallback:
I think you might be able to replace https://github.com/jazzband/django-robots/blob/be2e781b46aeceb728303f46da585d237e079409/src/robots/views.py#L21 and just use what Django provides: https://github.com/django/django/blob/main/django/contrib/sites/shortcuts.py#L18

Here's an updated code for django-robots that allows the Django sites package to be optional:
from django.conf.urls import url
from django.http import HttpResponse
from django.urls import reverse
from django.views.generic.base import View
from django.contrib.sites.shortcuts import RequestSite, get_current_site

class RobotsView(View):
    def get(self, request, *args, **kwargs):
        content = "User-agent: *\nDisallow:\n"
        protocol = request.scheme
        site = get_current_site(request) if 'django.contrib.sites' in settings.INSTALLED_APPS else RequestSite(request)
        domain = site.domain
        sitemap_url = '{}://{}{}'.format(protocol, domain, reverse('sitemap'))

        content += 'Sitemap: {}\n'.format(sitemap_url)

        response = HttpResponse(content, content_type='text/plain')
        return response

urlpatterns = [
    # ... your other URLs ...
    url(r'^robots\.txt$', RobotsView.as_view(), name='robots'),
]

Changes Made:

Updated get_current_site() method to use RequestSite instead of django.contrib.sites.shortcuts.get_current_site when django.contrib.sites is not in INSTALLED_APPS
Added the protocol to the sitemap URL to make it a full URL using the request.scheme attribute
Moved the sitemap URL into the content variable and appended it to the User-agent and Disallow directives using the Sitemap directive

Note that you will need to add the 'django.middleware.locale.LocaleMiddleware', middleware to your settings file to enable multilanguage support in the robots.txt file.


Allocate and release unique IDs based on build directory

With this change, we should have confidence that the allocated IDs are unique given that there are sufficient IDs available to fan out to the requested number of execution slots.
If we run out, a warning will be printed and the job will have no ROS_DOMAIN_ID value set.
Full CI, since paths are involved:

Linux
Linux-aarch64
Windows

Fresh CI after the review tweaks:

Linux


Fix errors with isnull() that appear with pandas 0.21

xref #1542

[x] Tests added / passed
[x] Passes git diff upstream/master | flake8 --diff
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API

The culprit is the truly monstrous _func_slash_method_wrapper function where we read names from methods if need be:
https://github.com/pydata/xarray/blob/master/xarray/core/ops.py#L211-L216
We should have a more sane way to add methods on xarray objects, but this fix will have to do for now.


Feature/aaronchan32/profile backend

Tracking Info
Resolves #31
Changes

Asynchronously fetch username data from firestore based user's UID
Add functioning sign-out button
Redirect unauthenticated user to TakeAction page if they try to access profile page from navbar

Testing

Requires change made from Routing auth #29
Please merge the changes from above for everything to work. Unless future changes to profile.dart are made in issue 29, accept current changes for profile.dart when merging.

Confirmation of Change

Demonstrating protected route and username fetch

https://user-images.githubusercontent.com/42254254/235544058-4ebd54d4-f41c-48d2-9626-1b1e0786b953.mp4

Implemented on Routing Auth PR


Jibri - org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized

Hello Community,
When I installed the Helm Chart with no modifications besides required variables, Jibri will fail to record meetings.  After investigation, I found the error below was being generated on the jibri server.  I was able to solve the error by creating the jibri and record user manually on the prosody server.  Thereafter, I was able to record a meeting.
Therefore, there seems to be an issue when the users are created.  I was able to resolve by reading the post here: https://community.jitsi.org/t/jibri-saslerror-using-scram-sha-1-not-authorized/63146/3.
Anyone else experiencing this issue?  Is this a bug or is there a workaround?
Error
Jibri 2023-03-20 01:52:18.249 WARNING: [31] [hostname=jitsi-meet-prosody.default.svc.cluster.local id=jitsi-meet-prosody.default.svc.cluster.local] MucClient.lambda$getConnectAndLoginCallable$9#651: Failed to login. Disconnecting to trigger a re-connect.
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:286)
at org.jivesoftware.smack.AbstractXMPPConnection.lambda$new$2(AbstractXMPPConnection.java:407)
at org.jivesoftware.smack.NonzaCallback$ClassAndConsumer.accept(NonzaCallback.java:177)
at org.jivesoftware.smack.NonzaCallback$ClassAndConsumer.access$200(NonzaCallback.java:166)
at org.jivesoftware.smack.NonzaCallback.onNonzaReceived(NonzaCallback.java:46)
at org.jivesoftware.smack.AbstractXMPPConnection.parseAndProcessNonza(AbstractXMPPConnection.java:1444)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.access$1700(XMPPTCPConnection.java:131)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1010)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$700(XMPPTCPConnection.java:916)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:939)
at java.base/java.lang.Thread.run(Thread.java:829)

One issue I found which is that I needed to uncomment the below settings in values.yaml.  It is not mentioned in the README.md, and I found it when investigating the entire values.yaml file.  Maybe good a good idea to add instructions to the README.md.    I can submit a PR if it helps.
Uncomment this if you want to use jibri:
- secretRef:
name: '{{ include "prosody.fullname" . }}-jibri'

Hello @palmtown!
Sorry for the late answer. Yes, it's necessary to uncomment this part in values.yaml, so that Prosody knows about Jibri and registers it in its' own internal user database.
I'll add this to the README soon, thank you.

Fixed in 0b952897 (and release v1.3.4).


Update code samples to work with newer ADAL lib

@LordJZ What version of ADAL are you using with this change?

@LordJZ What version of ADAL are you using with this change?

@LordJZ I am closing this PR. I have updated the article to make it current with newer ADAL and MSAL libraries.. Thanks for pointing out that the article needed revision.


Remove time information from all date fields

RATO requests to remove all hour information from all date fields. This is to become in line with their internal workers agreement.

ON HOLD, RATO will discuss internally for now and let us know

Never heard back


Consider setting custom labels on managed resources

Custom labels are translated to annotations on the managed resource (e.g. deployments, services). I wonder why not also set labels on the managed resource?
Some platforms make a difference between annotations and labels on resources. I think it would make sense to set both on kubedock managed resources.

BTW many thanks for the awesome work and kubedock!

The reasoning of using annotations is the difference of how docker defines labels, and how kubernetes defines labels. The value that is set in the docker-label might not be compatible with the k8s label requirements. This would mean the value can't be adopted 1:1 in the label, and requires some sanitisation.
Is there a specific use case you have in mind? E.g. would you want to have all labels bluntly copied over, or do you want to be able to add a label to a container and get that specific label propagated?

Thank you for the clarification. My usecase would be to set labels such as app.kubernetes.io/name or app.openshift.io/part-of (see https://github.com/redhat-developer/app-labels/blob/master/labels-annotation-for-openshift.adoc). Platforms such as OpenShift use this label information to set icons, connections and groups in the UI (e.g. https://docs.openshift.com/container-platform/4.11/applications/odc-viewing-application-composition-using-topology-view.html#odc-grouping-multiple-components_viewing-application-composition-using-topology-view)
So being able to add labels that translate to labels on the managed resource would be sufficient for that use case. Either copy all labels or use some filtering to propagate specific labels would work.

Are you able to populate them via the docker labels, or do you need another interface?
If docker-labels is an accepted interface, I would like to be able to control which labels will be propagated and which not. Not sure how that filter would look like though...

yes, I think the docker labels api interface would be totally sufficient.

awesome! many thanks!
please let me know when this change is available (maybe in v0.9.1?) so I can consume this enhancement
I think we can close this issue as fixed

Great :-) I released https://github.com/joyrex2001/kubedock/releases/tag/0.9.1 with this enhancement and another small bugfix.

works like a charm. many thanks!


--esnext reports "Operator , should stick to preceding expression" for comma after RegExp literal

Test case
title.replace(/[^a-z0-9]+/gi, '-').replace(/^-*|-*$/g, '').toLowerCase() + '.md';

C:\tests\jscs-esnext>jscs --esnext regex-comma.js
Operator , should stick to preceding expression at regex-comma.js :
     1 |title.replace(/[^a-z0-9]+/gi, '-').replace(/^-*|-*$/g, '').toLowerCase() + '.md';
------------------------------------^
     2 |

Operator , should stick to preceding expression at regex-comma.js :
     1 |title.replace(/[^a-z0-9]+/gi, '-').replace(/^-*|-*$/g, '').toLowerCase() + '.md';
-------------------------------------------------------------^
     2 |

Now that the esprisma issues is fixed, when should we see this working in jscs?

@jimmyhmiller when a new version is released. Which should be in the next few days.

I am currently getting this issue on version 0.2.1 of jscs

Current one is 1.13.1

Oooh sorry I forgot I have jscs symlinked to jsxcs. Oops!

@mikedfunk If you want jsx support you can use esprima-fb as the esprima parser or babel-jscs


startup error on magic 7.1

I just did a fresh install on magic 7.1 and I'm getting this error on server startup:
https://pastebin.com/1sk4WbyY

Oops, sorry! It looks like this would happen if you have SkillAPI but have its attribute system disabled. Does that sound right?
If so it's fixed in 7.1.1
http://jenkins.elmakers.com/job/MagicPlugin/2282/com.elmakers.mine.bukkit.plugins$Magic/

yes, I was going to enable it, just hadn't done it yet.

Great, thank you for confirming- that should be fixed, then.


change assert to warning

Type of Change
change assert is_int8_model to warning
Description
sometimes the loaded model may be a pure bf16 model, we should allow this situation.
Expected Behavior & Potential Risk
no error in model test.
How has this PR been tested?
N/A
Dependency Change?
N/A

extension test


PyPI package

Could you release this package to pypi for easier installation? The name wapi is not taken yet.

Hey filmor
Yes, we will look into doing that.

The package is now published on pypi, as wapi-python.


Feature: Cover entity

Basic support for cover entities

Covers reporting position or tilt position is not supported, yet. It can probably handled in a separate PR as it (might) require quite a bit of rework.
Tests are added as well as a readme entry.
NOTE: not tested  with actual hardware, as I do not own any.
License Acceptance

[x] This repository is Apache version 2.0 licensed and by making this PR, I am contributing my changes to the repository under the terms of the Apache 2 license.

Type of changes

[ ] Add/update a helper script
[ ] Add/update link to an external resource like a blog post or video
[ ] Bug fix
[x] New feature
[x] Test updates
[ ] Text cleanups/updates

Checklist

[x] I have read the CONTRIBUTING document.
[x] All new and existing tests pass.
[x] Any scripts added use #!/usr/bin/env interpreter instead of potentially platform-specific direct paths (#!/bin/sh is an allowed exception)
[x] Scripts added/updated in this PR are all marked executable.
[x] Scripts added/updated in this PR do not have a language file extension unless they are meant to be sourced and not run standalone. No one should have to know if a script was written in bash, python, ruby or whatever. Not including file extensions makes it easier to rewrite the script in another language later without having to change every reference to the previous version.
[x] I have confirmed that any links added or updated in my PR are valid.

Closes #127


Getting a 500 error after entering OTP code and error is unable to parse the JSON

Trying get it to work with onelogin and I get this error after auth.

onelogin-aws-login
<Response [200]>
Onelogin Username: 'XXX'
Onelogin Password:
<Response [200]>
OTP Token: XXXX
<Response [500]>

Traceback (most recent call last):   File "/usr/local/bin/onelogin-aws-login", line 26, in <module>     api.save_credentials()   File "/usr/local/lib/python2.7/site-packages/onelogin_aws_cli/__init__.py", line 140, in save_credentials     self.assume_role()   File "/usr/local/lib/python2.7/site-packages/onelogin_aws_cli/__init__.py", line 115, in assume_role     self.get_saml_assertion()   File "/usr/local/lib/python2.7/site-packages/onelogin_aws_cli/__init__.py", line 110, in get_saml_assertion     headers, params)   File "/usr/local/lib/python2.7/site-packages/onelogin_aws_cli/__init__.py", line 57, in request     raise Exception("Error: {}".format(res.json()))   File "/usr/local/lib/python2.7/site-packages/requests/models.py", line 866, in json     return complexjson.loads(self.text, **kwargs)   File "/usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 339, in loads     return _default_decoder.decode(s)   File "/usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 364, in decode     obj, end = self.raw_decode(s, idx=_w(s, 0).end())   File "/usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 382, in raw_decode     raise ValueError("No JSON object could be decoded") ValueError: No JSON object could be decoded
MacOS 10.12
Onelogin API key is for auth only
AWS login works from onelogin into AWS console.
pip install onelogin_aws_cli Requirement already satisfied: onelogin_aws_cli in /usr/local/lib/python2.7/site-packages Requirement already satisfied: boto3 in /usr/local/lib/python2.7/site-packages (from onelogin_aws_cli) Requirement already satisfied: requests in /usr/local/lib/python2.7/site-packages (from onelogin_aws_cli) Requirement already satisfied: botocore<1.6.0,>=1.5.0 in /usr/local/lib/python2.7/site-packages (from boto3->onelogin_aws_cli) Requirement already satisfied: jmespath<1.0.0,>=0.7.1 in /usr/local/lib/python2.7/site-packages (from boto3->onelogin_aws_cli) Requirement already satisfied: s3transfer<0.2.0,>=0.1.10 in /usr/local/lib/python2.7/site-packages (from boto3->onelogin_aws_cli) Requirement already satisfied: docutils>=0.10 in /usr/local/lib/python2.7/site-packages (from botocore<1.6.0,>=1.5.0->boto3->onelogin_aws_cli) Requirement already satisfied: python-dateutil<3.0.0,>=2.1 in /usr/local/lib/python2.7/site-packages (from botocore<1.6.0,>=1.5.0->boto3->onelogin_aws_cli) Requirement already satisfied: futures<4.0.0,>=2.2.0; python_version == "2.6" or python_version == "2.7" in /usr/local/lib/python2.7/site-packages (from s3transfer<0.2.0,>=0.1.10->boto3->onelogin_aws_cli) Requirement already satisfied: six>=1.5 in /usr/local/lib/python2.7/site-packages (from python-dateutil<3.0.0,>=2.1->botocore<1.6.0,>=1.5.0->boto3->onelogin_aws_cli)

ok so
the username has to be entered with ' around it as its expecting a string.
password does not need the '
OTP token needs the ' as its expecting a string.
Also,
The Onelogin API credentials need to be "Manage All" type and not just Auth only.


Add enable_auto_discounts property to offer and shop info

For issue #30

Codecov Report

Merging #31 into master will decrease coverage by 0.78%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##             master      #31      +/-   ##
============================================
- Coverage     99.60%   98.82%   -0.79%
- Complexity      277      281       +4
============================================
  Files            19       19
  Lines           763      763
============================================
- Hits            760      754       -6
- Misses            3        9       +6

Impacted Files
Coverage Δ
Complexity Δ

src/Model/Offer/AbstractOffer.php
96.82% <50.00%> (-1.56%)
69.00 <2.00> (+2.00)
:arrow_down:

src/Model/ShopInfo.php
93.87% <50.00%> (-6.13%)
17.00 <2.00> (+2.00)
:arrow_down:

src/Generator.php
100.00% <0.00%> (ø)
55.00% <0.00%> (ø%)

src/Model/Offer/OfferBook.php
100.00% <0.00%> (ø)
6.00% <0.00%> (ø%)

src/Model/Offer/OfferTour.php
100.00% <0.00%> (ø)
24.00% <0.00%> (ø%)

src/Model/Offer/OfferCustom.php
100.00% <0.00%> (ø)
10.00% <0.00%> (ø%)

src/Model/Offer/OfferSimple.php
100.00% <0.00%> (ø)
8.00% <0.00%> (ø%)

src/Model/Offer/OfferAudiobook.php
100.00% <0.00%> (ø)
12.00% <0.00%> (ø%)

src/Model/Offer/OfferArtistTitle.php
100.00% <0.00%> (ø)
10.00% <0.00%> (ø%)

... and 1 more

Continue to review full report at Codecov.

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

Thank you.