[FEATURE] Support KEYS_ONLY secondary index

given a Example Table with secondary index that ha projection_type = 'KEYS_ONLY':
class Example(Dyntastic):
    __table_name__ = "example"
    __hash_key__ = "id"
    __table_host__ = "http://localhost:8000"
    __table_region__ = "us-east-1"

    some_required_attribute: str

when you get the results from dynamodb only return the __hash_key__ because of projection_type, this raises an error when calling the query() method because some_required_attribute is missing.
query_results = cls.query(
    A.is == id,
    index="example-index",
)

You can make optional all the fields to make this work, but I think that is a bad idea when using schema validation, lol.
Feature Idea:
When querying secondary indexes with KEYS_ONLYS projection would be great to:
(1) disable the validation of the pydantic schema upon getting the data and validate only keys and return the object with the partion keys only.
(2) [optional argument for query] query method return the full object using GET operations after getting (1)

@flolas This is supported in 0.12.0. You can pass load_full_item=True to automatically refresh and get the full item. I haven't tested with INCLUDE projection indexes, but it should also work in that case.


python3Packages.cryptography: 3.1.1 -> 3.2 (security, CVE-2020-25659)

SECURITY ISSUE: Attempted to make RSA PKCS#1v1.5 decryption more
constant time, to protect against Bleichenbacher vulnerabilities. Due to
limitations imposed by our API, we cannot completely mitigate this
vulnerability and a future release will contain a new API which is
designed to be resilient to these for contexts where it is required.
Credit to Hubert Kario for reporting the issue. CVE-2020-25659

Motivation for this change
Things done

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

[x] 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"
[x] 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)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

We also have a 2.9 version, should we apply the same patch there? Is that version now considered "insecure"? The CVE description says everything < 3.2 is vulnerable.

We also have a 2.9 version, should we apply the same patch there?

Yeah, I think we should try to apply https://github.com/pyca/cryptography/commit/58494b41d6ecb0f56b7c5f05d5f5e3ca0320d494, the tests should hopefully cover that code path.
Personally I'd like to mark it as insecure, but I don't think we should given that there are probably still a lot of legacy Python 2 packages around that depend on it :o

Is that version now considered "insecure"?

AFAIK, yes. When I opened the PR the CVE details weren't available, but now it seems pretty clear. Though I'm not sure if / how many Python packages are really affected by this (and how practical the attack is for them). (But I don't mean that we should just ignore it.)


VNET is now supported for Azure Image Builder DevOps task

There is a VNET option that works when configuring the Azure Image Builder DevOps Task.

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

@kof-f – Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"

@ericd-mst-github Can you check with Kofi on this?

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


Animating on spannables, using TextView as base class

Performance should be improved by flattening view hierarchy, all TextView attributes should be supported

Sorry for not taking look at this merge request earlier on, I will do so in next days.
Any outside opinion as always is appreciated.


not overlaying the targeted button

[x] I have verified the issue exists on the latest version
[ ] I am able to reproduce it

Version used:1.8.0
Stack trace:
Android version:6.0

tried code...
   new TapTargetSequence(this)
            .targets(
                    TapTarget.forView(findViewById(R.id.button), "Button 1", "This is button 1 click").tintTarget(false).targetRadius(100).transparentTarget(false),
                    TapTarget.forView(findViewById(R.id.button2), "Button 2", "This is button 2 click").tintTarget(false),
                    TapTarget.forView(findViewById(R.id.button3), "buttton 3", "This is button 3 click").tintTarget(false))

            .start();

Tap targets are usually for icon sized things. If you want to have your button appear under the tap target, you will need to increase the target radius like you have already and you will need to set transparentTarget to true.


Contact Us form not working

When you submit the Contact Us form an error results.

URI changed from ../api/send**F**eedback to ../api/send**f**eedback.

Issue re

URI changed from ../api/sendFeedback to ../api/sendfeedback.


[Feature] Support ElasticSearch 7 as backend storage

Add storage-elasticsearch7-plugin module
Motivation:
Support ES7 as storage
Modification:
Add storage-elasticsearch7-plugin, make the compilation passed, add maven profiles to distinguish different version of ES
Result:
ES7 storage plugin can co-exist with ES6 storage plugin
Most of the codes come from the existed ES6 plugin, and the credits should belong to @peng-yongsheng

Before all codes related discussion, a question, as this profile based solution, how should developers run the local test for both ES6 and ES7? I mean in the IDE.

Before all codes related discussion, a question, as this profile based solution, how should developers run the local test for both ES6 and ES7? I mean in the IDE.

Simply switch the profile in maven tab

and I'm not sure if it's possible to achieve the same goal without using profiles, we have to build two distribution package, and have two dependency hierarchies

and I'm not sure if it's possible to achieve the same goal without using profiles, we have to build two distribution package, and have two dependency hierarchies

That is why I proposed two starter module. After you have that, you don't need profile anymore.
From my understanding, our project repo has been too complex already, if need profile to package different dist, it is very hard for a new developer.

Another thing, if you have the exclude and dependency right in new starter and storage, you could use most of existing es6 storage codes, rather than copy them again. It increases the payload to maintain codes. You should just need to implement the ES7 DAO, if ES API changed.

@wu-sheng  Review comments are addressed, please recheck when you have got some time

/run agent-work-load-1

/run agent-plugin-test-1

@kezhenxu94 You need to sync and resolve the new YAML file. Facing conflicts.

Hi @kezhenxu94
I found thread_pool.index.queue_size is deprecated in es7.4.2. Do we need to update the FAQ of the document?

Hi @kezhenxu94
I found thread_pool.index.queue_size is deprecated in es7.4.2. Do we need to update the FAQ of the document?

The FAQ is for users who are facing the exceptions, if the thread_pool.index.queue_size is not set by default in ES7, which I thing is the case, the users won't reach the FAQ

What we recommend for es7? Is write queue size still there? Add these two in document directly?

@dmsolr I think we also need to update the document, another PR for that?

@dmsolr I think we also need to update the document, another PR for that?

Yes, I will do that.

/run agent-plugin-test-4

/run agent-plugin-test-4

/run ci

/run agent-plugin-test-3

Merging.


Switch GT -> LT

Why is NonEmptyText 10 length between 0 - 10, and not length >= 10?
My intuition for NonEmpty containers is that they're specifying a Lower Bound, not an Upper Bound.


help me how to fix this

how to fix these errors? I'm using the latest version of Python

Not sure whats causing the exact error. You can try disabling live microphone, that way there will be no need got the DLL thats causing the issue.


fails to install

~/sabre-master$ make
gcc -Wall -pedantic -DVERSION=1.00 -O3 -c src/barcode.c
FATAL:/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../libexec/as/x86_64/as: I don't understand 'm' flag!
make: *** [barcode.o] Error 1
Any suggestions?
I also heard that sable requires something called  zlib - is this the reason for this error? Where and how do I get zlib?
Thanks!

Hi, I have the same issue. Did you solve it ? or do you have some idea about this problem ? @l-yampolsky


Show latests comments on index.

A suggestion.

I prefer this kind of feature to be a moderator one.

Moderators need to be able to police them.
Members aren't generally going to need to see what is on other people's profiles on the index page.  Threads are different because they are able to reply to them.
Permissions would have to be taken into consideration if members were able to view this.

I don't think it is hard to implement this. Also note that the comments feature could be used as a status one.
I have also been thinking about showing my comments to other users profiles in my own comment list. A la Facebook. I would like to think of MyProfile as a full profile mod pack.


[BEAM-8166] Allow in process workers to exit without killing the process.

Allow for runners that do not spawn distinct processes for workers. InProcess runners can be useful for testing, or to support for any future native go runner. When running multiple pipelines simultaneously, it's desireable to allow for some measure of independance as well.
Responding fatally on GRPC connection terminations prevents these behaviours.
Further, improve the error messages to include additional context when there are GRPC issues.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @youngoli

Run Go PostCommit

Excellent question, and you're correct the new mode isn't presently available for any public runners at this time. Flink, Spark, Dataflow all rely on containers, which don't run into this.
However, native Go runners might choose to make different calls, or runners where the runner half a worker is linked into the same binary run into this, such as the internal Google runner I work on uses. It has an inprocess mode that can take advantage of this as well.


CLI: Omit metadata and attachment counts if stats are not present

After this change,
$ mcap info tests/conformance/data/OneAttachment/OneAttachment.mcap
library:
profile:
channels:

We should probably apply similar logic to "channels", but that will require changing the library to return a pointer instead of a map, which will require a library release first.

We could also consider keeping the output lines but saying attachments: unknown explicitly instead of just omitting the line.

yeah, I like that idea

Updated output:
$ mcap info tests/conformance/data/OneAttachment/OneAttachment.mcap
library:
profile:
channels:
attachments: unknown
metadata: unknown


Fixed InterconnectedSystems name bugs.

3 fixes to InterconnectedSystem's init:

It wasn't setting the name properly
It also wasn't setting the output and input names properly
I also made it so that instead of using generic state names, it uses subsys.statename when available

For example, if we Interconnected these two systems
System: predprey
Inputs (1): u,
Outputs (2): H, L,
States (2): H, L,

System: control
Inputs (3): Ld, u1, u2,
Outputs (1): y[0],
States (0):

we would get
System: (None)               # point (1)
Inputs (0):
Outputs (3):                 # point (2)
States (2): x[0], x[1],      # point (3)

Now instead, we get
System: io_closed
Inputs (0):
Outputs (3): y[0], y[1], y[2],
States (2): predpreyH, predpreyL,

Coverage decreased (-0.1%) to 84.008% when pulling b68872927b79cf5c10dbf7ae27f93affbefb5ffe on samlaf:interconnectedsystems into 6b24bb42a8da5b15cb79699e74fb33b30ba7935a on python-control:master.

Here's a short code snippet to visualize the signal names for different Connections:
import control

nlios111 = control.NonlinearIOSystem(
    lambda t,x,u,params: x, inputs=2, outputs=2, states=2
)
nlios101 = control.NonlinearIOSystem(
    None, lambda t,x,u,params: u, inputs=2, outputs=2
)

series = nlios111 * nlios101
parallel = nlios111 + nlios101
neg = - nlios111
feedback = nlios101.feedback(nlios111)
dup = nlios111 * nlios111.copy() #if we remove the .copy() we get a warning and names are messed up
hierarchical = series*nlios111

print("1 input, 1 state, 1 output:\n", nlios111, "\n")
print("1 input, no state, 1 output:\n", nlios101, "\n")
print("Series connection: sys[0] * sys[1]\n", series, "\n")
print("Parallel connection: sys[0] + sys[1]\n", parallel, "\n")
print("Negative connection: -sys[0]\n", neg, "\n")
print("Feedback connection: sys[1].feedback(sys[0])\n", feedback, "\n")
print("Connection with duplicate systems: sys[0] * sys[0].copy()\n", dup, "\n")
print("Hierarchical connection: series * sys[0]\n", hierarchical)

And the output after my last push:

1 input, 1 state, 1 output:
System: sys[0]
Inputs (2): u[0], u[1],
Outputs (2): y[0], y[1],
States (2): x[0], x[1],
1 input, no state, 1 output:
System: sys[1]
Inputs (2): u[0], u[1],
Outputs (2): y[0], y[1],
States (0):
Series connection: sys[0] * sys[1]
System: sys[2]
Inputs (2): u[0], u[1],
Outputs (2): y[0], y[1],
States (2): sys[0].x[0], sys[0].x[1],
Parallel connection: sys[0] + sys[1]
System: sys[3]
Inputs (2): u[0], u[1],
Outputs (2): y[0], y[1],
States (2): sys[0].x[0], sys[0].x[1],
Negative connection: -sys[0]
System: sys[4]
Inputs (2): u[0], u[1],
Outputs (2): y[0], y[1],
States (2): sys[0].x[0], sys[0].x[1],
Feedback connection: sys[1].feedback(sys[0])
System: sys[5]
Inputs (2): u[0], u[1],
Outputs (2): y[0], y[1],
States (2): sys[0].x[0], sys[0].x[1],
Connection with duplicate systems: sys[0] * sys[0].copy()
System: sys[7]
Inputs (2): u[0], u[1],
Outputs (2): y[0], y[1],
States (4): sys[6].x[0], sys[6].x[1], sys[0].x[0], sys[0].x[1],
Hierarchical connection: series * sys[0]
System: sys[8]
Inputs (2): u[0], u[1],
Outputs (2): y[0], y[1],
States (4): sys[0].x[0], sys[0].x[1], sys[2].sys[0].x[0], sys[2].sys[0].x[1],

@samlaf Can you add some unit tests to cover your new code and show that things are working?  The examples that you have in your comment from 20 May would probably be fine.  You might also try mixing named systems and named signals with unnamed systems/signals to make sure that nothing funny happens.  And, as a harder test, try creating a system/signal with a name that would conflict with the default name (eg, create a system whose name is sys[1] and combine it with an unnamed systems).

@samlaf Can you add some unit tests to cover your new code and show that things are working? The examples that you have in your comment from 20 May would probably be fine. You might also try mixing named systems and named signals with unnamed systems/signals to make sure that nothing funny happens. And, as a harder test, try creating a system/signal with a name that would conflict with the default name (eg, create a system whose name is sys[1] and combine it with an unnamed systems).

Should I be enforcing sys/signals names here? Wouldn't this render the API a bit too rigid (in case people want to change the naming conventions later, etc.)
Otherwise, what kind of unit tests did you have in mind?

Unit tests are failing because
nlsys * nlsys

no longer works.  It seems like it should be possible to take two copies of a system and put them in series (which is what this does) without generating an error.

Thank you for pointing this out @murrayrm, and thanks a lot to both of you two for your patience... newbie at work here.
I was concentrating on the signal_names test for too long and forget to rerun the other tests afterwards. Should be fixed now.
The system naming convention code should be fine now. Still need to write the signal name convention unit test though.

Looks like git got confused by the new unit test.  I don't see any actual conflicts, but you may need to fiddle with things to allow the automatic merge check to work.

It seems like a conflict between my branch and master branch?

That's what it's saying, but what's odd is that I don't see the conflict.  You added in a test and it shouldn't conflict with other tests.  If you agree, I can try to fix it via the web interface and we'll see if that gets things running again.

Sure, please do. I wouldn't know what to try anyways and would be scared to break other things.

I added the last unit tests. This is ready to be reviewed and hopefully should be close to done.

The changes remove test coverage of the functions set_input_map() and set_output_map()
https://coveralls.io/builds/32204258/source?filename=control%2Fiosys.py#L1284
In fact, those functions are not used by the whole package anymore. But they are public API. So a unit test for them should be present. (I would personally prefer that they are created in the style of #438. Feel free to add them as a PR against the bnavigator:array-matrix-tests branch)

Sure I can do that.
Just to make sure I understand, I think these functions were used in the add, mul, etc. functions which interconnect systems. Before they would create a blank interconnected system and then use the setters like set_input_map to populate the object. I changed it so that the "setting" was done in the init code.
Anyways, my question is: this code being "covered" before means that the unit test was calling them? So even if there wasn't a designed unit test for these specific functions, at least if they had caused a bug that would have caused some unit test to fail, but now that's not the case anymore, so we should add an explicit unit test. Is this correct?

Yes, that is correct. The unit tests should make sure that using those functions results in the documented behavior. Previously, this was more or less implicit by the tests when __add__ , __mul__. __neg__  and feedback were called.

Hi @samlaf, if you still intend to update your PR with the requested  unit tests, please do so based on the iosys_test.py in #438. We are discussing in #451 about the proper merge sequence, and #438 will likely be the first.

Hi @bnavigator, I was planning on doing these, but I got major neck pain recently, and am spending some time away from the keyboard. Are you waiting on me to merge the other PRs? I'm not sure when I'll have time to write these, but if it's not a hurry I will eventually get to them.

No hurry, get well soon! As I wrote, I removed the dependency in my PR so your PR can be merged later. Whenever you can get to it. You will have to rebase.


Add isUndoable property to manipulate resizable component width and h…

…eight with via props, for undo/redo apps.
I am working on an application where you are dragging onbjects into a stage, resize and move them, and have redo/undo buttons. Resizable components do not resize on passing new width/height props with current build. So i added special prop to see if width height shall be updatable via props.

@EugeneHlushko thanks. it looks good to me, but please rename property canUpdateSizeByParent.

@bokuweb, Thanks for appreciation, renamed!

@EugeneHlushko thanks!


Desktop UI testing error on sendTextInputCommand on JUnit4

I'm using:

kotlin 1.6.10
compose 1.1.0
compose.ui:ui-test-desktop 1.1.0

with a Desktop application.
I have the following UI test:
@get:Rule
val compose = createComposeRule()

@Test
fun `login button on start is disabled`() {
    runBlocking(Dispatchers.Main) {
        compose.setContent {
            AuthView()
        }
        compose.awaitIdle()

        compose.onNodeWithTag("auth-login-button").assertIsNotEnabled()
        val email = compose.onNodeWithTag("auth-email")
        email.performClick()
<EMAIL_ADDRESS>        compose.onNodeWithTag("auth-login-button").assertIsEnabled()
    }
}

I'm experimenting with this simple UI test where I get a node with a testTag and try to fill it with a text value. The actions result in a kotlin.NotImplementedError: An operation is not implemented. exception from the performTextInput() as shown below:

When I follow the stacktrace up to DesktopComposeTestRule.desktop.kt, I find that the performTextInput() method is actually not implemented:

I need these validations on my test suite, and I am not aware of other methods of testing UI with Desktop Compose, can I expect these to be implemented anytime soon? Or is there a workaround to my problem?
Thanks!

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Update Axios to 0.21.1

We should upgrade Axios due to Prevent SSRF:
https://github.com/axios/axios/pull/3410

Closing due to #381

Closing due to #381


Navigate Back

After you CMD-click on a symbol to navigate to it, we need some way to navigate BACK to where we were. Is there some existing binding already for this that I'm not aware of?
Thanks!

There are a couple of atom plugins that provide this functionality. Not at
my computer right now to look for links!
On 31 Jul 2015 16:57, "Clay Fowler"<EMAIL_ADDRESS>wrote:

After you CMD-click on a symbol to navigate to it, we need some way to
navigate BACK to where we were. Is there some existing binding already for
this that I'm not aware of?
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/OmniSharp/omnisharp-atom/issues/458.

Someone had mentioned https://atom.io/packages/cursor-history earlier, take a look at that.


Fix hookAll()

I didn't realize that hookClient only works on client sockets. Server sockets don't emit keylog events.
So, mention this in the docs, and fix hookAll to hook servers as well. It'd be ideal to hook tls.Server constructor, but there's no easy way to do so :(

I don't like how complex hookAll is getting... Hopefully it's working now

I hope to invest some time at evening to take a closer look. Thanks for the fixes! Merging it now.

(unrelated: it seems that Travis prints version number as "number", so "11.0" becomes "11" (see here)  - although build log shows that correct version was installed)

Yeah, that's odd :_


Images broken in readme

Images broken in readme

Thanks for the headsup @Noitidart! This is now fixed.

Thank you!


Nix: webpack support

Problem
Webpack fails to work on nix
Solution
Implements support for webpack for nix builds using dream2nix
@d4hines

$ direnv allow

direnv: loading ~/Documents/workspace/deku/.envrc
warning: Using saved setting for 'trusted-substituters = https://cache.nixos.org/ https://deku.cachix.org' from ~/.local/share/nix/trusted-settings.json.
direnv: export +AR +AS +CC +CONFIG_SHELL +CXX +DETERMINISTIC_BUILD +GHSTACK_TARGET_REPOSITORY +HOST_PATH +IN_NIX_SHELL +LD +LD_DYLD_PATH +MACOSX_DEPLOYMENT_TARGET +NIX_BINTOOLS +NIX_BINTOOLS_WRAPPER_TARGET_HOST_aarch64_apple_darwin +NIX_BUILD_CORES +NIX_BUILD_TOP +NIX_CC +NIX_CC_WRAPPER_TARGET_HOST_aarch64_apple_darwin +NIX_CFLAGS_COMPILE +NIX_COREFOUNDATION_RPATH +NIX_DONT_SET_RPATH +NIX_DONT_SET_RPATH_FOR_BUILD +NIX_ENFORCE_NO_NATIVE +NIX_HARDENING_ENABLE +NIX_IGNORE_LD_THROUGH_GCC +NIX_INDENT_MAKE +NIX_LDFLAGS +NIX_NO_SELF_RPATH +NIX_STORE +NM +NODE_PATH +OCAMLFIND_DESTDIR +OCAMLPATH +PATH_LOCALE +PYTHONHASHSEED +PYTHONNOUSERSITE +PYTHONPATH +RANLIB +SIZE +SOURCE_DATE_EPOCH +STRINGS +STRIP +SYSTEM_CERTIFICATE_PATH +TEMP +TEMPDIR +TMP +USE_NIX +XDG_DATA_DIRS +__darwinAllowLocalNetworking +__impureHostDeps +__propagatedImpureHostDeps +__propagatedSandboxProfile +__sandboxProfile +buildInputs +buildPhase +builder +configureFlags +depsBuildBuild +depsBuildBuildPropagated +depsBuildTarget +depsBuildTargetPropagated +depsHostHost +depsHostHostPropagated +depsTargetTarget +depsTargetTargetPropagated +doCheck +doInstallCheck +dontAddDisableDepTrack +name +nativeBuildInputs +out +outputs +patches +phases +propagatedBuildInputs +propagatedNativeBuildInputs +shell +shellHook +stdenv +strictDeps +system ~CAML_LD_LIBRARY_PATH ~NIX_SSL_CERT_FILE ~PATH ~TMPDIR

🎉
$ nix build .#deku

warning: Using saved setting for 'trusted-substituters = https://cache.nixos.org/ https://deku.cachix.org' from ~/.local/share/nix/trusted-settings.json.

🎉
But got the following output for dune build, ./sandbox.sh setup and ./sandbox.sh start:
File "src/tezos_interop/dune", line 9, characters 0-154:
 9 | (rule
10 |  (deps ./webpack.config.js ./tezos_js_bridge.js)
11 |  (targets ./tezos_js_bridge.bundle.js)
12 |  (mode fallback)
13 |  (action
14 |   (run webpack --env=%{profile})))
asset tezos_js_bridge.bundle.js 10.9 KiB [emitted] (name: tezos_js_bridge)
./tezos_js_bridge.js 7.56 KiB [built] [code generated]
external "stream" 42 bytes [built] [code generated]
external "util" 42 bytes [built] [code generated]

ERROR in ./tezos_js_bridge.js 3:33-60
Module not found: Error: Can't resolve '@taquito/taquito' in '/Users/gauthier/Documents/workspace/deku/_build/default/src/tezos_interop'

ERROR in ./tezos_js_bridge.js 4:22-45
Module not found: Error: Can't resolve '@taquito/rpc' in '/Users/gauthier/Documents/workspace/deku/_build/default/src/tezos_interop'

ERROR in ./tezos_js_bridge.js 5:27-53
Module not found: Error: Can't resolve '@taquito/signer' in '/Users/gauthier/Documents/workspace/deku/_build/default/src/tezos_interop'

3 errors have detailed information that is not shown.
Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.

webpack 5.72.0 compiled with 3 errors in 68 ms

@gsebil08,
Could you show me the output of $NODE_PATH in your shell?
It works fine on my-side, and if you managed to build it, it looks like its just a shell issue..

@r-muhairi
$ $NODE_PATH

zsh: no such file or directory: /nix/store/c5xbvmqg3fd1yrxilz1c5zfrwis6z709-sidechain-0.0.0/lib/node_modules/sidechain/node_modules:/nix/store/kmq0p8mbld14a64a7lj7a7syhi751z2d-__at__taquito__slash__taquito-11.2.0/lib/node_modules/@taquito/taquito/node_modules

FYI, dune isn't installed locally.

@gsebil08
Would you mind trying this version instead?
https://github.com/r-muhairi/deku/tree/nix-webpack-patch
It simply contains a wrapped version of the webpack package passing in NODE_PATH directly,
I couldn't reproduce still your issue, but its clearly due to NODE_PATH being missing, so hopefully this fixes it.

@r-muhairi 🎉 https://github.com/r-muhairi/deku/tree/nix-webpack-patch everything seems to be perfectly working on this branch!
Would you mind report the changes here, or in an other dedicated PR
@ulrikstrid you should try it!

Superseded by #612


Feature/remove private

Changed the private wording back to what it was at Brians request.

LGTM

do not merge this change.
gov uk pattern for private and public beta is to have the phrase - 'this service is in private beta [your feedback will help us improve it]? [] = link
so do not change it. :)


(bugsbash) remove repeat imports

Signed-off-by: aSquare14<EMAIL_ADDRESS>Pull Request template
Why is this PR required? What issue does it fix?:
Fixes package "k8s.io/api/core/v1" is being imported more than once and improves consistency.
What this PR does?:
Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[ ] Fixes #
[ ] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

PLEASE REMOVE BELOW INFORMATION BEFORE SUBMITTING
The PR title message must follow convention:
<type>(<scope>): <subject>.
Where:
Most common types are:
* feat        - for new features, not a new feature for build script
* fix         - for bug fixes or improvements, not a fix for build script
* chore       - changes not related to production code
* docs        - changes related to documentation
* style       - formatting, missing semi colons, linting fix etc; no significant production code changes
* test        - adding missing tests, refactoring tests; no production code change
* refactor    - refactoring production code, eg. renaming a variable or function name, there should not be any significant production code changes
* cherry-pick - if PR is merged in master branch and raised to release branch(like v0.4.x)
IMPORTANT: Please review the CONTRIBUTING.md file for detailed contributing guidelines.

@asquare14 -- Please rebase your branch.


The screenshot for sign-up needs to be updated.

The sign-up & create resource blades has been merged.

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

ID: b32aaa37-2293-5db2-9dc5-95be31be3a8b
Version Independent ID: 11ed3a7d-b4bb-00c0-828d-b61498947194
Content: Microsoft Azure Data Box Edge overview
Content Source: articles/databox-online/data-box-edge-overview.md
Service: databox
GitHub Login: @alkohli
Microsoft Alias: alkohli

@anoobbacker thanks for the feedback! I have assigned this issue to the content author, @alkohli , to look into your comment and update as appropriate.

@anoobbacker The signup is no longer relevant for GA docs. The new resource creation is already a part of the GA doc updates. These docs will go live on 3/25. I am going to close this as this already came through the regular content channel. Thanks!
#please-close This request came through a PM for this product but this is a part of GA content task list. And will be addressed via the regular content updates.


Do not define "NULL" string as a default value at nextflow_schema.json

Description
Some fields at nextflow_schema.json file define default values like an string ("default": "NULL") this will be a problem in the upcoming version of tower.nf. The "NULL" string will be set at the launchpad form and send to Nextflow when launching the pipeline. Finally the run will fail because Nextflow will interpret it as a string and not as an empty parameter.
Solution
Aligned with the discussion here about enforcing stricter rules for initialising params with no default value, I suggest to just set this fields to null at nextflow.config file and remove the default setting from the schema file. This will be compatible with the future tower.nf release.

Fixed in the recent PR.


[xerces-c] hard coded path to libnsl.so

On Linux platforms, XercesCConfigInternal.cmake contains are hard coded path to libnsl.so:
Linux x86-64 .../share/xercesc/XercesCConfigInternal.cmake
    INTERFACE_LINK_LIBRARIES "/usr/lib64/libnsl.so;\$<LINK_ONLY:Threads::Threads>"
Linux ARM64 .../share/xercesc/XercesCConfigInternal.cmake
    INTERFACE_LINK_LIBRARIES "/usr/lib/aarch64-linux-gnu/libnsl.so;\$<LINK_ONLY:Threads::Threads>"
Is this correct? The absolute path is causing the library to fail to load.

https://packages.debian.org/search?searchon=contents&keywords=libnsl.so&mode=path&suite=stable&arch=any
This is system library, not a vcpkg port. Doesn't the file exist?
What do you mean by "fail to load", a build-time issue or a run-time issue?

I would say the problem here is that vcpkg build of xerces-c is not portable, meaning that if you call
vcpkg install xerces-c

on machine A where libnsl is under /usr/lib64/ and copy the resulting library files to machine B where you build your executable that links to xerces then your application will fail to link if machine B has libnsl under a different location, say, /usr/lib/x86_64-linux-gnu/.
I believe that it is a port bug and there should be no absolute paths in any of the CMake config files that vcpkg generates. A simple workaround (not sure how robust though) would be to put "nsl" into INTERFACE_LINK_LIBRARIES instead of the absolute path to at least give linker a chance to find libnsl on machine B.

your application will fail to link if machine B has libnsl under a different location, say, /usr/lib/x86_64-linux-gnu/.

Sure, this is stating the obvious. I wanted to get an explicit confirmation that this is the error which the OP meant by "The absolute path is causing the library to fail to load."
But even with -lnsl, there might be errors, due do (rare) API changes. What is available at usage time simply varies independently from what was available at build time.
I wonder if a "validating XML parser" really needs that lib at all.


Change transaction list layout to display details

I think this layout will be more suited, as we can display preimage and hash in the right window, so user can just view it without copying it
We can also later expand it by more data (eg. links to nostr profiles if it's a zap?)

Alternative view
We could combine View balance and Recent transactions into one function


Requiring the list of providers as argument on workspace creation

@ricardo-espinoza Can you share why remove the default provider? I like short command. It is harder to use when more parameters become required.

@qwordy , we removed the default provider because of a change on the service side. We can't assume that any of the providers will be available in all subscriptions, and as such, some might have Microsoft/Basic and not others. We're discussing if we will have that in the future, but for now, requiring the user to be explicit on the provider ensures that they will only specify those available to them.


Get windows build working

Description
Initial PR for #1563. Fixes Windows CMAKE build.
Finally had time to come back to this - build on a fresh Windows11 machine, all steps to setup/reproduce included.
The change to core/plugins/CMakeLists.txt seems like it should be unrelated to this. I was unable to build because 'cudnn.h' was required, but the include path was not being passed to the compiler as the cuDNN module wasn't specified. This might not be a problem in other targets because commonly the cudnn files are just installed in to the cuda include/lib/bin dirs.
Also note - windows is generally case insensitive. The normal output dir is build/ but that doesn't work on Windows as there is a BUILD file. So I'm using out/ as the output. But that isn't in the .gitignore, and I haven't included a change for that in this PR.
Type of change

Bug fix (incomplete and probably breaks other build targets)
This change requires a documentation update

Notes to reproduce with Visual Studio Code (I didn't want to pull down the whole Visual Studio)

[ ] Install Visual Studio Code
[ ] Install Build Tools for Visual Studio 2022

Select "Desktop Development with C++"

Currently, this installs MSVC v143 - 2022. There are also options to install previous 2019/2017/2015 editions of MSVC

License term "1b Build Tools additional use right" allows using Build Tools to compile Open Source Dependencies
Also allows using Build Tools to develop and test Open Source Dependencies, to the minor extend of ensuring compatibility with Build Tools

[ ] Install CUDA 11.7.1
[ ] Install CuDNN <IP_ADDRESS>

Set cuDNN_ROOT_DIR

[ ] Install TensorRT <IP_ADDRESS>

Set TensorRT_ROOT
Add TensorRT_ROOT\lib to PATH

[ ] Install "libtorch-win-shared-with-deps-latest.zip"

Select the CUDA 11.7 version
Set Torch_DIR
Add Torch_DIR\lib to PATH

[ ] Clone TensorRT repo
[ ] Install C++ and CMake Tools extensions from MS

Change build to RelWithDebInfo

[ ] Update .vscode\settings.json
[ ] Clean, configure, build

/.vscode/settings.json
{
    "cmake.generator": "Ninja",
    "cmake.configureSettings": {
        "CMAKE_MODULE_PATH": {
            "type": "FILEPATH",
            "value": "$PWD\\cmake\\Modules"
        },
        "CMAKE_CXX_FLAGS": {
            "type": "STRING",
            "value": "-D_SILENCE_EXPERIMENTAL_FILESYSTEM_DEPRECATION_WARNING"
        },
        "Torch_DIR": {
            "type": "FILEPATH",
            "value": "X:\\libtorch\\share\\cmake\\Torch"
        },
        "TensorRT_ROOT": {
            "type": "FILEPATH",
            "value": "X:\\path\\to\\tensorrt"
        },
        "cuDNN_ROOT_DIR": {
            "type": "FILEPATH",
            "value": "X:\\path\\to\\cudnn"
        },
        "CMAKE_CUDA_FLAGS": "-allow-unsupported-compiler"
    },
    "cmake.buildDirectory": "${workspaceFolder}/out"
}

Awesome @bharrisau, thanks for opening this. Will take a look.


MOpt havoc doesn't appears in UI

I'm trying QEMU CompCov in combination with MOpt and I notoced that the results of MOpt havoc are not shown in the UI

As you can see only the information about trim are present.

did you run it with -L0?
for anything X > 0 it means it runs normal afl and only after X minutes of no new paths found it activates MOpt.
but even if running in MOpt it uses some of the original afl mutators. when it's special mutators are running you an see it in the "now tryiing" row.

btw - can you send me an email at<EMAIL_ADDRESS>to discuss planning aside from issues :)
Plan is to go into feature freeze on Sunday and do a release between Thursday and Sunday next week.

@andreafioraldi no creating an issue is the right thing.
the email is for overall afl++ planning and strategy as I dont have your email address :)
About the issue: I dont understand what you think is going wrong. is it that trim 4/4 should never happen in MOpt?

The issue is that this stuff https://github.com/vanhauser-thc/AFLplusplus/blob/866e22355c4bb00abe6ee43c7ff2231e93b15005/afl-fuzz.c#L7107 is not present in the MOpt fuzz routine. Without updating stage_finds and stage_cycles the "fuzzing strategy yields" fields in the UI are always 0.

ah ok. can you fix it? I am in-deep in rare_trim at the moment :)

Of course but not today, tomorrow morning i can.

no clue what that fix did :D - but thank you for taking care of it :)


py517: implement get_build_requires

This complies with the pep that will probably be adopted in any case, and doesn't break any existing functionality.

@jaraco This should be okay to go if the tests pass. It's not bulletproof but pip can always fall back.

Can you provide a link to the pep? Why use py517 instead of pep517?

Wow, it looks like it's been accepted.
https://www.python.org/dev/peps/pep-0517/
@jaraco I'll rename the module. I think pip was originally going to have it's own setuptools backend but if we put the backend in the setuptools repository, then pip can just require the latest setuptools by default and then execute the backend according to the standards. In other words, it move all of the monkeypatching and hackery out of pip and into setuptools, where it belongs.

@ncoghlan Can you specify the additonal concerns for out-of-tree builds?

@pfmoore

Hello all:
I have been attempting to resolve the horrible easy_install behavior where compiled wheels published on pypi are not used to fulfill setup requirements. To address this issue, I have submitted pull requests to both setuptools and pip that would allow a proprietary communication method that can later be easily adjusted to be fully PEP 517 compliant, saving work while resolving a specific issue.
However, everyone appears to be ignoring these pull requests, in my estimation, because PEP 517 is not fully completed. That’s fine, but partial PEP 517 compliance in one area is better than nothing at all, which is currently the default scenario.

So just as a reference we need to use wheel.egg2wheel to convert egg_info to dist_info.

What's the status of this PR? It's still tagged WIP, yet one comment says it's good to go. Other comments still say "we need", suggesting there's more work to be done.
I've added some comments about the implementation. I'm generally fine with new pep517 module, but I'm reluctant to add implicitly-defined hooks that complicate the (already complicated) behavior. I've suggested another possible approach which may prove simpler, but first, I think we need to understand how it is that this behavior is intended to be used.

What's the status of this PR? It's still tagged WIP, yet one comment says it's good to go. Other comments still say "we need", suggesting there's more work to be done.

The reason for this is that the PEP was modified after it was initially accepted. It's not currently acceptable to merge. I'm working on the pip side of the chain first and will then update this.

@jaraco Let's go ahead and get this in here as the pip people seem to be taking their time.

I've suggested another possible approach which may prove simpler, but first, I think we need to understand how it is that this behavior is intended to be used.

I added some tests that should help clarify this matter. Let me know if you have any other questions.


Unable to add custom domain with TXT

I am having a problem in attempting to create a custom domain with TXT. I am using the Azure DNS Zone. I have followed the steps provided in https://docs.microsoft.com/en-au/azure/static-web-apps/custom-domain?wt.mc_id=azurestaticwebapps_inline_inproduct_general&tabs=azure-dns#configure-txt-record-with-your-domain-provider.
It shows the status as validating for a long time and eventually disappear from the list. Screen shot:

I am not sure if every one else having this same issue.

How long time did you give it? For me, it took a couple of days.

Also, what is your domain?

@cnotoham Currently, if validation fails, it fails silently and the domain simply disappears from the list. We're working on getting the error to display on the screen instead. In the meantime, @miwebst might be able to help look into the error.

@cnotoham Currently, if validation fails, it fails silently and the domain simply disappears from the list. We're working on getting the error to display on the screen instead. In the meantime, @miwebst might be able to help look into the error.

Thank you @anthonychu for your reply. Hi, @miwebst, let me know what further information you need from me in order to investigate this issue. I tried again today with no luck.

It's working now after many attempts and I also noticed that it now shows the validation errors rather than disappear from the list. Closing this issue now.


Fix SampleBasedStatistics bug.

What changes were proposed in this pull request?
Fix SampleBaseStatisticsSuite bug #249 .
This happens with low possibility, for the sample based property.
StatisticsManager does not has this problem for its analyze function.
How was this patch tested?
unit test.

Thanks!


[feature request] Support custom keyboard shortcut

Please enable support to change the keyboard shortcut. For example, I'd prefer to use CMD + P for Search pages in logseq
Is there way to add customize the shortcuts?

CMD + P is the default search page shortcut on Mac. Everytime I search a page I end up pinned one page. No wonder after a whole day I have many pages pinned 😅

Released in https://github.com/pengx17/logseq-plugin-tabs/releases/tag/v1.11.0


sync

[ ] I understand that this repository is auto-generated and my pull request may not be merged

Changes being requested
Additional context & links

@rattrayalex ops sorry, made this by accident hehe


Fix typo in UraniumContentPage.md

Fix a typo in documentation. Replaced mothod by method.

Thanks for your contribution 🎊


voice command TOGGLE

would you mind adding "toggle" voice command ?

it has already be included, in italian is
It still has to be documented @plinioseniore

Tnx


mypy update

Using mypy instead of mypy-lang. Had to work about some existing mypy issues and filed one new. At least they are all known :)
A couple of fixes were actual bugs in types: missing variants, extra commas, misplaced type annotations. Also mypy started to check None return type more strictly (it's required in type signature and explicit return None is required for Option return type).
Fixes #168

Codecov Report

Merging #170 into master will decrease coverage by 0.47%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #170      +/-   ##
==========================================
- Coverage   97.02%   96.54%   -0.48%
==========================================
  Files          37       37
  Lines        2250     2258       +8
  Branches      440      440
==========================================
- Hits         2183     2180       -3
- Misses         35       46      +11
  Partials       32       32

Impacted Files
Coverage Δ

eli5/base.py
100% <ø> (ø)
:arrow_up:

eli5/formatters/utils.py
97.14% <ø> (ø)
:arrow_up:

eli5/xgboost.py
99.4% <ø> (-0.01%)
:arrow_down:

eli5/lime/lime.py
96.8% <ø> (ø)
:arrow_up:

eli5/formatters/html.py
100% <100%> (ø)
:arrow_up:

eli5/sklearn/text.py
97.75% <100%> (+0.05%)
:arrow_up:

eli5/sklearn/explain_prediction.py
96.34% <100%> (-1.81%)
:arrow_down:

eli5/lightning.py
76.47% <100%> (-17.28%)
:arrow_down:

eli5/formatters/text_helpers.py
94.11% <100%> (ø)
:arrow_up:

eli5/sklearn/explain_weights.py
97.6% <100%> (-2.41%)
:arrow_down:

... and 4 more

@kmike this is ready to get merged I think, but perhaps it's better to merge it after #169 , so that you don't have to delay the merge to fix more type errors if they arise.

yes - do you think it's ok? I think it's easy to fix if this is undesireable

I'm not sure; it seem the only practical difference is that after the change TypeError won't be raised if someone passes an argument unsupported by a library for an estimator which is not implemented for a library.

Ah, I didn't realise that - let me check if fixing it is not too
cumbersome.
Ср, 26 апр. 2017 г. в 17:55, Mikhail Korobov<EMAIL_ADDRESS>
I'm not sure; it seem the only practical difference is that after the
change TypeError won't be raised if someone passes an argument unsupported
by a library for an estimator which is not implemented for a library.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TeamHG-Memex/eli5/pull/170#issuecomment-297434870,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZ6pfL2y7rA2htd78NOn7akqVk8M8X5ks5rz1rcgaJpZM4NEojf
.

Hm, it seems coverage got down because explain_prediction_ovr_sklearn and explain_weights_ovr_sklearn are no longer called.

Hmm, actually I expected them to be called, maybe I missed something.
Yeah, new mypy+our singledispatch use are not a great fit at the moment, but hopefully it's possible to solve it once and for all.

The reason why coverage changed is that dispatch was happening not the way I expected:
In master, if we call explain_weights(ovr), it first gets dispatched to explain_weights_sklearn(ovr), and only then to explain_weights_ovr_sklearn. But in this branch there is no double dispatch, and explain_weights_sklearn is never called for ovr classifier in tests.
Now I'll check how to better fix it.

@kmike I decided to add an explicit call to explain_*_sklearn for OvR to tests instead of changing how OvR is dispatched - it looks simpler to understand. Hopefully now the coverage will improve.

Ok, thanks!


Add compacting body filters

Description

Add body filters to compact most common content types
Motivation and Context

Custom HttpLogForrmatters (different from JsonHttpLogFormatter) have also need to minify message body. To reduce code duplication from formatter to formatter, it could be extracted as delegating body filters.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.

To reduce code duplication from formatter to formatter, it could be extracted as delegating body filters.

But from what I see there is nothing shared, is there?

Well, it shared not as part of every single formatter, but as part of infrastructural body filters.
E.g.:

you have json http log formatter, but some of your endpoints are xml based, you will receive minified xml, as soon as xml compacting body filter will be configured.
you introduces another http log formatter (like #358) and you don't have to repeat logic to minify json or xml, or your custom format

I failed to realize that you moved the compacting from the formatter to the filter.
We could think about removing it from the JSONHttpLogFormatter in favor of registering those two filters by default, but that would be a breaking change. Maybe something for 2.x

Due to backward compatibility (JsonHttpLogFormatter marked as STABLE), I was not going into that direction myself. But I also find it would be a proper change.

So do we have some open tasks, preventing that PR ?

I released your changes as 1.10.0. :tada:


how to tell --reload  to ignore emacs lock files?

Hi. I am using
ghcid --reload=test-data/ -W -Tt1 -- -freverse-errors -isrc Main.hs

since evalution of t1 will read some files from test-data.
It's great that this works (and traverses test-data recursively) but it's  somewhat eager:
The test gets run twice: once when I actually save one such data file, and then when I change the file in the editor (without saving)  since Emacs then creates a lock file
(https://www.gnu.org/software/emacs/manual/html_node/elisp/File-Locks.html).
It seems that  ghcid  notices creation and deletion of lock files, or the resulting modification of the containing directory.
Is there a way to tell ghcid to ignore these files/events?

Unfortunately, not at the moment. The solution would be to integrate the filepattern library into Ghcid, so the --reload could take a pattern, which could include only the data files. However, I don't have any work planned to do that - but contributions welcome.


Thread safe logging

This PR adds Logger::setThreadSafeLogging(bool) and if true is passed the logging methods will lock a mutex before printing to logOutput and firing logEvent

Look good to me.
cc @dragonflylee @XITRIX

Good, not sure why we even need not thread safe logging, btw

Good, not sure why we even need not thread safe logging, btw
Is there any reason to make it "false" by default, or not use mutex without any checks?

I thought most application are single threaded or didn't log from async task thread so it would avoid the overhead of locking the mutex in those cases, but that overhead might be kinda small so I'm not really sure.
I let you decide what default value we should use for that property

I enabled thread safe logging by default. Could the PR be merge ?

Looks good to me


Convert to UFT8 without BOM...

Hello,
Is it possible to convert an Ainsi Text file to UFT8 without BOM, with UniConv ?
Big thank you for your great UniConv.
With Best Rehgards,
Michel

Hello,
Sure it is possible
You should initialize TUniConvContext-instance with UTF8<--SBCS(Ansi) encodings, and call Convert function
Look FileConversion.dpr demo
You can also use CachedTexts library: https://github.com/d-mozulyov/CachedTexts
It has automatically conversion classes
It should be something like that:
Reader := TByteTextReader.CreateFromFile(CODEPAGE_UTF8, FileName);
while (not Reader.EOF) do
begin
  Stream.Write(Reader.Current^, Reader.Margin);
  Reader.Skip(Margin);
  Reader.Flush;
end;

Big thank you for your help, I'll test your solution.

Hope it will be useful for you :)


Timing Issues with MI50 and performance metrics

When tracing with the performance counters enabled on MI50, the kernel timings are not correct. When testing against MI100, the problem does not appear.
OS: Ubuntu 20.04
Kernel: 5.4.0-104
ROCm version: 5.0.0
GPU: tested on 2 configurations one with MI50 and one with MI100

Could you please provide small synthetic test, build instructions and profiler options used to run?

Hi @arfio, if you are still experiencing this issue with the latest ROCm 6.2.0 release, please provide a minimal reproducible example which we can use to further investigate this issue.

@arfio, if you are still encountering this issue, please provide a MRE and I will re-open this ticket. Thanks!


Fix dependency version conflict

Purpose

Remove dependancies from Ballerina.toml so it will fetch the latest in the central.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add version of P4 reference code that compiles with p4c-dpdk compiler

using the Portable NIC Architecture

This PR is mostly a copy and paste of the P4 files in the dash-pipeline/bmv2 directory into a new dash-pipeline/dpdk-pna directory, with relatively small changes required to compile the code using the open source p4c-dpdk compiler.
See the README.md file added in this PR for more details.

I agree we should discuss these things and decide how this should be made into a PR we would actually want to merge.  This PR is primarily publishing my work in progress in an easily findable place that others can check out if they are interested.
I also believe that a single P4 code base with a few more #ifdef's should be a reasonable way to go.  There are not that many different lines of code between what is there in the bmv2 directory, and my modified version.

Andy, thanks for the response, I sort of figured you were (as usual) providing a well-documented and stable vantage point from which to make subsequent decisions. We shall discuss!

Hi @jfingerh I submitted a PR against your https://github.com/jfingerh/DASH/tree/add-p4-dpdk-reference-code branch to add p4c-dpdk docker image and make targets to the workflow, please take a look.

Folks, let's avoid ifdef in our code.  The use of it may balloon up if we let this one in.  So avoiding it from the get go is highly recommended.  Instead, we should put the target specific code (bmv2 vs dpdk) in separate files and keep the common code in common files.  Since we will be compiling target specific code (p4c-bm2-ss vs p4c-dpdk), let the makefile pick the right set of files and do the trick.

@mhanif I'm OK with approaches that do not add more ifdef's to the code, but. you do realize there are dozens already in there now, I hope?

Per Andy:

I also believe that a single P4 code base with a few more #ifdef's should be a reasonable way to go. There are not that many different lines of code between what is there in the bmv2 directory, and my modified version.

I think this carries a lot of weight. Maintaining parallel files carries its own burden, so it needs to be a balanced decision. And, the decision can be reconsidered in the future if #ifdefs become untenable.

i agree, better to consolidated into one file.

I think this carries a lot of weight. Maintaining parallel files carries its own burden, so it needs to be a balanced decision. And, the decision can be reconsidered in the future if #ifdefs become untenable.

@chrispsommers agreed.

Whether or not we merge the code or keep two versions, we could also make a CI pipeline to catch regressions.

Closing this PR in favor of a newer one that adds #ifdef's to the existing P4 code, instead of creating copies of the files as this PR does.  The newer PR is this one: https://github.com/sonic-net/DASH/pull/332


Kernel module is hb_rf_usb_2 instead of hb_rf_usb-2

I just tried to use a HB-RF-USB-2 for the first time on my host.
detect_hardware.inc was unable to find or use the device because the kernel module is called hb_rf_usb_2 instead of hb_rf_usb-2.
$ uname -a
Linux raspberrypi 5.15.32-v8+ #1538 SMP PREEMPT Thu Mar 31 19:40:39 BST 2022 aarch64 GNU/Linux

$ lsmod | grep hb_rf
hb_rf_usb_2            24576  3

As the Kernel Module binary is named hb_rf_usb-2.so the kernel module will be loaded with the current code and it will be loaded by udev directly when the matching usb id is detected.
So changing the mentioned code line will not solve your problem.
There did you get the HB-RF-USB-2 from? Can you provide pictures of it? What USB cable do you use? What hardware platform do you use? How do you power the hardware? Please provide output of the command dmesg | grep "hb".

$ dmesg | grep "hb"
                  24:   [    0.000000] CPU features: detected: Spectre-BHB
                 279:   [    3.369487] usb 1-1.1: Product: HB-RF-USB-2
                 454:   [    9.325255] usb 1-1.1: Found HB-RF-USB-2 with serial 00db28fe2ec1e8118dad6b713b0549ec at usb-0000:01:00.0-1.1
                 468:   [    9.517985] raw-uart raw-uart: Registered new raw-uart device using underlying device HB-RF-USB-2@usb-0000:01:00.0-1.1.
                 469:   [    9.522511] usbcore: registered new interface driver hb_rf_usb_2

I got the device from smartkram.de. Changing the code actually works.
USB cable. I'm using a Raspberry Pi 4 with Raspbian Bullseye 64-bits.
Here's a photograph of the module:

Is that output produced with the code changes or without them?

The code changes do not matter for the output since I only changed detect_hardware.inc which is executed by the service as far as I understand.

That code in detect_hardware.inc is just a backup to ensure, that the modules are loaded. As written, normally the modules are loaded automatically using the usb id and at that code place as backup using the .so file name.
Detection of the radio module will be done using the devices /dev/raw-uart*, which will be created after successful loading of the modules. So if you say, the output is the same, the radio module should be detected as well.


Add cli command to setup a new daemon in Digital Ocean

Create a cli command nimona daemon install --platform do that is able to spin up a new droplet in DO, setup docker if needed, and run the nimona daemon as a container.
A design that will allow us to "easily" add providers/platforms in the future might be nice.
Closes #151 as this approach seems saner.

@superdecimal do we wanna consider something like pulumi?
There seems to be a DO lib that supports at least creating droplets.
Not sure what else exists out there similar to that. I think you mentioned packer at some point, can it be used as a lib?


[macOS] Fix Bazel issue

Description
We've faced issue related Bazel 4.0.0. Please see: https://github.com/bazelbuild/bazel/pull/12882
We've decided to hardcode the 3.7.1 version of Bazel for the macOS images less than macOS 1015.
Related issue: #1733
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos1013, macos1014, macos1015, macos110

/azp run macos1013, macos1014, macos1015, macos110


Google Nest answers but nothing happens

Hello,
I have a Google Nest mini and a Windows 11 PC with Home Assistant OS in a Virtualbox VM.
I followed the installation procedure to install Plex Assistant.
But when I say "Hey Google tell Plex to play the Amadeus movie on the pc"
the Google Nest mini answers "Okay, action in progress"
but nothing happens on the pc.
Could someone help me to complete the installation?
Thank you ;)

The trigger method : IFTTT
The method used to install : HACS
My log files
home-assistant.log
2021-11-05 19:05:04 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration plex_assistant which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-11-05 19:05:04 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration plex_recently_added which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-11-05 19:05:04 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-11-05 19:05:04 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly 2021-11-05 19:05:04 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=21 from 2021-11-05 17:57:52.030171) 2021-11-05 19:05:07 WARNING (MainThread) [homeassistant.config_entries] Config entry 'MFC-J825DW E70045H1F316914' for brother integration not ready yet: Bad IPv4/UDP transport address BRN001BA98BB33E.local@161: [Errno -2] Name does not resolvecaused by <class 'socket.gaierror'>: [Errno -2] Name does not resolve; Retrying in background 2021-11-05 19:05:18 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Orange Livebox' for upnp integration not ready yet; Retrying in background 2021-11-05 19:05:36 WARNING (MainThread) [homeassistant.components.media_player] Setup of media_player platform denonavr is taking over 10 seconds. 2021-11-05 19:06:01 DEBUG (SyncWorker_0) [custom_components.plex_assistant.const] Media titles: 33811
home-assistant.log.1
2021-11-05 18:57:51 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration plex_recently_added which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-11-05 18:57:51 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-11-05 18:57:51 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration plex_assistant which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-11-05 18:58:17 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Orange Livebox' for upnp integration not ready yet; Retrying in background 2021-11-05 18:58:33 WARNING (MainThread) [homeassistant.components.media_player] Setup of media_player platform denonavr is taking over 10 seconds. 2021-11-05 18:58:53 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: plex_assistant
home-assistant.log.fault is empty

Try using the zip file again to restore the intent and see if that helps? What happens when you try to do it from the Dialog flow test console (right)?

Hello,
Thank you for your help.
I did the install process again and it is the same.
I think it is a problem with Plex Sensor because
during the installation, when I add
`sensor:

platform: plex_assistant`

in configuration.yaml
and then restart Home Assistant, it can not restart because of this line I added


axel: 2.17.10 -> 2.17.11

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/axel-download-accelerator/axel/releases.
meta.description for axel is: "Console downloading program with some features for parallel connections for faster downloading"
meta.homepage for axel is: "https://github.com/axel-download-accelerator/axel"
meta.changelog for axel is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/rddi9fl8vbawhfyx5c7d031hp6pzfvlc-axel-2.17.11/bin/axel passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 2.17.11 with grep in /nix/store/rddi9fl8vbawhfyx5c7d031hp6pzfvlc-axel-2.17.11
found 2.17.11 in filename of file in /nix/store/rddi9fl8vbawhfyx5c7d031hp6pzfvlc-axel-2.17.11

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
axel
docbookrx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rddi9fl8vbawhfyx5c7d031hp6pzfvlc-axel-2.17.11 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A axel https://github.com/r-ryantm/nixpkgs/archive/5131db104868020a5012388aa5e0efa677ea8d67.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rddi9fl8vbawhfyx5c7d031hp6pzfvlc-axel-2.17.11
ls -la /nix/store/rddi9fl8vbawhfyx5c7d031hp6pzfvlc-axel-2.17.11/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

axel

Maintainer pings
cc @pSub for testing.

Basic functionality looks good to me.


Redesign crx API

crx(['/path/to/manifest.json', '/path/to/**.js', '!/path/to/node_modules'], { options })
  .then(crx => {
    crx.options; // { options }
    crx.included; // => ['manifest.json', 'index.js'];
    crx.excluded; // => ['node_modules/jquery/dist/jquery.js', ...]
    crx.mapping; // => { '/path/to/manifest.json' => 'manifest.json', ... }

    crx.archive()
      .then(archive => archive.pipe(fs.createWriteFile('extension.zip')))
      .then(archive => crx.sign(archive))
      .then(stream => stream.pipe(fs.createWriteFile('extension.crx')));
  });

API

keys API
[ ] create Public Key
[ ] read Private Key
[ ] generate Private Key
crx API
[ ] crx(files, options) file selection constructor
[ ] pack().then(archive)
[ ] sign(archive).then(crx)
autoupdate API
[ ] getManifest(appId)

Under the hood we need to have:

[ ] generateAppId(publicKey).then(appId)
[ ] generateSignature(archive).then(signature)

Are dropped:

[ ] writeFile
[ ] load
[ ] options.rootDirectory, options.path and options.src

Options

ignore (defaults to ['*.pem', '.git', '*.crx'])
publicKey
privateKey (optional, to use #sign() only)
autoupdate

codebase
prodversionmin

I'm not sure that separating pack and sign is really needed. Without signing, pack becomes basically just a ZIP command, and there are already other modules for that.
Also, while this:
.then(stream => stream.pipe(fs.createWriteFile('extension.crx')));

looks quite nice, it would require keeping everything in memory. I thought the goal was to stream data without caching it.
AFAIK, there is no way to target specific position earlier in stream while piping. CRX header is at the beginning of a file, but to create header data, one has to know all the ZIP data to be written after the header.
In my version of CRX3 module there is a crx3stream but it works like a file write stream, i.e, not possible to pipe it to a next stream, because it "jumps over" header position, writes incoming ZIP stream while generating it's hash, after which it generates header data and writes it at the beginning of the file. So it does not have to keep whole ZIP in memory, but it does not allow to pipe CRX stream elsewhere (i mean, without reopening the file and reading from it later).


strange safari troubles

Dialog polyfill seemed to work fine at first, until I tried safari (iOS 10) in production mode (scripts compiled with uglify2). Then I got an exception in DialogManager:updateStacking() (line 495). No idea why so far.
After replacing all occurencies of .dialog with .dialog_ in dialog-polyfill.js, things seem to work again...

Line 495 is pretty innocuous—
for (var i = 0, dpi; dpi = this.pendingDialogStack[i]; ++i) {

I'll take a look again soon on iOS though. Can you give me a link to your compiled source—is this something running in production?

Not yet in production, but soon enough I hope.
But looking through the source, I can't see how the .dialog property without the _ at the end would make sense...
I'll see about the compiled source soon...

Re-reading your comment, it sounds like this might be a problem with Uglify and the polyfill. Can you post the compiled source of the polyfill?

Hmm, it's not the compilation it seems.
But after adding some sanity checkes, never on first load, only after navigating through a few pages of my app.
Testing with uncompiled dialog-polyfill.js, with and without my changes, iOS Safari still sometimes seems to miss a dialog tag...
But trying all the same steps with FireFox on the desktop, everything seems to work fine. With our without my changes. Even with the touch-emulation active.
Waiting now for our mac to finish updating, hopefully the debug tools there will give me better answers.

Hmm, I generously sprinkled some more ev.preventDefault() around in my code and added some more async decoupling to my code, and now it also works on safari. I really hope that company learns how to make a browser one of these days...
What still confuses me a bit is the .dialog vs. .dialog_ issue. I'm currently still running the version with my replacement changes applied, and all seems to be fine...

Can you please show me some code where this problem is occurring?
Unfortunately it's really hard to understand the problem from your comments.


slideclick

Renaming slideClick to slideclick in the documention

Coverage remained the same at 67.692% when pulling 93b2a86ba95591aaf8746b297e0548f3dceb3c13 on adrien-tech:patch-1 into 0e45e9a9ff6e2c3bcec795dde4875b8aadbe5556 on SSENSE:master.

Hey, good find @adrien-tech! Will merge this in now 🚀


AskarWallet.close: Invalid resource handle

We have a node project that is running test suites via jest.
In two of the suites, we are using AFJ to test mediation cases.
All AFJ agents are using Askar, and mediator agents are using postgres storage.
On MacOS, the tests are consistently working fine without any failures, but on Linux (Ubuntu 20.04) some test suites are failing to start due to Askar closing errors:
WalletError: Error closing wallet': Resource handle in use
      at AskarWallet.close (node_modules/@aries-framework/askar/src/wallet/AskarWallet.ts:383:13)
      at WalletApi.close (node_modules/@aries-framework/core/src/wallet/WalletApi.ts:97:5)
      at Agent.shutdown (node_modules/@aries-framework/core/src/agent/Agent.ts:218:7)

and
ERROR: Error closing wallet': Invalid resource handle {
        "error": {
          "name": "Error",
          "stack": "Error: Invalid resource handle\n    at NodeJSAriesAskar.handleError (/app/node_modules/@hyperledger/aries-askar-nodejs/src/NodeJSAriesAskar.ts:200:11)\n    at cb (/app/node_modules/@hyperledger/aries-askar-nodejs/src/NodeJSAriesAskar.ts:144:16)\n    at Object.<anonymous> (/app/node_modules/ffi-napi/lib/callback.js:66:27)\n    at Object.callbackTrampoline (node:internal/async_hooks:130:17)",
          "message": "Invalid resource handle",
          "code": 5
        },
        "errorMessage": "Invalid resource handle"
      }

Note, this is only happening on Linux (via Github Actions), and is not happening ALL of the time. Just most of the time.
Update: We use Node v18.16.0

I've seen this happen sometimes when we try close the wallet and afterwards still try to process an incoming message / use the wallet, even though it was already closed.

I think this must be isolated to the JS wrapper, passing in a Store handle after it has been removed.

Any idea how to fix this @TimoGlastra ? Our CI fails most of the time due to this

Could you provide maybe a repo with a minimal reproduction? That would really help in debugging the issue.
However, as this is happening on Github Actions (which is like really slow), I think it's just a race condition in your tests, and maybe not a problem on macOS as your local machine is a lot faster.
Is your agent processing any messages? Could it be that something is not fully awaited before closing the agent?
E.g. an issue I've run in quite often with AFJ is that it would keep picking up messages, and so then we'd close the wallet and it would still receive pickup messages, and thus cause issues. The solution was to first stop messages pickup, so the agent was for sure not processing anything anymore, and then closing it.

Hello @niall-shaw,
Any updates on the issue and if you were able to solve it?


docs: add ToC & file tree example

(the ToC is a bit tricky, since the auto-generated ToCs do not handle emojis in link too well, so that part is not fully automatable it seems.)

I wouldn't add a toc
users can just use the one at the top left

Thank you for the effort, but I don't want a Toc in there and I don't think that file tree is needed. Thank you though!


MudMenu: Add IsOpen property (#7266)

Description
Adds a new MudMenu.IsOpen property as described in #7266 . This makes it possible to handle the <ESC> key / back button correctly, by either closing the menu or by navigating backwards. It is especially useful for Blazor Hybrid apps.
fixes #7266
How Has This Been Tested?
There is a unit test checking the state after opening / closing the menu.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Looks good and thanks for adding tests too!
The only thing i am struggeling with, is how we can add this property to the docs.
There are no annotations (as far as i know) that fit, as this is not a parameter.
Anyone got ideas?
@henon

Hi @martinstoeckli I also had a similar ticket a few months ago but didn't have time to get back to it. I'm linking it here and when this is closed we can close that too. There was also an extended discussion there about the name and if it should be bindable too.
https://github.com/MudBlazor/MudBlazor/pull/6297

Now that I thought about it more too, I agree, it's a lot more complicated to make it 2-way bindable. Maybe someone who knows the library better could intervene cause I think there are other components that have a bindable open state property or similar. I'll also take a look on how other components are implemented when I get a free hour.
On the other hand a read-only property sure helps both your problem and my initial one. But I also think that we should be consistent to other similar components.

I remembered now, we were talking about the Mud popover with the Toggled property. But that behaviour could not apply here unless there's a big rework of the Mud menu with a breaking change: the Open property would have to be declared everywhere menu is used.
I'm not sure now which behaviour is better (I hope I'm not missing something, writing this on the go)

MudMenu with internal open state is easier to use but cannot be opened manually and it's open action cannot be listened to.
Mud popover with a bindable property, can be easily opened closed, can listen to state change and it's state is well known but it's harder to use since you need to declare it's Toggled state property everywhere it's used.

I think there's a bigger discussion here, but we should strive for consistency even if there are breaking changes.
@Mr-Technician @henon I'm also pinging you here since we had the initial discussion about this topic.

The way I see it, this PR is perfect as it is. It solves the problem of getting the state in order to close it programmatically. Ease-of-use for 99% of use-cases is our design goal so if for the rest 1% there is a programmatic workaround that is preferred over making it more complicated for the 99%.


[Snyk] Upgrade @spectrum-web-components/button from 0.40.5 to 0.41.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @spectrum-web-components/button from 0.40.5 to 0.41.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 23 days ago, on 2024-02-13.

Release notes

Package name: @spectrum-web-components/button

0.41.0 - 2024-02-13v0.41.0

0.40.5 - 2024-02-05v0.40.5

    from @spectrum-web-components/button GitHub release notes

Commit messages

Package name: @spectrum-web-components/button

0bf38fd chore: release new versions #publish
40701ac docs: move Menu Item out of mobile critical path loading
782560d fix(slider): high contrast improvements for filled track (#3952)
485a67c fix: support generating random IDs outside of secure contexts
124dd0d ci: expand lighthouse usage and reporting (#4027)
29866b4 test: leverage latest playwright (#4029)
0b80d7b test(coachmark): use locally cachable 64bit encoded images to ensure availability at VRT time (#4028)
4f9aa4a fix(tray): only allow "click" events when they "pointerdown"ed on the Underlay (#4020)
a94389c feat(coachmark): rename "sp-coachmark" to "sp-coachmark-indicator", add "sp-coachmark" (#3639)
80d2228 ci: add lighthouse benchmark in Github Actions (#3708)
4ff403e fix(popover): correct tip delivery size (#4018)
b49862f chore: bump @ spectrum-css/quickaction from 3.1.0 to 3.1.1
5cf1dec chore: bump cssnano from 5.1.14 to 6.0.3
01610c6 ci: update golden images cache
a11ef6b feat(icon): use core tokens
0b79d67 chore: bump pretty-quick from 3.1.3 to 3.3.1
c5e533f chore: bump @ spectrum-css/slider from 4.3.0 to 4.3.1
026a9c6 chore: bump @ types/prismjs from 1.26.0 to 1.26.3
b69b972 chore: use latest floating-ui and remove local plug-in work (#4012)
c78de32 docs: place demos at the top of each docs page (#3957)
a55342f docs(overlay): expand API coverage and demos (#3971)
3dc5b1f perf(combobox): prevent initial list render and update tests to prove that reduces render time

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Updated dependency manually


fix(JDBC): Syntax error on INSERT

Apache Phoenix does not provide an INSERT statement. Instead UPSERT is the only way to insert data to HBase via Phoenix.


.github/workflows: Get Go version from root go.mod file

Use the actions/setup-go v3 major version, which has support for configuring Go based on the version specified in the root go.mod file. This reduces the amount of changes needed to bump Go versions over time.
Signed-off-by: timflannagan<EMAIL_ADDRESS>

(recycling checks)


Cross-compiling sysrepo

Hi,
As per the instructions provided in the INSTALL.md file in the sysrepo github repository, there are a number of required libraries (libyang, google proto buffer, protobuf-c, libev and libredblack). Other than that, if we want to compile for an ARM architecture, we need to provide the REPOSITORY_LOC pointing to /et/sysrepo on the target's rootfs.
(1) Can I just compile (make only) by providing the /etc/sysrepo to any local directory on my host PC and then copy the sysrepo.h and other header files and sysrepod, sysrepoplugind to /bin or wherever the environment variable on my target is set to? Will this work if I manually copy those files and set my env variable properly?
(2) For the "Required libraries", is there something similar to building sysrepo for a cross-compiling or is it the same as the default option which is x86?
Thanks.

Hi,
So, I was trying to manually copy the libsysrepo.a, libsysrepo.so* files to my local directory and compile a piece of code that is supposed to run on my target (the compiler for the target is "arm-wrs-linux-gnueabi-g++", the linker is: "arm-wrs-linux-gnueabi-ld").
The compilation happened fine after I pointed the correct sysrepo.h and other header files but the linker gives me an error saying "libsysrepo.a: error adding symbols: File format not recognized: ld returned 1 exit status".
It seems the sysrepo library has to be compiled for this specific target . How can I do that? Thanks

It seems that you are having difficulties setting up your cross-compiling environment correctly. My suggestion is to use existing tooling which already handles these use cases well. If you're manually copying files around, you will have troubles.
There are makefiles/recipes for Buildroot, for example, in our Buildroot development branch. If you are using a different system, such as Yocto, you will have to adapt a similar technique yourself.
The short answers to your questions are "no". Also understand that there's no env variable, REPOSITORY_LOC is a build option which hard-codes the prefix into the resulting binaries. You cannot override it at runtime, and you will have to understand the build process if you want to customize it.

Hi,
I agree with @jktjkt, it's inconvenient to cross compile sysrepo from the ground up because you will need to cross compile libpcre, libyang, libredblack/libavl and sysrepo. There are sysrepo OpenWrt packages and we sometimes cross compile programs for OpenWrt and for that we use the cmake command:
$ mkdir build
$ cd build
$ # path to OpenWrt target toolchain
$ export STAGING_DIR=/opt/openwrts/staging_dir/target-arm_xscale_uClibc-<IP_ADDRESS>_eabi
$ export COMP=$STAGING_DIR/../toolchain-arm_xscale_gcc-4.8-linaro_uClibc-<IP_ADDRESS>_eabi
$ $STAGING_DIR/../host/bin/cmake -DCMAKE_FIND_ROOT_PATH=$STAGING_DIR --DCMAKE_LIBRARY_PATH=$STAGING_DIR -DCMAKE_C_COMPILER=$COMP/bin/arm-openwrt-linux-uclibcgnueabi-gcc -DCMAKE_C_FLAGS="-Wall -std=gnu99" -DCMAKE_BUILD_TYPE=Debug ..
$ make

Hope this helps.


Create deployments.yml

Terraform Format and Style 🖌success
Terraform Initialization ⚙success
Terraform Validation 🤖success
Terraform Plan 📖success
Show Plan
```terraform
data.aws_vpcs.selected: Reading...
data.aws_iam_role.name: Reading...
data.aws_iam_role.name: Read complete after 0s [id=LabRole]
data.aws_vpcs.selected: Read complete after 0s [id=us-east-1]
data.aws_subnets.selected: Reading...
data.aws_subnets.selected: Read complete after 0s [id=us-east-1]
data.aws_subnet.selected["subnet-0ffdb76131a10cb4a"]: Reading...
data.aws_subnet.selected["subnet-0882ea5606dafb700"]: Reading...
data.aws_subnet.selected["subnet-045bd3642cf85bbee"]: Reading...
data.aws_subnet.selected["subnet-01384f326c54262f5"]: Reading...
data.aws_subnet.selected["subnet-0ec5dba8893985b0e"]: Reading...
data.aws_subnet.selected["subnet-0ce3fcc2791a575a1"]: Reading...
data.aws_subnet.selected["subnet-0ec5dba8893985b0e"]: Read complete after 0s [id=subnet-0ec5dba8893985b0e]
data.aws_subnet.selected["subnet-01384f326c54262f5"]: Read complete after 1s [id=subnet-01384f326c54262f5]
data.aws_subnet.selected["subnet-0ce3fcc2791a575a1"]: Read complete after 1s [id=subnet-0ce3fcc2791a575a1]
data.aws_subnet.selected["subnet-0882ea5606dafb700"]: Read complete after 1s [id=subnet-0882ea5606dafb700]
data.aws_subnet.selected["subnet-0ffdb76131a10cb4a"]: Read complete after 1s [id=subnet-0ffdb76131a10cb4a]
data.aws_subnet.selected["subnet-045bd3642cf85bbee"]: Read complete after 1s [id=subnet-045bd3642cf85bbee]
aws_eks_cluster.eks-techlanches: Refreshing state... [id=eks-techlanches]
aws_eks_addon.aws_ebs_csi_driver: Refreshing state... [id=eks-techlanches:aws-ebs-csi-driver]
aws_eks_node_group.techlanches-node: Refreshing state... [id=eks-techlanches:techlanches-node]
No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
</details>
*Pushed by: @aoliveiramateus, Action: `pull_request`*


Fixes #54: Reduced repo size

Regarding #54:
I added an explanation to the README to explain why someone would want to use the "small" command.
I also ran git reflog expire --expire=now --all and git gc --prune=now --aggressive. It only took a couple of minutes, and it reduced the size of .git from 862268KB to 818808KB. A 43.46MB difference.
This fixes #54

I believe this commit only updates the README, it doesn't reduce the size of the repo.
it may have done it locally, but the push to the remote side hasn't changed.

Maybe he meant that long time users can prune it to make it smaller.

I believe this commit only updates the README, it doesn't reduce the size of the repo.
it may have done it locally, but the push to the remote side hasn't changed.

So it would seem...
I did read some dubius claims that this didn't do anything to remote. They said that for this to have an effect, the command would have to be ran directly on the original host (in this case, the github servers). Oh well. I still think it's worth adding that little comment to the README though

The issue is, the README then gets dated with more work/commits added - and its another thing to remember to keep up-to-date.
The amount of work it causes vs the pay off (the value of adding the size of repo).

In short: How many people need to know the size of the repo?

The issue is, the README then gets dated with more work/commits added - and its another thing to remember to keep up-to-date. The amount of work it causes vs the pay off (the value of adding the size of repo).
In short: How many people need to know the size of the repo?

That number doesn't need to be updated. It's just to give users a vague idea of how much baggage they'll download if they choose to do the full git clone.

I see it as another thing to maintain and update.
Could this be automated?

Closing due to lack of response


3d Shapes example crashes with headless rendering.

Bevy version
0.11
The release number or commit hash of the version you're using.
commit: 324c057b7195881397e2db2f0417cb105ff53c24
[Optional] Relevant system information
Linux VM headless
If you cannot get Bevy to build or run on your machine, please include:
cargo 1.72.0 (103a7ff2e 2023-08-15)
rustc 1.72.0 (5680fa18f 2023-08-23)
Ubuntu 20.04.6 LTS
Adapter info:
`AdapterInfo { name: "llvmpipe (LLVM 10.0.0, 256 bits)", vendor: 65541, device: 0, device_type: Cpu, driver: "", driver_info: "", backend: Gl }`

You should also consider testing the examples of our upstream dependencies to help isolate any setup-specific issue:

wgpu for rendering problems
winit for input and window management
gilrs for gamepad inputs

What you did
Describe how you arrived at the problem. If you can, consider providing a code snippet or link.
Running the following example fails:
xvfb-run cargo run --release --example 3d_shapes
Error:
xvfb-run cargo run --release --example 3d_shapes
    Finished release [optimized] target(s) in 0.16s
     Running `target/release/examples/3d_shapes`
2023-09-13T19:42:05.652763Z  INFO bevy_winit::system: Creating new window "App" (0v0)
2023-09-13T19:42:05.652878Z  WARN winit::platform_impl::platform::x11::util::randr: XRandR reported that the display's 0mm in size, which is certifiably insane
2023-09-13T19:42:05.652915Z  INFO winit::platform_impl::platform::x11::window: Guessed window scale factor: 1
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4732:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5220:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2642:(snd_pcm_open_noupdate) Unknown PCM default
2023-09-13T19:42:05.685682Z  WARN bevy_audio::audio_output: No audio device found.
2023-09-13T19:42:06.278328Z  INFO bevy_render::renderer: AdapterInfo { name: "llvmpipe (LLVM 10.0.0, 256 bits)", vendor: 65541, device: 0, device_type: Cpu, driver: "", driver_info: "", backend: Gl }
2023-09-13T19:42:06.294722Z  WARN bevy_pbr::ssao: ScreenSpaceAmbientOcclusionPlugin not loaded. GPU lacks support: TextureFormat::R16Float does not support TextureUsages::STORAGE_BINDING.
2023-09-13T19:42:06.319465Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Linux 20.04 Ubuntu", kernel: "5.15.0-1040-azure", cpu: "AMD EPYC 7V13 64-Core Processor", core_count: "24", memory: "216.3 GiB" }
Mesa: User error: GL_INVALID_ENUM in glTexStorage2DMultisample(target=GL_TEXTURE_2D)
2023-09-13T19:42:06.368964Z ERROR wgpu::backend::direct: Shader translation error for stage ShaderStages(FRAGMENT): gsamplerCubeArrayShadow isn't supported in textureGrad, textureLod or texture with bias
2023-09-13T19:42:06.368988Z ERROR wgpu::backend::direct: Please report it to https://github.com/gfx-rs/naga
2023-09-13T19:42:06.368998Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
thread 'Compute Task Pool (13)' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_render_pipeline
      note: label = `pbr_opaque_mesh_pipeline`
    Internal error in ShaderStages(FRAGMENT) shader: gsamplerCubeArrayShadow isn't supported in textureGrad, textureLod or texture with bias

', /home/azureuser/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-0.16.3/src/backend/direct.rs:3019:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `bevy_render::render_resource::pipeline_cache::PipelineCache::process_pipeline_queue_system`!
thread 'Compute Task Pool (11)' panicked at 'called `Result::unwrap()` on an `Err` value: RecvError', crates/bevy_render/src/pipelined_rendering.rs:145:45

The following example works though:
xvfb-run cargo run --release --example 2d_shapes
What went wrong
If it's not clear, break this out into:

I was expecting this to run. I am trying to take screenshots of my scene on a machine that does not have a gpu.
Unfortunately, bevy crashes.

Additional information
I've installed LLVMPipe as a software renderer.

Actually, this seems to be a duplicate of https://github.com/gfx-rs/naga/issues/2275.
Are there no 3d examples running as part of CI?

Are there no 3d examples running as part of CI?

Some are, and they work. You can find the screenshots taken here for Bevy CI, or check there for something outside CI that runs all examples and takes screenshots
Your example seems to be running with a Gl backend, which is not the most tested. And you're using an llvmpipe that is maybe kinda hold, at least from 2020.
Bevy CI is running with:
AdapterInfo { name: "llvmpipe (LLVM 15.0.7, 256 bits)", vendor: 65541, device: 0, device_type: Cpu, driver: "llvmpipe", driver_info: "Mesa 23.1.7 - kisak-mesa PPA (LLVM 15.0.7)", backend: Vulkan }
SystemInfo { os: "Linux 22.04 Ubuntu", kernel: "5.15.0-1041-azure", cpu: "Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz", core_count: "2", memory: "6.8 GiB" }

The problem was indeed with the GL backend.


add rule (vue-strong): Tightly coupled component names

https://vuejs.org/style-guide/rules-strongly-recommended.html#tightly-coupled-component-names

can we decide this programatically?

This depends a lot on having some context for each folder, should we assume the folder name is the correct prefix? Also, it wouldn't apply to all cases where for example in a /components folder you have reusable or shared SFC...
Is this getting done by another package? Like eslint-plugin-vue, to check for references 🤔

Is this getting done by another package? Like eslint-plugin-vue, to check for references 🤔

As I see they did not implemented it (yet)


Start fails due to relative path

I've encountered a minor hurdle with a brand new project. Trying to start an installed Neo4j server with the rails neo4j:start command fails. Failure output (I've redacted portions of the path with …):
$ rails neo4j:start
Starting Neo4j in development...
Active database: graph.db
Directories in use:
  home:         /Users/…/asdf/db/neo4j/development
/Users/…/asdf/db/neo4j/development
  config:       /Users/…/asdf/db/neo4j/development
/Users/…/asdf/db/neo4j/development/conf
  logs:         /Users/…/asdf/db/neo4j/development
/Users/…/asdf/db/neo4j/development/logs
  plugins:      /Users/…/asdf/db/neo4j/development
/Users/…/asdf/db/neo4j/development/plugins
  import:       NOT SET
  data:         /Users/…/asdf/db/neo4j/development
/Users/…/asdf/db/neo4j/development/data
  certificates: /Users/…/asdf/db/neo4j/development
/Users/…/asdf/db/neo4j/development/certificates
  run:          /Users/…/asdf/db/neo4j/development
/Users/…/asdf/db/neo4j/development/run
Starting Neo4j.
db/neo4j/development/bin/neo4j: line 418: /Users/…/asdf/db/neo4j/development
/Users/…/asdf/db/neo4j/development/run/neo4j.pid: No such file or directory
db/neo4j/development/bin/neo4j: line 417: /Users/…/asdf/db/neo4j/development
/Users/…/asdf/db/neo4j/development/logs/neo4j.log: No such file or directory
rails aborted!
Unable to run: db/neo4j/development/bin/neo4j start
/Users/…/.gem/ruby/2.5.1/gems/neo4j-rake_tasks-0.7.19/lib/neo4j/rake_tasks/server_manager.rb:249:in `system_or_fail'
/Users/…/.gem/ruby/2.5.1/gems/neo4j-rake_tasks-0.7.19/lib/neo4j/rake_tasks/server_manager.rb:32:in `start'
/Users/…/.gem/ruby/2.5.1/gems/neo4j-rake_tasks-0.7.19/lib/neo4j/rake_tasks/neo4j_server.rake:59:in `block (2 levels) in <main>'
/Users/…/.gem/ruby/2.5.1/gems/railties-5.2.0/lib/rails/commands/rake/rake_command.rb:23:in `block in perform'
/Users/…/.gem/ruby/2.5.1/gems/railties-5.2.0/lib/rails/commands/rake/rake_command.rb:20:in `perform'
/Users/…/.gem/ruby/2.5.1/gems/railties-5.2.0/lib/rails/command.rb:48:in `invoke'
/Users/…/.gem/ruby/2.5.1/gems/railties-5.2.0/lib/rails/commands.rb:18:in `<main>'
/Users/…/.gem/ruby/2.5.1/gems/bootsnap-1.3.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require'
/Users/…/.gem/ruby/2.5.1/gems/bootsnap-1.3.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `block in require_with_bootsnap_lfi'
/Users/…/.gem/ruby/2.5.1/gems/bootsnap-1.3.0/lib/bootsnap/load_path_cache/loaded_features_index.rb:65:in `register'
/Users/…/.gem/ruby/2.5.1/gems/bootsnap-1.3.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in `require_with_bootsnap_lfi'
/Users/…/.gem/ruby/2.5.1/gems/bootsnap-1.3.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in `require'
/Users/…/.gem/ruby/2.5.1/gems/activesupport-5.2.0/lib/active_support/dependencies.rb:283:in `block in require'
/Users/…/.gem/ruby/2.5.1/gems/activesupport-5.2.0/lib/active_support/dependencies.rb:249:in `load_dependency'
/Users/…/.gem/ruby/2.5.1/gems/activesupport-5.2.0/lib/active_support/dependencies.rb:283:in `require'
bin/rails:9:in `<main>'
Tasks: TOP => neo4j:start
(See full trace by running task with --trace)

Note the duplication of the file paths separated by a newline.
If I run the same start command db/neo4j/development/bin/neo4j start manually I get the same failure. However, if I run the same start command prefixed to adjust for the relative path, everything works:
$ ./db/neo4j/development/bin/neo4j start
Active database: graph.db
Directories in use:
  home:         /Users/…/asdf/db/neo4j/development
  config:       /Users/…/asdf/db/neo4j/development/conf
  logs:         /Users/…/asdf/db/neo4j/development/logs
  plugins:      /Users/…/asdf/db/neo4j/development/plugins
  import:       /Users/…/asdf/db/neo4j/development/import
  data:         /Users/…/asdf/db/neo4j/development/data
  certificates: /Users/…/asdf/db/neo4j/development/certificates
  run:          /Users/…/asdf/db/neo4j/development/run
Starting Neo4j.
Started neo4j (pid 83941). It is available at http://localhost:7474/
There may be a short delay until the server is ready.
See /Users/…/asdf/db/neo4j/development/logs/neo4j.log for current status.

Runtime information:

macOS 10.13.5
Ruby MRI 2.5.1
Bundler 1.15.2
Rails 5.2.0

Project creation:

rails new asdf --template=http://neo4jrb.io/neo4j/neo4j.rb --skip-active-record
echo 'gem "neo4j-rake_tasks"' >> Gemfile
bundle
rails neo4j:install[community-stable,development]

Neo4j database version: Community 3.4.1
neo4j gem version: 9.2.4
neo4j-core gem version: 8.1.4
neo4j-rake_tasks gem version: 0.7.19

Has anyone else encountered this?
Should the path used to initialise a ServerManager always be absolute? If you can point me in the direction you'd like this addressed, I'm more than happy to submit a pull request.


User profiles not able to download application builds in appcenter

What App Center service does this affect?
Appcenter android apk distribution not working for certain users
Describe the bug
Currently there are certain users in our organization that cannot download any android apks that are distributed through app center.  They can see the application buckets when they log in, but when they click to see the versions of the apk, app center throws an error and says there are no releases available.   Our current workaround is to go to the legacy hockeyapp website and download apks manually from there through a mobile browser and install them that way
To Reproduce
Steps to reproduce the behavior:

Go to app center apk or appcenter website
Click on an application to install
Receive an error message that there are no releases for this application, even though builds have been there for at least 3 years, and it is continually updated

Expected behavior
Expect the ability to continue to download and install android apks through appcenter with profiles that have not changed.
Desktop (please complete the following information):

OS: MacOs
Browser: Chrome

Smartphone (please complete the following information):

Device: Samsung Tab S2
OS: Android
Browser: Stock app center app and website in the browser
Version: Nougat

We're having issues with our iOS builds as well.

We are currently investigating this issue.

We have identified the issue and rolled out a fix. Can you see if your issue was fixed?

We had confirmation the issue has been resolved. Thanks for bringing this to our attention. Closing this for now.

FYI I am having this problem on a Samsung Galaxy Note 8 running Android v7.1.1

FYI, this problem comes again. Any solution to resolve