Multi-owner/role support

This is  a feature request.
Description
When dealing with multiple "owners"(groups/companies/...) the need quickly arrises to need certain users with multiple owners. Esp. when tying in with AD (where the user table (can) get provisioned by it; but owner_id & role_id are blocking that insertion)

Owners are role collections used to limit the user role to a certain collection.
In some simple cases you can extend Owners into some other entity, like Companies, like your example. I don't see how a user should belong to two companies but that's another thing...
If things get complicated you should make a dedicated Companies structure, and if it makes sene map Owners to Companies.
For instance, owners can be: comercial, technical, management, training, and you can have companies which have trainers (or a training dep) and companies that don't.

99% of our users do fine with just 1 owner; the issue is those select few (& the mapping that can't happen via our AD)
just realized we could likely abuse the impersonation system for those users; however dealing with the user profile not showing up while I was testing 😅  (doing a fresh upgrade to the latest enso now; as quite a lot changed recently so might've updated to a bad version)

I believe that we can close this.

There's a workaround possible indeed; although I'd still consider it for a future refactor.


Dhall deprecations

There are a number of deprecation warnings in ./src/Spago/Config.hs stemming from usage of Dhall.TypeCheck.X.
We ought to fix that up unless there is a real reason to continue using the deprecated features.
@f-f  - is there a reason not to resolve?

@Benjmhart no, they should be fixed! I'm fixing this as part of #458

Fixed in #486


Fix links render inside for loops

related to issue #133

Thanks, i'll take a look. I see i have a reproduction case already on a branch.

I have added a test case and moved this commit to #193 so the original library maintainer can review it. Also, there was a little compiler error still in there, which i fixed. You name is still on the original commit so your authorship is maintained. Thanks for contributing!


Fix typos in negative-margins file

I am only using selected src files in my project.
All variables in the _negative-margins.css file appear to have a leading - which is preventing the value from being calculated.
For example:
.na1 { margin: -var(--spacing-extra-small); }
Should be:
.na1 { margin: var(--spacing-extra-small); }

Hey @meandillar!
All css files src need to be run through postcss. Tachyons offers built in build tooling, but you can also use your own. That's why the values aren't being calculated.
If you only want selected modules and you're running a fork/clone of tachyons-css/tachyons you can comment out the modules you don't want to include in src/tachyons.css and then run npm run build.
Let us know if you run into any other issues.

@johno Thanks for the help, much appreciated.


NTLM support for chained proxy

This is code proposal for LittleProxy to support preemptive NTLM authentication to a chained proxy.
In the class extending ChainedProxyAdapter, just set an NTLM handler to enable this feature.
setNtlmMessageHandler(new NtlmHandlerImpl(new JcifsNtlmProvider("myuser", "mypass")));
I have used http://jcifs.samba.org/ as default provider to generate NTLM messages, but any provider can be plugged in.

Hi, @dparmar
Is it possible to introduce NTLM anthentication into this project? Http basic anthentication is unsecure.

Yes I think it should be feasible. I can explore possible ways to do it and give it a shot.

Nice to hear this. Looking forward to your contribution.  Thanks very much.

Hey everybody, how can I introduce ntlm authentication into an exiting project? And how can I set a NTLM handler, so which imports do I have to do? Thanks in advance

I am confused. This pull request has been open for almost 3 years. Yet it is has not been accepted. Is there a fundamental reason for this?

Is there a reason this has been open for almost three years and not accepted?

@arykov: There are probably a few reasons this hasn't been merged:

There are merge conflicts that the author hasn't resolved
The unit tests don't work out-of-the-box
There are breaking changes to existing interfaces
It includes an LGPL 2.1 dependency, which the ASF claims is ASL-incompatible
The changes are complex and require scrutiny that the current maintainers are unable to give
The demand for this change is perceived to be low

I'm inclined to agree with you, though. I think this PR should be closed if there isn't an appetite to move it forward.

Based on the lack of updates, I'll close this PR.


fix: Generate noir interface for constructors

With the last changes for contract deployment, a contract can call another contract's initializer.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit c2371936 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
5,668
18,852
36,420

l1_rollup_calldata_gas
66,388
239,316
470,148

l1_rollup_execution_gas
648,126
932,234
1,311,448

l2_block_processing_time_in_ms
1,305 (+5%)
4,679 (+1%)
8,992 (-3%)

note_successful_decrypting_time_in_ms
192 (+24%)
518 (-3%)
948

note_trial_decrypting_time_in_ms
96.7 (+61%)
36.0 (-27%)
78.6 (+1%)

l2_block_building_time_in_ms
17,922 (+1%)
68,049 (+1%)
136,144 (+2%)

l2_block_rollup_simulation_time_in_ms
8,129 (+1%)
28,731
56,801

l2_block_public_tx_process_time_in_ms
9,773 (+2%)
39,265 (+3%)
79,248 (+4%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,960 (+1%)
27,789 (+6%)

note_history_successful_decrypting_time_in_ms
1,290 (+4%)
2,476 (+1%)

note_history_trial_decrypting_time_in_ms
108 (+66%)
184 (+15%)

node_database_size_in_bytes
18,665,552
35,049,552

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
283 (+1%)
44,366
28,245

private-kernel-ordering
217 (+1%)
52,869
14,327

base-parity
1,850 (+4%)
128
311

base-rollup
722 (+2%)
165,788
925

root-parity
1,582 (-3%)
1,244
311

root-rollup
51.8
4,487
725

private-kernel-inner
651 (+1%)
73,772
28,245

public-kernel-app-logic
435 (+2%)
35,260
28,215

public-kernel-tail
174 (+1%)
40,926
28,215

merge-rollup
8.30 (-7%)
2,696
925

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.1 (+1%)
16.1
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.588
0.496
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
46.1
75.1 (+4%)
229
445
867
1,722
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.472
0.464 (+4%)
0.419
0.416
0.414
0.413
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
53.8
108 (+2%)
336
666 (+1%)
1,307
2,603 (-1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
104
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.479
0.489 (+2%)
0.457
0.458 (+1%)
0.455
0.453
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
61.2

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.535

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes

tx_size_in_bytes
22,013

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes

tx_pxe_processing_time_ms
3,171 (-1%)
1,762 (+1%)

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
13.8 (+15%)
1,223 (+1%)


Add moon.

Fixes https://github.com/nrwl/monorepo.tools/issues/92

@bcabanes Would appreciate a review when you have a chance!

Bump.


PWWS Attack

PWWS Attack implementation
Files/utils for text models, datasets, tokenizers, word substitutions, etc.

@someshsingh22 , please have a look.


faster equals comparison run vs array #161

There's no observable speed up in average speed, but the high centiles are improved significantly (on my laptop).

Coverage decreased (-0.03%) to 89.853% when pulling 79c61ca8698ad6342f16cea6ea1a1a3072f85277 on richardstartin:equality-run-vs-array into 6568498dda044dc3e94400e57b1cf6d1f60c1191 on RoaringBitmap:master.

Coverage decreased (-0.03%) to 89.853% when pulling decb74414def50cf0241bf8172a096bf2b135c93 on richardstartin:equality-run-vs-array into 6568498dda044dc3e94400e57b1cf6d1f60c1191 on RoaringBitmap:master.

@gssiyankai  I think we can issue a release based on this at some point in the future. Let me know.

Coverage increased (+0.03%) to 89.906% when pulling 12b3c337109178167b9e64d31f3af5a1d89b2d13 on richardstartin:equality-run-vs-array into 6568498dda044dc3e94400e57b1cf6d1f60c1191 on RoaringBitmap:master.

Good job! I'll merge the PR soon.

@lemire let's issue a new release

Ok. Proceeding.


closing child window does not always focus parent

The most recently opened window is focused when a window closes, instead of the parent / spawner of the closed window.
example: open two terminals, use each to open an image. the newest terminal is always focused after the image closes, instead of the terminal that spawned the image.

berry is a non-reparenting window manager, similar to katriawm. It's unclear to me whether or not this is feasible to implement, although I can look into it.

So, I have developed an imperfect but reasonable solution on the development branch. Until now, berry has default to focusing the next window in the focus list whenever a client is closed. However, if we instead focus the previous window, we achieve this behavior about 99% of the time. I see this situation being most common when you do some action in an application that spawns another window (i.e. a file browser to send an email attachment, or something similar). Since the parent window is almost always focused last, we revert to that window, emulating parent focusing without needing re-parenting.
Such a solution is imperfect in a few edge cases. If you were to 1) open a popup 2) open another new window and switch to it 3) close the popup, focus would revert to the newly opened window, not the parent of the popup. Likewise, if a window spawns a child without being focused this would not work either. However, both of these situations seems rare and not something I see as a high priority.
The feature is available on the development branch here. Feel free to try it out. I will close this issue once the feature has been merged to master.
:)

Merged with master as of 0.1.5. Closing :)


pkg/meta: using a function with a @required parameter as tear-off does not warn about missing required parameter

Dart VM version: 2.1.0-dev.4.0 (Fri Sep 7 16:44:38 2018 +0200) on "windows_x64"
import 'package:meta/meta.dart';

void main() {
  // analyzer info: The parameter 'paramB' is required.
  doStuff(1);
  // nothing wrong here according to the analyzer
  // but I would expect the analyzer to inform me about the missing parameter
  [1].forEach(doStuff);
}

void doStuff(int paramA, {@required bool paramB}) {}

My guess (?) is this is WAI (working-as-intended), since @required is not a language feature, and the tools are not tracking the intention of this annotation - you see some of the discussion at https://github.com/dart-lang/language/issues/15 for details.
For example, what about the following cases:

Is @required applicable to function types void Function({@required String name})?
Is @required inherited across extends/implements/with?

One silly idea to move forward is to introduce a lint, i.e. avoid_tearoff_required, for the above case.
/cc @Hixie @bwilkerson @munificent

Yeah, this is a good example of why relying on metadata annotations for features like this doesn't give as nice of an experience as baking the feature fully into the language.
Because @required isn't part of the language, it's not part of the type system. Even if analyzer was changed to statically propagate the @required through tear-offs and function types, it's still not able to do that to the runtime type of the function, so you'll still be able to get into bad situations.

What bad situations? @required is only for static analysis, it shouldn't do anything at runtime.

@Hixie:
Here is one:
import 'package:meta/meta.dart';

class A {
  void doThing() => print('doThing()');
}

class B {
  void doThing({@required String name}) => print('doThing($name)');
}

void main() {
  B b = B();
  A a = b;
  // Required not linted... resulting in:
  // Runtime error: `name` is null.
  a.doThing();
}

The grammar does not currently allow metadata on the parameter types in a "new style" function type like void Function({@required String name}), but I don't see any particular difficulties in adding support for that.
However, it may be somewhat tricky to support that with an analysis which is an enhanced version of the one we have currently to use this kind of information on function types. We would flag certain casts as violations of "requiredness preservation":
void foo1({int i}) {}
void foo2({@required int i}) {}

void Function({@required int i}) f1;
void Function({int i}) f2;
void Function() f3;

main() {
  f1 = foo1; // OK, requiredness can be overestimated, no problem.
  f2 = foo1; // OK, extended type unchanged.
  f3 = foo1; // OK, regular function type upcast.
  f1 = foo2; // OK, extended type unchanged.
  f2 = foo2; // Flagged as bad, forgets requiredness.
  f3 = foo2; // Flagged as bad, forgets required parameter.
}

It may be surprising that we are flagging otherwise always-ok transitions like upcasts as bad, and there may be some tricky corners around type variables:

Y foo<X extends Y, Y>(X x) => x;

main() {
  Function() f = foo(({@required int i}) => i); // Bad!
}

It is surprising that the invocation of foo is "bad", because the declaration seems safe (it is a plain upcast to return x because X extends Y).
We can't see at the call site that the execution of foo will perform an upcast from the first to the second type argument (so it will be overkill to flag all such generic function calls), and we can't see in the implementation that it is unsafe to perform that upcast (so it will be overkill to flag all such function declarations). But that upcast for this call site will be an upcast from Function({@required int i}) to Function(), and that would allow us to "forget a required parameter".
There may be an easy and elegant solution, but it hasn't dawned upon me yet. ;-)
PS: I don't think this difficulty has anything to do with being part of the language or not, there's nothing stopping the linter from knowing all the things that the type checker knows, and then some, and there's nothing (other than convention) stopping the type checker from seeing metadata.

Ah, I forgot this: The relationship between A.doThing and B.doThing here is exactly one of those situations involving an upcast: It is generally considered safe to access a B using the static type A, but when some upcasts are bad (like that from void Function({@required String name}) to void Function()) we make standard OO subsumption a problem.

@matanlurey I assume B extends A? I don't understand why that's a runtime error caused by @required. It's exactly what would happen if the annotation was absent. Fundamentally that code is bogus, anyway, and ideally would be linted by something else (the subclass is changing the API in ways that aren't valid in reasonable OOP).

@required is being replaced by required, so no further work will be done to support @required.

@required is being replaced by required, so no further work will be done to support @required.

I just tested with required instead of @required and it's working correctly.

I just tested with required instead of @required and it's working correctly.


Update to sprockets 4

This has failing checks. flushed

I've now added some extra commits to fix the apparent SCSS issues that are now problematic with Sprockets 4.


pojoutil support generic

PojoUtils support generic class with return data no classname

Codecov Report

Merging #11914 (f9aae43) into 3.2 (7d9e955) will increase coverage by 2.06%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.2   #11914      +/-   ##
============================================
+ Coverage     64.66%   66.73%   +2.06%
+ Complexity       14        2      -12
============================================
  Files          1433     1678     +245
  Lines         60077    67058    +6981
  Branches       8829     9600     +771
============================================
+ Hits          38851    44748    +5897
- Misses        17158    17990     +832
- Partials       4068     4320     +252

see 3111 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


All timestamps must be normalize to application timezone

All LDAP timestamps displayed must be converted to the application's timezone.

Fixed: 4a1e392


Environ definition

Add local requirements with additional pip dependencies for developer machines
Add environ variables for Registration
Update heroku documentation

We will need to transfer all API Keys and Secret values to environ to avoid sharing them on git.

lgtm


docs: compatibilityVersion is available in the latest release.

🔗 Linked issue

📚 Description
Hi!
The first of the opt in steps in Nuxt 4 is the change to nightly release, but the compatibilityVersion is available in the latest version.
Therefore, we would like to clarify that it is also available in the latest version.

In fact we should probably also indicate that the nightly version now has breaking changes without opt out. So nightly release would have to have 3x version... Maybe worth mentioning both here and on nightly release page.

Indeed, that's true.
I'll create a PR!

You have already fixed it!
Thank you!


EVA modes of inheritance and ClinVar submitters

We would like to be able to extract inheritance patterns (autosomal dominant, X-linked recessive, etc) specific to mendelian disorders as well as identify more heavily curated sources of associations to them within ClinVar like OMIM and ClinGen (i.e. we'd like to identify those submitters).  We also know how to get that kind of information directly from ClinVar, but I wanted to see if you guys have ever discussed the value of dimensions like this as part of a target ranking scheme.
From our perspective, it would be ideal if this was incorporated as a part of the evidence strings provided via eva-cttv-pipeline.  Have data elements like this ever been requested before?
Thanks!

It's on our immediate plans to increase the amount of information on our mendelian evidence. Mode of inheritance, mutation consequence, variant-disease confidence, variant IDs (when available) or increase coverage are some of the aspects we want to cover for different data sources. Of course, this will lead into improved scores for some of these evidence.
We'll work with EVA on improving eva-cttv-pipeline, but we will also need to work with some of the evidence sources such as gene2phenotype, OMIM or Genomics England PanelAPP.
It would help if you could share with us any wish list of feature you would like to see

Thanks @d0choa, I think that covers everything on our wishlist -- mode of inheritance, consequence (e.g. clinical significance), and variant-disease confidence (based on the source/submitter of the association).
When you say OMIM, do you mean anything other than the OMIM data collected as part of EVA from ClinVar?

Yes, sorry I was not very specific. A subset of the OMIM data does not have variant information, therefore it does not come to us through EVA. However, this information is still relevant to establish target - disease relationships.
You will see a set of tickets for different bits of the work starting from Monday.

Hey @d0choa that's great to know -- what is that extra OMIM information?  Is it simply established gene - disease associations without knowledge of underlying variants or something less proximate?
I'll keep an eye out for those issues.  From my perspective, feel free to close this out if those new issues address this all in more detail.

Yes that's the case for a subset of the OMIM evidence. I'm sure we will learn a bit more about them as we review them.


Configure multiples resources on same url

When I try to deploy 2 resources with the same URL but different exposed ports, I get the error Domain http://domain is already in use.
Related issue i ran into: there is no check server-side when i set http://domain:port as URL. The deployement suceed in with this url but application can't be reached through it.
On Coolify v3.

The url input is required. Is it really possible to deploy without domain name ?

you can do this with my pr at https://github.com/coollabsio/coolify/pull/1505


Remove some mrbgems from build_config.rb

Remove some mrbgems from build_config.rb.
These mrbgems are now bundle as mruby core library (See mruby/mrbgems). So, no need to explicitly install.

Thanks!


Due date persistance fails

The temp field is saved, but the parsing and saving into due date does not work as intended

Fixed due date persistence bug and added the option to write "today" or "tomorrow" converting those keywords into naivedates.


support tikz,tikz-cd,includegraphics

Motivation

Manim is not correctly drawing tikzpictures
Proposed changes

svg_mobject.py
tex_file_writing.py

Test

Code:
from manimlib import *

class Video(Scene):

    def construct(self):

        txt = r"""
\begin{tikzcd}
    {\mathcal{C}}
    \arrow["K"', from=1-1, to=2-1]
    \arrow[bend left=37, "F" name=U, from=1-1, to=2-2]
    \arrow[Rightarrow, "\eta" description,
    shorten <=4pt, pos=0.58, from=U, to=2-1] \\
    {\mathcal{D}}
    \arrow["\mathrm{Lan}_K F"', ""{name=UU, below},
    from=2-1, to=2-2] & {\mathcal{E}}  \\
    {\quad } & {\quad }
    \arrow[phantom, ""{coordinate,name=Z},
    from=3-1, to=3-2]
    \arrow["L"', ""{name=DD},
     from=2-1, to= 2-2,
     rounded corners,
    to path={ -- ([yshift=-3ex] \tikztostart.south)
              |- (Z) [pos=1] \tikztonodes
              -| ([yshift=-3ex] \tikztotarget.south)
              -- (\tikztotarget)}]
    \arrow ["\chi", Rightarrow,  shorten <=1.5pt,
    from=UU, to= DD, yshift=-1ex]
\end{tikzcd}
        """

        tex = TexText(txt, template="ctex",additional_preamble=r"\usepackage{tikz-cd}").set_stroke(RED,width=4)
        self.play(ShowCreation(tex),run_time=10)

Result:
https://github.com/3b1b/manim/assets/15604323/20dadf47-97b2-4d0d-8af0-276e479af55a

Thanks for the proposed fix, but this doesn't seem to work for me. Specifically at this line, (in svg_mobjct.py, at line 122)
element_tree = ET.parse(file_path)
It doesn't seem to find the given file path.


Swipe up to remove an item

Hello. I'm looking for a component like yours, that can get a bunch of cards/elements, and the user be able to swipe left/right to browse the elements, but when the user swipes up, the card needs to be removed from the list and a new card loaded from the backend using state or something.
Also when swipe down, the card should load another scene/page.
Is this possible?
Thank you!

Hi @medisoft,
Currently, this can't be implemented because the plugin is based on a FlatList component while what you're after requires an advanced PanResponder. I've favored the former so far because of its ability to handle huge amounts of items.
Still, my roadmap includes implementing a custom PanResponder on top of the FlatList to unify the snap behavior between Android and iOS. This may also allow more advanced interactions like the ones you're after. Honestly, I won't be able to add this kind of feature anytime soon; it's going to take a lot of hard work. But it's my wish to make it happen in the long run.
For now, these plugins might be of interest to you:

https://github.com/alexbrillant/react-native-deck-swiper
https://github.com/meteor-factory/react-native-tinder-swipe-cards


Zippy CL

🐛 Bug Report
There's a report on Zippy not showing up from being before the pets CL but I got a zippy just the other day and its not shown up on my CL, yet one of my CC mates has zippy unlocked on his. Also checking the mostdrops it says one person has over 400 and another over 80, are drops going towards them somehow? Or is that left over dice banking mischief?

Regarding the bit about mostdrops: There was a bug with hunter where hunting ferrets actually gave zippy (due to same ID), so the mostdrops list got skewed. Zippys aren't going towards anyone else!

I got zippy at 18 qp yesterday on my ironman?

I got zippy at 18 qp yesterday on my ironman?

This is not what the issue is about. In the future, please take care to make sure your comments are productive and not clogging up the issue thread.

What's the context then? As worded, I don't understand, I guess?
Just handed info that seemed to contradict the claim. Apologies.

Zippys aren't going towards anyone else!

The context here isn't that Zippy not dropping, we know it is dropping correctly. The issue is that its not being added to the collection log (Or rather, being inconsistently added. IE: SDRad got a zippy and it didn't count towards log, but his buddies zippy did count). Is Zippy in your =cl pets?

I just got Zippy on ironman, and it does not appear in the collection log.
Neither does my Wilvus, but I don't even a placeholder for Wilvus

I believe this is fixed now.


System Check Script #8: Structure / Full Check Script

Note on the structure of the tests: the base level check of “is it there” is run when the satellite object is initialized within pycubed. The results of this check populate the “hardware_dict” that’s referenced in main.py. Every other file / test first checks the hardware_dict to ensure that the object being tested is in fact there, and then runs the higher level “is it functional” check.

Every “is it functional” test, apart from radio and burnwire, is fairly fast (5 minutes total), so I took your suggestion on only explicitly asking the user if they want to run the radio and burnwire test
Let me know if there’s any other user input changes y’all want to add (given this setup) / if there’s any structural changes you want me to make to change this

Order to merge system check script in:
First, merge System Check PRs #1-7 with this branch
Then, merge PR #8 (this) with the main branch

Looks solid, just a little confused about a few things.
Also I'd like to be able to test out the UX of this, could you make it so that if I add the updated driver to this branch I could test out this check script?

Hey @thetazero, sorry I missed this comment. The check script already works with the updated driver. I'm holding off on adding all the files to this branch because I want to make sure we can look at each of them separately.
If you'd like, I can either create a new branch for the current version of the full check script or send a folder to you on Slack for you to test out.

Gonna keep this on request changes until all the other test scripts and main are merged into this. Then we should test it out on hardware.

Agreed. Regarding testing, I've tested this and sent Losha a copy of the full script to test out. He suggested a few style changes apart from the ones in the PRs, so I'll implement all of that and then re-request review. I can also send you a copy of the folder if you'd like to test it out before we merge everything!

Major changes:

Print the tests that weren't run separately

New changes: edited main.py to support the logging infrastructure

I've tested the IMU and the entire script; it should be ready for UX testing now.


USHIFT-706: Add CSI Deployment Flag and Config

Definition of Done:

[x] Feature implementation complete
[ ] Added test scenarios to test workflows described by the EP
[x] Added unit-tests as necessary
[ ] ~Repo documentation is updated and Docs team has reviewed the changes~ TBD in separate PR

/test all

/retest-required

squashed commit history

lgtm, I will let others label it

/lgtm


Inconsistent declarations for FStar.UInt.min_int

I keep getting inconsistent declarations for FStar.UInt.max_int, see below. I wasn't able to figure whether that's a problem in the source or in Kremlin, but since it used to work, I guess it depends on something that changed recently.
cc -O3 -march=native -mtune=native -funroll-loops -I /mnt/e/everest/joonwonc_merkle_tree/kremlin/include -I /mnt/e/everest/joonwonc_merkle_tree/kremlin/kremlib -I /mnt/e/everest/joonwonc_merkle_tree/hacl-star/lib -Wall -Wextra -Werror -Wno-parentheses -Wno-unused-parameter -Wno-unused-variable -Wno-infinite-recursion   -c -o c/FStar.o c/FStar.c
c/FStar.c:14:18: error: static declaration of ‘FStar_UInt_min_int’ follows non-static declaration
 static Prims_int FStar_UInt_min_int(Prims_int n)
                  ^~~~~~~~~~~~~~~~~~
In file included from /mnt/e/everest/joonwonc_merkle_tree/kremlin/kremlib/extracted/TestLib.h:14:0,
                 from c/Prims.h:12,
                 from c/FStar.h:11,
                 from c/FStar.c:7:
/mnt/e/everest/joonwonc_merkle_tree/kremlin/kremlib/extracted/FStar_UInt.h:20:11: note: previous declaration of ‘FStar_UInt_min_int’ was here
 Prims_int FStar_UInt_min_int(Prims_int n);
           ^~~~~~~~~~~~~~~~~~
cc1: error: unrecognized command line option ‘-Wno-infinite-recursion’ [-Werror]
cc1: all warnings being treated as errors
<builtin>: recipe for target 'c/FStar.o' failed
make[2]: *** [c/FStar.o] Error 1

(It's easy to fix post-hoc, but I'd rather have the actual problem resolved.)

hello Christoph,
It seems like some files that come from two different invocations of kremlin are being included in the same scope. This is unsupported. If I had to make a wild guess, I would suspect you have two different TestLib.h, one that is in c/ and another one that is in kremlib/, and that compiling c/FStar.c ends up including kremlib/TestLib.h instead of c/TestLib.h.
Can you compile the contents of c and kremlib separately, without exposing one to the other on the include path? That should help identifying the build error.
Thanks,
Jonathan

Hmm, actually, I don't think that was the case. I was using kremlib via the Merkle trees and I tried to reuse as much as possible of that so I don't have to have a second copy. I don't think I need TestLib.h though, so maybe I'll just exclude that from the snapshot.

The new snapshot of Merkle trees does not include TestLib.h after my latest merge. This should solve it.


add rutar.org

I am suggesting my personal site rutar.org. My site has been posted on HN and received some attention: https://news.ycombinator.com/from?site=rutar.org.
The compressed non-icon size of the homepage is 5.31KB according to Firefox. A page with more content also comes in at 9.38KB.
Thanks for your time!

Thank you for submitting this website. It has now been added in commit 0f5a036. This website now appears at the 8th position at https://10kbclub.com/.


Stop adding new features, start adding more tests!

This is our test coverage at the moment. Test Coverage
At this point, stability and optimization is more important than new features. So if you want to contribute:

Copy the real life scenarios in readme.md into unit tests or vice versa (Very easy and beginner friendly)
Add new tests to uncovered methods
Optimize speed/syntax/document/version compatibility of current methods

I will be creating empty test files for everything so it will be easy to fill in. Ideally if a user wants to know what a function does, they should be able to just check the tests files and understand from the example code in there.
Thank you all for contributing!

We should use Danger to automatically fail a pull request if it doesn't include tests, as well as a bunch of other stuff

So if you can create all the testing files, we can start opening issues for everything that is missing

Testing files are ready. Just needs to be filled, so thats like 40 issues. I'd rather people choose one file at a time and write tests for it, send a pull request than start working on another file. Kind of like  how piv199 is doing

@goktugyil can we close this? We're about to hit 40% coverage

40%? Thats still too low :(

@goktugyil I agree, but 40% is good enough for it to stop being our main focus.
The title of this issue is "Stop adding new features, start adding more tests!"


Hi Great Example!

Hi @ovrmrw Great Example! But why not use redux? It would be grateful than flux.

Thanks, @kenchengch  :)
The way to make my store is strongly influenced by Tackling State.
This is a great article that illustrates how to make a store like Redux using RxJS.


Math.random incompatibility with popular libraries

(I'm trying to get more code to work under SES, and I'm gathering incompatibility problems as I go).
The temp library (1.5m downloads/week, 1.5k directly-dependent packages) uses  Math.random at runtime to create (somewhat) unique temporary filenames, we use this in cosmic-swingset.
temp also imports the very popular glob (26m downloads/week, 18k dd), library, which imports minimatch (15m dl/wk, 4k dd), which imports brace-expansion, which calls Math.random() at import time to create unlikely-to-already-exist replacement names for escaping various punctuation marks. (The pattern is apparently: escape, manipulate, unescape, which doesn't sound very sound to me, but was probably easier to write).
When Math.random() throws under SES, these libraries cannot be imported, or used at runtime. The current workaround is to disable taming of Math.random during lockdown(). A partial workaround (for only the import-time problem) would be to e.g. import 'brace-expansion' before lockdown, then import 'temp' after lockdown, which might help if we happened to not use the portions of temp which needed Math.random (unlikely).
For our own use cases, we're only using these libraries in the start compartment. I remember we discussed allowing the start compartment's Math to have a working Math.random (but still hardened / tamed against .constructor attacks), but remove Math.random from the globals of all other compartments. I think that approach would resolve this incompatibility.

The temp library (1.5m downloads/week, 1.5k directly-dependent packages) uses Math.random at runtime to create (somewhat) unique temporary filenames, we use this in cosmic-swingset.

Yes, the source of randomness should be passed in.
I wonder how I dealt with this in xs... hm... looks like I used Math.random() ambient authority. I wonder if it actually works; if so, that means XS compartments aren't as pure as I thought.
https://github.com/dckc/agoric-sdk/blob/xs-build-lite/packages/cosmic-swingset/lib/xs-npm/temp.js#L11

... brace-expansion, which calls Math.random() at import time to create unlikely-to-already-exist replacement names

How about a PR to choose at build time? I suppose a build time choice could be exploited by an adversary, but it's not like Math.random() is all that secure either.

@warner is this fixed? Can we close it?

@warner is this fixed? Can we close it?

Closing. Please reopen if this is still a problem.


Bugged earnings / not clear

Hi, my game is stuck in this situation and earn zero-to-none money and takes too much time.

it's something like one cent per second

same situation in another game

Thanks for reporting. Was there any error thrown at the console?

I had no issues in the console so far, only the "game saved" or so periodically


Data workflows deployment

from our 7/15 meeting, BBL suggested:

https://compass.pnnl.gov/welcome; Seems like we could ask about having a https://compass.pnnl.gov/diagnostics webpage(s) that we upload your rmarkdown html outputs to?

[ ] let's look into this next week


[Request]  Coqui TTS

🥰 需求描述 | Feature Description
It would be nice to add support for Coqui TTS. For example, if you start a local server and connect to it.
Coqui TTS docs:
https://tts.readthedocs.io/en/latest/inference.html
🧐 解决方案 | Proposed Solution
You can just give the system, or the made VENV commands like tts -list-models and so on. Just to run locally or on a server with a normal processor
📝 补充信息 | Additional Information
And as a side note. I want to use TTS voiceover for SRT and ASS subtitles, it would be nice to have such a function in the application

I have encapsulated the method for calling TTS into hooks. You only need to write a fetch request that restricts the returned result to a Blob to achieve compatibility. The relevant code can be referred to as follows:

useTTS: https://github.com/lobehub/lobe-tts/blob/master/src/useTTS/index.ts
useOpenaiTTS: https://github.com/lobehub/lobe-tts/blob/master/src/useOpenaiTTS/index.ts
fetchOpenaiTTS: https://github.com/lobehub/lobe-tts/blob/master/src/services/fetchOpenaiTTS.ts

If you urgently need support from Coqui, welcome to submit a PR. Alternatively, I will try to provide support after completing the main feature development on my end.


Sideboxes not always rendering

The boxes on the right side aren't always rendering — on this page for example.
http://<IP_ADDRESS>/project/slide/0.1
http://<IP_ADDRESS>/manage/slide/41
One sidebox renders and one doesn't. I'm confused

The sidebox renderer previously required [--box--] and [--endbox--] to be on the same line.  The sidebox injection rejex has been updated to allow the start and end placeholders to be on separate lines.


Update .all-contributorsrc

Added myself to the file and removed all other elements

@all-contributors
please add @natnew for doc

@all-contributors
please add @natnew for doc

@all-contributors
please add @natnew for doc

@all-contributors
please add @natnew for doc

@all-contributors
please add @natnew for doc

@all-contributors
please add @natnew for research


Support FPS Bridging and Wrapping in App

We should rework this area in the pool page (https://app.frankencoin.com/pool):

It should show the users balance of FPS, WFPS and Polygon WFPS. It should contain etherscan links to all three token contracts as well as a link to defillama swap where polygon WFPS can be swapped to polygon ZCHF. Furthermore, we should think about how we could support wrapping, unwrapping, bridging and unbridging.

discussion moved to #63


Feature request - unpack needs single-file / footprint-file option

Unpacking a multi-mb/multi-gb MSIX to pull out one file is wasteful.  Please include a "-f" and "-ff" option, like:
# Unpack just the muffin.wasm and a group of DLLs
makemsix unpack -p file.msix -d .\output -ss -f code-assets\muffin.wasm -f appsvcimpl\*.dll

# Unpack just the catalog and manifest
makemsix unpack -p file.msix -d .\output -ss -ff codeintegrity -ff manifest

Where the "-ff" options are for the footprint files.

Option
File

manifest
The AppXManifest.xml for the package

blockmap
The blockmap XML file

signature
The signature file, if present

codeintegrity
The catalog file, if present

contentgroupmap
The content group map file

Is -ff needed?
Footprint files are unique filenames; you can't put a 'content' file in an MSIX named appxmanifest.xml or signature.p7x. Filenames are unique so -f appxmanifest.xml would work equally well as -f foo.exe
Footprint files have well defined unique names, so -ff manifest as an alias for -f appxmanifest.xml seems unnecessary overkill


nyc report --reporter=json not doing anything?

There is no .json file created in the project folder. Any tips on this @bcoe ? tnx

my bad, it's inside the coverage folder


fix: show maximums events for /txid

closes #865

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


All generate objects are same

I write a 3DGAN myself,after training,I find that the object generate are all the same,though different random_noise input,Do you know why?
(my network not set eval mode)

What you mentioned is called "Mode Collpase", which is one of common problems.
There are various approaches, so please look into them.
https://developers.google.com/machine-learning/gan/problems


Is 3D Secure support?

I would like to know, does cordova-plugin-braintree, plugin support 3D secure? I found 3dsecure branch and how can it test it?

Register a Braintree Sandbox account and you can use it for test.
https://www.braintreepayments.com/sandbox

Is there a way to check a card is enrolled in a 3D Secure program? At javascript, I can check a card is enrolled or not by using following code.
client.verify3DS({   amount: 500,creditCard: NONCE_FROM_DROPIN_OR_CUSTOM_INTEGRATION }, .........
When a card is enrolled in a 3D Secure, customer will be prompted to authenticate using their bank login credentials. It does not prompted when I am using plugin.

I found it on 3dsecure branch. I have check out 3dsecure branch and it is worked as expected.
    BraintreePlugin.presentThreeDSecureVerification(secureoptions, function(result){.....                                    })


feat: bump @lifi/sdk to 3.0.0

Description
See #7278.
Since the issue most likely lays without LiFi internals (i.e here
https://github.com/lifinance/sdk/blob/25e7edc37a31858585f54c89ef11661369bc88d4/src/request.ts#L75), bumping Li.Fi SDK to latest major should ensure we have the latest bugfixes, which may or may not fix this issue.
Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

contributes to https://github.com/shapeshift/web/issues/7278

Risk

High Risk PRs Require 2 approvals

Medium - Li.Fi could be borked

What protocols, transaction types or contract interactions might be affected by this PR?

Testing

Li.Fi routes are still happy
Execute Li.Fi route and ensure trade execution / completion  is still happy

Engineering

^

Operations

^

Screenshots (if applicable)
LiFi routes are still happy

LiFi bridge still happy e2e
https://jam.dev/c/bb6307f8-4cbf-44be-99b4-093f9d8b3a80
https://explorer.li.fi/tx/0x9338cbb613d2ef7a768f002bbaf1adb2e25874c5c77a260211e9b04815489519/

Trade:

Bridge:


the error message ("incorrect visualization") instead of the extension...

I don't know why but both in Qlik Sense Desktop and Server I see the error message ("incorrect visualization") instead of the extension...

I believe you just cloned the github repo. You have to compile it like it written in the readme.
Or you can download here the binary: https://m.sense2go.net/extension-package


Default to name fix

Fixes problem of potential mismatch of receiver's email address and name as described here.
Also adds support of email only arrays<EMAIL_ADDRESS><EMAIL_ADDRESS>and enables throwing 'empty to' error only if both to and defaultTo are not set.

@ScottAgirs fixed and tested.
But one more bug seems to be found. If you'll add Cc(as well Bcc and Attachments) field to your message, you'll get msg object of following structure:
{
  Messages: [
    {
      From: ...
      To: ...
      ...
    }
  ],
  Cc: ...,
  Bcc: ...
}

Hey @burlakko thanks for the commits and sorry for the delay, I think we're good to merge, the last thing, though - it looks like your ESLint/Prettier settings are reformatting things - please revert those changes, then merging in! :)

Hi @ScottAgirs! Sorry for the delay. Can you please provide your eslint config file, so i could apply desired code formatting? Also maybe it's a good idea to have it inside of project?

Hi @ScottAgirs! Sorry for the delay. Can you please provide your eslint config file, so i could apply desired code formatting? Also maybe it's a good idea to have it inside of project?

@burlakko thanks for the PR, and you make a good point. I think the Linting issue is ok for now, we will be adding linting config to the project as you suggested! :)
Cheers!

@burlakko thanks for the PR, and you make a good point. I think the Linting issue is ok for now, we will be adding linting config to the project as you suggested! :)
Cheers!


resourcemgr uses 100% CPU on Ubuntu 16.04 x86_64

I cloned the current TPM2.0-TSS master and built it on an Ubuntu 16.04 x86_64 desktop system. resourcemgr is started as a systemd service and doesn't use any CPU resources. After successfully executing any of the tpm2-tools (e.g. tpm2_listpcrs) the resourcemgr is left behind using up 100% of the CPU cycles. Repetitive tpm2-tool calls will cause the resourcemgr to use all available processor cores.
This behaviour does not occur with the official Ubuntu libtss2 package which apparently is based on a much older version of the TPM2.0-TSS software.
Best regards
Andreas

Attached a backtrace of the thread caught in an endless loop: resourcemgr_bt.txt

Thanks for the backtrace @strongX509. Queuing this up.

Thanks for the patch. resourcemgr is working fine now.


Transparent proxy

Hello. How about add feature transparent proxy. Is it possible?

What do you mean transparent? Sorry for my stupidity

Basically if you give pattern argument, then the url that doesn't match the pattern will be sent transparently

Transparent proxy is a way of routing all traffic via a proxy. Usually done in iptables using the TPROXY extension for a PREROUTING rule in the NAT table. More on this here: https://www.kernel.org/doc/Documentation/networking/tproxy.txt
Not sure what it has to do with SpoofDPI. Automatic adding of the needed iptables rules may be?


ScopedBuilder invalid behaviour

Hello,
thanks for the great package!
There is an error related to the loading / error behaviour on "ScopedBuilder".
Here is the example code:
import 'package:flutter/material.dart';
import 'package:flutter_triple/flutter_triple.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(title: 'Tripple Test', home: MyHomePage());
  }
}

class Counter extends StreamStore<Exception, int> {
  Counter() : super(0);

  Future<void> increment() async {
    setLoading(true);

    await Future.delayed(Duration(seconds: 1));

    int value = state + 1;
    if (value < 5) {
      update(value);
    } else {
      setError(Exception('State not can be > 4'));
    }
    setLoading(false);
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key}) : super(key: key);
  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  final _counter = Counter();

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Test'),
      ),
      body: ScopedBuilder<Counter, Exception, int>(
        store: _counter,
        onState: (state, counter) {
          print('onState called: $counter');
          return Padding(
            padding: EdgeInsets.all(10),
            child: Text('$counter'),
          );
        },
        onError: (context, error) {
          print('onError called: $error');
          return Center(
            child: Text(
              error.toString(),
              style: TextStyle(color: Colors.red),
            ),
          );
        },
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: (() async {
          await _counter.increment();
        }),
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ),
    );
  }
}

This is the output:
Restarted application in 155ms.
onState called: 0
onState called: 0
onError called: null
onState called: 2
onState called: 3
onState called: 4
onState called: 4
onState called: 4
...

It never calls onError. If I remove setLoading(true); / setLoading(false); then everything works as expected.
This is my Flutter configuration:
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.4 20F71 darwin-x64, locale en-GB)

Thanks!

Thanks for comments !
Could you tell me what the version?

Hi,
I am sorry. Here is the version in my pubspec.yml:
flutter_triple: ^1.2.0

Fixed version 1.2.1. Thank you @unipenlabs

Great work! Thank you!


nixos/networkd: get rid of *Config attributes in lists

Description of changes
This patch is about removing wireguardPeerConfig, dhcpServerStaticLeaseConfig - a.k.a. the
AbstractSingletonProxyFactoryBean of nixpkgs - and friends.
As a former colleague said

worst abstraction ever

I second that. I've written enough networkd config for NixOS systems so far to have a strong dislike. In fact, these don't even make sense: netdevs.wireguardPeers._.wireguardPeerConfig will be rendered into the key [WireGuardPeer] and every key from wireguardPeerConfig is in there. Since it's INI, there's no place where sections on the same level as wireguardPeerConfig fit into. Hence, get rid of it all.
For the transition, using the old way is still allowed, but gives a warning. I think we could drop this after one release.
The tests of rosenpass and systemd-networkd-dhcpserver-static-leases were broken on the rev before, hence they were updated, but are still not building.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

We have to wait with the merge until after the branch-off since this is a breaking change and thus unfortunately too late for 24.05.

Isn't the idea of these *Config options that we could have abstractions in sibling options that get rendered into the *Config option? Granted, I guess that hasn't actually happened yet, or else this PR wouldn't be possible.

@ElvishJerricco for systemd.network, the structure has pretty much always been a direct mapping to how the .ini files look like, no? (Sure, with a few modifications such as using lists for sections that can appear multiple times).
I don't expect much to happen there given what the options are for. Also, I don't know anyone who likes the way this is currently structured and the usually recommended "workaround" is using "extraConfig" which is IMHO worse since it doesn't have any eval-time validation, so I'd strongly prefer my solution over the current state.

As 24.05 got branched off let's merge now and fix possible fallout of this change in the next weeks.


Add Natural Language Firebase implementation

Hi, @TheDOme6!
Thank you for contributing!
Can you implement iOS Natural Language?

:lgtm:


Segmentation fault from logger in s2s and rescorer

Logging is not yet initialized in addOptions, so we get segmentation fault in s2s and rescorer from here: 2def3251add6af4d959db127bfd96cd1c1de90e6:
0x0000000000444cbf in spdlog::details::line_logger
    spdlog::logger::_log_if_enabled<>(spdlog::level::level_enum, char const*) ()

I temporally commented the logging, but a fix is needed.
Another thing: is "verbose" here correct?

What's going on with this one? Is the pull request still valid after the recent changes?


abort in uv__io_poll

'sometimes' I get a program abort. After several retries I was able to get a backtrace in gdb, seems it is caused by libuv. (But probably because I'm doing something too exotic?)
I would rather have some explanation instead of a plain old abort() or some help as to resolve the problem.
Thank you.
GDB backtrace:
(gdb) backtrace full
#0  0xb7fdd424 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb7df1607 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
        resultvar = <optimized out>
        resultvar = <optimized out>
        pid = -1208561664
        selftid = 1956
#2  0xb7df4a33 in __GI_abort () at abort.c:89
        save_stage = 2
        act = {__sigaction_handler = {sa_handler = 0x805453c, sa_sigaction = 0x805453c}, sa_mask = {__val = {1,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>,
<PHONE_NUMBER>, 1,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>, 1, 1, 0, 134617276, 134563184, 134563132,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>,
<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>, 134563284,<PHONE_NUMBER>,<PHONE_NUMBER>,<PHONE_NUMBER>, 255,<PHONE_NUMBER>, 134563284, 1, 134562588,<PHONE_NUMBER>}},
          sa_flags = 1, sa_restorer = 0xb7df48f0 <__GI_abort>}
        sigs = {__val = {32, 0 <repeats 31 times>}}
#3  0xb7fb5bed in uv__io_poll (loop=loop@entry=0x805431c, timeout=-1) at src/unix/linux-core.c:183
        events = {{events = 1, data = 9}, {events = 0, data = 0} <repeats 81 times>, {events = 0, data =<PHONE_NUMBER>}, {events = 0, data =<PHONE_NUMBER>}, {
            events = 0, data =<PHONE_NUMBER>2674840576}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>98149624}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>8425974802}, {
            events = 134530885, data = 1}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0,
            data = 0}, {events = 0, data = 0}, {events =<PHONE_NUMBER>, data = 0}, {events = 0, data = 0}, {events = 10, data = 0}, {events = 0, data = 0}, {
            events = 0, data = 0}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>741092}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>}, {events = 0,
            data =<PHONE_NUMBER>}, {events = 0, data =<PHONE_NUMBER>87002368}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>2}, {events = 0,
            data =<PHONE_NUMBER>5636899654}, {events = 0, data = 0} <repeats 23 times>, {events = 0, data =<PHONE_NUMBER>4}, {events =<PHONE_NUMBER>,
            data =<PHONE_NUMBER>8988305136}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>0}, {events = 4096, data =<PHONE_NUMBER>1288}, {events = 134597768,
            data =<PHONE_NUMBER>61000960}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>0043650184}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>4851431720}, {
            events = 128, data =<PHONE_NUMBER>2437140930}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>7}, {events = 9663, data =<PHONE_NUMBER>}, {events =<PHONE_NUMBER>,
            data = 7894382}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0,
            data =<PHONE_NUMBER>893077504}, {events = 30068, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0,
            data = 0}, {events = 858861107, data =<PHONE_NUMBER>258779694}, {events =<PHONE_NUMBER>, data = 99}, {events = 0, data = 0}, {events = 0, data = 0}, {
            events = 0, data = 0}, {events = 0, data =<PHONE_NUMBER>843462400}, {events = 544568430, data =<PHONE_NUMBER>697164627}, {events = 544366925,
            data =<PHONE_NUMBER>574431282}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>4831188}, {events = 0, data = 0}, {events = 0, data =<PHONE_NUMBER>602727424}, {
            events = 13880, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 671088640,
            data =<PHONE_NUMBER>38}, {events = 0, data = 0}, {events = 0, data =<PHONE_NUMBER>7180598272}, {events =<PHONE_NUMBER>, data = 0}, {events = 0,
            data =<PHONE_NUMBER>4}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>9409609739}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>4715804745}, {
            events =<PHONE_NUMBER>, data =<PHONE_NUMBER>9581140251}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>85}, {events = 134597768, data =<PHONE_NUMBER>}, {
            events = 1, data = 0}, {events = 0, data = 134597768}, {events =<PHONE_NUMBER>, data = 0}, {events = 1, data = 0}, {events = 0, data = 16885952}, {
            events = 0, data = 0}, {events = 0, data =<PHONE_NUMBER>9758187}, {events = 824210021, data =<PHONE_NUMBER>191659577}, {events = 667950,
            data =<PHONE_NUMBER>529678409}, {events = 541347393, data =<PHONE_NUMBER>1047002413}, {events = 12, data =<PHONE_NUMBER>8214957728}, {
            events =<PHONE_NUMBER>, data =<PHONE_NUMBER>5}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>4096258060}, {events =<PHONE_NUMBER>,
            data =<PHONE_NUMBER>9981950452}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>9981950304}, {events = 12, data =<PHONE_NUMBER>4}, {events =<PHONE_NUMBER>,
            data =<PHONE_NUMBER>4236793868}, {events = 12, data =<PHONE_NUMBER>}, {events = 12, data = 0}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>2638127104}, {
            events = 12, data =<PHONE_NUMBER>4020321632}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>2}, {events = 0, data = 0}, {events = 12, data = 0}, {
            events = 0, data =<PHONE_NUMBER>2636734224}, {events = 0, data =<PHONE_NUMBER>9159079936}, {events = 0, data = 0}, {events =<PHONE_NUMBER>,
            data =<PHONE_NUMBER>4488843948}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0,
            data = 0}, {events = 0, data = 0}, {events = 0, data =<PHONE_NUMBER>}, {events = 0, data = 0}, {events = 0, data = 0}, {events = 0, data = 0}, {
            events =<PHONE_NUMBER>, data =<PHONE_NUMBER>}, {events = 0, data =<PHONE_NUMBER>380934144}, {events =<PHONE_NUMBER>, data = 170926138}, {events = 0,
            data = 0}, {events = 0, data =<PHONE_NUMBER>752}, {events = 4, data =<PHONE_NUMBER>}, {events = 0, data = 0}, {events = 134563544, data =<PHONE_NUMBER>},
          {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>3}, {events = 2048, data =<PHONE_NUMBER>9958715096}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>1814873301}, {
            events = 9, data =<PHONE_NUMBER>0}, {events =<PHONE_NUMBER>, data = 4}, {events =<PHONE_NUMBER>, data = 0}, {events = 0, data =<PHONE_NUMBER>}, {events = 1,
            data = 0}, {events = 0, data = 0} <repeats 372 times>, {events = 0, data = 134597832}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>3274105856}, {
            events =<PHONE_NUMBER>, data =<PHONE_NUMBER>6452764672}, {events = 0, data =<PHONE_NUMBER>5781025792}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>99518496}, {
            events =<PHONE_NUMBER>, data =<PHONE_NUMBER>}, {events = 0, data =<PHONE_NUMBER>5015388160}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>}, {
            events =<PHONE_NUMBER>, data =<PHONE_NUMBER>9033020416}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>9032918156}, {events =<PHONE_NUMBER>,
            data =<PHONE_NUMBER>5977113576}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>3449560166}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>6493883494}, {
            events = 38, data =<PHONE_NUMBER>50}, {events = 6, data =<PHONE_NUMBER>76}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>}, {events =<PHONE_NUMBER>,
            data = 42400}, {events = 5, data =<PHONE_NUMBER>5670647808}, {events = 49412, data =<PHONE_NUMBER>72850178}, {events = 3, data = 47}, {
            events =<PHONE_NUMBER>, data = 0}, {events = 0, data =<PHONE_NUMBER>4461858864}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>0998318056}, {
            events = 134598544, data =<PHONE_NUMBER>40}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>88}, {events = 0, data =<PHONE_NUMBER>1696829997}, {events = 38,
            data =<PHONE_NUMBER>72850178}, {events = 0, data =<PHONE_NUMBER>2511220736}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>72850176}, {events =<PHONE_NUMBER>,
            data =<PHONE_NUMBER>2}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>}, {events = 9, data = 0}, {events = 0, data = 2049}, {events = 0,
            data =<PHONE_NUMBER>07995}, {events = 1, data =<PHONE_NUMBER>8757475616}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>0874463235}, {events =<PHONE_NUMBER>,
            data =<PHONE_NUMBER>159477257}, {events = 6, data =<PHONE_NUMBER>85780}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>1500032260}, {events = 50132,
            data =<PHONE_NUMBER>3124333570}, {events =<PHONE_NUMBER>, data =<PHONE_NUMBER>0}, {events = 0, data =<PHONE_NUMBER>560}, {events = 0,
            data =<PHONE_NUMBER>47744}, {events = 33188, data = 1}, {events = 0, data = 0}...}
        pe = <optimized out>
        e = {events = 4, data = 1}
        q = <optimized out>
        w = <optimized out>
        sigmask = <optimized out>
        base = <optimized out>
        diff = <optimized out>
        nevents = <optimized out>
        count = <optimized out>
        nfds = <optimized out>
        fd = <optimized out>
        op = <optimized out>
        i = <optimized out>
        no_epoll_wait = 0
        __PRETTY_FUNCTION__ = "uv__io_poll"
#4  0xb7fa7fb2 in uv_run (loop=0x805431c, mode=UV_RUN_DEFAULT) at src/unix/core.c:324
        timeout = <optimized out>
        r = 1
#5  0x0804abe3 in run (global=0x80542f8) at ../src/dbtest.c:432
        start = 43767
        hr_start =<PHONE_NUMBER>184
        end = 134523779
        hr_end =<PHONE_NUMBER>4919230247
        cpu_time = 5,0307156866601071e-270
        real_time = 1,9097962118687451e-313
#6  0x0804ada8 in main (argc=2, argv=0xbffff624) at ../src/dbtest.c:463
        global = 0x80542f8

Can you provide some more information? Line numbers don't match, what libuv version are you using? How did you reproduce it?

Hi,
I'm using libuv version 1.2.1.
The abort is on line 183 in src/unix/linux-core.c.
I'm not sure how I reproduced it, rerun of program under gdb doesn't always cause the abort.
Ben...

For the record, this is the failing code: https://github.com/libuv/libuv/blob/v1.2.1/src/unix/linux-core.c#L181-183
Can you print the errno on frame 3?

Yes you are correct.
I have changed those lines:
    if (uv__epoll_ctl(loop->backend_fd, op, w->fd, &e)) {
      if (errno != EEXIST) {
        fprintf(stderr, "errno: %d: %s\n", errno, strerror(errno));
        abort();
      }

This gave me
errno: 1: Operation not permitted
Note that before the error I did get 3 successful runs (only the 4th failed)

Hum, that is really weird. Errno 1 is EPERM, which means the target fd doesn't support epoll. Do you have a minimal test case I could try? Are you using uv_poll_t handles for polling some fds?

Here's some more insight:
Changed the lines some more:
    if (uv__epoll_ctl(loop->backend_fd, op, w->fd, &e)) {
      if (errno != EEXIST) {
        fprintf(stderr, "errno: %d: %s %p %d\n", errno, strerror(errno), w, w->fd);
        abort();
      }

Now got:
errno: 1: Operation not permitted 0x808496c 1
Which means it's stdout which is failing.
The uv_write doesn't indicate failure though.

Any chance fd 1 is not really stdout, but was replaced with something else? I suspect there is aproblem in your code, but unless you paste a way for us to reproduce it there is not much else I can do.

My program automagically increased the buffer size when the input was generated very fast.
When the input transfer is slow, no problems.
When the input transfer is high, each time the output buffers are doubled.
But it seems that uv_write cannot handle more that 1024 buffers.
I can't find such limit in the documenation.
I found IOV_MAX is set to 1024
So it was indeed a bug in my program, I just have to take IOV_MAX into account when increasing my buffer size.
Example test case:
//Compile with: gcc -g test.c -luv -o test
//run with: test <buffer size>

#include <uv.h>

#include <stdlib.h> //calloc
#include <string.h> //strlen
#include <unistd.h> //STDOUT_FILENO
#include <stdio.h> //fwrite/fputs

void write_cb(uv_write_t* req, int status) {
	fprintf(stderr, "write_cb: %d\n", status);
	if(status!=0) fprintf(stderr, "write_cb: %s: %s\n", uv_err_name(status), uv_strerror(status));
}

int main(int argc, char* argv[]){
	uv_loop_t loop;
	uv_loop_init(&loop);

	uv_tty_t console;
	uv_tty_init(&loop, &console, STDOUT_FILENO, 0);

	if(argc<2) {
		fputs("specify buffer count\n", stderr);
		return 1;
	}
	size_t count=atoi(argv[1]);
	uv_buf_t *bufs=calloc(count, sizeof(*bufs));
	size_t index=0;
	for(;index<count;++index) {
		bufs[index].base="Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n";
		bufs[index].len=strlen(bufs[index].base);
	}
	uv_write_t req;
	int result=uv_write(&req, (uv_stream_t*)&console, bufs, count, write_cb);
	if(result!=0) {
		fprintf(stderr, "uv_write: %d\n", result);
		fprintf(stderr, "uv_write: %s: %s\n", uv_err_name(result), uv_strerror(result));
	}

	fprintf(stderr, "run...\n");
	uv_run(&loop, UV_RUN_DEFAULT);
	free(bufs);
	fprintf(stderr, "done\n");
	uv_loop_close(&loop);
	return 0;
}

Hum, I tried your test case and even with 1000000 buffers it doesn't fail :-S

Try redirecting stdout to a file: test 1025 > test.txt

@bwijen I think the documentation for uv_tty_init() is somewhat lacking; it neglects to mention that you can't use uv_tty_init() when the file descriptor refers to a file.
If you look at io.js and node.js, they first call uv_guess_handle(STDOUT_FILENO) and then either call uv_tty_init() if it's a tty, socket or pipe, or call uv_fs_write() when it's a file.
In a future version of libuv, we should probably let libuv take care of all that behind the scenes so the libuv user doesn't have to worry about it.  If nothing else, it would simplify the tty handling code in io.js quite a bit.
I'll open a pull request that updates the documentation and makes uv_tty_init() check that the file descriptor is compatible.

@bnoordhuis great, thanks!

@bnoordhuis Thank you!
It would be nice if libuv supports a uv_file_t 'subclass' of uv_stream_t to abstract the uv_guess_handle away. (Where can I sign up?)

Update: When using uv_fs_write I do get an EINVAL when using a nbufs > IOV_MAX (and offset==-1)
So for now, there's no difference in using either uv_write or uv_fs_write when nbufs<=IOV_MAX
I would be nice to use uv_write with nbufs>IOV_MAX, but I find checking IOV_MAX as upperbound is a suitable workaround.

@bwijen Filed https://github.com/libuv/libuv/issues/260 for that.  You're welcome to take a stab at it if you want. :-)

Closing, now that #259 landed. #260 remans an open issue though. Thanks everyone!


Check block request only if system index

Description

Category : Bug Fix
Why these changes are required? : There was an issue where documents could not be queried without system index permissions, even if the index was not a system index. This has been fixed.
What is the old behavior before changes and new behavior after changes?

old : Documents could not be searched without system index permissions when plugins.security.system_indices.permission.enabled enabled
new : Documents in normal indexes can always be searched regardless of system index permissions.

Issues Resolved
issue: https://github.com/opensearch-project/security/issues/4429
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[x] New functionality includes testing
[ ] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@10000-ki could you plz rebase? The main branch contains fix for the DelegatingRestHandlerTests test

@willyborankin
thank you I have rebased my branch.

@cwperks @willyborankin
Oh.. I have enhanced the test cases, and the approval was removed.
I'm sorry, but could I please ask you to review it again?

@cwperks @willyborankin Oh.. I have enhanced the test cases, and the approval was removed. I'm sorry, but could I please ask you to review this pr again?

@10000-ki, will do during the day


Ecto 2.0 Changes

This supplants #2

@romul I switched to using schema.__struct__ |> model_name and it worked great!

@veverkap If it supports both version of Ecto, then dependency should be >= 1.1
And I guess git rebase origin/master -i with squashing of commits to a small one would be cool.

@romul I'm not sure that it supports both versions of Ecto
== Compilation error on file lib/new_relixir/plug/instrumentation.ex ==
** (CompileError) lib/new_relixir/plug/instrumentation.ex:50: unknown key :data for struct Ecto.Changeset
    (elixir) src/elixir_map.erl:185: :elixir_map."-assert_struct_keys/5-lc$^0/1-0-"/5
    (elixir) src/elixir_map.erl:62: :elixir_map.translate_struct/4
    (stdlib) lists.erl:1353: :lists.mapfoldl/3

@veverkap Well, I will try it by myself.

@romul do you think you will merge either this PR or #6?

I'm going to close this in lieu of #6 which seems nicer.

@doomspork I would recommend to take a look at #10 as well.
Personally I use {:new_relixir, github: "romul/new-relixir"} until there is no feedback to PRs.

Sorry @romul!  I wrongfully assumed you were the maintainer, I now see it is @dcuddeback.


Error: no JSON at incomin...

I'm using alexa-remote2 Echo node to activate Bluetooth connection to my soundbar upon a certain trigger (in my case when Echo starts playing music). This worked fine in the beginning but suddenly stopped working and I get an error message "Error: no JSON at incomin..." (cannot see whole message as it is cut at the end).
I'm using proxy authentication with seems to be fine. The error is available in the latest version (3.7.0).

Additional information: When I restart my flows, everything works again for some time, but then some time later, the error reappears.

@bwims yes that could be the case (however I have no proof for this). Still I would consider this a bug.

I've meanwhile changed my flow to avoid sending the same command subsequently to the alexa nodes but the error still occurs. Seems to be less often now but still happening.

Have you found a solution to this problem? I continue to have random "NO JSON" error
This is the flow that I'm testing:

Often the last node gets the NO JSON error, but sometimes it happens also for the others

Please update the issue if you find something new

will do!
On Thu, 30 Apr 2020 at 16:51, Walter Lucetti<EMAIL_ADDRESS>wrote:

Please update the issue if you find something new
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/586837r/node-red-contrib-alexa-remote2/issues/84#issuecomment-621940020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENIQ2LDV3LG7MSOK3HJ5YTRPGM7JANCNFSM4J3BONQQ
.

I have not seen this error since I inserted a delay node to limit the message rate.
This leaves Alexa enough time to complete one message before she gets the next message.
In my use case, limiting the message rate to one every 3 seconds works fine.

I don’t think that there are so high frequent requests to the echo nodes in my flow. I’m just switching on Bluetooth connection when the echo starts playing music and switching off Bluetooth connection one minute after the echo stops playing music. Still I get this error from time to time.

I tried suddenly with delays, but they are not useful. What instead helped me is using a catch node that catches the error and triggers the node again after a little delay.
I add a catch node for each Amazon node.

If this actually helps, then it should be implemented in the nodes themselves as a recovery mechanism.

Amazon sends a "Rate exceeded: Too many requests." in these cases. I'm thinking about a way to handle this generally. (And to have more helpful errors.)
Also keep in mind that if possible you can also send a command sequence at once with the Node option instead of chaining them.

@586837r this is interesting. I will investigate how to do it

Also keep in mind that if possible you can also send a command sequence at once with the Node option instead of chaining them.
@586837r do you have an example on how we might do that?

What is the actual status of this issue?  I still get this error.
@Myzhar How did you solve this with the catch node?
In my case I just want to set the volume to a special amount.
If the error was triggered I can't get anything beside the error itself. So how did you reenter the given value until it is sent successfully?

What solved the problem to me has been to use de Node tool whithin the Alexa Routine Node instead of branching the flow in Node. You can choose between Serial or Parallel execution

I must add, I believe it's just a "Too Many Requests" error. If you chain several Alexa nodes in serial execution, putting a delay of 1.5 - 2 seconds between them should solce the issue. Putting them in parallel greatly increases the risk of such error. For parallel request, better use the Node setting whithin the Routine Node


Define project outline for 07/02/2020

https://blackboard.aber.ac.uk/webapps/blackboard/content/listContent.jsp?course_id=_23765_1&content_id=_1534710_1

Completed: Documentation/ProjectOutline/Project_Outline.pdf


Incorrect type cast for FutureOr

Dart SDK Version: 2.1.0-dev.2.0
OS: Windows 10 (64 bit)
I am not 100% sure that this is not a duplicate of #34264, however on the firs glance these cases looks different.
The following code sample assign FutureOr variable (without type parameter specified) to int and then prints it:
import "dart:async";

main() {
 FutureOr fff;
 int i = fff;
 print(i);
}

It passes both with analyzer and dart,no compiler errors and dart prints null value here.
I'm just wandering - should not it fail here in the strong mode?
Please note that if I change FutureOr to Future this test starts to fail  both with analyzer and dart,, from my point of view this is expected behavior both for Future and FutureOr.

This is (unfortunately) WAI: https://github.com/dart-lang/sdk/issues/31410.
FutureOr really means FutureOr<dynamic> (https://github.com/dart-lang/sdk/issues/33119), and FutureOr<dynamic> is a poor-man's "union type" of Future<dynamic> and dynamic. Of course, dynamic is statically assignable to int (with a runtime check), and it succeeds because everything is nullable right now (null is valid for anything).
/cc @lrhn if you have anything else to add, but I'll close for now.


Draft: Add Challenge system

Adds the core challenge system

for future reference, this implementation will be based on: https://dl.acm.org/doi/10.1145/1315245.1315318


feat: enable resizing the side panel

The child component is hidden when resizing to speed up rendering
The handle has a 5px+ border around it to help users select it
Removed the code related to transitions as it wasn't working (transitions were activated on transform, transform wasn't used)

looks good! could you provide a minimal gif of the result before merging? Thanks!

done!


Default color

#65

@krsyoung, kindly requesting feedback on my initial attempt

@johnmal-dev sorry for the delay - this looks great! I'll review in detail tomorrow.


Making a change to update the security best practices for app service

Making a change to security best practice doc to handle code deployments securely.

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

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

#label:"aq-pr-triaged"


Is bulk import possible to beeftext?

i'm trying to import to beeftext but it's not accepting my json file. I'm filling out a csv file first, then converting it to json. Am i doing something wrong?

I guess there is a problem with the json format you are using. CSV import will be implemented in a future version. See #104.


fix float index issue

when trying to deserialize from version 2.0.0 of serialization, I encountered a problem in which the shape is saved as float hence causing issues in unpacking. I do not know how it managed to save it as float since I did not interfere with the process but changing it so that we are always passing an int for index and shape

Codecov Report

Merging #597 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master    #597   +/-   ##
======================================
  Coverage    93.5%   93.5%
======================================
  Files          52      52
  Lines        3727    3727
======================================
  Hits         3485    3485
  Misses        242     242

Impacted Files
Coverage Δ

dimod/sampleset.py
94.97% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Invalid MOF definition in DevOps Fundamentals Configuration

Running Server 2016 with what I think is the latest version of this project. In the DevOps Fundamentals configuration getting this error:
Write-NodeMOFFile : Invalid MOF definition for node 'DC1': Exception calling "ValidateInstanceText" with "1"
argument(s): "Undefined class: MSFT_RoleResource
 At line:94, char:2
 Buffer:
onName = "AutoLab";
};^
insta
"
At
C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\PSDesiredStateConfiguration.psm1:2369
char:21
+ ...             Write-NodeMOFFile $Name $mofNode $Script:NodeInstanceAlia ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], InvalidOperationException
    + FullyQualifiedErrorId : InvalidMOFDefinition,Write-NodeMOFFile

Version info:
Name                           Value
----                           -----
PSVersion                      5.1.14393.953
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.953
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Uninstalled the new PSDscResources module introduced in 5.1 and that seems to have removed the errors. There is a duplication of core resources like WindowFeature between PSDesiredStateConfiguration and PSDscResources. We may need to revise configs for PowerShell 5.1 and this new module because this is the direction the PowerShell DSC team is headed.

PSDSCResources does overwrite the in-box resources per their notes in GitHub.  PSDSCResources only runs on 5.1 from what I recall.

I just love all the random breaking updates.  This is going to be addressed in the new version under development. Will leave this issue open for testing.


(bugfix): OCPBUGS-3072 - fix operator-sdk run bundle(-upgrade) PSA related issues

Description of the change:

Update default channel name selection to be different based on using FBC vs SQLite image.
Update the SecurityContext from the registry pod containers created by operator-sdk run bundle(-upgrade) to only be added to the containers when --security-context-config=restricted
Change default of --security-context-config flag to be legacy in anticipation of some OpenShift PSA changes.
Set the CatalogSource.grpcPodConfig.securityContextConfig to the same value of the --security-context-config flag.

Motivation for the change:

Fixes a bug where SQLite bundle images couldn't be properly run due to setting the default channel name to operator-sdk-run-bundle.

This became a problem because we can manipulate FBCs to utilize this default channel, but we can not as easily manipulate the SQLite bundle to do the same.

Fixes a bug where even when specifying --security-context-config=legacy , the registry pod created still set the SecurityContext on the container as if it was in a restricted environment.

Checklist
If the pull request includes user-facing changes, extra documentation is required:

[x] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[x] Add or update relevant sections of the docs website in website/content/en/docs

Fixes a bug where even when specifying --security-context-config=legacy , the registry pod created still set the SecurityContext on the container as if it was in a restricted environment.

@everettraven The SecurityContext was always there even before PSA. So are we saying that if the context is legacy mode that ALL of the security contexts are removed? It might be correct, but I'd make sure to ask that we're not undoing something that was needed before.

The SecurityContext was always there even before PSA. So are we saying that if the context is legacy mode that ALL of the security contexts are removed? It might be correct, but I'd make sure to ask that we're not undoing something that was needed before.

@jmrodri I don't think we ran into this issue previously because we were by default using a container in the pod that wasn't running as root. The problem is that when you specify a specific index image that may be attempting to run as root and set --security-context-config=legacy we were still enforcing PSA in a way that made it so the container is not able to run as root, hence it would fail to run the registry pod.
I haven't taken a look at this for a couple weeks since I was on vacation, so I don't recall if I have tested all possible scenarios. Since I have to fix the failing unit tests I will run through a manual suite of tests again to ensure this is functioning as expected.

/lgtm

/cherry-pick v1.25.x


Changed ripple to monorepo for whole Front end

JIRA issue: https://digital-engagement.atlassian.net/browse/SDPA-2505
Changed

Added nuxt modules into packages
Added example
Added yarn workspaces
Moved ripple components into packages

Note:

More work required to make it stable to use.

Screenshots

CI hasn't been setup so won't work for now.


change exists() on bucket to fallback to ls if cannot list buckets

In anonymous mode, or when accessing a bucket not included in our project, it will not appear in the buckets list (or, indeed, listing buckets may not be possible). In this case, exists() on a bucket should instead attempt to list the bucket and return True if that succeeds.

@asford , interested in implementing this?


Dependencies update 202109

aim to solve all the problems encountered by automatic update dependencies before 202109.

[ ] #73
[ ] #95
[ ] #97
[ ] #98
[ ] #99

It's better to split this PR


Implement UDIM Discard (UV Tile Discarding)

I hesitate slightly submitting this for a couple reasons, but I feel that these changes offer a large benefit that are worth considering!
Being able to selectively cull certain polygons isn't trivial with the current lilToon options, especially if one wants to stay on an Opaque render mode. This PR allows for an early return of the vert function or a calling of clip, if it's in a user-specified UV tile.
This is the MIT-Licensed implementation present in current (8.1) Poiyomi Toon, written by Razgriz ( @rrazgriz , I assume ), that's one hesitation. I take no ownership of their shader code.
I retained the original property names to keep compatibility with tools that already support Poi's names (i.e. VRCFury), otherwise I would have renamed everything to "UV Tile Discard."
And the other hesitation is, I'm pretty sure I missed something! The documentation on lilToonMulti isn't very clear on what it does and why you'd want to use it, so I don't know if I messed up. >.< I also tested with Fur and Gem modes, and they seem to work properly, but I'm again unclear as to when I'd edit their specific .hlsl's and similar.
I used the ID Mask's inclusion commit as a basis as that was the most similar.
Lastly, I'm unsure as to how accurate the "localized" text additions are in lang.txt, those were suggested by Copilot and seemed close enough when passing it through machine translation back into English. I'll make any changes requested, including reverting to English for now.
Thanks in advance for any suggestions, and for the amazing shader!
https://github.com/lilxyzw/lilToon/assets/20761757/ab02a636-c241-4683-961d-c233ca12bb19

Thanks, I merged this feature because it looks nice!


[TEST] longhorn-test pod crashed on aks pipeline when perform test_setting_concurrent_volume_backup_restore_limit[s3]

What's the test to develop? Please describe
longhorn-test pod crashed on aks pipeline

AMD64 build 84,  86
ARM64 build 85

On above 3 builds, longhorn-test pod all crashed during perform test_settings.py::test_setting_concurrent_volume_backup_restore_limit[s3]
test_settings.py::test_setting_concurrent_rebuild_limit PASSED
test_settings.py::test_setting_concurrent_volume_backup_restore_limit[s3] rpc error: code = NotFound desc = an error occurred when try to find container "2c00313210b84355a6f95450856a52327b842fc11acbf7003993783c1b833160": not found++ kubectl get pod longhorn-test '-o=jsonpath={.status.containerStatuses[?(@.name=="longhorn-test")].state}'
++ grep -v terminated
+ [[ -n '' ]]
+ kubectl cp longhorn-test:/tmp/test-report/longhorn-test-junit-report.xml /src/longhorn-tests/test_framework/longhorn-test-junit-report.xml -c longhorn-test-report
error: cannot exec into a container in a completed pod; current phase is Failed

I started another bulild https://ci.longhorn.io/job/private/job/managed-k8s/job/longhorn-tests-aks/87/ with backup store use nfs only to observe the test result.
cc @longhorn/qa
Describe the tasks for the test

Additional context

Sounds weird. The minio image isn't updated for a while.

Update:

Perform entrie regression test with v1.7.x on azure pipeline with nfs backup store only, longhorn-test pods crash while execute test_setting_concurrent_volume_backup_restore_limit
Perfomr only test_setting_concurrent_volume_backup_restore_limit with v1.7.x)  and master image, longhorn-test pods crash while executing test case

I will build longhorn-test images without test_setting_concurrent_volume_backup_restore_limit to run on azure to observe if there are problems. and https://github.com/longhorn/longhorn/issues/9042 for analyze

Skip test_setting_concurrent_volume_backup_restore_limit but longhorn-test pod crashed when perform test_snapshot_hash_detect_corruption_in_global_enabled_mode
test_snapshot.py::test_snapshot_hash_detect_corruption_in_global_enabled_mode snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: checksum in resource=a1379d73b7ebc13a, checksum recalculated=a1379d73b7ebc13a
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: checksum in resource=a1379d73b7ebc13a, checksum recorded=a1379d73b7ebc13a
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: ctime recorded=2024-07-19 23:38:21.143062698 +0000 UTC, ctime=2024-07-19 23:38:21.143062698 +0000 UTC
snapshot ad5060aa-a6f1-4835-8579-a984e6ccf030: checksum in resource=9e4fa8dd1355c834, checksum recalculated=9e4fa8dd1355c834
snapshot ad5060aa-a6f1-4835-8579-a984e6ccf030: checksum in resource=9e4fa8dd1355c834, checksum recorded=9e4fa8dd1355c834
snapshot ad5060aa-a6f1-4835-8579-a984e6ccf030: ctime recorded=2024-07-19 23:37:56.591184978 +0000 UTC, ctime=2024-07-19 23:37:56.591184978 +0000 UTC
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: checksum in resource=a1379d73b7ebc13a, checksum recalculated=a1379d73b7ebc13a
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: checksum in resource=a1379d73b7ebc13a, checksum recorded=a1379d73b7ebc13a
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: ctime recorded=2024-07-19 23:38:21.143062698 +0000 UTC, ctime=2024-07-19 23:38:21.143062698 +0000 UTC
snapshot ad5060aa-a6f1-4835-8579-a984e6ccf030: checksum in resource=9e4fa8dd1355c834, checksum recalculated=9e4fa8dd1355c834
snapshot ad5060aa-a6f1-4835-8579-a984e6ccf030: checksum in resource=9e4fa8dd1355c834, checksum recorded=9e4fa8dd1355c834
snapshot ad5060aa-a6f1-4835-8579-a984e6ccf030: ctime recorded=2024-07-19 23:37:56.591184978 +0000 UTC, ctime=2024-07-19 23:37:56.591184978 +0000 UTC
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: checksum in resource=a1379d73b7ebc13a, checksum recalculated=a1379d73b7ebc13a
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: checksum in resource=a1379d73b7ebc13a, checksum recorded=a1379d73b7ebc13a
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: ctime recorded=2024-07-19 23:38:21.143062698 +0000 UTC, ctime=2024-07-19 23:38:21.143062698 +0000 UTC
snapshot ad5060aa-a6f1-4835-8579-a984e6ccf030: checksum in resource=9e4fa8dd1355c834, checksum recalculated=9e4fa8dd1355c834
snapshot ad5060aa-a6f1-4835-8579-a984e6ccf030: checksum in resource=9e4fa8dd1355c834, checksum recorded=9e4fa8dd1355c834
snapshot ad5060aa-a6f1-4835-8579-a984e6ccf030: ctime recorded=2024-07-19 23:37:56.591184978 +0000 UTC, ctime=2024-07-19 23:37:56.591184978 +0000 UTC
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: checksum in resource=a1379d73b7ebc13a, checksum recalculated=a1379d73b7ebc13a
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: checksum in resource=a1379d73b7ebc13a, checksum recorded=a1379d73b7ebc13a
snapshot 70ef451c-0fcb-4940-92fb-3d6c89c3bb9d: ctime recorded=2024-07-19 23:38:21.143062698 +0000 UTC, ctime=2024-07-19 23:38:21.143062698 +0000 UTC
snapshot 8d4afdb3-a1e6-4f29-8ac7-fba032981536: checksum in resource=d0548269b2af6866, checksum recalculated=d0548269b2af6866
snapshot 8d4afdb3-a1e6-4f29-8ac7-fba032981536: checksum in resource=d0548269b2af6866, checksum recorded=d0548269b2af6866
snapshot 8d4afdb3-a1e6-4f29-8ac7-fba032981536: ctime recorded=2024-07-19 23:38:45.986938893 +0000 UTC, ctime=2024-07-19 23:38:45.986938893 +0000 UTC
10+0 records in
10+0 records out
10 bytes copied, 0.000189499 s, 52.8 kB/s
rpc error: code = NotFound desc = an error occurred when try to find container "fbe5d3b1e142dc6d4a541b76be66ec67bfc67cd40968278e9f8f0535eb0dda5c": not found++ kubectl get pod longhorn-test '-o=jsonpath={.status.containerStatuses[?(@.name=="longhorn-test")].state}'
++ grep -v terminated
+ [[ -n '' ]]
+ kubectl cp longhorn-test:/tmp/test-report/longhorn-test-junit-report.xml /src/longhorn-tests/test_framework/longhorn-test-junit-report.xml -c longhorn-test-report
error: cannot exec into a container in a completed pod; current phase is Failed


fixed readLoop not exiting when exiting channel is closed

I encountered an issue where the read loop would not exit upon an error being received on the error channel which in turn blocked RunContext at wg.Wait().

Thanks for submitting this, however I need to take a closer look - since if the issue is that it's hanging on ReadMessage, adding in this check isn't guaranteed to fix it. It would add a race condition.

I think when I initially wrote this, I think I assumed a ReadWriteCloser would be used and Run would call rwc.Close... that would cause ReadMessage to return an error and eventually exit. However, I didn't do that... so it does need to be fixed somehow.

Merged in ed17aa90a7554ad7578bfa90b27b8378d316ac10
Thanks for submitting this.


feat: add basic proxy

Stacked PRs:

#403
#402
#401
->#400
#399
#398

feat: add basic proxy

closing in favor https://github.com/GoogleCloudPlatform/java-docs-samples/pull/9689