Build error : (*:buildFlatbuffers) Flatbuffers build failed.

Hi I try to reproduce the benchmark but i failed to compile the whole project. Your prebuilt docker image works fine but I am afraid that benchmarking within a container may affect its best performance. Have you met this flatbuffer error before? Thanks!
./build/sbt compile
./build/sbt: line 201: [[: .: syntax error: operand expected (error token is ".")
OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
[info] Loading project definition from /home/lqp0562/opaque/project
[info] Compiling 1 Scala source to /home/lqp0562/opaque/project/target/scala-2.10/sbt-0.13/classes...
[info] Set current project to opaque (in build file:/home/lqp0562/opaque/)
[info] Executing in batch mode. For better performance use sbt's shell
[info] Generating flatbuffers for /home/lqp0562/opaque/src/flatbuffers/Expr.fbs
/home/lqp0562/opaque/target/flatbuffers/flatbuffers-1.7.0/flatc: error: Unable to generate C++ for Expr
Usage: /home/lqp0562/opaque/target/flatbuffers/flatbuffers-1.7.0/flatc [OPTION]... FILE... [-- FILE...]
--binary     -b    Generate wire format binaries for any data definitions.
--json       -t    Generate text output for any data definitions.
--cpp        -c    Generate C++ headers for tables/structs.
--go         -g    Generate Go files for tables/structs.
--java       -j    Generate Java classes for tables/structs.
--js         -s    Generate JavaScript code for tables/structs.
--ts         -T    Generate TypeScript code for tables/structs.
--csharp     -n    Generate C# classes for tables/structs.
--python     -p    Generate Python files for tables/structs.
--php              Generate PHP files for tables/structs.
-o PATH            Prefix PATH to all generated files.
-I PATH            Search for includes in the specified path.
-M                 Print make rules for generated files.
--version          Print the version number of flatc and exit.
--strict-json      Strict JSON: field names must be / will be quoted,
no trailing commas in tables/vectors.
--allow-non-utf8   Pass non-UTF-8 input through parser and emit nonstandard
\x escapes in JSON. (Default is to raise parse error on
non-UTF-8 input.)
--defaults-json    Output fields whose value is the default when
writing JSON
--unknown-json     Allow fields in JSON that are not defined in the
schema. These fields will be discared when generating
binaries.
--no-prefix        Don't prefix enum values with the enum type in C++.
--scoped-enums     Use C++11 style scoped and strongly typed enums.
also implies --no-prefix.
--gen-includes     (deprecated), this is the default behavior.
If the original behavior is required (no include
statements) use --no-includes.
--no-includes      Don't generate include statements for included
schemas the generated file depends on (C++).
--gen-mutable      Generate accessors that can mutate buffers in-place.
--gen-onefile      Generate single output file for C#.
--gen-name-strings Generate type name functions for C++.
--escape-proto-ids Disable appending '_' in namespaces names.
--gen-object-api   Generate an additional object-based API.
--cpp-ptr-type T   Set object API pointer type (default std::unique_ptr)
--cpp-str-type T   Set object API string type (default std::string)
T::c_str() and T::length() must be supported
--no-js-exports    Removes Node.js style export lines in JS.
--goog-js-export   Uses goog.exports* for closure compiler exporting in JS.
--go-namespace     Generate the overrided namespace in Golang.
--raw-binary       Allow binaries without file_indentifier to be read.
This may crash flatc given a mismatched schema.
--proto            Input is a .proto, translate to .fbs.
--grpc             Generate GRPC interfaces for the specified languages
--schema           Serialize schemas instead of JSON (use with -b)
--bfbs-comments    Add doc comments to the binary schema files.
--conform FILE     Specify a schema the following schemas should be
an evolution of. Gives errors if not.
--conform-includes Include path for the schema given with --conform
PATH
--include-prefix   Prefix this path to any generated include statements.
PATH
--keep-prefix      Keep original prefix of schema include statement.
--no-fb-import     Don't include flatbuffers import statement for TypeScript.
--no-ts-reexport   Don't re-export imported dependencies for TypeScript.
FILEs may be schemas, or JSON files (conforming to preceding schema)
FILEs after the -- must be binary flatbuffer format files.
Output files are named using the base file name of the input,
and written to the current directory or the path given by -o.
example: /home/lqp0562/opaque/target/flatbuffers/flatbuffers-1.7.0/flatc -c -b schema1.fbs schema2.fbs data.json
java.lang.RuntimeException: Flatbuffers build failed.
at scala.sys.package$.error(package.scala:27)
at $97f688414a332020e117$$anonfun$$sbtdef$1$$anonfun$apply$2.apply(/home/lqp0562/opaque/build.sbt:219)
at $97f688414a332020e117$$anonfun$$sbtdef$1$$anonfun$apply$2.apply(/home/lqp0562/opaque/build.sbt:215)
at scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47)
at $97f688414a332020e117$$anonfun$$sbtdef$1.apply(/home/lqp0562/opaque/build.sbt:215)
at $97f688414a332020e117$$anonfun$$sbtdef$1.apply(/home/lqp0562/opaque/build.sbt:200)
at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
at sbt.std.Transform$$anon$4.work(System.scala:63)
at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:228)
at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:228)
at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
at sbt.Execute.work(Execute.scala:237)
at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:228)
at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:228)
at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159)
at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
[error] (*:buildFlatbuffers) Flatbuffers build failed.
[error] Total time: 0 s, completed Aug 14, 2020, 12:28:43 PM

Hi, we haven't seen this before but it could be because of an environment problem. What is the output for java -version for you?

openjdk version "11.0.7" 2020-04-14
OpenJDK Runtime Environment (build 11.0.7+10-post-Ubuntu-2ubuntu218.04)
OpenJDK 64-Bit Server VM (build 11.0.7+10-post-Ubuntu-2ubuntu218.04, mixed mode, sharing)

I don't think Opaque will work with OpenJDK 11. I believe this is limitation comes from our use of Spark 2.4.0 and Scala 2.11. I'd suggest downgrading to OpenJDK 8 (sudo apt install openjdk-8-jdk; sudo update-alternatives --config java).
It appears that our build/sbt script parses the Java version incorrectly for OpenJDK 11. We should upgrade to the latest one.
I'm not sure how that could produce the error you see, though.

Thanks for your suggestion! I have another concern here. Like I said before, I can run the prebuilt docker image provided by Opaque repo. I runseveral benchmarks after entering build/sbt console here are some results. The SparkSQL performance is good. BDB1 over 1million rows 0.2 seconds and BDB2 over 1million rows 3.5 seconds. BDB3 is 24.2seconds. However, the Encrypted Opaque mode is much slower than SparkSQL : over 1 million rows, BDB1 is 8 seconds. BDB2 is 32 seconds and BDB3 is 237 seconds. Have you tried running BDB queries over 1 million rows in your docker image? I am quite confused with this performance gap between the Opaque Encrypted and Spark SQL because according to Opaque NSDI17 paper, they should have similar performance over 1million rows.

In the single-machine setting, Opaque’s encryption mode performance varies from 58% performance gain to 2.5x performance loss when compared with the Spark SQL baseline.

When query over  BDB "tiny" dataset, the performance gap between Spark SQL and Opaque Encrypted is acceptable. You can refer to the results whose size=10000 in below logs.  Opaque paper does not mention the BDB dataset size in evaluation section. As the second author of Opaque paper, do you still remember it? Thanks!
20/08/20 17:23:46 INFO Utils: {"size": "10000", "system": "spark sql", "query": "big data 1", "distributed": false, "sgx": "sim", "time": 846.47859}
20/08/20 17:23:48 INFO Utils: {"size": "100000", "system": "spark sql", "query": "big data 1", "distributed": false, "sgx": "sim", "time": 208.491093}
20/08/20 17:23:54 INFO Utils: {"size": "1000000", "system": "spark sql", "query": "big data 1", "distributed": false, "sgx": "sim", "time": 237.443078}
20/08/20 17:23:57 INFO Utils: {"size": "10000", "system": "spark sql", "query": "big data 2", "distributed": false, "sgx": "sim", "time": 2257.048925}
20/08/20 17:24:05 INFO Utils: {"size": "100000", "system": "spark sql", "query": "big data 2", "distributed": false, "sgx": "sim", "time": 1913.835306}
20/08/20 17:24:59 INFO Utils: {"size": "1000000", "system": "spark sql", "query": "big data 2", "distributed": false, "sgx": "sim", "time": 3511.305008}
20/08/20 17:25:06 INFO Utils: {"size": "10000", "system": "spark sql", "query": "big data 3", "distributed": false, "sgx": "sim", "time": 6651.975442}
20/08/20 17:25:14 INFO Utils: {"size": "100000", "system": "spark sql", "query": "big data 3", "distributed": false, "sgx": "sim", "time": 8026.138777}
20/08/20 17:25:41 INFO Utils: {"size": "1000000", "system": "spark sql", "query": "big data 3", "distributed": false, "sgx": "sim", "time": 24220.148276}
20/08/20 17:25:44 INFO Utils: {"size": "10000", "system": "encrypted", "query": "big data 1", "distributed": false, "sgx": "sim", "time": 158.813051}
20/08/20 17:25:46 INFO Utils: {"size": "100000", "system": "encrypted", "query": "big data 1", "distributed": false, "sgx": "sim", "time": 1096.49591}
20/08/20 17:26:04 INFO Utils: {"size": "1000000", "system": "encrypted", "query": "big data 1", "distributed": true, "sgx": "sim", "time": 8236.803192}
20/08/20 17:26:07 INFO Utils: {"size": "10000", "system": "encrypted", "query": "big data 2", "distributed": false, "sgx": "sim", "time": 2409.730804}
20/08/20 17:26:36 INFO Utils: {"size": "100000", "system": "encrypted", "query": "big data 2", "distributed": false, "sgx": "sim", "time": 23512.367981}
20/08/20 17:33:16 INFO Utils: {"size": "1000000", "system": "encrypted", "query": "big data 2", "distributed": true, "sgx": "sim", "time":<PHONE_NUMBER>13}
20/08/20 17:33:20 INFO Utils: {"size": "10000", "system": "encrypted", "query": "big data 3", "distributed": false, "sgx": "sim", "time": 3318.489524}
20/08/20 17:33:43 INFO Utils: {"size": "100000", "system": "encrypted", "query": "big data 3", "distributed": false, "sgx": "sim", "time": 18009.025002}
20/08/20 17:38:31 INFO Utils: {"size": "1000000", "system": "encrypted", "query": "big data 3", "distributed": true, "sgx": "sim", "time":<PHONE_NUMBER>35}

Yes, this a known performance regression that was introduced in #12. It's because we switched from (manual) compilation to interpretation. If you want to reproduce the paper's performance numbers, I would suggest using this version of the code: https://github.com/mc2-project/opaque/tree/c42fe1bb758a93239fae284885c3d64991affddf

Also, I believe the BDB size in the paper was 1 million.

I see. Would you mind providing a docker image of this version? We are writing a paper and want to add Opaque in prior work comparison section. Clearly it is unfair to compare with Opaque with the slower one. I met too many errors during compiling opaque:( Thanks!

BTW. I will meet this error during building the docker image using docker/Dockerfile myself. Maybe you should replace the URL with a stable one.

Downloading sbt launcher for 0.13.17:
From  http://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.13.17/sbt-launch.jar
To  /home/opaque/.sbt/launchers/0.13.17/sbt-launch.jar
Download failed. Obtain the jar manually and place it at /home/opaque/.sbt/launchers/0.13.17/sbt-launch.jar

I am trying to build the c42fe1bb758a93239fae284885c3d64991affddf version opaque which uses a different version of sbt. I may finish this myself successfully. I will update to you soon.

Unfortunately I don't have a Docker image of that version, so I'd have to go through these steps as well.
Regarding the sizefunc deprecation error, perhaps you could try to disable fatal warnings by removing -Werror from https://github.com/mc2-project/opaque/blob/c42fe1bb758a93239fae284885c3d64991affddf/src/enclave/Makefile?

Oh i will. I did this before when I tried to compile it not in the docker container

This could be due to a libssl version problem. What version do you have installed? You may want to try building using version 1.1.0.

Thanks. It it SSL version problem. After downgrading to 1.0.2, I can compile opaque now.


Add Greater IPS Patch Support

Write logic for applying more IPS Patches than currently

I'd say that covers this


[QUERY] Max value for maxAutoLockRenewDuration

Query/Question
Are there any upper limits for serviceBusClientBuilder.maxAutoLockRenewDuration() property? Currently I've setup it to 3h, but I want to know whether it safe to have the value set for any number, let's say 24h. Do you have any recommendations for that?
Why is this not a Bug or a feature Request?
The functionality works fine, I just want to ask for proper usage or suggestions.
Setup (please complete the following information if applicable):

OS: iOS
IDE: intelliJ
Library/Libraries: azure-messaging-servicebus:7.13.1

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Query Added
[x] Setup information Added

@anuchandy could you please follow up with @garoplin on this question?

@anuchandy Any update on that question?

The lock token renewal is a recurring task on the SDK running on a host. It means the renewal will stop if the host node restarts (e.g., AKS pod) or certain SDK components need to restart.
All the states associated with the lock token renewal are scoped to the underlying AMQP connection (think of it as a TCP connection). So for some reason, if the connection goes down (e.g., networking disconnect), the state is also lost, so token renewal stops. Underneath, the SDK recovers and resumes receiving on a new connection. By Service Bus design, those old messages (with the lock expired) will be redelivered (if they haven't exhausted the delivery count) on a new connection.
The recommendation I heard from teams helping to build business solutions is - to split the application computation logic into stages where each stage doesn't have to renew for more than a few mins, then checkpointing it to continue to the next stage. This way, the application can sustain transient downtime and doesn't have to repeat the entire computation.
So to answer your question, technically, there is no upper limit, but it has a risk as the transient issue can happen anytime.


Miscellaneous UI Polishes

[x] Change Edit to Edit Username on Profile Screen
[ ] Make empty state views more inviting
[x] Get rid of likes in Liked view
[ ] Fix positioning of plus button in Liked View
[ ] Implement better design for Login Screen
[ ] Remove Login button and show loading screen after login attempt. Bring back button only on failure.

More to come...

Plus button in liked view? it isn't there

Yes

Yes it is not?

You'd have to check. It should only show up after logging into Spotify.

Add spotify view enhancement .. CHECK

UI Issues can be addressed when new designs are in. Closing this for now.


Hi is there any fix for this its asking for too much storage version 0.1.5

Isn't asking for "too much storage". The game is almost 90G (and it's keep growing), it needs the space to download the zips of the entire game and then more space to unzip the downloaded one. It will eventually delete the zips after installed, but there's nothing that can be done, the game is huge.

Isn't asking for "too much storage". The game is almost 90G (and it's keep growing), it needs the space to download the zips of the entire game and then more space to unzip the downloaded one. It will eventually delete the zips after installed, but there's nothing that can be done, the game is huge.

on windows it only asks for about 170gb for installation unzipping

and it does not end here i already have about 10gb more space than it needs yet it says that im short on space

Isn't asking for "too much storage". The game is almost 90G (and it's keep growing), it needs the space to download the zips of the entire game and then more space to unzip the downloaded one. It will eventually delete the zips after installed, but there's nothing that can be done, the game is huge.

on windows it only asks for about 170gb for installation unzipping
and it does not end here i already have about 10gb more space than it needs yet it says that im short on space

Different filesystem, different OS, probably even a different method. I never checked how windows does but isn't comparable in any way.
Also, check if you have time machine copies, they don't show towards the free space.


ash/device: Allow building device from handle+fns

Adds a constructor to build a device from a handle + functions.
Helps with interoperability with other vulkan wrappers where the user might have loaded the functions already.

Another wrapper will have its own function pointer table structs, and converting those to ash's would be incredibly tedious and fragile. Why not just let ash re-load the function pointers as usual?

Another wrapper will have its own function pointer table structs, and converting those to ash's would be incredibly tedious and fragile. Why not just let ash re-load the function pointers as usual?

Vulkano uses ash under the hood and therefore the same function pointer table structs. I don't know if there are other examples. Loading twice would obviously work but doesn't seem like it should be the only choice to me.

Then Vulkano has ash::Device already, or should start using it and take out the function pointers via fp_v1_x functions on ash::Device? Otherwise, is there an upstream issue for Vulkano why they are owning the function-pointer tables themselves, and why this change on the ash side is needed to accommodate for something?

Then Vulkano has ash::Device already, or should start using it and take out the function pointers via fp_v1_x functions on ash::Device? Otherwise, is there an upstream issue for Vulkano why they are owning the function-pointer tables themselves, and why this change on the ash side is needed to accommodate for something?

They don't want to use ash::Device because they don't like that it takes slices from what I understand.
I don't think that's something that is going to change.

Then Vulkano has ash::Device already, or should start using it and take out the function pointers via fp_v1_x functions on ash::Device? Otherwise, is there an upstream issue for Vulkano why they are owning the function-pointer tables themselves, and why this change on the ash side is needed to accommodate for something?

Also the request for this functionality is not coming from them, it's coming from me, I need to use both crates because vulkano is removing some unsafe wrappers which I use.
Thinking this is simething one might generally be interested in doing and also something that doesn't add maintenance burden I opened this PR.

To put it another way, it seems like it makes sense that loading the driver shouldn't be the only way of using the wrappers.

They don't want to use ash::Device because they don't like that it takes slices from what I understand.

Not liking the high level wrappers does not preclude using Device to load and represent the function pointer tables.

Loading twice would obviously work but doesn't seem like it should be the only choice to me.

It has significant upsides. For example, it does not force you to use the same version of ash as Vulkano.
That said, so long as we expose DeviceFn*::load, it makes sense to allow someone who uses those interfaces to put them together into a Device, so I'm okay with adding this API.

Thoughts:

Entry::from_static_fn already exists and is spiritually similar
If we're offering this for Device, we should also add it for Instance.

Thoughts:
* [`Entry::from_static_fn`](https://docs.rs/ash/0.37.2+1.3.238/ash/struct.Entry.html#method.from_static_fn) already exists and is spiritually similar

* If we're offering this for `Device`, we should also add it for `Instance`.

As suggested I added an analogous constructor to Instance

Hmm, one other consideration: these might force semver breakage when we support new minor versions of Vulkan. Do we otherwise necessarily break on such updates? If not, that makes this more costly. We could mitigate that by having a separate constructor for every minor version, in which case this should probably be renamed, though that feels rather ugly.

That's a good point, so would it be sufficient if I appended _1_3 to the current function? Or maybe, even though there is no real need to do so, I should add previous versions as well? (I suppose for consistency?)

would it be sufficient if I appended _1_3 to the current function?

I think that solves the problem. I'm interested in @MarijnS95's thoughts on this too.

Or maybe, even though there is no real need to do so, should I add previous versions as well?

Let's not; we can always add them in the future. It could confuse users targeting earlier Vulkan versions, but it's an obscure enough interface that I'm not too bothered.

Vulkano doesn't use ash for external interoperability but (at least initially) to not have to manually generate and keep up with low-level sys-like bindings and the function tables.
I was under the impression that Vulkano might not expose their internals nor ash types to more strictly guarantee the extra safety that they aim to provide around Vulkan by utilizing Rust semantics. But it seems to give you access to these (all function pointers including extensions) after all.
Perhaps we could ask @Rua to replace ash::vk::Device with ash::Device after all if this is intended.

Sure, we could provide this helper to be more lenient in how ash high-level wrappers are put together and used. After all, a user could pass a custom loader function with a massive match table that forwards already-loaded pointers to achieve the same, which is only cumbersome.
If you want to be consistent and provide it for Device and Instance, we should also provide it for Entry. Entry::from_static_fn() likewise only takes a loader callback which is used to load a few enumeration functions in vk::EntryFnV1_0 and vk::EntryFnV1_0.

Then the semver-breakage: this is tricky. We cannot easily version the function as all fields must be initialized (they are not Option<>al nor have a Default). The only thing we can do is:

Add newer (versioned) from_parts constructors (or version them from the get-go), marking any non-latest fn as #[deprecated] which is not breaking;
Initialize every newer version that isn't passed as argument (i.e. from_parts_v1_3 for a hypothetical new vk::DeviceFnV1_4) with a no-op loader function that returns NULL for every function.

Alternatively we can preemptively make this function return an Option/Result and utilize that, which would be an API break on newer versions but not an ABI break. The former is more likable though.

@Ralith what's your opinion on the from_parts naming?

I think from_parts is an idiomatic name for this.

The only thing we can do is ... version them from the get-go

That's what I had in mind, though I don't know if it's useful to deprecate older ones, since they'll continue to be reasonable to use when targeting older versions. Deprecating does let us remove them when we break for other reasons, which might be nice to limit growth, though I'm not sure if Vulkan is going to get that many minor versions, and we can always deprecate in the future.

Added a 1_3 postfix

That's what I had in mind, though I don't know if it's useful to deprecate older ones, since they'll continue to be reasonable to use when targeting older versions. Deprecating does let us remove them when we break for other reasons, which might be nice to limit growth, though I'm not sure if Vulkan is going to get that many minor versions, and we can always deprecate in the future.

I'd #[deprecate] them to point out that certain functions are never going to be initialized and will always panic, even if it is now clear from the function name and arguments. It's a discussion point we have globally anyway for the current loader functions being infallible, even if it might be helpful to make them infallible to have a clearer overview of what is available (on a side-note: this is problematic when functions within the same extension have different requirements: https://github.com/ash-rs/ash/issues/635).

Thanks @pac85. Looks like a few things remain before this is ready:

[ ] Add the function to Entry as well (suggested above);
[ ] List these additions in the changelog (copy-paste the title, with (#748) suffix at the bottom of the ### Added list;
[ ] Mark these functions as #[inline].

Thanks @pac85. Looks like a few things remain before this is ready:
* [ ]  Add the function to `Entry` as well (suggested above);

* [ ]  List these additions in the changelog (copy-paste the title, with `(#748)` suffix) at the bottom of the `### Added` list;

* [ ]  Mark these functions as `#[inline]`.

Those things should now be done and I've also rebased.
Let me know if there is something else I need to do or if you don't like the commit messages.

Let me know if there is something else I need to do or if you don't like the commit messages.

I generally try to (but not always) stick to a single commit, especially if all the messages would be the same, since it gets squash-merged in the end. Having a separate commit per entry/instance/device doesn't really add value here. But don't worry about squashing them, I can fix that up very easily while applying.
Sorry for the conflicts, we just removed a bunch of fields (with empty structs) in #752 :)

Looks good, thanks! I've been wondering if it makes sense to let e.g. Entry::from_static_fn() use the new function, but other than that I'll merge and backport this shortly.

Mmm so do I need to change it to use it?

I think that would look clean, yes.

I think that would look clean, yes.

And I suppose we should do the same with Device and Instance

Now constructors use the from_parts frunctions and I've solved the conflicts

Thanks, looks like it still wouldn't compile though, but let me allow the CI workflow to be sure.

Thanks, looks like it still wouldn't compile though, but let me allow the CI workflow to be sure.

compilation fixed now

Fantastic! Thanks everyone!


Disable motd-news.timer

https://raymii.org/s/tutorials/Disable_dynamic_motd_and_motd_news_spam_on_Ubuntu_18.04.html

systemctl disable motd-news.timer should be sufficient


Switch to std::wstring from std::string

To be able to handle wide characters Anagram was switched to use std::string instead of std::wstring.
fixes: #10

wstring isn't a good way to do this and isn't universally supported, so I am closing this.


Carloshenrique1996

Criação do Currículo.

 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.:x: CarlosHenrique1996 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Scroll-to-top button disturbs left-handed user's scrolling experience

Steps to Reproduce
1 - Use the left hand to scroll down the timeline
You'll notice that sometimes you'll press the button by mistake, or you will trigger a horizontal scroll accidentally.
Attachments
https://github.com/user-attachments/assets/c751ba99-77d9-459b-a5b6-44dd451ef207
What platform(s) does this occur on?
Android
Device Info
Samsung Galaxy S20+
What version of the app are you using?
Build version: <IP_ADDRESS>4; Bundle info: b2b5be5 (prod); Bundle date: 24091719; Platform: android
Additional Information
Right-handed users may not understand how this is bad because how we're conditioned to use depends on our dominant hand. Left-handed users are used to have the left area free for scrolling
An example of how the dominant hand can change the way we use the device is how left-handed users press the volume buttons of a smartphone (usually with the index finger instead of the thumb):

The same happens to a smaller degree with me, a right-handed user, when I accidentally slide my thumb over the post composer button.
Perhaps an option to place them on the top half of the device screen could be useful?

it'd be awesome if it were possible to press-and-hold the button to move it to an arbitrary location. an example of this is the "skip to next comment" button that's shown on the bottom-right in the official Reddit app when inside a post's comments

To be honest, I think that only showing the scroll-to-top button when the user is scrolling up is enough thinking about the complexity of other changes. It's the common behavior I see in other apps and it works perfectly (at least I was never bothered by this).
The header with the tabs already has this behavior of showing up again when the user scrolls up, so it would probably be just a new condition to show the scroll-to-top button. I tried to find it in the code to make a better suggestion, but I'm not so familiar with React Native and wasn't able to debug what makes the header appear.

I think we should just nix that button and move the dot into the tab bar which is pretty standard. Second tap on the bar already scrolls you up.

I think we should just nix that button and move the dot into the tab bar which is pretty standard. Second tap on the bar already scrolls you up.

Makes sense. I never noticed this behavior in some apps, just did it naturally 😅.


How to block saturday and sunday and block specific dates

https://github.com/wdullaer/MaterialDateTimePicker#additional-options
setSelectableDays()
setDisabledDays()
https://github.com/wdullaer/MaterialDateTimePicker#how-do-i-use-my-custom-logic-to-enabledisable-dates

@wdullaer  can you provide a sample code?

That's not the purpose of the issue tracker.
The information in the readme should allow you to write this code yourself.
The issue tracker is for reporting bugs with the library, not a forum for me to help you build your app.

@wdullaer can you provide a sample code?

I have written some code to
            // Setting Min Date to today date
            Calendar min_date_c = Calendar.getInstance();
            datePickerDialog.setMinDate(min_date_c);

            // Setting Max Date to next 2 years
            Calendar max_date_c = Calendar.getInstance();
            max_date_c.set(Calendar.YEAR, Year+2);
            datePickerDialog.setMaxDate(max_date_c);

There is also sample code to disable all SUNDAYS and SATURDAYS between above min max check here

That's currently not supported.
Someone opened a PR, but never bothered to incorporate the code review comments.
This will be the next feature I add, but I can't give an ETA. I haven't had a lot of spare time to work on this.
In general: it's better to open a new issue rather than resurrecting a 3 year old one.


Particles Animation repeat the first frame when using not square sheets

Godot version:
3.2 stable
OS/device including version:
Ubuntu 19.10
Issue description:
The Particles2D with Particles Animation repeat the first frame when it animates.
On a 3x2 sheet the Particles Animation shows in this order: 1, 2, 3, 1, 5, 6. But it must be: 1, 2, 3, 4, 5, 6
The sheet is correctly created from left to right and uppter to bottom.
I numerated the sheet and it repeat the number "1". So it is eventualy wrong.
Steps to reproduce:

Add a Particles2D node.
Load a texture with a sheet of animation (ie: Explosion)
Create a CanvasItemMaterial and set it to animate and fill the H and V frames properly.

Minimal reproduction project:

Workaround: Instead of 3x2 sheet I created a 2x3 sheet with the same frames and it works as expected.

Can't reproduce in 3.2.2.stable.
Minimum reproduction project: 36435.zip
Video (0m10s)

@tom-jk Thanks for testing it! I'll close this as resolved then.
If anyone else can still reproduce this in 3.2.2 or later, please comment so this issue can be reopened.

The problem is still present but different behaviour. And the same behaviour in CPUParticles2D. So it appears to be a bug inside of the sheet handling.
Bug#36435.zip

I found another discussion on this topic where the conclusion was that it must be related to older hardware or drivers: #31699
I can reproduce this bug on v3.3.3.stable.official [b973f997f]. I'm using Ubuntu 21.04 but my hardware is not old (AMD Ryzen 7 4800H with Radeon Graphics).

I looked into this issue and found out that the issue is caused by an imprecision in the shader when calling floor(). For example the parameter in floor() could be expected to be 1.0 and should be floored to 1.0 but in fact it is something like 0.999999 and gets floored to 0.0 (because of the imprecision). Have a look at my bugfix for the exact line of code #53233 . You will see that I added a 0.5 to the number of frames before using floor which ensures we wont get close to number where imprecision might happen.


Depth of Field support?

Hi Garrett!
Would it be possible to add DoF support? That would be stellar!

Hey @setpixel! It would definitely be possible to add more realistic camera parameters for things like bokeh blur and depth of field but it isn't high on my list of priorities at the moment. Things like more complete materials models, performance adjustments, and other features will probably come first.
If this is something you're interested in for professional work I'm happy to talk about funding the addition of more complex features to the project. Or if you'd like to look into contributing it yourself you're more than welcome and I can work with you on that!

Awesome! We are working on a storyboarding tool that uses threejs to create scenes to layout storyboards. Currently, we have a style that is white/gray meshes without inverse hull outlines. It does the job, but I've been wanting to change the look to something more beautiful: cleaner gray meshes with AO and maybe some really nice bounce lighting. I can show you examples. I've been following your work for a while, so when I saw this project, I got super excited!!!
I'm definitely interested in funding the addition of more features / helping wherever I can!!!

Great! Why don't you send me an email (in my profile) and we can set up a call to discuss details and what we can do.


MQTT commands response time

Is AT+MQTTPUB command maximum timeout 10 second?
How to shorten this timeout, like the <so_sndtimeo> option for AT+CIPSEND?

network timeout is 10 seconds, not the command timeout. you could change the network timeout in esp-idf/components/mqtt/esp-mqtt/lib/include/mqtt_config.h (MQTT_NETWORK_TIMEOUT_MS)

network timeout is 10 seconds, not the command timeout. you could change the network timeout in esp-idf/components/mqtt/esp-mqtt/lib/include/mqtt_config.h (MQTT_NETWORK_TIMEOUT_MS)

Thanks for your reply!


Questions about moderation

I have a couple of questions regarding moderation:

When the buyer or seller initiates a moderated dispute, how does chat work with the moderator? Are there only two separate bilateral chats between the moderator and the buyer/seller? Is a 3-way chat with the moderator, buyer and seller also created?
What is the process for the buyer to provide OpenBazaar evidence to the moderator? For example, the buyer may want to disclose the OpenBazaar chat that has happened with the seller. Should we aim to have this disclosure tamper proof by having chat messages signed?

UI needs to send separate messages to the other two parties.

There isn't a way to do that atm.

Closing in favour of #362.


Fix HPACK Dynamic Table Cleanup

Fix #6748. This is introduced by TS-3719, it was trying to fix a bug.

The table size is reduced by the by max size - new size instead of current size - new size. This causes the table to try to delete items that don't exist.

We don't need to worry about this with the current code, because we're using a for loop now.
https://github.com/apache/trafficserver/blob/4638ddcc2848da53b94f8678d22057d8efda8df3/proxy/http2/HPACK.cc#L427

96bd1fa didn't break anything it fixed a security issue. The check it done inside the while loop to prevent deleting a header that didn't exist. After it was refactored the check is outside of the for loop. Looks like whoever refactored it created the bug.

I agree that 96bd1fa fixed a security issue, but I'd say the fix was not the way it should. As long as the eviction logic is correct, the function doesn't cause a compression error.

IMO, we need more tests to cover edge cases like this PR has.

Cherry-picked to v9.0.x branch.

Cherry-picked to 8.1.x


Deprecation notice about parseLinks() method

Composer output is getting flooded with:
Deprecation Notice: Composer\Package\Version\VersionParser::parseLinks is deprecated. Use \Composer\Package\Loader\ArrayLoader::parseLinks() instead

See #133, #135.


Buying a House: Migrate deprecated keyCode to KeyboardEvent.key

Changes

Buying a House: Migrate deprecated keyCode to KeyboardEvent.key.

How to test this PR

Check http://localhost:8000/owning-a-home/explore-rates/ and see that loan amount isn't updated when the enter, arrow, shift, or tab keys are pressed. A non-numeric value can't be entered.

Coverage failure is N/A. It's because I'm touching those files.


Add Strava heatmaps

These have max zoom level of 12, so I'm not sure if you want to include them.

I'm not sure if the heatmap is supposed to be used by third-party apps?
Where did you get the URL? What are the terms of use?

I've taken it from JOSM, the way you described it in #630


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 11:48:29 on 2023.04.17
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 1, errors out: 0
Original problem ID: 18497
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=18497

Problem has been resolved in 3m 0s at 11:51:29 on 2023.04.17
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 18497


Issues with build steps

Some things I've noticed while building.
First, I think ctags is not needed to build this.
Second, nodejs bower package is needed, so
sudo apt-get install -y nodejs
npm install -g bower

should be added.
Third, bower seems to be deprecated: npm WARN deprecated<EMAIL_ADDRESS>..psst! While Bower is maintained, we recommend yarn and webpack for new front-end projects! Please read our blog for more.
Fourth, the service names do not match, i.e. it should be otbr-agent and otbr-web

ctags is needed when doing distcheck.
Added, thanks.
Thanks, we are also investigating yarn.
updated, thanks.

@GiedriusM, thanks for your feedback!  It seems most of the issues you raised have been addressed.  If you agree, would you mind closing this issue and possibly opening a new one to track the deprecated bower issue?


[Feature]: Add ssl disable for Rest API queries

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
I cant disable ssl verification in appsmith like postman and I think this is a important feature
Why should this be worked on?
I have self-signed ssl and wiht appsmith I cant send request to it, and appsmith doesn't have disable SSL like the postman

Duplicate of https://github.com/appsmithorg/appsmith/issues/16889


r11s: enable socket.io long-polling as a fallback

This change will allow long-polling as a fallback/downgrade option in the r11s-driver and r11s server. We should be able to release this driver change before the server change, because if WebSockets are not available in a client's browser/network, then their scenario is already broken.

Some observations:

Please take a look at https://github.com/microsoft/FluidFramework/issues/7964 and the article it references.
based on what I read about socket.io protocols, adding long polling will result in it being used first, for some indeterminate period of time. I.e., its less of a fallback (the way it's implemented), latency of communication might be affected negatively by this change for all connections that do support websocket upgrade.
So it would be great to actually do some measurements and see if this approach is good, or it's better to first try websocket protocol, and if it fails, retry with long-polling.
It would be also nice to understand what problem is being solved (i.e. particular user scenario). It's possible that we do not like long-polling perf and would want to use it to formulate better error message to users, i.e. isolate case where we can't reach relay service with any protocol, or can only with long polling (but not websocket), to point them to the root of the problem, but not support FF over long polling.

@vladsud

based on what I read about socket.io protocols, adding long polling will result in it being used first, for some indeterminate period of time. I.e., its less of a fallback (the way it's implemented), latency of communication might be affected negatively by this change for all connections that do support websocket upgrade.

This is correct when talking about the defaults used by socket.io (["polling", "websocket"]), however, order matters; by setting the value to ["websocket", "polling"], a WebSocket connection is attempted first, and polling is only used as a fallback. See socket.io's transports docs for more info.
const socket = io("https://example.com", {
  transports: ["websocket", "polling"] // use WebSocket first, if available
});

socket.on("connect_error", () => {
  // revert to classic upgrade
  socket.io.opts.transports = ["polling", "websocket"];
});

That being said, looking at the code example from socket.io, it appears that in order for the failover to actually work we might need to add an on("disconnect") handler to switch over to polling by default. I'm still working out how to actually validate this failover by reproducing the customer scenario that prompted this change.

So it would be great to actually do some measurements and see if this approach is good, or it's better to first try websocket protocol, and if it fails, retry with long-polling.

See above, the "better" option here is what this PR does.

It would be also nice to understand what problem is being solved (i.e. particular user scenario). It's possible that we do not like long-polling perf and would want to use it to formulate better error message to users, i.e. isolate case where we can't reach relay service with any protocol, or can only with long polling (but not websocket), to point them to the root of the problem, but not support FF over long polling.

We have some very specific customers who have this requirement. Please reach out offline, and I can connect you with the right people to give you more information about the specific need.

It would be great to share your learnings in #7964, including impact on service (I believe there is non-zero impact here RE COGS).
We want to learn as same change is likely needed on ODSP side.

I was able to mimic a WebSocket failure -> polling downgrade using a TamperMonkey script that closes a websocket connection before the handshake is able to complete. Using this test, I was able to confirm that some additional changes were needed to make the failover actually happen. Previously, driver-base/DocumentDeltaConnection would fail and terminate on any connect_error. However, we need to allow socket.io to re-attempt failover with polling once before terminating. Please take a look at the latest commit to see how I implemented that.
Scenarios I tested using Clicker and the result:

Script Blocks WebSockets
Server Allows WebSockets
Server Allows Polling
Result

No
Yes
Yes
Successful WebSocket handshake and connection, no polling attempt made, collaboration works as expected

Yes
Yes
Yes
WebSocket error: closed before connection established, polling begins, collaboration works as expected

Yes
Yes
No
WebSocket error: closed before connection established, polling attempt fails with 400 error, documentDeltaConnection fails with DeltaConnectionFailureToConnect {"delay":1000,"duration":1743,"online":1,"category":"error","error":"socket.io (connectError): xhr poll error: {\"type\":\"TransportError\",\"description\":400}"

Ideally, we would be able to know when the connect_error is due to a transport layer failure versus a socket.io server middleware error. I will continue to look into adding more specificity.
TL;DR this works, but I'm curious if there are other ideas on how to allow 1 reconnect attempt.

One way I heard people block websockets upgrade is by proxy inspecting traffic and dropping http headers (I can probably try to dig on where I heard about it).

@vladsud that's a great idea. I think I can probably find a way to configure nginx in front of local R11s to prevent websocket upgrade


Opera GX is a browser that has a very clean UI and some very useful time saving and battery saving features. It also has a nice ad and tracker blocker, like Brave does. I mostly use it when Brave refuses to work.

Disagree. Glary and CCleaner are both proprietary and untrustworthy. You can clean all of that with alternative software already in the tool.
Opera GX however may be a good idea, as it seems a lot of people use it, tho it is still kinda weird.

I absolutely hate Opera as a company and refuse to put any of their products in. Glary is fine, even though I don't use any of those tools.


feat: add typescript declaration file

close: #38

Could this please be pulled?  Might as well not wait on a re-write.

@DavidPx
If you need this declare file as soon as possible, you can create package @types/msw-storybook-addon!!
It is a chance of contributing to Definitely Typed :)

Thanks everyone for the discussion and thanks @tyankatsu0105 for the contribution!
I rewrote the project in Typescript in #61, so soon there will be proper types in the addon.
I'll be closing this PR if you don't mind!


Add post build hook

Add an example build hook to run unit tests as part of the build.
:thought_balloon: I tried doing so myself but couldn't get it working without friction, so deferring it for later or someone else.
The hook shall be added to the BuildConfigs of our templates:
+        "postCommit": {
+          "script": "perl -Iextlib/lib/perl5 t/*"
+        }

I am not sure about the right one-liner to run unit tests.

@ppisar FYI

The tool for executing perl tests is called prove. It can be found in -perl-Test-Harness package or  by installing Test::Harness module from CPAN. It automatically searches tests in t/.t, so the only think you need to do pass is a correct -I argument to point to the directory where your application installed the modules.
If you want to run tests of modules installed from CPAN, setting ENABLE_CPAN_TEST environment variable to true should be enough.
But I have no idea what BuildConfigs of our templates is.

@ppisar for the code in this repository, what are the steps to run the tests under t/, if you were developing this app?
Are the existing tests minimally reasonable? They seem to be coming from some scaffolding, not hand written.

I messed up and created this in the wrong repo.
Migrated to the appropriate place :arrow_right: https://github.com/openshift/dancer-ex/issues/29


Accessing files from private bucket

I'm a little unclear on the config necessary for using a private bucket.
CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.dummy.DummyCache',
    },
    'django-backblaze-b2': {
        'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
    }
}

BACKBLAZE_CONFIG = {
    'application_key_id': 'my_id',
    'application_key': 'my_key',
    'bucket': 'my_bucket',

}

Model Field:
class MyModel(models.Model):
    ...
    backblaze_file = models.FileField(
        upload_to='uploads',
        storage=PublicStorage,
    )

This setup allows me to save/upload the file, but then when accessing it via local URL (mydomain.com/b2/uploads/my_image_file.jpg) I simply get A server error occurred.  Please contact the administrator. in the browser along with TypeError: download_file_by_name() got an unexpected keyword argument 'download_dest' in the terminal.

I went to double check your settings and they look correct to me. I'm using a private bucket in production with no issues.
What version of the b2 sdk are you using? I'm in the process of updating the library for the latest python and SDK, but as of yet it's only tested up to 1.9

b2sdk=1.14.0
It looks like you have dependencies setup to install b2sdk >=1.9.0
https://github.com/ehossack/django-backblaze-b2/blob/556777a74a23780bffde68296c3173fb5a7d5ccd/pyproject.toml#L46
If it's not been tested about 1.9, then I assume it's a matter of changing that to b2sdk=1.9.0

This should be fixed in version 3.0
Dependabot has been enabled too so that any future breaking changes can be caught, and a minor version capping them released if necessary.


tabBarVisible property for BottomNavigationTab

💬 Question
This how i structure my navigation file, i want to hide TabBar visibility on ProductPages is there any way to do that. i have tried tabBarVisible which is mentioned here that's never helped me :( can anyone help me please?
  <Stack.Navigator screenOptions={{ headerShown: false, }} >
    <Stack.Screen name="Home">{(props) => <HomeScreen  {...props}/>}</Stack.Screen>
    <Stack.Screen name="Product">{(props) => <ProductPages  {...props} />}</Stack.Screen>
    <Stack.Screen name="Modal">{(props) => <ModalPages  {...props}/>}</Stack.Screen>
  </Stack.Navigator>
);

const ProductPages = () => (
  <Stack.Navigator>
    <Stack.Screen name="Single" options={{ headerShown: false }}>
         {(props) => <ProductScreen  {...props}/>}
    </Stack.Screen>
  </Stack.Navigator>
);

const BottomTabBar = ({ navigation, state }) => (
    <BottomNavigation
      selectedIndex={state.index}
      onSelect={index => navigation.navigate(state.routeNames[index])}>
      <BottomNavigationTab title='HOME'/>
      <BottomNavigationTab title='CATEGORY'/>
      <BottomNavigationTab title='ABOUT'/>
    </BottomNavigation>
);

const TabNavigator = () => (
    <Navigator tabBar={props => <BottomTabBar {...props} />}>
      <Screen name='Home' component={HomePages}/>
      <Screen name='Category' component={CategoryPages} />
      <Screen name='About' component={HomePages}/>
    </Navigator>
);

export const AppNavigator = () => (
  <NavigationContainer>
    <TabNavigator/>
  </NavigationContainer>
);

UI Kitten and Eva version

Package
Version

@eva-design/eva
^2.0.0

@ui-kitten/components
^5.0.0

Hi @joeljerushan. Thanks for your question.
It's a quite common behavior, so I decided to create a Gist for that, you may see it by the link below.
The BottomNavigation component doesn't react itself on the props passed though the navigation. However, you may use an option prop to control the params passed to a specific route and handle that in your custom TabBar.
See the example.

Hi @joeljerushan. Thanks for your question.
It's a quite common behavior, so I decided to create a Gist for that, you may see it by the link below.
The BottomNavigation component doesn't react itself on the props passed though the navigation. However, you may use an option prop to control the params passed to a specific route and handle that in your custom TabBar.
See the example.


More capability interfaces

Pull Request Test Coverage Report for Build 627

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 77.866%

Totals

Change from base Build 625:
0.0%

Covered Lines:
1402

Relevant Lines:
1727

💛  - Coveralls


Add a simple cache for objects stored in etcd

This is a prototype of a simple cache that stores objects stored in etcd. It uses ModifiedIndex as a key, assuming that each modification changes only one object.
It's pretty hard to benchmark effect of this change, but I have measurements and observations:

e2e performance tests (100 nodes, 3000 pods) runs ~25% faster (from ~20 min down to ~15 min)
CPU profiles shows that conversion code is now below 20% (usually around 10%) where it used to be up to 70% of CPU time
cache hit ratio is 100:1 (100 reads for 1 write) or more

@wojtek-t @davidopp @lavalamp @timothysc @smarterclayton

I like this a lot more than I was expecting to. :) But I fear adding a deep copy call in the cache is going to give back most of the performance gains. :(

My money is on it'll be 10% better.
I'd really like to wait on the local caching until we have the unified watcher from etcd.  Then we will be in a much better place to impose "fake etcdhelper".  Just my 2c
----- Original Message -----

I like this a lot more than I was expecting to. :) But I fear adding a deep
copy call in the cache is going to give back most of the performance gains.
:(

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/7288#issuecomment-96017947

I addressed all of the initial comments, tests pass so this PR is ready for normal review.

LGTM-- travis appears to have found a data race that you should probably figure out before we merge.

Won't there be a consistency issue here if we have multiple apiservers?
@rrati ^ FYI.

@timothysc If we have multiple apiservers, we do not need the same cache entries. We only require that etcd returns the same ModifiedIndex for the same objects (which will be the case).

Can you get numbers again with the second deep copy?
Also I really would perfer to use runtime.Object as the type of the cache...

DeepCopy in write path does not change anything, because of hit ration (1 write for ~100 reads)
Per request changed to runtime.Object.

e2e tests pass.

LGTM, no more comments.
----- Original Message -----

e2e tests pass.

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/7288#issuecomment-97414545

LGTM

What's the status now?  Looks like it got reverted.
@fgrzadkowski, @cjcullen

@timothysc - yes it was reverted, but the hopfully fixed version is send out for review - see #7559


Add schema.org / BioSchema annotation for each cohort call

Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond. The aim is to improve the web by creating a structured data markup schema supported by major search engines.
It is embedded in the HTML as JSON-LD to tag pages with metadata (title, authors, date, etc).
Bioschemas extended schema.org specification to also support annotation of training and course.
It would be great to add the schedule template the annotation of each cohort call using the Bioschemas Course Profile

Hello @bebatut I would like to give this a shot, can I?

@bebatut is this still open?

Yes it is still open. I assign this issue to you

@bebatut Thanks for assigning this issue to me.
Please can I get a lead on what I should do. So far, I know that schemas are used to make website pages indexable on search engines and in extension bioschemas narrows this objective to life sciences.

The best is to embed JSON-LD in the generated HTML, so in the Jekyll template used to create the schedule pages.
Here are some documentation that could be useful: https://bioschemas.org/tutorials/what_why_schema
To validate the schema.org you can use: https://validator.schema.org/

Thank you 😊

Hi @bebatut please I need clarity on the last statement here. Am I to make the schedule template an annotation of each cohort call with the Bioschemas course profile? Where can I find the schedule template, please?

Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond. The aim is to improve the web by creating a structured data markup schema supported by major search engines.
It is embedded in the HTML as JSON-LD to tag pages with metadata (title, authors, date, etc).
Bioschemas extended schema.org specification to also support annotation of training and course.
It would be great to add the schedule template the annotation of each cohort call using the Bioschemas Course Profile

The template for the detailed schedule is there: https://github.com/open-life-science/open-life-science.github.io/blob/main/_includes/detailed-schedule.md

Thanks so much, @bebatut you've been super helpful. I now fully understand what should be done but there's still a tad bit of constraint for me to navigate the code base. Is this https://github.com/open-life-science/open-life-science.github.io/blob/main/_includes/detailed-schedule.md same as the generated HTML where i am embedding the JSON-LD?

Hello @bebatut added the schema/bioschema annotation for each cohort and validated the schema markup with no errors after compilation. Made a pull request on "Hope" branch please do review when you have the time.

Linking PR #469


Configuration Issue: ESP32+stmpe610       ERROR: "pin detection"

Discussed in https://github.com/ImpulseAdventure/GUIslice/discussions/476

Originally posted by Bwanna September 26, 2022
Hi,
I have an ESP32 with an ST7789+ STMPE610 Touch and am getting the following error msg when compiling the "diag_ard_touch_detect" sketch:
D:\Arduinofiles\libraries\GUIslice-master\examples\arduino\diag_ard_touch_detect\diag_ard_touch_detect.ino:31:4: error: #error "Only DRV_TOUCH_ADA_SIMPLE supports pin detection"
   #error "Only DRV_TOUCH_ADA_SIMPLE supports pin detection"
    ^~~~~
D:\Arduinofiles\libraries\GUIslice-master\examples\arduino\diag_ard_touch_detect\diag_ard_touch_detect.ino:35:2: error: #error "Pin detection not supported on ARM or ESP platforms"
 #error "Pin detection not supported on ARM or ESP platforms"
  ^~~~~

exit status 1

Compilation error: #error "Only DRV_TOUCH_ADA_SIMPLE supports pin detection"

Both the ST7789 (SPI) and the STMPE610 (I2C) are working using Adafruit sketches/drivers. However, this error is appearing here.
In "GUISLICE_CONFIG.h"  the following:
#include "../configs/esp-tftespi-default-stmpe610.h"
In esp-tftespi-default-stmpe610.h" the following:
#define ADATOUCH_I2C_HW 1  // Touch controller via hardware I2C (uses ADATOUCH_I2C_ADDR)
#define ADATOUCH_SPI_HW 0  // Touch controller via hardware SPI (uses ADATOUCH_PIN_CS)
#define ADATOUCH_SPI_SW 0  // Touch controller via software SPI [not yet supported]
Any assistance would be greatly appreciated.
Can someone explain where the 'pin detection' is configured?  which file?  Have searched and unable to locate.
Thanks!

@Bwanna Sorry but there is nothing to help with.  This is an unimplemented feature for your  touch driver as the error clearly states.   You must already know your pins for touch or the Adafruit sketches would not work for you.  You simply need Calibration of your touch driver.  The x and y min and maxes that should be entered into your version of /esp-tftespi-default-stmpe610.h.  For that simply run the diag_ard_touch_calib.ino sketch and place the numbers it gives you into the config file.   I generally use the serial monitor an just cut and paste from that.
Paul--

@Bwanna Sorry but there is nothing to help with.  This is an unimplemented feature for your  touch driver as the error clearly states.   You must already know your pins for touch or the Adafruit sketches would not work for you.  You simply need Calibration of your touch driver.  The x and y min and maxes that should be entered into your version of /esp-tftespi-default-stmpe610.h.  For that simply run the diag_ard_touch_calib.ino sketch and place the numbers it gives you into the config file.   I generally use the serial monitor an just cut and paste from that.
Paul--

First  thanks for the feedback, but there is possibly a misunderstanding here ...
This is a question about 'which' file would the "Pin Detection" be configured?.
I'm unable to locate this in any of the GUISlice files.
Thank you.

@Bwanna Yes, I can see there is a misunderstanding.   So I'll try again.  There is no PIN Detection.
The pin detection feature is only needed to debug  and report the set of pins currently wired to a 4-wire resistive touch display. It exists only inside the test program diag_ard_touch_detect.ino and nowhere else.
These 4-wire displays unlike the  touch driver for STMPE610 generally comes with almost no documentation so this program is needed for them.
Since you have stated above that your Adafruit_STMPE610 test program works I assume its TouchTest.ino and you have correctly defined your touch interface at the top of this routine so you can simply edit your  "../configs/esp-tftespi-default-stmpe610.h" file with the correct information.
Now how to config GUIslice detailed in the wiki:
Configure Touch Support
And for your specific touch driver in:
Configuring Touch for STMPE610
As an example inside my configs/esp-tftespi-default-stmpe610.h in   SECTION 4A: Update your pin connections here
I edit the file and set:
  // TFT_eSPI: Chip Select for Touch Device
  // - Since we are not using the TFT_eSPI's integrated XPT2046 touch driver,
  //   it is best to disable it. This can be done by ensuring that the TOUCH_CS line
  //   in TFT_eSPI's User_Setup.h is commented out.

  // Select touch device wiring method by setting one of the following to 1, others to 0
  #define ADATOUCH_I2C_HW 0  // Touch controller via hardware I2C (uses ADATOUCH_I2C_ADDR)
  #define ADATOUCH_SPI_HW 1  // Touch controller via hardware SPI (uses ADATOUCH_PIN_CS)
  #define ADATOUCH_SPI_SW 0  // Touch controller via software SPI [not yet supported]

  // Touch bus & pinout
  #define ADATOUCH_I2C_ADDR   0x41  // Touch device I2C address (for ADATOUCH_I2C_HW=1)
#ifdef ESP8266
  #define ADATOUCH_PIN_CS     D0    // Touch device chip select (for ADATOUCH_SPI_HW=1)
#elif ESP32
  #define ADATOUCH_PIN_CS     32    // Touch device chip select (for ADATOUCH_SPI_HW=1)
//  #define ADATOUCH_PIN_CS     13    // Touch device chip select (for ADATOUCH_SPI_HW=1)
#endif

I hope this clears things up for you.
Paul--

Very much appreciate the reply!  I've been researching the Wiki and testing this for days with no luck.
The Adafruit_STMPE610 test program (TouchTest.ino)  only  requires a simple call, so nothing obvious to incorporate into the "../configs/esp-tftespi-default-stmpe610.h" file:  (unless I'm missing something?)
// Option #1 - uses I2C, connect to hardware I2C port only!
// SCL to I2C clock (#A5 on Uno) and SDA to I2C data (#A4 on Uno)
// tie MODE to GND and POWER CYCLE (there is no reset pin)
Adafruit_STMPE610 touch = Adafruit_STMPE610();

Here is what I have in "configs/esp-tftespi-default-stmpe610.h" in SECTION 4A:
What information should I transfer from the TouchTest.ino to this file?

  // TFT_eSPI: Chip Select for Touch Device
  // - Since we are not using the TFT_eSPI's integrated XPT2046 touch driver,
  //   it is best to disable it. This can be done by ensuring that the TOUCH_CS line
  //   in TFT_eSPI's User_Setup.h is commented out.

  // Select touch device wiring method by setting one of the following to 1, others to 0
  #define ADATOUCH_I2C_HW 1  // Touch controller via hardware I2C (uses ADATOUCH_I2C_ADDR)
  #define ADATOUCH_SPI_HW 0  // Touch controller via hardware SPI (uses ADATOUCH_PIN_CS)
  #define ADATOUCH_SPI_SW 0  // Touch controller via software SPI [not yet supported]

  // Touch bus & pinout
  #define ADATOUCH_I2C_ADDR   0x41  // Touch device I2C address (for ADATOUCH_I2C_HW=1)
#ifdef ESP8266
  #define ADATOUCH_PIN_CS     D0    // Touch device chip select (for ADATOUCH_SPI_HW=1)
#elif ESP32
  #define ADATOUCH_PIN_CS     13    // Touch device chip select (for ADATOUCH_SPI_HW=1)
#endif

Again, REALLY appreciate the assistance!!!  Been at this for many days and still unsuccessful.  :(
I'm really at a loss what to try next to get past this "pin detection" error.  It's preventing me from uploading the sketch.
Thank you!
Steve

@Bwanna First please ignore the diag_ard_touch_detect.ino program it doesn't apply to your touch driver.
Use ex02_ard_btn_txt.ino as your test platform.  Note to circle back to diag_ard_touch_calib.ino to get an accurate set of X And Y min maxes for SECTION 4B  once you get ex02 to compile and run.
As for your "configs/esp-tftespi-default-stmpe610.h" in SECTION 4A the TouchTest if unmodified sets:
  // If using I2C you can select the I2C address (there are two options) by calling
  // touch.begin(0x41), the default, or touch.begin(0x44) if A0 is tied to 3.3V
  // If no address is passed, 0x41 is used
  if (! touch.begin()) {

So your defaults inside "configs/esp-tftespi-default-stmpe610.h" should be set to:
  // Select touch device wiring method by setting one of the following to 1, others to 0
  #define ADATOUCH_I2C_HW 1  // Touch controller via hardware I2C (uses ADATOUCH_I2C_ADDR)
  #define ADATOUCH_SPI_HW 0  // Touch controller via hardware SPI (uses ADATOUCH_PIN_CS)
  #define ADATOUCH_SPI_SW 0  // Touch controller via software SPI [not yet supported]

  // Touch bus & pinout
  #define ADATOUCH_I2C_ADDR   0x41  // Touch device I2C address (for ADATOUCH_I2C_HW=1)```

and believe it or not you are done.
Paul--

@Pconti31  Perfect!  Thank you VERY much for the clarifications!
Touchscreen is working with the other files.  Ran Calibration and inserted the numbers into the config file.  I'll stay away from the "Detect" sketch.   (I probably didn't need to get hung up on that sketch as much as I did. )
Cheers!
Steve


OOM using RTX4090 24g

I completed fitting using video.mp4 from gyeongsik. Then, I used the result to run the training with python train.py --subject_id $SUBJECT_ID, but encountered an OOM (Out of Memory) issue. Is there any way to reduce the memory usage during training?
I found that the batch size for training is already set to 1. I tried using the mixed precision training provided by torch, but encountered the following error. I'm not sure if this excellent project supports mixed precision training.

hi, which gpu are you using? what is your vram limitation?

I remember ExAvatar usually takes 11~12 GB for the training.

Hi, I've just checked 'gyeongsik' sequence takes 17~20 GB VRAM, which fits to your VRAM limitation. Could you check whether there are some other jobs you're running with taking some VRAM? Also, If you can decrease the image resolution (and corresponding masks/camera intrinsics/keypoints) to save VRAM usage. Or cropping human regions?

Sorry for my delayed response. I compared the gyeongsik data I processed using fitting with the gyeongsik data you provided. The difference is that I kept all 720 frames. Later, I reprocessed the gyeongsik data, keeping only 400 frames, and the memory usage decreased.  Why does the number of frames retained affect memory usage, even though the training input batch is one? Sorry if the questions are dumb I'm new to this field.

I guess that is because of this one: https://github.com/mks0601/ExAvatar_RELEASE/blob/69e12bb1bee4d0401b304c3ab245a6c8658a8bc2/avatar/main/model.py#L17
It have smplx parameters of all frame, and they are optimizable, so they are on gpu

Got it！


Error RZ9991 since VS 17.6 upgrade

Hello,
I'm facing an issue with Blazor component inheritence since my upgrade to VS 2012 17.6 / .NET 7.0.302.
To reproduce, create a base component InputBase.razor :
<input @bind="@Value" @bind:event="oninput"/>
@code {
    private string _value;

    [Parameter]
    public string Value
    {
        get => _value;
        set
        {
            if(_value == value) return;
            _value = value;
            ValueChanged.InvokeAsync(value);
        }
    }

    [Parameter]
    public EventCallback<string> ValueChanged { get; set; }
}

Create a second component MyInput that inherit from InputBase :
@inherits InputBase;

@code {

}

When I use MyInput like this
<MyInput @bind-Value="@Data"></MyInput>

@code
{
    public string Data { get; set; }
}

I have a build error code RZ9991.
The build works fine if I use .NET version 7.0.203
Is there a breaking change I have missed ?

Please see the issue here. It'll be a duplicate of this:
https://github.com/dotnet/razor/issues/8718

Closing as a dupe of #8718


warn: mqtt-client.0 (2266) adapter.objects.getObjectView is deprecated

2021-02-12 16:03:13.047 - warn: mqtt-client.0 (2266) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
Probably allready in work?

Already fixed, just needs a new version, maybe you can publish one @Apollon77

nope, only @GermanBluefox


Admin UI changes

Closes #416
Pending things:

[x] Placeholder images
[ ] Placeholder text
[x] Preview in new window

@gullible1 Other than the placeholder texts, this PR is good to be merged. Can you help me with that?


Extract formulas

See #124

How do you expect users to update Formulas? e.g. a CLI command fontist update?

Currently the formulas repo is pulled on each load of the library. Do you see any downsides of this implementation?

Decided to build the update command in a new PR


dedupe the internal/wait package

The internal/wait package is a superset of deployer/pkg/deployer/wait package. We need to dedupe them, possibly extending the latter with all the features needed by the former, or making it extensible or anything.

this is a good first issue but not among the simplest. It's probably a very nontrivial task for a newcomer

I would like to give this a try if that is ok with you @ffromani

go for it


swift_build_support: unify CMake toolchain code

Currently, a lot of products defined in utils/swift_build_support contain duplicated code that checks for Darwin/Linux triples and generates an appropriate CMake toolchain file. Since all of these products inherit from the Product class, it makes sense to reduce this code duplication by refactoring it into a single function.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please test Windows

@swift-ci please test Windows


miss function

The function 'compute_rollout_attention' in trans_fer.py is not defined. It is referenced in the function VisionTransformer.relprop().
"/APViT/Paddle/ppcls/arch/backbone/model_zoo/trans_fer.py"

This function is used for visualization. We do not tend to maintain the visualization codes. You may refer to their official repo (already replied in #3 ) to modify the visualization part.


Specifying motion_prior_smooth_weights

Hi! Thanks for the great work.
When running "fitting on PROX stage 2" the code stops at the following assertion check:
https://github.com/sanweiliti/LEMO/blob/main/temp_prox/fit_temp_loadprox_slide.py#L227
body_pose_prior_weights has length of 5 whereas motion_prior_smooth_weights has length of 1, which is normal because config file specifies just one value: https://github.com/sanweiliti/LEMO/blob/main/cfg_files/PROXD_temp_S2.yaml#L33 and no extra pre-processing is applied on motion_prior_smooth_weights in the main_slide.py.
Seems like this assertion error will just always happens. Is this expected?
As a quick workaround, should I just make motion_prior_smooth_weights [1e8, 1e8, 1e8, 1e8, 1e8,] or [0, 0, 0, 0, 1e8]?

I found the reason. Closing this issue.

I found the reason. Closing this issue.


Keynames for < and > sign in aerospace config

HI! Thank you so much for this repo, since I can finally use quick workspace switch like in i3 which I couldn't do with default slow transitions <3 I love the app so far
I have a question if I may ask. I've tried to find a solution for that but couldn't make it work
In my i3config I had a binding Meta + Shift + > or Meta + Shift + < to move workspace to either left or right monitor
https://github.com/Kamyil/.dotfiles/blob/9422d244a7e01ed68902b5244ffb8a44003a8acb/i3/config#L187
I've tried to replicate that shortcut in aerospace.toml file, but I couldn't find the keyname of < & >  keys that aerospace would parse. I've tried looking here
https://github.com/nikitabobko/AeroSpace/blob/main/src/config/keysMap.swift
and in referenced skhd source file, but couldn't find them there to
I've also tried blindly guessing the keyname with those keynames less//greater,  lessThan/greaterThan, leftChevron/rightChevron and didn't work
So in tl;dr: I would like to make these work
cmd-shift-lessThan = 'move-workspace-to-monitor --wrap-around prev'
cmd-shift-greaterThan = 'move-workspace-to-monitor --wrap-around next'

Extra info
aerospace CLI client version: 0.8.4-Beta 4951cbc3167737235c4dcf9c7521bd9a6418c699
AeroSpace.app server version: 0.8.4-Beta 4951cbc3167737235c4dcf9c7521bd9a6418c699

macOS Sonoma 14.2.1

My config so far:
# Reference: https://github.com/i3/i3/blob/next/etc/config

enable-normalization-flatten-containers = false
enable-normalization-opposite-orientation-for-nested-containers = false

[mode.main.binding]
# alt-shift-t = 'exec-and-forget open -n /System/Applications/Alacritty.app'

alt-j = 'focus left'
alt-k = 'focus down'
alt-l = 'focus up'
alt-semicolon = 'focus right'

alt-h = 'split horizontal'
alt-v = 'split vertical'

# alt-f = 'fullscreen'
# alt-s = 'layout v_accordion' # 'layout stacking' in i3
# alt-w = 'layout h_accordion' # 'layout tabbed' in i3
# alt-e = 'layout tiles horizontal vertical' # 'layout toggle split' in i3

# Not supported, because this command is redundant in AeroSpace mental model.
# See: https://nikitabobko.github.io/AeroSpace/guide.html#floating-windows
# alt-space = 'focus toggle_tiling_floating'

# `focus parent`/`focus child` are not yet supported, and it's not clear whether they
# should be supported at all https://github.com/nikitabobko/AeroSpace/issues/5
# alt-a = 'focus parent'

cmd-1 = 'workspace 1'
cmd-2 = 'workspace 2'
cmd-3 = 'workspace 3'
cmd-4 = 'workspace 4'
cmd-5 = 'workspace 5'
cmd-6 = 'workspace 6'
cmd-7 = 'workspace 7'
cmd-8 = 'workspace 8'
cmd-9 = 'workspace 9'
cmd-0 = 'workspace 10'

cmd-shift-1 = 'move-node-to-workspace 1'
cmd-shift-2 = 'move-node-to-workspace 2'
cmd-shift-3 = 'move-node-to-workspace 3'
cmd-shift-4 = 'move-node-to-workspace 4'
cmd-shift-5 = 'move-node-to-workspace 5'
cmd-shift-6 = 'move-node-to-workspace 6'
cmd-shift-7 = 'move-node-to-workspace 7'
cmd-shift-8 = 'move-node-to-workspace 8'
cmd-shift-9 = 'move-node-to-workspace 9'
cmd-shift-0 = 'move-node-to-workspace 10'

cmd-shift-less = 'move-workspace-to-monitor --wrap-around prev'
cmd-shift-= 'move-workspace-to-monitor --wrap-around next'

alt-shift-c = 'reload-config'
alt-shift-f= 'layout floating tiling' # 'floating toggle' in i3
alt-shift-r = 'mode resize'
alt-shift-h = 'move left'
alt-shift-j = 'move down'
alt-shift-k = 'move up'
alt-shift-l= 'move right'

[mode.resize.binding]
h = 'resize width -50'
j = 'resize height +50'
k = 'resize height -50'
l = 'resize width +50'
enter = 'mode main'
esc = 'mode main'

I hope you use qwerty

cmd-shift-lessThan = 'move-workspace-to-monitor --wrap-around prev'

cmd-shift-comma = 'move-workspace-to-monitor --wrap-around prev'

cmd-shift-greaterThan = 'move-workspace-to-monitor --wrap-around next'

cmd-shift-period = 'move-workspace-to-monitor --wrap-around next'

Thanks, it works!


Internet Explorer interface: Submit button is compressed

In IE10 this is not an issue. Not sure how to debug this...

The hospitals may run on Internet Explorer 11 and not 10. I can check this again the next time I'm in the hospital.


Using Builders without class after 2.0

Q
A

Version
2.0.2 after migrating from 1.3

Support Question
Query and Aggregation builders in version before 2.0 were able to work with queries against collections that did not have their own class.
I used to be able to instantiate them and then pass a string indicating what collection I wanted to ask. Then if the string I passed was not a valid class name, a direct collection name was assumed.
Was this feature never intended to work? Was it dropped intentionally, or rather it was a case of a feature that was cut off unintentionally?
From what I've seen in the code, both Builders immediately ask for ClassMetadata instance, which is the reason why passing collection name no longer works. I've managed to get around the issue by injecting a listener for onClassMetadataNotFound event, creating a fake class for it to work with and adjusting collection name in Event instance accordingly. However I feel it's a rather hacky solution.
My use-case is a "legacy" application that partitions data between multiple collections based another object's property.
Depending on whether it was intentional or not, I would like to propose:

Expand upgrade document to add information that it is no longer possible to query collections directly.
If this solution has no side-effects that I didn't notice, then maybe add it to the docs as a workaround.
Allow getClassMetadata to fail silently in both builders and/or allow them to work without ClassMetadata instance in those cases.

WDYT?

I think it was unintentional feature drop however I had no clue such thing was possible with 1.x :D

But I believe such thing was possible due to all builders in 1.x being inherited from doctrine/mongodb which was dealing with plain collections. FWIW I think it would be nice to preserve this functionality if that's not too much hassle on our side.

But I believe such thing was possible due to all builders in 1.x being inherited from doctrine/mongodb which was dealing with plain collections.

Yes, that's the case actually. Since in 2.0 they no longer extend from those base classes, hence no ability of building those queries with support of ODM (without anythying that relied on metadata, of course).
Using onClassMetadataNotFound seems to have no obvious side-effects - MetadataFactory caches entries using original requested class name, so asking for another collection afterwards seem to work.

I'll have to take a look. That definitely wasn't an intended BC break, and if we can easily bring that back, I'd be happy to do so.
@Steveb-p do you want to cook up some test cases or even give the implementation a shot?

do you want to cook up some test cases or even give the implementation a shot?

Yes, I'll try to work it out this week.

Bad bot!

@malarzm putting the issue into a project (e.g. the Roadmap) keeps the bot away :)

I like the stale bot though. It exists as a constant reminder of my failure to deliver promises and things I forgot about :smiley_cat:

@Steveb-p I'm glad you like it - I always appreciate it reminding me about issues and PRs that I forgot to follow up on :)=


feat(asus/zephyrus): add GU603H (2021 Zephyrus M16)

Description of changes
Adds configs for the Asus ROG Zephyrus M16, model GU603H. My specific model is listed as a GU603HM, but I think other laptops in the same series would work too.
Things done

[x] Tested the changes in your own NixOS Configuration
[x] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

@mergify queue


Fixed some bugs about csi replication.

What this PR does / why we need it:

Update default access protocol into db
Remove replication probe step.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:
Release note:

Coverage increased (+0.008%) to 43.254% when pulling ae09407e73e87ba18fb6bcd0e81aadd251d836bc on xxwjj:csi_replication into 645b2c1af88c1279e07a5603b3e250b879a2af38 on opensds:development.


mup deploy hangs without error

mup deploy stays forever at console output Building Started: <appPath>. When I try to check the logs with mup logs -f it says `cannot open '/var/log/upstart/.log' for reading: No such file or directory.
I can deploy the app to meteor.com. I can deploy other apps on my server: mup setup and mup deploy run fine and the log file can be found in /var/log/upstart/<appName>.log.
How can I proceed in this situation?

That means your app is not building locally. Try building your app with
meteor build <dirnam>
On Fri Feb 20 2015 at 3:04:04 PM miri-am<EMAIL_ADDRESS>wrote:

mup deploy stays forever at console output Building Started: .
When I try to check the logs with mup logs -f it says `cannot open
'/var/log/upstart/.log' for reading: No such file or directory.
I can deploy the app to meteor.com. I can deploy other apps on my server:
mup setup and mup deploy run fine and the log file can be found in
/var/log/upstart/.log.
How can I proceed in this situation?
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/272.

It builds successfully. meteor build <dirname> gives me a folder with /android, /ios, and <appname>.tar.gz. Sorry, forgot to mention this.

@arunoda any hints how I could debug this situation?

it is working now. I am not sure what caused this: removed platforms and added them again, deleted smart files... cannot say. Closing this.

If you changed any settings in mup.json, you need to call mup setup to re initialize configuration.


Provide an Arbitrary[Uri] instance

As per gitter discussion:

@rossabaker Nov 30 16:42
There are some arbitraries in TestInstances, but it's not published. There is no URI, but I needed one this week.
@Unisay Nov 30 16:43
I can contribute it if you want :grinning:
@rossabaker Nov 30 16:43
I would love that!

Closed by cherry-pick-and-merge of #780.


Joined to the friends list

Joined to the friends list..

Your pull request needs further work because of the following reason(s):

Your filename must be Odatha.html

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

f5c443ef1730c0b5d983ffb0b726985739c9b221

rename the html file

Your pull request needs further work because of the following reason(s):

More than one file has been added/removed/modified.

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

517a0ef143d98464c5ce7006cf9c56177cbc2d26

Remove "Friends/Odprofile.html" and i will merge

This PR has been idle for more than 24 hours, and will now be closed. Feel free to re-open.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

705517e66b85aa1fb80c936439336758b170dc94


Tidy supplier results view

Ticket
I'll probably squash most of these together before merging into master, but I wanted to show my working and make it easier for my reviewer to make sense of this.
This PR is to change the ccs-sourcing-admin's journey. It brings it into line with the other admin roles while adding a small tweak that prevents them from seeing links they can't access.
Previous search results:

New search results:

New detail page:

My functional tests passed locally  However given Jenkins is currently unhappy, I'd hold off merging for the moment as the preview tests are likely to fail (also the commits will need squashing).

Fair. I'll do the squashing now in any case


Rewrite entrypoint to use jq

Suggested change from @kusalananda on SciLifeLab Slack 🙏🏻

Tested and working as much as it was before I think. However we're having issues with 403 Forbidden errors across nf-core currently and I want to test this change after that was resolved before merging..

Merging as this is no less broken than the current implementation and I want to rewrite the whole thing anyway.


[Documentation]: How can I extract picture for towhee by io

Is there an existing issue for this?

[X] I have searched the existing issues

What kind of documentation would you like added or changed?
I am using towhee to extract picture, but according to demo, it just can extract by url， as below code:
class ResNet50:
def init(self):
self.pipe = (towhee.dummy_input()
.image_decode()
.image_embedding.timm(model_name='resnet50')
.tensor_normalize()
.as_function()
)
#图片路径即url解压为向量
# @staticmethod
def resnet50_extract_feat(self, img_path):
feat = self.pipe(img_path)
if isinstance(feat, _Reason):
raise feat.exception
return feat
if name=='main':
c = ResNet50()
vector = c. resnet50_extract_feat(https://XXXXXXXXXXX)
how can I extract by io, maybe like code as below:
if name=='main':
with open(r'd:\abc\123.jpg','rb')as file:
pic_io = file
c = ResNet50()
vector = c. resnet50_extract_feat(pic_io)
Why is this needed?
when client upload a picture, server receive a picture which is io. I prefer extract picture for io rather than  save picture first and extract a picture path
Anything else?
No response

by bytes both ok

Try this
import cv2
import numpy as np

import towhee
from towhee.types import Image

def decode(content):
    arr = np.asarray(bytearray(content), dtype=np.uint8)
    return Image(cv2.imdecode(arr, -1), 'BGR')

pipe = (towhee.dummy_input()
        .runas_op(decode)
        .image_embedding.timm(model_name='resnet50')
        .tensor_normalize()
        .as_function()
)

with open('image_path', 'rb') as f:
    content = f.read()
    print(pipe(content))

@sulmz
is it ok now?

Try this
import cv2
import numpy as np

import towhee
from towhee.types import Image

def decode(content):
    arr = np.asarray(bytearray(content), dtype=np.uint8)
    return Image(cv2.imdecode(arr, -1), 'BGR')

pipe = (towhee.dummy_input()
        .runas_op(decode)
        .image_embedding.timm(model_name='resnet50')
        .tensor_normalize()
        .as_function()
)

with open('image_path', 'rb') as f:
    content = f.read()
    print(pipe(content))

thank you very much! it is work

@sulmz is it ok now?

yes


Rename APIGroup

This PR renames APIGroup from admission.apps.openshift.io to admission.runoncedurationoverride.openshift.io.
This PR is blocked by https://github.com/openshift/run-once-duration-override/pull/11

Blocker PR is merged. however probably retest will fail again due to new image has not been published yet.
/retest-required

/retest

/lgtm

/lgtm

@ingvagabund I think we need to wait new image of run-once-duration-override. Do you know when possibly we can retest this? or is there any place I can watch the new image?

The image promotion/mirroring takes some time. Not sure how often that job is run thought. Let's wait. We still have time.
@kasturinarra FYI this will block the testing until the PR merges. We merged a breaking change in the operand. Until the operator applies the same change as well, the operand will not work properly.

Maybe we can retest one more time;
/retest-required


Tasks with gyp built dependencies

I'm currently trying to write my own VSTS extension with its custom task. This task depends on sharp that has to be build at npm install time through gyp. But the node_modules seem to have to be included into the .vsix before upload of the extension so I didn't find any solution for this (maybe pre-compiling the module for all agent architectures and requiring the module thanks to the current agent executing architecture) ...

please open on the vsts-task-lib repo and we'll discuss their (this covers tasks in this repo)


Stats page

TypeError: moment.duration(...).format is not a function
Hmm``

Not sure why this isn't working as it should. It used to work. I have added something that I think should fix the issue. Unfortunately, I cannot test the fix right now as my new laptop isn't set up for this yet and might not be set up for this until the end of June due to school work and exams.


Add diff intellj support in test errors

:pushpin: References

Issue: fixes #49
Pull Requests #47

:tophat: What is the goal?

Support to diff snapshot files using Intellj idea view assertEquals difference to improve the readability of the diff files.

:memo: How is it being implemented?

Extends SnapshotException with ComparisonFailure JUnit exception which shows the typical JUnit message with expected but was actual.
Must follow this message structure: expected:<will not match[ ;)]> but was:<will not match[]>

💥 How can it be tested?

Test which throws SnapshotException if a test fails
Test which matches the expected message when a SnapshotException has been thrown.

👓 Example
When a test fails

Diff

@tonilopezmr 🔝 contribution to this repository. Thank you so much 😃


gui demo for the API

Hey,
I'm working on a gui demo for illustrating how the API works, if someone wants to discuss it we can do so here!
I intend to put it in a folder "API demo"
I intend to provide some godot gui to :
buttons to illustrates function in the API:
cost_map #labels on top of the case
direction map : little arrows
connect disconnect points
connect all neighbour points
disconnect all
show point under cost
adding/show source/ target
automatic recalculate djisktramap
recalculate for target(s) with cost
Share your thoughts !

I had something similar in my testing rig. I've posted images in the reddit thread, but they don't appear to work. I've managed to dig up one of them: https://imgur.com/a/AqLzoJf
Unfortunately, I'm not very familiar with Godot yet, so I just kinda hacked it in somehow with spaghetti code. I've added setter method for a dummy boolean exported variable, and the setter method recalculated the dijkstra map. I'm sure there are better ways to do it.

I've done something, the pull request is coming when I understand git ;)

git is hard XD
I'm trying !


ValueError: mutable default <class 'flet.alignment.Alignment'> for field begin is not allowed: use default_factory

Context:

Ubuntu 21.10
flet 0.1.48
Python 3.11.0b4

I was trying to follow the introduction and I received this traceback:
>> python3 app.py
Traceback (most recent call last):
  File "/home/nsukami/GIT/flet_example/app.py", line 1, in <module>
    import flet
  File "/home/nsukami/vrtlnvs/flet/lib/python3.11/site-packages/flet/__init__.py", line 11, in <module>
    from flet.container import Container
  File "/home/nsukami/vrtlnvs/flet/lib/python3.11/site-packages/flet/container.py", line 9, in <module>
    from flet.gradients import Gradient
  File "/home/nsukami/vrtlnvs/flet/lib/python3.11/site-packages/flet/gradients.py", line 25, in <module>
    @dataclasses.dataclass
     ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dataclasses.py", line 1221, in dataclass
    return wrap(cls)
           ^^^^^^^^^
  File "/usr/local/lib/python3.11/dataclasses.py", line 1211, in wrap
    return _process_class(cls, init, repr, eq, order, unsafe_hash,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dataclasses.py", line 959, in _process_class
    cls_fields.append(_get_field(cls, name, type, kw_only))
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dataclasses.py", line 816, in _get_field
    raise ValueError(f'mutable default {type(f.default)} for field '
ValueError: mutable default <class 'flet.alignment.Alignment'> for field begin is not allowed: use default_factory
(flet) ~/GIT/flet_example

Is there something I'm doing correctly ?
The only Python class with an attribute named begin is here. If there is really a bug somewhere, is there anything I can do to help you fix this ?
o/

Thanks for reporting that!
Could you please try replacing begin: Alignment = field(default=alignment.center_left) with begin: Alignment = field(default_factory=alignment.center_left) in "/home/nsukami/vrtlnvs/flet/lib/python3.11/site-packages/flet/gradients.py", line 27 to see if that fixes that error?

This explains an issue more:
https://stackoverflow.com/a/52064202
https://stackoverflow.com/a/53633297
I'm not sure why it's not reproducible with Python 3.10, but definitely it looks like a bug.

Could you please try replacing [...] to see if that fixes that error?

I've made the following modifications inside /home/nsukami/vrtlnvs/flet/lib/python3.11/site-packages/flet/gradients.py and the error was fixed:
@dataclasses.dataclass
class LinearGradient(Gradient):
    # begin: Alignment = field(default=alignment.center_left)
    begin: Alignment = field(default_factory=alignment.center_left)
    # end: Alignment = field(default=alignment.center_right)
    end: Alignment = field(default_factory=alignment.center_right)
    type: str = field(default="linear")

@dataclasses.dataclass
class RadialGradient(Gradient):
    # center: Alignment = field(default=alignment.center)
    center: Alignment = field(default_factory=alignment.center)
    radius: Union[float, int] = field(default=0.5)
    focal: Alignment = field(default=None)
    focal_radius: Union[float, int] = field(default=0.0)
    type: str = field(default="radial")

@dataclasses.dataclass
class SweepGradient(Gradient):
    # center: Alignment = field(default=alignment.center)
    center: Alignment = field(default_factory=alignment.center)
    start_angle: Union[float, int] = field(default=0.0)
    end_angle: Union[float, int] = field(default=math.pi * 2)
    type: str = field(default="sweep")

So, it's been fixed in https://pypi.org/project/flet/0.1.49/ - please update flet module and give it another try.


Chalenges marked as complete but do NOT show solutions

Challenge Name
https://www.freecodecamp.com/challenges/comparison-with-the-less-than-or-equal-to-operator
Issue Description
Chalenges show green check mark, but do not show my solutions this has been a problem since the very 1st challenge to the challenge above
Browser Information
FireFox ,  Chrome  (PC, Dell, Windows 10 , Latest browser version )

Directly browsing from map will not show your solutions. To check your solutions, you have to open and view your profile where all your completed challenges are listed and you will have an option to view your solution too. To view your profile, just click on your profile picture thumbnail at top right corner.

@jlorenzo123 what @Jaskaranbir says is correct. Go to your Free Code Camp page at https://www.freecodecamp.com/username, where username is your username for Free Code Camp. There, you'll be able to see your solutions.Let us know if that helps.

Curious as to the reasoning behind this. Sometimes when I click on challenge in the map I've completed recently I see the solution code but other times I don't. It always works when I go to my profile, but I was wondering why it's only there sometimes in the map. Something to do with a cache?

Closing as stale.

https://www.freecodecamp.com/username does not opens , can anyone help me get it my freecodecamp username


Code Coverage for qemu_x86 is not getting generated due to a build error

Describe the bug
While running the below command for code coverage the tests on qemu_x86 are failing due to a build error. Tests are passing while running sanity check with out the code coverage option.
~/zephyr/scripts/sanitycheck --coverage --coverage-platform qemu_x86 -p qemu_x86 --coverage-platform qemu_x86_nommu -p qemu_x86_nommu --gcov-tool /opt/zephyr-sdk/i586-zephyr-elf/bin/i586-zephyr-elf-gcov -T ~/zephyr/tests/kernel -T ~/zephyr/tests/subsys/logging | tee output.log
What have you tried to diagnose or workaround this issue?
Build error is observed after the below commit.
Commit ID: fb0faaa1239ad5f6577d3268c67ba168aab57656
To Reproduce
Steps to reproduce the behavior:
Run the above command and tests fail due to a build error.
Expected behavior
Tests should pass.
Impact
Blocking the code coverage.
Screenshots or console output
[ 83%] Building C object zephyr/CMakeFiles/zephyr_prebuilt.dir/misc/empty_file.c.obj
[ 84%] Linking C executable zephyr_prebuilt.elf
/opt/zephyr-sdk/i586-zephyr-elf/bin/../lib/gcc/i586-zephyr-elf/8.3.0/../../../../i586-zephyr-elf/bin/ld:linker.cmd:161: undefined symbol `_region_min_align' referenced in expression
collect2: error: ld returned 1 exit status
make[3]: *** [zephyr/CMakeFiles/zephyr_prebuilt.dir/build.make:95: zephyr/zephyr_prebuilt.elf] Error 1
make[3]: Target 'zephyr/CMakeFiles/zephyr_prebuilt.dir/build' not remade because of errors.
make[3]: Leaving directory '/home/syerabol/zephyr/sanity-out/qemu_x86/tests/subsys/logging/log_output/logging.log_output'
make[2]: *** [CMakeFiles/Makefile2:480: zephyr/CMakeFiles/zephyr_prebuilt.dir/all] Error 2
make[2]: Target 'all' not remade because of errors.
make[2]: Leaving directory '/home/syerabol/zephyr/sanity-out/qemu_x86/tests/subsys/logging/log_output/logging.log_output'
make[1]: *** [Makefile:84: all] Error 2
make[1]: Target 'default_target' not remade because of errors.
make[1]: Leaving directory '/home/syerabol/zephyr/sanity-out/qemu_x86/tests/subsys/logging/log_output/logging.log_output'
For complete log, please find the attached log.
build.log
Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows): Fedora
Toolchain (e.g Zephyr SDK, ...)
Commit SHA or Version fb0faaa1239ad5f6577d3268c67ba168aab57656

Additional context
Add any other context about the problem here.

it seems this change just consider Arm platform, we should also take care x86. I'm cooking the patch for this issue.