Bundler crashes when force_ruby_platform is set to true

This is in response to https://github.com/bundler/bundler/issues/5337 .
Error Report
Questions
Please fill out answers to these questions, it'll help us figure out
why things are going wrong.

What did you do?
I ran the command

C:\Users\lars\railstest>bundle config force_ruby_platform true
C:\Users\lars\railstest>bundle

What did you expect to happen?
I expected Bundler to install only platform=ruby gems and ignore any native gems.

What happened instead?
Instead, what happened was that bundler crashed with this exception.

Have you tried any solutions posted on similar issues in our issue tracker, stack overflow, or google?
I tried bundle lock --add-platform=ruby and bundle lock --add-platform=ruby --remove-platform=x86-mingw32 as alternatives, which don't crash, but get unexpected results. See issue https://github.com/bundler/bundler/issues/5337 .

Have you read our issues document, https://github.com/bundler/bundler/blob/master/ISSUES.md?
... Good to know - I probably should.

Backtrace
NoMethodError: undefined method `os' for "ruby":String
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/current_ruby.rb:65:in `mingw?'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/dependency.rb:123:in `block in current_platform?'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/dependency.rb:122:in `any?'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/dependency.rb:122:in `current_platform?'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/dependency.rb:106:in `should_include?'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/definition.rb:894:in `block in compute_requires'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/definition.rb:893:in `each'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/definition.rb:893:in `reduce'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/definition.rb:893:in `compute_requires'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/definition.rb:120:in `initialize'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/dsl.rb:200:in `new'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/dsl.rb:200:in `to_definition'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/dsl.rb:12:in `evaluate'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/definition.rb:33:in `build'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler.rb:128:in `definition'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/cli/install.rb:67:in `run'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/cli.rb:181:in `block in install'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/settings.rb:98:in `temporary'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/cli.rb:180:in `install'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/cli.rb:20:in `dispatch'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/cli.rb:11:in `start'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/exe/bundle:32:in `block in <top (required)>'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors'
  C:/Ruby24/lib/ruby/gems/2.4.0/gems/bundler-1.14.0/exe/bundle:24:in `<top (required)>'
  C:/Ruby24/bin/bundle:22:in `load'
  C:/Ruby24/bin/bundle:22:in `<main>'

Environment
Bundler   1.14.0
Rubygems  2.6.8
Ruby      2.4.0p0 (2016-12-24 revision 57164) [i386-mingw32]
GEM_HOME  C:/Ruby24/lib/ruby/gems/2.4.0
GEM_PATH  C:/Ruby24/lib/ruby/gems/2.4.0;C:/Users/lars/.gem/ruby/2.4.0
Git       2.5.0.windows.1
Platform  x86-mingw32
OpenSSL   OpenSSL 1.0.2j  26 Sep 2016

Bundler settings
build.nokogiri
  Set for the current user (C:/Users/lars/.bundle/config): "--use-system-libraries --with-xml2-include=c:/msys64/mingw64/include/libxml2 --with-xslt-dir=c:/msys64/mingw64"
force_ruby_platform
  Set for the current user (C:/Users/lars/.bundle/config): "true"

Can you please also include your Gemfile?

The corresponding Gemfile: https://gist.github.com/larskanis/a1769c8abca6577c6d0d640889965d5b

https://github.com/bundler/bundler/pull/5345 should fix this!

Yes, #5345 fixes this issue.


Firewall configuration

Firewall configuration for whole cluster moved to new playbook tendrl_firewall.yml (separated by particular role).
Workaround (disable firewall) moved to tendrl_firewall_workaround.yml.

That said, later when we have a clear understanding of ceph/gluster vs tendrl firewall setup and related responsibilities and supported use cases, we may need to tweak or even change how we do the firewall configuration during setup (ci_default.yml playbook). That said, playbook firewall_tendrl.yml or firewall roles (such as firewall-ceph-osd) would remain as it is now.


Add go-bindata-assetfs to glide

Resolves Issue #751

Coverage remained the same at 100.0% when pulling 76451bae9adb10e5f1f5da6cec8df4a4726e5566 on cory-klein:master into 5c09726c52401b0794bbb930111b5390e32c2ce1 on jaegertracing:master.

CI failure is not related to this change. Fix is #753
@cory-klein could you please sign commits with -s when doing git commit?

@pavolloffay Done

did you run glide up?  We keep glide.lock under source control  too, without it glide install will not install bindata, and you're back to the same problem.

@cory-klein the change looks good, please just run glide up to add it to lock file

@pavolloffay Done

it if failing on travis. Could you please also sing the last commit?

Doh, sorry forgot the -s on that last one. Re-committed with it included this time.

This part of the build keeps failing, but I don't see any clear reason why:
The command "if [ "$CROSSDOCK" == true ]; then bash ./scripts/travis/build-crossdock.sh ; else echo 'skipping crossdock'; fi" exited with 2.
0.00s$ if [ "$DOCKER" == true ]; then bash ./scripts/travis/build-docker-images.sh ; else echo 'skipping docker images'; fi
skipping docker images

Unfortunately I'm unable to replicate the setup for that build step locally, so I can't reproduce.

Build is failing here:
$ if [ "$CROSSDOCK" == true ]; then bash ./scripts/travis/build-crossdock.sh ; else echo 'skipping crossdock'; fi
CGO_ENABLED=0 GOOS=linux installsuffix=cgo go build -o ./cmd/agent/agent-linux -ldflags "-X github.com/jaegertracing/jaeger/pkg/version.commitSHA=0decadb5a363030e422660e836fac82c4eaaab6c -X github.com/jaegertracing/jaeger/pkg/version.latestVersion=v1.2.0 -X github.com/jaegertracing/jaeger/pkg/version.date=2018-03-27T19:04:01Z" ./cmd/agent/main.go
# github.com/jaegertracing/jaeger/vendor/github.com/spf13/viper
vendor/github.com/spf13/viper/viper.go:1371:10: cannot assign 1 values to 2 variables
make: *** [build-agent-linux] Error 2
The command "if [ "$CROSSDOCK" == true ]; then bash ./scripts/travis/build-crossdock.sh ; else echo 'skipping crossdock'; fi" exited with 2.

But it's not apparent to me whether this could be caused by changes specific to this PR.
The cited viper.go code is here

Looks like a breaking change was introduced in viper? Do you mind pinning viper to 25b30aa063fc18e48662b86996252eabdcf2f0c7 in glide.yaml and see if that passes?


ts-web/ext-utils: add instructions

Part of this is imported from some materials we shared privately. I've adjusted it to be more general. Then, I added instructions for the dapp side as well.

ah I see you filed #251


Fix issues involving math.tau

Many users have been complaining about the number extension suddenly not working. This is because some servers don't have math.tau defined on them for whatever reason. This PR presents a twofold solution:

It sets a fallback for math.tau when it is undefined.
It ensures any future invalid constants will not cause extensions to fail loading.

Changes:

Add fallback for math.tau
Change error in E2Lib.registerConstant to use WireLib.Notify instead so invalid constants don't break the extension.
Added some context to the errors in E2Lib.registerConstant (This functionality should probably be moved to its own function)
Added timeout for WireLib.Notify "nudges" on the client

Updated error form (note E2 executes extension files twice):

Messed up something with the git history whatever

This is because some servers don't have math.tau defined on them for whatever reason.

That's because GMod updates are optional and servers are outdated sometimes. The math.tau constant was added in last main update. Rubat's tip toeing around net compatibility makes it possible that server could be outdated by 2+ years and still be able to connect to. Good look accounting for those servers in addon code on the long run.


Marriage Abroad - Update Cyprus outcome

Cyprus has a High Commission office and not Embassy or Consulate. Content updated.
ticket: https://www.pivotaltracker.com/story/show/87797826

Jack just explained this to me. :partly_sunny:


Enhancement: multiple versions installed

Is there an existing issue for this?

[X] I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?
windows OP installer is removing records of current versions of OP installed.

previous versions need to be removed manually

How would you imagine the implementation of the feature?

the installer should register each version and let the user uninstall specific version
the installer should ask if you want to remove already installed version

Are there any labels you wish to add?

[X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:
No response
Additional context:
OS: Windows
[cuID:OP-6035]

obsolete with AYON, closing


Unable to locate DLL file (7b96aa82)

This issue was submitted by the add-in's exception handler.

Exception:
Bovender.Unmanaged.DllNotFoundException: Unable to locate DLL file
   at Bovender.Unmanaged.DllManager.LoadDll(String dllName, String expectedSha1Hash)
   at Bovender.Unmanaged.DllManager.LoadDll(String dllName)
   at XLToolbox.Export.Exporter..ctor()
   at XLToolbox.Export.Exporter..ctor(SingleExportSettings settings)
   at XLToolbox.Export.ViewModels.SingleExportSettingsViewModel..ctor(SingleExportSettings singleExportSettings)
   at XLToolbox.Dispatcher.ExportSelection()
   at XLToolbox.Dispatcher.Execute(Command cmd)

Message: Unable to locate DLL file
Environment

Parameter
Value

Version
7.1.4

OS
Microsoft Windows NT 6.1.7601 Service Pack 1, 64-bit

Excel
2013 SP1 (15.0.4867), 32-bit

CLR
4.0.30319.18444, 32-bit

VSTO runtime
10.0.40820

ClickOnce
True

Bovender
<IP_ADDRESS>

FreeImage
Unable to locate DLL file

Fixed in v7.2.0.


EntryPointNotFoundException: Entry point not found 'rs2_query_devices_ex' in DLL file 'realsense2'.

Required Info

Camera Model
SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win (10) x64

Platform
PC

SDK Version
2.0 (build 2.16.3)

Language
C#

.NET Framework
4.6.1

Issue Description
Just updated the Real Sense SDK to the latest release, (uninstalled and perform a clean installation), then on my project reimported the Intel.Realsense.dll for my current release configuration: Release x64.
Imported Intel.Realsense.dll reference from C:\Program Files (x86)\Intel RealSense SDK 2.0\bin\x64
Then after compiling VS throws this exception:
EntryPointNotFoundException: Entry point not found 'rs2_query_devices_ex' in DLL file 'realsense2'.
Just for this simple code:
      public void ExampleTwo()
        {
            FrameQueue q = new FrameQueue();
            using (var ctx = new Context())
            {
                var lst = ctx.QueryDevices();
                foreach (var item in lst)
                {
                    Console.WriteLine(item.Info[CameraInfo.SerialNumber]);
                }
            }
        }

How can I tackle this issue??....
The RealSense Viewer works fine and detect both SR300 cameras connected to the PC.

I think there is a version mismatch between realsense2.dll and Intel.Realsense.dll. I suggest a search for realsense2.dll under your .NET solution folder, followed by replacing all occurrences with the one from  C:\Program Files (x86)\Intel RealSense SDK 2.0\bin\x64. Please let me know if it helps, hope it does, this seem like the most likely solution.

Solved, just replaced the realsense2.dll on the project folder, not the solution one. Thanks.


Update bootstrappers

@ryanbrandenburg,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@mikaelm12 / @natemcmaster could you guys take a look?


⚠ Bofrost.at has degraded performance

In f10b2f0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1255 ms

Resolved: Bofrost.at performance has improved in b494c48.


Change from Named to Ephemeral/Anonymous channels

Currently each request create a new named channel which requires an offer/accept to be concluded before the request stream can be used.
The intention is to have a configurable number of fixed Ephemeral/Anonymous channels so that the request stream can be sent to immediately hence reducing latency.
Note: Both ends will need to be configured with the same number of channels if not using the default

After initial attempt creating a creating a pool of channels from the server side (updated RelayConnection class below) the main limitation is on the client end as there needs to be an event to trigger the creation of the MultiplexingStreamConnectionContext anyways.
So the ChannelOffered mechanism almost perfectly facilitates this so this enhancement is no longer valid.
public class RelayConnection(WebSocket webSocket) : IDisposable
{
    private Channel<MultiplexingStream.Channel>? channels;
    private MultiplexingStream? stream;
    private ConcurrentBag<int> availableChannels = new();

    public async Task<IDisposable> OpenAsync(int capacity)
    {
        if(stream != null) throw new InvalidOperationException("stream already open");
        channels = Channel.CreateBounded<MultiplexingStream.Channel>(capacity);
        var options = new MultiplexingStream.Options { ProtocolMajorVersion = 3,};
        foreach (var i in Enumerable.Range(1, capacity))
        {
            availableChannels.Add(i - 1);
            options.SeededChannels.Add(new ());
        }
        stream = await MultiplexingStream.CreateAsync(webSocket.AsStream(), options);
        _ = PopulateChannelsAsync();
        return stream;
        async Task PopulateChannelsAsync()
        {
            while (!channels!.Reader.Completion.IsCompleted)
            {
                if(!await channels.Writer.WaitToWriteAsync()) break;
                if (availableChannels.IsEmpty)
                {
                    await Task.Delay(100);
                    continue;
                }
                var channel = stream!.AcceptChannel(availableChannels.First());
                _ = channel.Completion.ContinueWith(_ => availableChannels.Add((int)channel.QualifiedId.Id));
                await channels.Writer.WriteAsync(channel);
            }
        }
    }

    public async Task<MultiplexingStream.Channel> GetChannel() => await channels!.Reader.ReadAsync();

    public void Dispose() {
        channels?.Writer.Complete();
        webSocket.Dispose();
        stream?.Dispose();
    }
}


Options don't override previous setting

Checks to see if option variables already exist before setting them to the default value to allow them to be set in a .vimrc.

Thanks for the PR :-) I'll check it out later in the week/weekend when I get back from holiday.

@Carpetsmoker Ping. :)

Whoops; guess no one has ever tried setting an option before :-)
Thanks!


build error: could not find system library 'glib-2.0' required by the 'glib-sys' crate

build exited with :
  error: could not find system library 'glib-2.0' required by the 'glib-sys' crate

  --- stderr
  Package glib-2.0 was not found in the pkg-config search path.
  Perhaps you should add the directory containing `glib-2.0.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'glib-2.0' found

I did install sudo apt install libglib2.0-dev
but now it says error: could not find system library 'cairo'

Hey, @TristramGreen what is your OS?

Linux Mint. Thank you, it resolved errors about missing packages.

@TristramGreen what was missing, I am also having same error in linux mint, wish you shared what you install.

omg.it is really hard to resolve this problem in windows 10.


Access private User metadata through dashboard

What I'm trying to achieve
After introducing private metadata to User model there might be need for staff to edit/delete/add metadata manually.
Describe a proposed solution
Component to access metadata for User and other future objects with meta.

I don't think we'll need a generic component for accessing metadata in the Dashboard. Instead, I think we'll have some very specific use-cases (payments, particular integrations) that we support and we want them to be configurable in UI.


Remove IJMPConnection as it's not used anymore

Make sure that the kernel.functional tests are still available though. They should either be rewritten to use the rawkernel, or moved to the notebook.functional tests. In particular we don't have a test that verifies a kernel's environment is used.

Interrupt should also be enabled in the other tests for raw kernel.


NEW SOLVER: table.freeze() issues; TypeError when freezing a table with a metatable, and missing first argument crashes the solver

local meta = {
	__index = function()
		return "foo"
	end
}

local myTable = setmetatable({}, meta)
table.freeze(myTable)
--[=[
	table.freeze( ** myTable) **
	TypeError: Type 'myTable' could not be converted into 'table'
]=]

also: table.freeze with a missing first argument crashes the entire solver
local myTable = setmetatable({}, meta)
-- if you were trying to type table.freeze(meta)
-- then the entire solver would crash, forcing you to
-- restart whatever you're coding on
table.freeze() -- Crash!

this wasnt happening to my friend, occurs with VS Code luau language server, please let me know if im using the wrong extension or something

seems to be an issue with the luau language server plugin on VS code, this doesn't occur in roblox studio or neovim

Seems to be fixed


make the docstring more readable and improve the list_models logic

dict.update is more performant, on the side note, we can use something like
from typing import TypedDict

class ModelInfo(TypedDict):
  status: str
  description: str

def list_models(...) -> dict[str, ModelInfo]:
  ...

edit: or maybe we can use Dict from the typing module for compatibility reasons*

ah I ended up writing
models = models.update()


iOS App crash when open isar

Steps to Reproduce
Open app and open isar then crash.
It doesn't crash every time open app. However it does really affect our users.
Code sample
isar = await Isar.open([
    PostMessageEntitySchema,
    AssetEntitySchema,
]);

Details

Platform: iPhone10,6
Flutter version: 3.3.5
Isar version: 3.0.5

crash log
Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Triggered by Thread:  24

Thread 24 name:
Thread 24 Crashed:
0   libsystem_kernel.dylib        	0x00000001bb535bbc __pthread_kill + 8 (:-1)
1   libsystem_pthread.dylib       	0x00000001dbfa4854 pthread_kill + 208 (pthread.c:1668)
2   libsystem_c.dylib             	0x000000018b4220b0 __abort + 124 (abort.c:155)
3   libsystem_c.dylib             	0x000000018b3cd6b8 abort + 136 (abort.c:126)
4   libsystem_malloc.dylib        	0x0000000191ef89d8 malloc_vreport + 548 (malloc_printf.c:183)
5   libsystem_malloc.dylib        	0x0000000191ef8b88 malloc_report + 60 (malloc_printf.c:192)
6   libsystem_malloc.dylib        	0x0000000191eded00 free + 284 (malloc.c:1963)
7   isar_flutter_libs             	0x000000010a7fe5c4 env_close + 140
8   isar_flutter_libs             	0x000000010a7fc320 mdbx_env_open + 1680
9   isar_flutter_libs             	0x000000010a780674 isar_core::instance::IsarInstance::open_internal::h5dfcafd44edbc112 + 736
10  isar_flutter_libs             	0x000000010a75b494 isar_instance_create + 1028
11  isar_flutter_libs             	0x000000010a73f504 _$LT$F$u20$as$u20$threadpool..FnBox$GT$::call_box::hcbf6df1e100ade07 + 60
12  isar_flutter_libs             	0x000000010a7cfbe4 std::sys_common::backtrace::__rust_begin_short_backtrace::hdb41e98604887671 + 4364
13  isar_flutter_libs             	0x000000010a7ce854 core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::h8fa6c9cf16cfd721 + 196
14  isar_flutter_libs             	0x000000010a7ce350 _$LT$alloc..boxed..Box$LT$F$C$A$GT$$u20$as$u20$core..ops..function..FnOnce$LT$Args$GT$$GT$::call_once::h41c5eddec8d05b6a + 12 (boxed.rs:1935)
15  isar_flutter_libs             	0x000000010a7ce350 _$LT$alloc..boxed..Box$LT$F$C$A$GT$$u20$as$u20$core..ops..function..FnOnce$LT$Args$GT$$GT$::call_once::hc63e63e8bd0a819d + 16 (boxed.rs:1935)
16  isar_flutter_libs             	0x000000010a7ce350 std::sys::unix::thread::Thread::new::thread_start::h9881401f140304fe + 36 (thread.rs:108)
17  libsystem_pthread.dylib       	0x00000001dbf9a348 _pthread_start + 116 (pthread.c:891)
18  libsystem_pthread.dylib       	0x00000001dbf98948 thread_start + 8 (:-1)

[x] I searched for similar issues already
[x] I filled the details section with the exact device model and version
[x] I am able to provide a reproducible example

Thank you @JimmyTai for opening this. We've also started experiencing it on random devices. Latest is an iPad per below.
Hardware Model:      iPad11,6
Process:             Runner [40416]
Path:                /private/var/containers/Bundle/Application/2C00AA32-8098-47EE-B2AD-8E98ED968B0E/Runner.app/Runner
AppVariant:          1:iPad11,6:16
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
OS Version:          iPhone OS 16.2 (20C65)

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread:  26

Thread 26 name:
Thread 26 Crashed:
0   libsystem_kernel.dylib        	0x0000000217661160 __pthread_kill + 8 (:-1)
1   libsystem_pthread.dylib       	0x0000000227cbc1ac pthread_kill + 268 (pthread.c:1670)
2   libsystem_c.dylib             	0x00000001e1c6c3e4 __abort + 128 (abort.c:155)
3   libsystem_c.dylib             	0x00000001e1c14c98 abort + 192 (abort.c:126)
4   libsystem_malloc.dylib        	0x00000001e8a77e2c malloc_vreport + 908 (malloc_printf.c:220)
5   libsystem_malloc.dylib        	0x00000001e8a78010 malloc_report + 64 (malloc_printf.c:229)
6   libsystem_malloc.dylib        	0x00000001e8a73a34 find_zone_and_free + 308 (malloc.c:2155)
7   isar_flutter_libs             	0x00000001069ce56c env_close + 140
8   isar_flutter_libs             	0x00000001069cc2c8 mdbx_env_open + 1680
9   isar_flutter_libs             	0x0000000106950480 isar_core::instance::IsarInstance::open_internal::h5dfcafd44edbc112 + 736
10  isar_flutter_libs             	0x000000010692b2a0 isar_instance_create + 1028
11  isar_flutter_libs             	0x000000010690f310 _$LT$F$u20$as$u20$threadpool..FnBox$GT$::call_box::hcbf6df1e100ade07 + 60
12  isar_flutter_libs             	0x000000010699f9f0 std::sys_common::backtrace::__rust_begin_short_backtrace::hdb41e98604887671 + 4364
13  isar_flutter_libs             	0x000000010699e660 core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::h8fa6c9cf16cfd721 + 196
14  isar_flutter_libs             	0x000000010699e15c _$LT$alloc..boxed..Box$LT$F$C$A$GT$$u20$as$u20$core..ops..function..FnOnce$LT$Args$GT$$GT$::call_once::h41c5eddec8d05b6a + 12 (boxed.rs:1935)
15  isar_flutter_libs             	0x000000010699e15c _$LT$alloc..boxed..Box$LT$F$C$A$GT$$u20$as$u20$core..ops..function..FnOnce$LT$Args$GT$$GT$::call_once::hc63e63e8bd0a819d + 16 (boxed.rs:1935)
16  isar_flutter_libs             	0x000000010699e15c std::sys::unix::thread::Thread::new::thread_start::h9881401f140304fe + 36 (thread.rs:108)
17  libsystem_pthread.dylib       	0x0000000227cb66cc _pthread_start + 148 (pthread.c:893)
18  libsystem_pthread.dylib       	0x0000000227cb5ba4 thread_start + 8 (:-1)

It happens "randomly" on app launch, so we're thinking it may have to do with leftovers from a prior session or something. Opening it a second time right after a startup crash starts the app normally in 99% of cases. It's a bit bizarre.

Hello,
It may be similar to https://github.com/isar/isar/issues/915

Seems like it, thanks for the pointer!

Setting memory limit to 256M per #915 fixed it for us. 3.0.6-dev didn't fix it previously.

I have the issue on my iPhone X with iOS 16. It seems the bug is related to older devices.

Due to this issue, we fallback whole local storage system back to Hive on our production App temporary. Thanks for isar team's hard working. Hope we could have a stable version recently. Then we will come back to isar again.
It seems this issue is a duplicate of #915, I should close this issue and discuss further in #915.


[google_maps_flutter] Support for containsLocation() - Check if coordinate is within a Polygon

Hi
I have a set of polygons covering different areas of a GoogleMap.
How can I check if a given coordinate is within a polygon?
I believe some GoogleMaps api's have a containsLocation() to do this, but I can't find it for google_maps_flutter.
Is it available? Will it be implemented?
Or does someone have an alternative way of doing this in Flutter?
Thanks

Hi, if the native Google maps api contains this function please make a feature request issue to add it to the Flutter package.
Is best to ask questions like this on stackoverflow as we can't give individual support here

I have created a package from the original Google Maps Utils for Android of the most used 3 classes, MathUtil, SphericalUtil and PolyUtil
https://github.com/KohlsAdrian/google_maps_utils/issues/1
I am trying to find the solution for this issue, can't fix the original code to dart, as dart related compiler issue (double data type calculation issue, maybe)
If someone could help me, my package is still the best progress for implementing google maps utils for Flutter


Example using Containerfile / bootc / systemd

I should be able to turn on my container and "replicate" the same environment as if I was converting to a bootable image.
See: https://github.com/johwes/bootc-quarkus-optaplanner/blob/main/Containerfile.systemd

Added notes:
We should have a small tutorial how we could "create a bootable OS that runs a single container on startup" kind of system.
So that we can showcase a http server demo / small demo with a real-world container.


⚠ ClamAV has degraded performance

In 63a3942, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 182 ms

Resolved: ClamAV performance has improved in df642c0.


outlined text field caused overflow

What RMWC Version are you using [major.minor.patch]:
4.0.6

Name your build system [Webpack, Rollup...]:
vanilla create-react-app, webpack

Describe the bug with as much detail as possible:
textfield outlined caused overflow when used inside flexbox inside flexbox

What happened, and what was supposed to happen:
should not overflow

checkout the sandbox
https://codesandbox.io/s/n5xwymmz0j

workaround
using rmwc@next solve the problem
but damn I'm using typescript so I got typed definition issue
my current workaround is using overflow: hidden;

Related to #380
This is a very strange bug indeed. A few things:

This bug is likely caused upstream by material-components-web and is not something that can be easily fixed in RMWC
In the latest version of material-components-web, they have changed the implementation of the notched outline.
Timing wise, RMWC is getting a major upgrade and refactor for the 5.x branch. This is the branch that also happens to include the latest version of material-components-web (0.43.0). The 4.x branch of RMWC will not be receiving this upgrade.
Thank you for testing out the 5.x branch. I would love to know what the type definition issues you're running into are so I can fix them
Pending upgrading to 5.x, your workaround is probably the best path forward.

Fixed with the release of V5


how to run examples of ollama

Traceback (most recent call last):
  File "/data/projects/stanford-oval/storm/examples/run_storm_wiki_ollama.py", line 25, in <module>
    from lm import OllamaClient
ModuleNotFoundError: No module named 'lm'

where can I find the source of src?
import os
import sys
from argparse import ArgumentParser

from dspy import Example

sys.path.append('./src')
from lm import OllamaClient
from rm import YouRM, BingSearch
from storm_wiki.engine import STORMWikiRunnerArguments, STORMWikiRunner, STORMWikiLMConfigs
from utils import load_api_key

I was able to use ollama https://github.com/jaigouk/storm_wiki/blob/main/util/storm_runner.py#L132

close as resolved


Build nagios payload more dynamically

We included fields in the payload that are going to be None, let's
remove them.

This payload is a bit fragile. (I've done some previous work on this check) Let's chat offline :smile:


Fix file separator errors

I had a double separator between the temp dir path and the name of the file. This commit fixes the problem.
Moreover, it's better to avoid keeping folder without the / at the end (imho), and use os.path.join to create path instead of %s/%s

LGTM.


Bicep documentation for 'Microsoft.Insights/diagnosticSettings@2021-05-01-preview' is missing

Please add documentation on how to add this kind of a resource with a Bicep or ARM template.
Most resources in Azure have a way to view as JSON but this particular kind of resource seems impossible or very hard to find the json for and the documentation doesn't seem to indicate how to do it. Its a gap in my infrastructure as code so far and I can't seem to figure out how to create the diagnostic settings via bicep.

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

ID: 89743709-c3fa-9ce1-55fb-e9b7f6d2dba9
Version Independent ID: a4c9f0b7-5dde-d60c-1110-3ca53d904d61
Content: Diagnostic settings in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/essentials/diagnostic-settings.md
Service: azure-monitor
Sub-service: essentials
GitHub Login: @rboucher
Microsoft Alias: robb

@justinmchase Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Work item #51263 created for this issue.

Tracking internally.  Closing issue for now.  Thanks for the input @justinmchase .   #please-close


Implement OIDC protocol on top oauth2 for secure authentication

Feature Description
Currently, we are just authorizing users using oauth2, but open id lets us authenticate users more securely on top of oauth2
Describe the solution you'd like
Check the following video on how it works
youtube.com/watch?v=996OiexHze0
Describe alternatives you've considered

Additional context

Use https://github.com/lyokato/goidc


merge meta repository with backend repository

also, update some Readme's

does I need to do any other steps to get merge ?
@ryjones
https://github.com/ryjones


Review the tooltips on the liquidity view

The Chore
A few of these are outdated or not that clear.  Needs a review.
Tasks

[x] Write new ones
[x] Get Candida to review
[ ] Add them to the code
[ ] Swap Adjusted stake and Share columns

Additional details / background info
Adjusted stake

The effective stake of the liquidity provider, adjusted for length of commitment and impact on equity like share.

Live liquidity score

The liquidity score of the provider, used to determine allocation of fees to the best performing LPs.  Posting volume closer to the mid on both sides of the book will improve this score.

Last time on book

Fraction of time on the book at the end of the last epoch.

Last fee penalty

Penalty applied on the fees a liquidity provider collected in the last epoch. This number increases if an LP did not meet the SLA, or if they met it but other LPs outscored them in the previous epoch.

Last bond penalty (do we need to keep given this has been set to zero now?)

Penalty applied on a provider's bond penalty at the end of the last epoch. This percentage increased if an LP: had a shortfall and their bond needs to be used to cover it, did not meet the SLA, and/or reduced their commitment to the point that the market was below its target stake.

This is ready to go @MadalinaRaicu so whenever you're ready


Follow having problem loading ECW with 12-02-2011 release

This issue was imported from CodePlex
geofran80 wrote 2011-02-15 at 17:51
In the last release using the X86 binaries I follow having problem loading big ECW images up to 100 MB.
Is there anyother form to load this images? I have a memory exception relate this. Is possible to load it using pyramids?
Thanks in advanced.
PD. I will try to upload the file tomorrow if you like to try it.
Francisco J.
jirikadlec2 wrote 2011-02-16 at 02:36
Did the ECW file work with the previous release (15-12-2010) ?
geofran80 wrote 2011-02-16 at 09:12
Not, it doesn't work in any version.
I will try to upload in some minutes and send you the link.
Thanks.
Francisco J.
geofran80 wrote 2011-02-16 at 09:34
Here you have the sample ECW image file:
http://www.megaupload.com/?d=M9WT0U7V
Thanks in advanced.
Francisco J.
geofran80 wrote 2011-02-23 at 19:13
Dear friends,
Has someone tried loading the image that I upload to the server?
Thanks in advanced.
Francisco J.
geofran80 wrote 2011-04-06 at 00:17
Friends, any notice about this issue?
Thanks in advanced.
Francisco J.

Duplicate of #440


[Bug]: PointAnnotation onTap logic is incorrect

### Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
iOS
@rnmapbox/maps version
10.0.15
Standalone component to reproduce
import React from 'react';
import {
  MapView,
  ShapeSource,
  LineLayer,
  Camera,
} from '@rnmapbox/maps';

const aLine = {
  type: 'LineString',
  coordinates: [
    [-74.00597, 40.71427],
    [-74.00697, 40.71527],
  ],
};

class BugReportExample extends React.Component {
  render() {
    return (
      <MapView style={{flex: 1}}>
        <Camera centerCoordinate={[-74.00597, 40.71427]} zoomLevel={14} />
        <ShapeSource id="idStreetLayer" shape={aLine}>
          <LineLayer id="idStreetLayer" />
        </ShapeSource>
      </MapView>
    );
  }
}

Observed behavior and steps to reproduce

tap annotation 1, fires event a_1_selected
tap on annotation 1 again, fires events a_1_deselected & a_1_selected
tap on annotation 2, fires events a2_deselected & a2_selected

Expected behavior

tap annotation 1, fires event a_1_selected
tap on annotation 1 again, fires event a_1_deselected
tap on annotation 1 again, fires event a_1_selected
tap on annotation 2, fires events a1_deselected & a2_selected

Notes / preliminary analysis
Android has the correct behavior. iOS used to have the correct behavior too but it's broken.
Here's my fix:

class PointAnnotationManager : AnnotationInteractionDelegate {
  weak var selected : RCTMGLPointAnnotation? = nil
  private var draggedAnnotation: PointAnnotation?
  var lastSelectedGeojson: Feature?

  func annotationManager(_ manager: AnnotationManager, didDetectTappedAnnotations annotations: [Annotation]) {
    // We handle taps ourselfs
    //   onTap(annotations: annotations)
  }

  func onTap(annotations: [Annotation]) {
    guard annotations.count > 0 else {
      fatalError("didDetectTappedAnnotations: No annotations found")
    }

    for annotation in annotations {
      if let pointAnnotation = annotation as? PointAnnotation,
         let userInfo = pointAnnotation.userInfo {

        if let rctmglPointAnnotation = userInfo[RCTMGLPointAnnotation.key] as? WeakRef<RCTMGLPointAnnotation> {
          if let pt = rctmglPointAnnotation.object {
            let position = pt.superview?.convert(pt.layer.position, to: nil)
            let location = pt.map?.mapboxMap.coordinate(for: position!)
            var geojson = Feature(geometry: .point(Point(location!)))
            geojson.identifier = .string(pt.id)
            geojson.properties = [
              "screenPointX": .number(Double(position!.x)),
              "screenPointY": .number(Double(position!.y))
            ]
            if pt != selected {
              // If the current annotation is not the selected one, trigger deselect for the current selection
              if let selected = selected {
                guard let onDeselected = selected.onDeselected else {
                  return
                }
                let deselectEvent = RCTMGLEvent(type: .tap, payload: logged("doHandleDeselect") { try? lastSelectedGeojson?.toJSON() ?? [:] })
                onDeselected(deselectEvent.toJSON())
                selected.onDeselect()
                self.selected = nil // Reset selected to nil after deselection
              }

              // Store the geojson of the last selected annotation
              lastSelectedGeojson = geojson

              // Then, proceed to handle the select event for the new annotation
              guard let onSelected = pt.onSelected else {
                return
              }
              let selectEvent = RCTMGLEvent(type: .tap, payload: logged("doHandleSelect") { try geojson.toJSON() })
              onSelected(selectEvent.toJSON())
              pt.onSelect()
              selected = pt
            }
          }
        }
      }
    }
  }
}

Additional links and references
No response

@aimroboticsbying thanks much, can you add an example or point to an example that reproduces the issue? I don't see PointAnnotation in the current example. Also can you open a PR with the proposed fix?

@mfazekas sorry, I didn't get a chance to get back to you yet. I just saw you fixed it and it seems to be much better solution. Thanks.


nim: fix nim mangling patch

Things done
The extra mangling of modules added by extra-mangling.patch and extra-mangling-2.patch was also mangling the extension which means when nim did a lookup for the file name to generate the compile cmd there was a mismatch with the mangled extension being avz instead of nim.
To fix this, I modified the rot13 proc to only mangle up to the .nim.
Closes #356524

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 357711

x86_64-linux

:x: 2 packages failed to build:

nph
syndicate_utils

:white_check_mark: 33 packages built:

balls
base45
c2nim
chawan
emocli
eriscmd
eriscmd.bin
hottext
min
mosdepth
nim
nim-1_0
nim-2_0
nim-atlas
nim-unwrapped
nim-unwrapped-1
nim-unwrapped-2_0
nim_builder
nim_lk
nimble
nimdow
nimlangserver
nimlsp
nimmm
nitch
nitter
nrpl
promexplorer
snekim
swaycwd
tridactyl-native
ttop
vimPlugins.fruzzy

nph should be fixed by https://github.com/NixOS/nixpkgs/pull/357703
syndicate_utils fails to build on master

Thanks! I was wondering what the ".avz" extension meant.

@daylinmorgan I support making the mangling less aggressive if it can still still trick the Nix store path dependency detection.


Pairs of reactions with identical stoichiometry but different GPRs

Not sure if I should check the references to see if this reaction should be reversible or if we can assume that it is reversible and remove the irreversible one, like nearly all NAD(H)-dependent reactions seem to be:

[x] MAR03933: formylglutathione [c] + H+ [c] + NADH [c] <=> hydroxymethylglutathione [c] + NAD+ [c], GPR: ENSG00000197894
MAR20045: hydroxymethylglutathione [c] + NAD+ [c] --> formylglutathione [c] + H+ [c] + NADH [c], GPR: ENSG00000197894

In addition to figuring out whether or not ENSG00000197763 should be in this GPR, these should probably be merged into a single reversible reaction:

[x] MAR08482: H+ [m] + NADPH [m] + oxidized thioredoxin [m] --> NADP+ [m] + thioredoxin [m], GPR: ENSG00000184470 or ENSG00000197763 or ENSG00000198431
MAR02358: NADP+ [m] + thioredoxin [m] --> H+ [m] + NADPH [m] + oxidized thioredoxin [m], GPR: ENSG00000184470 or ENSG00000198431

These have one GPR that is fully contained within the other; haven't looked into any to determine whether the longer or shorter GPR seems more accurate/justified

[x] MAR03984: 2.0 H2O2 [x] --> 2.0 H2O [x] + O2 [x], GPR: ENSG00000121691 or ENSG00000166016
MAR20066: 2.0 H2O2 [x] --> 2.0 H2O [x] + O2 [x], GPR: ENSG00000121691

[x] MAR04521: glucose-6-phosphate [r] + H2O [r] --> glucose [r] + Pi [r], GPR: ENSG00000131482 or ENSG00000141349 or ENSG00000152254
MAR20020: glucose-6-phosphate [r] + H2O [r] --> glucose [r] + Pi [r], GPR: ENSG00000131482 or ENSG00000141349

[x] MAR06631: NAD+ [c] + retinol [c] --> H+ [c] + NADH [c] + retinal [c], GPR: ENSG00000025423 or ENSG00000135437 or ENSG00000147576 or ENSG00000170786 or ENSG00000172955 or ENSG00000187758 or ENSG00000196344 or ENSG00000196616 or ENSG00000197894 or ENSG00000198099 or ENSG00000248144
MAR20002: NAD+ [c] + retinol [c] --> H+ [c] + NADH [c] + retinal [c], GPR: ENSG00000198099 or ENSG00000196616

The longer GPR does not fully contain the shorter one, and I haven't looked up any of the genes to figure out what the situation is yet:

[ ] MAR00025: MAM01268n -> MAM01268c, GPR: ENSG00000065833 or ENSG00000105398 or ENSG00000112972 or ENSG00000130304 or ENSG00000139278 or ENSG00000143344 or ENSG00000147872 or ENSG00000170485 or ENSG00000198431
MAR00030: MAM01286c -> MAM01286n, GPR: ENSG00000004799 or ENSG00000005471 or ENSG00000072310 or ENSG00000099194 or ENSG00000100979 or ENSG00000105398 or ENSG00000110090 or ENSG00000113790 or ENSG00000117054 or ENSG00000118137 or ENSG00000130304 or ENSG00000134240 or ENSG00000134824 or ENSG00000135218 or ENSG00000138823 or ENSG00000147872 or ENSG00000149485 or ENSG00000151726 or ENSG00000156096 or ENSG00000157184 or ENSG00000158874 or ENSG00000161533 or ENSG00000163586 or ENSG00000165029 or ENSG00000166819 or ENSG00000166821 or ENSG00000167114 or ENSG00000167588 or ENSG00000167772 or ENSG00000169710 or ENSG00000175445 or ENSG00000177666 or ENSG00000185000 or ENSG00000187048 or ENSG00000278540

All of these except the last one were found by the Python code in #562

Nice!  Please go ahead and make changes. I suggest to remove MAR20045, MAR02358, MAR20066, MAR20020, MAR20002 by a separate PR.
As for the last one, the GPR need to be doubled checked.
This is not a conventional metabolic rxn, it is difficult to decide wether the gene is associated with this rxn.
but for sure ENSG00000065833  is not this function
ENSG00000112972
ENSG00000198431

It looks like the only other reaction MAM01286n can participate in is MAR00024, which irreversibly produces it, so we could also just remove MAR00030 and leave MAR00025 as-is (irreversible transport from [n] to [c]) since, unless someone adds some other reactions that can consume MAM01286n, there's no reason for there to be a [c] to [n] transport reaction. I'm leaning towards removing MAR00030 instead of looking through all of the genes associated with MAR00030 since, as you said, it's not really clear how to tell which genes should or shouldn't be there

all duplicate pairs reported seem to be reasonable, except the last one MAR00025 versus MAR00030. They apparently are not duplicate to each other.

It looks like the only other reaction MAM01286n can participate in is MAR00024, which irreversibly produces it, so we could also just remove MAR00030 and leave MAR00025 as-is (irreversible transport from [n] to [c]) since, unless someone adds some other reactions that can consume MAM01286n, there's no reason for there to be a [c] to [n] transport reaction.

This is speculation purely based on current model, without literature- or annotation-based evidence. Is there any paper that describes transportation direction or mechanism of MAM01268n?

I'm leaning towards removing MAR00030 instead of looking through all of the genes associated with MAR00030 since, as you said, it's not really clear how to tell which genes should or shouldn't be there

removing MAR00030 would lead to deletion of ENSG00000072310, ENSG00000100979, ENSG00000138823. The first one ENSG00000138823 is regulatory transcription factor involving into cholesterol biosynthesis and lipid metabolism, while the last two are transporters with a bunch of substrates, of which if any is related to MAM01268n?

MAM01286n is named "activation-ppara", which I assume means it represents the active, ligand-bound form of Peroxisome Proliferator Alpha, a transcription factor. In some sense, a [c] -> [n] transport reaction would be a reasonable representation of the fact that it's first translated on a cytosolic ribosome (like all proteins) and must subsequently be imported into the nucleus before it can do its job as a transcription factor, but, as I mentioned earlier, there aren't any "reactions" that represent its role as a transcription factor in the nucleus (only its binding to ligands), since this is a model of metabolism and not transcriptional regulation. As far as I can tell, there's no reason to believe that it can be exported from nuclei (I can find zero papers that mention nuclear transport of PPARA in either direction), and I assume that was only added in to give it a connection to the exchange reaction for MAM01286e so that people could model activation of PPARA by the various metabolites that can activate it.

MAM01286n is named "activation-ppara", which I assume means it represents the active, ligand-bound form of Peroxisome Proliferator Alpha, a transcription factor. In some sense, a [c] -> [n] transport reaction would be a reasonable representation of the fact that it's first translated on a cytosolic ribosome (like nearly all proteins) and must subsequently be imported into the nucleus before it can do its job as a transcription factor

good summary

As far as I can tell, there's no reason to believe that it can be exported from nuclei (I can find zero papers that mention nuclear transport of PPARA in either direction), and I assume that was only added in to give it a connection to the exchange reaction for MAM01286e so that people could model activation of PPARA by the various metabolites that can activate it.

this transport reaction from nuclei bring activated PPARA into cytosol, from which it is further transported into various compartments where however story ends and no follow-ups

but, as I mentioned earlier, there aren't any "reactions" that represent its role as a transcription factor in the nucleus (only its binding to ligands), since this is a model of metabolism and not transcriptional regulation.

make sense, what if just remove the "reactions" related this transcription factor?

removing all reactions involving "activation-ppara" or PPARA would remove:

MAR00024: PPARA [n] + fatty acid-ligands [n] ⇒ activation-ppara [n]
MAR00025: activation-ppara [n] ⇒ activation-ppara [c]
MAR00030: activation-ppara [c] ⇒ activation-ppara [n]
MAR00026: activation-ppara [c] ⇒ activation-ppara [r]
MAR00027: activation-ppara [c] ⇒ activation-ppara [m]
MAR00028: activation-ppara [c] ⇒ activation-ppara [x]
MAR00029: activation-ppara [c] ⇒ activation-ppara [e]
MAR13064: activation-ppara [e] ⇔
MAR05289: 467 ATP [l] + 934 H2O [l] + PPARA [l] ⇒ 467 ADP [l] + 476 H+ [l] + 467 Pi [l] + 31 alanine [l] + 19 arginine [l] + 19 asparagine [l] + 27 aspartate [l] + 19 cysteine [l] + 34 glutamate [l] + 16 glutamine [l] + 28 glycine [l] + 13 histidine [l] + 29 isoleucine [l] + 47 leucine [l] + 33 lysine [l] + 15 methionine [l] + 22 phenylalanine [l] + 20 proline [l] + 37 serine [l] + 18 threonine [l] + 14 tyrosine [l] + 27 valine [l]

Ok yea while putting together that list I noticed that there are a bunch of random genes associated with those transport reactions that are absolutely not responsible for transporting proteins across intracellular membranes (e.g. ACOX1 and ACADM, fatty acid oxidation enzymes, and ME1, malic enzyme), so they all seem just as questionable as MAR00030 and MAR00025. Also the two PPARA metabolites (MAM02757l and MAM02757n) could only be consumed and never produced, so this whole pathway was completely non-functional

thanks for the listing that helps a lot!

Should I open a separate PR to remove all of these PPARA-related reactions, or add that on to https://github.com/SysBioChalmers/Human-GEM/pull/657?

would lean toward letting #657 go first, because not sure about MAR05289. @JonathanRob any clue about this reaction, would it be okay to remove it?

In addition to figuring out whether or not ENSG00000197763 should be in this GPR, these should probably be merged into a single reversible reaction:
MAR08482: H+ [m] + NADPH [m] + oxidized thioredoxin [m] --> NADP+ [m] + thioredoxin [m], GPR: ENSG00000184470 or ENSG00000197763 or ENSG00000198431
MAR02358: NADP+ [m] + thioredoxin [m] --> H+ [m] + NADPH [m] + oxidized thioredoxin [m], GPR: ENSG00000184470 or ENSG00000198431

based on the catalytic activity of ENSG00000184470, ENSG00000197763, and ENSG00000198431, they all irreversibly catalyze toward oxidized NADP+. So MAR08482 should be in its original way and just remove MAR02358.
Additionally, only ENSG00000184470 should be kept given its localization, while the other two should be for MAR03931 which is the cytosolic version of MAR08482 and now has the same GPR with the 3 genes.

yep it looks like all three of those enzymes can reduce but not oxidize thioredoxin, ENSG00000184470 is localized to mitochondria, and both ENSG00000197763 and ENSG00000198431 are not localized to mitochondria

thanks, the changes were just made to #657
should there also be a separate PR about that? at this point I'm maybe thinking I should just close https://github.com/SysBioChalmers/Human-GEM/pull/657 altogether, since it seems like each one of these pairs maybe has a distinct issue going on
or just merge it, the others are just pure duplicate pairs

oh yea I didn't see that you were making those changes while I was typing that comment; if you think #657 is ok to merge now, that's fine by me

Addressed by #657 and #678


Fix paths on Windows.

Use path.posix to make sure the paths are consistent across all OS. This fixes tests on Windows.

Hmmm, it seems path.posix was added in node.js 0.12. How do you want me to proceed? I could do it manually but this seems much cleaner.

Added a manual way of dealing with this. Let me know if you want this squashed or not.

Updated.


UI from standalone image does not work

UI from all-in-one image fails to start.
docker run -it --rm --network=host jaegertracing/all-in-one

Stack trace from browser:
main.7c74e600.js:2 Uncaught Error: React.PropTypes type checking code is stripped in production.
    at r (main.7c74e600.js:2)
    at Object.r (main.7c74e600.js:59)
    at Object.<anonymous> (main.7c74e600.js:45)
    at t (main.7c74e600.js:1)
    at Object.<anonymous> (main.7c74e600.js:45)
    at t (main.7c74e600.js:1)
    at Object.<anonymous> (main.7c74e600.js:25)
    at t (main.7c74e600.js:1)
    at Object.<anonymous> (main.7c74e600.js:45)
    at t (main.7c74e600.js:1)

#95

Try pulling the latest image and run it with:
docker run -d --rm -p5775:5775/udp -p16686:16686 jaegertracing/all-in-one:latest
There's a couple of port issues we're dealing with but the UI and the stand-alone should be working.

Feel free to reopen if the UI still isn't working.


clamav: 1.1.0 -> 1.2.0

Description of changes
Updates clamav to the latest version.
Homepage: https://www.clamav.net/
Things done
Version update

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/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Release notes: https://blog.clamav.net/2023/08/clamav-120-feature-version-and-111-102.html
Should probably also update to 1.1.2 on release-23.05

Build failing for me on macos 10.15:
In file included from /tmp/nix-build-clamav-1.2.0.drv-0/clamav-1.2.0/libclamav/cache.c:34:
/nix/store/sq9w5y029sl08x2v7f42qldz5yvjarap-Libsystem-1238.60.2/include/math.h:163:58: error: expected ')'
        static __inline__  int __inline_isfinitef       (float      ) __MATH_H_ALWAYS_INLINE__;
                                                                      ^
/nix/store/sq9w5y029sl08x2v7f42qldz5yvjarap-Libsystem-1238.60.2/include/math.h:67:55: note: expanded from macro '__MATH_H_ALWAYS_INLINE__'
    #define __MATH_H_ALWAYS_INLINE__            __attribute__ ((always_inline))
                                                                ^
/tmp/nix-build-clamav-1.2.0.drv-0/clamav-1.2.0/libclamav/others.h:876:30: note: expanded from macro 'always_inline'
#define always_inline inline __attribute__((always_inline))
                             ^

Holup. Have we just knowingly broken this for macos x86_64?

I thought this was going stale and x86_64-linux with gcc+glibc is a tier 1 platform. Missed the platform notification to the @NixOS/darwin-maintainers before proceeding. UnU
https://github.com/NixOS/rfcs/blob/master/rfcs/0046-platform-support-tiers.md

Fix for the Darwin build https://github.com/NixOS/nixpkgs/pull/254843

Release notes: blog.clamav.net/2023/08/clamav-120-feature-version-and-111-102.html
Should probably also update to 1.1.2 on release-23.05

Can someone look into this? Apparently there is also a 1.0.3 release that might be more suitable.


Update DG for task command

Updated the implementations sections to include task command.

Codecov Report

Merging #108 (b21d788) into master (bd8d7db) will decrease coverage by 1.43%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #108      +/-   ##
============================================
- Coverage     51.87%   50.44%   -1.44%
  Complexity      414      414
============================================
  Files            94       96       +2
  Lines          1866     1919      +53
  Branches        221      229       +8
============================================
  Hits            968      968
- Misses          811      864      +53
  Partials         87       87

Impacted Files
Coverage Δ

...a/seedu/address/model/person/UniquePersonList.java
36.97% <0.00%> (-7.93%)
:arrow_down:

src/main/java/seedu/address/model/AddressBook.java
57.14% <0.00%> (-6.02%)
:arrow_down:

...rc/main/java/seedu/address/model/ModelManager.java
72.30% <0.00%> (-4.75%)
:arrow_down:

src/main/java/seedu/address/model/Model.java
100.00% <0.00%> (ø)

...va/seedu/address/logic/commands/AssignCommand.java
0.00% <0.00%> (ø)

...eedu/address/logic/parser/AssignCommandParser.java
0.00% <0.00%> (ø)

...person/exceptions/ModuleCodeNotFoundException.java
0.00% <0.00%> (ø)

...rson/exceptions/PartialDuplicateTaskException.java
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


test(test-plugin-ledger-connector-besu): jestify v21-sign-transaction-endpoint

Commit to be reviewed
test(test-plugin-ledger-connector-besu): jestify v21-sign-transaction-endpoint
Primary Changes
----------------
packages/cactus-test-plugin-ledger-connector-besu/src/test/typescript/
integration/plugin-validator-besu/v21-sign-transaction-endpoint.test.ts

Fixes #3565
Pull Request Requirements

[x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[x] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

[x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

PR-Commit Parity is failing to a known bug: https://github.com/hyperledger-cacti/cacti/issues/3557 (This workflow result can be skipped for evaluating PR for merge)

@outSH re-requested for review, already done with your requested changes. Thank you

@petermetz re-requested for review, already fixed the requested changes. The besu test packages are now passing. Thank you

@petermetz I have fixed the problem where the ctp-ledger-connector-besu is being skipped, and it is now passing. Re-requested for review. Thank you.


Update MAMP to 3.2.1

Current link returns a 404 error.

Thanks for noticing, but it will be necessary to update the sha256 as well.
osx-10_10:~ vagrant$ brew cask install mamp
==> Downloading http://downloads.mamp.info/MAMP-PRO/releases/3.2.1/MAMP_MAMP_PRO_3.2.1.pkg
######################################################################## 100.0%
==> Note: running "brew update" may fix sha256 checksum errors
Error: sha256 mismatch
Expected: 62d09243465007335deba5fc5a3979f0bf44695f07494216fc8fa786cdfcaf8a
Actual: 370b9b70f7b3ad7155fe84a6635366e28f277948fd15f7721b9c4aad09203a9b
File: /Library/Caches/Homebrew/mamp-3.2.1.pkg
To retry an incomplete download, remove the file above.

Fixed :)

Thanks, and can you please squash your two commits into one?

Sorry about this, I messed something up when rebasing (kind of new to using git). Will submit a new PR.

Just for the record, this was fixed on #10566


[FEAT] retrain all

A feature to retrain all matches when you have to start a new detector database from scratch but you already have a library of matches in double-take.

Hey thanks for the suggestion, I think I have something similar to this implemented.
If you select a name from the dropdown, you can then click the "sync" button which should resync/retrain all images with the current configured detectors.

Yes totally use that sync on a per person basis.
I was just look for a sync all that would sync all the people in one fell swoop.
If you think that's a benefit and are willing to include that in a future version it would be much appreciated thank you.

Maybe it is good idea to:

rename button Sync into Retrain
add extra name 'all'. If 'all' will be selected retrain and untrain should affecting all pictures. upload button should be disabled if all is selected

Yes, this would be a good addon.
I'm trying different compreface builds and need to retrain my 10 persons every time I switch. A retrain or sync all button would be ideal.

Totally agree - a sync all button would be extremely useful

So this worked for me
for i in personname personsname; do
  curl https://double-take.url/api/train/retrain/$i
  sleep 300
done

So personname is just a name in the list, if you have linux or OSX you can run this in terminal. The sleep is a 5 minute break gbetween going to the next person, you can tweak that as you see fit


Added Matrix Transpose codes

Added Matrix Transpose codes in CPP, java, and python in respective folders.

Hey @GTron-1729 you are doing awsome job 😍
You can also create issues and solve it, it will be highly appreciable if you help me make this repo a sweet spot! 😀


feat(fan): added support for gorilla fan v2

Add support for Gorilla Fan V2
This PR adds support for the Gorilla Fan V2 device to the Tuya Local integration.
Changes

Added new device configuration file gorilla_fan_v2.yaml defining the DPS mappings and entities for the Gorilla Fan V2
Added new test class [TestGorillaFanV2](file:///Users/aj/Projects/Personal/tuya-local/tests/devices/test_gorilla_fan_v2.py#11%2C7-11%2C7) in test_gorilla_fan_v2.py to test the specific functionality of the Gorilla Fan V2, including:

Testing supported features (preset modes, set speed)
Testing preset mode mapping
Testing preset mode setting
Testing fan speed percentage mapping
Testing fan speed setting in normal and boost modes
Testing that setting speed to 0 turns off the fan

Added new test case [test_init_entry_for_gorilla_fan_v2](file:///Users/aj/Projects/Personal/tuya-local/tests/test_fan.py#125%2C11-125%2C11) in test_fan.py to test the initialization of the [TuyaLocalFan](file:///Users/aj/Projects/Personal/tuya-local/tests/test_fan.py#14%2C46-14%2C46) entity specifically for the "gorilla_fan_v2" device type

Testing

Manually tested with a physical Gorilla Fan V2 device
Added new unit tests to verify correct configuration loading and entity initialization
All existing tests pass

Resolves: #1971

@make-all  The configurations are updated as per your recommendations. Please review my comments and changes.


editorial: move necessary AOs from Temporal

In #92, @ljharb pointed out that it's a bit odd that this proposal points to the Temporal spec, which is a Stage 3 proposal itself. Due to the high amount of interaction between Temporal.Duration and this proposal, it's somewhat inevitable, but this should be taken into account if we intend to ship this proposal before Temporal.

@ryzokuken in general, i think plenary needs to be notified if one proposal is going to be effectively blocked on another - and cribbing non-generic AOs wholesale from Temporal isn't likely to be a viable path forward.

I agree. I just wanted to consult TG2 before going to plenary about this, but most likely I think implementer feedback would point to the same conclusion.

Discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-05-19.md#editorial-move-necessary-aos-from-temporal-96
Conclusion: Decouple Intl.DurationFormat from Temporal.Duration. Make the format function only accept an options bag for now, and the Temporal proposal should change Intl.DurationFormat to make it accept strings. The exact mechanism for decoupling the proposals needs to be decided.

No longer necessary because of #98


Document breaking changes for extensions around service provider caching

See https://github.com/dotnet/efcore/issues/19152

Also see https://github.com/dotnet/efcore/pull/26111


Add template for OSD onboarding

As of MTSRE-178:

Create the Deployment manifests in the addon-operator repository. Example:
https://github.com/openshift/managed-upgrade-operator/blob/master/hack/olm-registry/olm-artifacts-template.yaml

/hold


Video support for mobile asset uploads.

Work in progress.
Related to https://github.com/curalate/pinsights-mobile/pull/159

@ksho looks good to me. I don't totally understand what's going on. Like why the deleted code in SOSPicker.m doesn't need to be replaced by a call to some new code?
Another question too... qualitatively, how does the performance feel for uploading a video? Specifically a Snapchat video? I think the iPhone SDK has some transcoding APIs that might be able to shrink video file sizes if we think we need this to make performance acceptable.

@mikeacook The deleted code in SOSPicker was doing image scaling and quality changes. I figured we could simplify it for now, and just send the URL no matter an image or video. But yes, some transcoding is a good idea. We should talk about what the expectation will be for video quality -- I imagine snapchat already compresses a bit.

@ksho how does that affect performance? I'd expect the reason that they're doing the scaling/quality changes on the URL they're returning is so that the image picker view renders very quickly when the images are huge. Is the image they're scaling only for the image picker gridview, or is it affecting the actual image that gets passed to the selected file?

@mikeacook It's affects the image that gets passed as the selected file to our API. I didn't think we'd want to compress the image twice (once in the image-picker plugin and once on our backend).

@mikeacook any thoughts on the most recent comment?

Makes sense, as long as it looks good and performs well on the device (and during upload) we should be fine. :shipit:

@mikeacook Discovered a read permission bug when using on an actual device (rather than the simulator). Fixed by copying our file to the Application sandbox https://github.com/curalate/mobile-image-picker/pull/1/commits/d286cc93a76ae80b89d1a2f9f9508817fae65ab6
Upload performance is solid, and processing feels comparable to what we get from desktop (it shouldn't vary since that's server-side).

@ksho can you squash this up so we can merge it?

@mikeacook Done.


Reactive API: Emit items during command processing

The current implementation of the reactive API awaits command completion before elements are emitted.  The API should emit elements while the results are received. This is to reduce memory usage (when loading large results) and to improve reactivity.

Support instant emission in pure collection outputs
Remove terminal synchronization for collections in ReactiveCommandDispatcher

Implemented.


Create Data Models as per the diagram

Create the tables for User, Food, Recipe & Recipe Food with their respective relations
Generate the schema file


Head shake occurs with blendshapes

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
None
OS Platform and Distribution
Windows 11
MediaPipe Tasks SDK version
0.10.9
Task name (e.g. Image classification, Gesture recognition etc.)
Face landmarker detection
Programming Language and version (e.g. C++, Python, Java)
Python
Describe the actual behavior
The 52 points given when the head is still are jitter
Describe the expected behaviour
No jitter
Standalone code/steps you may have used to try to get what you need
Use the code link:
https://developers.google.com/mediapipe/solutions/vision/face_landmarker/python#live-stream

Other info / Complete Logs
No response

Hi @xiaoshuai-tw,
Thank you for bringing this matter to our attention. Could you please provide any relevant reference images or videos that would assist us more effectively? This information will greatly contribute to our thorough understanding of the issue and will facilitate internal discussions with our team to improve overall performance.
Thank you

https://github.com/google/mediapipe/assets/82313318/74916734-8b30-4979-93a7-45aca0080d0c
This is the face_blendshapes taken from the result_callback function in the linked python code above and passed into the UE4 3D digital Man for expression clone display video.There is shaking of the brow and the position of the face and jaw.


Improve and correct documentation

Since by default, the * rule is being applied, some code examples were incorrect in code comments.
I've also added strict checking examples to the README.

Thanks! 👍


ImportError: cannot import name 'isin' from 'jax._src.numpy.lax_numpy'

Cloned repo, followed setup, ran example and got:
$ python main.py --out_dir results --config_folder configs --task semicircle
2022-08-01 12:44:45.944149: W external/org_tensorflow/tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory
2022-08-01 12:44:45.960144: W external/org_tensorflow/tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory
2022-08-01 12:44:45.961190: W external/org_tensorflow/tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory
Traceback (most recent call last):
  File "/home/USER/projects/jkonet/main.py", line 7, in <module>
    import flax
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/flax/__init__.py", line 20, in <module>
    from . import linen
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/flax/linen/__init__.py", line 20, in <module>
    from .activation import (celu, elu, gelu, glu, leaky_relu, log_sigmoid,
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/flax/linen/activation.py", line 46, in <module>
    from flax.linen.module import Module, compact
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/flax/linen/module.py", line 32, in <module>
    from jax._src.numpy.lax_numpy import isin
ImportError: cannot import name 'isin' from 'jax._src.numpy.lax_numpy' (/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/jax/_src/numpy/lax_numpy.py)

Seems to be a version problem of Flax. I suggest updating it.

@bunnech this is the version from the requirments file. What version should I use?

After running
pip install --upgrade flax

I now get
$ python main.py --out_dir results --config_folder configs --task semicircle
Traceback (most recent call last):
  File "/home/USER/projects/jkonet/main.py", line 13, in <module>
    import wandb
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/wandb/__init__.py", line 27, in <module>
    from wandb import sdk as wandb_sdk
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/wandb/sdk/__init__.py", line 9, in <module>
    from .wandb_init import _attach, init  # noqa: F401
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/wandb/sdk/wandb_init.py", line 31, in <module>
    from .backend.backend import Backend
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/wandb/sdk/backend/backend.py", line 21, in <module>
    from ..interface.interface import InterfaceBase
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/wandb/sdk/interface/interface.py", line 21, in <module>
    from wandb.proto import wandb_internal_pb2 as pb
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/wandb/proto/wandb_internal_pb2.py", line 15, in <module>
    from wandb.proto import wandb_base_pb2 as wandb_dot_proto_dot_wandb__base__pb2
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/wandb/proto/wandb_base_pb2.py", line 36, in <module>
    _descriptor.FieldDescriptor(
  File "/home/USER/anaconda3/envs/jko/lib/python3.9/site-packages/google/protobuf/descriptor.py", line 560, in __new__
    _message.Message._CheckCalledFromGeneratedFile()
TypeError: Descriptors cannot not be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
 1. Downgrade the protobuf package to 3.20.x or lower.
 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).

More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates


fix: ensure that profiling does not lowercase columns

This PR resolves: Profiling shows duplicate column names for Snowflake and CLOUD-2123
This PR implements the following changes:

Remove the line column_name = column_name.lower() from here
Creates a new test table that has a capitalised column name in it
Add a new unit tests that ensures that the running the profiling on the new test table returns the capitalised version (if the database does not make the columns lowercase)
For unit tests that test column profiling, we now base the expected output on the way the datasource type handles lower/upper-case columns. Setting the expected output based on the datasource is currently done in the unit tests themselves. This seemed like the best approach as it's just a few lines of code and does not seem to warrant a separate fixture/expected output file.

@bastienboutonnet In profiling we also lowercase the table names, see here and here, but it seems that that is the intended behaviour (I checked and core actually does the same when it returns the table names here).

@bastienboutonnet In profiling we also lowercase the table names, see here and here, but it seems that that is the intended behaviour (I checked and core actually does the same when it returns the table names here).

and yes no need to change anything about tables at this point as it behaves as intended and I'm 99% sure matching on cloud is case-insensitive for those.


bug：_knownMappings[typeID] == false alway is true

in android platform ,haxe 3.4 with new hxcpp and lime.
when _knownMappings[typeID] = some other instance,
_knownMappings[typeID] == false alway is true .replace by a real instance to fix the bug.

oh,sorry ,i found the bug is the same as https://github.com/robotlegs/openfl-robotlegs-framework/pull/13

Thanks for pointing this out. This has now been resolved and is available in 0.4.2 on Haxelib


Please add documentation for the --chown flag to COPY/ADD

File: engine/reference/builder.md, CC @mistyhacks
Per release 17.09, the ADD and COPY commands take a --chown flag to set the user/group: https://github.com/moby/moby/pull/34263
The functionality is there for sure, we just did a double-take at work today because it wasn't in the docs.

Same thing from me. Did some jumps around to avoid expensive 'RUN chown -R ' over a big directory.

This has been documented for some time. Sorry for forgetting to close here.


Does not work in qBittorrent v5.0.0

The progress bars are red and not blue. Although I like them more in red, it looks like it has some sort of error.

The green line that shows the progress is no longer there.

Those are the issues I noticed, I'll come back or make another issue if I notice any other.

The progress bars are brown for me. It might follow accent color?
(Mostly comment to follow when the green line is fixed).

In that case I'd like it if they either don't follow the Windows accent color or just have some sort of way to choose if you wanna have accent color.
By the way, you can follow a GitHub issue even without posting a comment. I don't mean to be rude by saying this, but I just thought I'd let you know.🙃

By the way, you can follow a GitHub issue even without posting a comment. I don't mean to be rude by saying this, but I just thought I'd let you know.🙃

It's okay 😉 Thanks for letting me know. I didn't notice GitHub has had a subscribe button.

In that case I'd like it if they either don't follow the Windows accent color or just have some sort of way to choose if you wanna have accent color.

Make an issue on the official Qbittorrent github page, they should add a toggle for it in the settings.

I'm hoping this repo is still maintained. I really like this theme, but the missing progress bars in qBT 5.0.0 is a deal breaker for me.

I can confirm that the Progress and Availability bars use your Windows accent colour (at least for Win 11). If you change your accent colour the bars will recolour after restarting qBittorrent.

@philkonick when i follow what you suggested, it shows up for a second and then it disappears again. win 10.

Just to clarify, I was referring to the bars in the first screenshot in the initial post, not the download progress bars in the torrents table. Those are not showing at all for me, just like the second screenshot in the initial post. Not sure if that was clear in my last comment.

Pretty sure it's not supposed to do that...

Some brave soul has just opened a pull request with a fix!

Some brave soul has just opened a pull request with a fix!

no release yet?

Some brave soul has just opened a pull request with a fix!

no release yet?
Those 4 qbtheme files are in here:
https://github.com/witalihirsch/qBitTorrent-fluent-theme/tree/main/Builds
No version for default icons tho.

Some brave soul has just opened a pull request with a fix!

no release yet?

Those 4 qbtheme files are in here: https://github.com/witalihirsch/qBitTorrent-fluent-theme/tree/main/themes
~No version for default icons tho.~ Nvm. I downloaded the code and was able to compile the defaulticons versions.

yeah i prefer old icons too. can you please upload the qbtheme file with old icons somewhere? is that a possibility?

yeah i prefer old icons too. can you please upload the qbtheme file with old icons somewhere? is that a possibility?

defaulticons-fluent.zip

yeah i prefer old icons too. can you please upload the qbtheme file with old icons somewhere? is that a possibility?

defaulticons-fluent.zip

Thank you! Although I thought you kept the old icons from the fluent theme, not the default qbittorrent icons. Like these:

Thank you! Although I thought you kept the old icons from the fluent theme, not the default qbittorrent icons. Like these: !

Ah. You meant the icons before the update with qbittorrent  5.0.
Pre-5.0-icons-fluent.zip

Thank you! Although I thought you kept the old icons from the fluent theme, not the default qbittorrent icons. Like these: !

Ah. You meant the icons before the update with qbittorrent 5.0. Pre-5.0-icons-fluent.zip

Yes! Thank you so much for doing this for me.

yeah i prefer old icons too. can you please upload the qbtheme file with old icons somewhere? is that a possibility?

defaulticons-fluent.zip

Is this same as defaulticons-fluent-dark-no-mica ? since among those 4 theme files i cant seem to find one with default icons

The Mica effect isn't working in this version from the pull request. Also the alternative tray icon isn't available anymore.


Missing constants for x86_64-unknown-linux-gnu

Latest version of cryptoki-sys does not include CKF_EC_F_2M constant and so compilation of cryptoki v0.4.1 as dependency fails.
My system:
Linux blade 6.2.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 03 Mar 2023 15:58:31 +0000 x86_64 GNU/Linux

Steps to reproduce
cargo new cryptoki-repro
cd cryptoki-repro
cargo add<EMAIL_ADDRESS>cargo build

Fails with message:
error[E0425]: cannot find value `CKF_EC_F_2M` in this scope
   --> /home/jck/.cargo/registry/src/github.com-1ecc6299db9ec823/cryptoki-0.4.1/src/mechanism/mechanism_info.rs:26:25
    |
26  |         const EC_F_2M = CKF_EC_F_2M;
    |                         ^^^^^^^^^^^ help: a constant with a similar name exists: `CKF_EC_F_P`
    |
   ::: /home/jck/.cargo/registry/src/github.com-1ecc6299db9ec823/cryptoki-sys-0.1.5/src/bindings/x86_64-unknown-linux-gnu.rs:581:1
    |
581 | pub const CKF_EC_F_P: CK_FLAGS = 1048576;
    | ------------------------------ similarly named constant `CKF_EC_F_P` defined here

error[E0425]: cannot find value `CKF_EC_ECPARAMETERS` in this scope
  --> /home/jck/.cargo/registry/src/github.com-1ecc6299db9ec823/cryptoki-0.4.1/src/mechanism/mechanism_info.rs:27:33
   |
27 |         const EC_ECPARAMETERS = CKF_EC_ECPARAMETERS;
   |                                 ^^^^^^^^^^^^^^^^^^^ not found in this scope

error[E0425]: cannot find value `CKF_ERROR_STATE` in this scope
  --> /home/jck/.cargo/registry/src/github.com-1ecc6299db9ec823/cryptoki-0.4.1/src/slot/token_info.rs:35:29
   |
35 |         const ERROR_STATE = CKF_ERROR_STATE;
   |                             ^^^^^^^^^^^^^^^ not found in this scope

For more information about this error, try `rustc --explain E0425`.
error: could not compile `cryptoki` due to 3 previous errors

I can see that latest main branch code contains those constants so perhaps all that is to be done is tagging a new version?

I can reproduce this problem. Adding generate-bindings feature does not help.
I did succeed when I used crate directly via git: cryptoki = { version = "0.4.1", git = "https://github.com/parallaxsecond/rust-cryptoki" }. Maybe recent changes in #130 helped?

I'm having the same problems. These constants disappeared in packaged pkcs11.h of<EMAIL_ADDRESS>296d295
< #define CKF_ERROR_STATE		(1UL << 24)
1048,1049d1046
< #define CKF_EC_F_2M		(1UL << 21)
< #define CKF_EC_ECPARAMETERS	(1UL << 22)

I'm having the same problem.
It seems as though there may have been error releasing or tagging.
cryptoki-0.4.1 was created on 2022-09-29.
cryptoki-0.4.0 was created on 2022-09-07.
cryptoki-0.3.0 was created on 2022-01-14.
Then, on 2023-03-15, cryptoki-0.3.1 and cryptoki-sys-0.1.5 were created on the cryptoki-0.3.0 branch.  Crates.io shows the cryptoki-sys dep for cryptoki as "^0.1.4", so cargo selects 0.1.5.
If I manually say cryptoki-sys = "=0.1.4" in my Cargo.toml, I can build.

Ok, sorry for the huge delay.
So, it seems when we branched out cryptoki-0.3.x to release Parsec back in March, we branched from the latest v0.3 of cryptoki. We made some changes to cryptoki-sys and upstreamed that as 0.1.5 - however the problem here is that we had added other stuff to cryptoki-sys since that v0.3 of cryptoki. Which means this newest version of cryptoki-sys is actually missing some stuff that is present in main.
My suggestions here are:

we bump the main version of cryptoki-sys to 0.1.6 and release that ASAP
we yank 0.1.5 of cryptoki

Apologies everyone for this mistake, it is yet another lesson in juggling the versions of two interdependent crates in the same repo :[
cc @gowthamsk-arm - I don't think this would affect Parsec in any way.

Update: I have released v0.1.6 of cryptoki-sys. I'll be yanking 0.1.5 tomorrow.

cryptoki-sys 0.1.5 doesn't seem to be yanked.

Closing as new release of cryptoki-sys were made. Re-open if not!


Private volatile props does not work with @observer

I've tried to use shared private values with MST (https://github.com/mobxjs/mobx-state-tree#volatile-state, tip 4) and found that value is stucking when I add @observer decorator.
Sandbox: https://codesandbox.io/s/824qm4qx3l
Code:
import React from "react";
import ReactDOM from "react-dom";
import { types } from "mobx-state-tree";
import { observer } from "mobx-react";

// Store
const Store = types.model({}).extend(self => {
  let localState = 1;

  return {
    views: {
      get x() {
        return localState;
      }
    },
    actions: {
      setX(value) {
        console.log("Local:before: ", localState);
        console.log("Getter:before:", self.x);
        localState = value;
        console.log("Local:after: ", localState);
        console.log("Getter:after:", self.x);
      }
    }
  };
});

// Create store
const store = Store.create();
const store2 = Store.create();

// Value
const ObservedValue = observer(({ store }) =>
Value: {store.x}
);
const DirectValue = ({ store }) =>
Value: {store.x}
;

// App
class App extends React.Component {
  state = {
    click: 0
  };

  render() {
    return (

        <button
          onClick={() => {
            store.setX(store.x + 1);
            store2.setX(store2.x + 1);
            this.setState({ click: this.state.click + 1 });
          }}
        >
          Click
        </button>
        <ObservedValue key={"obs_" + store.x} store={store} />
        <DirectValue key={"direct_" + store2.x} store={store2} />

    );
  }
}

// Render
const rootElement = document.getElementById("root");
ReactDOM.render(<App store={store} />, rootElement);

As you can see pure component is changing but observed component not.
And another thing that value getter invoke only once for observed component

https://github.com/mobxjs/mobx-state-tree#modelvolatile

https://github.com/mobxjs/mobx-state-tree#modelvolatile

Yes i know about that but I don't want the action triggers changing model.

As the doc suggests you either have to make volatile state observable manually:

In that case, in the above example, localState could have been declared as const localState = observable.box(3)

Or you can use .volatile, which does the same, but additionally exposes it as prop.

// Store
const Store = types.model({}).extend(self => {
  let localState = observable.box(1); // <---

  return {
    views: {
      get x() {
        return localState.get(); // <---
      }
    },
    actions: {
      setX(value) {
        console.log("Local:before: ", localState);
        console.log("Getter:before:", self.x);
        localState.set(value); // <---
        console.log("Local:after: ", localState);
        console.log("Getter:after:", self.x);
      }
    }
  };
});

Wait wait wait)) I know about observable volatile but I don't want to make this state observable. I found tip 4 from documentation for this purpose and it does not work.
P.S. Now i'm using .volatile as workaround but it causes extra rerender.

If the state (localState) is not observable then observer (ObservedValue) can't see it's modification...
In your example:
this.setState({ click: this.state.click + 1 });
causes App to render
ObservedValue recieves new props, but update is skipped, because observer makes the component pure and passed store stays the same.
DirectValue recieves new props, but it's not pure (it's functional thats something entirely different), therefore is updated as usual, even thought store2 stays the same.

To avoid this i'm using key prop and React always creates NEW component. So ObservedValue should call getter anytime. But it calls INTERNAL getter as closure which his copied before from original store.

You can add any observed states for this example and result will be the same.

Take a look on console and you can see that localState in store2 is not changing but setter and getter always calling.

Oh right I see it now... :) It's because the computed cache... computeds don't recalculate if they're observed by something (ObservedValue) and their (observable) dependencies does not change ....

So MST volatile TIP 4 does not work with mobx-react :) Is it possible to fix?)

I think it works as intended, just the example is a bit misleading...
Getters (computeds) shouldn't be used together with non-observable state.
You can change it to getX() {} and it should work...

I just copied this example from documentation :)

Thats the example I had in mind...
If you insist on getter, perhaps you can Object.defineProperty(self, 'x', { get() { return localState } }) not sure it thats possible/allowed in MST

Closing for inactivity

@mweststrate Consider improving mobx-state-tree docs. As noted above, the volatile state example can easily lead to buggy code:
const Todo = types.model({}).extend(self => {
    let localState = 3

    return {
        views: {
            // !!! this will turn into computed, so it won't reflect the changes of `localState` due to memoization
            get x() {
                return localState
            }
        },
        actions: {
            setX(value) {
                localState = value
            }
        }
    }
})

Good point, cc @xaviergonz
On Thu, Mar 14, 2019 at 12:59 PM urugator<EMAIL_ADDRESS>wrote:

@mweststrate https://github.com/mweststrate Consider improving
mobx-state-tree docs. As noted above, the volatile state example can
easily lead to buggy code:
const Todo = types.model({}).extend(self => {
let localState = 3
return {
    views: {
        // !!! this will turn into computed, so it won't reflect the changes of `localState` due to memoization
        get x() {
            return localState
        }
    },
    actions: {
        setX(value) {
            localState = value
        }
    }
}

})
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/620#issuecomment-472822517,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABvGhLRTEAJ60Dvfq13uJWf8fK9q_ea_ks5vWjmPgaJpZM4ZIroa
.

@mweststrate thanks, fixed via https://github.com/mobxjs/mobx-state-tree/pull/1219


Navigating to any orchestration template throws an error

Services -> Catalogs -> Orchestration Templates -> [any orchestration template]
throws the following error:
FATAL -- : Error caught: [RangeError]<PHONE_NUMBER>0006 is out of range for ActiveRecord::ConnectionAdapters::PostgreSQL::OID::Integer with limit 4
active_record/type/integer.rb:45:in `ensure_in_range'
active_record/type/integer.rb:23:in `type_cast_for_database'
active_record/connection_adapters/abstract/quoting.rb:28:in `type_cast'
active_record/connection_adapters/postgresql_adapter.rb:602:in `block in exec_cache'
active_record/connection_adapters/postgresql_adapter.rb:601:in `map'
active_record/connection_adapters/postgresql_adapter.rb:601:in `exec_cache'
active_record/connection_adapters/postgresql_adapter.rb:589:in `execute_and_clear'
active_record/connection_adapters/postgresql/database_statements.rb:160:in `exec_query'
active_record/connection_adapters/abstract/database_statements.rb:351:in `select'
active_record/connection_adapters/abstract/database_statements.rb:32:in `select_all'
active_record/connection_adapters/abstract/query_cache.rb:68:in `block in select_all'
active_record/connection_adapters/abstract/query_cache.rb:83:in `cache_sql'
active_record/connection_adapters/abstract/query_cache.rb:68:in `select_all'
active_record/querying.rb:39:in `find_by_sql'
active_record/statement_cache.rb:107:in `execute'
active_record/associations/collection_association.rb:451:in `get_records'
active_record/associations/collection_association.rb:455:in `find_target'
active_record/associations/collection_association.rb:392:in `load_target'
active_record/associations/collection_association.rb:315:in `length'
active_record/associations/collection_proxy.rb:751:in `length'
app/helpers/application_helper/toolbar_builder.rb:1059:in `build_toolbar_disable_button'
app/helpers/application_helper/toolbar_builder.rb:118:in `block (3 levels) in build_toolbar_buttons_and_xml'
app/helpers/application_helper/toolbar_builder.rb:98:in `each'
app/helpers/application_helper/toolbar_builder.rb:98:in `each_with_index'
app/helpers/application_helper/toolbar_builder.rb:98:in `block (2 levels) in build_toolbar_buttons_and_xml'
app/helpers/application_helper/toolbar_builder.rb:67:in `each'
app/helpers/application_helper/toolbar_builder.rb:67:in `block in build_toolbar_buttons_and_xml'
app/helpers/application_helper/toolbar_builder.rb:53:in `each'
app/helpers/application_helper/toolbar_builder.rb:53:in `each_with_index'
app/helpers/application_helper/toolbar_builder.rb:53:in `build_toolbar_buttons_and_xml'
app/helpers/application_helper/toolbar_builder.rb:3:in `call'
app/helpers/application_helper.rb:266:in `build_toolbar_buttons_and_xml'
app/controllers/catalog_controller.rb:1808:in `replace_right_cell'
app/controllers/catalog_controller.rb:312:in `tree_select'
app/controllers/catalog_controller.rb:303:in `x_show'

@Fryguy do you have any ideas on what may be causing this?  Thx, Dan

This appears to be resolved; cannot recreate. Please reopen the issue if it is still occurring.


[release/1.6] go.mod: Bump hcsshim to v0.9.5

This bumps hcsshim to include a bug fix from https://github.com/microsoft/hcsshim/commit/cae120b42536adea72101e6a358183c74a0bdac5.
You can see the full changelog here: https://github.com/microsoft/hcsshim/releases/tag/v0.9.5
Signed-off-by: Kathryn Baldauf<EMAIL_ADDRESS>

/ok-to-test

Looks you might need to fix vendoring in /integration/client

LGTM. But just  quick question. The change fix doesnt actually make it into containerd because the shim itself is a binary. Do we really need to take this? Or is that we use the go.mod version to determine which binary to build and thus we do need the update even the containerd vendor itself doesnt have any real code changes to speak of?

LGTM. But just quick question. The change fix doesnt actually make it into containerd because the shim itself is a binary. Do we really need to take this? Or is that we use the go.mod version to determine which binary to build and thus we do need the update even the containerd vendor itself doesnt have any real code changes to speak of?

We use the go.mod version when building the binary 🙂

Test failure looks unrelated afaict

@katiewasnothere 👍


feat(core): support allSourceTags (#768) and wildcards in check-module-boundaries.js

Addresses #768
Also adds regex and glob matching - another feature of @nx/eslint-plugin

I'm not really sure what's up with the failing e2e, I don't see the function call it's referring to??

Can you rebase the PR?

Can you rebase the PR?

After rebase I'm having issues with the git hooks - it's trying to call generate-docs and failing
C:\Users\Chris Leigh\Source\nx-dotnet [module-boundaries ↓3 ↑2]> git push -f
yarn run v1.22.17
$ ts-node ./tools/scripts/hooks/documentation.check.ts
📖 Checking for documentation changes
Error: Command failed: nx g @nx-dotnet/nxdoc:generate-docs --exclude=workspace-plugin
    at checkExecSyncError (node:child_process:885:11)
    at execSync (node:child_process:957:15)
    at Object.<anonymous> (C:\Users\Chris Leigh\Source\nx-dotnet\tools\scripts\hooks\documentation.check.ts:39:1)

Running the generator directly I see:
C:\Users\Chris Leigh\Source\nx-dotnet [module-boundaries ↓3 ↑2]> nx g @nx-dotnet/nxdoc:generate-docs --exclude=workspace-plugin --verbose

 >  NX   Failed to process project dependencies with "@nx-dotnet/core".

   Source file "demo\apps\webapi\NxDotnet.Test.Webapi.csproj" does not exist in the workspace.

   Because of the error the Nx daemon process has exited. The next Nx command is going to restart the daemon process.
   If the error persists, please run "nx reset".

Ideas?   I did yarn install following the @nrwl -> @nx changes

t the graph processing faili

@Tungsten78 I seen the comment about the graph processing failing, did you figure that out locally?

Yes, it was environment specific (yarn install related I believe).  All good, thanks for checking.


Fixes issue #354

Coverage remained the same at 81.579% when pulling 37f357b7190343553d3006ce8597ae4bdd91d514 on feature/fix into aaebde0a41ec211df69015daa46b4773df3e2aef on master.

Coverage remained the same at 81.579% when pulling 37f357b7190343553d3006ce8597ae4bdd91d514 on feature/fix into aaebde0a41ec211df69015daa46b4773df3e2aef on master.

Coverage remained the same at 81.579% when pulling 37f357b7190343553d3006ce8597ae4bdd91d514 on feature/fix into aaebde0a41ec211df69015daa46b4773df3e2aef on master.

Coverage remained the same at 81.579% when pulling 37f357b7190343553d3006ce8597ae4bdd91d514 on feature/fix into aaebde0a41ec211df69015daa46b4773df3e2aef on master.

@FinalAngel fix confirmed
Fix #354


feat(Event-Store): Add Terminate as a way of gracefully shutting down

As part of working on the PostgreSQL storage engine, I realised that for most of the engine
implementations, I would need a way to signify that the application itself is shutting down, and a
graceful shutdown is required. This could entail closing connections, draining pools, etc. Basically
perform some good-citizen duties.

:tada: This PR is included in version 1.1.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.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add one hour to minDate

Hi everyone,
I use two blocks of time picker and separately a datepicker and  a timepicker.
So i have 4 values, fromDate and fromHour then toDate and toHour.
When i modify my fromHour field, right now i set the minDate of toHour to be the value of fromHour
toHourtimepicker.data("DateTimePicker").minDate(fromHourtimepicker.val()); and format is format:            'HH:mm',
But actually i don't want it to be "fromDate" but fromDate + 1 hour. How can i do that ? is that possible directly with the library bootstrap-datetimepicker or i need to use some basic JS ?
Thanks !
cheers
Nicolas Z

Just use moment.js which is a dependency of bootstrap-datetimepicker. The syntax is .add(1, 'hours')

Ok, thank you ! i do something and it works but with moment.js it should be realy easier.


📖 Some overdue documentation updates

Summary
This PR does some catch-up on the existing document set.
Related issue(s)
Fixes #

/cc @nirrozenbaum
/cc @ezrasilvera
/cc @pdettori
/cc @clubanderson

The force-push to a80dca6fc makes some changes in response to the review above.