Feature Request: Vast cargo kani output simplification

Requested feature: Improvements to the user (layperson) experience when running cargo kani.
Use case: Folks I'd like to introduce this technology to (Rust developers / evaluators, who I also image is your target user-base) don't have a background in automated reasoning and will likely be turned off by the massive amount of cruft one has to sift through to find out whether or not their code has an issue. Eliding non-relevant information (non-relevant from a user perspective) is also pertinent to CI integration -- "why did this CI run fail?" -- also CI log sizes are typically limited.
Here's an example run on a pretty simple program --
< PRINTED THOUSANDS OF TIMES >
Unwinding loop _RNvXs9_NtNtCs4bv2lBw1mAj_4core4iter5rangeINtNtNtB9_3ops5range14RangeInclusivejENtB5_26RangeInclusiveIteratorImpl9spec_nextCs8cGVXT8IZMx_8aes_rust.2 iteration 1 file /rustc/bc4b39c271bbd36736cbf1c0a1ac23d5df38d365/library/core/src/ops/range.rs line 540 column 9 function <std::ops::RangeInclusive<usize> as std::iter::range::RangeInclusiveIteratorImpl>::spec_next thread 0
Unwinding loop _RNvXs9_NtNtCs4bv2lBw1mAj_4core4iter5rangeINtNtNtB9_3ops5range14RangeInclusivejENtB5_26RangeInclusiveIteratorImpl9spec_nextCs8cGVXT8IZMx_8aes_rust.0 iteration 1 file /rustc/bc4b39c271bbd36736cbf1c0a1ac23d5df38d365/library/core/src/iter/range.rs line 1005 column 12 function <std::ops::RangeInclusive<usize> as std::iter::range::RangeInclusiveIteratorImpl>::spec_next thread 0
Unwinding loop _RNvCs8cGVXT8IZMx_8aes_rust4xorb.0 iteration 15 file /local/packages/aes-rust/src/main.rs line 271 column 3 function xorb thread 0
Unwinding loop _RNvXs9_NtNtCs4bv2lBw1mAj_4core4iter5rangeINtNtNtB9_3ops5range14RangeInclusivejENtB5_26RangeInclusiveIteratorImpl9spec_nextCs8cGVXT8IZMx_8aes_rust.2 iteration 1 file /rustc/bc4b39c271bbd36736cbf1c0a1ac23d5df38d365/library/core/src/ops/range.rs line 540 column 9 function <std::ops::RangeInclusive<usize> as std::iter::range::RangeInclusiveIteratorImpl>::spec_next thread 0
Unwinding loop _RNvXs9_NtNtCs4bv2lBw1mAj_4core4iter5rangeINtNtNtB9_3ops5range14RangeInclusivejENtB5_26RangeInclusiveIteratorImpl9spec_nextCs8cGVXT8IZMx_8aes_rust.0 iteration 1 file /rustc/bc4b39c271bbd36736cbf1c0a1ac23d5df38d365/library/core/src/iter/range.rs line 1005 column 12 function <std::ops::RangeInclusive<usize> as std::iter::range::RangeInclusiveIteratorImpl>::spec_next thread 0
Unwinding loop _RNvCs8cGVXT8IZMx_8aes_rust4xorb.0 iteration 16 file local/packages/aes-rust/src/main.rs line 271 column 3 function xorb thread 0
Unwinding loop _RNvXs9_NtNtCs4bv2lBw1mAj_4core4iter5rangeINtNtNtB9_3ops5range14RangeInclusivejENtB5_26RangeInclusiveIteratorImpl9spec_nextCs8cGVXT8IZMx_8aes_rust.1 iteration 1 file /rustc/bc4b39c271bbd36736cbf1c0a1ac23d5df38d365/library/core/src/iter/range.rs line 1005 column 12 function <std::ops::RangeInclusive<usize> as std::iter::range::RangeInclusiveIteratorImpl>::spec_next thread 0
Unwinding loop memcmp.0 iteration 1 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 2 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 3 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 4 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 5 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 6 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 7 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 8 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 9 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 10 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 11 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 12 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 13 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 14 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 15 file <builtin-library-memcmp> line 25 function memcmp thread 0
Unwinding loop memcmp.0 iteration 16 file <builtin-library-memcmp> line 25 function memcmp thread 0
Runtime Symex: 255.182s
size of program expression: 2812596 steps
slicing removed 1853734 assignments
Generated 972478 VCC(s), 155801 remaining after simplification
Runtime Postprocess Equation: 2.46339s
Passing problem to propositional reduction
converting SSA
Runtime Convert SSA: 225.859s
Running propositional reduction
Post-processing
Runtime Post-process: 2.4369e-05s
Solving with MiniSAT 2.2.1 with simplifier
15248398 variables, 31897971 clauses
SAT checker: instance is SATISFIABLE
Runtime Solver: 81.1218s
< HANG FOR AN INDEFINITE PERIOD OF TIME >

Information such as _RNvXs9_NtNtCs4bv2lBw1mAj_4core4iter5rangeINtNtNtB9_3ops5range14RangeInclusivejENtB5_26RangeInclusiveIteratorImpl9spec_nextCs8cGVXT8IZMx_8aes_rust.0 iteration 1 file is better guarded by your verbose/debug output flags. As well, top says cbmc has been running for 20 minutes, and I have no idea what's it's trying to solve.
Some suggestions would be to have cargo kani (the default way to run the tool) output only information relevant to a layperson and ensure that operations that may take time are prefixed w/ some indication of that.

Folks I'd like to introduce this technology to (Rust developers / evaluators, who I also image is your target user-base) don't have a background in automated reasoning and will likely be turned off by the massive amount of cruft one has to sift through to find out whether or not their code has an issue.

Understood and we're in complete agreement.
There is some amount of difficulty here: one problem we have to cope with (somehow) is that unwinding can sometimes fail to terminate. We actually made a significant improvement here recently in that this output gets written out as it comes, and not all buffered up until the "end." (which may never come!)
So there's a balance that needs striking where we DO need to provide some kind of output from cbmc "live" so that this failure mode can be spotted. But obviously it needs to be better.
What's more, a lot of this output from CBMC is just strings, so we'll probably have to bite the bullet and parse things here...

Thanks @tedinski!
Since there are plans for other backends, rather than parsing CBMC output have you considered a backend management layer that would, by default, elide all output from the backend and respond generically, for example:
Working on proving 'assert(x == y)` in `myfile.rs` line 12 using backend `CBMC`.
  Starting symbolic execution.
    Unwinding loops in function 'f'.
  Symbolic execution complete in 28.125s.
  Discharging 47 safety proofs.
  Safety proofs discharged in 3.401s.
  Discharging main assertion `assert(x == y)`.
  Assertion discharged in 2.401s.
Proved 'assert(x == y)` in `myfile.rs` line 12 in 34.9.27s

And, if there are any errors along the way then Kani could report them generically, such as "Symbolic execution failed, rerun with --verbose_sym = 1 to see more information about the failure."

Totally agree! We appreciate the feedback. We've been putting some effort into simplifying the output, but there's still a lot to be done. One related issue is https://github.com/model-checking/kani/issues/1194, which we should perhaps turn into an RFC and gather user feedback on what they would like to see (and not see!).

Totally agree! We appreciate the feedback. We've been putting some effort into simplifying the output, but there's still a lot to be done. One related issue is #1194, which we should perhaps turn into an RFC and gather user feedback on what they would like to see (and not see!).

Thanks for the pointer to #1194. I'll close this issue in favor of that and a potential RFC.


Fix up styling of Popup in carbon skin

Decide on and implement the right layout and colors for a popup in carbon
Current:

@ryanjduffy  and @Djspaceg  to discuss this further and add detailed requirements


[api] expose allowed tags for a request workflow

Created a virtual_column for allowed_tags which is required in order to populate the tags tree in the Request Workflow in SUI
api/requests/<id>?attributes=v_allowed_tags
https://www.pivotaltracker.com/n/projects/1914499/stories/137139937

@imtayadeway Can you please review this when you get a chance? Thanks!

/cc @chriskacerguis

In general I'm ok with this, short of the rubocop warning above.
Just curious, could you get that information today without this PR via:
  GET /api/requests/:id?attributes=workflow.allowed_tags

Thanks.

GET /api/requests/:id?attributes=workflow.allowed_tags

@abellotti Interesting! However, that did not work. I got this --
{
  "error": {
    "kind": "internal_server_error",
    "message": "undefined method `has_attribute?' for ManageIQ::Providers::Vmware::InfraManager::ProvisionWorkflow:Class\nDid you mean?  class_attribute",
    "klass": "NoMethodError"
  }
}

@abellotti  As far as the rubocop warning goes, I think we could ignore it.
I have deliberately added the spacing for readability like all the other virtual_columns on top that use :uses
 virtual_column  :reason,               :type => :string,   :uses => :miq_approvals
 virtual_column  :v_approved_by,        :type => :string,   :uses => :miq_approvals
 virtual_column  :v_approved_by_email,  :type => :string,   :uses => {:miq_approvals => :stamper}
 virtual_column  :stamped_on,           :type => :datetime, :uses => :miq_approvals

Maybe I could move this newly added virtual column on top with the others that have :uses

@AparnaKarve thanks for checking.
This LGTM!!
@imtayadeway thoughts/input ?

👍


fix Gateway name in TLSRoute invalid reference grant test

What type of PR is this?
/kind test
Optionally add one or more of the following kinds if applicable:
/kind failing-test
/area conformance
What this PR does / why we need it:
Fixes Gateway name to be consistent between
YAML and Go, and to not conflict with other
TLSRoute tests.
(See https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/tests/tlsroute-invalid-reference-grant.go#L45 for where Gateway name is referenced).
Which issue(s) this PR fixes:

Fixes # NA
Does this PR introduce a user-facing change?:

NONE

Thanks @skriss!
/lgtm
/approve


Dev bst

as requested,

branch was rebased to master

all commits on the feature branch squashed in to 2 commits, 1 for bma253, and another for new driver bmp388

thanks for the comments, all those suggestions would be incorporated in the new PR.
this PR has been closed.


using 2 source language with different vocabalury

In the example script for multilingual NMT, French and German are the 2 source languages. I am trying to replace them with 2 Indian languages. Is it required that the 2 languages must contain common or shared vocab. It will be helpful if someone let me know about the required conditions?

@pipibjc

Please give some idea about it

@PC09, current implementation doesn't support different vocabulary sets for different source languages. We only allow source (encoder) and target (decoder) to use different vocabulary set.
The common practice is to build a shared vocabulary set for all source languages (or source+target). We can choose share/not share encoder vocabulary embeddings during training.

In the example script for multilingual NMT, French and German are the 2 source languages. I am trying to replace them with 2 Indian languages. Is it required that the 2 languages must contain common or shared vocab. It will be helpful if someone let me know about the required conditions?

Sharing vocabulary helps if the scripts are not too different (I have not worked with very different scripts). Plus if you have shared vocabulary it can handle sentences with code-switching.
Read more about it here.
Google's Multilingual Neural Machine Translation System: Enabling Zero-Shot Translation

Closing due to inactivity.


CLOUD-46413 SPI resource builder documentation

@akanto

Jenkins build failed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1734/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1735/


(bug) short-hand module declaration not working in combination with 'noImplicitAny'

TypeScript Version:  2.1.0-dev.2016080
Code
Trying to declare a module with the new short-hand syntax like this:
  declare module 'lodash';

leads to the following TypeScript-Compiler error
error TS7005: Variable ''lodash'' implicitly has an 'any' type.

I also can't find a way to make this "explicit any".
Expected behavior:
new shorthand syntax for module-declaration should also work with 'noImplicitAny' activated

Actually from the source code

// Ambient shorthand module is an implicit any

At the very least, the error message you got is bad.
@mhegazy @andy-ms do we really want to consider this an implicit any? The entire point of noImplicitAny was to warn when the type system couldn't figure out the type of something. Here, you didn't expect the type system to figure anything out. You just wanted it to be quiet about something else and it yelled at you about your fix. The solution isn't any better than the original problem.

I don't see why we should make you write a type annotation either. It's just ceremony and the thing you have to write is very awkward.

but the module import is typed implicitly as any. how is this different from declare var $. we force you to write :any or it is an error.

the question here is why use declare module 'lodash'; instead of including the declaration file for lodash?

@mhegazy I would be happy, If I could say
declare module 'myuntypedmodule' : any;

but AFAIK there is just no way to do this. lodash was just an example. We are integrating a lot of legacy libs in our project, so this is where this short-hand syntax could be useful.


Building the browser demo fails

Following the instructions in bin/node/cli/browser-demo, I get:
./build.sh: 3: ./build.sh: wasm-bindgen: not found
/usr/bin/python: No module named http
swader@DESKTOP-0OEAV37:~/repos/substrate/bin/node/cli/browser-demo$ cargo install wasm-bindgen
    Updating crates.io index
error: specified package `wasm-bindgen v0.2.60` has no binaries
swader@DESKTOP-0OEAV37:~/repos/substrate/bin/node/cli/browser-demo$

cc @expenses

Hi, try cargo install wasm-bindgen-cli instead!


Recalculate a user's business case when the market model is updated

Fixes: #1422

I added a control group in the specs to validate that no other business cases are being reset. I also moved the relevant code to a separate service.

LGTM; thanks! :+1:


Add delete cache API endpoint

Equivalent to clearing your browsing history.

Coverage decreased (-0.03%) to 26.039% when pulling 8e8ff082d8cc126306ae8708610a30de2f9e5347 on cache into f1a04218edff7c94b6d5efad47db8c7c6576eacf on master.


Missing characters in time travel video

When pausing the time travel video in the readme, I noticed lots of missing characters at several points on the timeline. Is that from an older buggier version, or is it still an issue?
That little worry aside, Loro looks really promising! You've got an early adopter here.

Thanks for your interest! Yes, it’s from a more buggy version. We’ve fixed a few bugs related to time travel and added new fuzzing tests to cover more corner cases caused by the combination of time travel and collaboration.


Error:  attribute x: Expected length, "NaN"

I'm trying to display a stacked vertical bar series and am receiving the error:

Error:  attribute x: Expected length, "NaN".

The code being used to render the graph is as follows:

            <XYPlot
              margin={{left: 50,bottom: 100}}
              xType="time"
              yType="linear"
              height={300}
              width= {500}
              stackBy="y"
            >
            <XAxis tickLabelAngle={-90} />
            <YAxis/>
            <VerticalBarSeries data={this.props.additionStats}/>
            <VerticalBarSeries data={this.props.deletionStats}/>
            </XYPlot>

And the props being passed have the following form:
0: {x: Sun May 26 2013 01:00:00 GMT+0100 (Irish Standard Time), y: 45515}
1: {x: Sun Jun 02 2013 01:00:00 GMT+0100 (Irish Standard Time), y: 5842}
2: {x: Sun Jun 09 2013 01:00:00 GMT+0100 (Irish Standard Time), y: 4934}
3: {x: Sun Jun 16 2013 01:00:00 GMT+0100 (Irish Standard Time), y: 1019}

The date objects are generated using:
 var date = new Date(data[entry][0] * 1000);

Where data[entry][0] is a 10-digit timestamp returned from the GitHub API in the form<PHONE_NUMBER>.

Solved this issue, turns out VerticalBarSeries don't seem to support date objects for the X values, instead I had to use a VerticalRectSeries as follows:

        <XYPlot
          margin={{left: 50,bottom: 100}}
          xType="time"
          height={300}
          width= {500}
          stackBy="y"
        >
        <XAxis tickLabelAngle={-90}/>
        <YAxis/>
        <VerticalRectSeries data={this.props.additionStats} />
        <VerticalRectSeries data={this.props.deletionStats} />
        </XYPlot>


Execute method must be of type int in Magento 2.4.6

Magento 2.4.6, PHP 8.2
After end process of bin/magento ok:urlrewrites:regenerate
There is an error in /.../vendor/symfony/console/Command/Command.php at line: 301
Return value of "OlegKoval\RegenerateUrlRewrites\Console\Command\RegenerateUrlRewrites::execute()" must be of the type int, "null" returned.#0
https://github.com/olegkoval/magento2-regenerate_url_rewrites/issues/165
as per: vendor/symfony/console/Command/Command.php
protected function execute @return int 0 if everything went fine, or an exit code
so to fix this error we just need to add return 0; at the end of execute() function in vendor/olegkoval/magento2-regenerate-url-rewrites/Console/Command/RegenerateUrlRewrites.php

Can I have the contributor badge now? :grin:


Fluid input/output not working correctly (steam deck user)

Having an issue where the fluid direction arrow isn’t changing the exterior of the factory output into an input. Also, i can’t rotate the interior pipe i can only vertically flip it which changes the arrows direction but doesn’t update the exterior output into an input.
Also, the interior pipe says: “not set” to change transfer direction. I have a feeling steam deck controls aren’t registering properly with the mod? (Vertically flipping)

So, i found the issue! (More like was told the problem) most mods dont have default key binds for controller users! Which includes this mod. I guess a simple fix is just to add some default key binds like:
Down arrow: decrease connection speed
up arrow: increase connection speed
Right arrow: change connection direction


Add template name to bot event

Proposed changes:
Closes #4424

Added the template_name to metadata of BotUttered object

Changes Made:

The default behavior of the method run of the class ActionUtterTemplate was changed to add the template_name inside the message dict. This will make the function create_bot_utterance(message) always add the template_name into a BotUttered object;
Some tests needed to be changed, especially those which assert events of type BotUttered.

Status (please check what you already did):

[ ] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog
[x] reformat files using black (please check Readme for instructions)

Thanks for the PR, @ViniciusBernardo! In the future, it would be great if you would write on the issue that you're interested in working on that specific issue, so that someone can assign it to you and others will know it is already being worked on.
One question: did you install black via pip install -r requirements.txt? It looks like black changed some files you haven't touched, which shouldn't happen if you're on the same version we are.
I notice the PR is still a WIP, please add a comment when it is ready for review so that I don't miss it 😄

Sorry, my bad, next time I will write on the issue. About the black package, I installed again using pip install -r requirements-dev.txt and it only changed the files that I touched. I will ammend the modification into the last commit and force the update of the branch. Thanks for the advises!

Regarding the implementation:

I think some sort of template-id should be an event property and not part of the metadata
every BotUttered event should get this information (you currently implemented it only for utter actions, but there are other actions which use templates as well and create bot utterances)

@tmbo, I think I added the template_name to all actions that create BotUttered events. About the template_id. Do you think it would be a great idea to add an attribute called template_id to the class BotUttered? This way, I would be able to remove the template_name from the metadata and set the template_id attribute of the event as the template_name.

Do you think it would be a great idea to add an attribute called template_id to the class BotUttered? This way, I would be able to remove the template_name from the metadata and set the template_id attribute of the event as the template_name.

Not sure if @tmbo will get back to this, but seems like a solid solution to I think some sort of template-id should be an event property and not part of the metadata

@erohmensing, Thanks for the feedback. I will try to add an attribute called template-id at the BotUttered. When I finish I will notify you for another review.

needed some additional changes, will be merged as part of #5836


Test for InstructLab PR

If your PR is related to a contribution to the taxonomy, please, fill
out the following questionnaire. If not, replace this whole text and the
following questionnaire with whatever information is applicable to your PR.
Describe the contribution to the taxonomy

A knowledge skill about using the InstructLab CLI.
Contribution checklist

[x] The contribution was tested with ilab generate
[x] No errors or warnings were produced by ilab generate
[x] All commits are signed off (DCO)
[x] The qna.yaml file contains at least 5 seed_examples
[x] The qna.yaml file was linted and prettified (yaml-validator can do both)
[x] An attribution.txt file in the same folder as the qna.yaml file
[x] Content does not include PII or otherwise sensitive or confidential information
[x] Content does not include anything documented in the project's Avoid these Topics guidelines

@instructlab-bot precheck

@instructlab-bot generate

There are some issues with the generated data. Submitter will update to try again.

Hi! :wave:
With the new update and release of 0.18.0, our base knowledge submissions have drastically changed. This has given us an opportunity to significantly improve the accuracy of our fine-tuned models, which is a major win for our community!
But alas, that has caused some changes that this PR isn't able to continue forward. We greatly appreciate the work you've put into this, and wish we could accept it but the amount of work to get it to be version: 3 is unrealistic for us to ask.
If you do want to do this, please don't hesitate to take the qna.yaml update it, and build it out. Otherwise, we hope you come back to our community with a new submission and help build out our Open Source community-driven LLM.
If you have any questions directly, please don't hesitate to comment on the PR or email me at awesomeATinstructlab.ai (yes, really), and I'll do my best to answer your questions.


Add host dependency path via -L for cargo_test.

Proc-macro crates' dependencies in the host dependency directory cannot
be found when running cargo test with the --target {target} flag
set as reported in #4224. This adds the host dependency directory to the
search path to find those missing dependencies with -L when building tests
and adds a test case that fails before and passes after this patch.
A new function find_host_deps(..) is added to accomplish this which can
determine the path of the host dependencies directory from within
run_doc_tests(..) where the missing library search path is needed.
Fixes #4224
Fixes #4254
Modeled after a similar patch: a298346d6e8862992be3fd93dd8a6c833cc72719
Concerns
The test case seems to require a non-local crate from crates.io to example the failure before this patch. Couldn't make it fail with simply another local subcrate, but if others think it's possible that'd be great. This means that during tests for the cargo project itself that this test case actually downloads and compiles a crate, which I don't think any other tests do and is obviously not ideal and is perhaps even unacceptable. I've used the base64 crate pretty arbitrarily, but which crate it is really doesn't matter to test the case's content. So if anyone knows a tiny or empty crate on crates.io to use instead that'd speed this up and if someone can figure out how to make it fail before this patch is applied without downloading an external crate that would help as well.
Also, I'm not 100% confident about the find_host_deps(..) style and whether it's the best way to find the host dependencies directory with just the TestOptions and Compilation structs available since I'm new to this project. Any comments are appreciated.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks so much for the PR!

I've removed the find_host_deps(..) function and added a host_deps_output field to the Compilation struct instead that is similar to the deps_output field. I noted that the field is somewhat identical to plugins_dylib_path and is initialized in the same place with the same value even. But I was thinking this is used for different reasons and maybe it's best to be different? Not sure if you want me to just use plugins_dylib_path and rename it or something.
Also, there is a confusing problem with the Package::new(..).publish() method you suggested and I switched to. It seems to make the test case no longer actually test the case! When I comment out the lines in run_doc_tests(..) where the host deps directory linkage is added, it still passes! However, if I add a base64 dependency to proc_macro_dep/Cargo.toml and an extern crate base64 in proc_macro_dep/src/lib.rs, it WILL test the case again and commenting out the lines causes a failure.
No idea what is going on with that tbh. Seems I genuinely might need an external crates.io crate... or maybe I'm just confused haha

Hm can you gist the error you see with the base64 crate? https://github.com/rust-lang/cargo/issues/4224 seems to indicate the failure is when you cargo test a proc-macro crate itself?
Also yeah actually, let's stick to using plugins_dylib_path or just renaming that to host_deps_output!

Here is an explanatory gist with 1. the exact lines commented out,  2. the exact code for the altered test case, and 3. the error output.

I tried adding a dependency below dep_of_proc_macro_dep in the same way using Package::new(..).publish() and specifying a Cargo.toml and lib.rs for dep_of_proc_macro_dep that externs the dependency and it just won't fail. With and without commented out lines in the source, I have never seen it fail unless adding an external crate like base64 still.

I've made the choice and pushed a commit to remove the plugins_dylib_path field entirely and replaced it with host_deps_output in the single place it is used. I think host_deps_output is more general and has a more clear relationship to the deps_output field when used in places like run_doc_tests(..).

Oh I think I see what's going on, try doing:
Package::new("foo", "0.1.0").publish();
Package::new("bar", "0.1.0")
    .dep("foo", "0.1")
    .file("src/lib.rs", "extern crate foo;")
    .publish();

and then have the procedural macro depend on bar?

You're right that did it! Thank you so much for helping me figure all this out.
If the CI testing passes, I think this PR is done then. Let me know if you want me to squash the last little commit or anything like that.

@bors: r+
Nice!
Nah leaving as is is fine by me :)

:pushpin: Commit 95c6e68 has been approved by alexcrichton

:hourglass: Testing commit 95c6e68f9e71d9119c58f992a51ad752d205bfda with merge f519d3de318269754c331be006ce7dc0eaeb5004...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing f519d3de318269754c331be006ce7dc0eaeb5004 to master...


Fail to run example code with Raspberry Pi

Description
With a fresh Raspbian install on a Raspberry Pi 4 I'm not able to run this example. Would be nice to have a pre compiled wheel for Raspberry that includes the OpenCV. I tried to build the MXNet from the source, but I'm having an error as well.
Environment info
----------Python Info----------
Version      : 3.7.3
Compiler     : GCC 8.2.0
Build        : ('default', 'Apr  3 2019 05:39:12')
Arch         : ('32bit', 'ELF')
------------Pip Info-----------
Version      : 18.1
Directory    : /usr/lib/python3/dist-packages/pip
----------MXNet Info-----------
Version      : 1.5.0
Directory    : /home/pi/.local/lib/python3.7/site-packages/mxnet
Commit hash file "/home/pi/.local/lib/python3.7/site-packages/mxnet/COMMIT_HASH" not found. Not installed from pre-built package or built from source.
Library      : ['/home/pi/.local/lib/python3.7/site-packages/mxnet/libmxnet.so']
Build features:
No runtime build feature info available
----------System Info----------
Platform     : Linux-4.19.57-v7l+-armv7l-with-debian-10.0
system       : Linux
node         : raspberrypi
release      : 4.19.57-v7l+
version      : #1244 SMP Thu Jul 4 18:48:07 BST 2019
----------Hardware Info----------
machine      : armv7l
processor    :
Architecture:        armv7l
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
Vendor ID:           ARM
Model:               3
Model name:          Cortex-A72
Stepping:            r0p3
CPU max MHz:         1500.0000
CPU min MHz:         600.0000
BogoMIPS:            270.00
Flags:               half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
----------Network Test----------
Setting timeout: 10
Timing for MXNet: https://github.com/apache/incubator-mxnet, DNS: 0.0327 sec, LOAD: 0.5603 sec.
Timing for Gluon Tutorial(en): http://gluon.mxnet.io, DNS: 0.0068 sec, LOAD: 0.2168 sec.
Timing for Gluon Tutorial(cn): https://zh.gluon.ai, DNS: 0.0319 sec, LOAD: 0.6907 sec.
Timing for FashionMNIST: https://apache-mxnet.s3-accelerate.dualstack.amazonaws.com/gluon/dataset/fashion-mnist/train-labels-idx1-ubyte.gz, DNS: 0.0062 sec, LOAD: 0.3093 sec.
Timing for PYPI: https://pypi.python.org/pypi/pip, DNS: 0.1843 sec, LOAD: 0.5646 sec.
Timing for Conda: https://repo.continuum.io/pkgs/free/, DNS: 0.0092 sec, LOAD: 0.1116 sec.
----------Environment----------

Error Message:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/pi/.local/lib/python3.7/site-packages/gluoncv/data/transforms/presets/yolo.py", line 99, in load_test
    imgs = [mx.image.imread(f) for f in filenames]
  File "/home/pi/.local/lib/python3.7/site-packages/gluoncv/data/transforms/presets/yolo.py", line 99, in <listcomp>
    imgs = [mx.image.imread(f) for f in filenames]
  File "/home/pi/.local/lib/python3.7/site-packages/mxnet/image/image.py", line 83, in imread
    return _internal._cvimread(filename, *args, **kwargs)
  File "<string>", line 35, in _cvimread
  File "/home/pi/.local/lib/python3.7/site-packages/mxnet/_ctypes/ndarray.py", line 92, in _imperative_invoke
    ctypes.byref(out_stypes)))
  File "/home/pi/.local/lib/python3.7/site-packages/mxnet/base.py", line 252, in check_call
    raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: [00:10:34] /work/mxnet/src/io/image_io.cc:249: Build with USE_OPENCV=1 for image io.

Stack trace returned 8 entries:
[bt] (0) /home/pi/.local/lib/python3.7/site-packages/mxnet/libmxnet.so(dmlc::StackTrace()+0x34) [0xadf0aacc]
[bt] (1) /home/pi/.local/lib/python3.7/site-packages/mxnet/libmxnet.so(dmlc::LogMessageFatal::~LogMessageFatal()+0x30) [0xadf0adb0]
[bt] (2) /home/pi/.local/lib/python3.7/site-packages/mxnet/libmxnet.so(mxnet::io::Imread(nnvm::NodeAttrs const&, std::vector<mxnet::NDArray, std::allocator<mxnet::NDArray> > const&, std::vector<mxnet::NDArray, std::allocator<mxnet::NDArray> >*)+0x3c) [0xae059d38]
[bt] (3) /home/pi/.local/lib/python3.7/site-packages/mxnet/libmxnet.so(mxnet::Imperative::Invoke(mxnet::Context const&, nnvm::NodeAttrs const&, std::vector<mxnet::NDArray*, std::allocator<mxnet::NDArray*> > const&, std::vector<mxnet::NDArray*, std::allocator<mxnet::NDArray*> > const&)+0x1b4) [0xae0389a0]
[bt] (4) /home/pi/.local/lib/python3.7/site-packages/mxnet/libmxnet.so(MXImperativeInvokeImpl(void*, int, void**, int*, void***, int, char const**, char const**)+0x3b4) [0xadf31314]
[bt] (5) /home/pi/.local/lib/python3.7/site-packages/mxnet/libmxnet.so(MXImperativeInvokeEx+0x80) [0xadf32240]
[bt] (6) /usr/lib/arm-linux-gnueabihf/libffi.so.6(ffi_call_VFP+0x54) [0xb64d8cc0]
[bt] (7) /usr/lib/arm-linux-gnueabihf/libffi.so.6(ffi_call+0x154) [0xb64d96cc]

Minimum reproducible example
I've followed this installation guide.

Steps to reproduce

Execute this example.

What have you tried to solve it?

Tried to build from source, but without success as well.

Which pip package did you use?

Which pip package did you use?

This one. It's on the installation guide on this page.

This one. It's on the installation guide on this page.

Still error after successfully installed on respberry pi 4b, ubuntu 19.10.1 Python3.6
>>> import mxnet
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/ubuntu/.local/lib/python3.6/site-packages/mxnet/__init__.py", line 24, in <module>
    from .context import Context, current_context, cpu, gpu, cpu_pinned
  File "/home/ubuntu/.local/lib/python3.6/site-packages/mxnet/context.py", line 24, in <module>
    from .base import classproperty, with_metaclass, _MXClassPropertyMetaClass
  File "/home/ubuntu/.local/lib/python3.6/site-packages/mxnet/base.py", line 213, in <module>
    _LIB = _load_lib()
  File "/home/ubuntu/.local/lib/python3.6/site-packages/mxnet/base.py", line 204, in _load_lib
    lib = ctypes.CDLL(lib_path[0], ctypes.RTLD_LOCAL)
  File "/usr/local/lib/python3.6/ctypes/__init__.py", line 348, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /home/ubuntu/.local/lib/python3.6/site-packages/mxnet/libmxnet.so: wrong ELF class: ELFCLASS32

hi, i'm getting the same error as you on my raspberry pi 3b, until Friday i will compile mxnet and try to create a wheel. I will give my best !

hi, i'm getting the same error as you on my raspberry pi 3b, until Friday i will compile mxnet and try to create a wheel. I will give my best !

To compile with no issues for the raspberry pi, at least for what i tested, add to the cmake command this parameters:
- DCMAKE_C_COMPILER=gcc-4.9 -DCMAKE_CXX_COMPILER=g++-4.9.
This will force the use of version 4.9. I tested using the demo.py file and a yolo.py example.

hi, i'm getting the same error as you on my raspberry pi 3b, until Friday i will compile mxnet and try to create a wheel. I will give my best !

To compile with no issues for the raspberry pi, at least for what i tested, add to the cmake command this parameters:
- DCMAKE_C_COMPILER=gcc-4.9 -DCMAKE_CXX_COMPILER=g++-4.9.
This will force the use of version 4.9. I tested using the demo.py file and a yolo.py example.

Compiling worked, many thanks!
After everything was compiled, just ran python3 setup.py install --user under mxnet/python, then the mxnet lib would be successfully installed.

@aGiant or @pedrooct Could you kindly share the reference link for the complete set of instructions for building mxnet on raspberry pi. Thanks

@aGiant or @pedrooct Could you kindly share the reference link for the complete set of instructions for building mxnet on raspberry pi. Thanks

HI, i created this tutorial: https://medium.com/@ce4theguys/how-to-compile-mxnet-for-raspberry-pi-fast-7e397c7c8a36
Be careful, the new version of mxnet is broken on compile, use version 1.5.1
Hope this helps!

@pedrooct Thanks for the medium article, it helped a lot. I tried building mxnet on rpi itself and unfortunately it seems that the device seems to get hanged in the process and everything gets stuck. However , the process you mentioned for emulating worked perfectly. Can the build on the emulated distro be transferred to rpi directly and used as is ? Thanks

@pedrooct Thanks for the medium article, it helped a lot. I tried building mxnet on rpi itself and unfortunately it seems that the device seems to get hanged in the process and everything gets stuck. However , the process you mentioned for emulating worked perfectly. Can the build on the emulated distro be transferred to rpi directly and used as is ? Thanks

HI### i'm glad it helped you. Responding to the first statement, to compile it on the rpi(1/2gb) you need to increse swap memory to 2 or 3 gb. Responding to the question, when you finish the process of building the libmxnet.so you can just copy the mxnet folder to the raspberry pi and install it with pip as in the tutorial.
Hope this helps you futher.

@pedrooct Thanks for the detailed instructions it worked out like a charm.
I had one additional query regarding compiling mxnet with NNPACK. According to the instructions at here, we need to make updates to the config.make file. However since you have used the cmake based flow, is there an equivalent version for compiling with NNPACK utilizing cmake instead.

@pedrooct Thanks for the detailed instructions it worked out like a charm.
I had one additional query regarding compiling mxnet with NNPACK. According to the instructions at here, we need to make updates to the config.make file. However since you have used the cmake based flow, is there an equivalent version for compiling with NNPACK utilizing cmake instead.

Sorry for the late response. I never tested NNPACK but it is something i will look into. I think rpi 3 1gb is armv6 so probably won't work, rpi4 probably will work but try it and report it :) !


AttributeError: 'XXXXX' object has no attribute 'YYYYY' only in aws lambda function

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the SQLModel documentation, with the integrated search.
[X] I already searched in Google "How to X in SQLModel" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to SQLModel but to Pydantic.
[X] I already checked if it is not related to SQLModel but to SQLAlchemy.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
class CoursePostgresORM(SQLModel, table=True):
    __tablename__ = 'courses'
    __table_args__ = {'schema': 'course_catalog', }
    id_: str = Field(alias='id', sa_column=Column('id', primary_key=True))

    regions: List['CourseRegionLinkPostgresORM'] = Relationship(back_populates='course')

class RegionPostgresORM(SQLModel, table=True):
    __tablename__ = 'regions'
    __table_args__ = {'schema': 'public', }
    id_: int = Field(sa_column=Column('id', primary_key=True))

    courses: List['CourseRegionLinkPostgresORM'] = Relationship(back_populates='region')

class CourseRegionLinkPostgresORM(SQLModel, table=True):
    __tablename__ = 'courses_regions'
    __table_args__ = {'schema': 'course_catalog', }
    course_id: str = Field(foreign_key='course_catalog.courses.id', primary_key=True)
    region_id: int = Field(foreign_key='public.regions.id', primary_key=True)
    modified_at: datetime
    created_at: datetime

    course: 'CoursePostgresORM' = Relationship(back_populates='regions')
    region: 'RegionPostgresORM' = Relationship(back_populates='courses')

def lambda_handler(event, context):
    """
    This LF responsible for syncing joint tables.
    """
    LOGGER.info(msg='Updating course-region table...')
    with Session(POSTGRES) as session:
        results = session.exec(select(CourseRegionLinkPostgresORM))
        first_row = results.fetchall()[0]
        print(first_row.region)

Description
I encountered some issue where I was thrown with AttributeError: 'XXXXX' object has no attribute 'YYYYY' while trying to access an Relationship attribute of a model in aws lambda function. I was able to run the above code fine on my local but it would produced the following error in an AWS lambda function.
AttributeError: 'CourseRegionLinkPostgresORM' object has no attribute 'region'. Any thoughts are welcome. I've got stuck for the whole day. Thanks!
Operating System
Other
Operating System Details
AWS lambda function
SQLModel Version
0.0.6
Python Version
3.7
Additional Context
No response

What version of SQLAlchemy is being used in AWS Lambda? Perhaps you bumped into https://github.com/tiangolo/sqlmodel/issues/315?

What version of SQLAlchemy is being used in AWS Lambda? Perhaps you bumped into https://github.com/tiangolo/sqlmodel/issues/315?

@byrman , thanks for pointing me to it! By pinning my sqlalchemy to .34, the code works fine again!


Usage of astyle

Currently, the astyle command - together with the astyle option, is placed inside a Makefile (i.e. the Makefile for canpie-fd tests). This has two drawbacks:

the Unity files are modified, which is not desired
the QCan classes are not changed (i.e. files which are not under control of a Makefile, but of qmake)

Possible solution:
Create an astyle.rc file which holds all settings and call astyle  --options=astyle.rc <file>manually. This allows an individual checking and beautifying of the files.

That is nice idea to have one central command file, that can be used by different builder/makfiles for corresponding project files.

Hello, It is possible to exclude specific  files or folder with
--exclude=(path to folder)


Custom Configurations Unsupported

Hello, and thank you for this fantastic extension. I've been running into an issue with defining custom configurations beyond Debug and Release for my project.
In my use case I have two separate debug configurations, Debug, used for local debugging, and Debug_Staging that defines some constants that let me debug against our staging environment.
Changing the active configuration in the status bar of VS Code always results in the Debug configuration being built, and the configuration selection in the status bar that I believe is associated with DotNet.Meteor only ever gives the options of Debug or Release.
I have attempted to handle this configuration change via VS Code Tasks using args to change the configuration being built. This works to build that configuration, however DotNet.Meteor still tries to launch the last build completed with Debug (/bin/Debug/) instead of Debug_Staging (/bin/Debug_Staging/).
I tried to work around this by changing the build path for Debug_Staging to build into /bin/Debug, which works, however after the build completes and launches it hangs on the app splash screen indefinitely with no errors and nothing of particular relevance logged. Building with Debug instead of Debug_Staging works fine. Additionally building and running the configuration through the dotnet cli using dotnet build -t:Run -f net8.0-ios -c Debug_Staging; also works properly using the correct configuration.
This has left me at a bit of a standstill as I'm not sure if there is any further I can take this in working around the issue. I'm hoping you can tell me that I'm just missing something simple or doing this all wrong 😂.

Hi, @ChrisMonson ! I did not know that you can create custom configuration in csproj, except Debug or Release =)
Yeah, .NET Meteor uses only Debug or Release folder for detecting the application:
https://github.com/JaneySprings/DotNet.Meteor/blob/46dcf6936dccf952545dbe8124ff5f34ce347860/src/DotNet.Meteor.Common/ProjectExtensions.cs#L84
I have a suggestion. I can create an option in the launch.json for specifying custom configuration, for example:
 "configurations": [
        {
            "name": ".NET Meteor Debugger (custom config)",
            "type": "dotnet-meteor.debugger",
            "request": "launch",
            "preLaunchTask": "dotnet-meteor: Build",
            "configuration": "Debug_Staging",
        }
    ]

it will be nice for you?

Awesome! I know that it's a little bit of a niche problem, but custom configurations can be really nice for having applications build in different ways for different situations. That sounds like a fantastic solution to me. I think that would solve all of the issues I have.

OK! I've already fixed it, but it's too late today. Tomorrow I will check that everything is working and I will release a new version

You are amazing. Thank you so much!

Hi, I have fixed this bug in the 5.3.1 version! You can use the following workaround:
tasks.json - change default value, provided by .NET Meteor
{
	"version": "2.0.0",
	"tasks": [
		{
			"type": "dotnet-meteor.task",
			"target": "build",
			"problemMatcher": [
				"$dotnet-meteor.problemMatcher"
			],
			"label": "dotnet-meteor: Build",
			"args": [
				"-p:Configuration=Debug_Staging"
			],
			"group": {
				"kind": "build",
				"isDefault": true
			}
		}
	]
}

launch.json - specify custom configuration
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": ".NET Meteor Debugger",
            "type": "dotnet-meteor.debugger",
            "request": "launch",
            "configuration": "Debug_Staging",
            "preLaunchTask": "dotnet-meteor: Build",
        }
    ]
}

I just updated the .Net Meteor extension and gave this a try and it works perfectly. Thank you so much for this amazingly quick update! I don't believe I've ever submitted a bug and had it fixed and deployed in under 24 hours before 😀.

@JaneySprings
runtime had been remove，how can i continue use it？

Hi @maonaoda ! Yes, I have rewritten this part and add more settings for the debugger launch.
You can specify path to your x64 application in the launch.json (Preferred way):
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "iossimulator-x64",
            "type": "dotnet-meteor.debugger",
            "request": "launch",
            "program": "${workspaceFolder}/bin/Debug/net8.0-ios/iossimulator-x64/MauiTestApp.app",
            "preLaunchTask": "dotnet-meteor: Build"
        }
    ]
}

Or you can change your device settings in the launch.json:
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "iossimulator-x64",
            "type": "dotnet-meteor.debugger",
            "request": "launch",
            "device": {
                "serial": "${command:dotnet-meteor.activeDeviceSerial}",
                "runtime_id": "iossimulator-x64",
                "platform": "ios",
                "is_mobile": true,
                "is_emulator": true,
            },
            "preLaunchTask": "dotnet-meteor: Build"
        }
    ]
}

I also want to make a note of all the options in the documentation or readme.

Documentation link:
https://github.com/JaneySprings/DotNet.Meteor/wiki/How-to-fix-the-error:-clang-exited-with-code-1


doc: add function argument order convention

Ordering by usage is the de facto ordering given to arguments. It's
logical, and makes finding argument usage easier. Putting lib first is
common in NixOS modules, so it's reasonable to mirror this in nixpkgs
proper. Additionally, it's not a package as such, has zero dependencies,
and can be found used anywhere in a derivation.
Motivation for this change
Following up on a conversation with @alyssais on IRC:
[...]
<V> stdenv only goes first in a lot of places b/c packages are written as { ... }: stdenv.mkDerivation { ... }, not because stdenv is special
<qyliss> I can see where you're coming from
<V> if we make stdenv be the first arg, then we should make buildGoPackage come before lib as well
<V> (I could go on)
<qyliss> if we're going to change it, we need to update the examples in the manual
<qyliss> if somebody puts together a PR for that I think it's fine
[...]

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.
Ordering by usage is the de facto ordering given to arguments. It's
logical, and makes finding argument usage easier. Putting lib first is
common in NixOS modules, so it's reasonable to mirror this in nixpkgs
proper. Additionally, it's not a package as such, has zero dependencies,
and can be found used anywhere in a derivation.

I've wondered a bit about this as I write a few packages. I'm a bit pleased to see order-by-usage suggested--because it should be formatter/linter-enforceable.
On the other hand, it's also common to interleave comments; I'm less sure if a formatter can just optimistically move the preceding comment, if any, any time it reorders arguments? :)

I've wondered a bit about this as I write a few packages. I'm a bit pleased to see order-by-usage suggested--because it should be formatter/linter-enforceable.
On the other hand, it's also common to interleave comments; I'm less sure if a formatter can just optimistically move the preceding comment, if any, any time it reorders arguments? :)

@abathur Although there's a few common patterns comments fall into, they can also get quite convoluted: see ffmpeg for a gnarly example. This will probably be quite a tricky problem to solve correctly (unless we decide to change the format of packages to something more structured).

@abathur Although there's a few common patterns comments fall into, they can also get quite convoluted: see ffmpeg for a gnarly example. This will probably be quite a tricky problem to solve correctly (unless we decide to change the format of packages to something more structured).

Yes. I thought about commenting about semantic groupings, though I waffled since they might actually still group well enough by first use. (Though, no--I hadn't noticed how gnarly ffmpeg is).
I guess it might be easier to address with a linter--since it can just complain that the order is wrong and make a human sort out t he comments--as long as it can respect the semantic-grouping concept.
I see occasional chatter about docstrings--I hope a principled solution could fit there, if nowhere else.

Yes. I thought about commenting about semantic groupings, though I waffled since they might actually still group well enough by first use. (Though, no--I hadn't noticed how gnarly ffmpeg is).
I guess it might be easier to address with a linter--since it can just complain that the order is wrong and make a human sort out t he comments--as long as it can respect the semantic-grouping concept.
I see occasional chatter about docstrings--I hope a principled solution could fit there, if nowhere else.

ffmpeg is definitely the exception, not the norm. I'm more accustomed to seeing fairly straightforward examples that would likely stand up to this kind of treatment. Presumably you've had a similar experience.
What I'd like to see is the whole callPackage convention being replaced with a structured package format, with configuration à la Gentoo's USE flags. It's a shame that the proposed config DSL hasn't yet appeared, as I feel it would really help with some of these problems. A structured config format could have these comments instead be docstrings, as you said, allowing them to be queried — again, as on Gentoo:
v@gentoo ~> equery u coreutils
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-apps/coreutils-8.32-r1:
 U I
 + + acl       : Add support for Access Control Lists
 + + caps      : Add Linux capabilities support in output of file utilities (ls, dir, ...) via sys-libs/libcap
 - - gmp       : Add support for dev-libs/gmp (GNU MP library)
 - - hostname  : Build the hostname program
 - - kill      : Build the kill program
 - - multicall : Build all tools into a single `coreutils` program akin to busybox to save space
 + + nls       : Add Native Language Support (using gettext - GNU locale utilities)
 - - static    : !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically
 - - test      : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
 - - vanilla   : Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL SCALE as the severity of the meaning changes drastically

ffmpeg is definitely the exception, not the norm. I'm more accustomed to seeing fairly straightforward examples that would likely stand up to this kind of treatment. Presumably you've had a similar experience.
What I'd like to see is the whole callPackage convention being replaced with a structured package format, with configuration à la Gentoo's USE flags. It's a shame that the proposed config DSL hasn't yet appeared, as I feel it would really help with some of these problems. A structured config format could have these comments instead be docstrings, as you said, allowing them to be queried — again, as on Gentoo:
v@gentoo ~> equery u coreutils
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-apps/coreutils-8.32-r1:
 U I
 + + acl       : Add support for Access Control Lists
 + + caps      : Add Linux capabilities support in output of file utilities (ls, dir, ...) via sys-libs/libcap
 - - gmp       : Add support for dev-libs/gmp (GNU MP library)
 - - hostname  : Build the hostname program
 - - kill      : Build the kill program
 - - multicall : Build all tools into a single `coreutils` program akin to busybox to save space
 + + nls       : Add Native Language Support (using gettext - GNU locale utilities)
 - - static    : !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically
 - - test      : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
 - - vanilla   : Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL SCALE as the severity of the meaning changes drastically

Also I am saying how it is but I don't think we can enforce this at all or people are getting mad.

Also I am saying how it is but I don't think we can enforce this at all or people are getting mad.

For now, it's a guideline, not a rule. Later, we can have formatting tools apply the reordering for us.
I'm not really sure why you'd think people would be mad at having some actual coding conventions, though. The lack of any is a common complaint.

For now, it's a guideline, not a rule. Later, we can have formatting tools apply the reordering for us.
I'm not really sure why you'd think people would be mad at having some actual coding conventions, though. The lack of any is a common complaint.

This is, at its core, a two line change. I've reached my limit with how much bikeshedding I'm willing to deal with at the moment, so I'm leaving it to someone else to carry to the finish line if they want this merged. This kind of feedback is extremely draining to engage with, and seriously demotivates me from contributing.

This is, at its core, a two line change. I've reached my limit with how much bikeshedding I'm willing to deal with at the moment, so I'm leaving it to someone else to carry to the finish line if they want this merged. This kind of feedback is extremely draining to engage with, and seriously demotivates me from contributing.

This is, at its core, a two line change. I've reached my limit with how much bikeshedding I'm willing to deal with at the moment, so I'm leaving it to someone else to carry to the finish line if they want this merged. This kind of feedback is extremely draining to engage with, and seriously demotivates me from contributing.

It is not just a two line change. This impacts everyone that contributes to nixpkgs and if we do not have the right tooling first then this kind of guideline does not add anything.
If we have a formatter that does this and most people can agree on using it then we can make the formatter a hard requirement.
Right now if I would suggest people to sort their inputs in a PR review I would start a lot of bike sheeting with a lot of people.

This is, at its core, a two line change. I've reached my limit with how much bikeshedding I'm willing to deal with at the moment, so I'm leaving it to someone else to carry to the finish line if they want this merged. This kind of feedback is extremely draining to engage with, and seriously demotivates me from contributing.

It is not just a two line change. This impacts everyone that contributes to nixpkgs and if we do not have the right tooling first then this kind of guideline does not add anything.
If we have a formatter that does this and most people can agree on using it then we can make the formatter a hard requirement.
Right now if I would suggest people to sort their inputs in a PR review I would start a lot of bike sheeting with a lot of people.

Right now if I would suggest people to sort their inputs in a PR review I would start a lot of bike sheeting with a lot of people and they would discard my reviews even more.

Nixpkgs is huge and broad. If the inputs are getting unwieldy, then you can say to sort if it improves comprehension, but I don't think this is true across the board. Also, you can convey that something is not a blocker (I usually say, I don't feel strongly about something). I think it's important for maintainers to have some "ownership" over the style of code they use.
@SuperSandro2000 I agree it would be nice for some conventions to be well defined, but the nature of nixpkgs is that it's a "living document", in the packages it contains and the conventions it adheres to. Like @grahamc  said, this is a step in the right direction, and overall improvement.
Maybe one day we will be like elm, where the style is already determined for everyone, and adherence will be easy because any nix command will auto format your code. Until then, incremental improvement is always a good choice.

Right now if I would suggest people to sort their inputs in a PR review I would start a lot of bike sheeting with a lot of people and they would discard my reviews even more.

Nixpkgs is huge and broad. If the inputs are getting unwieldy, then you can say to sort if it improves comprehension, but I don't think this is true across the board. Also, you can convey that something is not a blocker (I usually say, I don't feel strongly about something). I think it's important for maintainers to have some "ownership" over the style of code they use.
@SuperSandro2000 I agree it would be nice for some conventions to be well defined, but the nature of nixpkgs is that it's a "living document", in the packages it contains and the conventions it adheres to. Like @grahamc  said, this is a step in the right direction, and overall improvement.
Maybe one day we will be like elm, where the style is already determined for everyone, and adherence will be easy because any nix command will auto format your code. Until then, incremental improvement is always a good choice.


chore(main): release sandworm-mocha 1.5.1

:robot: I have created a release beep boop
1.5.1 (2022-10-03)
Bug Fixes

refactor afterAll hook (19e55bb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sandworm-mocha/releases/tag/sandworm-mocha-v1.5.1 :sunflower:


Navigating file explorer by keyboard is now broken

Is the bug present when using the default Obsidian theme?
No
Minimal theme version
5.3.0
Describe the bug
Obsidian insider build recently introduced the ability to put keyboard focus on the file explorer so you can navigate the file tree with arrow keys. I think it was in Minimal 5.2 when that was introduced, and it worked perfectly. In the latest update, however, you can no longer see which file has focus as you navigate the file explorer in the sidebar.
The issue appears to be related to the following style in src/scss/obsidian/file-nav.scss:
.workspace-leaf.mod-active .nav-folder.has-focus > .nav-folder-title,
.workspace-leaf.mod-active .nav-file.has-focus {
  border:none;
}

By default, the border should be visible so you can see which file or folder you're trying to select.
Debug info
SYSTEM INFO:
Obsidian version: v0.15.3
Installer version: v0.14.6
Operating system: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000 21.5.0
Login status: logged in
Catalyst license: vip
Insider build toggle: on
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: Minimal
Snippets enabled: 11
Safe mode: off
Plugins installed: 60
Plugins enabled: 57
1: Metadata Extractor
2: MetaEdit
3: Remember cursor position
4: ReadItLater
5: QuickAdd
6: Quick Switcher++
7: Quick Explorer
8: Paste URL into selection
9: Pane Relief
10: Pandoc Plugin
11: Note Folder Autorename
12: Natural Language Dates
13: Multi-cursor
14: Minimal Theme Settings
15: Markdown Attributes
16: Obsidian42 - Jump-to-Date
17: Obsidian42 - BRAT
18: Readwise Official
19: Jump to link
20: Link Favicons
21: Imgur Plugin
22: Hotkeys++
23: Hotkeys for templates
24: Templater
25: Typewriter Scroll
26: Hider
27: Get Info
28: CustomJS
29: Dataview
30: Advanced Cursors
31: Advanced Mobile Toolbar
32: Advanced Slides
33: Advanced Tables
34: Advanced URI
35: Another Quick Switcher
36: Auto Link Title
37: Better Word Count
38: Calendar
39: Citations
40: Contextual Typography
41: Copy as HTML
42: Customizable Page Header and Title Bar
43: Editor Syntax Highlight
44: Find unlinked files and unresolved links
45: Focus Mode
46: Folder Note
47: Force note view mode
48: Show Whitespace
49: Sortable
50: Style Settings
51: Tag Wrangler
52: Task Collector (TC)
53: User Plugins
54: Wikilinks to MDLinks
55: Note Auto Creator
56: Reading Time
57: Code Editor Shortcuts
RECOMMENDATIONS:
Custom theme: for cosmetic issues, please first try updating your theme to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

I have just installed the theme 5.03 in Obsidian 1.5.9 (Win) and that's the first thing I noticed (👍 for the bug report above):
Obsidian Release v0.15.6

Keyboard Accessibility
Added keyboard navigation to the File Explorer, Tag pane, and Search views Arrow keys to move through items, Enter / Shift+Enter to select.

Keyboard navigation stops working when the Minimal theme is selected.

So it seems to be strictly a style fix to restore the visual cue when navigating the file tree. I can edit the name of this issue if it helps make that clearer.

I experienced the same when installing Minimal 5.3.2 with BRAT plugin. When I installed the release version of 5.3 all was good.

This will be fixed in Minimal 6.0 which will coincide with the next major version of Obsidian

6.0… a whole number version update, that sounds exciting! :-)


Need a share button for the article/news pages to share the desired article via a short link ( Not too long links )

Is your feature request related to a problem? Please describe.
Whenever I am reading any article and I want to share that , there is no option.
I had to copy the 'long' url  and the share the url.
Describe the solution you'd like
It will be really helpful if the (news) pages has the "share" option like 'youtube' where if we click the "Share" button a 'short' url pops up. And we can share easily
Describe alternatives you've considered
Also social options would be nice
Additional context
My main concern is the very long links. This is annoying.
I love FreeCodeCamp and use it almost everyday.  So a short url would be helpful to share any specific article
Thanks

@mibijoy007 i can work on this looks intresting can you assing me

I would like to work on this issue,can u assign this to me

it's interesting, I can do it, could you assign me, please?

Hi @mibijoy007
Thanks for requesting this, we discussed this and decided against short-links at the time owing to need for maintaining additional resources (domains, servers, maintenance) etc.
Since we are tiny team with limited resources we can only prioritize features that we think make significant impact to our campers and supporters :)
Hope this is understandable.
Happy coding!


Adds market manager and new interfaces.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 166 (0.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-16.2%) to 53.996%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

Solnet.Serum/MarketFactory.cs
0
1
0.0%

Solnet.Serum/SerumClient.cs
0
18
0.0%

Solnet.Serum/MarketUtils.cs
0
32
0.0%

Solnet.Serum/Models/OrderBook.cs
0
39
0.0%

Solnet.Serum/MarketManager.cs
0
76
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-16.2%

Covered Lines:
453

Relevant Lines:
792

💛  - Coveralls


Techtalent - The job location is "remote/no city/Cluj/Bucuresti/Brasov" instead of "Remote"/Cluj/["Cluj", "Bucuresti", "Brasov"]

ENVIROMENT: production
URL: https://solr.peviitor.ro
Browser: Chrome
Device: laptop
OS: Windows 11
STEPS TO REPRODUCE:

Open the URL in the browser
Execute Query for "Techtalent" Company
Check the jobs location for Senior Java Developer (remote is not a city in Romania), Product Validation Engineer (no city), Product Validation Engineer(Cluj/Bucuresti/Brasov is not a city in Romania)
Open https://www.techtalent.ro/careers
Check the jobs location for the 3 positions (Senior Java Developer,Product Validation Engineer, Product Validation Engineer)
EXPECTED RESULTS:
The location of the job must match the one in the job advert
Senior Java Developer, Remote
Product Validation Engineer, Remote (I propose Remote because on the company website there is no city)
Product Validation Engineer, ["Cluj", "Bucuresti", "Brasov"]

ACTUAL RESULTS:
The job location is "remote/no city/Cluj/Bucuresti/Brasov" instead of "Remote"/"Remote"/["Cluj", "Bucuresti", "Brasov"]
On the scrapers.peviitor.ro the messages "remote is not a city in Romania" , "no city" and "Cluj/Bucuresti/Brasov is not a city in Romania" are displayed

Fixed!

Verificat, OK!


Documentation

Is your feature request related to a problem? Please describe.
Trying to standardize README.md documentation for docker projects.

Pull Requests

https://github.com/Senzing/docker-senzing-base/pull/27


Fix uploading multiple output packages (fixes #1)

FWIW adding the upload_or_check_non_existence.py script and simply re-rendering will have the same effect.

That's what I did. Just took me a bit to dig through the scripts to realize that I could "overwrite" it for this recipe.

Ah ok. Cool.
I'm use to seeing the MNT: Re-rendered with conda-smithy X.X.X commit messages. So wasn't sure.
Yeah believe it or not that is intended to be a feature for all feedstocks should it be needed. Though, in practice, only conda-forge-build-setup uses them. Though it could come in handy if the build setup needs to get tweaked in a hurry. Probably should be documented. 😅

I think documenting in the source is fine. If you are going to mess with the build process, you need to read that anyway. My issue was mainly figuring out where it came from because it's installed without the .py. Perhaps it could just log itself. E.g. `no local upload_or_check_existance found; using default from conda-forge-build-setup-feedstock.

It's good to have the option to override locally though. If only as a path for testing. I wouldn't claim it works if it hadn't here.


Enroll button is still active after user has enrolled

Steps to Reproduce

Visit a course detail page, like https://rc.mitxonline.mit.edu/courses/course-v1:MITx+14.310x/
Enroll
Confirm the enrollment appears on the dashboard
Return to the course detail page

Expected Behavior

Enroll button should be deactivated. On xPRO this means that the text changes to "Enrolled" and the button has a white background with red text and red outline.

Actual Behavior

Enroll button is still active.

Stacktrace
(Optional)
Related Issues
(Optional)
Screenshot or Screencast
(Optional)

@pdpinch The button just appears active because of the styling. The text changes to "Enrolled ✓" and the button becomes just a simple link to the edX course page.

Looks like there are two things to fix here:

Update the styling to the xpro-esque red outline you described
Remove the link to the edX course page if it hasn't started yet (we already made this fix in the dashboard, but we neglected this page)

@pdpinch https://github.com/pdpinch The button just appears active because of the styling. The text changes to "Enrolled ✓" and the button becomes just a simple link to the edX course page.

Wow. I totally missed that.

Update the styling to the xpro-esque red outline you described
That would be clearer. I think it would help also to remove the hover state.
Remove the link to the edX course page if it hasn't started yet (we already made this fix in the dashboard, but we neglected this page)
Yes.


Error Activating the Remote Language Server Q# Extension

I re-installed the extension twice and got the same error. In fact it got worse the second time. I really want to use this but it's impossible when it doesn't work. Here are my logs.
10  ShellFolder
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\   VisualStudio 2020/07/12 17:26:41.142
2076 ERROR Failed to set Public Key Token  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:44.997
2077 ERROR Binding Redirect / CodeBase entry from configuration hive is malformed, ignoring.
Software\Microsoft\VisualStudio\16.0_32bd5b91_Config\RuntimeConfiguration\dependentAssembly\codeBase{0746BB9F-4F6E-4C38-BCF0-8F601D6AD0C1}  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:44.997
2078 ERROR Failed to set Public Key Token  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:44.997
2079 ERROR Binding Redirect / CodeBase entry from configuration hive is malformed, ignoring.
Software\Microsoft\VisualStudio\16.0_32bd5b91_Config\RuntimeConfiguration\dependentAssembly\codeBase{167AF614-476E-4BDF-952E-57A6C7CF39A5}  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:44.997
2080 ERROR Failed to set Public Key Token  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.007
2081 ERROR Binding Redirect / CodeBase entry from configuration hive is malformed, ignoring.
Software\Microsoft\VisualStudio\16.0_32bd5b91_Config\RuntimeConfiguration\dependentAssembly\codeBase{5C67FEBD-A585-4D39-8B7E-FCC06A805297}  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.007
2082 ERROR Failed to set Public Key Token  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.007
2083 ERROR Binding Redirect / CodeBase entry from configuration hive is malformed, ignoring.
Software\Microsoft\VisualStudio\16.0_32bd5b91_Config\RuntimeConfiguration\dependentAssembly\codeBase{7A9AEA02-2F54-493C-8E45-580D66D02799}  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.007
2084 ERROR Failed to set Public Key Token  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.007
2085 ERROR Binding Redirect / CodeBase entry from configuration hive is malformed, ignoring.
Software\Microsoft\VisualStudio\16.0_32bd5b91_Config\RuntimeConfiguration\dependentAssembly\codeBase{7E3052B2-FB42-4E38-B22C-1FD281BD4413}  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.007
2086 ERROR Failed to set Public Key Token  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.007
2087 ERROR Binding Redirect / CodeBase entry from configuration hive is malformed, ignoring.
Software\Microsoft\VisualStudio\16.0_32bd5b91_Config\RuntimeConfiguration\dependentAssembly\codeBase{938D3E45-5067-45C4-9349-5E939A639CBF}  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.007
2088 ERROR Failed to set Public Key Token  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.017
2089 ERROR Binding Redirect / CodeBase entry from configuration hive is malformed, ignoring.
Software\Microsoft\VisualStudio\16.0_32bd5b91_Config\RuntimeConfiguration\dependentAssembly\codeBase{C8992C7B-8D67-41E9-ADD1-D44D1ACDD139}  80070057 - E_INVALIDARG VisualStudio 2020/07/12 17:26:45.017
2156 ERROR Loading UI library {2FFE45C4-5C73-493C-B187-F2E955FF875E} 800a006f VisualStudio 2020/07/12 17:26:46.941
2157 ERROR Error loading UI library for package Microsoft.VisualStudio.LanguageServices.TypeScript.TypeScriptPackage, Microsoft.VisualStudio.LanguageServices.TypeScript, Version=<IP_ADDRESS>, Culture=neutral. HrLoadNativeUILibrary failed with 0x800a006f.   VisualStudio 2020/07/12 17:26:46.941
2159 ERROR Failed to find CTMENU resource '#1000' in loaded UI library.   VisualStudio 2020/07/12 17:26:46.952
2160 ERROR Loading UI library {C78CA057-CC29-421F-AD6D-3B0943DEBDFC} 800a006f VisualStudio 2020/07/12 17:26:46.962
2161 ERROR Error loading UI library for package Windows Forms Remote Designer Hosting Package. HrLoadNativeUILibrary failed with 0x800a006f.   VisualStudio 2020/07/12 17:26:46.962
2162 ERROR Loading UI library {2EF1EC52-C8BF-4FE0-8ECE-BA9C0D5D1603} 800a006f VisualStudio 2020/07/12 17:26:46.972
2163 ERROR Error loading UI library for package XamlLanguagePackage. HrLoadNativeUILibrary failed with 0x800a006f.   VisualStudio 2020/07/12 17:26:46.972
2164 ERROR Loading UI library {71054795-27FD-4816-9AEA-667FE14EDD2A} 800a006f VisualStudio 2020/07/12 17:26:47.012
2165 ERROR Error loading UI library for package New Project Dialog. HrLoadNativeUILibrary failed with 0x800a006f.   VisualStudio 2020/07/12 17:26:47.020
3344 ERROR Failed to get preselected extension name.   ProjectCreationViewModel 2020/07/12 17:26:57.424
3383 ERROR Failed to load package string with id 12b27ee7-3aa0-474e-8bb8-dd1a3bb2bced and resource id #114   PreviewFeaturesPane 2020/07/12 17:27:05.477
3385 ERROR Failed to load package string with id 2d510815-1c4e-4210-bd82-3d9d2c56c140 and resource id #8003   PreviewFeaturesPane

Hi, sorry to hear that. Can you give us more details about the scenario. Is the error happens right after you installed the extension or when you click on live share button ? Also, Your logs may provide us with helpful information to investigate. You can find your logs in the %TEMP%/VSFeedbackVSRTCLogs directory. You can attach them to here or  email them to<EMAIL_ADDRESS>with the issue number 3722

@BrunoGuardia assigning to you, feel free to reassign if it is not your area.

@jbrandes - which versions of Visual Studio and LiveShare are you using? Seems you are using a VS 2017, but the errors report 16.0 compatibility issues. Logs as described by @setaskin will be useful

Closing this issue due to lack of enough information to investigate a fix for it. Thank you!


Research: can we display a table footer in the list page and display sum/average etc there?

Research: can we display a table footer in the list page and display sum/average etc there?

 Research: can we display a table footer in the list page and display sum/average etc there?


Build Android, iOS and Desktop apps

Maybe better than adding PWA #243, which is of course easier, would be to build android, ios and desktop apps. For each platform you would need a shell, like the one for the web (header, navigation, toc) and a renderer for Markdown. Which probably should be a WebView which just renders the nextjs pages.

This seems like a good starting point: https://capacitorjs.com/blog/mobile-apps-with-tailwind-css-nextjs-ionic-and-capacitor


No module named censys.certificates

While running Sudomy I get the following error:
Traceback (most recent call last):
  File "lib/censys/censys_subdomain_finder.py", line 3, in <module>
    import censys.certificates
ImportError: No module named censys.certificates

pip3 install censys
Requirement already satisfied: censys in /usr/local/lib/python3.8/dist-packages/censys-0.0.8-py3.8.egg (0.0.8)
Requirement already satisfied: netaddr in /usr/lib/python3/dist-packages (from censys) (0.7.19)
Requirement already satisfied: requests in /home/kali/.local/lib/python3.8/site-packages (from censys) (2.24.0)
Requirement already satisfied: certifi>=2017.4.17 in /home/kali/.local/lib/python3.8/site-packages (from requests->censys) (2020.6.20)
Requirement already satisfied: chardet<4,>=3.0.2 in /usr/lib/python3/dist-packages (from requests->censys) (3.0.4)
Requirement already satisfied: idna<3,>=2.5 in /home/kali/.local/lib/python3.8/site-packages (from requests->censys) (2.10)
Requirement already satisfied

Same with pip
pip install censys
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: censys in /home/kali/.local/lib/python2.7/site-packages (0.0.8)

Try to remove the Censys Python Library on python3  and try to reinstall on python2
Check the lib like this
Python 2.7.17 (default, Jan 19 2020, 19:54:54)
[GCC 9.2.1 20200110] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import censys
>>> import censys.certificates


Add IN clause

It could be useful to quickly search again for a specific subset of the data

Fixed in version 0.0.2


404, message='Invalid response status'

I have setup with:

HA 2023.4.4
Frigate 0.12 installed on a separate device, using docker-composer
Frigate NVR Proxy 1.3 addon in HA
go2rtc configured inside Frigate
Dahua cameras which I would like to monitor using 'custom:webrtc-camera' card

Frigate, proxy addon and go2rtc seem to be working fine:

I am able to see camera views in Frigate addon UI in HA
For each configured camera I can successfully choose mse/webrts/jsmpeg and for mse and webrtc I get a high resolution real-time views

Issue starts when I am trying to configure 'custom:webrtc-camera' card.
I get a constant "404, message='Invalid response status'" error message which does not give me any hints what do I do wrong.

Since I am able to see cameras real-time view in Frigate addon UI I guess streams configuration, access matters, etc. are rather fine.
Configuration is:

Frigate host: <IP_ADDRESS>
HA: <IP_ADDRESS>
WebRTC integration added to HA with following go2rtc server URL: http://<IP_ADDRESS>:5000

Docker Composer script:
frigate:
  container_name: frigate
  privileged: true
  restart: unless-stopped
  image: ghcr.io/blakeblackshear/frigate:stable
  shm_size: "216mb"
  devices:
    - /dev/bus/usb:/dev/bus/usb
    - /dev/dri/renderD128
  volumes:
    - /etc/localtime:/etc/localtime
    - /home/sebo/frigate/config.yml:/config/config.yml
  ports:
    - "5000:5000"
    - "8554:8554"     # RTSP feeds
    - "8555:8555/tcp" # WebRTC over TCP
    - "8555:8555/udp" # WebRTC over UDP
  environment:
    FRIGATE_RTSP_PASSWORD: "***"

Frigate go2rtc configuration:
go2rtc:
  streams:
    frigate_schody:
      -<EMAIL_ADDRESS>
'custom:webrtc-camera' card configuration:
type: custom:webrtc-camera
url<EMAIL_ADDRESS>title: Schody

Using camera entity ID directly in the card should be also possible, as far as I understand docs:
type: custom:webrtc-camera
entity: camera.frigate_schody
title: Schody

But if I do I just get another error:
"Can't get URL for camera.frigate_schody"

Is it like the 'custom:webrtc-camera' is not yet ready for new Frigate/go2rtc configuration and will require some updates ?
Or do I do something very wrong ?

For the 2nd part - "Can't get URL for camera.frigate_schody" I may already find the answer.
It looks that the camera entity cannot be the one created by Frigate.
When I create a camera entity in configuration.yaml, giving RTSP stream URL, than the card starts failing in the same way - "404, message='Invalid response status'"

You using wrong port. 5000 - Frigate web. 1984 - go2rtc web.


Allow "not specified" in envvars for CPU and memory resources

Users can create "burstable" Pods by specifying .spec.resources.requests and pruning .spec.resources.limits in custom resources, like the following.
kind: VMAgent
spec:
  resources:
    requests:
      cpu: 100m
      memory: 200Mi
    # limits are not specified

This cannot be done with the environment variables for the operator.
They have default values, and users can override the values only with some valid quantity, not with "not specified."
For example, the following configuration with removing .spec.resources from VMAgent will produce Pods with the limits of cpu: 200m and memory: 500Mi taken from the default.
env:
- name: VM_VMAGENTDEFAULT_RESOURCE_REQUEST_CPU
  value: 100m
- name: VM_VMAGENTDEFAULT_RESOURCE_REQUEST_MEM
  value: 200Mi
# RESOURCE_LIMIT_* are not specified

Forcing limits in the cluster-wide configuration is useful for strict resource planning, but it can sometimes be dangerous because violating Pods may be killed immediately.
It would be nice if users could use a special notation for "not specified" in envvars.

updated.

Added to the latest release v0.10.0


how do i select virtual env from WSL (windows subsystem from linux) in Windows Neovim?

I think this may not be right repo for this question, but someone might know.
I have a setup such that my nvim config is in Windows and it works well.
I tried setting up a duplicate config in WSL, and after much trial, most things work, except LSP.
When I clone repos, I clone then in Windows, but most of the times, I have to work within WSL to actually get things to run. For instance, I have to create my venv in WSL. This means that though my LSP can do most things, it can't figure out libraries I have installed in my WSL venv.
Any help is appreciated!

Maybe some windows user can give input on this. I don't have a windows machine myself and don't know the WSL very well.

This is an old issue and hopefully you figured out a way to do this by now. Closing it. :)


Add new maintainers

volunteers?

Yes!

Welcome to the team

Closing, but if anyone else is interested in helping, feel free to step forward.

In terms of publishing to Sonatype, how do we proceed?

I'd be happy to automate that using tag push.

Ok, I can do the CI setup with something like: https://github.com/sbt/sbt-unidoc/blob/develop/.github/workflows/release.yml
If you can fill the secret env variables, I'm happy to do the rest.


Environment configuration management

It would be nice to have a way to manage different configuration parameters based on environment. It could allow to store things like api endpoints, ...
For example angular-cli override a environment.ts file based on the target environment.

I am already doing this in a project where I am using the seed. I will try to push this feature upstream early next week.

Also it would be nice if we could dynamically add environments, and not be limited to just development and production.
I don't know your concrete implementation if you have this that is great, if not maybe this could a feature for some future release?

I am thinking of only two build configurations - dev and prod like what we have now.
On top of that, we can have multiple configuration variables loaded dynamically from a JSON config files, located somewhere in the root. So npm run build.prod --env-config staging will run the prod build but set end points, settings, etc for the staging environment.

Hi,
@mgechev has a point; from a build technical perspective, a "development" build and a "production" build should be sufficient. But i agree too, any further environment specific environments (e.g. staging, integration ) could be provided for / configured through JSON config files. IMHO we should rough out a more specific concept for this (in the likes of #913), and then tacle it. Yet, i guess it would be preferable if we first finish up with the works on #913 (respectively https://github.com/mgechev/angular2-seed/pull/926) before we add / enhance on the environment configuration.

@TheDonDope makes sense, lets hold it until #913 is resolved.

Actually looking at my current solution I don't think we should add this to the seed at this point.
@jbouzekri my suggestion for managing configurations for different environments is to add plugin/task specific config in your project.config.ts file.
Let you can require this config using this call. You can store the entire configuration for all the different environments in JSON files, if you prefer.
Finally in your config.ts (or whatever you name it) which is part of your project, you can just insert the correct configuration based on the user choice using a template <%= CHOSEN_CONFIG %>. This is also supported by the seed.

@mgechev : thanks. Too bad you won't add it to seed. I think it would be useful in a professional job environment to be able to manage this.
I have already implemented my own solution inspired by angular-cli where I deploy in dev or tmp folder an environment.ts file containing the configuration for my current environment target.

Just for the record - the feature is implemented and waiting to be merged here https://github.com/mgechev/angular2-seed/pull/1026.


Removing vim, verified vi is available

What was changed

Removing vim from base container images
Why?

CVE
confirmed vi is still available if needed.
Checklist

Closes
#28

How was this tested:

Confirmed through local docker run/exec/build

Any docs updates needed?

No

Need to open from a repo local branch for CI.


User can edit a case from the individual case card.

moment.js library added to manage ant design datePicker.
JWT token fix for CaseOverview and CaseUpdate.

It looks good overall. 👍 Some minor changes: since we aren't using useHistory in CaseOverview anymore, we should probably remove that. Also, this PR includes package.json, this should be removed before merge.

Agreed


how to use stage2 ckpt fine-tuning stage3？

First, I modified the scripts/llama/train/stage_1_2_full_v7b_336_hr_768.sh, changing parameter ”--model_name_or_path” to the stage2 checkpoint “MGM-7B”, and then got loar model_path.
Afterwards, using scripts/merge_lora_weights.py to merge the base and lora. But  I found that it does not work. Compared to LLava, the mgm.model.builder.load_pretrained_model method seems to be lacking several components, the method don't load peftmodel.

Hi, please refer to the issue #49 for the continuous fine-tuning. And all our models are fully finetunded. Actually, I did not try LoRA. This could be checked and supported soon.


[feat request] Add http proxy and socks proxy to Telegram server

I would like to add an API for setting network proxies, which is important in some cases. Please consider this. Thank you.

I see it in e78f82d. Thank you for your contributions to the Kotlin community! 🍻

Yes, maven publishing didn't go through due to errors with their server so it took a bit longer, but the new version should now be resolving.
If you want to use socka proxy try to exclude the cio engine and implement for example okhttp and it should work too.
Or take a look there:
https://ktor.io/docs/proxy.html#supported_engines


"BposSAllModality" needs to be documented

This cmdlet refers to the Global (org-wide default) policy as "BposSAllModality". This needs to be documented. The admin UI and all the other cmdlets use the actual name, not "BposSAllModality" so it's pretty confusing.

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

ID: f3898f54-71f3-44c6-8412-c3eeee517aa7
Version Independent ID: 8ea324f5-a833-f877-3888-a8a703bebd97
Content: Get-CsUserPolicyAssignment (MicrosoftTeamsPowerShell)
Content Source: teams/teams-ps/teams/Get-CsUserPolicyAssignment.md
Service: teams-powershell
GitHub Login: @tomkau
Microsoft Alias: tomkau

Hello @npherson Nash, how are you?
Actually, "MeetingPolicy" are the ones returned by Get-CsConferencingPolicy if you look at the output of that cmdlet you can see there is a Global and all of the rest, start with BposS
Identity : Global
Identity : Tag:BposSAllModality
Identity : Tag:BposSAllModalityNoVideo
Identity : Tag:BposSAllModalityMinVideoBW
[...]

These were back from the days of SFBO. Not to be confused with TeamsMeetingPolicy that indeed are for Teams.
So BposSAllModality is not Global (Org Wide Default), in this case.
I also could verify this

if an effective policy is not returned, this indicates that the effective policy for the user is either the tenant global default policy (if set) or the system global default policy.

applying the Global (Org Wide Default) TeamsMeetingPolicy to a user.
Thank you

@yogkumgit


[SYSTEMML-467] Update script invocation of Beginner's Guide

Preview:
http://deroneriksson.github.io/incubator-systemml/beginners-guide-to-dml-and-pydml.html
http://deroneriksson.github.io/incubator-systemml/engine-dev-guide.html

Overall this LGTM.   I noted a few other changes that we could go ahead and do too while we're at it.

@dusenberrymw
Made the additional updates. I will merge. Thanks for reviewing!


Missing header file "readline"

src/kjv.c:14:10: fatal error: readline/readline.h: No such file or directory
   14 | #include <readline/readline.h>
      |          ^~~~~~~~~~~~~~~~~~~~~```
   getting the above error  and for the life of me I can not fine this header.   I am on a Debian base distro.

You need to install the readline development libraries:
sudo apt-get install libreadline-dev

You need to install the readline development libraries:
sudo apt-get install libreadline-dev

Yes sir that fixed it!  Thank you!  I am closing this issue!

Yes sir that fixed it!  Thank you!  I am closing this issue!


DNS lookup broken if original DNS server goes down but has already been changed in Windows

Experienced this with build 14905.
My router's DNS started to stop responding to dns lookups so instead of restarting it I set my DNS server from <IP_ADDRESS> to OpenDNS <IP_ADDRESS>, <IP_ADDRESS> in Windows.
Ubuntu for Windows seemed to still be using the old DNS as all lookups would fail. It wasn't until I disabled and then re-enabled the Ethernet adapter in Windows that I was able to have DNS lookups working again in the shell.

The workaround is to note that /etc/resolv.conf is generated from Windows settings when Bash is started from scratch. So, theoretically, if the Windows DNS changes while a Bash.exe is running, the value of /etc/resolv.conf will not change to reflect the new Windows settings until later, according to the Devs. So, to test, make sure all bash.exe processes are stopped and then start them up again, and check to make sure that /etc/resolv.conf reflects new settings on the Windows side (e.g. by comparing to ipconfig /all in Windows). (It might be good to test to see if it also updates when you just restart networking on Windows, but that's less critical.)
The other workaround is to leave your router listed as the first DNS resolver, then put the OpenDNS resolvers in as second and third (using DHCP setup on the router or perhaps Windows network setup). /etc/resolv.conf should then also end up with the same three resolvers the next time it is auto-generated. Then if the router's DNS stops working, both Windows and WSL will switch to one of the alternatives, without having to restart or edit anything. (This is a good strategy any time one sets up a network, assuming fallback resolvers that are secure and work properly.)
Or you could edit /etc/resolv.conf by hand to get things going in WSL without restarting anything, understanding that the file will be auto-generated again when everything restarts.
In no sense do the workarounds mitigate the core problem, which is that DNS resolver selection is about the only core networking functionality of WSL (routing, firewall, adapter configuration, etc) that isn't handled by the Windows side in real time.

Apologize the delay in response here. It is true that /etc/resolv.conf is generated by bash during first launch. Also, the original intended design is to keep the /etc/resolv.conf up to date with any changes that happen on the Windows side. This happens by the LXSS Manager, which registers for WNF notifications for any network changes including IP address & DNS updates. For DNS updates, it should then in turn update the /etc/resolv.conf. But, the update does not seem to be happening (probably because the notification is not coming in) and that is just a bug. I have opened a bug on our end to track this and hopefully we should have a fix for this soon. Apologize for the poor experience and please keep the feedback coming!

I have a similar issue to this with regard to VPNs whereas based on the order of the DNS servers in /etc/resolv.conf anything after the first one doesn't fully work. So for example, I have my normal internet network, and I'm connected to my work VPN via split tunnel. Therefore, all my internet traffic still goes through my network and any VPN traffic will go through that, and of course the VPN traffic would have its own DNS server. This all works fine in Windows itself, but inside the Ubuntu Bash, things are not as happy. the /etc/resolv.conf lists my local dns server for internet, and the couple DNS servers from my VPN. the local dns is first and the others follow it. When I do a 'nslookup or dig' on a VPN only hostname say, vmatwork.myworkvpn.com, it will properly cycle through all the DNS servers and provide the result. However, if I do a 'ping', 'ssh' or anything else using that same hostname, the DNS resolution fails. It basically only tries the first DNS server, and bails out. If I modify and move the VPN's DNS servers to be first in /etc/resolv.conf, it will now allow me to use 'ping', 'ssh', etc against the VPN hostname. However, when doing that, my internet DNS now fails because now it's not first. While this workaround lets me utilize my VPN's internal hostnames, it results in all external (internet) hostnames to fail DNS resolution.
As mentioned, this is not a problem anywhere else in Windows 10. If I use cygwin, both networks work as expected. It's only using Bash for Windows that this is a problem.

@wizll - The VPN issue is a known one and is already being tracked by other GitHub posts such as #1350, #963. Please track it using those posts.
The general issue of /etc/resolv.conf should already been fixed in Insider builds.


Use of argparse to parse input

Hello @gopinath-langote! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file onebuild/input_parser.py:

Line 9:80: E501 line too long (81 > 79 characters)
Line 11:80: E501 line too long (107 > 79 characters)


uTorrent Not Passing File Back to Sonarr

I have the mp4 automator script converting my sonarr labeled downloads after completion but the converted file doesn't seem to be passed back to sonarr.
I'm using Windows 10 and I have an output director called C:\Converting where the file is moved from C:\Downloads\Torrents\Completed. So this part is working correctly. However, after converting, the episode files remain in the Converting folder, untouched by sonarr (not renamed and not placed in C:\TV\[showname]
Python shows me that the uTorrentPostProcess.py script is being called and conversion completes without error. I have quadruple-verified that the uTorrent label for sonarr matches in the settings. It's called sonarr_label. Are underscores somehow not allowed? If anyone can help, I would really appreciate it. Thanks!

Have you made sure that utorrent is pointed to the .py with %L %T %D %K %F %I %N in that order? so it should look like C:\[wherever the converter is stored]\uTorrentPostProcess.py %L %T %D %K %F %I %N
Also to make things simple I only ever use the label's Sonarr, Couchpotato, Bypass. theres no need to add the _label as it dose sometimes confuse sonarr.

Thanks for getting back to me. I did and I added quotes around %L %T %D %K %F %I %N so C:\[wherever the converter is stored]\uTorrentPostProcess.py "%L %T %D %K %F %I %N"
I'll try simplifying the labels by renaming them back to what they originally were and post an update. Thanks!

I recently switched from linux to windows 8.1 and then back to linux again but when i was on windows I ran the script with quotes on each thing. Try putting
C:\[wherever the converter is stored]\uTorrentPostProcess.py "%L" "%T" "%D" "%K" "%F" "%I" "%N"
see if that helps.


lodash compatibility

replaces _.contains with _.includes in order to make package compatible with lodash 4.0.0 and underscore
Alternatively, you could add underscore as a dependency in the package.js file ? (this might be a better long term solution)

Cool!


make cache injectable into NotaryRepository

Reasonably minimal changes to make cache injectable while not having to move around much code. Also want to keep and add to "helper" constructors (e.g. NewFileCachedNotaryRepository) rather than push too much of that code up the call stack.
Also moved a bunch of errors that were in client/client.go into a new client/errors.go to keep things a little cleaner. client/client.go was a bit messy with a bunch of error types. They're still in the same scope (i.e. in the client package) so nothing else had to be changed by moving them.
Signed-off-by: David Lawrence<EMAIL_ADDRESS>(github: endophage)

also as a breadcrumb, this partially addresses https://github.com/docker/notary/issues/932