Custom DataAnnotation ValidationAttribute error message is not showing

Model Definition:
    [DbRequired]
    [Display(Name = "USER NAME", Prompt = "ENTER USER NAME")]
    public string User_Name
    {
        get { return GetValue(() => User_Name); }
        set { SetValue(() => User_Name, value); }
    }

    [Display(Name = "PASSWORD", Prompt = "ENTER PASSWORD")]
    [DataType(DataType.Password)]
    [DbRequired]
    public string User_Password
    {
        get { return GetValue(() => User_Password); }
        set { SetValue(() => User_Password, value); }
    }

ValidationAttribute:
public class DbRequired : RequiredAttribute
{
DataContext db;
protected override ValidationResult IsValid(object value, ValidationContext validationContext)
{
if ((value == null || value.ToString() == string.Empty || value.ToString() == "0"))
{
return new ValidationResult("USER NAME IS REQUIRED FIELD !");
}
else
{
return ValidationResult.Success;
}
}
}
When using builtin Required then working fine but when overriding RequiredAttribute then error message not displayed:

@PKYADAV Did you find the solution to this? Running into the same issue.

@PKYADAV Did you find the solution to this? Running into the same issue.

Yes, just pass the member name in validation context in below line:
return new ValidationResult("USER NAME IS REQUIRED FIELD !");
Please try and let me know, if any issue. Will post source code reference.

@PKYADAV Thank you for the help! I ended up ditching DataAnnotations out of frustration with custom attributes, and am now using FluentValidation. I appreciate such a quick response! 😄

Hii @pelhamrj,
If your requirement is static then Fluent Validation is best option but if your requirement is dynamic then you need to write custom validation attribute.

@PKYADAV Did you find the solution to this? Running into the same issue.

Yes, just pass the member name in validation context in below line:
return new ValidationResult("USER NAME IS REQUIRED FIELD !");
Please try and let me know, if any issue. Will post source code reference.

this is works for me but why? if i don't know the member name how can i solve it?

Can you share more information and scenario on that you want to achieve?

Can you share more information and scenario on that you want to achieve?

well, in asp.net project when I used custom data annotation attributes, I didn't need to explicitly put input name in returning of ValidationResult but now in blazor projects, if I don't do this, custom annotations won't work

At least in Blazor Server 3.0 we can confirm the same behavior that @dev-masih is reporting.
We also find this confusing behavior. Ideally the system should be defaulting to the field that the validator is attached to if an explicit list of one or more fields is omitted.

We were trying to use custom validation in Blazor Server 3.0. We were not having any success until we found this issue. Just wanted to share a clear example of what works for us in case it helps anyone.
return new ValidationResult("REQUIRED FIELD !", new [] { validationContext.MemberName });


fully split / more work on d_com_inf_game

i'll fix clang later, need 2 sleep

i'll fix clang later, need 2 sleep


PNG with embedded color profile not displayed correctly

Hi,
I was trying to load a PNG image in TEV which was exported from GIMP. I did not create the image myself, but the person who created the image essentially loaded an EXR image in GIMP and exported it as a PNG with minor changes. The PNG displays correctly in Adobe Photoshop and Preview on MacOS, but not in TEV.
Upon closer inspection, I found that the PNG was stored in 16 bit with a custom color profile from GIMP. Reducing to 8 bit, but keeping the profile, does not change anything about the way TEV displays the image. If I convert the profile to a more standard RGB profile in Photoshop, TEV displays the image correctly.
So it seems that the problem is that TEV ignores custom color profiles in PNG files (?). I am not sure how easy it is to change that, but it would be good to at least have a warning being shown.
I have attached both an 8 bit and the original 16 bit version of the file.
test_images.zip
Best,
Delio

Hi Delio, thanks for sharing + allowing for reproduction! This is a good issue to keep track of.
PNG decoding is unfortunately completely out of the hands of tev. tev uses stbi to open LDR images, including PNGs, and stbi doesn't support querying color profile information. See this issue on their end.
I'm hesitant to pull in heavier cannons than stbi to decode LDR images more correctly, since the primary purpose of tev remains operating on HDR data.

Hi Thomas,
I knew that TEV was using an external library to load PNGs, but I wasn't aware that they don't even support color profiles! Let's hope someone replies to your comment on the other issue, such that we can at least have some kind of warning :)
Thanks for looking into it
Delio

Thank you so much for mentioning this problem and the tips on how to fix it with photoshop! After I used photoshop to open the problematic png file, photoshop prompted that there was a problem with the color profile. After conversion, it can be displayed normally in Tev after saving.


Destructuring of records doesn't work in lambda parameters

This works:
List<(int, int)> vals = [];
for (var (a, b) in vals) {
  print(a+b);
}

but this fails with error The argument type 'InvalidType Function(dynamic Function(int, int))' can't be assigned to the parameter type 'dynamic Function((int, int))':
List<(int, int)> vals = [];
final sums = vals.map(((int a, int b)) => a + b).toList();  // Error

I assumed destructuring should work in lambda parameters.
Actually it doesn't work even in function definitions -- this fails with a very strange syntax error, Use the generic function type syntax to declare the parameter ''. Try using the generic function type syntax.
void sum((int a, int b)) => a + b;  // Error

The following works (by not using destructuring at all). You can't use v.a or v.b, since the field names are ignored in the type:
void sum((int a, int b) v) => v.$1 + v.$2;

Duplicate of https://github.com/dart-lang/language/issues/3001
(On which you have already commented few weeks ago by the way. So no need to file new issues).

Face-palm :-D  Thanks for pointing that out, I totally forgot that I found that issue. I went looking for it again, and didn't find it this time...
Before I go file another dup, is there an issue for allowing v.a and v.b to be used instead of v.$1 and v.$2, in the last example I gave?

is there an issue for allowing v.a and v.b to be used instead of v.$1 and v.$2, in the last example I gave?

I don't think so. Please file it at dart-lang/language repo (that's the place for all language feature requests).
The choice of names not having any meaning was deliberate, but I don't see any reason why it would not work to just allow this in a statically typed context (i.e. ignoring dynamic invocations entirely).


Is Grpc Proxy Support available in the SDK?

Is Grpc Proxy  Support Available?
Please help us understand if Grpc Proxy Support is available in dotnet dapr sdk?
As described here:
https://docs.dapr.io/developing-applications/building-blocks/service-invocation/howto-invoke-services-grpc/
We tried to follow the instruction/steps shown on this  video but  the client fails to hit Grpc Port.
https://www.youtube.com/watch?v=Q2xS153IofM
We are on DotNet 6.0.100 and Version 17.1.0 Preview 3.0

Yes it is, we just don't have an example for proxying. You'd use this method to create your invoker which will handle passing the header for you:
https://github.com/dapr/dotnet-sdk/blob/master/src/Dapr.Client/DaprClient.cs#L133


error prisma migrate

Hello,
I have an existing project using pPrisma. Im trying prisma migrate. And I got this Error. How can I debug that?
npx prisma migrate dev --name init
Environment variables loaded from .env
Environment variables loaded from prisma/.env
prisma:warn @prisma/cli has been renamed to prisma.
Please uninstall @prisma/cli: npm remove @prisma/cli
And install prisma: npm i --save-dev prisma
Prisma schema loaded from prisma/schema.prisma
Datasource "db": MySQL database "nacho@prod" at "localhost:3306"

✔ Drift detected: Your database schema is not in sync with your migration history.

We need to reset the MySQL database "nacho@prod" at "localhost:3306".
Do you want to continue? All data will be lost. … yes

Error: Database error: Error querying the database: Server error: `ERROR 42000 (1061): Duplicate key name 'userId''
   0: migration_core::api::ApplyMigrations
             at migration-engine/core/src/api.rs:75

Hi @alan345
So:

Is this your production database? Does it has data already in it (that you care about, don't want to lose)
Are you using version 2.19.0?
It looks like it's not your first migration? Did you edit the migration.sql file maybe?

Hello

Yes I care about data. But I ran it in localhost. So I accept to delete
all data.
yes the latest. 2.19.0
no it's my first migration. Why do you think it is not? No I did not
change the sql file

Thanks
On Thu, Mar 18, 2021, 5:57 AM Joël Galeran @.***> wrote:

Hi @alan345 https://github.com/alan345
So:

Is this your production database? Does it has data already in it
(that you care about, don't want to lose)
Are you using version 2.19.0?
It looks like it's not your first migration? Did you edit the
migration.sql file maybe?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prisma/prisma/issues/6152#issuecomment-801905569, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADUKJPUANANO2SHXSOTYHATTEH2DBANCNFSM4ZLCHFGA
.

So because you already have a database with data you care about I recommend you to read these docs about the baselining flow:

Baselining is for introducing Prisma Migrate to existing databases / brownfield projects. Concretely it's to tell Prisma Migrate to assume that one or more migration(s) were already executed so the generated migration(s) won't fail when they will try to create tables that already exist.
https://www.prisma.io/docs/guides/prisma-guides/add-prisma-migrate-to-a-project

If you have any feedback/questions let me know!

Please open a new issue if other problems arise, thanks!


ImportError: Failed to load the native TensorFlow runtime due to undefined symbol

Issue Description
I encountered an error while trying to run my project that uses TensorFlow. The error seems to be related to the TensorFlow runtime and an undefined symbol in the _pywrap_tensorflow_internal.so file. Below is the stack trace of the error.
System Information

OS Platform and Distribution: Ubuntu 20.04.6 LTS
Python Version: 3.10.14
TensorFlow Version: 2.9.3

Stack Trace
File "pywrap_tensorflow.py", line 77, in <module>
    raise ImportError(ImportError: Traceback (most recent call last):
  File "pywrap_tensorflow.py", line 62, in <module>
    from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: /.../_pywrap_tensorflow_internal.so: undefined symbol: _ZNK10tensorflow4data11DatasetBase8FinalizeEPNS_15OpKernelContextESt8functionIFNS_8StatusOrISt10unique_ptrIS1_NS_4core15RefCountDeleterEEEEvEE

Failed to load the native TensorFlow runtime.

Any help to resolve this issue would be greatly appreciated.
Thank you!

@MatthiasNeumueller,
There are at least 3 possible scenarios:
    1. You need to install the MSVC 2019 redistributable
    2. Your CPU does not support AVX2 instructions
    3. Your CPU/Python is on 32 bits
    4. There is a library that is in a different location/not installed on your system that cannot be loaded.

Could you please confirm that you installed Tensorflow using pip and kindly share the steps you have followed to install Tensorflow. It is recommended to follow the installation instructions from here.
https://github.com/tensorflow/tensorflow/issues/63082#issuecomment-1970413004
https://github.com/tensorflow/tensorflow/issues/67067#issuecomment-2100116063
Thank you!

@tilakrayal thanks for the fast response.
I created a conda environment using conda version 24.5.0 and python version 3.10. Then I installed tensorflow according to the installation instructions shared above using the following command:
python3 -m pip install tensorflow[and-cuda]
After the installation finished successful the verification of tensorflow as stated in the installation instruction shows the following ImportError:
from tensorflow.python.platform import _pywrap_cpu_feature_guard

ImportError: /.../_pywrap_tensorflow_internal.so: undefined symbol: _ZN10tensorflow10OpRegistry8RegisterERKSt8functionIFN4absl12lts_202308026StatusEPNS_18OpRegistrationDataEEE

@tilakrayal any update on this issue?

@MatthiasNeumueller,
Apologies for the delay. Tensorflow v2.9 is the pretty old version. Could you please try to install the tensorflow latest version 2.15 or 2.17 and let us know if it is working in this case.
https://www.tensorflow.org/install/pip
Thank you!

@tilakrayal no worries.
I checked that I installed the latest tf version (2.17.0) on a fresh venv and proceeded by checking whether everything is working properly with the code shown in the instruction. and I get the same error again.
Code to verify the installation:
python3 -c "import tensorflow as tf; print(tf.config.list_physical_devices('GPU'))"
Error message:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/path/to/tensorflow/__init__.py", line 38, in <module>
    from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow  # pylint: disable=unused-import
  File "/path/to/tensorflow/python/pywrap_tensorflow.py", line 34, in <module>
    self_check.preload_check()
  File "/path/to/tensorflow/python/platform/self_check.py", line 63, in preload_check
    from tensorflow.python.platform import _pywrap_cpu_feature_guard
ImportError: /path/to/tensorflow/python/platform/../_pywrap_tensorflow_internal.so: undefined symbol: _ZN10tensorflow10OpRegistry8RegisterERKSt8functionIFN4absl12lts_202308026StatusEPNS_18OpRegistrationDataEEE

@MatthiasNeumueller,
Apologies for the delay. Could you please provide the complete environment details and the steps you followed to install the tensorflow which helps to debug the issue. Thank you!

@tilakrayal yes sure.
Installed packages and their versions:
absl-py==2.1.0
astunparse==1.6.3
certifi==2024.7.4
charset-normalizer==3.3.2
flatbuffers==24.3.25
gast==0.6.0
google-pasta==0.2.0
grpcio==1.65.4
h5py==3.11.0
idna==3.7
keras==3.4.1
libclang==18.1.1
Markdown==3.6
markdown-it-py==3.0.0
MarkupSafe==2.1.5
mdurl==0.1.2
ml-dtypes==0.4.0
namex==0.0.8
numpy==1.26.4
nvidia-cublas-cu12==<IP_ADDRESS>
nvidia-cuda-cupti-cu12==12.3.101
nvidia-cuda-nvcc-cu12==12.3.107
nvidia-cuda-nvrtc-cu12==12.3.107
nvidia-cuda-runtime-cu12==12.3.101
nvidia-cudnn-cu12==<IP_ADDRESS>
nvidia-cufft-cu12==<IP_ADDRESS>
nvidia-curand-cu12==<IP_ADDRESS>
nvidia-cusolver-cu12==<IP_ADDRESS>
nvidia-cusparse-cu12==<IP_ADDRESS>
nvidia-nccl-cu12==2.19.3
nvidia-nvjitlink-cu12==12.3.101
opt-einsum==3.3.0
optree==0.12.1
packaging==24.1
protobuf==4.25.4
Pygments==2.18.0
requests==2.32.3
rich==13.7.1
six==1.16.0
tensorboard==2.17.0
tensorboard-data-server==0.7.2
tensorflow==2.17.0
tensorflow-io-gcs-filesystem==0.37.1
termcolor==2.4.0
typing_extensions==4.12.2
urllib3==2.2.2
Werkzeug==3.0.3
wrapt==1.16.0
System details:
Linux-5.15.0-119-generic-x86_64-with-glibc2.31
Steps to install tensorflow are the same as listed in the official documentation:
https://www.tensorflow.org/install/pip


#100 inner scrolling doesnt respect container border width

for test case: http://mkoryak.github.io/floatThead/tests/issue-100/

Thanks for looking into this one :)
Unfortunately your PR breaks the  absolutePostioning:false version of the testcase, and also removing tableContainerGap breaks tables where there is stuff above table but within the scrollingContainer. Since you took the time to open this PR, I took some time to create a jsfiddle which show the issues above:
This is what the original code does:
https://jsfiddle.net/2rv7mo29/2/embedded/result/
This is what this PR does:
https://jsfiddle.net/5xcvu0tk/3/embedded/result/
Thanks!

Thanks for the quick review on this. I'll look into it some more based on the test cases you mentioned.

moved to https://github.com/mkoryak/floatThead/pull/185


No internal package use in tests

Based on a comment I made earlier in #1073, I had a look at it would take to enforce a "No imports from internal in tests" policy.
A couple of easy, self-contained packages to make public fell out, but then the next thing I wanted to make public was internal/cmd, and it exposes a couple of types in its APIs from internal/cow and internal/uvm, and the dependency graph explodes at that point, even before I looked at test/functional/wcow_test.go which pulls 10 different packages from internal plus hcsshim itself, probably because of https://github.com/microsoft/hcsshim/blob/1f8211a77a20be7a196e31f49d007ccc61dd0981/test/functional/wcow_test.go#L29-L36
which leaps-out as a super-code smell if it's testing old and new interfaces, and the entire "new" interface is not public.
So I'm posting this for direction/consideration/ideation:

Both of the existing changes (<dropped in favour of #1201> and fbffeaab3f079eaea463706f9b0f23fc367792a1) have some alternative approaches listed.
I still think using pkg/ for publishing ociwclayer was a mistake, but I guess it does send the signal that this is intended to be a more-stable API, within the constraints of the current v0.x version. (It also sends the signal that I was using last decade's best-practice due to learning Go from old tutorials). And #1201 has doubled down on this, so I guess this is where we're going now.
Similarly to the current state of #1073, I'm not sure if we want to go wide on publishing modules, go narrow using a lot of type aliases, or even consider a bunch of helper functions to expose/wrap internal APIs.
It's possible that I'm wrongheaded about this, and the preference is to keep these modules mostly internal, in order to drive users via containerd-shim and similar utilities. In this case, I can drop this experiment, and focus narrowly on getting the layer manipulation code (which doesn't have a wrapper, e.g., containerd imports it directly) sorted out for v2, which are blocked for me on #1073 and #1076, but are not blocked by this work particularly.

If I or someone else ever come back to this, I saw a neat trick in the Go source itself, of having an _test.go-suffixed file that only exports internal symbols for use in tests. It might not help here, but did remind me of this experiment.


fix: use EthTraceMapper to mapper geth trace

{"type": "trace", "transaction_index": 0, "from_address": "0xe5e7492282fd1e3bfac337a0beccd29b15b7b240", "to_address": "0x25e1c58040f27ecf20bbd4ca83a09290326896b3", "value": 0, "input": "0x202ee0ed000000000000000000000000000000000000000000000000000000000000c8ed00000000000000000000000000000000000000000000000000000060746d4aa0", "output": "0x", "trace_type": "call", "call_type": "call", "reward_type": null, "gas": 478596, "gas_used": 141339, "subtraces": 1, "trace_address": [], "error": null, "status": null, "transaction_hash": null, "block_number": 170001, "trace_id": null, "trace_index": null, "block_timestamp":<PHONE_NUMBER>, "block_hash": "0x468fc6aa57726df8ff0026547f2e5c3231bc364a4f5cb50bee376c5ee387517f"}

still have some bug for tx hash


Github workers warn about set-output command going to be deprecated

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

It looks that the set-output workflow command has been removed.


[OPPRO-162] Fix BHJ coredump

Depends on https://github.com/oap-project/velox/pull/23

Verified locally on TPC-H.

note, the GHA failed due to missing parquet support in velox, which is fixed in main already


Unnecessary package?

@luiztauffer  I couldn't find a reference to the tdt package in this repo (there shouldn't be any need for it), so I'm not sure why a version is hard coded in here (which could affect versions in our own code). Can you remove it unless there's a reason it should be there?
https://github.com/catalystneuro/ecogVIS/blob/c4ea9aaf05b427ec28b9eea21496ca694a2b9b56/requirements.txt#L20

removed


Release rayon 0.8.2

ParallelSliceMut now has six parallel sorting methods with the same
variations as the standard library.

par_sort, par_sort_by, and par_sort_by_key perform stable sorts in
parallel, using the default order, a custom comparator, or a key extraction
function, respectively.
par_sort_unstable, par_sort_unstable_by, and par_sort_unstable_by_key
perform unstable sorts with the same comparison options.

/r/rust is excited, so let's ship it!

Done!


refactor(rust): NodeManager constructor

* Work in progress *
Current Behavior
Current version of NodeManager::create receives 11 arguments.
#[allow(clippy::too_many_arguments)]
pub async fn create(
        ctx: &Context,
        node_name: String,
        node_dir: PathBuf,
        // Should be passed only when creating fresh node and we want it to get default root Identity
        identity_override: Option<IdentityOverride>,
        skip_defaults: bool,
        enable_credential_checks: bool,
        ac: Option<&AuthoritiesConfig>,
        project_id: Option<Vec<u8>>,
        projects: BTreeMap<String, ProjectLookup>,
        api_transport: (TransportType, TransportMode, String),
        tcp_transport: TcpTransport,
) -> Result<Self>

Proposed Changes
This PR is meant to fix #3527

Extract NodeManager::create arguments into three new Options structs.
-- NodeManagerGeneralOptions, NodeManagerProjectsOptions and NodeManagerTransportOptions

pub async fn create(
        ctx: &Context,
        general_options: NodeManagerGeneralOptions<'_>,
        projects_options: NodeManagerProjectsOptions,
        transport_options: NodeManagerTransportOptions,
) -> Result<Self>

Checks

[ ] All commits in this Pull Request are signed and Verified by Github.
[ ] All commits in this Pull Request follow the Ockam commit message convention.
[ ] I accept the Ockam Community Code of Conduct.
[ ] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository.

Hey @mrinalwadhwa, this is my work in progress draft PR.
First of all, I'll rename commits and sign so they follow convention before marking as ready for review.
But I'd like to ask you for some input on the following issues:

I've tried grouping options based on what I've read and understood from the places where NodeManager::create is used. Do you agree with the ...Options structs I've created or would there be a better suggestion?
I haven't created ::new or ::default methods for these new structs, so that's why the struct properties are set to pub now. I haven't found any convention regarding that on the project. So, would you like for those methods to be created?

The last one is more because of my inexperience with Rust in big projects.

How can I run the tests mod inside service.rs? It does not seem to be run by using cargo nextest run or cargo test and I haven't found a way of running it anywhere?

Hey @vncsalencar , tnx for your contribution. Answering your questions:

I think Options suffix makes sense here, I have no objections. Also, it's easy to rename later if needed
We have few approaches in the codebase, but I would suggest following:

Implement or derive Default trait where it makes sense
Make fields private with getters
Create a constructor (::new). It may take all of the fields as arguments if there aren't too many. If makes sense, some of them (that are rarely used/optional) may be not included in the constructor, must have setters then
Make setter for some fields (those that are expected to change, or are optional

cargo test should run enough tests in your case. Also cargo fmt and cargo clippy may be useful

Let me know if you need anything else

@mergifyio rebase

@vncsalencar Thank you for spending time on this, before we can merge please
Accept the Ockam Contributor License Agreement by adding your Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository.
The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a PR, this will make the commit as verified.
Also, could you please look at why CI fails? Probably needs cargo fmt and commit message convention fix

@SanjoDeundiak ran cargo fmt and pushed it now. Re-requesting permission for the CI to run.

Sorry, had trouble with gpg on my side, I rebased and signed + verified the commits.

@mergifyio rebase


:sparkles: feat: support lastUpdated

💻 变更类型 | Change Type

[x] ✨ feat
[ ] 🐛 fix
[ ] 💄 style
[ ] 🔨 chore
[ ] 📝 docs

🔀 变更说明 | Description of Change
close: #100

📝 补充信息 | Additional Information

@Wxh16144 rebase 一下？


[FLINK-4035] Add a streaming connector for Apache Kafka 0.10.x

This pull request subsumes https://github.com/apache/flink/pull/2231.
Compared to #2231, I've based the connector on the existing 0.9 code (by extending it, reducing the amount of copied code), added a test case for the timestamp functionality and updated the documentation.

Just looked over this briefly.
What struck me first is that this again uses the dirty trick of adding a dependency to "Flink Kafka 0.9" and then transitively excluding "Kafka 0.9". Is there a nicer way to solve this?

Left a few comments on some high-level design choices for a first review. Mostly on FlinkKafkaProducer010, I wonder if there are other better possibilities over there?

@StephanEwen: The explicit exclude is actually not needed, because the kafka version defined in the connector has precedence over transitive kafka versions.
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ flink-connector-kafka-0.10_2.10 ---
[INFO] org.apache.flink:flink-connector-kafka-0.10_2.10:jar:1.2-SNAPSHOT
[INFO] +- org.apache.flink:flink-connector-kafka-0.9_2.10:jar:1.2-SNAPSHOT:compile
[INFO] |  \- org.apache.flink:flink-connector-kafka-base_2.10:jar:1.2-SNAPSHOT:compile
[INFO] +- org.apache.kafka:kafka-clients:jar:<IP_ADDRESS>:compile
[INFO] |  +- net.jpountz.lz4:lz4:jar:1.3.0:compile
[INFO] |  \- org.xerial.snappy:snappy-java:jar:<IP_ADDRESS>:compile

Thank you for the review @tzulitai. I'll try to find some time soon to look into your comments in detail.

This may be the wrong place to bring this up, but as you are discussing changes to the Kafka connector API, I think it is worth bring it up.
As I've pointed out elsewhere, the current connector API makes it difficult to make use of Kafka native serializer or deserializer (org.apache.kafka.common.[Serializer, Deserializer]), which can be configured via the Kafka client and producer configs.
The connector code assumes that ConsummerRecords and ProducerRecords are both parametrized as <byte[], byte[]>, with the Flink serdes performing the conversion to/from byte[].  This makes it difficult to make use of Confluent's KafkaAvroSerializer and KafkaAvroDecoder, which make use of their schema registry.
If you are going to change the connector API, it would be good to tackle this issue at the same time to avoid future changes.  The connector should allow the type parametrization of the Kafka consumer and producer, and should make use of a pass through Flink serde by default.

@eliaslevy, I assume you are referring to https://issues.apache.org/jira/browse/FLINK-4050.
Its good that you are mentioning the issue again, so I can move it a bit up on my TODO list.
I would personally prefer to first add the Kafka 0.10 module in this pull request and then resolve FLINK-4050 independently. I know that this might lead to a little bit of duplicate work on the Kafka 0.10 code, but on the other hand its easier to discuss one issue at a time :)

@rmetzger that's the one. NP.  I realize breaking it up makes things easier.  I just thought I'd mention it.

@tzulitai I've addressed your comments.
The Producer is now "hybrid": you can use it with both invocation methods.
The AbstractFetcher now accepts a long timestamp instead of a record.

Thanks Robert for addressing my comments :)
Overall, I like the new hybrid producer approach. However, I'm still curious whether or not it is possible / reasonable to drop the FlinkKafkaProducer010Configuration return type of invocation (b), and let both invocation methods return FlinkKafkaProducer010 instead. So,
FlinkKafkaProducer010 kafka = new FlinkKafkaProducer010(...)
// or FlinkKafkaProducer010 kafka = FlinkKafkaProducer010.writeToKafkaWithTimestamps(...) for timestamp support

// setter config methods directly done on the FlinkKafkaProducer010 instance regardless of (a) or (b)
kafka.setLogFailuresOnly(true)
kafka.setFlushOnCheckpoint(true)
kafka.setWriteTimestampToKafka(true) // would not have effect if original invocation method (a) was used

But we'll need to be bit hacky in invokeInternal(element, elementTimestamp), something like only letting the given timestamp to ProducerRecord be non-null if writeTimestampToKafka && elementTimestamp != Long.MIN_VALUE.
What do you think?

+1 for this pr

Any thoughts on when this might make it into a release? We are having issues running Flink with Kafka 0.10 and would like to have an idea of whether we can/should wait for this or pull it and try building our own. Thanks.

Looks like we need to rebase this PR on the recently merged Kerberos support.

@cjstehno I would expect this to be in the 1.2.0 major release, which would probably be ~2 months from now according to Flink's past release cycle. The Flink community usually doesn't release major new features like this between minor bugfix releases.

I'm currently working on rebasing the PR and addressing the comments.

@tzulitai I addressed all your comments except the one relating FlinkKafkaProducer010Configuration: I had a quick offline discussion with @StephanEwen about the issue and he suggested to add the timestamp to the regular sink interface.
But I would like to make that change separate from this one, and merge the Kafka 0.10. support as-is. This will make it easier for people to try it out now and provide us with feedback. Also, I think some other Kafka related pull requests are blocked on this one.
@tzulitai could you do a final pass over the changes. If you agree, I'd like to merge it afterwards.

@rmetzger Thanks for addressing the comments! Did a final pass, and the changes look good to me.
I agree with merging the connector as is. Adding the timestamp to the regular sink interface seems like a good long term solution.
+1 to merge once travis turns green ;)

Just found some minor issues that can be fixed when merging.

Thank you for the review. I'll address your comments, rebase again, test it, and if it turns green merge it ;)

Tests are running https://travis-ci.org/rmetzger/flink/builds/166441047


Adding TOC to docs and improving 101's

Some tests should be run again. Please check, @mmerce

@unmonoqueteclea , tests passed, but please wait till I add some improvements to the api.ok method

@unmonoqueteclea, finally tests passed. Can you please merge, tag and publish?

version.py is not updated


[Docs]: Send emails using the SMTP plugin -  How-to-guide

Is there an existing issue for this?

[X] I have searched the existing issues

Documentation Link
No response
Discord/slack/intercom Link
No response
Describe the problem and improvement.
Send emails using the SMTP plugin

Duplicate of #1719


[CompliantRecordingBot] CallHandler.OnRecordingStatusFlip()

I understand that this method intends to demonstrate the operation that Media Bot may stop the recording in the middle of the call/meeting. However, I do not understand other operations, i.e. setting the status to 'RecordingStatsu.Failed' or calling IParticipant.DeleteAsync(). What kind of real world scenarios do they try to simulate? I don't see ICall.UpdateReocrdingStatusAsync(), and do you plan to add this to the doc by the next update?

ICall.UpdateReocrdingStatusAsync() is only in beta, so no documentation yet.  All it does is send a signal to the Teams client, which would then draw up some UI that tells users what is happening.  I believe the Teams client changes have rolled out, so you can try and test it out and see what happens when you set the different states.
https://docs.microsoft.com/en-us/graph/api/call-updaterecordingstatus?view=graph-rest-beta&tabs=http
The Started state must be reported for by bots recording the call (while they are recording), and is a requirement to use the Compliance Recording APIs.  If we find any bots not conforming to this requirement, we will disable them.
The Failed state is required for compliance for reporting purposes, and it is recommended that if anything goes wrong the bot, it should send this state.
IParticipant.DeleteAsync() allows the bot to remove only the Recorded Participant (RP) from the call.  This is to support policy evaluations.  One example is if an RP can only be in a call with other compliant users, and if anyone joins that is non-compliant the bot can eject the RP.
Consider the APIs exposed as a toolbox to allow the bot to perform various Compliance Recording related activities.  Your bot may not have a need for these, but others may.

Thank you for the explanation.
That totally makes sense.
The good news is that I observed correctly that Teams client UI showed the banner for it!

Let me ask two follow up questions.

Am I correct that media feed to the bot starts and ends unrelated to this method? i.e. this method does not directly affect the timing of media streaming?

You said 'reporting purpose'. Am I correct that Teams will have (or already has) the capability to record this call and report it to Tenant admin?

yes
That would be a PM question, I am not sure.

Thank you! I will find out someone who may answer #2 via our business channel.


Fix centos sidecar

Please provide a description of this PR:
Seeing a failure trying to build the centos image. It looks like they moved from http to https
curl http://vault.centos.org/centos/8/AppStream/x86_64/os/repodata/repomd.xml
...
<title>301 Moved Permanently</title>

Moved Permanently

The document has moved here.

In response to a cherrypick label: new pull request created: #37399

In response to a cherrypick label: new pull request created: #37400

In response to a cherrypick label: new pull request created: #37401


feat(chat): fix app icon publishing warning message, add 'save all' option to code editor and 'save' to code editor file context menu, fix code editor empty files content (Issues #2576, #2515, #2427)

Description:
fix app icon publishing warning message
add 'save all' option to code editor and 'save' to code editor file context menu
fix code editor empty files content
Issues:

Issue #2576
Issue #2515
Issue #2427

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review

/deploy-review

/deploy-review


Tests failed with haxe 3.3.0

Hello,
I just ran :
haxe test.hxml

And it prints the following :
/home/gogoprog/.haxelibs/hamcrest/2,0,1/org/hamcrest/collection/IsHashContaining.hx:36: characters 26-34 : Warning : Usage of this typedef is deprecated
test/ash/core/SystemTest.hx:218: characters 33-45 : Unknown identifier : sameInstance
test/ash/core/SystemTest.hx:224: characters 33-45 : Unknown identifier : sameInstance
test/ash/core/SystemTest.hx:169: characters 49-61 : Unknown identifier : sameInstance
test/ash/core/SystemTest.hx:196: characters 34-46 : Unknown identifier : sameInstance
test/ash/core/AshAndFamilyIntegrationTest.hx:48: characters 37-49 : Unknown identifier : sameInstance
...

I don't know if it this linked to the latest version.
By the way using the framework seems to be fine, just the tests are failing.

I think those tests require older version of munit or hamcrest or something. I'll look into it and set specific versions in hxml.

I checked a bit and I think it would be better to update the test code to match the latest munit/hamcrest versions


Feature request: disable event validation

Let's say that I would like to handle invalid events that do not conform with specification in my own receiver function.
Is it possible to add a feature toggle to disable validation in Invoke?
// Check if event is valid before invoking the receiver function
if e != nil {
    if validationErr := e.Validate(); validationErr != nil {
        r.observabilityService.RecordReceivedMalformedEvent(ctx, validationErr)
	return respFn(ctx, nil, protocol.NewReceipt(false, "validation error in incoming event: %w", validationErr))
    }
}

The problem I'm trying to solve is to send ack even for invalid events received from kafka.

I see two ways to go about this,
1- use the bindings and protocol directly without the client.
2- There used to be a way to recover from malformed events, it was a function you would register with the client and you could return back a correctly formatted event or nil and it would do what you want: ack the upstream.
Which of these options would best solve your problem? I am not sure it is a great idea to allow the validation to be turned off in the client, but if there is a compelling enough use-case I could be convinced. (guess this is option 3 as the issue suggests)

Is there any example how to implement the second option?
Thanks

Came here with a similar issue. I have a client that uses the http protocol to receive cloudevents from a pubsub push. (I have a custom Format to handle the "application/json" that pub-sub sends.)
If any kind of malformed event gets into the pubsub topic, and my format.Unmarshal() returns an error, cloud run reports a 500, but pubsub will continue to send it infinitely. It's hard to trace exactly where Unmarshal gets called in the receive loop, but I'm presuming it's in binding.ToEvent(), which I think happens just before event validation.
I actually wonder whether a message that fails event parsing or validation should ever do anything other than NACK, because definitionally, it can't be handled. I actually thought that's what the current code was doing when it responds with protocol.NewReceipt(false, "failed to convert Message to Event: %w", eventErr), but apparently not?
(I guess there are cases where you could potentially redeploy and be in a position to handle them later, if it was not the message that was malformed, but the parser 🤷🏼 .)
I'd like to continue using the client, which provides a simpler way of interacting with inbound events. And, I like that the validation exists. But, I too would love an option to recover from a malformed event.
I'm happy to do a user-defined method that returns nil. I'd also be happy with a client option that automatically NACK'd failed event parsing or validation. That seems a bit safer than allowing to be turned off entirely?


uhdm, surelog 1.83 -> 1.84-unstable-2024-11-07

Update both, UHDM and Surelog (that are somewhat version-locked) to 1.84 and their respective latest unstable upstream git hashes.
Two separate commits.
Replaces #332963
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Looks like this PR got caught in the middle of projects being moved to pkgs/by-name/ hence the merge conflict.
Will open a separate one.


Run localization without mapping. Nav tuning.

Sorry, I meant to make this PR against my own private fork. Although I think there are some useful things here which I should probably break out into smaller PR's...


Run TravisCI builds in containers

TravisCI now supports containerised builds, per
blog.travis-ci.com/2014-12-17-faster-builds-with-container-based-infrastructure/.
Enable them.

It's worth stating why we want to use this build system.

@mattbostock Amended.


Last step "Add-AppxPackage -Register path-to-extracted-msix\AppxManifest.XML" doesn't work

I performed all steps listed in the instructions, and all seemed to work property, except...
When I go to the  "C:\WSA\WsaPackage_2203.40000.3.0_x64_Release-Nightly" folder, and execute "Add-AppxPackage -Register .\AppxManifest.xml" I get the following error:
Add-AppxPackage: Deployment failed with HRESULT: 0x80073CF9, Install failed. Please contact your software vendor. (Exception from HRESULT: 0x80073CF9)
Rejecting a request to register from AppxBundleManifest.xml because the manifest is not in the package root.
NOTE: For additional information, look for [ActivityId] f19f99bc-5489-0000-564a-2ef38954d801 in the Event Log or use the command line Get-AppPackageLog -ActivityID f19f99bc-5489-0000-564a-2ef38954d801

I performed all steps listed in the instructions, and all seemed to work property, except...
When I go to the "C:\WSA\WsaPackage_2203.40000.3.0_x64_Release-Nightly" folder, and execute "Add-AppxPackage -Register .\AppxManifest.xml" I get the following error:
Add-AppxPackage: Deployment failed with HRESULT: 0x80073CF9, Install failed. Please contact your software vendor. (Exception from HRESULT: 0x80073CF9) Rejecting a request to register from AppxBundleManifest.xml because the manifest is not in the package root. NOTE: For additional information, look for [ActivityId] f19f99bc-5489-0000-564a-2ef38954d801 in the Event Log or use the command line Get-AppPackageLog -ActivityID f19f99bc-5489-0000-564a-2ef38954d801

The Manifest is either in the wrong folder or you messed up the folder structure somehow

I get Windows cannot install package MicrosoftCorporationII.WindowsSubsystemForAndroid_2203.40000.3.0_x64__8wekyb3d8bbwe beca use this package is not compatible with the device. The package requires OS version 10.0.22000.120 or higher on the Win dows.Desktop device family. The device is currently running OS version 10.0.19044.1645.

You are on too old of a version of Windows to install this. Either you downloaded the wrong build or they have begun to switch retail over to requiring 11

is there a version for windows 10?

Straight from the readme on the front page of the project, lol
Just update 10 to latest, or install 11

This is confusing - WSA doesn't work on Windows 10 at all (even after force-editing the manifest files), users need to have Windows 11; But the preparation steps (involving usage of WSL) can be done on Windows 10, version 2004 and above.

WSL is used to do the prep steps because Android is based on Linux, so Linux tools can be used to manipulate the Android disk images that ship with WSA. So WSL is a convenient way to do it, but you can use any Linux PC or VM to do those steps. You can probably use something like Cygwin or native Windows ports of the tools the scripts run but you're on your own if you try that.

I got the following error:
Add-AppxPackage : Deployment failed with HRESULT: 0x80073CFD, A Prerequisite for an install could not be satisfied.
Windows cannot install package MicrosoftCorporationII.WindowsSubsystemForAndroid_2206.40000.15.0_x64__8wekyb3d8bbwe
because this package is not compatible with the device. The package requires OS version 10.0.22000.120 or higher on
the Windows.Desktop device family. The device is currently running OS version 10.0.19044.1889.
NOTE: For additional information, look for [ActivityId] 8ce5e5c8-b0c5-0001-3a86-e78cc5b0d801 in the Event Log or use
the command line Get-AppPackageLog -ActivityID 8ce5e5c8-b0c5-0001-3a86-e78cc5b0d801
At line:1 char:1

Add-AppxPackage -Register C:\WSA\MicrosoftCorporationII.WindowsSubsys ...

  + CategoryInfo          : NotSpecified: (C:\WSA\Microsof...ppxManifest.xml:String) [Add-AppxPackage], Exception
  + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

You need Windows version 10.0.22000 or greater, aka Windows 11


Test Time 12

Test Time 12

@amihaiemil this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2020-12-23T11:04:09.353513.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@MihaiDejeu please keep in mind that manual assignment of tickets is a bad practice and it is discouraged. Next time, please let me elect the assignee.

@amihaiemil thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.


Incorrect expansion

Start with a wire next to a half-braid:

Now drag the braid to the left. In the directed version this does nothing. In the labelled version, it does a bubbling:

This is correct. I had mistakenly thought this is a contraction/expansion pair but it's actually just an expansion.
It's different to beta because we're no longer normalising, but that's fine (arguably more intuitive).


Please add the switch to the Explorer to show the size of the DIR.

Description of the new feature / enhancement
Add a switch to the Explorer to show the size of the DIR
Scenario when this would be used?
I am sure we can easily find the bigggest files and delete them
Supporting information
No response

Duplicate of #356

Issue is a duplicate
Thank you for your issue! We've linked your report against another issue to centralize the thread.
Thanks for helping us to make PowerToys a better piece of software.


Bug: ServiceMonitor should use https instead of http

current servicemonitor resources without option scheme, it can only be used for insecure clusters, example like this.
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: cockroachdb
spec:
  endpoints:
    - interval: 10s
      path: /_status/vars
      port: http
      # without scheme: https
      tlsConfig:
        ca:
          secret:
            key: ca.crt
            name: cockroachdb-node
        cert:
          secret:
            key: tls.crt
            name: cockroachdb-node
        insecureSkipVerify: true
        keySecret:
          key: tls.key
          name: cockroachdb-node
  namespaceSelector:
    any: true
  selector:
    matchLabels:
      app.kubernetes.io/component: cockroachdb
      app.kubernetes.io/instance: cockroachdb
      app.kubernetes.io/name: cockroachdb

And relabelings config is missing, a better suggestion is that, use cluster-name on relabelings to add additional labels for cluster, it makes better to run multiple helm releases in a cluster for monitor

Added: due to service cockroachdb-public(ClusterIP) and cockroachdb(headless) have some labels, it might create duplicate target on prometheus targets(or any other prometheus-like system)


⚠ Bofrost.at has degraded performance

In 807b512, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1224 ms

Resolved: Bofrost.at performance has improved in e4d2320.


chore: Migrate to Scoped Package

Description
Migrated near-wallet-selector to @near-wallet-selector/core.

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Type of change. This type of change is the main reason for the PR.

[ ] FIX - a PR of this type patches a bug.
[ ] FEATURE - a PR of this type introduces a new feature.
[ ] BUILD - a PR of this type introduces build changes.
[ ] CI - a PR of this type introduces CI changes.
[ ] DOCS - a PR of this type introduces DOCS improvement.
[ ] STYLE - a PR of this type introduces style changes.
[ ] REFACTOR - a PR of this type introduces refactoring.
[ ] PERFORMANCE - a PR of this type introduces performance changes.
[ ] TEST - a PR of this type adds more tests.
[x] CHORE - a PR introduces other changes than the specified above.

Breaking changes

[ ] BREAKING CHANGE - SPECIFY: _______
[x] NO BREAKING CHANGE - this PR doesn't contain any breaking changes and it's backwards compatible

Hey @lewis-sqa we might need to update the build command in this file too:
https://github.com/near/wallet-selector/blob/v3-preview/CONTRIBUTING.md
yarn nx run @near-wallet-selector/core:build


[98] Add BaseSharedPreferences for RxJavaTemplate

#98
What happened 👀
We are using SharedPreferences on most current projects for caching data. Creating BaseSharedPreferences for common usage.
Insight 📝

Add one abstract class and two new classes for Storage management and caching data: BaseSharedPreferences, EncryptedSharedPreferences and NormalSharedPreferences.
Setup Hilt with the new StorageModule.
Add some utility functions for BaseSharedPreferences.
Update minSdk to 23 since it is required for the crypto lib to work:

Proof Of Work 📹

Just under the hood optimization, no visual changes. The app is built and running successfully:

@minhnimble You are adding the BaseSharedPreferences in the RxJavaTemplate so I think it could be shared for common usage for both templates 🤔

@minhnimble You are adding the BaseSharedPreferences in the RxJavaTemplate, I think it could be shared for common usage for both templates 🤔
Yeah that would make sense, now I prefer we do it in another PR instead since this PR is for RxJavaTemplate only. I will create another PR for the other template once the final implementation of the SharedPreferences is good. What do you think?

@minhnimble currently, our app module does not contain repository or usecase (where we should use SharePreference), so that there is no usage for SharePreference here. Therefore, I would recommend moving SharePreference to domain package, where repository and usecase are located 😄  How do you think? 🙏


Implement Parametric Evaluation Datasets of the R-Learner paper

The datasets are generated and used here. There are 4 settings A to D, which are useful for researchers, as the R-Learner is currently one of the best Meta-Learner methods.
The data generating processes can be reimplemented so that the user can himself decide on how  many replications to use, etc.

Implemented in 3910d8233.


Add support for force_pull_image

Mesos 0.22 introduced a new option to DockerInfo called "force_pull_image", see:
https://issues.apache.org/jira/browse/MESOS-1886
This option causes mesos to always attempt to pull versions of an existing image. I did not see a way to leverage this option when launching docker containers with singularity...would it be possible to add support for force_pull_image?

duplicate of #584


Async implementation for storage queues.

Async for QueueClient
Async for QueueServiceClient
Port test suite for async ( into the asynctests folder )

Can one of the admins verify this patch?


Operator Min is missing?

I found the operator Max : https://caffe2.ai/docs/operators-catalogue.html#max
but not the operator Min, is it missing? Thanks!

It was added ! https://github.com/caffe2/caffe2/commit/8c7d1bd9c24a1d3f1554563df5ed502177a2ff1b#diff-466a478e6c6e70d96253a4f76441a555
It would have been nice to update this ticket for notice.

Our operator catalog was updated recently and I missed this issue. Thanks for closing.


Clarify help message for --time option

Inspired by a confused user on Reddit

Accidentally created in my own repo


Do not mention issues with "not-a-bug" label in release notes

I think it is potentially confusing for the release notes to contain not-a-bug labeled issues.
E.g.: https://github.com/zalando/logbook/releases/tag/3.7.0 contains https://github.com/zalando/logbook/issues/1512 and https://github.com/zalando/logbook/issues/1513
These issues have not relation to the release so I think it would be better if there were not mentioned in the release notes.
What do you think?
By the way: Thank you very much for Logbook!

I've updated the last release. We need to start labeling the bug issues, that are not bugs, with invalid or wontfix before closing them. Release script will filter them out. I'll close the issue, as the infrastructure for this is in place, we just need a little bit more discipline around it.
cc @msdousti

Just re-read the text and issues, and looks like we could also add the no-a-bug label to the script. I missed that bit initially. Adding it to the script in - https://github.com/zalando/logbook/pull/1704

Thank you very much! :)


export pluginOptions type

Please export type pluginOptions.
I would like to create a nuxt module for your project, but I need the plugin options for typesafe configuring the module.

Maybe exporting CreateDialogOptions, CreateNotifyOptions and CreateBottomSheetOptions also would helpful for later use.

Done in 1.3.2, upgrade your package.json to include this new version 😉

Thanx, nuxt module is ready: @gabortorma/nuxt-vuetify3-dialog

Nice, I will add it on the README.md soon 😉


Fix issue #22

fix #22

Codecov Report

Merging #23 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           master     #23   +/-   ##
======================================
  Coverage    24.4%   24.4%
======================================
  Files          74      74
  Lines        1168    1168
  Branches      105     105
======================================
  Hits          285     285
  Misses        811     811
  Partials       72      72

Impacted Files
Coverage Δ

src/GitLabApiClient/MergeRequestsClient.cs
34.78% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Lucene5 implementation for querydsl

This is the lucene5 implementation based on a copy of lucene4. Tests are working, no new test added.

Thanks for the pull request, I added some comments that came to my mind.
Sorry that I took a little long.

@johnktims @Shredder121 I have nothing to add to this. Is this good to merge for you?

@Fneuch Could you rebase the commits to master?

Sorry, I was on vacation ...

No problem ;)


SNOW-1513909: transaction statements are not working as exepcted

Please answer these questions before submitting your issue. Thanks!

What version of Python are you using?
3.11

What operating system and processor architecture are you using?
Snowflake's Python Worksheets

What are the component versions in the environment (pip freeze)?
snowflake-snowpark-python==1.15.0

What did you do?
 session.sql("begin").collect()
 session.sql("INSERT INTO TEST(ID,NAME)VALUES('ccc','ddd')").collect()
 session.sql("commit").collect()

This statments are executed successfully in 1.14.0, and failed from 1.15.0 to 1.19.0

What did you expect to see?
Transaction statements should executed successfully. In the query histroy, I found that "begin" and "commit" are executed twice, first is success, second is failed.

Can you set logging to DEBUG and collect the logs?

Yes

Hello @AidenPTHuang ,
Thanks for raising the issue, we are looking into it, will update.
Regards,
Sujan

Hello @AidenPTHuang ,
I just checked with Snowpark python connector version 1.16.0 and transaction is working fine without any error, the begin and commit statements are executing only once as per the application logic
Attaching the screenshot for your reference where I executed it twice, so two times you can see begin and commit
session.sql("begin").collect()
session.sql("INSERT INTO MYCSVTABLE1(SEQ,LAST_NAME,FIRST_NAME)VALUES(9191,'QQQQ','RRRR')").collect()
session.sql("commit").collect()

Regards,
Sujan

Hi @sfc-gh-sghosh
My application is simple:

This application only works in 1.14.0.

But failed since 1.15.0 ~ latest
Any ideas?

issue not resolved

Hello @AidenPTHuang ,
I checked even with latest Snowpark python connector 1.19.0, its working as expected. There is no double commit etc.
Please use latest Snowpark python connector 1.19.0

Regards,
Sujan


Undefined symbols for architecture arm64:   "_MTLCreateSystemDefaultDevice"

OS Platform and Distribution
MacOS 13.6
Compiler version
No response
Programming Language and version
Python 3.11.5
Installed using virtualenv? pip? Conda?(if python)
No response
MediaPipe version
0.10.7
Bazel version
6.3.2
XCode and Tulsi versions (if iOS)
XCode 15.0
Android SDK and NDK versions (if android)
No response
Android AAR (if android)
None
OpenCV version (if running on desktop)
No response
Describe the problem
I'm trying to follow this tutorial https://developers.google.com/mediapipe/framework/getting_started/hello_world_ios
And to the build step, I run the command line
sudo bazel build -c opt --config=ios_arm64 mediapipe/examples/ios/HelloNewWorld/HelloWorld:HelloWorldApp
and it's failed with error Undefined symbols for architecture arm64
My BUILD file content:
MIN_IOS_VERSION = "12.0"

load(
    "@build_bazel_rules_apple//apple:ios.bzl",
    "ios_application",
)

load(
    "//mediapipe/examples/ios:bundle_id.bzl",
    "BUNDLE_ID_PREFIX",
    "example_provisioning",
)

ios_application(
    name = "HelloWorldApp",
    bundle_id = "trunghvbk.mediapipe.sample",
    families = [
        "iphone",
        "ipad",
    ],
    infoplists = ["Info.plist"],
    minimum_os_version = MIN_IOS_VERSION,
    provisioning_profile = example_provisioning(),
    deps = [":HelloWorldAppLibrary"],
)

objc_library(
    name = "HelloWorldAppLibrary",
    srcs = [
        "AppDelegate.m",
        "ViewController.m",
        "main.m",
    ],
    hdrs = [
        "AppDelegate.h",
        "ViewController.h",
    ],
    data = [
        "Base.lproj/LaunchScreen.storyboard",
        "Base.lproj/Main.storyboard",
    ],
    sdk_frameworks = [
        "UIKit",
        "AVFoundation",
        "CoreGraphics",
        "CoreMedia",
    ],
    deps = [
        "//mediapipe/objc:mediapipe_framework_ios",
        "//mediapipe/objc:mediapipe_input_sources_ios",
        "//mediapipe/objc:mediapipe_layer_renderer",
    ],
)

Complete Logs

Undefined symbols for architecture arm64:
  "_MTLCreateSystemDefaultDevice", referenced from:
      -[MPPMetalSharedResources mtlDevice] in libmetal_shared_resources.a(metal_shared_resources.o)
ld: symbol(s) not found for architecture arm64

Solved this error by adding this dependence into the deps array:
deps = [
        "//mediapipe/objc:mediapipe_framework_ios",
        "//mediapipe/objc:mediapipe_input_sources_ios",
        "//mediapipe/objc:mediapipe_layer_renderer",
        "//third_party/apple_frameworks:Metal",
        ]

Please update the document guide, because it's difficult for beginners to find the solution.
Thanks.


[W6.2][F09-B4] Liu Hang

@liuhang0213 Accepting this PR with minimal review. Do try out SceneBuilder and (optionally) ScenicView :p


Keystore and password security considerations

This issue can be used to discuss potential solutions to improving the security of how we currently manage keystore and password files.
At the moment, the Lodestar VC creates two folders the keystores folder which contains encrypted BLS12-381 private keys and the secrets folder which contains the plain text passwords to decrypt the keystores. This setup does not provide any additional security for the private keys in the keystores as the encryption keys are stored on the same device and even the same folder in most cases.  The described setup relies on the file system access to be secure which is sufficient security for most setups but we are not getting any benefits from additionally storing user provided passwords in plain text to just storing the keystore files in an unecrypted format. The main concern here is that leaking the user password can have further consequences as a lot of users reuse passwords which might give an attacker further access to the operating system itself or other services.
In an ideal world, we never want to store the plain text user password, only the first time the user imports a encrypted keystore, the password should be interactively provided through the CLI or keymanager API. While this should be easily possible we still want to be able to restart the VC in case of a reboot without human interaction.
Possible solutions to this problem

store password files on a different device then encrypted keystores and only mount drive if required, we would still store the password but at least get benefits from encrypted the keystores as an attacker would need access to multiple devices
use a remote signer/key manager, this solution already exists and seems to be a good option to improve security

Both those options are not really something we can influence on Lodestar directly as 1. requires an advanced server setup and might not be suitable for most users and option 2. requires to use another software component such as web3signer.
Looking forward to further ideas and suggestions on potential solutions we could directly implement in Lodestar itself.

It's not related to Etherem or Cryoto, it's a general philosophical pointer. Once must keep balance between security and usability. One should not make a system so secure that it's no more useable. Same applies to context here.
We want to secure the validator keys but on the same time we knew the softwares can crash and need to restart. And validators would not be bothered to provide password for 100s keys each time that happens.
Other common approach people mostly used for such scenarios is to use ENV variables instead of files. Based on my experience, that approach is less secure. If an system access is compromised that an attacker accessed to file system, he must already have access to shell and so all env variables. Additionally permissions to the file system can be restricted, but every program running on system have access to system wide env variables.

It's not related to Etherem or Cryoto, it's a general philosophical pointer. Once must keep balance between security and usability. One should not make a system so secure that it's no more useable. Same applies to context here.

that's definitely true, however my main concern is that we store a user provided password in plain text, if this was a machine generated password it would be a different story

Other common approach people mostly used for such scenarios is to use ENV variables instead of files. Based on my experience, that approach is less secure.

can't agree more here, using ENV variables is strictly worse in terms of security whether it is in a containerized environment like kubernetes in the cloud or on a bare metal server

store password files on a different device then encrypted keystores and only mount drive if required, we would still store the password but at least get benefits from encrypted the keystores as an attacker would need access to multiple devices

This can be done with our current implementation (and is the intention behind storing the secrets separately from the keystores), though this usage pattern isn't spelled out anywhere in the user docs.

We must support storing plain text secrets since that's expected by many types of users. If storing plain text secrets is not acceptable to an operator of Lodestar, use stdin to provide the passwords or the web3signer

To summarize

Security-conscious operators have the option to mount the secrets to an external drive which is kept offline and only mounted if required, e.g. on server reboot or restart of VC.
It is also possible to use  an external signer such as  web3signer which supports more advanced storage options such as using vault.
Use stdin to provide the passwords instead of providing from password file.


Fixed 0.4 problems

In 0.4 symbols are prefixed with module names when converted to strings. This caused the data files to not be found.

Thanks!


lang: Parse instruction doc comments into description fields in IDL

Adds description into IDL for instructions from doc comments. Do we want this for things apart from instructions?
Feature gated and off by default (maybe should be opt out rather than opt in to help discoverability?).
Closes https://github.com/project-serum/anchor/issues/373

I realized that you save doc comments into idl descriptions.
Then can we see them in IDL file? or just only save comments into description variable?
If the latter is right, what is the purpose of this feature?

Nice feature.

Closing in favour of #1561


Safely delete entry from listing cache

Fixes #239.
@TomAugspurger I'm guessing you'd probably want to do something similar in intake/filesystem_spec#216.

Thanks, merging.
I suspect if we really want to make this threadsafe we'll have to change how we handle cached state quite a bit, right?


[Feature Request]: Main Menu Music Player

Is there an existing issue for the feature?

[X] I have searched the existing feature requests

Describe the Feature
Currently, the main menu has no music. It would be nice if it could be used as a jukebox of sorts, kind of like how osu! does it. Could use packs as a playlist of sorts or have a shuffle function to shuffle music from every pack.
How Does The Feature Add To The Game?
Since a lot of players have close to 100gb of music, it would be nice to be able to use the game as a music player of sorts. It would also allow players to potentially discover some songs they've never played before but enjoy and decide to play.
Additional Context
No response

The Rebirth Theme has this and its awesome. If possible id like to see it in Til' Death aswell.

3a85e9ff1bc33b162d6db6be0666e6889635457a


HACKTOBERFEST (added new book in search engine)

hacktoberfest2022
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Only free books (legally) are allowed


Login errors

Depends on #17
Closes #16
Just auto-reloading for now rather than showing a button to click.

@chapmanio we should also add a way to indicate that the email address is wrong


Log/Serial functionality

Is there any function to store data from the MicroBit as a CSV file? Such as Data Logging

If you have a micro:bit v2 and you have flashed on it the latest firmware, then you should be able to use the native Data Logging functionalities (the one for which you posted the link). IntelliSense might not be there, but the code will work. For a similar case, please refer to this past issue.

With version 0.1.30 the firmware uploaded to the micro:bit is the latest version, so including the Log functionality. Hope it helps.


Version Dependency 0.6.0

Failed to use "redix" (version 0.6.0) because
  redix_pubsub (version 0.3.0) requires ~> 0.5.2

Please merge https://github.com/whatyouhide/redix_pubsub/pulls

Closed by #10.


why not set g_reg_file.ipsr.cip = 1; after generate_interrupt?

If the conditions to set that bit are still present (See <<IPSR_FIELDS>>) or if they occur after the bit is cleared then that
bit transitions again from 0->1.
https://github.com/riscv-non-isa/riscv-iommu/blob/main/iommu_ref_model/libiommu/src/iommu_reg.c#L505C1-L515C14
            if ( ipsr_temp.cip == 1 )
                g_reg_file.ipsr.cip = 0;
            if ( ipsr_temp.cip == 1 ) {
                if ( (g_reg_file.cqcsr.cmd_to ||
                      g_reg_file.cqcsr.cmd_ill ||
                      g_reg_file.cqcsr.cqmf ||
                      g_reg_file.cqcsr.fence_w_ip) &&
                     (g_reg_file.cqcsr.cie == 1) ) {
                    generate_interrupt(COMMAND_QUEUE);
                }
            }

it seems that   generate_interrupt(COMMAND_QUEUE);  lack a g_reg_file.ipsr.cip = 1 ?

it seems that  generate_interrupt(COMMAND_QUEUE); lack a g_reg_file.ipsr.cip = 1 ?

See here.


Could not open +page.svelte in the editor

Describe the bug
Randomly started getting this error on my Svelte projects recently when using the code inspector to open up files. Have no idea how to resolve. It only affects files with special characters in the name.

Could not open +page.svelte in the editor.
When running on Windows, file names are checked against a safe file name pattern to protect against remote code execution attacks. File names may consist only of alphanumeric characters (all languages), periods, dashes, slashes, and underscores.

Reproduction URL
https://github.com/sveltejs/vite-plugin-svelte/issues/new
Reproduction
Sorry, do not know how to replicate. Looking for advice on how to fix.
Logs
No response
System Info
Windows 11, VS Code, Tested with Brave and Edge

caused by https://github.com/yyx990803/launch-editor/commit/5366f3ee3addc9ea014088c254db6398f788fbff
launch-editor tries to protect from malicious filenames, not sure if + is a dangerous char on windoes or just too rigid check

fix could take a bit as launch-editor is bundled it vite

The linked change was included in vite 5.3.2

and how to fix this now? I got most recent versions and still get this error.

this needs a change in launch-editor first and then vite has to update the bundled version and release that.

As a temporary fix force vite to be version 5.3.1 in your package.json:
"devDependencies": { 	"vite": "5.3.1" }, "overrides": {     "@sveltejs/vite-plugin-svelte": { 	"vite": "5.3.1"     } }

please don't use partial overrides. If svelte-inspector on +page.svelte files is that important to you, go back to vite 5.3.1 entirely to ensure that you are using one consistent version.

the fix for this is going to be included in the next release of vite

Still doesn't work for me with  "vite": "^5.4.0",

Still doesn't work for me with  "vite": "^5.4.0",

can you provide more info here? the fix was pretty straight forward and another windows user just reported it working with 5.4.
can you open files that do not contain a + in their name? Which windows shell and ide versions?

Yes, I can open files that dont contain a +. Components for example.
My vscode version is 1.92.0 and I am running powershell

Does your username or the project directory contain any other special characters?

This is the path to one of my pages. Closest character to a special character is the underscore.

oof, [] and () are problems tooo i guess

can confirm this is still an issue with vite 5.4.2
Could not open Title.svelte in the editor.

When running on Windows, file names are checked against a safe file name pattern
to protect against remote code execution attacks. File names may consist only of
alphanumeric characters (all languages), periods, dashes, slashes, and underscores.

Referencing
issue: https://github.com/yyx990803/launch-editor/issues/50
pull: https://github.com/yyx990803/launch-editor/issues/50
commit: https://github.com/yyx990803/launch-editor/commit/5366f3ee3addc9ea014088c254db6398f788fbff

Happening for me on Win10 as well, after update to latest version of SvelteKit 2.
Only seems to happen when inspecting elements on routes (+page.svelte), but not components. I'm guessing '+' is not on the aforementioned safe file name pattern.

Any updates on this?

latest version of launch-editor and vite should have this fixed. if you still experience files that do not open please share their full path (skip your user dir for privacy if you prefer but mention if it has any special chars)

latest version of launch-editor and vite should have this fixed. if you still experience files that do not open please share their full path (skip your user dir for privacy if you prefer but mention if it has any special chars)

So I am running VSCode 1.94.0 and vite 5.4.8. Maybe its the underscore in my repo name?

Can confirm, issue has not been fixed at all for Svelte 4.

Also does not work at all in Svelte 5.

Actually a simple test project does work. However I tested this path from an actual production project and it fails:
C:\Users\loic.joachim\Documents\GitHub\nodejs-external\src\routes\portal\(orders)\ordermanagement\+page.svelte
Presumably because of the -

The fix is in launch-editor 2.9.1 which has been merged into vite main branch (6.0 beta) but not backported to 5.4 branch yet, sorry. still needs to wait a bit

please try again with vite 5.4.9

please try again with vite 5.4.9

Yes it works now, thanks


Make keyboard input event order consistent

All platforms should now receive events in the following order:

KeyboardInput(ElementState::Pressed, ..)
ReceivedCharacter
KeyboardInput(ElementState::Released, ..)

cc https://github.com/tomaka/glutin/issues/878

This updates X11 and Cocoa event orderings to match Win32. I don't have the means to test Wayland so I did not look into it.

Thanks

FTR, Wayland was already following this order, see https://github.com/tomaka/winit/blob/master/src/platform/linux/wayland/keyboard.rs#L41-L64

Thanks for the follow-up @vberger. With that, I think we can safely say all desktop platforms follow the same keyboard input event ordering.
@tomaka How do you feel about advertising this guarantee in the docs?

I'm still unsure if this is the right API or not, but I guess why not.


Can't save a legacy project cut and pasted from a different legacy file

Error: Bad Request
Error: Bad Request
    at Request.<anonymous> (https://homebrewery.naturalcrit.com/homebrew/bundle.js:71842:19)
    at Request.Emitter.emit (https://homebrewery.naturalcrit.com/homebrew/bundle.js:1768:20)
    at XMLHttpRequest.xhr.onreadystatechange (https://homebrewery.naturalcrit.com/homebrew/bundle.js:72151:10)
{
  "status": 400,
  "method": "POST",
  "url": "/api/newGoogle/"
}

Checkout discussion #1580. Those steps should clear up the issue

Does that method work if I've never logged in with Google before? Moreover, how would I, say, go about logging out? There's nothing on the My Brews page, nor the main page or the Natural Crit site itself. Should I delete my cookies and try logging in with Google?

@Teddy-Maz The fact that the error shows "url": "/api/newGoogle/" is evidence that the Homebrewery has a Google Drive account linked with your username.

Moreover, how would I, say, go about logging out?
Check out discussion #1580 for how to log out

@Teddy-Maz -- did #1580 get this resolved for you?   Going to close this issue for now and assume so, but if not we can definitely reopen it and see what else needs to be done.


RuntimeError: output with shape [1, 28, 28] doesn't match the broadcast shape [3, 28, 28]

When I run your code, I have met a error when executing data_source = data_source_iter.next():
RuntimeError: output with shape [1, 28, 28] doesn't match the broadcast shape [3, 28, 28].
I have no idea why this error occurs. Could you please give some suggestions.
Besides, I'm using Python3.6 and Pytorch 1.0. My operating system is Ubuntu 16.04. Thanks.

I have not tested it on pytorch 1.0 yet, but I have transfrom the gray images into 3 channels, can you post the complete errors here?

I have not tested it on pytorch 1.0 yet, but I have transfrom the gray images into 3 channels, can you post the complete errors here?

But there is no error on Windows10 with the same version of pytorch.

I've no idea about it, and I'll test it with pytorch 1.0 on Ubuntu soon.

Traceback (most recent call last):
File "/home/hou/桌面/DANN-master/train/main.py", line 98, in
data_source = data_source_iter.next()
File "/home/hou/anaconda3/envs/py36/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 637, in next
return self._process_next_batch(batch)
File "/home/hou/anaconda3/envs/py36/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 658, in process_next_batch
raise batch.exc_type(batch.exc_msg)
RuntimeError: Traceback (most recent call last):
File "/home/hou/anaconda3/envs/py36/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 138, in worker_loop
samples = collate_fn([dataset[i] for i in batch_indices])
File "/home/hou/anaconda3/envs/py36/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 138, in
samples = collate_fn([dataset[i] for i in batch_indices])
File "/home/hou/anaconda3/envs/py36/lib/python3.6/site-packages/torchvision/datasets/mnist.py", line 95, in getitem
img = self.transform(img)
File "/home/hou/anaconda3/envs/py36/lib/python3.6/site-packages/torchvision/transforms/transforms.py", line 60, in call
img = t(img)
File "/home/hou/anaconda3/envs/py36/lib/python3.6/site-packages/torchvision/transforms/transforms.py", line 163, in call
return F.normalize(tensor, self.mean, self.std, self.inplace)
File "/home/hou/anaconda3/envs/py36/lib/python3.6/site-packages/torchvision/transforms/functional.py", line 208, in normalize
tensor.sub(mean[:, None, None]).div(std[:, None, None])
RuntimeError: output with shape [1, 28, 28] doesn't match the broadcast shape [3, 28, 28]

This is the complete error info. It seems wrong about dataloader

I guess something wrong here, some images are not converted to 3 channels as rgb.

Yes, I agree with you. But I have no idea about why it dosen't work.

I built these codes on pytorch 0.4.0, python 2.7,  ubuntu 16.04, this could make any difference? I will test it soon.

Maybe it is not. According to the error ondo, there is a error about the source data loader, which is implementwd by in-place function. Therefore, Ithink this error is not caused by convertion.

This error was caused by the shape mismatch between the tensor and self.mean in F.normalize,  which tensor was [1,28,28] and self.mean was [0.5, 0.5, 0.5], so the shape of self.mean implied that the tensor should be [3, *, *], instead of [1, *, *]. So I think there is something wrong with this input tensor.

mnist dataset consists of grey images which are 1 channel. Thus the input tensor is [1, *, *]. Indeed, you have implemented the self-defined loader GetLoader where you convert the input images to RGB. But this loader is used to load mnist_m dataset rather than mnist dataset. Therefore, there is nothing to do with mnist dataset. And input tensor of mnist is still [1,  *, *].

Ooooooh, finally, I run the code successfully. I add a new transform like this
img_transform1 = transforms.Compose([
    transforms.Resize(image_size),
    transforms.ToTensor(),
    transforms.Lambda(lambda x: x.repeat(3,1,1)),
    transforms.Normalize(mean=(0.5, 0.5, 0.5), std=(0.5, 0.5, 0.5))
])

And  I replace the original transform of source data mnist with img_transform1.  By do so, the mnist images can be converted to [3, *, *] tensors. I am curious about why the code is OK under your settings.
In my opinion, is there a difference about torchvision.datasets.MNIST() function between torch 0.4 and torch 1.0???

Yes, you're right, input tensor of mnist is still [1, *, *]. The problem comes https://github.com/pytorch/vision/commit/21153802a3086558e9385788956b0f2808b50e51#diff-fc1f220b470714d05cf3ea6acf9fed59L204, where it used zip to return iterable object before, and If multiple iterables are passed, iterator stops when shortest iterable is exhaused, I think this is the reason that it ran well in my settings. After the zip was replaced by broadcasting, my codes failed because of shape mismatch.  I will fix it soon, thank you.

add transforms.CenterCrop(), after  transforms.Resize .
# load data
transform = transforms.Compose([
    transforms.Resize(224),
    transforms.CenterCrop(224),
    transforms.ToTensor(),
    transforms.Normalize(mean=(0.5, 0.5, 0.5), std=(0.5, 0.5, 0.5)),
])

Let me clarify, if the img has three channels, you should have three number for mean, for example, img is RGB, mean is [0.5, 0.5, 0.5], the normalize result is Rx0.5, Gx0.5, Bx0.5. If img is grey type that only one channel, so mean should be [0.5], the normalize result is R*0.5

Ooooooh, finally, I run the code successfully. I add a new transform like this
img_transform1 = transforms.Compose([
    transforms.Resize(image_size),
    transforms.ToTensor(),
    transforms.Lambda(lambda x: x.repeat(3,1,1)),
    transforms.Normalize(mean=(0.5, 0.5, 0.5), std=(0.5, 0.5, 0.5))
])

And I replace the original transform of source data mnist with img_transform1. By do so, the mnist images can be converted to [3, *, *] tensors. I am curious about why the code is OK under your settings.
In my opinion, is there a difference about torchvision.datasets.MNIST() function between torch 0.4 and torch 1.0???

transforms.Lambda(lambda x: x.repeat(3,1,1)),
transforms.Normalize(mean=(0.5, 0.5, 0.5), std=(0.5, 0.5, 0.5))

I received the fault , Can't pickle local object 'get_data_loaders..'.

@ShuuTsubaki try new code under pytorch 1.0

what should be the image_size in above code? I have image of 28x28.
When i set image size to 784, i get the following error.

RuntimeError: size mismatch, m1: [128 x 1843968], m2: [784 x 128] at /opt/conda/conda-bld/pytorch_1556653099582/work/aten/src/TH/generic/THTensorMath.cpp:961

@priteshgohil image_size = 28

Downgrading torch and torchvision to 0.2.0 and 0.2.1 solved this issue for me.

Downgrading torch and torchvision to 0.2.0 and 0.2.1 solved this issue for me.

Thanks So lot ! It helps me! BTW , Mine is  pytorch 1.1.0 + win10 , work with torchvision 0.2.0

I'm working on Ubuntu 16.04 version and using torch version 1.3.1
It's that MNIST data set consists of grey images.
transform = transforms.Compose([     transforms.ToTensor(),     transforms.Normalize(mean=(0.5, 0.5, 0.5), std=(0.5, 0.5, 0.5)), ])
can be changed to
transform = transforms.Compose([transforms.ToTensor(), transforms.Normalize((0.5,), (0.5,))])

I'm working on Ubuntu 16.04 version and using torch version 1.3.1
It's that MNIST data set consists of grey images.
transform = transforms.Compose([ transforms.ToTensor(), transforms.Normalize(mean=(0.5, 0.5, 0.5), std=(0.5, 0.5, 0.5)), ])
can be changed to
transform = transforms.Compose([transforms.ToTensor(), transforms.Normalize((0.5,), (0.5,))])

img_transform = transforms.Compose([
transforms.ToTensor(),
transforms.Normalize([0.5], [0.5])
])
dataset = MNIST('./data', transform=img_transform)


fix docs bugs：docs\api\paddle\nn\RNN_cn.rst

文档修复：
涉及API为 paddle.nn.RNN文档修复：
涉及API为 paddle.nn.RNN

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


The columns order is incorrect after executing 'Reorder Columns Based on Schema' for one entity which has a non-empty custom property

Storage Explorer Version: 1.29.0
Build Number: 20230424.2
Branch: rel/1.29.0
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Ventura 13.3.1 (Apple M1 Pro)
Architecture: ia32/x64/arm64
How Found: ad-hoc testing
Regression From: Previous release (1.28.1)
Steps to Reproduce

Expand a storage account -> Tables.
Create a table -> Add one entity with a custom property.
Right click the entity -> Click 'Reorder Columns Based on Schema'.
Check whether the columns order is correct.

Expected Experience
The columns order is correct.

Actual Experience
The columns order is incorrect.

@craxal Thanks for the response! One issue needs your confirmation.
If I reorder one custom property column, then click 'Add'. The Add Entity dialog as below.
This issue doesn't reproduces for Edit/Duplicate entity.
Do we need to pay attention to this?

No, you don't need to pay attention to that. Though, we'll look into it.


Add separate target for building the db migrator

new build target:
npm run build-migrator
or
gulp build-migrator
This target only builds the db migrator tool

LGTM


Add Chain Builder

⚠ Depends on https://github.com/5afe/safe-client-gateway-nest/pull/202

Adds ChainBuilder in order to build Chain entities without relying on the parameter order of the factory function

Coverage remained the same at 81.913% when pulling dfa47c7c6864eaf914419b48467139de928beca7 on add-chain-builder into 670300b7b784e832c6823e89a12df7c0ea34cc08 on replace-undefined-with-null.


feat: emit changed flags in configuration change event

Adds changed flags to in-process change event.
Fixes: https://github.com/open-feature/java-sdk-contrib/issues/901

@aepfli have implemented changes please help with re-review

@UtkarshSharma2612 I squashed all your changes, and made a few small changes in this commit:

added the changed flags to RPC mode as well (this was just a couple of lines, with the work you already did it was very easy)
added a new assertion in the e2e test suite which was previously not implemented because we didn't support flagsChanged
some minor checkstyle and spotbugs fixes

Really great work! Thanks for doing all the heavy lifting here!

Thank you, @toddbaert! I really enjoyed working on this issue and learned a lot in the process. Are there any other open issues I could contribute to? I'd love to continue helping out. 😄  If there’s anything, please let me know!

@UtkarshSharma2612 I squashed all your changes, and made a few small changes in this commit:

added the changed flags to RPC mode as well (this was just a couple of lines, with the work you already did it was very easy)
added a new assertion in the e2e test suite which was previously not implemented because we didn't support flagsChanged
some minor checkstyle and spotbugs fixes

Really great work! Thanks for doing all the heavy lifting here!

Thank you, @toddbaert! I really enjoyed working on this issue and learned a lot in the process. Are there any other open issues I could contribute to? I'd love to continue helping out. 😄

@UtkarshSharma2612 I'm sure there is.
I will also invite you to the org, which is the first step to getting more involved.

@UtkarshSharma2612 I squashed all your changes, and made a few small changes in this commit:

added the changed flags to RPC mode as well (this was just a couple of lines, with the work you already did it was very easy)
added a new assertion in the e2e test suite which was previously not implemented because we didn't support flagsChanged
some minor checkstyle and spotbugs fixes

Really great work! Thanks for doing all the heavy lifting here!

Thank you, @toddbaert! I really enjoyed working on this issue and learned a lot in the process. Are there any other open issues I could contribute to? I'd love to continue helping out. 😄

@UtkarshSharma2612 I'm sure there is. I'll let you know.
I will also invite you to the org, which is the first step to getting more involved.

Sure, Thanks!

Hey @UtkarshSharma2612, it was also a pleasure working with you.
As you seem to be interested, today I opened https://github.com/open-feature/java-sdk-contrib/issues/957, which would be a cool improvement for our testing tooling. ;)


modularize loading of iris and mesh models

Issue Description
iris.bin is still loaded when iris is set to false.
Steps to Reproduce
set config
 iris:{
    enabled:false,
...}

Expected Behavior
iris.bin file not loaded
**Environment
Chrome 86, node 14, Mac OS 10
dynamic create script element to load human.
document.createElement('script')

good catch.
face.detector, face.mesh and face.iris are a special case since they work in a single pipeline, they are all loaded together if detector is enabled.
but if face.mesh or face.iris have enabled: false, their execution will be skipped in runtime.
is this a problem? model sizes are really small, (iris is 2.5MB), so it shouldn't hurt load performance.

btw, its not related to the question, but why are you doing this?
document.createElement('script')

btw, its not related to the question, but why are you doing this?
document.createElement('script')

I want to lazy load human. But this project still in angular 6.  no  import('xxx.js') function.
The models is very big for me. can we have a smaller version to fit mobile. Some places don't have fast internet and they don't have the patience to wait.

Regarding network saving, did you look at serving app and models with brotli or gzip support?
That's what server/dev/js does internally as well and saving is quite significant.
And for any subsequent loads, I normally prefer to cache everything client side in local storage using service worker.
That's not implemented in this demo, but you can take a look at https://github.com/vladmandic/pigallery/blob/master/client/index/pwa-serviceworker.js and https://github.com/vladmandic/pigallery/blob/master/client/index/pwa-register.js for example.
That way, load is only slow first time user loads the app and it's nearly instant later.
But yes, I can modularize iris and mesh models as well.

I've modularized face iris & mesh and hand skeleton models.
The side-effect is that they cannot be dynamically disabled/enabled like all other models once first load has completed, you need to manually unload the model so the pipeline can be reinitialized.
For example, if config.face.iris.enabled = false, iris model will not be loaded.
But to enable it in runtime, you need to reset the face pipeline since models that are part of the pipeline cannot be easily added to existing pipeline:
  myConfig.face.iris.enabled = false // start with iris model disabled
  await human.load(myConfig)
  const res = await human.detect(input, myConfig)

  human.models.facemesh = null // this unloads face pipeline
  myConfig.face.iris.enabled = true // enable iris model
  await human.load(myConfig)
  const res = await human.detect(input, myConfig)

Implemented via https://github.com/vladmandic/human/commit/c688254269846aaf8f21af6c843bedc04c2d07d3
Please verify before issue can be closed.

closing as resolved.

Thanks

iris: { enabled: false }, still results in log: ["14:40:08.328","Human:","load model:","./human/models/iris.json"] which as described can be problematic for mobile pages.

@Utopiah, I don't see your entire configuration, but it's face.iris.enabled, not just iris.enabled
I just tried with
  face: { enabled: true,
    detector: { return: true },
    mesh: { enabled: true },
    iris: { enabled: false },
    description: { enabled: false },
    emotion: { enabled: false },
  },

And messages are correct:
09:07:00.679 Human: load model: ../models/blazeface.json
09:07:00.750 Human: load model: ../models/facemesh.json
09:07:00.750 Human: tf engine state: 3501876 bytes 231 tensors

Currently using
const config = {
        backend: 'webgl',
        modelBasePath: './human/models/',
        gesture: { enabled: false },
        body: { enabled: false },
        hand: { enabled: false },
        iris: { enabled: false }, // still loaded but only 2.5Mb
        profile: { enabled: false },
};

but if I add face: { iris: { enabled: false } } I get indeed what I expected.
I now see my mistake, looking at the full configuration I didn't see that iris was part of face. Thanks for the clarification.


Option: skip analysis

Implement option to skip one or multiple steps of the workflow.

Implemented boolean flags to skip individual steps such as QC  etc.


Mnist Dataset classification

Issue Title : Mnist Dataset classification

Info about the related issue (Aim of the project)

[x] SWOC Participant

[x] Contributor

Closes: #6
Describe the add-ons or changes you've made
I have created a machine learning project for image classification using MNIST dataset. I have compared 3 different models and accuracies.
How Has This Been Tested?
I have created the jupyter notebook and trained each model myself.
Checklist:

[x ] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

ok

actually i wanted to ask like do i keep the .vscode and .ipynb_checkpoints file or should i delete them

Then no need to put the Images folder @yagyesh-bobde

did the changes ..... PTAL

@yagyesh-bobde Some changes need to be done.

@yagyesh-bobde Congratulations on your first contribution to this project 🎉


Enable Keyboard Shortcuts for Audiobook Controls

Description: Improve accessibility by adding keyboard shortcuts for audiobook controls (e.g., play/pause, skip, volume control).
Tasks:
Implement JavaScript logic to detect keyboard inputs for controlling the audiobook player.
Map keyboard shortcuts to common actions (e.g., spacebar to play/pause, arrow keys to skip, etc.).
Ensure compatibility with all browsers.
Acceptance Criteria:
Users can control the audiobook player using keyboard shortcuts.
The shortcuts are intuitive and work across all browsers.
A help section is added to inform users about the available shortcuts.

Hey @Ctoic
I already did it

okay @YakeDev


Filtergroups

If there are filters in different filtergroups, are all filters copied? to the same filtergroup?

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

ID: a18136a6-a183-2e19-5419-8850e3704333
Version Independent ID: 85de3bc7-adfc-22e4-05e0-ee7e0dab0dac
Content: COPYFILTERS Function (Record) - Dynamics NAV
Content Source: dynamics-nav/COPYFILTERS-Function--Record-.md
Product: dynamics-nav-2018
GitHub Login: @jswymer

All filters are copied and remain in their assigned group numbers. I wanted to use this function to copy filters from one group to another but for that it is unsuited. The call
Rec.CopyFilters(FromRec)
disregards the current FilterGroup on both Rec and FromRec, and copies all filters in FromRec (regardless of group number) into the same Filter Group assignments on Rec.


require title and page-range fields to be filled out.

2015-01-13-Tue mtng requirement.

implemented in commit https://github.com/Brown-University-Library/easyscan/commit/1c070d228e1009c353ef6567a88fd7c215419374.


inDoc(node, win) causes Uncaught SecurityError

Vue.js version
1.0.23
Steps to reproduce
I embed a youtube link via jwplayer. The jwplayer is instantiated via a

When certain manipluations via vue.js happen I get the error

JS ERROR: Uncaught SecurityError: Blocked a frame with origin "https://...." from accessing a cross-origin frame. .... Error: Blocked a frame with origin "https://...." from accessing a cross-origin frame.

From there on vue.js does not function properly.
What is Expected?
vue.js should not interfere with the iframe that is embedded via jwplayer.
What is actually happening?
The exception seems to happen here:
`
/**
* Check if a node is in the document.
* Note: document.documentElement.contains should work here
* but always returns false for comment nodes in phantomjs,
* making unit tests difficult. This is fixed by doing the
* contains() check on the node's parentNode instead of
* the node itself.
*
* @param {Node} node
* @return {Boolean}
*/
function inDoc(node, win) {
	win = win || window;
	var doc = win.document.documentElement;
	var parent = node && node.parentNode;
	var isInDoc = doc === node || doc === parent || !!(parent && parent.nodeType === 1 && doc.contains(parent));
	if (!isInDoc) {
		var frames = win.frames;
		if (frames) {
			for (var i = 0; i < frames.length; i++) {
				if (inDoc(node, frames[i])) {
					return true;
				}
			}
		}
	}
	return isInDoc;
}`

In the line:
var doc = win.document.documentElement;

This has been fixed in 1.0.24: https://github.com/vuejs/vue/releases/tag/v1.0.24


Feature Request: Format CDS Views

Espacially
Case Statements

Doesn't CDS already have its own configurable pretty printer implementation in the base ADT installation?

have not found any settings for "Case" statements. And the goal for the abap cleaner is to be better than the "pretty printer" so why not add cds?

As far as I am aware the CDS pretty printer is implemented client side in ADT (i. e. in Java). Therefore it should already be independant of the backend release lifecycle and be extensible. Though of course I am all for it being open sourced as well :P
I also couldn't find any settings specific to case statements. Just for reference:

Hi Björn,
thanks for the idea – however, I'm afraid this is out of scope for ABAP cleaner, at least for the foreseeable future, because the tool was designed with (esp. object-oriented) ABAP in mind.
Kind regards,
Jörg-Michael

Too bad that this is out of scope.
It would be great, especially for the annotations. Such a pain in the arse:)

Hi @BjoernTheDev and @kaisicker,
as you maybe already noted in the Release Notes for  version 1.19.1, ABAP cleaner now finally supports formatting of CDS views (i.e. Data Definition Language)! Therefore, very glad to remove the "out of scope" label for one of our oldest issues :-)
Formatting of annotations as requested by @kaisicker is already supported by the rules "Standardize annotation layout" and "Rearrange annotations". However, @BjoernTheDev originally asked about CASE statements, for which there is indeed no rule yet (but we're a lot closer now!), therefore reopening this with label "new cleanup rule" :-)
Kind regards,
Jörg-Michael

Thank you so very much!

@jmgrassau thank you so much.😊


[BUILD] Build failed in dev branch for linux/arm64

Build failed in dev branch for linux/arm64 with commit 5ce895fe09a715ab0976814339685283a0177562
#46 322.4 npm ERR! gyp ERR! stack Error: Could not find any Python installation to use

Actions Log<PHONE_NUMBER>5
Probably can be solved by reinstalling python.

docker/getting-started#124

Temporary disable build for arm64 until proper build fixed for arm64 01e70e1645c7eae5b119d9924aab37a0565fc8ae. Will be fixed later.