Settings NoAck to true causes memory leak

Contact Details
No response
Version
8.x
On which operating system(s) are you experiencing the issue?
Windows, Linux
Using which broker(s) did you encounter the issue?
RabbitMQ
What are the steps required to reproduce the issue?
As I asked here, I want to use NoAck/AutoAck feature of RabbitMQ. I went a little more deep and found a workaround but the workaround seems to cause memory leak.
The work around is setting the following flag to true;
((RabbitMqReceiveSettings)((RabbitMqReceiveEndpointConfiguration)endCfg).Settings).NoAck = true; inside ReceiveEndpoint configuration. Please check the example repo.
From your attitude I would guess that you would not see this as an issue(feel free to prove me wrong). I'm creating an issue if other people also encounters this issue. Therefore, feel free to close the issue if you do not plan fix/implement it.
Please do not hesitate to ask if you need further information.
What is the expected behavior?
The memory usage should stay normal.
What actually happened?
After couple of minutes, the memory usage keeps increasing.
Related log output, including any exceptions
No response
Link to repository that demonstrates/reproduces the issue
https://github.com/aeb-dev/mt-memory-leak

Are you able to determine which memory objects are leaking?

the output of dotnet-dump
...rest
00007ffc2c903c48   219864     31660416 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.Middleware.DeadLetterFilter+<MassTransit-IFilter<MassTransit-ReceiveContext>-Send>d__3, MassTransit]]
00007ffc2c4f86b8   440599     31723128 System.Threading.Tasks.ContinuationTaskFromTask
00007ffc2c903928   219864     33419328 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.Middleware.RescueFilter`2+<MassTransit-IFilter<TContext>-Send>d__5[[MassTransit.ReceiveContext, MassTransit.Abstractions],[MassTransit.ExceptionReceiveContext, MassTransit.Abstractions]], MassTransit]]
00007ffc2c902f60   219864     33419328 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.Middleware.DeserializeFilter+<Send>d__4, MassTransit]]
00007ffc2c902c48   219864     35178240 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.Middleware.OutputPipeFilter`2+<SendToOutput>d__9[[MassTransit.ConsumeContext, MassTransit.Abstractions],[MassTransit.ConsumeContext`1[[mt_memory_leak.TestMessage, mt-memory-leak]], MassTransit.Abstractions]], MassTransit]]
00007ffc2c6d35f0   440611     35248880 System.Collections.Generic.Dictionary`2[[System.Int64, System.Private.CoreLib],[System.Threading.Tasks.Task, System.Private.CoreLib]]
00007ffc2c263058   441096     35287680 System.Threading.Tasks.Task+ContingentProperties
00007ffc2c8a8418   220744     35319040 MassTransit.RabbitMqTransport.RabbitMqReceiveContext
00007ffc2c866310   219899     36943032 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Boolean, System.Private.CoreLib],[MassTransit.Util.ChannelExecutor+<Run>d__11`1[[System.Boolean, System.Private.CoreLib]], MassTransit]]
00007ffc2c7517d8   219899     38702224 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.RabbitMqTransport.RabbitMqSendTransportContext+<Send>d__18`1[[mt_memory_leak.TestMessage, mt-memory-leak]], MassTransit.RabbitMqTransport]]
00007ffc2c589320   219899     40461416 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.Transports.HostConfigurationRetryExtensions+<Retry>d__0, MassTransit]]
00007ffc2c900cb8   219864     42213888 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.Middleware.ConsumerMessageFilter`2+<MassTransit-IFilter<MassTransit-ConsumeContext<TMessage>>-Send>d__4[[mt_memory_leak.TestConsumer, mt-memory-leak],[mt_memory_leak.TestMessage, mt-memory-leak]], MassTransit]]
00007ffc2c8bc8c8   219864     42213888 MassTransit.Serialization.EnvelopeMessageContext
00007ffc2c752228   219899     42220608 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.Transports.SendTransport`1+SendPipe`1+<Send>d__5[[MassTransit.RabbitMqTransport.ModelContext, MassTransit.RabbitMqTransport],[mt_memory_leak.TestMessage, mt-memory-leak]], MassTransit]]
00007ffc2c9003b8   219864     43972800 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.DependencyInjection.ScopeConsumerFactory`1+<Send>d__2`1[[mt_memory_leak.TestConsumer, mt-memory-leak],[mt_memory_leak.TestMessage, mt-memory-leak]], MassTransit]]
00007ffc2c904050   219864     45731712 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.Transports.ReceivePipeDispatcher+<Dispatch>d__20, MassTransit]]
00007ffc2c585958   219903     45739824 System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib],[MassTransit.Agents.PipeContextSupervisor`1+<Send>d__7[[MassTransit.RabbitMqTransport.ModelContext, MassTransit.RabbitMqTransport]], MassTransit]]
00007ffc2bbeb578   880819     45958192 System.Object[]
00007ffc2bc98410  1126988     48981084 System.Int32[]
00007ffc2c8bcfa8   219864     51008448 MassTransit.Serialization.SystemTextJsonSerializerContext
00007ffc2c6ab548   440646     56402688 RabbitMQ.Client.Framing.BasicProperties
00007ffc2c3ca940   907996     65375712 System.Threading.Tasks.Task`1[[System.Boolean, System.Private.CoreLib]]
00007ffc2c0cc768   439763     66843976 MassTransit.Serialization.JsonMessageEnvelope
00007ffc2c717360   219899     75645256 MassTransit.RabbitMqTransport.RabbitMqMessageSendContext`1[[mt_memory_leak.TestMessage, mt-memory-leak]]
00007ffc2c6d78f8   440611     84597024 System.Collections.Generic.Dictionary`2+Entry[[System.Int64, System.Private.CoreLib],[System.Threading.Tasks.Task, System.Private.CoreLib]][]
00007ffc2bca2bb8  1100347     88027760 System.Collections.Generic.Dictionary`2[[System.String, System.Private.CoreLib],[System.Object, System.Private.CoreLib]]
000001e4eceead60  1756027    317194096      Free
00007ffc2bc9d698  5529580    374652904 System.String
00007ffc2bd5dd40  1101642    524936473 System.Byte[]
Total 39342569 objects
Fragmented blocks larger than 0.5 MB:
            Addr     Size      Followed by
000001E4DB0E2250    1.5MB         000001E4DB2651D8 System.Threading.CancellationTokenSource+CallbackNode
000001E4DD6B7708    1.0MB         000001E4DD7B2460 MassTransit.RabbitMqTransport.RabbitMqBasicConsumer+<>c__DisplayClass24_0
000001E541CA4FC0    0.5MB         000001E541D2B850 System.Collections.Concurrent.ConcurrentDictionary`2+Node[[System.UInt64, System.Private.CoreLib],[MassTransit.RabbitMqTransport.RabbitMqReceiveContext, MassTransit.RabbitMqTransport]]

my test class is like this:
public class TestMessage
{
    public string Value1 { get; set; }
    public string Value2 { get; set; }
    public string Value3 { get; set; }
    public string Value4 { get; set; }
}

I am not an expert about dotnet-dump if you need more information I can provide

An output from PerfView

I'm not really sure why it's happening. The PerfView isn't super helpful, as I can't really see what's allocating memory that isn't released. dotMemory is what I'd typically use, but I don't use Windows and it's Windows-only.

So, I'm still not seeing anything in these screenshots that points to the actual memory leak you're describing. And I won't have any time to look at it in the next few days. Also, I can't run dotMemory on MacOS, so it's unlikely to be a priority for me. Since it's a hack, I'd likely just say seriously don't do that. But I'd be curious if the leak also occurs when using the DIRECT REPLY-TO client factory for faster RPC support (rarely used, the speed increase isn't that great).

Here are the screenshots from dotMemory. I played with it to find something unique but could not. If you know where to look direct me to it or I can share my screen via discord or whatever.
I understand what you mean by "do not do that" but our situation really does not need ACK and I want to use the power of MassTransit so I am trying my chances :)

So, this is a guess, but I really have no idea what you're seeing because again, I'm not running the code. But I'm just going to likely close this issue. Straight from the RabbitMQ documentation:

Another thing that's important to consider when using automatic acknowledgement mode is consumer overload. Manual acknowledgement mode is typically used with a bounded channel prefetch which limits the number of outstanding ("in progress") deliveries on a channel. With automatic acknowledgements, however, there is no such limit by definition. Consumers therefore can be overwhelmed by the rate of deliveries, potentially accumulating a backlog in memory and running out of heap or getting their process terminated by the OS. Some client libraries will apply TCP back pressure (stop reading from the socket until the backlog of unprocessed deliveries drops beyond a certain limit). Automatic acknowledgement mode is therefore only recommended for consumers that can process deliveries efficiently and at a steady rate.

Since you are producing messages quickly, you're likely consuming more and more messages. Since MassTransit doesn't block the channel and dispatches messages asynchronously, and since auto confirmation basically prevents the broker from respecting Prefetch, etc. then it's unlikely that what you're trying to do is the right thing to do.
Therefore, while I appreciate your effort to try and reproduce the possible memory leak, this isn't a way of using MassTransit that I'm willing to support.


Add prefix key metadata search to core code

Coverage decreased (-0.003%) to 97.829% when pulling dad91622847e24ea1464d7d93fcf471112d4298c on MrCreosote:master into ff5fc997d073d1d6689f4436445185c89d427530 on kbaseIncubator:master.


textDocument/implementation - derived entities

Semantics in LSP aren't totally clear here, but this looks like a good place to show:

overrides of virtual functions
derived classes of a base
maybe template specializations?

In general, where potentially multiple entities have an "is-a" relationship with the thing under the cursor.
We may want this to fall back to "go to definition" behavior as well.

Looks like this was added in https://reviews.llvm.org/D91626 and related patches.
Should we close this, or do we plan to do other things (like the "maybe template specializations" mentioned in the description)?

Looks like this was added in https://reviews.llvm.org/D91626 and related patches.
Should we close this, or do we plan to do other things (like the "maybe template specializations" mentioned in the description)?

Yeah, I think we should close this.
Template specializations would be nice, but I'm not sure anyone's working on it, and keeping bugs open forever because we could always do more is probably a bad habit :-)


chore(locale): Add en and de locales to headline theme

I localized the headline theme for German based on this documentation: https://ghost.org/docs/themes/helpers/translate/#5-use-the-translation-helper

AFAIK the only place I wasn't able to translate yet is this:

Does anyone know where to do so?

Hey there,
You're very welcome to translate the theme or release your own translated themes! We're not ready to include translations by default in the theme at the moment.


Allowed Enum variants to be individually marked as untagged

This should hopefully resolve #1402.
This can be thought of as applying the following transformation
#[derive(Serialize, Deserialize)
enum Test {
  A(u32, u32),
  B(u32),
  #[serde(untagged)]
  C(u32),
  #[serde(untagged)]
  D(u32, u32),
}

to
#[derive(Serialize, Deserialize)
enum TestTagged {
  A(u32, u32),
  B(u32),
}

#[derive(Serialize, Deserialize)
#[serde(untagged)]
enum TestUntagged {
  Tagged(TestTagged),
  C(u32),
  D(u32, u32)
}

#[derive(Serialize, Deserialize)
#[serde(from = "TestUntagged")]
#[serde(into = "TestUntagged")]
enum Test {
  ...
}

The actual implementation generates the implementation directly allowing it to also work efficiently for recursive enums.
The current version includes a restriction that all variants marked as untagged appear at the end of the enum (after the tagged variants) in order to keep the implementation strategy consistent with an alternate strategy of attempting to deserialize each variant in order.
Deserialize could also be implemented to accept all of the variants with tags, only falling back to untagged if none of them match, I'm not sure if this would be preferred.

Thanks for all the feedback. I've tried to implement the suggestions.

I wasn't sure what the policy was on warning-like cases. Other cases to consider might be:

marking a variant as untagged when the enum itself is already untagged
marking a variant with rename/alias as well as untagged (I don't think this has a different effect than just using untagged)
marking a variant with rename/alias when the enum is untagged (This is currently allowed, so changing it would be a breaking change)

@oli-obk Hi! This feature is really usefull, but sadly there is no activity on PR more than a month. The PR itself looks quite finished except warnings. Can it be merged in this state?

Unfortunately no one on the issue has so far tested out this branch to see if it works for their use cases.

@oli-obk I tried to check it, but don't know how to replace serde dependency in serde_json

Someone was so kind and wrote instructions at https://github.com/serde-rs/serde/issues/1402#issuecomment-1565751691

@oli-obk My case was covered too. https://github.com/serde-rs/serde/issues/1402#issuecomment-1574550592


How to change LLM？

Modify the init function in src/agents/LLM/base_llm and keep the interface method get_ Response, you must ensure that the output is consistent with the original string or generator.

Thank you, I saw base_LLM.py. It would be great if there is a config file.


Failed to lookup view "admin/plugins/import"

So, I've tried quite a few things. I disabled all the plugins, restarted the nodebb server, still getting this error.
NodeBB version: 1.12.1
Node version: 10.18.1
NPM version: 6.13.4
Ubuntu 18.04
Mongo 4.0.15
I also nuked the the NodeBB install by deleting the directory a few times, including dropping all the collections in Mongo. Maybe I'm not clearing everything away?

this is still an issue for me :(

NodeBB 1.12.1
Node 12.16.2
NPM 6.14.9
MongoDB 4.4
Windows 10 build 19041.685

help?

this is still an issue for me :(

NodeBB 1.12.1
Node 12.16.2
NPM 6.14.9
MongoDB 4.4
Windows 10 build 19041.685

help?

@GamerGirlandCo got any error logs? anything?

Can confirm a rebuild fixed my issue. Thanks!


TODO

Here I'll write the future ideas that I have so far for this project.
Core features:

[x] Support SWI-Prolog (threaded, 64 bits, version 8.5.5-3-gb856d332c-DIRTY) backend.
[x] Support GNU-Prolog (64 bits, 1.5.0) backend.

Examples

[ ] Add basic examples of interval arithmetic.

Additional features:

[ ]  First finish writing the tests for all the predicates in the interval_arithmetic library.
[ ] I'm also thinking of implementing some elementary interval functions (such as sqrt(X), abs(X), sin(X), cos(X)) defined on intervals. Neumaier's book looks good for such purpose as it's more mathematically strict comparing to Moore's.
[ ] The second step would be to implement some interval methods for finding roots of functions for a certain interval. Example of such methods are interval bisection and interval Newton (see here and here).
[ ] The next step would be to create an automatic differentiation library for interval functions, as we'll be needing finding derivatives for methods such as the Interval Newton.
[ ] The next step could be to implement some global optimization methods, such as those explained in Shary's paper, or Hansen's book.

Additional ideas are welcome.

Tested the library with SWI-Prolog, 64 bit, v.7.6.4 and it works just fine:
Welcome to SWI-Prolog (threaded, 64 bits, version 7.6.4)
SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software.
Please run ?- license. for legal details.

For online help and background, visit http://www.swi-prolog.org
For built-in help, use ?- help(Topic). or ?- apropos(Word).

?- logtalk_load(loader).
% [ /home/milia/logtalk/library/types/termp.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/term.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/atomic.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/atom.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/callable.lgt loaded ]
% [ /home/milia/logtalk/library/types/characterp.lgt loaded ]
% [ /home/milia/logtalk/library/types/character.lgt loaded ]
% [ /home/milia/logtalk/library/types/number.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/float.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/integer.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/natural.lgt loaded ]
% [ /home/milia/logtalk/library/types/compound.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/pairs.lgt loaded ]
% [ /home/milia/logtalk/library/types/listp.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/list.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/list1.lgt loaded ]
% [ /home/milia/logtalk/library/types/difflist.lgt loaded ]
% [ /home/milia/logtalk/library/types/numberlistp.lgt loaded ]
% [ /home/milia/logtalk/library/types/numberlist.lgt loaded ]
% [ /home/milia/logtalk/library/types/varlistp.lgt loaded ]
% [ /home/milia/logtalk/library/types/varlist.lgt loaded ]
% [ /home/milia/logtalk/library/types/comparingp.lgt loaded ]
% [ /home/milia/logtalk/library/types/type.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/loader.lgt loaded ]
% [ /home/milia/Documents/dev/logtalk/ia/interval_arithmeticp.lgt loaded ]
% [ /home/milia/Documents/dev/logtalk/ia/interval_arithmetic.lgt loaded ]
% [ /home/milia/Documents/dev/logtalk/ia/loader.lgt loaded ]
% (0 warnings)
true.

?- logtalk_load(tester).
%
% tests started at 2022-01-10, 15:43:11
%
% running tests from object tests
% file: /home/milia/Documents/dev/logtalk/ia/tests.lgt
%
% interval_arithmetic_new_3_01: success
% interval_arithmetic_new_3_02: success
% interval_arithmetic_new_3_03: success
% interval_arithmetic_is_in_2_01: success
% interval_arithmetic_is_in_2_02: success
% interval_arithmetic_is_in_2_03: success
% interval_arithmetic_add_3_01: success
% interval_arithmetic_add_3_02: success
% interval_arithmetic_sub_3_01: success
% interval_arithmetic_sub_3_02: success
% interval_arithmetic_mul_3_01: success
% interval_arithmetic_mul_3_02: success
% interval_arithmetic_div_3_01: success
% interval_arithmetic_div_3_02: success
% interval_arithmetic_div_3_03: success
% interval_arithmetic_mid_2_01: success
% interval_arithmetic_mid_2_02: success
% interval_arithmetic_wid_2_01: success
% interval_arithmetic_wid_2_02: success
% interval_arithmetic_mag_2_01: success
% interval_arithmetic_mag_2_02: success
% interval_arithmetic_mig_2_01: success
% interval_arithmetic_mig_2_02: success
% interval_arithmetic_intersection_3_01: success
% interval_arithmetic_intersection_3_02: success
% interval_arithmetic_hull_3_01: success
% interval_arithmetic_hull_3_02: success
%
% 27 tests: 0 skipped, 27 passed, 0 failed
% completed tests from object tests
%
%
% clause coverage ratio and covered clauses per entity predicate
%
% interval_arithmetic: add/3 - 1/1 - (all)
% interval_arithmetic: (div)/3 - 1/1 - (all)
% interval_arithmetic: hull/3 - 1/1 - (all)
% interval_arithmetic: intersection/3 - 1/1 - (all)
% interval_arithmetic: is_in/2 - 1/1 - (all)
% interval_arithmetic: mag/2 - 1/1 - (all)
% interval_arithmetic: mid/2 - 1/1 - (all)
% interval_arithmetic: mig/2 - 1/1 - (all)
% interval_arithmetic: mul/3 - 1/1 - (all)
% interval_arithmetic: new/3 - 1/1 - (all)
% interval_arithmetic: sub/3 - 1/1 - (all)
% interval_arithmetic: wid/2 - 1/1 - (all)
% interval_arithmetic: 12 out of 12 clauses covered, 100.000000% coverage
%
% 1 entity declared as covered containing 12 clauses
% 1 out of 1 entity covered, 100.000000% entity coverage
% 12 out of 12 clauses covered, 100.000000% clause coverage
%
% tests ended at 2022-01-10, 15:43:11
%
true.

Related commit: 44a7f0d1a78dd74dd4bbd7051ff4ce7b70a5a98c.

Tested the library with SWI-Prolog (threaded, 64 bits, version 8.5.5-3-gb856d332c-DIRTY) and it works just fine:
Welcome to SWI-Prolog (threaded, 64 bits, version 8.5.5-3-gb856d332c-DIRTY)
SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software.
Please run ?- license. for legal details.

For online help and background, visit https://www.swi-prolog.org
For built-in help, use ?- help(Topic). or ?- apropos(Word).

?- logtalk_load(loader).
% [ /home/milia/logtalk/library/types/termp.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/term.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/atomic.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/atom.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/callable.lgt loaded ]
% [ /home/milia/logtalk/library/types/characterp.lgt loaded ]
% [ /home/milia/logtalk/library/types/character.lgt loaded ]
% [ /home/milia/logtalk/library/types/number.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/float.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/integer.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/natural.lgt loaded ]
% [ /home/milia/logtalk/library/types/compound.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/pairs.lgt loaded ]
% [ /home/milia/logtalk/library/types/listp.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/list.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/list1.lgt loaded ]
% [ /home/milia/logtalk/library/types/difflist.lgt loaded ]
% [ /home/milia/logtalk/library/types/numberlistp.lgt loaded ]
% [ /home/milia/logtalk/library/types/numberlist.lgt loaded ]
% [ /home/milia/logtalk/library/types/varlistp.lgt loaded ]
% [ /home/milia/logtalk/library/types/varlist.lgt loaded ]
% [ /home/milia/logtalk/library/types/comparingp.lgt loaded ]
% [ /home/milia/logtalk/library/types/type.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/loader.lgt loaded ]
% [ /home/milia/Documents/dev/logtalk/ia/interval_arithmetic_protocol.lgt loaded ]
% [ /home/milia/Documents/dev/logtalk/ia/interval_arithmetic.lgt loaded ]
% [ /home/milia/Documents/dev/logtalk/ia/loader.lgt loaded ]
% (0 warnings)
true.

?- logtalk_load(tester).
%
% tests started at 2022-01-10, 20:06:52
%
% running tests from object tests
% file: /home/milia/Documents/dev/logtalk/ia/tests.lgt
%
% interval_arithmetic_new_3_01: success
% interval_arithmetic_new_3_02: success
% interval_arithmetic_new_3_03: success
% interval_arithmetic_is_in_2_01: success
% interval_arithmetic_is_in_2_02: success
% interval_arithmetic_is_in_2_03: success
% interval_arithmetic_add_3_01: success
% interval_arithmetic_add_3_02: success
% interval_arithmetic_sub_3_01: success
% interval_arithmetic_sub_3_02: success
% interval_arithmetic_mul_3_01: success
% interval_arithmetic_mul_3_02: success
% interval_arithmetic_div_3_01: success
% interval_arithmetic_div_3_02: success
% interval_arithmetic_div_3_03: success
% interval_arithmetic_mid_2_01: success
% interval_arithmetic_mid_2_02: success
% interval_arithmetic_wid_2_01: success
% interval_arithmetic_wid_2_02: success
% interval_arithmetic_mag_2_01: success
% interval_arithmetic_mag_2_02: success
% interval_arithmetic_mig_2_01: success
% interval_arithmetic_mig_2_02: success
% interval_arithmetic_intersection_3_01: success
% interval_arithmetic_intersection_3_02: success
% interval_arithmetic_hull_3_01: success
% interval_arithmetic_hull_3_02: success
%
% 27 tests: 0 skipped, 27 passed, 0 failed
% completed tests from object tests
%
%
% clause coverage ratio and covered clauses per entity predicate
%
% interval_arithmetic: add/3 - 1/1 - (all)
% interval_arithmetic: (div)/3 - 1/1 - (all)
% interval_arithmetic: hull/3 - 1/1 - (all)
% interval_arithmetic: intersection/3 - 1/1 - (all)
% interval_arithmetic: is_in/2 - 1/1 - (all)
% interval_arithmetic: mag/2 - 1/1 - (all)
% interval_arithmetic: mid/2 - 1/1 - (all)
% interval_arithmetic: mig/2 - 1/1 - (all)
% interval_arithmetic: mul/3 - 1/1 - (all)
% interval_arithmetic: new/3 - 1/1 - (all)
% interval_arithmetic: sub/3 - 1/1 - (all)
% interval_arithmetic: wid/2 - 1/1 - (all)
% interval_arithmetic: 12 out of 12 clauses covered, 100.000000% coverage
%
% 1 entity declared as covered containing 12 clauses
% 1 out of 1 entity covered, 100.000000% entity coverage
% 12 out of 12 clauses covered, 100.000000% clause coverage
%
% tests ended at 2022-01-10, 20:06:52
%
true.

As mentioned in mlliarm/ia/issues/12#issuecomment-1009008243 GNU-Prolog 1.5.0 is supported too.

Since some files have been changed (see 8ab62b1455329ae067b8c2bab0b4ab65f4e119d2) I've rerun the tests with GNU-Prolog 1.5.0.
GNU Prolog 1.5.0 (64 bits)
Compiled Jan 10 2022, 16:35:29 with gcc
Copyright (C) 1999-2022 Daniel Diaz

compiling /usr/share/logtalk/integration/logtalk_gp.pl for byte code...
/usr/share/logtalk/integration/logtalk_gp.pl compiled, 31 lines read - 402 bytes written, 13 ms
compiling /usr/share/logtalk/adapters/gnu.pl for byte code...
/usr/share/logtalk/adapters/gnu.pl compiled, 787 lines read - 31176 bytes written, 26 ms
compiling /usr/share/logtalk/paths/paths.pl for byte code...
/usr/share/logtalk/paths/paths.pl compiled, 299 lines read - 42021 bytes written, 24 ms
compiling /usr/share/logtalk/integration/logtalk_comp_gp.pl for byte code...
/usr/share/logtalk/integration/logtalk_comp_gp.pl compiled, 27241 lines read - 3898810 bytes written, 1134 ms
compiling /home/milia/logtalk/scratch/expanding_248406029_lgt.pl for byte code...
/home/milia/logtalk/scratch/expanding_248406029_lgt.pl compiled, 27 lines read - 9590 bytes written, 11 ms
compiling /home/milia/logtalk/scratch/monitoring_248406029_lgt.pl for byte code...
/home/milia/logtalk/scratch/monitoring_248406029_lgt.pl compiled, 26 lines read - 9118 bytes written, 14 ms
compiling /home/milia/logtalk/scratch/forwarding_248406029_lgt.pl for byte code...
/home/milia/logtalk/scratch/forwarding_248406029_lgt.pl compiled, 21 lines read - 6266 bytes written, 12 ms
compiling /home/milia/logtalk/scratch/user_248406029_lgt.pl for byte code...
/home/milia/logtalk/scratch/user_248406029_lgt.pl compiled, 45 lines read - 9744 bytes written, 12 ms
compiling /home/milia/logtalk/scratch/logtalk_248406029_lgt.pl for byte code...
/home/milia/logtalk/scratch/logtalk_248406029_lgt.pl compiled, 310 lines read - 149981 bytes written, 57 ms
compiling /home/milia/logtalk/scratch/core_messages_248406029_lgt.pl for byte code...
/home/milia/logtalk/scratch/core_messages_248406029_lgt.pl compiled, 367 lines read - 268160 bytes written, 92 ms
compiling /home/milia/logtalk/scratch/settings_229838580_lgt.pl for byte code...
/home/milia/logtalk/scratch/settings_229838580_lgt.pl compiled, 25 lines read - 5518 bytes written, 10 ms
compiling /home/milia/logtalk/tools/tutor/.lgt_tmp/loader_201082787_lgt.pl for byte code...
/home/milia/logtalk/tools/tutor/.lgt_tmp/loader_201082787_lgt.pl compiled, 4 lines read - 1072 bytes written, 12 ms
compiling /home/milia/logtalk/library/basic_types/.lgt_tmp/loader_244474867_lgt.pl for byte code...
/home/milia/logtalk/library/basic_types/.lgt_tmp/loader_244474867_lgt.pl compiled, 4 lines read - 1234 bytes written, 11 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/termp_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/termp_36522154_lgt.pl compiled, 71 lines read - 25137 bytes written, 15 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/term_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/term_36522154_lgt.pl compiled, 98 lines read - 37083 bytes written, 21 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/atomic_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/atomic_36522154_lgt.pl compiled, 31 lines read - 8864 bytes written, 11 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/atom_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/atom_36522154_lgt.pl compiled, 59 lines read - 25296 bytes written, 16 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/number_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/number_36522154_lgt.pl compiled, 67 lines read - 27535 bytes written, 18 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/float_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/float_36522154_lgt.pl compiled, 31 lines read - 8811 bytes written, 12 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/integer_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/integer_36522154_lgt.pl compiled, 70 lines read - 26050 bytes written, 19 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/compound_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/compound_36522154_lgt.pl compiled, 31 lines read - 9080 bytes written, 15 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/listp_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/listp_36522154_lgt.pl compiled, 276 lines read - 117668 bytes written, 38 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/list_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/list_36522154_lgt.pl compiled, 447 lines read - 173476 bytes written, 81 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/type_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/type_36522154_lgt.pl compiled, 338 lines read - 247829 bytes written, 84 ms
compiling /home/milia/logtalk/tools/tutor/.lgt_tmp/tutor_201082787_lgt.pl for byte code...
/home/milia/logtalk/tools/tutor/.lgt_tmp/tutor_201082787_lgt.pl compiled, 229 lines read - 174908 bytes written, 54 ms
| ?- logtalk_load(loader).
compiling /home/milia/Documents/dev/logtalk/ia/.lgt_tmp/loader_229838580_lgt.pl for byte code...
/home/milia/Documents/dev/logtalk/ia/.lgt_tmp/loader_229838580_lgt.pl compiled, 4 lines read - 1183 bytes written, 14 ms
compiling /home/milia/logtalk/library/types/.lgt_tmp/loader_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/loader_36522154_lgt.pl compiled, 4 lines read - 1281 bytes written, 10 ms
% [ /home/milia/logtalk/library/types/termp.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/term.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/atomic.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/atom.lgt already loaded; skipping ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/callable_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/callable_36522154_lgt.pl compiled, 31 lines read - 9827 bytes written, 12 ms
% [ /home/milia/logtalk/library/types/callable.lgt loaded ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/characterp_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/characterp_36522154_lgt.pl compiled, 125 lines read - 46540 bytes written, 22 ms
% [ /home/milia/logtalk/library/types/characterp.lgt loaded ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/character_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/character_36522154_lgt.pl compiled, 169 lines read - 41255 bytes written, 28 ms
% [ /home/milia/logtalk/library/types/character.lgt loaded ]
% [ /home/milia/logtalk/library/types/number.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/float.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/integer.lgt already loaded; skipping ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/natural_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/natural_36522154_lgt.pl compiled, 35 lines read - 11380 bytes written, 14 ms
% [ /home/milia/logtalk/library/types/natural.lgt loaded ]
% [ /home/milia/logtalk/library/types/compound.lgt already loaded; skipping ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/pairs_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/pairs_36522154_lgt.pl compiled, 92 lines read - 34742 bytes written, 28 ms
% [ /home/milia/logtalk/library/types/pairs.lgt loaded ]
% [ /home/milia/logtalk/library/types/listp.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/list.lgt already loaded; skipping ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/list1_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/list1_36522154_lgt.pl compiled, 35 lines read - 12793 bytes written, 15 ms
% [ /home/milia/logtalk/library/types/list1.lgt loaded ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/difflist_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/difflist_36522154_lgt.pl compiled, 345 lines read - 169740 bytes written, 66 ms
% [ /home/milia/logtalk/library/types/difflist.lgt loaded ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/numberlistp_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/numberlistp_36522154_lgt.pl compiled, 107 lines read - 47156 bytes written, 22 ms
% [ /home/milia/logtalk/library/types/numberlistp.lgt loaded ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/numberlist_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/numberlist_36522154_lgt.pl compiled, 178 lines read - 75864 bytes written, 40 ms
% [ /home/milia/logtalk/library/types/numberlist.lgt loaded ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/varlistp_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/varlistp_36522154_lgt.pl compiled, 135 lines read - 53072 bytes written, 25 ms
% [ /home/milia/logtalk/library/types/varlistp.lgt loaded ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/varlist_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/varlist_36522154_lgt.pl compiled, 180 lines read - 69486 bytes written, 40 ms
% [ /home/milia/logtalk/library/types/varlist.lgt loaded ]
compiling /home/milia/logtalk/library/types/.lgt_tmp/comparingp_36522154_lgt.pl for byte code...
/home/milia/logtalk/library/types/.lgt_tmp/comparingp_36522154_lgt.pl compiled, 46 lines read - 15379 bytes written, 16 ms
% [ /home/milia/logtalk/library/types/comparingp.lgt loaded ]
% [ /home/milia/logtalk/library/types/type.lgt already loaded; skipping ]
% [ /home/milia/logtalk/library/types/loader.lgt loaded ]
compiling /home/milia/Documents/dev/logtalk/ia/.lgt_tmp/interval_arithmetic_protocol_229838580_lgt.pl for byte code...
/home/milia/Documents/dev/logtalk/ia/.lgt_tmp/interval_arithmetic_protocol_229838580_lgt.pl compiled, 52 lines read - 15764 bytes written, 13 ms
% [ /home/milia/Documents/dev/logtalk/ia/interval_arithmetic_protocol.lgt loaded ]
compiling /home/milia/Documents/dev/logtalk/ia/.lgt_tmp/interval_arithmetic_229838580_lgt.pl for byte code...
/home/milia/Documents/dev/logtalk/ia/.lgt_tmp/interval_arithmetic_229838580_lgt.pl compiled, 69 lines read - 29392 bytes written, 18 ms
% [ /home/milia/Documents/dev/logtalk/ia/interval_arithmetic.lgt loaded ]
% [ /home/milia/Documents/dev/logtalk/ia/loader.lgt loaded ]
% (0 warnings)

(185 ms) yes
| ?- logtalk_load(tester).
compiling /home/milia/Documents/dev/logtalk/ia/.lgt_tmp/tester_229838580_lgt.pl for byte code...
/home/milia/Documents/dev/logtalk/ia/.lgt_tmp/tester_229838580_lgt.pl compiled, 4 lines read - 1507 bytes written, 12 ms
compiling /home/milia/Documents/dev/logtalk/ia/.lgt_tmp/interval_arithmetic_protocol_229838580_lgt.pl for byte code...
/home/milia/Documents/dev/logtalk/ia/.lgt_tmp/interval_arithmetic_protocol_229838580_lgt.pl compiled, 52 lines read - 15879 bytes written, 15 ms
compiling /home/milia/Documents/dev/logtalk/ia/.lgt_tmp/interval_arithmetic_229838580_lgt.pl for byte code...
/home/milia/Documents/dev/logtalk/ia/.lgt_tmp/interval_arithmetic_229838580_lgt.pl compiled, 69 lines read - 48889 bytes written, 23 ms
compiling /home/milia/logtalk/tools/lgtunit/.lgt_tmp/loader_8325212_lgt.pl for byte code...
/home/milia/logtalk/tools/lgtunit/.lgt_tmp/loader_8325212_lgt.pl compiled, 4 lines read - 1352 bytes written, 8 ms
compiling /home/milia/logtalk/library/os/.lgt_tmp/loader_219619627_lgt.pl for byte code...
/home/milia/logtalk/library/os/.lgt_tmp/loader_219619627_lgt.pl compiled, 4 lines read - 1113 bytes written, 8 ms
compiling /home/milia/logtalk/library/os/.lgt_tmp/osp_219619627_lgt.pl for byte code...
/home/milia/logtalk/library/os/.lgt_tmp/osp_219619627_lgt.pl compiled, 181 lines read - 75321 bytes written, 28 ms
compiling /home/milia/logtalk/library/os/.lgt_tmp/os_219619627_lgt.pl for byte code...
/home/milia/logtalk/library/os/.lgt_tmp/os_219619627_lgt.pl compiled, 231 lines read - 128630 bytes written, 52 ms
compiling /home/milia/logtalk/library/os/.lgt_tmp/os_types_219619627_lgt.pl for byte code...
/home/milia/logtalk/library/os/.lgt_tmp/os_types_219619627_lgt.pl compiled, 35 lines read - 19745 bytes written, 16 ms
compiling /home/milia/logtalk/library/arbitrary/.lgt_tmp/loader_7133456_lgt.pl for byte code...
/home/milia/logtalk/library/arbitrary/.lgt_tmp/loader_7133456_lgt.pl compiled, 4 lines read - 1245 bytes written, 9 ms
compiling /home/milia/logtalk/library/random/.lgt_tmp/loader_134467479_lgt.pl for byte code...
/home/milia/logtalk/library/random/.lgt_tmp/loader_134467479_lgt.pl compiled, 4 lines read - 1176 bytes written, 9 ms
compiling /home/milia/logtalk/library/random/.lgt_tmp/randomp_134467479_lgt.pl for byte code...
/home/milia/logtalk/library/random/.lgt_tmp/randomp_134467479_lgt.pl compiled, 109 lines read - 45436 bytes written, 20 ms
compiling /home/milia/logtalk/library/random/.lgt_tmp/random_134467479_lgt.pl for byte code...
/home/milia/logtalk/library/random/.lgt_tmp/random_134467479_lgt.pl compiled, 195 lines read - 111211 bytes written, 43 ms
compiling /home/milia/logtalk/library/random/.lgt_tmp/backend_random_134467479_lgt.pl for byte code...
/home/milia/logtalk/library/random/.lgt_tmp/backend_random_134467479_lgt.pl compiled, 157 lines read - 73628 bytes written, 30 ms
compiling /home/milia/logtalk/library/random/.lgt_tmp/fast_random_134467479_lgt.pl for byte code...
/home/milia/logtalk/library/random/.lgt_tmp/fast_random_134467479_lgt.pl compiled, 195 lines read - 101672 bytes written, 42 ms
compiling /home/milia/logtalk/library/arbitrary/.lgt_tmp/arbitrary_7133456_lgt.pl for byte code...
/home/milia/logtalk/library/arbitrary/.lgt_tmp/arbitrary_7133456_lgt.pl compiled, 604 lines read - 270439 bytes written, 89 ms
compiling /home/milia/logtalk/tools/lgtunit/.lgt_tmp/lgtunit_8325212_lgt.pl for byte code...
/home/milia/logtalk/tools/lgtunit/.lgt_tmp/lgtunit_8325212_lgt.pl compiled, 1608 lines read - 1006258 bytes written, 307 ms
compiling /home/milia/logtalk/tools/lgtunit/.lgt_tmp/lgtunit_messages_8325212_lgt.pl for byte code...
/home/milia/logtalk/tools/lgtunit/.lgt_tmp/lgtunit_messages_8325212_lgt.pl compiled, 128 lines read - 86323 bytes written, 43 ms
compiling /home/milia/Documents/dev/logtalk/ia/.lgt_tmp/tests_229838580_lgt.pl for byte code...
/home/milia/Documents/dev/logtalk/ia/.lgt_tmp/tests_229838580_lgt.pl compiled, 233 lines read - 124239 bytes written, 42 ms
%
% tests started at 2022-01-10, 20:21:15
%
% running tests from object tests
% file: /home/milia/Documents/dev/logtalk/ia/tests.lgt
%
% interval_arithmetic_new_3_01: success
% interval_arithmetic_new_3_02: success
% interval_arithmetic_new_3_03: success
% interval_arithmetic_is_in_2_01: success
% interval_arithmetic_is_in_2_02: success
% interval_arithmetic_is_in_2_03: success
% interval_arithmetic_add_3_01: success
% interval_arithmetic_add_3_02: success
% interval_arithmetic_sub_3_01: success
% interval_arithmetic_sub_3_02: success
% interval_arithmetic_mul_3_01: success
% interval_arithmetic_mul_3_02: success
% interval_arithmetic_div_3_01: success
% interval_arithmetic_div_3_02: success
% interval_arithmetic_div_3_03: success
% interval_arithmetic_mid_2_01: success
% interval_arithmetic_mid_2_02: success
% interval_arithmetic_wid_2_01: success
% interval_arithmetic_wid_2_02: success
% interval_arithmetic_mag_2_01: success
% interval_arithmetic_mag_2_02: success
% interval_arithmetic_mig_2_01: success
% interval_arithmetic_mig_2_02: success
% interval_arithmetic_intersection_3_01: success
% interval_arithmetic_intersection_3_02: success
% interval_arithmetic_hull_3_01: success
% interval_arithmetic_hull_3_02: success
%
% 27 tests: 0 skipped, 27 passed, 0 failed
% completed tests from object tests
%
%
% clause coverage ratio and covered clauses per entity predicate
%
% interval_arithmetic: add/3 - 1/1 - (all)
% interval_arithmetic: (div)/3 - 1/1 - (all)
% interval_arithmetic: hull/3 - 1/1 - (all)
% interval_arithmetic: intersection/3 - 1/1 - (all)
% interval_arithmetic: is_in/2 - 1/1 - (all)
% interval_arithmetic: mag/2 - 1/1 - (all)
% interval_arithmetic: mid/2 - 1/1 - (all)
% interval_arithmetic: mig/2 - 1/1 - (all)
% interval_arithmetic: mul/3 - 1/1 - (all)
% interval_arithmetic: new/3 - 1/1 - (all)
% interval_arithmetic: sub/3 - 1/1 - (all)
% interval_arithmetic: wid/2 - 1/1 - (all)
% interval_arithmetic: 12 out of 12 clauses covered, 100.000000% coverage
%
% 1 entity declared as covered containing 12 clauses
% 1 out of 1 entity covered, 100.000000% entity coverage
% 12 out of 12 clauses covered, 100.000000% clause coverage
%
% tests ended at 2022-01-10, 20:21:15
%

(669 ms) yes

All good.


Add Project: geofirestore-js

Link to project (GitHub): https://github.com/geofirestore/geofirestore-js
Describe the project in 2-3 sentences: GeoFirestore is an open-source library that extends the Firestore library in order to store and query documents based on their geographic location. At its heart, GeoFirestore is just a wrapper for the Firestore library, exposing many of the same functions and features of Firestore. Its main benefit, however, is the possibility of retrieving only those documents within a given geographic area - all in realtime.
Why would Firebase developers be interested in this project?: This library provides geoqueries, much like geofire, to users of Firestore!
Stage your project:
Follow the instructions here and post a link to your staged content:
https://firebaseopensource.com/projects/firebase/firebaseopensource.com/docs/stage-project.md/

@MichaelSolati I am happy to add this project but I don't see an .opensource/project.json file in the repo?

@samtstern I just realized I needed to do that 😅 (pushed it up)

@MichaelSolati your project should appear on the site within 24h!

@samtstern just wanted to mention that I haven't seen it yet on the site... Did I configure something incorrectly?

@MichaelSolati good catch the build had been broken for days!
https://firebaseopensource.com/projects/geofirestore/geofirestore-js/


the "collapse_to_SBS96=True" not working for SBS288 and SBS1536

File "/share/app/SigProfiler/lib/python3.9/site-packages/SigProfilerExtractor/sigpro.py", line 838, in sigProfilerExtractor
final_signatures = sub.signature_decomposition(processAvg, m, layer_directory2, genome_build=genome_build, cosmic_version=cosmic_version, add_penalty=0.05, remove_penalty=0.01, mutation_context=mutation_context, make_decomposition_plots=make_decomposition_plots, originalProcessAvg=originalProcessAvg)
File "/share/app/SigProfiler/lib/python3.9/site-packages/SigProfilerExtractor/subroutines.py", line 849, in signature_decomposition
sigDatabase = pd.read_csv(paths+"/data/Reference_Signatures/"+"GRCh37"+"/COSMIC_v"+str(3.2)+"_SBS"+str(signatures.shape[0])+"_GRCh37.txt", sep="\t", index_col=0)
File "/share/app/SigProfiler/lib/python3.9/site-packages/pandas/util/_decorators.py", line 311, in wrapper
return func(*args, **kwargs)
File "/share/app/SigProfiler/lib/python3.9/site-packages/pandas/io/parsers/readers.py", line 586, in read_csv
return _read(filepath_or_buffer, kwds)
File "/share/app/SigProfiler/lib/python3.9/site-packages/pandas/io/parsers/readers.py", line 482, in _read
parser = TextFileReader(filepath_or_buffer, **kwds)
File "/share/app/SigProfiler/lib/python3.9/site-packages/pandas/io/parsers/readers.py", line 811, in init
self._engine = self._make_engine(self.engine)
File "/share/app/SigProfiler/lib/python3.9/site-packages/pandas/io/parsers/readers.py", line 1040, in _make_engine
return mapping[engine](self.f, **self.options)  # type: ignore[call-arg]
File "/share/app/SigProfiler/lib/python3.9/site-packages/pandas/io/parsers/c_parser_wrapper.py", line 51, in init
self._open_handles(src, kwds)
File "/share/app/SigProfiler/lib/python3.9/site-packages/pandas/io/parsers/base_parser.py", line 222, in _open_handles
self.handles = get_handle(
File "/share/app/SigProfiler/lib/python3.9/site-packages/pandas/io/common.py", line 702, in get_handle
handle = open(
FileNotFoundError: [Errno 2] No such file or directory: '/share/app/SigProfiler/lib/python3.9/site-packages/SigProfilerExtractor/data/Reference_Signatures/GRCh37/COSMIC_v3.2_SBS1536_GRCh37.txt'

Dear @YingYa,
Please use the most updated version of SigProfilerExtractor from GitHub, since we have recently updated the decomposition module. This should solve your issue. Please let us know if this is not the case.
Best regards,
Marcos

Dear Marcos,
Tanks for helping.
The change not work for sigProfilerExtractor module. I got the same errors when I run sigProfilerExtractor with SBS15236.
The SBS288 could be ran without errors, but the  Decomposed_Solution result generated by sigProfilerExtractor module not mapped to SBS96 reference signatures,
Best regards,
YingYa

Let us have a look into this. Could you please share your JOB_METADATA file?
Just a reminder, when you tried to update your SigProfilerExtractor installation, have you run these commands below? This is needed to get the latest version on GitHub.
git clone https://github.com/AlexandrovLab/SigProfilerExtractor.git
cd SigProfilerExtractor
pip install .

Yes, I have been updated the latest version on GitHub.
I still got the same errors for SBS1536.
The  JOB_METADATA file have been attached.
JOB_METADATA.txt

Hi Marcos,
I have been found the issues:
I wrote a python wrapper to run SigProfilerExtractor, and some boolean parameters (ex. collapse_to_SBS96) were passed as string "True" or "False".
I could run the code successfully after I set the right type for parameters.
Kind regards


Identity/Git Gateway users with insufficient permissions see UI with "no entries"

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
When using Netlify Identity & Git Gateway, you're able to specify which user roles (assigned with Identity) have permission to access the site's Git Gateway. If the CMS is set up with a git-gateway backend, and a user not assigned a role with permission to use Git Gateway logs in, the user will get access to the CMS UI, including the Collections side bar, but without any content. Collection names are visible, but clicking on any collection produces "no entries" in the main section.
- If the current behavior is a bug, please provide the steps to reproduce.

Create a site with Netlify CMS, using git-gateway backend and Netlify Identity. (You can do this by using the Deploy to Netlify button in the test drive doc.)
From the site dashboard, go to Settings > Identity > Services, and under Git Gateway, click Edit settings. Add a role to the Roles field (call it whatever you like) and save.
Go to the Identity tab and Invite yourself as a user on the site. Don't assign any roles to the user.
Go to your email, and click the confirmation link in the invitation email.
Log in, and see the behavior described above.

- What is the expected behavior?
I would expect that the user not be able to log in to the CMS at all, preferably with an error message explaining that they don't have permission.
- Please mention your CMS, node.js, and operating system version.
CMS 0.5.0-beta.8 on current Chrome

Video snippet from a user test wherein this bug was seen. It's a bit confusing to watch as you only hear me speaking and not the test participant as well.
http://share.neutyp.com/0D2N3o2c3G33

The applicable code almost looks invalid:
https://github.com/netlify/netlify-cms/blob/78b60c0a0bd3b0d3b69b6a88dea7c1209ec475e1/src/backends/git-gateway/implementation.js#L57-L60

OK, that code was only breaking #792, this issue is separate. How do you guys see this being done? Just log out if we get a 401 from git-gateway? Or should there be a special endpoint that we could ping to check permissions without doing an actual request (I didn't see one in https://github.com/netlify/git-gateway)?

Gitter chat with fix: https://gitter.im/netlify/NetlifyCMS?at=5a073a7b505b630c05ce8a7f.

Agreed, here are the relevant bits from that chat:

Caleb @tech4him1 Nov 11 12:59
@erquhart @biilmann What git-gatway endpoint do you think would make sense to ping to make sure we had permission to use it?
Just try to access the main branch and see if we get a 401?

Mathias Biilmann @biilmann Nov 11 13:06
fetch('/.netlify/git/github/branches/${branch}', {headers: {Authorization: 'Bearer ${token}'}}) something like that might make the most sense, yeah

Caleb @tech4him1 Nov 11 13:12
OK, that sounds good.
That's probably the smallest response we can do as well, other than opening up a new endpoint.

Mathias Biilmann @biilmann Nov 11 13:25
yeah, that’s what I was thinking
and it has the bonus of verifygin that the branch configured actually exists


Nginx-proxy solution isn't working at all

This could be an alternative https://www.linuxserver.io/2018/02/03/using-traefik-as-a-reverse-proxy-with-docker/

I stumbled on your repo searching for inspiration. Nice setup, helped me a lot.
Tried traefik, here's a minimal docker-compose that works for me.
version: '3.5'

services:

  traefik:
    image: traefik
    container_name: traefik
    restart: unless-stopped
    command: --web --docker --docker.domain=localhost
    ports:
      - 8080:8080
      - 80:80
    networks:
      - aresnet
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /dev/null:/traefik.toml
    labels:
      - "traefik.backend=traefik"
      - "traefik.frontend.rule=Host:traefik.localhost"
      - "traefik.port=8080"

  emby:
    image: emby/embyserver
    container_name: emby
    restart: unless-stopped
    networks:
      - aresnet
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - $HOME/.config/embyserver:/config
      - /media/media/:/media
    environment:
      - AUTO_UPDATES_ON=true
      - UID=1000
      - GID=1000
    labels:
      - "traefik.backend=emby"
      - "traefik.frontend.rule=Host:emby.localhost"
      - "traefik.port=8096"

networks:
  aresnet:
    name: aresnet
    driver: bridge

You should then be able to visit Traefik using ltraefik.localhost and Emby using emby.localhost.

Awesome! Thank you so much!
Can you help me creating a PR? 👍


Copy on the play page

On the Play page https://roft.io/play/ I think that the copy is too technical.

Generations from GPT-2 XL with prompts taken from the Reddit Writing Prompts dataset.

and

Generations from GROVER with prompts taken from the New York Times.

Are too technical and jargon.
How about turning them into things that would make them seem fun?

Can a computer write a short story that makes sense?

and

Donald Trump thinks the NYTimes fake news, can you spot when our computer wrote the article?

Related to #48 . Updated in commit 05d811134df05e5fc07c5e72c0fa20e550eac027 - waiting to PR until we're sure there's agreement on these descriptions


Improve top area layout on mobile

One of the advantages of this classic interface is that it makes it easier to use on mobile devices (no left / right areas).
However at the moment the top area is a bit busy with the title and checkpoints indicator:

So these could either be truncated, or maybe put on separate lines.

Another improvement would be to apply a similar thing as in https://github.com/jupyterlab/jupyterlab/pull/9433


Replace WaveformCleaner and ChargeExtractor with WaveformExtractor

This PR should only be considered once #1032 has been merged. It contains the commits from that PR in addition to the new ones.
This PR replaces the WaveformCleaner and ChargeExtractor with WaveformExtractor.
The WaveformExtractor's purpose is to extract the charge and pulse_time from a waveform. It can also apply any sort of waveform cleaning, upsampling, interpolation etc. to extract these parameters. Essentially, a WaveformExtractor is some combination of the functions defined in waveform_extractor.py to obtain the charge and pulse_time.
The extract_charge method of the old ChargeExtractor has been replaced to use __call__ instead, as per #1024.
An initial algorithm for extracting the pulse_time (via a weighted average of the waveform) is also included in this PR. This approach may be replaced with a different pulse_time calculation if it is identified as providing a better time resolution.
The containers, calibration, and tools have also been updated to handle the new DL1 contents.

Perhaps there is a better name... right now "WaveformExtractor" seems like it extracts waveforms, and you would then get back a waveform.
At the end this algorithm returns estimated charges, right?  Is that intended to be before or after calibration?  I guess before (even if we did it backwards before), but if before it's actually more still a ChargeExtractor (even if there is some internal smoothing), or if there is calibration, it could be an "IntensityExtractor", since the final output is a calibrated light intensity.

The WaveformExtractor returns both charge and pulse_time.... I am open to a better name. But IntensityExtractor doesn't fully capture it either. I did start with WaveformReducer, as we are reducing the waveform down to two parameters, but I felt this was too similar to DataVolumeReducer.

Is that intended to be before or after calibration?

Before flat-fielding / calibration into p.e.
Yeh, the simtelarray waveforms are somewhat calibrated into p.e. in their R1Calibrator. But not fully (as the full calibration depends on the charge extraction scheme used, and the correct calib scale). There needs to be an additional calibration step added after the charge extraction, as discussed in the calibration call a few months back. I intend to add it.

Some ideas for the name:

SignalExtractor
ImageExtractor
CherenkovImageExtractor
WaveformEvaluator
WaveformReducer
ChargeExtractor (and we just accept that it also returns pulse_time)

ImageExtractor isn't too bad, but it may be too general. It does extract "images" of charge and time, but that's not so clear from the name. I guess there is no perfect one!

@FrancaCassol This PR has remove the waveform_cleaner module. I have moved your BaselineSubtractor class into the subtract_baseline found inside extractor.py. I have also created the BaselineSubtractedNeighborPeakWindowSum extractor, which from uses the subtract_baseline function before extracting the charge using the neighbouring pixels.
The idea in this new approach is that an ImageExtractor performs all of the operations required to extract the charge and time from the waveforms, including any waveform cleaning. I hope this makes sense.

@kosack @dneise @MaxNoe @FrancaCassol It would be really appreciated to have this reviewed so I may continue :)

Sorry for reviewing late and then asking stupid questions. Why was this API change needed/wanted again?
I mean this part:

This PR replaces the WaveformCleaner and ChargeExtractor with ImageExtractor.

The aim is to greatly simplify the charge extraction process. The first discussion on this can be found at #907.
To summarise, this seperation of waveform cleaning and charge extraction is unnecessary, as the two are often very closely coupled. An image extractor should define the waveform operations it wants to use in order to extract the charge (and time).
One example is a cross correlation charge extraction technique. Applying the cross correlation to a waveform with a reference pulse results in a trace which defines how correlated the waveform is with the pulse for each position in the waveform. This could be considered a waveform cleaning. However, the value of each sample of this result is already an integration of charge, therefore one only needs to select the correct sample. It does not make sense to allow the user to select a window for this charge extraction technique. See my ASWG presentation in Barcelona for more details on the cross correlation technique if you are interested.
I don't think the freedom to flexibly chose a waveform cleaner and charge extractor (and mix and match at will) is necessary at run time. Instead, I think it is better to explicitly define individual charge extractors that are deemed to be useful implementations, which the user can select from.

And a further point, the ChargeExtractor was replaced with ImageExtractor, as its purpose is to extract images of both charge and time from the waveform.

Wow ..long text ... but thanks a lot

I have renamed the UserWindowSum and set out-of-range pulse_times to zero.
@kosack @dneise Could you please restore your approvals?

Setting the out-of-bounds pulse-times to nan can cause problems down the chain (some algorithms are not happy with nans existing in an array). This is currently causing an error in travis. I suggest that the pulse time is set to -1 for the time being, and we create a better pulse_time calculation in a different PR.


ConstVisitor: Container Elements are calling relayAccept() by default

Container elements of ConstVisitor are now calling relayAccept() by default.
This would be useful in cases where we want to call only the default visitor (like printing the ID for all elements). Before this commit, calling the default visitor for each element would require to override the default visitor and all the Container visitors, since we have to relayAccept all the children of the containers. Now, we only have to override the default visitor.

Good change!


Fix JWT #152

Fixes/Resolves/Closes/Magic Word's #152
Change JWT to use uid instead of id which magically fixed things

Fixes #152

fixed @kberzinch


Enhancement: add option to suppress add edit message

close #888

Off topic: I actually think that git: add (edit) is not clear to explain what it does. Maybe we should rename it to something like git: edit diff and stage?

👍  for rename

close in favor of #892


Fix/galleriesquality

This change is

Reviewed 2 of 5 files at r1, 4 of 4 files at r2.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

app/src/main/java/edu/byu/suite/features/galleries/controller/AlbumActivity.java, line 56 at r2 (raw file):

			public void onSuccess(Call<ArtworkResponseWrapper> call, Response<ArtworkResponseWrapper> response) {
				artworkList = response.body().getArtworkList();
				GridView gridView = (GridView) findViewById(R.id.gridView);

Comment

app/src/main/java/edu/byu/suite/features/galleries/controller/ArtworkFragment.java, line 47 at r2 (raw file):

		((TextView) view.findViewById(R.id.descriptionText)).setText(artwork.getDescription());

		view.setOnClickListener(view1 -> descriptionLayout.setVisibility(visibility = visibility == View.GONE ? View.VISIBLE : View.GONE));

Remove

app/src/main/java/edu/byu/suite/features/galleries/controller/ArtworkFragment.java, line 55 at r2 (raw file):

	@Override
	public View getView() {
		descriptionLayout.setVisibility(visibility);

Comment

Comments from Reviewable

Review status: 4 of 6 files reviewed at latest revision, 3 unresolved discussions.

app/src/main/java/edu/byu/suite/features/galleries/controller/AlbumActivity.java, line 56 at r2 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Comment

Done.

app/src/main/java/edu/byu/suite/features/galleries/controller/ArtworkFragment.java, line 47 at r2 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Remove

Done.

app/src/main/java/edu/byu/suite/features/galleries/controller/ArtworkFragment.java, line 55 at r2 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Comment

Done.

Comments from Reviewable

Reviewed 2 of 2 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

app/src/main/java/edu/byu/suite/features/galleries/controller/ArtworkFragment.java, line 47 at r2 (raw file):
Previously, coreywoodfield (Corey Woodfield) wrote…
Done.

Try again please :)

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

app/src/main/java/edu/byu/suite/features/galleries/controller/ArtworkFragment.java, line 47 at r2 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Try again please :)

Done.

Comments from Reviewable

Reviewed 1 of 1 files at r4.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

app/src/main/java/edu/byu/suite/features/galleries/controller/ArtworkFragment.java, line 48 at r4 (raw file):

		view.setOnClickListener(v -> {
			visibility = visibility == View.GONE ? View.VISIBLE : View.GONE

Parenthesis

Comments from Reviewable

Review status: 5 of 6 files reviewed at latest revision, 1 unresolved discussion.

app/src/main/java/edu/byu/suite/features/galleries/controller/ArtworkFragment.java, line 48 at r4 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Parenthesis

Done.

Comments from Reviewable

Reviewed 1 of 1 files at r5.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Define ObjectMeta metav1.ObjectMeta at Test case level

This PR is specific to the controller package and is required before parameterizing hard coded resource names.
It mainly removes objects such as the following.
    testObjectMeta = metav1.ObjectMeta{
        Name:     "",
        Namespace: namespaceName,
    }

The problem we are facing is that objects such as testObjectMeta are used for any resource, such as metal3Machine, Machine, cluster and so on. This creates a problem when a specific test cases needs to change the name or namespace.

/test-v1b1-ubuntu-integration

/hold

/test-v1b1-ubuntu-integration

/hold cancel


Revise tkey-runapp and tkey-sign host programs

simplify output to make it somewhat scriptable

tkey-runapp outputs UDI
tkey-sign outputs the signature, or publickey if passed --show-pubkey
all other output goes to stderr

take positional arg instead of --file
add usage
add -k/--show-pubkey to tkey-sign
correct docs
harmonize impl with tkey-ssh-agent

Revise runtimer and runrandom argument handling slightly
Signed-off-by: Daniel Lublin<EMAIL_ADDRESS>

Merged.


Add support for an Amazon Redshift and Snowflake ConnectionConfigs [#45][#44]

❗ Contains migration, combined two issues into one PR as there is very similar code in the same locations required for both
Purpose
Add support for creating a connection to a Redshift instance and a Snowflake warehouse.
This PR just represents creating the connections themselves, no testing has been done on query building.
Changes

Since Amazon Redshift now has native support for SQLAlchemy, add requirement for sqlalchemy-redshift - hopefully this means a lot of our generic SQL Connector logic will work -
Adds requirement for snowflake-sqlalchemy - same idea, it would be great to use sqlalchemy compatible libraries where possible
Add migration which updates enum for supported connection types to include redshift and snowflake
Adds a RedshiftSchema which requires either a connection url, or a host/user/password combination at minimum
Adds a SnowflakeSchema which requires either a connection url or a user_login_name/password/account_identifier at minium
Adds RedshiftConnector and SnowflakeConnector
Adds unit tests that verify creating the connection and updating secrets, but secrets aren't actually verified.
Add new integration tests that can be run with make pytest-external-integration that connect to an external test instance of Redshift and Snowflake

Notes

Adding snowflake-sqlalchemy requirement had issues building the wheel for snowflake-connector-python"  To get around, I installed snowflake-connector-python in the Dockerfile with the flag "-no-use-pep517" which I think lets it get installed from the source instead of a wheel. The downside is that this flag now applies to all packages, so you have to install cryptography first, since it needs to use PEP-517.
Referenced this issue https://github.com/snowflakedb/snowflake-connector-python/issues/382#issuecomment-681933623 which was helpful

#11 25.73   Building wheel for snowflake-connector-python (pyproject.toml): started
#11 26.12   Building wheel for snowflake-connector-python (pyproject.toml): finished with status 'error'
#11 26.12   ERROR: Command errored out with exit status 1:
#11 26.12    command: /usr/local/bin/python /usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py build_wheel /tmp/tmpg6nq068b
#11 26.12        cwd: /tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944
#11 26.12   Complete output (154 lines):
#11 26.12   running bdist_wheel
#11 26.12   running build
#11 26.12   running build_py
#11 26.12   creating build
#11 26.12   creating build/lib.linux-aarch64-3.9
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/time_util.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/azure_storage_client.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/proxy.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/errors.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/ssd_internal_keys.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/network.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/ocsp_snowflake.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/ocsp_asn1crypto.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/auth_default.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/telemetry.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/file_util.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/telemetry_oob.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/result_batch.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/local_storage_client.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/auth_oauth.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/bind_upload_agent.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/file_compression_type.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/secret_detector.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/auth_idtoken.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/storage_client.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/feature.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/constants.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/auth_by_plugin.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/dbapi.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/auth_okta.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/converter.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/auth_usrpwdmfa.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/connection.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/incident.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/options.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/auth_keypair.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/arrow_context.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/s3_storage_client.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/gcs_storage_client.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/sfbinaryformat.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/converter_snowsql.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/mixin.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/result_set.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/ssl_wrap_socket.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/auth.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/file_transfer_agent.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/converter_issue23517.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/encryption_util.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/util_text.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/version.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/gzip_decoder.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/snow_logging.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/compat.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/cursor.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/auth_webbrowser.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/description.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/pandas_tools.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/errorcode.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/sfdatetime.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/sqlstate.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/test_util.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   copying src/snowflake/connector/converter_null.py -> build/lib.linux-aarch64-3.9/snowflake/connector
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/tool
#11 26.12   copying src/snowflake/connector/tool/dump_ocsp_response_cache.py -> build/lib.linux-aarch64-3.9/snowflake/connector/tool
#11 26.12   copying src/snowflake/connector/tool/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/tool
#11 26.12   copying src/snowflake/connector/tool/dump_ocsp_response.py -> build/lib.linux-aarch64-3.9/snowflake/connector/tool
#11 26.12   copying src/snowflake/connector/tool/dump_certs.py -> build/lib.linux-aarch64-3.9/snowflake/connector/tool
#11 26.12   copying src/snowflake/connector/tool/probe_connection.py -> build/lib.linux-aarch64-3.9/snowflake/connector/tool
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/vendored
#11 26.12   copying src/snowflake/connector/vendored/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/exceptions.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/api.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/hooks.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/sessions.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/adapters.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/certs.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/help.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/cookies.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/_internal_utils.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/__version__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/structures.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/auth.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/status_codes.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/models.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/compat.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   copying src/snowflake/connector/vendored/requests/utils.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/requests
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/exceptions.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/filepost.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/_collections.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/fields.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/response.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/connection.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/request.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/connectionpool.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/_version.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   copying src/snowflake/connector/vendored/urllib3/poolmanager.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/packages
#11 26.12   copying src/snowflake/connector/vendored/urllib3/packages/six.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/packages
#11 26.12   copying src/snowflake/connector/vendored/urllib3/packages/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/packages
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/packages/ssl_match_hostname
#11 26.12   copying src/snowflake/connector/vendored/urllib3/packages/ssl_match_hostname/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/packages/ssl_match_hostname
#11 26.12   copying src/snowflake/connector/vendored/urllib3/packages/ssl_match_hostname/_implementation.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/packages/ssl_match_hostname
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/packages/backports
#11 26.12   copying src/snowflake/connector/vendored/urllib3/packages/backports/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/packages/backports
#11 26.12   copying src/snowflake/connector/vendored/urllib3/packages/backports/makefile.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/packages/backports
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/ntlmpool.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/pyopenssl.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/securetransport.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/_appengine_environ.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/socks.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/appengine.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib/_securetransport
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/_securetransport/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib/_securetransport
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/_securetransport/low_level.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib/_securetransport
#11 26.12   copying src/snowflake/connector/vendored/urllib3/contrib/_securetransport/bindings.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/contrib/_securetransport
#11 26.12   creating build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/proxy.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/retry.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/url.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/ssltransport.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/queue.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/timeout.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/wait.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/__init__.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/response.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/connection.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/request.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   copying src/snowflake/connector/vendored/urllib3/util/ssl_.py -> build/lib.linux-aarch64-3.9/snowflake/connector/vendored/urllib3/util
#11 26.12   running build_ext
#11 26.12   building 'snowflake.connector.arrow_iterator' extension
#11 26.12   creating build/temp.linux-aarch64-3.9
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector/cpp
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector/cpp/ArrowIterator
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector/cpp/ArrowIterator/Python
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector/cpp/ArrowIterator/Util
#11 26.12   creating build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector/cpp/Logging
#11 26.12   gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -Isrc/snowflake/connector -I/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector/cpp/ArrowIterator -I/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector/cpp/Logging -I/usr/local/include/python3.9 -c /tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector/arrow_iterator.cpp -o build/temp.linux-aarch64-3.9/tmp/pip-install-oxomkrnq/snowflake-connector-python_d1e3a00dad7f439183011a9a41f6e944/src/snowflake/connector/arrow_iterator.o -isystem/tmp/pip-build-env-c9fx4b07/overlay/lib/python3.9/site-packages/pyarrow/include -isystem/tmp/pip-build-env-c9fx4b07/overlay/lib/python3.9/site-packages/numpy/core/include -std=c++11 -D_GLIBCXX_USE_CXX11_ABI=0
#11 26.12   gcc: error trying to exec 'cc1plus': execvp: No such file or directory
#11 26.12   error: command '/usr/bin/gcc' failed with exit code 1
#11 26.12   ----------------------------------------
#11 26.12   ERROR: Failed building wheel for snowflake-connector-python
#11 26.12   Building wheel for httptools (setup.py): started
#11 27.65   Building wheel for httptools (setup.py): finished with status 'done'
#11 27.65   Created wheel for httptools: filename=httptools-0.1.2-cp39-cp39-linux_aarch64.whl size=101859 sha256=aca0c5c01a2764424b18908922aaca40ae90147c917be6a9b988ced238c6994c
#11 27.65   Stored in directory: /root/.cache/pip/wheels/ae/23/c1/fb3c5e2bb37b559946d40f609b38f020f6ff31b536dc8e58e8
#11 27.65   Building wheel for websockets (setup.py): started
#11 27.86   Building wheel for websockets (setup.py): finished with status 'done'
#11 27.86   Created wheel for websockets: filename=websockets-8.1-cp39-cp39-linux_aarch64.whl size=65734 sha256=630e45aa0b71839d45f8cefda935d8190a176f7211762ff0e9a08274957c9114
#11 27.86   Stored in directory: /root/.cache/pip/wheels/d8/b9/a0/b97b211aeda2ebd6ac2e43fc300d308dbf1f9df520ed390cae
#11 27.86   Building wheel for promise (setup.py): started
#11 27.99   Building wheel for promise (setup.py): finished with status 'done'
#11 27.99   Created wheel for promise: filename=promise-2.3-py3-none-any.whl size=21502 sha256=31063237ced2691811678941aacc7ae614c89426b86d55be9772ad6c624afdeb
#11 27.99   Stored in directory: /root/.cache/pip/wheels/e1/e8/83/ddea66100678d139b14bc87692ece57c6a2a937956d2532608
#11 27.99 Successfully built fidesctl ordered-set python-multipart httptools websockets promise
#11 27.99 Failed to build snowflake-connector-python
#11 27.99 ERROR: Could not build wheels for snowflake-connector-python, which is required to install pyproject.toml-based projects

Ticket
Resolves #45
Resolves #44

Relates to https://github.com/ethyca/fidesops/pull/30 - This adds secrets schemas for documentation only, some work will need to be done to reconcile, as this adds new secrets schemas.

Without digging into the weeds here @pattisdr - is the reason for not including integration tests because we can't dockerize these warehouses?
If so, I think we should still implement integration tests but use some ENV variables to provision secrets to a testbed we setup in Redshift & Snowflake ourselves. We can configure those secrets in the GitHub actions so they're available to CI, and then any contributor that wants to work on Snowflake/Redshift/etc. can set those up locally so they can run tests too.

@NevilleS, it was also a concern of not exposing our redshift/snowflake creds.  I have some questions if you want these tests available to CI:

What are the costs incurred by regularly running unit tests against Redshift/Snowflake?
What security concerns do we need to consider?  For one, we'd need to be careful to set these secrets variables up so they're not running on forked PR's, related to https://github.com/ethyca/fidesops/issues/26.

The costs shouldn't be too bad - if they become problematic, we can always set the CI up to run the integration tests more selectively (right now they are run on every commit). Having automated coverage that these connectors are functioning as expected is worth that
We can use GitHub actions to store the secrets to these (test) Redshift & Snowflake DWs. For forked PRs, GitHub allows us to require approval to run CI actions, so we can avoid attackers trying to abuse our CI environment to print out those ENV vars. We can also just ensure that the credentials we store are pre-production test credentials anyways (they would be, we don't have any production infra reliant on Redshift/Snowflake today and can segment this easily). That makes it so that, even if an attacker compromises an otherwise trusted collaborator, the worst they can do is access our test warehouse with those credentials, which would be a pretty useless attack 😄

Still working on passing secrets from github actions into external integration tests FYI ^

yay @NevilleS integration tests successfully connecting to redshift/snowflake instances now using github secrets


[Cyber][scheduler]how to switch next CRoutine?

Dear Sir,
In the SchedulerClassic::DispatchTask operation, the scheduler will call PerfEventCache::Instance()->AddSchedEvent to create a croutine, and the AddSchedEvent will enqueue the SchedPerf::RT_CREATE event to event_queue_, I guess croutine module will dequeue the eventbuffer, but I can't find these codes segments.....

hi~ PerfEventCache is just a performance debug module, i think u can refer to croutine module directly which have the real croutine codes


Maven Central Indexing

Hi Vlad, big fan of your work.
I'm a current user of the hibernate-types library, and was trying to migrate to hyperpersistence-utils, but ran into a problem. I have to pull from an internal corporate repo for security reasons and for some reason the hyperpersistence-utils is not indexed there, only hibernate-types. I'm trying to figure out why, as I'm pretty sure we scrape all of the artifacts from maven central. I noticed that your previous library hibernate types is available on mvnrepository (https://mvnrepository.com/artifact/com.vladmihalcea/hibernate-types-55) in search, but hyperpersistence-utils does not appear at all on the site, even though I see it in the index here. Is there a particular reason hyperpersistence-utils isn't showing up properly?

The artifacts have magically appeared -- I swear I checked yesterday and they were not there and my project would not build if I changed the dependency, but now it suddenly works.

The MvnRepository website is a 3rd party app. It's not affiliated to Maven Central.
Better use Sonatype instead.


Massive 404s

Hi there, we run a site with about 7000 pages indexed (On the DJANGO CMS ofcourse) - Our recent crawl showed there are about 17,000 404s that are getting picked up. Funny thing is we have less than 2400 (600 in English, rest translated in Japanese, Italian and Korean) pages on the CMS itself. Has any other DJANGO CMS owner went through such massive discrepancy in their 404s. Is Django proned to create just URLS on it's own? What could be causing this?

Hello @JacobBose , please make sure to submit questions within the appropriate channels on either the User Mailing List, IRC (freenode#django-cms) or Stackoverflow.
You can find additional information on our support page.
In this case, I believe your question is best in the Users Mailing List.

Sorry about that guys. Thx for the info! :)


Added sticky navbar(UI/UX changes) and found and solved a card issue

When scrolled down, below the header.. the navbar can be still visible with white background and small icon of webwiznitr.. this is can be undone if the we scroll back to header file and thus original navbar is visible.. It is impressive u can have a look at it

Hi @himanshubobade The idea of having a sticky navbar is great but it will be better if it is in the same colour and design of the original navbar for smooth transition. It'll be great if you could make the required changes


Sample of training data for NER model

Excuse me, could you please shatre the training data for NER model, or just give me sample human-labeld traininig data for NER model.

No matter whether you agree or not, best wishes to you. I would appreciate it if you could help me.

hello，hava you solved this problem？I have the same issue with you.  Best wishes


Ramda: use named imports

https://www.npmjs.com/package/ramda
"Destructuring imports from ramda does not necessarily prevent importing the entire library. You can manually cherry-pick methods like the following, which would only grab the parts necessary for identity to work
import identity from 'ramda/src/identity'"
In our project we mostly use  import * as R from 'ramda', but now that it is not bundled by us, but instead a dependency, it is up to other projects to tree-shake, so perhaps it is better we do the named import method instead to make sure it is always properly tree shaked. We only use mergeDeepRight, and in a create-react-app this is properly tree-shaked as is, but as their documentation says, perhaps in some setups it does not.

I tried doing this but for some reason i get this error
<EMAIL_ADDRESS>Error: You must use the @babel/plugin-transform-runtimeplugin whenbabelHelpers is "runtime".
Of course we already do what the error says to do so something funky is goin on here. Tried using babel-plugin-ramda instead but same result. Tried moving ramda back to devdependencies, same result

The problem turned out to be a missing '/'in the exclude path so node_modules was not excluded from babel


[MINOR] Remove duplicate + no publics in interface

This is a follow-up to f9a9bf1f84cb4c7fa03ecb569ae19f306a7cd85b:

Removes a code duplication
@Get("/function/{name}")
Removes public qualifiers in UnityCatalogAuthorizer interface

/cc @creechy

It's approved so it'd be nice to have it merged 🙏  /cc @tdas @MrPowers @dennyglee


Jobs

Ability to select a job in character setup and spawn in with certain equipment.
Requires space-wizards/space-station-14-content#134

Seems like this should've been closed after #434 got merged.

Indeed.


Support for npm downloads total

It seems it's missing.
![](https://img.shields.io/npm/dt/react.svg)

badge:

daaaamn, btw.. more often and more often Shields goes too slow.

btw, i'm noticing some interesting things in the other downloads badges.
for example, it seems that 1250 downloads is shown as 1.25K/month, which... is quite correct? Shields shows 1k/month.

Credits goes to millify 😄

🤓


[Business Approvals Kit - QUESTION] Approvals Kit Comparison and Version

What is your question?
Help me understand what is different in this kit that can't already be done with the same level of ease? I see this happening a lot at Microsoft low code products now.
For example, when do we get the "save as draft" and "publish" functions? Different environment still have issues where moving a solution between environments requires lots of rework (example, even if we use components and environment variables, just as one example).
I think Microsoft should focus more on fixing the product, than invest time in marketing and re-branding already packaged products under different names and classifications.
What solution version are you using?
No response
What app or flow are you having the issue with?
No response
AB#1739

Thanks for sharing your question on the Approvals Kit, and I can understand your concerns and feedback.
The Approvals Kit is designed to combine multiple components, including Power Apps, Power Automate, and Dataverse, to deliver a managed solution for approvals. While it's true that some of these components can be combined manually, the Approvals Kit offers a prepackages solution to provide additional features like multi-stage approvals, decision-making delegation, and progress monitoring that would need to be created and maintained over time if done manually. You can read more on this comparison at https://learn.microsoft.com/power-automate/guidance/business-approvals-templates/approvals-kit-comparison.
Overall, for the Approvals kit is just one approach for Approvals, depending on the features you need to use the standard Approvals connector may meet your needs. In other cases, customers may want to leverage the additional features to streamline the approval process.
Regarding your question about versioning, Microsoft is working on a platform wide as part of the current release wave plans. This approach to versioning, and the versioning support is shown with Power Automate. More information on Power Automate versioning changes is in https://learn.microsoft.com/power-platform/release-plan/2023wave2/power-automate/use-versioning-solution-cloud-flows.
The Approvals Kit also includes a Dataverse-based versioning strategy that allows you to have draft and publish approvals workflows versions. The https://learn.microsoft.com/power-automate/guidance/business-approvals-templates/content discussed the high-level architecture and data model used by the Approvals kit. As the platform-wide approach to versioning is still in progress, we will continue to update and integrate the current versioning support for Power Automate and the Approvals Kit.

For the Approvals kit we also have #17 Business Approvals Kit - Feature]: Copy / Save as Workflow


updated DNS record entry

suggested in #59971
period at the end apparently makes the entry valid

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


Update 2022-10-06

Latest update changed pointers. SRT update required to work with latest version.

All pointers increased by 1A0. Update to this plugin is imminent.


bump mathlib

I bumped yesterday, so this seems unnecessary. The lake exe mk_all is useful though

Oh, I didn't noticed you bumped it yesterday. Do we merge it anyway or I need to change anything?

Can you undo the bump? The other changes should be merged.

Ok, will do it later today (now I'm from mobile).