not allowing consideration of ... deferring to libdir

Hi,
We are developing a GIS Application and we are using React Native to support both iOS and Android. Our company's primary GIS Provider is Esri and they provide both an iOS SDK and Android SDK for consuming their services. We have created a port to allow us to integrate their SDK with our RN project.
Our issue is that during the initial install of the Android application we are seeing the below error message which results in a white screen. The solution to this is to re-launch the application and the error goes away. I am unsure if the error is a problem with the Android SDK provided by Esri or ApkSoSource.
I have opened a ticket in SoLoader & on the ESRI Android SDK but have yet to receive a response from either. Any additional information that can be provided on why we are receiving this error would be greatly beneficial.
React Native version:

System:
    OS: macOS 10.15.1
    CPU: (4) x64 Intel(R) Core(TM) i7-4558U CPU @ 2.80GHz
    Memory: 3.95 GB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.16.3 - /usr/local/opt/node@10/bin/node
    Yarn: 1.19.1 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/opt/node@10/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.2
      System Images: android-25 | Google APIs ARM 64 v8a, android-25 | Google APIs ARM EABI v7a, android-28 | Android TV Intel x86 Atom, android-28 | China version of Wear OS Intel x86 Atom, android-28 | Wear OS Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>77832
    Xcode: 11.3/11C29 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.2 => 0.61.2
  npmGlobalPackages:
    create-react-native-module: 0.12.0
    react-native-cli: 2.0.1
    react-native: 0.61.4

Steps To Reproduce

Clone the dummy project & install deps
Run on Android emulator

Describe what you expected to happen:
I would expect the application to load without a white screen after being installed to the device.
Snack, code example, screenshot, or link to a repository:
Dummy project that replicates the issue: https://github.com/JacobSolomonUCF/RN-DummyArcGIS
Additional Refereneces:
https://community.esri.com/thread/246073-android-sdk-weird-behavior
https://github.com/facebook/SoLoader/issues/57

The error we are receiving on the first launch after install
D/ApkSoSource: not allowing consideration of lib/arm64-v8a/libc++_shared.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libfb.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libfolly_futures.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libfolly_json.so: deferring to libdir
D/ApkSoSource: not allowing consideration of lib/arm64-v8a/libglog.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libglog_init.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libimagepipeline.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libjsc.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libjscexecutor.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libjsijniprofiler.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libjsinspector.so: deferring to libdir
D/ApkSoSource: not allowing consideration of lib/arm64-v8a/libnative-filters.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libnative-imagetranscoder.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libreactnativeblob.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libreactnativejni.so: deferring to libdir
D/ApkSoSource: not allowing consideration of lib/arm64-v8a/libruntimecore.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libruntimecore_java.so: deferring to libdir
 not allowing consideration of lib/arm64-v8a/libyoga.so: deferring to libdir

This issue is connected to 64bit libraries which should be supported in rn-0.61.2
Maybe you have an issue with your configurations? As explained in the following post, a similar problem was solved with the correct settings in android/app/build.gradle
android {
    compileSdkVersion rootProject.ext.compileSdkVersion
            include "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
        }
    }
    signingConfigs {
        debug {
            storeFile file('debug.keystore')
            storePassword 'android'
            keyAlias 'androiddebugkey'
            keyPassword 'android'
        }
    }

    // etc..etc..
    buildTypes {
       // etc..
    }
}

this example was taken from the upgrade helper

Thanks for the reply @fabriziobertoglio1987
We are already doing something similar and if I analyze the APK I see all .so's there. What I find very strange is that this issue only occurs during the initial load after installing the application. All subsequent launches do not face this issue.

Issue's root cause was related to the version of the ArcGIS Android SDK


docs: improve middleware example

What does this PR do?
Specify that namespace option of middleware is optional.
Motivation
Shows that Middleware in the same namespace that IngressRoute can be used without specifying it.
More

[x] Added/updated documentation

Additional Notes
Supersede #10525, which was closed by mistake.

Thanks @mloiseleur, I would be even more verbose on the description, why not explain your use case directly?

Shows that Middleware in the same namespace that IngressRoute can be used without specifying it.


CDSiC Logo (small)

Overview

Adds CDSiC logo to the patient app
Logo can be enabled by setting env var CDSIC_LOGO=true when running the docker container

How it was tested

Ran patient app with ng serve and checked that it is displayed correctly with and without logo enabled in env.js
Ran patient app in docker with and without the logo enabled to make sure the env var works correctly

Checklist

[x] The title contains a short meaningful summary
[ ] I have added a link to this PR in the Jira issue
[ ] I have described how this was tested
[ ] I have included screen shots for changes that affect the user interface
[ ] I have updated unit tests
[ ] I have run unit tests locally
[ ] I have updated documentation (including README)


Build shared

Build with shared libraries

Really, this fixes so much stuff. We should now be building with the correct SDK version on Mac to integrate with conda. We have shared libraries now, instead of just static. :tada:


Add page for every gene set related to a DOID or GO term

On the Disease and GO tables create a modal popup for every related gene set
This will require Chris to add to the output.  Need to discuss further to figure out how to implement.

features and issues deferred for rewrite --closing here.


when launched by ns_server message do not end up console or log

this is making debugging within cbft difficult

When I run cluster_run, cbft.log is in the ns_server/logs/n_0/cbft.log file

Ah, interesting, its logs/... not data/logs/... I had assumed all the instance specific data would be stored under data.


Native Terraform functions doesn't work in included configuration

Describe the bug
Native Terraform functions are ignored in included configurations.
To reproduce
Define locals block that lists all available files in specific directory using Terraform fileset function.
terragrunt/example/terragrunt.hcl:
include "root" {
  path = find_in_parent_folders()
}

include "module" {
  path = "${get_path_to_repo_root()}/terragrunt/common/modules/ec2-instance.hcl"
}

locals {
  users_path  = "${get_path_to_repo_root()}terragrunt/common/users"
  users_files = fileset(local.users_path, "*.hcl")
  user_names  = [for user in local.users_files : read_terragrunt_config("${local.users_path}/${user}").locals.name]

  debug_path  = run_cmd("echo", "Users path: ${jsonencode(local.users_path)}")
  debug_files = run_cmd("echo", "Users files: ${jsonencode(local.users_files)}")
  debug_names = run_cmd("echo", "User names: ${jsonencode(local.user_names)}")
}

inputs = {
}

Here is the execution result:
$ terragrunt plan
Users path: "../../terragrunt/common/users"
Users files: ["user1.hcl"]
User names: ["user1"]
...

Now if I move that locals block to the include named module, the result is different.
terragrunt/common/modules/ec2-instance.hcl:
terraform {
  source = "git::git@github.com:terraform-aws-modules/terraform-aws-ec2-instance.git//."
}

locals {
  users_path  = "${get_path_to_repo_root()}terragrunt/common/users"
  users_files = fileset(local.users_path, "*.hcl")
  user_names  = [for user in local.users_files : read_terragrunt_config("${local.users_path}/${user}").locals.name]

  debug_path  = run_cmd("echo", "Users path: ${jsonencode(local.users_path)}")
  debug_files = run_cmd("echo", "Users files: ${jsonencode(local.users_files)}")
  debug_names = run_cmd("echo", "User names: ${jsonencode(local.user_names)}")
}

terragrunt/example/terragrunt.hcl:
include "root" {
  path = find_in_parent_folders()
}

include "module" {
  path = "${get_path_to_repo_root()}/terragrunt/common/modules/ec2-instance.hcl"
}

inputs = {
}

Execution result:
$ terragrunt plan
Users path: "../../terragrunt/common/users"
Users files: []
User names: []

It seems that fileset function was ignored and didn't produce any result.
Expected behavior
Terraform functions should work at any level, not just child configurations. At least from what I understand.
Versions

Terragrunt version: 0.44.5
Terraform version: 1.3.9
Environment details: macOS 13.2.1

Not a bug, just misunderstanding how the relative paths work in Terragrunt. I used get_repo_root function instead of get_path_to_repo_root and it works as expected.
Terragrunt docs:
Note: Any file* functions (file, fileexists, filebase64, etc) are relative to the directory containing the terragrunt.hcl file they’re used in.


(New module) Touch

Provide a generic 'touch' module, which acts to trigger other modules/actions.
Snakemake is a file-based system where the create of new files to act as triggers is common. This module add this facility.

Hi @jsbrittain I'm wondering why the output_namespace variable in the config.yaml file is out yet the file that is created is inside a directory called utility_touch? In the Snakefile it seems as if the directory name should be taken from this variable?

Hi @jsbrittain I'm wondering why the output_namespace variable in the config.yaml file is out yet the file that is created is inside a directory called utility_touch? In the Snakefile it seems as if the directory name should be taken from this variable?

@rowannicholls Yes, that's correct. But the output_namespace variable is overwritten when we build the module into a workflow using GRAPEVNE (check out the config/config.yaml file that is generated when you do this). This is the primary mechanism that we use to chain modules together. At the moment the output namespace will be overwritten with the name of the module (largely for ease of navigation during development). The default value (out) is there for testing purposes (i.e. when running snakemake directly on the module, without routing through GRAPEVNE).

I see, thanks


"bazel coverage" causes a link error on Linux.

The linker emits a bunch of warnings of form
bazel-out/k8-opt/bin/bio/encoding/_objs/encoding/bio/encoding/fastx_iter.o:fastx_iter.cc:function _llvm_gcov_init: error: undefined reference to 'llvm_gcov
init'
It looks like @bazel_tools/embedded_tools/tools/cpp/ unix_cc_configure.bzl, _coverage_feature hardcodes the flags for gcc. This function switches on whether or not the platform is darwin, but it's really clang vs gcc.

Yes, this toolchain is missing some flags for instrumentation. I left them out in the toolchain, because coverage generation for llvm right now does not quite work completely, even with the flags.
https://github.com/bazelbuild/bazel/issues/1118#issuecomment-387133237
I will add those flags in for both linux and darwin to remove the warnings.


Upgrade Kensington Trackball Works to 1.2.1

Thank you for the contribution. It was merged directly as https://github.com/caskroom/homebrew-cask/commit/f727450ae1cae318aea9cbf21be1d648ec8c5de6 to keep commit history cleaner. Your contribution is still included (and still credited to you).


Update tr_tr.json and CREDITS.txt

Typos in the Turkish file (tr_tr.json) have been corrected and CREDITS.txt has been updated.

Thank you! Merging now.


Consider removing -beta tag

Background
When running go get http://github.com/lightningnetwork/lnd, it tries to pull down a very old version of lnd that was accidentally published without the beta flag. I understand why one may still want to consider LND beta software, but with go conventions around the -beta tag, it makes things difficult for those without that knowledge. It's not typical in any other of my golang projects (and probably other people as well) to be specifying beta libraries. I think that should be reserved for RC's.
If it's still considered that LND is "beta", then you can keep using v0.X.X without the -beta flag and that would still be the semver way of declaring something as beta.
Chatting with @guggero on slack, he seemed to have tried to retract the old non-beta version of LND but it's not possible without there being any other non-beta version.
Steps to reproduce
Run go get http://github.com/lightningnetwork/lnd
Expected behaviour
It should get the latest version of LND.
Actual behaviour
It gets v0.0.2

Pretty please with a 🍒on top


train_step and valid_step return the prediction

The predictions are then passed to on_batch_end.
That way, they can be re-used for things like validation scores.

Implemented in #152.


fix: add SynchronousFuture in obtainKey

The obtainKey function always returned Future, and because of this, the caching of the image did not work correctly. I added the return SynchronousFuture when the image is already cached and returns instantly so that there are no problems in the event loop, because of which the image is loaded every time not from the cache
before fix: blink gift after return from page
https://github.com/user-attachments/assets/de21013a-5d59-48bd-abdb-af8394373849
after fix:
https://github.com/user-attachments/assets/78231667-bb70-4358-8e2f-5870169db7ff

Thanks


adding mccv website made in quarto

What does this PR do?
Awesome quarto website for a python package for clinical machine learning
https://ngiangre.github.io/mccv/
Requirements for your Awesome item list

[CHECK ] Only has awesome items. Awesome lists are curations of the best, not everything.
[ CHECK] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
[CHECK ] Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
[CHECK ] Has consistent formatting and proper spelling/grammar.
- The link and description are separated by a dash.
Example: - [AVA](…) - JavaScript test runner.
- The description starts with an uppercase character and ends with a period.
- Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
[CHECK ] Doesn't use hard-wrapping.
[CHECK ] Your item(s) fit into an existing sections. (if you think a new section is needed, please explain why your item does not fit into an existing one and what would be the interest of your new section.
[CHECK ] Add your new item to the bottom of the list in a section.
[CHECK ] If a duplicate item exists, discuss why the new item should replace it.
[CHECK ] Check your spelling & grammar.
[CHECK ] The item must follow this format:- [item name](https link) - Description beginning with capital, ending in period.

[ CHECK] Be sure to have read the contributing guidelines.

Thanks for the suggestion!
I had a quick look and did not find any particular things in your website.
Did you use anything in addition to the default?
There are already few "default" website, so I don't want to add more.
See for example the last five website in https://github.com/mcanouil/awesome-quarto#websites-formats, they all have custom things.

To be interested to Quarto user, it has to have something more than what the base Quarto website offers.
I can't tell what since it's HTML, thus can be anything.

Ok sounds good. You can not merge and close this PR. Thanks for considering!


add php solve for MAYDAY

add php solve for tfcctf2023-MAYDAY
I made a request yesterday but I closed. it has a spelling mistake.

Please read the contributors md and add your name to your file name.

Hello
Sorry, I didn't see it
I will close this and open a new request


[FEATURE] Utilize  Microsoft.IO.RecyclableMemoryStream in flavor of creating new MemoryStream instances when serializing

Problem
The serializers implemented are using a new MemoryStream instance every time it have to serialize or deserialize the cache entries (in async overloads), it can leave to high allocation rates (and time spent in GC).
Solution
How about implement in serializers the features from Microsoft.IO.RecyclableMemoryStream library?

Hi @viniciusvarzea , thanks for the suggestion!
I'm looking into it and doing some benchmarking and it seems in fact quite good.
Will update soon.

Hello @jodydonetti, i have a large experience using this library, if you need some help, please count on me.

Hi @viniciusvarzea  awesome, thanks!

Hi @viniciusvarzea so the implementation has been quite easy to make.
This is the System.Text.Json one, with comments removed for brevity:
public class FusionCacheSystemTextJsonSerializer
	: IFusionCacheSerializer
{
	private static readonly RecyclableMemoryStreamManager _manager = new RecyclableMemoryStreamManager();

	public FusionCacheSystemTextJsonSerializer(JsonSerializerOptions? options = null)
	{
		_options = options;
	}

	private readonly JsonSerializerOptions? _options;

	public byte[] Serialize<T>(T? obj)
	{
		return JsonSerializer.SerializeToUtf8Bytes<T?>(obj, _options);
	}

	public T? Deserialize<T>(byte[] data)
	{
		return JsonSerializer.Deserialize<T>(data, _options);
	}

	public async ValueTask<byte[]> SerializeAsync<T>(T? obj)
	{
		using var stream = _manager.GetStream();
		await JsonSerializer.SerializeAsync<T?>(stream, obj, _options);
		return stream.ToArray();
	}

	public async ValueTask<T?> DeserializeAsync<T>(byte[] data)
	{
		using var stream = _manager.GetStream(data);
		return await JsonSerializer.DeserializeAsync<T>(stream, _options);
	}
}

For the RecyclableMemoryStreamManager I've used the default options, but if you have some suggestions I'd be happy to know.
Benchmarks show some pretty good old vs new numbers:

Method
Size
Mean
Error
StdDev
P95
Ratio
RatioSD
Gen0
Gen1
Gen2
Allocated
Alloc Ratio

SerializeAsync_OLD
1
492.6 ns
6.93 ns
6.14 ns
501.4 ns
1.00
0.00
0.0782
-
-
984 B
1.00

SerializeAsync_NEW
1
642.1 ns
6.34 ns
5.93 ns
648.9 ns
1.30
0.02
0.0725
-
-
920 B
0.93

DeserializeAsync_OLD
1
769.3 ns
11.45 ns
10.71 ns
784.2 ns
1.56
0.03
0.0772
-
-
976 B
0.99

DeserializeAsync_NEW
1
999.7 ns
13.76 ns
12.87 ns
1,017.7 ns
2.03
0.04
0.0935
-
-
1192 B
1.21

SerializeAsync_OLD
100
23,484.7 ns
102.12 ns
95.52 ns
23,623.2 ns
1.00
0.00
4.7607
0.3967
-
59856 B
1.00

SerializeAsync_NEW
100
22,606.4 ns
142.26 ns
133.07 ns
22,833.3 ns
0.96
0.00
1.2512
-
-
15744 B
0.26

DeserializeAsync_OLD
100
51,011.0 ns
500.74 ns
418.14 ns
51,606.7 ns
2.17
0.02
3.2349
0.3052
-
41096 B
0.69

DeserializeAsync_NEW
100
51,964.5 ns
470.68 ns
440.27 ns
52,594.8 ns
2.21
0.02
3.2349
0.3052
-
41312 B
0.69

SerializeAsync_OLD
10000
2,811,384.3 ns
48,038.91 ns
44,935.62 ns
2,889,311.9 ns
1.00
0.00
671.8750
664.0625
664.0625
5264201 B
1.00

SerializeAsync_NEW
10000
2,510,884.4 ns
15,943.09 ns
14,913.18 ns
2,525,672.7 ns
0.89
0.02
160.1563
160.1563
160.1563
1499627 B
0.28

DeserializeAsync_OLD
10000
9,559,862.6 ns
183,341.18 ns
196,173.01 ns
9,831,249.5 ns
3.39
0.09
437.5000
421.8750
125.0000
4103255 B
0.78

DeserializeAsync_NEW
10000
9,666,130.0 ns
152,706.18 ns
142,841.45 ns
9,810,493.9 ns
3.44
0.08
437.5000
421.8750
125.0000
4104012 B
0.78

Overall it looks good, and I'm inclined to use it for the others too and merge it for the new version.
One question: are you aware of any edge case or strange scenario that I should know of, where it may have issues?
Thanks!

Hello @jodydonetti, prettty good man. Thank you for considering it. :)
One observation from the library documentation and from my experience:
"Important!: If you do not set MaximumFreeLargePoolBytes and MaximumFreeSmallPoolBytes there is the possibility for unbounded memory growth!"
In my experience, the default options work very well, except for these 2 parameters. Setting it helps to avoid some memory leaks in heavy utilization scenaries.

Thanks for the tip, any suggestion for reasonable values or a rationale to follow?

@jodydonetti Since the redis does not works well with large values, and the default 'BlockSize' of 128KB and the 'LargeBufferMultiple' of 1MB provided by the library, 16MB is a reasonable value for MaximumFreeSmallPoolBytes, 64MB is a reasonable value for MaximumFreeLargePoolBytes.
Keep in mind that the library does not pre-allocate any buffer, the buffers are allocated as need, so, these limits are used just as upper limits to avoid memmory leaks.
In a future release, we can also improve the DistributedCache performance, compressing the payloads before send it to redis.

Btw I'm reading here and there are other considerations to look out for, for example "Most applications should not call ToArray", which I am currently calling, so I have to change that.

877 / 5.000
Hi @jodydonetti. Sorry for the delay in responding, I was a little sick.
About this: "Most applications shouldn't call ToArray", it's the way to go as long as you use stream up until the point of sending the data to redis. Due to the use of the IDistributedCache interface (which only has byte[] overloads) I think we cannot use streams in all sending methods, so at some point the ToArray() method must be called, but as the tests show benchmark, there are some benefits (allocation issue) even calling ToArray( ).
About this: "but when using it without correctly configuring some options, it will probably cause a memory leak. but..."
Since redis itself doesn't handle larger values very well, we can provide the default options that fit most scenarios and expose the user to the option to tune it or disable it at all.

Hi @viniciusvarzea , I tried to look back at this.
The perf boost in my opinion is not so insane to justify the added risk of using it maybe badly configured (truth be told, any perf boost I think would not justify an added risk).
On the other hand, I'd like to give users the option of using it, because there's value in it.
Therefore I'm adding support for it, but turning it off by default (at least for now) and making it opt-in, with the ability of turning it on by passing an instance of RecyclableMemoryStreamManager in the ctor, so the options will be explicit.
In this way there will not be surprises for users and, if enabled, it would mean the user (hopefully) took an informed decision.
Thoughts?

Hello friend. I Will take a look at it.

De: Jody Donetti @.>
Enviado: sábado, 24 de agosto de 2024 17:36
Para: ZiggyCreatures/FusionCache @.>
Cc: viniciusvarzea @.>; Mention @.>
Assunto: Re: [ZiggyCreatures/FusionCache] [FEATURE] Utilize Microsoft.IO.RecyclableMemoryStream in flavor of creating new MemoryStream instances when serializing (Issue #241)
Hi @viniciusvarzeahttps://github.com/viniciusvarzea , I tried to look back at this.
The perf boost in my opinion is not so insane to justify the added risk of using it maybe badly configured (truth be told, any perf boost I think would not justify an added risk).
On the other hand, I'd like to give users the option of using it, because there's value in it.
Therefore I'm adding support for it, but turning it off by default (at least for now) and making it opt-in, with the ability of turning it on by passing an instance of RecyclableMemoryStreamManager in the ctor, so the options will be explicit.
In this way there will not be surprises for users and, if enabled, it would mean the user (hopefully) took an informed decision.
Thoughts?
—
Reply to this email directly, view it on GitHubhttps://github.com/ZiggyCreatures/FusionCache/issues/241#issuecomment-2308530084, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEJGOMUTICBIGQAX724C5YTZTDVDHAVCNFSM6AAAAABHPYUOP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGUZTAMBYGQ.
You are receiving this because you were mentioned.Message ID: @.***>

Hello @jodydonetti Sorry for the delay in response, i think give to user this option is a perfect solution, in this way the user can tune the RecyclableMemoryStreamManager instance to fits the workload.
Thank you for considering it.

Hi @viniciusvarzea the feature has been developed, tested and is ready to be released probably tomorrow.

Hi, v1.4.0 has been released 🥳


Manuscript can be written

Hi all,
we have 3 weeks from now on to write this manuscript. Let coordinate a little bit and start writing :)
Thanks all!
Bjoern

Thanks, Bjoern! great news indeed.
well, three-week is a bit stressing. any proposal on who is doing what?

No plan yet, besides that we will work on the same Google Docs as the abstract.
We should describe example workflows and describe use-cases that RNAw will solve, in the same time make clear that it is a lego bricks system that can be used in a flexible way to create complete novel workflows + allows integration with other types of data analysis beyond RNA.

Awesome!

Submitted. But we should include more useful workflows and testing is highly appreciated, we had a lot of additions since December and I upgrade the underlying Galaxy Image.


Add memory_limiter, debug, and zpages to OTel Collector

This adds some OTel Collector features when running in production, including troubleshooting tools:

memory_limiter processor: https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor/memorylimiterprocessor
debug exporter: https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/debugexporter
zpages extension: https://github.com/open-telemetry/opentelemetry-collector/tree/main/extension/zpagesextension

None of them are turned on by default – they have to be enabled via the Collector's config Job property.

Closing this, as we're reconsidering which of these are necessary.


Release 2.0.2

Questions
Answers

Description?
Release 2.0.2

Type?
improvement

Hello @PierreRambaud ,
Thanks for the PR, LGTM !
QA ✅

Thanks @PierreRambaud & @florine2623


[REVIEW]

Github Profile Link:
https://github.com/nikita-jain-01

Some suggestions from my side.

Maybe remove the view counter
specify the "looking for collaboration on projects" a little bit more what kind of projects languages etc.
may remove the links of the language and tools or link to the specific websites

Some suggestions from my side.

Maybe remove the view counter
specify the "looking for collaboration on projects" a little bit more what kind of projects languages etc.
may remove the links of the language and tools or link to the specific websites

Thanks for your suggestions. I have done some changes.

Thanks for sharing - we will review on a livestream as time allows :)

I would love to give some suggestions on your profile :

Remove the Vs code and Github icons from the Languages and tools section. As vs code doesn't define anything about you coding abilities and github icon because you are already present on the same platform.
Instead of putting the github stats and streaks one below the other you can put them side by side then will help you optimize your readme file

I would love to give some suggestions on your profile :

Remove the Vs code and Github icons from the Languages and tools section. As vs code doesn't define anything about you coding abilities and github icon because you are already present on the same platform.
Instead of putting the github stats and streaks one below the other you can put them side by side then will help you optimize your readme file

@kaiwalyakoparkar Thanks for your suggestions. I've done the changes.

Reviewed on live stream https://www.youtube.com/watch?v=XT3_O4jULRE

looks great 👍
suggest using the GitHub bio and link section (update via settings)
suggest using some of the white space to the top right and bottom left of the customised GitHub profile, maybe move the last graph to the top right next to the list of bullet points
100% commits, suggest doing pull requests, code reviews and issues


WSL failed to reopen after run wsl --shutdown

Windows Version
Microsoft Windows [Version10.0.19045.4412]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Ubuntu 20.04
Other Software
No
Repro Steps
Everything was fine at first, when my computer was booted up and running wsl's Ubuntu.
Until I shutdown Ubuntu, I run wsl --shutdown through the powershell, and powershell didn't return any value at this time.
I shut down powershell and tried to reopen Ubuntu, but I got stuck without any error messages, and I used powershell to try to view wsl-l--v without returning any values.

Expected Behavior
Reopen my wsl's Ubuntu 20.04.6
Actual Behavior
Nothing shown in terminal

Diagnostic Logs
No response

Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.
Once completed please upload the output files to this Github issue.
Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to<EMAIL_ADDRESS>with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
View similar issues
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Closed similar issues:

WSL-2 Ubuntu: [process exited with code 1] after exit (#7484),  similarity score: 0.77
Wsl service hung out after poweroff or crash (#10802),  similarity score: 0.75
Force shutdown and restart the PC, and then launch wsl, show Error code: Wsl/Service/CreateInstance/MountVhd/0×80070570 (#10684),  similarity score: 0.75
When I use command 'wsl' in powershell, there is no respond. (#9827),  similarity score: 0.75
WSL dies after closing and won't re-open until windows reboots (#10630),  similarity score: 0.74

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

/question

The error message was shown now.

Oops, I solved this issue by restart LxssManager in services.msc. If anyone got the same issue, welcome to contact me by<EMAIL_ADDRESS>:)


Allow expanding collection properties

Properties that return collections should expand to a full datagrid of those items, if they have multiple properties; or a single column if a collection of scalar values.

Each such collection should return its elements as a string[][], or perhaps a 2D array.
For WPF datagrid binding, a jagged array is probably better.

We still need to handle an infinite sequence. Perhaps a fixed limit of 100 items?

I'm not sure how to do this:

How do we handle instances of multiple types? An ArrayList or List<object> could contain multiple types. Even in a List<T>, there could be derived types.
The value at the property could be a never-ending sequence.

I think I will leave this for now.

Perhaps something like this:

Create a dictionary / property bag for each element in the collection.
Use StringValue to render the property values for each instance.
Construct a custom type descriptor from the superset of all properties


VSR: Allow backup to reply to partitioned client

If the client is partitioned from the primary (but able to communicate with the backup), the client should still be able to receive replies.
The client can currently send a request to the backup, which is forwarded to the primary, but it has no way to receive the reply, since only the primary replies.
One solution would be for the backup to reply directly to the client if the corresponding reply is already in its client table. (Clients retry requests, so this should happen eventually. The client's latency will be slightly degraded.)

Amendment: We forward all requests except register requests, so a client must still be able to talk to the primary to register.
https://github.com/tigerbeetledb/tigerbeetle/blob/c6473d0dc7b7dc2bc34e33f529a800ba3318e819/src/vsr.zig#L614-L619


fix(ui): implement invoice status update in request modal

Description:
Update invoice status to "paid" once payment is received
Motivation and Context:
Fix UI bug. Currently invoice status update is not implemented
How Has This Been Tested?
Manually
Screenshots (if appropriate):
Before:
Before the patch. Status is not updating though the invoice was paid already

After:
With this patch status updates automatically once invoice is paid

Coverage increased (+0.009%) to 19.058% when pulling b31030500815ab5db7e0b3c54041a75fb688ca61 on korhaliv:master into 4db1bb0092c345c7663d0efdd235efb3f20ec780 on LN-Zap:master.

Coverage increased (+0.009%) to 19.058% when pulling b31030500815ab5db7e0b3c54041a75fb688ca61 on korhaliv:master into 4db1bb0092c345c7663d0efdd235efb3f20ec780 on LN-Zap:master.

Coverage increased (+0.009%) to 19.058% when pulling b31030500815ab5db7e0b3c54041a75fb688ca61 on korhaliv:master into 4db1bb0092c345c7663d0efdd235efb3f20ec780 on LN-Zap:master.

Coverage increased (+0.009%) to 19.058% when pulling b31030500815ab5db7e0b3c54041a75fb688ca61 on korhaliv:master into 4db1bb0092c345c7663d0efdd235efb3f20ec780 on LN-Zap:master.


Add bit::flip

This is the same thing as std::transform with a function [](auto b) { return ~b; }

[ ] flip general implementation
[ ] flip general tests
[ ] flip general benchmark

bad issue, the op provided to transform can do this.


[Feature] PUT, PATCH and DELETE HTTP request support

[+] Added PUT request support
[+] Added PATCH request support
[+] Added DELETE request support

LGTM


STM32H7 CAN driver UAVCAN GlobalTimeSyncMaster pub conflict

Describe the bug
When using a STM32H7 based autopilot like the HEX CubeOrange with UAV-CAN it publish ERROR UAVCAN GlobalTimeSyncMaster pub conflict messages.
To Reproduce
Steps to reproduce the behavior:

Load PX4 master on a CubeOrange
Enable UAV-CAN param set UAVCAN_ENABLE 2
Connect SLCAN Interface to CubeOrange
Start UAVCAN GUI Tool
Get Error Message in UAVCAN GUI Tool

Log Files and Screenshots

@JacobCrabill

Hmm, I can give this a look next week perhaps.

Just took a brief look at it; this comment in GlobalTimeSyncMaster may hold the key to the issue:
/**
 * Please read the specs to learn how the time synchronization works.
 *
 * No more than one object of this class is allowed per node; otherwise a disaster is bound to happen.
 *
 * NOTE: In order for this class to work, the platform driver must implement
 *       CAN bus TX loopback with both UTC and monotonic timestamping.
 *
 * Ref. M. Gergeleit, H. Streich - "Implementing a Distributed High-Resolution Real-Time Clock using the CAN-Bus"
 *
 * TODO: Enforce max one master per node
 */

Specifically: NOTE: In order for this class to work, the platform driver must implement CAN bus TX loopback with both UTC and monotonic timestamping.
I don't know when I'll have free time to look into this, but this could give another developer a clue on where to start digging into the driver.


adds envelope guid

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 11 (18.18%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 77.931%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

vs_listener/models.py
2
11
18.18%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
113

Relevant Lines:
145

💛  - Coveralls


CoreMLModels:No such file or directory

After cloning the project to the local environment, the compilation shows a lack of CoreMLModels and Assets files, preventing local execution.

me 2

It might be a issue with the repo structure.
Try delete the folder of CoreMLModels, create a new one in your Finder, then put models + .txt/.json files into that folder. And drag that folder into your Xcode structure, remember to choose "Create folder reference", then it should be fine.

改完之后 fatalError("Fatal error: failed to find the CoreML models.")  PhotoSearcherModel 第19行 报错

You need to modify the path of CoreMLModels based on your own situation, as shown in the following figure.

to

1.CoreMLModels: Open the project and select the red file in the structure, delete it and select 'Remove Reference' in the alert, then drag and drop the CoreMLModels folder from the cloned project to Xcode project, after that you will see a blue folder below Queryable.

Assets: select Queryable in the structure, right click and select 'New File...', select and double click 'Asset Catalog', name it Assets and click 'Create'. Then select it and create two 'New Image Assets' named AccentColor and AppIcon.

After you done the two steps above, the final result will look like the following figure:

Good luck!

Assets.xcassets needs to be supplemented by the author.

added in this commit: https://github.com/mazzzystar/Queryable/commit/738fcac880d44d1961186d77de9b8709f2863d51

https://github.com/mazzzystar/Queryable/pull/8
fixed by above pr.


AttributeError: 'CrawlResult' object has no attribute 'fit_markdown'

import asyncio
from crawl4ai import AsyncWebCrawler
import json
async def main():
async with AsyncWebCrawler(verbos=True) as crawler:
result = await crawler.arun(
url="https://batteriesnews.com/lg-chem-files-lawsuit-against-unit-of-chinas-ronbay-over-battery-tech",
bypass_cache=True,
word_count_threshold=10,
)
print(result.fit_markdown)  # Print clean markdown content
AttributeError: 'CrawlResult' object has no attribute 'fit_markdown'
result.markdown no problem

@wg20170107 Make sure to update your library (current version 0.3.72). If not, reinstall it with pip using 'pip install -U cralw4ai', as it already includes the added feature, which should be the only reason.


hotfix(cd): skip comment on commit step

The token seems to be changed/expired and no longer working. Allow the step to fail to unblock the workflow.

can this be reverted? and is this needed in EE? @fffonion @windmgc

@jschmid1 The EE token is still valid, the CE token is not fixed yet. No action needed at this time.


[Release 3.1] Merging code to Main branch for release

Docs Update.
Create data: Country list dropdown in manufacturing_country column.
Descriptions for each page under title.
Error logs of uploaded data in upload history.
Error handling for all api calls.
Unified BPN validation in access policy section.
Decline contract option for provider contracts.
App version and collapse button added in sidebar.
Frontend document updates.
Purpose restriction added in usage policies.

@ajithsimons please fix the bugs.


junit-addons/junit-addons 1.4

Type: Missing
Summary:
junit-addons/junit-addons 1.4
Details:
Maven pom has no license info
Jar includes license which is OTHER (The JUnit-addons Software License, Version 1.0
(based on the Apache Software License, Version 1.1)
Resolution:
OTHER
Affected definitions:

junit-addons 1.4

Updated to Apache-1.1. Diff tool shows 72.2% match, but when you look at what was changed, it is the text that is marked as editable per SPDX matching guidelines.
https://spdx.org/licenses/Apache-1.1.html


Upgrade the Kubernetes client minor version.

Description
This is to fix #5274 by upgrading the Kubernetes client.
Related issue and scope

[x] I opened an issue to propose and discuss this change (#5274)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Scheduler
[x] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[x] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[x] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report

Merging #5275 (d79386e) into master (639c4a9) will decrease coverage by 65.76%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #5275       +/-   ##
==========================================
- Coverage   70.36%   4.59%   -65.77%
==========================================
  Files         238     238
  Lines       14084   14084
  Branches      588     588
==========================================
- Hits         9910     647     -9263
- Misses       4174   13437     +9263

Impacted Files
Coverage Δ

...re/containerpool/kubernetes/KubernetesClient.scala
0.00% <ø> (-37.44%)
:arrow_down:

...ain/scala/org/apache/openwhisk/spi/SpiLoader.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...n/scala/org/apache/openwhisk/utils/JsHelpers.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...scala/org/apache/openwhisk/common/Prometheus.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...scala/org/apache/openwhisk/core/FeatureFlags.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ala/org/apache/openwhisk/common/ConfigMXBean.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...la/org/apache/openwhisk/http/BasicRasService.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/org/apache/openwhisk/common/ConfigMapValue.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/org/apache/openwhisk/core/entity/WhiskAuth.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

.../org/apache/openwhisk/core/entity/EntityPath.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 192 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 639c4a9...d79386e. Read the comment docs.


Add Levant job-logs command to tail logs

Description
Nomad 0.8.0 will bring in a proxy style feature so that client based HTTP API requests can be proxied through the Nomad server API. This is required as Nomad clients should be running in private subnets and programatic access from applications such as Jenkins controlled and only allowed access through the server API.
This feature therefore is to create a new command using this feature which allows the streaming of job logs until the completion of the job. This is very helpful for batch and parameterised job where operators likely wish to trigger an instance of the job and then track the logs until completion.

Was going to jump on this, just wondering if it should be a separate command or rolled into the monitor command thats in progress?

I'd like to see this as a separate command - though it might build on top of what is already in the monitor command.
One thing I'd also like to see is the ability to tail logs for multiple jobs. This might be useful in the case where multiple jobs make up a given application, and a user wants to tail all logs for an app as a single unit.


Realistic time management

Hey! This is another idea I have. Essentially it'd be a togglable option that allows an engine to realistically control the time it has. This could be influenced by a number of factors, including but not limited to:

Time control (for both you, and opposite player),
Evaluation (e.g. blunder by the opposite player would cause the bot to act quicker, or when you're losing it'd act slower),
Phase of the game (e.g. beginning, midgame and endgame)
Opening moves (of course, this would make the bot play out faster)
Trades (the bot could make piece trades faster)

Of course, there can be a lot more factors, but it'd be interesting to see how this would behave since it'll allow for a lot more realistic timed games which current bots lack.

Time-management is handled by stockfish internally. It is quite simple to implement.
All you have to do is to pass Whites remaining time, Blacks remaining time, Whites move-increment per move and Blacks move-increment per move as parameters to the get-move function and then stockfish will automatically handle time-management.
If you want the bot to play faster or slower, then you can decrease or increase the slow-mover setting, which tells stockfish how fast it should play.

i tried increasing beyond 1000ms no difference , still plays at same speed


Typo in path to assets copy target in copyAssetsToPublic hook

Hi Nick, team, & friends,
Tiny fix — looks like when the folder structure was updated in the bump up to v1, the public destination of the assets folder in the copyAssetsToPublic hook didn't update.
Nice talk today Nick! 👍

ah thats my fault. i'm still on an old version of elderjs.

@andrew-j-roberts thanks for bringing this up and fixing it. I tested @sw-yx PR manually but didnt clear my public folder so missed it. Thanks. 👍


fix-preprocessing

Hey @ielis @pnrobinson,
I would like to iterate the phenopacket schema and check the data types each field requests to give specific error messages to the user. E.G.:
phenopackets.VitalStatus (v2.0.0) expects an enum value out of  'ALIVE', 'DECEASED', and 'UNKNOWN_STATUS' for the phenopackets.VitalStatus.status field. Instead found ['passed away', 'alive', 'etc'] in DataField <field_id> corresponding to column <column_id>.

Please provide a mapping from the local value set to the Phenopackets value set.

Similar error messages might be possible for other issues with the values provided.
Can we access specific versions of the schema upon user request?
Can we get an 'inside' look at the definiton of the schema? Maybe by parsing the protobuf definition?
I would greatly appreciate your help here.

FOr now it makes sense to support ONLY v.2.0. But the software should be able to handle the next version when that comes. Not sure what you mean by access specific versions? Note that the v2.01 and 2.0.2 do not change the schema


Depends on "Debugging Tools for Windows"?

Exception: dbghelp.dll not found in "C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\dbghelp.dll"
You must install the "Debugging Tools for Windows" feature from the Windows 10 SDK.
ERROR at //build/toolchain/win/BUILD.gn:49:3: Script returned non-zero exit code.
  exec_script("../../vs_toolchain.py",

Obviously it is.


Performance metrics

In order to know where we have bottlenecks, and to know if we have regressions over time, it would be nice to provide performance metrics, covering at least:

Provide equivalent flag to opa eval --metrics: timer_rego_query_eval_ns and timer_rego_query_parse_ns
Java / clojure function call "heat graph"
Wall clock time
Memory / CPU usage

In order to catch performance regressions, we should add a task to the build which captures performance metrics and report the outcome.

https://github.com/hugoduncan/criterium


"file could not be opened successfully" on a v2.LR.historical_0101 tar ball

I'm trying to extract the v2.LR.historical_0101 run from NERSC HPSS archive and ran into "file could not be opened successfully" error on zstash/00005.tar when beginning extract archive/atm/hist/v2.LR.historical_0101.eam.h0.1978-05.nc.
To reproduce:
source /global/common/software/e3sm/anaconda_envs/load_latest_e3sm_unified_cori-haswell.sh
zstash extract  --hpss=/home/f/forsyth/E3SMv2/v2.LR.historical_0101 "archive/atm/hist/*h0.197[8-9]*"

Not sure how to trouble shooting, maybe it's a problem in the archive?
The Traceback is as follows:
INFO: Opening tar archive zstash/000005.tar
Traceback (most recent call last):
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.7.0_nompi/bin/zstash", line 10, in <module>
    sys.exit(main())
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.7.0_nompi/lib/python3.9/site-packages/zstash/main.py", line 64, in main
    extract()
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.7.0_nompi/lib/python3.9/site-packages/zstash/extract.py", line 45, in extract
    failures: List[FilesRow] = extract_database(args, cache, keep_files)
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.7.0_nompi/lib/python3.9/site-packages/zstash/extract.py", line 275, in extract_database
    failures = extractFiles(matches, keep_files, keep, cache)
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.7.0_nompi/lib/python3.9/site-packages/zstash/extract.py", line 444, in extractFiles
    tar: tarfile.TarFile = tarfile.open(tfname, "r")
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.7.0_nompi/lib/python3.9/tarfile.py", line 1625, in open
    raise ReadError("file could not be opened successfully")

After consulting @golaz, a failed extraction leave an incomplete tar file (i.e. 00005.tar in this case) on the local disk under zstash/. and zstash will not retrieve it from tape the second time because it thinks the file is already there. To remove the tar file on disk (under zstash/ sub-directory) and try again resolved the problem.
An earlier feature request on supporting retry would be helpful to handle extraction failure due to some HPSS system problems.

Resolved by #218.


Pull to refresh on profile

Fixes https://github.com/subconsciousnetwork/subconscious/issues/598
Reworked the structure to add empty states and make everything support .refreshable{}
https://github.com/subconsciousnetwork/subconscious/assets/5009316/b9f1ff2f-039e-4eb9-bfb9-cb592246aa13

For future: .refreshable now takes an async function. The function will keep the spinner going until the async call completes.
We could consider a special exception to the way we typically handle effects:
.refreshable {
    // Any setup state
    store.send(.refreshing)
    let value = await store.environment.refreshThing()
    // Pass back into model update logic
    store.send(.refreshed(value))
}

@gordonbrander if we had an API to wait for an action on the store we could keep it all in the model?
.refreshable {
    store.send(.refresh)
    await store.listen(action: .refreshed)
}


feat: add -f/--values option to fsm mesh upgrade command

Description:

Testing done:

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[ ]

Upgrade
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?

Is this a breaking change?

Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)?

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

Comparison is base (c339007) 48.33% compared to head (a65d80f) 48.34%.
Report is 1 commits behind head on release/v1.2.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##           release/v1.2     #104   +/-   ##
=============================================
  Coverage         48.33%   48.34%
=============================================
  Files               194      194
  Lines             14621    14656   +35
=============================================
+ Hits               7067     7085   +18
- Misses             7510     7527   +17
  Partials             44       44

Flag
Coverage Δ

unittests
48.34% <65.71%> (+<0.01%)
:arrow_up:

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

Files
Coverage Δ

cmd/cli/mesh_upgrade.go
64.77% <65.71%> (+0.62%)
:arrow_up:

... and 2 files with indirect coverage changes

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


license to use? (not an issue)

I am interested in hosting the solitaire on unopico, there is no usage license however and I dont want to step on anyone's toes :) Mind adding a license to use?

Wahyu,
Thank you for asking about the license. I'm thrilled that you wanted to host my first JS project!!  A license just got added, so feel free to use the code. Be aware that the game is not perfect. See the Further To Do in the readme.
Regards,
Xiaoyu


Ability to ignore / take ownership of project when opening.

Is your feature request related to a problem? Please describe.
This problem comes up often : #172 ,  #2229 , #4364 .
There is definitely use cases for sharing projects without a full-blown ghidra server, accross machines with different user names. Export + Import as an archive is not always an option, and just about as tedious as manually editing the .prp file
Describe the solution you'd like
A global option to ignore ownership, or an extra button in the dialog that informs me of the username mismatch, allowing me to take ownership of the project. It should also mention obvious caveats (don't open project simultaneously on multiple machines (( I think the lock files already prevent this ?)), other user may be unable to open project etc etc.)
Describe alternatives you've considered
Editing the .prp file by hand is tedious. I often jump from one machine to another.
Additional context
UI design could be  trivial : simple dlg box, 2 buttons, "Force open / take ownership", "Cancel".

Due to the high-probability that bad File permissions exist, this is not an "Easy button" type of situation.  The owner concept was created for this very reason.  While we could probably examine all project files and folders to check for such permission issues, we would have no recourse other than to fail if such a situation exists.  It would seem having an Admin alter file ownership/permissions at the file-system level is much more involved then the edit of the property file once permissions have been corrected.   For these reasons we are unlikely to incorporate such a mechanism.

In addition to the above, any project file checkouts from a Ghidra Server could pose a problem when taking possesion of another user's project.

Are you accessing a shared Ghidra Server project where others have checked-in revisions and you have not?  Could you look at your  Program information properties and tell me what you have for "Created with Ghidra Version".  You can find this from the Help->About <your-program-name>.
What version of Ghidra are you currently using?
There are no provisions in the DomainFile.getChangesByOthersSinceCheckout method to cope with a VersionException, however you should not have run into this under normal conditions.
The Module DB Adapter schema version has not been changed since Ghidra was released so I can only assumed there may be some other issue.  Are you able to share your Ghidra project file with us?  If so, I would need to it to be produced from the project file on your server and not the one you may have checked-out.  If your answer is yes, I will provide further instructions on how best to do this.

@ghidra1 did you post this in the correct ticket ? I'm not sure I follow; I'm not using Ghidra Server at all and this was a feature request, not really a bug report


MongoDB Task. Punko Pavel

https://travis-ci.org/github/PashaPunko/db-assignments/builds/719366670

Try to decrease the time of performing these tests up to 100 ms. Adding some indexes to specific collections  should help

I'll mark the PR as "Draft", please click "ready for review" when it will be finished. Thank you!

https://travis-ci.org/github/PashaPunko/db-assignments/builds/725843707

Closing the PR as accepted! Thanks!


CHANGE_ENDIAN_* usage in EncryptParam / DecryptParam / GetCommandCode / execute modules

These usages are look like they're all over the map.

Fixed in 16369f8c


chore(net): add back get-network-address module to fix<EMAIL_ADDRESS>

<EMAIL_ADDRESS>is now broken because it depends on<EMAIL_ADDRESS>which now resolves to<EMAIL_ADDRESS>but that path doesn't exist in<EMAIL_ADDRESS>(because of this change https://github.com/denoland/std/pull/5949 ). This PR fixes it.

It would be nice to have a lint in deno std to detect stable code depending on unstable code and ban that.

Sounds a good idea 👍


fix inconsistent modifiers declaration order

Title
fix inconsistent modifiers declaration order for RSACryptServiceProvider sample
Summary
use “public static” instead of "static public"

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Open Weather Map API key not accepted

What happened?
I'm trying to setup the irrigation integration (completely new install, never used it before), but my OWM API key gets rejected by it, while the OWM Integration accepts my key.
Only log message is:
[custom_components.smart_irrigation.weathermodules.OWMClient] Cannot talk to OWM API, check API key.
How to reproduce
Fresh install of HASmartIrrigation integration, trying to setup with Open Weather Map
Relevant log output
No response
Which version are you running?
v2024.8.0
Diagnostics file

[X] I have attached a diagnostics file

Additional information
No response

see https://jeroenterheerdt.github.io/HAsmartirrigation/installation-weatherservice.html#getting-open-weather-map-api-key - it can take hours before your API key is activated. If you already had an API key, test it using postman or something similar that it actually works.

Solution was to subscribe for the One Call API that is free for 1000 calls/day, and limited it to a 1000 as well to aviod charges. Thanks for the quick response!


changed to better hash function

This should significantly reduce the clashes

I've used the hash function suggested in the review, but I've increased the multiplier from 31 to 1023. This is because the x and z values are usually small (750 is 12000 blocks out), and dimension values are within the range of -1 to 300

I've used the hash function suggested in the review, but I've increased the multiplier from 31 to 1023. This is because the x and z values are usually small (750 is 12000 blocks out), and dimension values are within the range of -1 to 300


Gamification by adding a score system named kudos

Related Issue
Closes #42
Type of Change
Put x inside the square bracket to specify what type of change your PR is:

[x] New Feature

Description of Change
Now, on completing a task, one gets kudos added to their kudos score. If the task had no deadline then you get 1 point, if it had a deadline, completing the task x days before deadline adds x points to your score and delaying by y days deducts y points. Your score and the kudos history is saved in Shared preferences.
Demo

@pranavkonidena I discussed its approach with @Akshit517 . Please review this.

Added that Constants.dart . Pardon I am unable to understand what you mean by adding a EOF?

Added that Constants.dart . Pardon I am unable to understand what you mean by adding a EOF?

@Sanat-Jha EOF means adding an empty line at the end of file

Added that Constants.dart . Pardon I am unable to understand what you mean by adding a EOF?

@Sanat-Jha EOF means adding an empty line at the end of file

oh okay, will do it right now.

@pranavkonidena Done, added EOF.


subsys: pm: Fix cpus active count

Only set a cpu as active (on pm subsystem) when the cpu is effectively initialized. We cannot assume on pm subsystem that all cpus were initialized since when the option CONFIG_SMP_BOOT_DELAY is used cpus are initialized on demand by the application.
Note that once cpus are properly initialized the subystem is able to track their status.

While I think I agree with either @andyross or @gmarull in that the bidirectional dependency here needs solving, this is a bug fix, solving a problem.
Refactoring to fix the dependencies here can be done in the 3.5 timeline.

I think the solution should be the other way around: PM can subscribe to Kernel, so that when a CPU is initialized, PM subsys is notified and can do the appropriate actions. This way we keep subsystems isolated.

What exactly you propose ? Right now we have no thread on pm subsys that we could use to subscribe for kernel events (that also would requires an additional event)  or other mechanisms like messages queue, pipes or whatever.  Also, is not something can be done in an initial service through SYS_INIT (kernel keeping count of cpus) since CPUs can be brought up asynchronous.
Adding a new API where the kernel keeps callbacks to be called when CPUs are activated is possible but will introduce overhead for this specific thing (also this will not be necessary if we move pm into kernel). I think the right direction will be moving the pm subsystem into the kernel, but I think is way to risky doing it now.
Not that kernel calling pm subsystem already exists, it is not something new.
Just to be clear, I agree with @gmarull and @andyross I just don't see a better solution for this bug fix now.

Something like:
typedef void (*k_cpu_enabled_cb)(uint8_t cpu);

struct k_cpu_enabled_subs {
    sys_snode_t node;
    k_cpu_enabled_cb *cb;
};

void k_cpu_enabled_subscribe(struct k_cpu_enabled_subs *subs, k_cpu_enabled_cb *cb);

ie, Kernel will keep a list of subscribers to be called when a CPU is enabled. PM subsys can subscribe before Kernel starts. Does it sound reasonable?

Something like:
typedef void (*k_cpu_enabled_cb)(uint8_t cpu);

struct k_cpu_enabled_subs {
    sys_snode_t node;
    k_cpu_enabled_cb *cb;
};

void k_cpu_enabled_subscribe(struct k_cpu_enabled_subs *subs, k_cpu_enabled_cb *cb);

ie, Kernel will keep a list of subscribers to be called when a CPU is enabled. PM subsys can subscribe before Kernel starts. Does it sound reasonable?

that is what I mentioned about overhead and a new API, specially because it won't be necessary if we move the subsystem to the kernel. That's said, we need to fix it, if that is what gates this I can change the patch. @andyross do you prefer this path ?

In the abstract, sure.  But between runtime power management and the kernel?  Meh.  It's basically the kernel already, at least at this level.  That was what I was getting at upthread: maybe we should separate the device model side of PM from the kernel stuff; the former is reasonably a "subsystem", the latter not so much.

Honestly given that the only user is a single global subsystem which is inherently tied to the kernel anyway, I think I'd prefer the code as originally written. I was only complaining about the directory location and the API layering hygiene. But I wouldn't NAK either trick.
Dynamic runtime pubsub/listener/handler registration is sort of Not The Zephyr Way, we've always preferred build time complexity to runtime behavior.

If runtime complexity is the problem, we can use iterable sections so everything is sorted at compile time. To me, creating such inter dependencies is just a bad design, and we should do better if we can.

It is not creating any new dependency @gmarull. The kernel already does calls to subsys/pm. There is no discussion about this inter dependency, I will work to properly fix it. The point here is that make it more complex will not break this already existent dependency and will probably be reverted when we move it to the kernel.

Fixes #58502


[$500] Room - Message about exceeding length of welcome message is displayed only after opening it again

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.15-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Go to URL https://staging.new.expensify.com/
Login with any Expensifail account
Open any room
Click on the room's header -> Settings -> Welcome message
Enter any long text -> Save
Open Welcome message again

Expected Result:
A message about exceeding the length of the welcome message is displayed when you try to save it
Actual Result:
Message about exceeding the length of the welcome message is displayed only after opening it again.

incorrect error message displayed, I was expecting a message that the welcome message is too long, but it shows a message that the room name is too long

Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/3ac9f561-62bd-4641-873e-d6075af0921e
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01b9540602d7d80bc9
Upwork Job ID:<PHONE_NUMBER>541582336
Last Price Increase: 2023-12-21

Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
The BE's limit for the welcome message's length is lower than the one set on the form.
What changes do you think we should make in order to solve the problem?
We do have the maxLength set for the welcome message field. We can just adjust this value to the one that's accepted by BE so we'll avoid failing with the error:
https://github.com/Expensify/App/blob/fd71747303cd8df7fc1dfc9b010752e5635b2684/src/pages/ReportWelcomeMessagePage.js#L106
What alternative solutions did you explore? (Optional)

It needs to be handled in https://github.com/Expensify/App/issues/18647

Proposal
Please re-state the problem that we are trying to solve in this issue:
When we save a long text to welcome message, we will see the error message only after reopening the page. Also, the wrong error gets displayed (room name, not welcome message).
What is the root cause of that problem?
In fact, no error should be displayed in the first place. The welcome message gets treated as a comment, with '    MAX_COMMENT_LENGTH: 10000', whereas the room name has a max name of 'MAX_ROOM_NAME_LENGTH: 79'. The tester above typed in a message of a character length of 85, which is above max_room_name_length but vastly below max_comment_length.
What changes do you think we should make in order to solve the problem?
Install front-end checks (currently backend seems to define error messages, which are not fine-tuned for maxLength property https://github.com/Expensify/App/issues/18647). Install the front-end checks in the function: 'updateWelcomeMessage', by adding an additional prop 'maxLength' - and checking if 'newValue' before parsing is smaller than MAX_ROOM_NAME_LENGTH.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~012a0720a0e6c74f6a

Should be fixed here https://github.com/Expensify/App/issues/18647.


[FEA] Make the Morpheus CLI Extendable with the Ability to Add New Commands

Is your feature request related to a problem? Please describe.
All pipelines that define at least 1 custom Stage must use the Python interface and cannot use the CLI. This is because there is no way to register new stages with the CLI unless they are built as first-party stages. This forces all of our built-in examples to use the python interface, duplicating a lot of click commands.
Describe the solution you'd like
Custom stages could be registered as commands with the CLI using various methods (such as a decorator). Once registered, CLI commands simply forward all options as kwargs to the constructor of each stage.
Additional context
Custom stages could be automatically discovered using the entry_point functionality in python. This is used by tools such as pytest to build extensions into the pytest CLI.

click-plugins has not been updated in a few years but may be helpful as an example solution even if you don't use it directly.


Enable Hyperthreading Support using threads

The latest release switched from vcpu to pcpu, so hyperthreading is no longer captured in the configuration.  Suggest using threads to allow 2 threads per core/cpu on VMs that support it.

@anhoward I'm still seeing the following in my cyclecloud.conf:
PartitionName=hpc Nodes=hpc-pg0-[1-10] Default=YES DefMemPerCPU=7680 MaxTime=INFINITE State=UP
Nodename=hpc-pg0-[1-10] Feature=cloud STATE=CLOUD CPUs=2 ThreadsPerCore=2 RealMemory=15360

PartitionName=htc Nodes=htc-[1-10] Default=NO DefMemPerCPU=3584 MaxTime=INFINITE State=UP
Nodename=htc-[1-10] Feature=cloud STATE=CLOUD CPUs=2 ThreadsPerCore=2 RealMemory=7168

The htc partition is F4s_v2 and the hpc partition is D4ds_v4.  I would expect to see CPUs=4 ThreadsPerCore=1 for both.
I'm on CC v8.1.1-1451 and Slurm 2.4.4


[BUG] Segment fault error caused by pxTopOfStack

Hi~
I use ubuntu 20.04 and run FreeRTOS_Plus_TCP_Echo_Posix on it.
However, it down because of segment error.
And I use gdb to debug it.
Found that this func " pxNewTCB->pxTopOfStack = pxPortInitialiseStack( pxTopOfStack, pxNewTCB->pxStack, pxTaskCode, pvParamet)" that produce some bug?
I used static way.
I also change some xTaskCreateStatic to xTaskCreate, however, it only works for some task while others don't.

Could you share a minimal code sample reproducing the issue?

Hi xzwDavid. We have applied a simple patch, increasing the stack size. Could you please verify that this addresses your issue?

Thanks for your responding!

It seems still wrong.Here is my debug info.
Sorry for I could not upload image last time.

Also, when I change static way to dynamic, it works for some at the beginning, however, it fails when called by Timer.c

Hi, I think I found the problem.
In ubuntu, the StackDepth would be set to zero.
And I don't know how to fix it.
PS:
I made some hard code for it, like set the onfigTIMER_TASK_STACK_DEPTH to big which is passed in "xTaskCreate". Such trick works.

After a lot of time and debugging, I think I found where the bug is.
In some linux-OS, the value of "PTHREAD_STACK_MIN" would be too big to fail the type casting.
Such problem could be fixed by change type casting to match bigger "PTHREAD_STACK_MIN".
I do want to commit a PR but It seems that I don't have permission.
: )

Hi xzwDavid,
We have tried running the Demo on Ubuntu 20.04 LTS and 22.04 LTS , it runs properly without any segmentation error. Would you try re-running with a fresh clone and check if the issue still persists?
And when you say changing type casting to match bigger "PTHREAD_STACK_MIN", I assume you mean this line
https://github.com/FreeRTOS/FreeRTOS/blob/main/FreeRTOS-Plus/Demo/FreeRTOS_Plus_TCP_Echo_Posix/FreeRTOSConfig.h#L46

xzwDavid, could you post the FreeRTOSConfig.h you are using as well along with the toolchain you are using to compile if it is not the default one?

Sure!

FreeRTOSConfig.zip

I've tried to reproduce with your FreeRTOSConfig.h. I am running on a 64bit platform and so I have to add the following config otherwise an assertion was triggered, however it does keep executing with the assertion and it could mean under-allocated buffers which could result in a stack overflow:
#define ipconfigBUFFER_PADDING (30)
I also tried building adding -fstack-protector-string and running it through valgrind and wasn't able to find any other issue in my setup. Could you try the config above?
I'm testing with the same version of Ubuntu and gcc.

Hi~ Thanks for your guys time.
I just reclone it with command "git clone https://github.com/FreeRTOS/FreeRTOS.git --recurse-submodules" and navigate to Demo, make, cd build and run.
This bug still here and I still insist my opinion about it so I print the value.

There is a considerable difference that my ubuntu is arm architecture:

Archive.zip

Your finding is correct. We should remove the unsigned short cast from here - https://github.com/FreeRTOS/FreeRTOS/blob/main/FreeRTOS-Plus/Demo/FreeRTOS_Plus_TCP_Echo_Posix/FreeRTOSConfig.h#L46

This PR address this - https://github.com/FreeRTOS/FreeRTOS/pull/971
Can you confirm that this fixes your issue?

I am closing this issue. Feel free to reopen or create a new one if you still face some issue.


[41] First Missing Positive & [27] Remove Element

Codecov Report

Merging #29 (d2ab4af) into master (547a095) will increase coverage by 3.6%.
The diff coverage is 97.6%.

Impacted Files
Coverage Δ

src/problem/p0027_remove_element.rs
96.4% <96.4%> (ø)

src/problem/p0041_first_missing_positive.rs
100.0% <100.0%> (ø)


Use webpack's i18n

Use Webpack's i18n plugin.
https://github.com/webpack/webpack/tree/master/examples/i18n

Webpack's plugin is not what should be used for the current architecture of the project.


Allow configuring of CORS allow origin headers

Code Version
running satosa in docker, with SATOSA oidcop frontend
Expected Behavior
Have a way to configure CORS allowed origins, for example in keycloak they seem to call it "Web Origins" and it's configured per client
Current Behavior
When making requests to for example openid-configuration or userinfo endpoint from a react SPA, requests are blocked because there is no Access-Control-Allow-Origin headers in the response, and I can't find a way to configure this in satosa
Possible Solution
New configurations and/or documentation?
Steps to Reproduce

Right now this functionality is offloaded to the frontend web-server that you are probably already using (ie, nginx). There you can define properly what headers should be returned for a specific request.
I do not reject implementing this but it is definitely not a priority, and it brings in the question "how many other things that a web-server does should be part of the configuration of this app?".


Cert issues on projectlombok.org

Hi,
Currently https://projectlombok.org/ is not viewable due to cert issues:

@bcoughlan For me, it works with both Chromium (Version 64.0.3282.167 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)) and Firefox (58.0.2 (64-bit)). And with lynx (2.8.9dev.8 (21 Dec 2015)), too. Click on learn more to learn more?

Seemed to have been exclusive to Firefox Nightly. Probably was a bug in the Firefox trunk.

@bcoughlan @Maaartinus This is not an issue with Firefox Nightly (since 60), same happens with Chrome Cannary (since 66) - this is probably ongoing removal of Symantec issued certificates:

https://blog.nightly.mozilla.org/2018/03/05/these-weeks-in-firefox-issue-33/
https://security.googleblog.com/2017/09/chromes-plan-to-distrust-symantec.html

It looks like you need to get new certificates.

@krzyk You're right. My Chrome writes a warning in the console:
The SSL certificate used to load resources from https://projectlombok.org will be distrusted in M66. Once distrusted, users will be prevented from loading these resources. See https://g.co/chrome/symantecpkicerts for more information.
@rzwitserloot @rspilker The certificate expires on 2018-05-02, Chrome 66 won't accept it (as it was issued before June 1, 2016). Chrome 66 beta is planned for on 2018-03-05, Chrome 66 stable is planned for 2018-04-17.

see https://dotblogs.com.tw/grayyin/2018/08/14/120458
1、compile the class InstallCert.java :  "javac InstallCert.java"
2、run the class :  "java  InstallCert projectlombok.org"
3、input "1"  enter
4、 copy the cert which output form steps before  to  "JAVA_HOME/jre/lib/security"
5、enjoy it !


Crash on exit with OSX

While upgrading to the master branch, I came across a very rare crash (sometimes it'll take 10s of thousands of runs before a crash) that happened upon shutdown on my high sierra OSX machine:
libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument

This is a bug in OIIO.  The following patch, which is perfectly valid code, allows it to happen on almost every run:
diff --git a/src/libutil/thread.cpp b/src/libutil/thread.cpp
index ca2d8024..fe758703 100644
--- a/src/libutil/thread.cpp
+++ b/src/libutil/thread.cpp
@@ -126,7 +126,9 @@ public:

     // the destructor waits for all the functions in the queue to be finished
     ~Impl () {
+        printf("~thread_pool::Impl called\n");
         this->stop(true);
+        printf("~thread_pool::Impl manual destruction finished. Automatic destructors happen now\n");
     }

     // get the number of running threads in the pool
@@ -300,8 +302,11 @@ private:
                         isPop = this->q.pop(_f);
                 }
                 // the queue is empty here, wait for the next command
+                printf("set_thread: the queue is empty here, wait for the next command\n");
+                sleep(1); // wait for mutex to be destroyed
                 std::unique_lock<std::mutex> lock(this->mutex);
                 ++this->nWaiting;
+                printf("this->cv.wait\n"); // we made it through with no crashes!
                 this->cv.wait(lock, [this, &_f, &isPop, &_flag](){ isPop = this->q.pop(_f); return isPop || this->isDone || _flag; });
                 --this->nWaiting;
                 if (!isPop)
@@ -322,6 +327,9 @@ private:
     std::atomic<bool> isStop;
     std::atomic<int> nWaiting;  // how many threads are waiting
     int m_size {0};             // Number of threads in the queue
+    struct Foo{ ~Foo() {
+       printf("mutex was destructed. pausing ~thread_pool::Impl() for 1s!\n"); sleep(1); }
+    } this_gets_destroyed_after_mutex;
     std::mutex mutex;
     std::condition_variable cv;

The bug here is that when we are shutting down and destroying everything, the thread pool class is destroyed while the detached worker threads are still making use of its member variables.  This patch pauses the destructor for 1s after the mutex is destroyed and makes the worker thread delay exiting by 1s so that when it finally locks the mutex it's now much more likely that the mutex will have been destroyed and OSX throws the error.
We could wrap all usage of the mutex usage in a try/catch block, and that does help a lot with this crash, however, even then I worry that we might still get other crashes due to other errors that could be triggered with using a mutex and other state that has been destroyed, not to mention maybe on other operating systems, or future versions of OSX, this could start to fail.  So I think it might be better to have a proper fix.
I wonder if this could be related to #1572 and #1795?

Another important bit of info is that this crash happens only when we do  OIIO::attribute ("threads", 1); because that causes all the threads to be detached which are not waited on when we exit.  I think the following might fix it:
diff --git a/src/libutil/thread.cpp b/src/libutil/thread.cpp
index c1da23d8..bb10bf9b 100644
--- a/src/libutil/thread.cpp
+++ b/src/libutil/thread.cpp
@@ -159,7 +159,8 @@ public:
             else {  // the number of threads is decreased
                 for (int i = oldNThreads - 1; i >= nThreads; --i) {
                     *this->flags[i] = true;  // this thread will finish
-                    this->threads[i]->detach();
+                    this->terminating_threads.push_back(std::move(this->threads[i]));
+                    this->threads.erase(this->threads.begin() + i);
                 }
                 {
                     // stop the detached threads that were waiting
@@ -218,10 +219,15 @@ public:
             if (thread->joinable())
                 thread->join();
         }
+        for (auto& thread : this->terminating_threads) {  // wait for the terminated threads to finish
+            if (thread->joinable())
+                thread->join();
+        }
         // if there were no threads in the pool but some functors in the queue, the functors are not deleted by the threads
         // therefore delete them here
         this->clear_queue();
         this->threads.clear();
+        this->terminating_threads.clear();
         this->flags.clear();
     }

@@ -317,6 +323,7 @@ private:
     void init() { this->nWaiting = 0; this->isStop = false; this->isDone = false; }

     std::vector<std::unique_ptr<std::thread>> threads;
+    std::vector<std::unique_ptr<std::thread>> terminating_threads;
     std::vector<std::shared_ptr<std::atomic<bool>>> flags;
     mutable Queue<std::function<void(int id)> *> q;
     std::atomic<bool> isDone;

If it looks good I can try to make a pull request.

Fixed by #2013


python39Packages.howdoi: disable failing tests

Description of changes
Fix build (https://hydra.nixos.org/build/175224744)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 171519 run on x86_64-linux 1

2 packages built:

python310Packages.howdoi
python39Packages.howdoi


refactor(ES6): WebWorkerHotUpdateChunkTemplatePlugin.test.js

What kind of change does this PR introduce?
refactor, ES5 => ES6

Did you add tests for your changes?
All existing tests pass

If relevant, link to documentation update:
N/A

Summary
Refactor WebWorkerHotUpdateChunkTemplatePlugin.test.js to ES6

Does this PR introduce a breaking change?
No

Looks good thanks


Unusual 3rd-party keyboard layout issue; Can't type digits with Shift in Neovim in PowerShell?

Environment
Windows build number: 10.0.19033.0
Windows Terminal version (if applicable): 0.7.3382.0 (but it's reproduceable in earlier builds too)

Neovim: 0.4.2
PowerShell Core: 7.0.0-preview.6
Universal keyboard layout: https://github.com/braindefender/universal-layout

Steps to reproduce

Start Terminal with PowerShell Core.
Start Neovim.
Switch to insert mode (press i).
Type any digit by holding Shift and pressing a key with a digit on it. Like 3.

Expected behavior

The digit is typed.
Actual behavior

Nothing is typed.
Additional information
I can type digits in WSL2 Ubuntu. The rest of the setup is the same.
I also can type digits in plain PowerShell Core, without Neovim.
Also, I can type digits in Neovim under PowerShell Core if I run it not in Windows Terminal, i.e. if I run the regular old school terminal.
Also, I can type digits in Vim instead of Neovim.

This is now the master thread for "the things that third-party keyboard layout patches" cause. Thanks for the report!


Suggestions for ZeroDowntimeMigrations::Validation::AddColumn

I see that you recommend splitting one (potentially unsafe) change over several migrations, in the case of ZeroDowntimeMigrations::Validation::AddColumn.
I think it would be just as good to have the change just split into the suggested statements. This would leave just one point of truth for the change and also make rollback easier as a consequence.
Also, I would suggest to use say or even better say_with_time for the find_in_batches-output.
What are your thoughts on this?

Hey @kronn - the issue for the add_column case is that ActiveRecord wraps each migration in one big DDL transaction. Even if we split apart into the suggested statements, if they all run in the same DDL transaction then splitting them has no effect. It will lock the table just like it does when we call add_column with the :default option.
By splitting these statements into separate migrations, each transaction is committed before moving onto the next one. This way the column can be added quickly without holding up the transaction and locking the table while thousands of existing records are updated with the new column default.
I like your suggestion for using say_with_time for the batches output, I'll leave this issue open until we make that change. Thanks for the feedback!


New to python and hand history conversion. Need help

I have successfully downloaded python and this converter, but I don't know how to use it. I have no idea what to type for filename and am very confused about usage in general. Is there an example input I can follow? Sorry for the inconvenience, but I am a newbie. Thanks.

Hey Mike,
Apologies, I only just saw your message! If you are still wanting to use the tool and are not had any luck please reopen/reply to this issue and I will walk you through it!
Thanks,
Charles


MP Data source: cannot override using environment variables

Environment Details

Helidon Version: 1.4.1
Helidon MP

Problem Description
When using CDI integration for data sources, we cannot override some settings using environment variables.
This is most likely caused by approach (such as in AbstractDataSourceExtension line 312) where we iterate through config sources instead of getting the value from config.
This approach may miss environment variable rules.

I'll take a look.  Related: https://github.com/eclipse/microprofile-config/issues/431#issuecomment-519858099

@tomas-langer Looping back to this: is it your opinion that environment variable substitution rules should be housed outside of individual ConfigSources?

@ljnelson - yes, this is done by the environment variable config source (and if you disable it, it should not happen). This also depends on order of config sources (so if your file source is before environment variables source, these rules will not trigger.
The method to get config sources is not intended for obtaining properties. You should always use methods on Config to follow the spec (otherwise you may get values from the wrong place)

Do you know offhand if, in our implementation, the requirement that the set of property names returned by Config#getPropertyNames() be equal to the union of the sets of property names returned by each installed ConfigSource is honored?  It would seem if environment variables are aliased based on, among other things, the order of installed ConfigSources this would not be the case.

Whoops; never closed this; fixed back in September with #2322


wee-slack read state not sync'd with Slack

It seems like somewhere between c9e801e and 9e0db5b827768d2b406787b609f400343b8929f6 (current master) wee-slack marking messages as read was broken. Currently if I receive a message, read/respond to it via wee-slack and then open Slack.app, the message is still unread. This also means if you relaunch weechat the buffers are again marked as unread. I also ran /slack setallreadmarkers and it did not solve the problem.

Turns out this might not be a wee-slack problem. Even the first commit I mentioned stopped correctly writing the read state, now I wonder if it's slack/slack.app

Does this apply to normal messages?  I'm not seeing this (but I'm seeing something slightly related where we highlight some messages on startup even though they're not generating highlights in a running wee-slack, due to the smart irc filter).

Yep, I'm seeing this on DMs, channel notifications, and just channel unread state.

Seems like this has resolved itself. So I guess this is on the API side.


Instagram OSINT is not working

Instagram OSINT  is not working. OS was Kali Linux....

Hey, thanks for bringing our attention toward the  issue , the issue has been fixed and reflect in the next version


Add logging of transport error

Hello,
I noticed that the transport error are not logged here while they are logged in the enricher example.
This is a small PR to add logging of these errors.

Good catch. Will test and merge. Thank you


Cpacs 3 choice validation

Added generator support for validating choices.
Fixes #246

Nice PR! Just as I want it to be ;) I just let the CI finish before merging.


Doubts about GeometricBilinear Implementation

Regarding the Geometric bilinears, paper mentions :

showing x and y to be the same for geometric product and join operation.
However, in the GeometricBilinear class: https://github.com/Qualcomm-AI-research/geometric-algebra-transformer/blob/b101736ea293796176cc09dd7d5456773e65a95c/gatr/layers/mlp/geometric_bilinears.py#L14
4 Equilinears are defined. If x and y are the same for both join and geometric product operator, the shouldn't the corresponding code be like the following?
        # EquiLinear Layer
        left, _ = self.linear_left(multivectors, scalars=scalars)
        right, _ = self.linear_right(multivectors, scalars=scalars)

        # GP
        gp_outputs = geometric_product(left, right)

        # Equivariant join
        join_outputs = equivariant_join(left, right, reference_mv)

        # Output linear
        outputs_mv = torch.cat((gp_outputs, join_outputs), dim=-2)
        outputs_mv, outputs_s = self.linear_out(outputs_mv, scalars=scalars)

Hi,
good catch!
Indeed, here the paper description is not accurate. Both versions in principle define expressive architectures. However, we believe that it makes more sense to use two independent equivariant linear maps for the join and the GP: the version implemented in the repository is in our opinion better than the simpler equation in the paper.
Apologies for the confusion. We can't update the NeurIPS paper anymore, but we will discuss updating this in the arXiv version.
Thanks,
Johann


endpoints: Wait for Envoy to be ready before peers are updated with new Endpoints

This issue is for the following sub-issues:

[ ] Build a quick proof of concept of the idea described below
[ ] Create a small design document
[ ] Create sub-issues and link to this issue
[ ] Implement (if feasible) the design

Context
Current version of OSM (v0.8.2) signals an update to Envoys' endpoints when a new Pod appears.
This needs to be augmented with an additional checks.  A new endpoint is ready to be sent to all interested / relevant proxies when:

[ ] new Pod appears in the cluster
[ ] an Envoy for the Pod has connected to the OSM Control plane
[ ] the Envoy has been configured to accept traffic

All 3 must be in effect before the endpoint is sent to relevant Envoys.
The endpoints OSM should be sending to connected Envoys is the following set operations:
{available endpoints}  :=  {pods}  ∩  {connected Envoys}  ∩  {configured Envoys}

This is where we create Pods informer and trigger updates to the rest of OSM when Pod (add/delete/update) events arrive from Kubernetes:  https://github.com/openservicemesh/osm/blob/release-v0.8/pkg/kubernetes/client.go#L112-L122
These events are sent via the PubSub singleton used by many of the OSM Components: https://github.com/openservicemesh/osm/blob/release-v0.8/pkg/kubernetes/event_handlers.go#L40
Where the NewPodEvent triggers an Envoy config update:  https://github.com/openservicemesh/osm/blob/release-v0.8/pkg/catalog/dispatcher.go#L82

@draychev could you kindly describe how the following in this issue:

How this optimization benefits the system?
What the tradeoffs are with the subtle optimization vs additional complexity?

@shashankram Just to be clear -- with this GitHub issue we are going to:

Understand what can be done to send Endpoint (EDS) updates at the right time (when these Endpoints are indeed ready)
Show a prototype and a design doc proposing the solution
Discuss the complexity this will add and whether the benefits outweigh drawbacks (complexity etc.)

@shashankram I believe the 1,2,3 above will address your concerns, which are valid, valuable, and must be addressed!
@nojnhuh I hope you agree with this plan of attack.

I've written up my findings on what difference this change would make and involve here: https://docs.google.com/document/d/1M1-lKRIeZ53sKen1tfHG8Q9Etof6PHSVyFcu1o0oJGQ/edit?usp=sharing
To sum it up, adding this may change very little and implementing it properly would probably be fairly costly.
/cc @shashankram @draychev @eduser25

Based on what I've written up for this previously, I don't think it's worth looking into anymore.


Error while setting up mintmobile platform for sensor

Describe the bug
After configuring the integration through the UI I hit finish (with no errors). The integration does not show any entities/devices. In the logs I found this:
Error while setting up mintmobile platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 199, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/mintmobile/sensor.py", line 27, in async_setup_entry
    lines = await hass.async_add_executor_job(mm.lines)
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/mintmobile/api.py", line 124, in lines
    self.get_family_members()
  File "/config/custom_components/mintmobile/api.py", line 85, in get_family_members
    for activeMembers in response["activeMembers"]:
KeyError: 'activeMembers'

I do not have mint family setup.
To Reproduce
Steps to reproduce the behavior:

Try to configure a new integration (installed through hacs)

Version: HA 2020.12.0

I'll take another look at that section and push out a new version some time today.

@FoxxMD Just released v1.4 that should hopefully fix the issue you were seeing. Please let me know as I don't have a single account to test with.

Updated to 1.4 and still getting the same error. I restarted HA after the HACS install. then tried reloading the integration, then removing and re-adding it. Same error all three times.
2020-12-22 23:11:59 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up mintmobile platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 199, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/mintmobile/sensor.py", line 27, in async_setup_entry
lines = await hass.async_add_executor_job(mm.lines)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/mintmobile/api.py", line 130, in lines
self.get_family_members()
File "/config/custom_components/mintmobile/api.py", line 88, in get_family_members
if response["activeMembers"]:
KeyError: 'activeMembers'

Interesting. Let me add a few more items to my debugging script as that will help me identify what response you are getting back from their API. I figured it would just be an empty object but that doesn't seem like the case.

Same, HA: 2020.12.7 Home Assistant OS: 5.8, Version 1.4 Installed via hacs

@Codel1417 @FoxxMD Try v1.4.1 as it should be fixed. I was able to get credentials for a single account to test with and was able to replicate the issue myself this time around.

Fixed it for me! thanks


feat: optimism

Added config for Optimism

lgtm tests passing

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


HTML

HTML
User Story
As a bootcamp student
I want the prework notes to be structured on the webpage
so that i can easily find and read information
Acceptance criteria
GIVEN A prework study guide website
WHEN I visit the website in my brower
THEN I see four boxes titles HTML,CSS,JAVASCRIPT,GIT with associated notes listed

successfully closed


Add a "Secure your home network and devices" section to the "Preparations" chapter

What
This PR is a proposal to add a recommendation to harden the security of the user home network and devices before starting building their node  (e.g. set WPA2, disable WPS, change admin password etc).
This is done through a new section at the end of the "Preparations" chapter; after creating all the passwords. The section introduces the rationales for securing the home networks and devices and points to a 3rd party tutorial (external URL).
While I prefer avoiding 3rd-party tutorials if possible, making an internal guide that goes through all the security tips might make that chapter a bit too long and be considered OOT.. (?)
I selected this guide: https://restoreprivacy.com/secure-home-network/ but if you know of a better/more reliable or trustworthy tutorial, please suggest an alternative URL.
Why
Securing the home network and devices is a critical component of securing the use of a Bitcoin and Lightning node and new users would benefit from being guided on how to do it.
Wdyat?
Scope

[ ] significant change to core configuration
[x] minor change to core configuration
[ ] independent bonus guide
[ ] simple bug fix

Test & maintenance
Read the tutorial and check that its recommendations are valid and sufficient.

reasonable addition!

Do you think an external link is the best way to do it?
If so, do you know of maybe a better external tutorial? Maybe one done by a bitcoiner?

Do you think an external link is the best way to do it?
If so, do you know of maybe a better external tutorial? Maybe one done by a bitcoiner?

I think your linked guide covers all the important things to do on every network.