linux: add fanotify(7) API bindings.

The fanotify API is a Linux-specific API for notification and interception of filesystem events. In some ways it is similar to inotify, but with different advantages/tradeoffs. It is particularly well suited to full filesystem/mount monitoring (vs operating per directory/file like inotify) and for allowing/denying access to files (inotify lacks this capability).
The fanotify API has been updated several times since it was enabled in Linux 2.6.37. Presently I've only included support for the original fanotify features, and the FAN_MARK_FILESYSTEM addition made in Linux 4.20. There are subsequent updates in 5.0 and 5.1 not covered in this initial commit.
This commit adds the relevant constants and types from uapi/linux/fanotify.h and two new functions (fanotify_init (man page) and fanotify_mark (man page)) to src/unix/linux_like/linux/mod.rs. While I believe this API is also present on Android I have presently limited my attention to Linux.
Although this commit focuses on Linux 4.20.x's fanotify API/constants I have skipped adding constants for FAN_ALL_CLASS_BITS, FAN_ALL_INIT_FLAGS, FAN_ALL_MARK_FLAGS, FAN_ALL_EVENTS, FAN_ALL_PERM_EVENTS and FAN_ALL_OUTGOING_EVENTS even though they are present in this kernel version's headers. These defines were deprecated in later releases with instructions to not use them in new programs or extend them with new values. It would be a shame for new Rust programs to use deprecated #defines!
Note to reviewers: I'm very new to Rust and the libc crate. I've tried my best to match project guidelines for contributing but friendly advice/pointers are welcome! I've also tested my work by building some WIP nix wrappers on top of the libc work and porting an example program from the fanotify man page to Rust: https://github.com/cpu/rfanotify. I've had success running this program on Linux 4.4.0, 5.0.0 and 5.5.8
Edit: I also understand this Crate is understaffed. This is a side project and doesn't need immediate attention

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

rust-lang.libc — #20200318.6 failed

Looks like there's some test failures to sort out :sweat:
It seems like like none of the musl jobs passed. That makes sense to me, I only tested with GNU libc. I don't have any experience with musl but it seems like there is support since this commit in 2014. Would folks prefer I pursue supporting musl or would it be best to move the bindings from src/unix/linux_like/linux/mod.rs to src/unix/linux_like/linux/mod.rs to src/unix/linux_like/linux/gnu/mod.rs?
I'm less certain what could be at fault with the other jobs and probably need some assistance to make progress there.

Hey, thanks for the PR! I haven't reviewed deeply yet but I think we should add linux/fanotify.h here:
https://github.com/rust-lang/libc/blob/276eaa2d2f5d85432f0e99c06887529ec02b9bac/libc-test/build.rs#L2224-L2229

I haven't reviewed deeply yet but I think we should add linux/fanotify.h here:

@JohnTitor Thanks for the quick pointer! I've applied this suggestion in 501762b.

@JohnTitor Thanks for the detailed review! I believe I've addressed all of your review feedback and this branch is ready for a second pass when you have a chance.

Great! Now some targets pass CI. I'll take a look at the log after taking a bath but at a glance:

some targets complain re-definition of fanotify_event_metadata and fanotify_response, so we already have them somewhere
i686-unknown-linux-gnu complains that fanotify_event_metadata's align size is wrong, we should tweak it.

Great! Now some targets pass CI

Progress! :tada: Thanks for your help :-)

i686-unknown-linux-gnu complains that fanotify_event_metadata's align size is wrong, we should tweak it.

After some fiddling I got the ci/run-docker.sh script working locally. I was able to fix this target/test failure in my local repro's by adding an #[repr(align(8))] attribute in bdd80b6. If I'm on the wrong track here (or am ignoring a compat. issue with other targets) I can revert the commit.

some targets complain re-definition of fanotify_event_metadata and fanotify_response, so we already have them somewhere

I noticed all of the tasks that failed with this error seem to be using musl and was able to repro locally. That led me to this musl project FAQ entry on this particular compiler error: "Q: Why am I getting “error: redefinition of struct ethhdr/tcphdr/etc”?"
I tried the first possible solution listed and removed the linux/fanotify.h include I added in 501762b (I left sys/fanotify.h).
Re-running the x86_64-unknown-linux-musl test locally showed a different failure at this point:
cargo:warning=/checkout/target/x86_64-unknown-linux-musl/debug/build/libc-test-a1a47ab82627b1bc/out/main.c: In function '__test_fn_fanotify_mark':
cargo:warning=/checkout/target/x86_64-unknown-linux-musl/debug/build/libc-test-a1a47ab82627b1bc/out/main.c:31770:24: error: returning 'int (*)(int,  unsigned int,  long long unsigned int,  int,  const char *)' from a function with incompatible return type 'int (*)(int,  unsigned int,  uint64_t,  int,  const char *)' {aka 'int (*)(int,  unsigned int,  long unsigned int,  int,  const char *)'} [-Werror=incompatible-pointer-types]
cargo:warning=31770 |                 return fanotify_mark;
cargo:warning=      |                        ^~~~~~~~~~~~~

The long long unsigned int vs uint64_t argument mismatch seems like it answers the question you had about whether the fanotify_mark's mask argument needs to be ::c_ulonglong vs u64 :-)
When I reverted 42ac577 and f082b9935022a7635b1a78ddc16bac2cc01566d8 the target's tests passed locally :tada: I'll push the relevant commits to this branch and see how a full CI run goes. :crossed_fingers:

It's also possible I've been barking up the wrong tree :laughing:

Seems like this might have been the case. Other targets that were passing before (e.g. x86_64-unknown-linux-gnu) failed. I'm going to put this branch down for the day and come back with fresh eyes before I make more of a mess :-)

Thanks!

The long long unsigned int vs uint64_t argument mismatch seems like it answers the question you had about whether the fanotify_mark's mask argument needs to be ::c_ulonglong vs u64 :-)

That's fair but some other targets still complain that, hmm it's odd, I'll investigate.

That's fair but some other targets still complain that, hmm it's odd, I'll investigate.

It felt odd to me too. I poked at it a little bit more this morning and using u64 seems to work fine for everything except the musl targets. Using ::c_ulonglong works for musl but breaks on some other targets (64bit glibc) (Which feels strange to me since I thought c_ulonglong was a type def for u64). I haven't found a solution that worked for all targets but I admit to being a neophyte when it comes to C types and portability.

Using ::c_ulonglong works for musl but breaks on some other targets (e.g. 64bit glibc) (Which feels strange to me since I thought c_ulonglong was a type def for u64).

So, I think we can switch u64 with c_ulonglong by adding #[cfg(target_env = "musl")] or #[cfg(not(target_env = "musl"))].

So, I think we can switch u64 with c_ulonglong by adding #[cfg(target_env = "musl")] or #[cfg(not(target_env = "musl"))].

Cool, :+1: I implemented that suggestion in 2eab0f8.
Almost there! It looks like CI is green across the board now with the exception of two tasks:

DockerTierLinux2 sparc64-unknown-linux-gnu

Not sure what's up with this one. I'll try to repro locally and see what I can figure out. I can't see any failed tests in the test output on Azure :thinking:

StyleAndDocs - Check style

I used the cfg attribute directly in 2eab0f8 and it looks like I should prefer cfg_if or splitting things into the gnu and musl modules.
I gave a quick first shot at using cfg_if in the same context I was using cfg and it fails to build: https://gist.github.com/cpu/4280a148aad1619e9b71139b48e6fc8f so I think that's not the right approach.
@JohnTitor Q for you: If I move the pub fn fanotify_mark export with the u64 argument to src/unix/linux_like/linux/gnu/mod.rs and the pub fn fanotify_mark export with the ::c_ulonglong argument to src/unix/linux_like/linux/musl/mod.rs should I leave the common parts (pub fn fanotify_init, etc) in src/unix/linux_like/linux/mod.rs to avoid duplication, or should I remove the common parts from the linux mod and have everything self contained in the musl and gnu subcrates?
Thanks!

should I leave the common parts (pub fn fanotify_init, etc) in src/unix/linux_like/linux/mod.rs to avoid duplication

I decided to try this route in 0bef8ef, happy to adjust if required.

DockerTierLinux2 sparc64-unknown-linux-gnu
Not sure what's up with this one. I'll try to repro locally and see what I can figure out.

Both this and the style check are passing now (locally and in CI) :tada:
Unfortunately there's a handful of new task failures :sweat: Three of them are "BuildChannelsLinux" tasks. There's also one "SemverOSX" failure that looks to be caused by a missing crate. Looking through the failures they all seem unrelated to my fanotify work and I'm not sure how to proceed/fix. Guidance welcome!

Unfortunately there's a handful of new task failures sweat Three of them are "BuildChannelsLinux" tasks. There's also one "SemverOSX" failure that looks to be caused by a missing crate. Looking through the failures they all seem unrelated to my fanotify work and I'm not sure how to proceed/fix. Guidance welcome!

After merging master again the "SemverOSX" failure went away :man_shrugging:
As for the "BuildChannelsLinux" failures I was able to figure out the problem and I was wrong about it being unrelated to the diffs in this branch. The root cause was https://github.com/rust-lang/libc/commit/bdd80b62f39c3ede93685cf7a227625bd4c07571 and my use of the #[repr(align(8))] attribute. This feature requires Rust 1.25+ and so failed the BuildChannelsLinux tasks using Rust 1.13.0, 1.19.0 and 1.24.0. (I found the background in https://github.com/rust-lang/libc/issues/1042 to be useful context).
To continue supporting Rust versions < 1.25 I split the fanotify_event_metadata struct across src/unix/linux_like/linux/align.rs and src/unix/linux_like/linux/no_align.rs in 8b30245. The former keeps the nice #[repr(align(8))] attribute while the latter uses the older __align field style. I think this matches up with how the rest of the crate is operating today.
That did the trick! All green across the board now :fireworks: :checkered_flag:

@JohnTitor This branch is ready for another review pass when you have a chance. Thank you!

As for the "BuildChannelsLinux" failures I was able to figure out the problem and I was wrong about it being unrelated to the diffs in this branch. The root cause was bdd80b6 and my use of the #[repr(align(8))] attribute. This feature requires Rust 1.25+ and so failed the BuildChannelsLinux tasks using Rust 1.13.0, 1.19.0 and 1.24.0. (I found the background in #1042 to be useful context).

That's correct!

After merging master again the "SemverOSX" failure went away

The semver check depends on nightly rustc API and I fix it when noticing usually :)
Okay, finally I'd say "LGTM", the last work is to squash commits since they're verbose a bit to merge as-is.

Okay, finally I'd say "LGTM", the last work is to squash commits since they're verbose a bit to merge as-is.

Great! I squashed all of my work down to one commit: 46b18b8

Thanks for separating commits, it made my reviews easy :)

Glad to hear it :-) Thanks for the reviews!

Ohh, you messed up the branch, try to rebase/squash again?

Ohh, you messed up the branch, try to rebase/squash again?

Drat I see what you mean :-( Sorry about that! Should be fixed now w/ my force-push to 01b4fc7.


context.getPackageManager is not a function error

I am getting this error for Android, real device:
context.getPackageManager is not a function error
Could you please fix it :( otherwise I am gonna have to manually set it every time for ios and Android and I might forget.
Thanks

Please check 1.2.0 (also available on npm) and close if it's working nicely. Thanks for bringing this kind of usage to my attention!

Works perfect! Closing.


Add travis build

Maybe add travis build, useful to see the stability of the project

Resolved by #27


Fix typo in vhosts.md

I copy-paste some commands from docs and find typo

@uncle-roma Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@pivotal-cla this is an obvious fix

@uncle-roma This Pull Request contains an obvious fix. Signing the Contributor License Agreement is not necessary.


Unable to install minimap package on Windows 8.1 with Atom v.0.176

Hi, I tried to do a package install with Atom and I am unable to install minimap. Not sure what is going on but there is the error message that I got. I just did a fresh install of Atom to my Windows 8.1 laptop.
npm ERR! Failed to clone git+https://github.com/Benvie/harmony-collections.git#e81b4b808359e2def9eeeabfdee69c2989e1fe96 from https://github.com/Benvie/harmony-collections.git Cloning into 'C:\Users\Josh\AppData\Local\Temp\npm-1952-09bd2c23\git-cache-d860487d2c7d\e81b4b808359e2def9eeeabfdee69c2989e1fe96'...
npm ERR! Failed to clone git+https://github.com/Benvie/harmony-collections.git#e81b4b808359e2def9eeeabfdee69c2989e1fe96 from https://github.com/Benvie/harmony-collections.git fatal: '/cygdrive/c/Users/Josh/.atom/.node-gyp/.atom/.apm/_git-remotes/https-github-com-Benvie-harmony-collections-git-df214100/c:\Users\Josh.atom.node-gyp.atom.apm_git-remotes\https-github-com-Benvie-harmony-collections-git-df214100' does not appear to be a git repository
npm ERR! Failed to clone git+https://github.com/Benvie/harmony-collections.git#e81b4b808359e2def9eeeabfdee69c2989e1fe96 from https://github.com/Benvie/harmony-collections.git fatal: Could not read from remote repository.
npm ERR! Failed to clone git+https://github.com/Benvie/harmony-collections.git#e81b4b808359e2def9eeeabfdee69c2989e1fe96 from https://github.com/Benvie/harmony-collections.git
npm ERR! Failed to clone git+https://github.com/Benvie/harmony-collections.git#e81b4b808359e2def9eeeabfdee69c2989e1fe96 from https://github.com/Benvie/harmony-collections.git Please make sure you have the correct access rights
npm ERR! Failed to clone git+https://github.com/Benvie/harmony-collections.git#e81b4b808359e2def9eeeabfdee69c2989e1fe96 from https://github.com/Benvie/harmony-collections.git and the repository exists.
npm ERR! Failed to clone git+https://github.com/Benvie/harmony-collections.git#e81b4b808359e2def9eeeabfdee69c2989e1fe96 from https://github.com/Benvie/harmony-collections.git
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "c:\Users\Josh\AppData\Local\atom\app-0.176.0\resources\app\apm\bin\\node.exe" "c:\Users\Josh\AppData\Local\atom\app-0.176.0\resources\app\apm\node_modules\npm\bin\npm-cli.js" "--globalconfig" "c:\Users\Josh\AppData\Local\atom\app-0.176.0\resources\app\apm\.apmrc" "--userconfig" "c:\Users\Josh\.atom\.apmrc" "install" "C:\Users\Josh\AppData\Local\Temp\d-11513-9844-uadpna\package.tgz" "--target=0.20.0" "--arch=ia32" "--msvs_version=2013"
npm ERR! node v0.10.35
npm ERR! npm  v2.3.0
npm ERR! code 128
npm ERR! Command failed: Cloning into 'C:\Users\Josh\AppData\Local\Temp\npm-1952-09bd2c23\git-cache-d860487d2c7d\e81b4b808359e2def9eeeabfdee69c2989e1fe96'...
npm ERR! fatal: '/cygdrive/c/Users/Josh/.atom/.node-gyp/.atom/.apm/_git-remotes/https-github-com-Benvie-harmony-collections-git-df214100/c:\Users\Josh.atom.node-gyp.atom.apm_git-remotes\https-github-com-Benvie-harmony-collections-git-df214100' does not appear to be a git repository
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     http://github.com/npm/npm/issues

You should report this in the package's repo.
https://github.com/fundon/atom-minimap/issues

@AbeEstrada I think the error is in the installation of minimap, not in the usage of minimap. and It's Atom who handles the installation process. :smiley:

Gonna close this one out since this was on such an old version - feel free to reopen if you experience this again with the latest version of Atom.


Arrow warning: Some reference contigs aligned against are not found in the reference FASTA.

Operating system
Which operating system and version are you using?
$ cat /etc/centos-release
CentOS Linux release 7.5.1804 (Core)
$ arch
x86_64

Package name
Which package / tool is causing the problem? Which version are you using, use tool --version. Have you updated to the latest version conda update package?
Using arrow from GenomicConsensus,
$ arrow --version
2.3.2

Conda environment
What is the result of conda list?
The input data consistency checks do not catch the following user error: Running arrow with a BAM file mapped against referenceA.fasta but accidentally supplying referenceB.fasta, where the two references are different but have many contig names in common.
In this case I was using two different assemblies from Canu, which names its contigs like "tig0000000n" (not always counted continuously - many will be missing), resulting in many contig names in common.
Error message
Paste the error message / stack.
arrow -j 32 -r wrong_reference.fasta -o after_arrow.fasta -o after_arrow.vcf pbalign_merged.bam
[WARNING] Some reference contigs aligned against are not found in the reference FASTA.  Will process only those contigs supported by the reference FASTA.

The big problem is there was no error message - I want this to fail!
To Reproduce
Steps to reproduce the behavior. Providing a minimal test dataset on which we can reproduce the behavior will generally lead to quicker turnaround time!
Regrettably the files are too large to easily share, and are currently confidential.
Expected behavior
A clear and concise description of what you expected to happen.
Referring to the source code, the warning is from here:
https://github.com/PacificBiosciences/GenomicConsensus/blob/master/GenomicConsensus/reference.py#L124
https://github.com/PacificBiosciences/GenomicConsensus/blob/develop/GenomicConsensus/reference.py#L124
In the comments above you say:
    # Contigs in FASTA may disagree with those in cmp.h5 ref info
    # table, for instance if the FASTA has been edited.  Here's how we
    # handle things:
    #
    # |fastaContigs \   cmpContigs| > 0 : OK, extra FASTA contigs just ignored
    # |cmpContigs   \ fastaContigs| > 0 : Not necessarily OK---a warning should be
    #                                     issued.  We then proceed to operate on
    #                                     the contigs that are in both.
    # |cmpContigs ^ fastaContigs| == 0  : Nothing to work with.  This is an error.
    #
    # While we formerly used MD5s to vouch for the identity of a
    # contig, we now use the name.  This is an inferior approach but
    # is necessary, in using the FastaTable.

In my example, checking the MD5 would have revealed that while there were some contigs of the same name in the FASTA and BAM, they did not match.
The BAM file does contain the MD5 of each reference contig as part of the @SQ header lines, but also contain the expected length.
I can understand not checking the MD5 due to speed, but checking the name and lengths are consistent ought to be a very quick test and would catch most cases (even if by chance the first few contigs matched up, the chances of all the contig lengths matching ought to be minimal).

In my use case, this issue is not a problem.
I have a large (>10 gbp) genome I want to polish, and in order to parallelize the variant calls, I need to split the merged, sorted BAM file and the genome assembly. The merged, sorted BAM file has a header covering all the contigs in the assembly, but in the split jobs, I only reference a small number of contigs per job. I use the header lines from the big merged, sorted BAM file, and I do get the warning message, and that's fine.
Please do not change the code to make this error. Instead, please provide an option to allow the user to make this an error if they choose to do so. Then, 'pb-dseifert' can achieve the program behavior he or she needs, and my use case still works.
Thanks.

@peterjc @bruc provide a PR and I will merge it and cut a new release

It is good to have an explicit use-case for why the FASTA file might not match the BAM alignment, but rather a subset of the alignment. [In this case you could likely subset the BAM file, but I can can see it is convenient not to have to]. Here those names in common would have matching lengths in the reference FASTA and the alignment header (and indeed their sequence MD5 would match if that were checked)
i.e. I don't think checking names and lengths for consistency would block @bruc's use case - I think you would still get the same warning as now:
[WARNING] Some reference contigs aligned against are not found in the reference FASTA.  Will process only those contigs supported by the reference FASTA.

Closing due to lack of activity.


Roadmap for eCheck

Is there a roadmap to implement this same methodology for eChecks.
Bank Name
Routing Number
Account Number
Account Type

Some code for a valid routing number ...

// https://en.wikipedia.org/wiki/Routing_transit_number#MICR_Routing_number_format
function validRoutingNumber(str)
	{
	str = trim(str);
	console.log("validRoutingNumber: "+str);
	if(!validNumber(str)) { return false; }
	var len = str.length;
		console.log(len);
	if(len != 9) { return false; }
	var sum = 0;
		var multiply = [3,7,1,3,7,1,3,7,1];
	for(var i=0;i<len;i++)
		{
		sum += multiply[i]*parseInt(str.charAt(i));
		}
		console.log(sum);
	if(sum % 10 != 0) { return false; }

	return true;
	}

@MonteShaffer
I'm happy to see you excited about this project. Please keep the requests coming, and as with all of them you're welcome to submit a PR, or someone will pickup the request when they have time. :)
Thanks!

Duplicate of https://github.com/jessepollak/card/issues/410


the answers of chatgpt dont appear in the whatsappchat

They do. Except:

your own.
Users once activated disappearing messages. Even they deactivate it, they never get a reply again.
Users used "reply to message"-function of WhatsApp, or submit an attachment. Like hyperlink with preview.

In my fork is it repaired. Outdated whatsapp-lib.

In my fork is it repaired. Outdated whatsapp-lib.

Great, but how to "upgrade"? I tried it, but I get errors in "go", like:
main.go:23:2: missing go.sum entry for module providing package go.mau.fi/whatsmeow/types/events; to add:
go mod download go.mau.fi/whatsmeow
Maybe I'm naive, but I have no idea what to do now.
Because the 500-error, you could do a "refresh" inside the browser to reload the page's content before pushing the new message inside. In that case I have to make sure, that the chat is opened at the specific chat, and not on the "new chat tab".
In my case, sometimes messages are very long, so I did a split-up to 100-words + words to the next .!?\n with iterating through the original message. Delivering n+ messages back. I also added a context-id which helps chatGPT to keep these split-messages' context together. - All with the help of ChatGPT, because I have no Idea of programming.

For the length, you would have to look in the code. But regarding the error during the update, here changes had to be made to the code. There were breaking changes in the Whatsapp client.
If you have the error 500 after a certain time, you just have to look again whether you are logged in or whether a Cloudflare Captcha appears.

For the length, you would have to look in the code. But regarding the error during the update, here changes had to be made to the code. There were breaking changes in the Whatsapp client.
If you have the error 500 after a certain time, you just have to look again whether you are logged in or whether a Cloudflare Captcha appears.

Thx for your reply.
I already implemented some of these things. The "Browser refresh" helps to avoid Error 500, because the internal token system of ChatGPT gets a new token through the refresh. I split the messages, in chunks of 100 words + rest to the next ".", "!", "?" or "\n". Works fine. So, longer Messages are replied with n messages. I also embed the WhatsApp-Message inside a pre-defined priming for ChatGPT, to aim special behavior.
I will upgrade my version to your version within the next week. I thing it will be better. Let's see! It's amazing!

Currently I am also working on an automatic login. Cloudflare Captcha Solving I could not test yet.


[BugFix] fix be start crash when load same tablet

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #20618
Problem Summary(Required) ：

There is a tablet that exists in two datadirs, possibly due to the remnants of an old tablet caused by migrate/clone.
BE restart, load this tablet twice.
If the old tablet is loaded first and then the new tablet is loaded, the new tablet will overwrite and delete the old tablet, and this will not cause a crash in BE. However, if the new tablet is loaded first and then the old tablet is loaded, it will cause a crash in BE.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


AttributeError: 'Tensor' object has no attribute 'numpy'

I use tensorflow with Google Colaboratory
I have TensorFlow 2.x selected.
I wrote a small error metrics but could not succeed to transform the result to numpy array.
I got AttributeError: 'Tensor' object has no attribute 'numpy'
I thought I could transform my tensor to numpy array with a .numpy() call
def custom__error(y_true, y_pred):
  # ---- y_pred
  yp = tf.nn.softmax( y_pred)
  bp = tf.argsort(yp,axis=-1,direction='DESCENDING',stable=False,name=None)
  #cp = bp.numpy()
  xcp = bp[None,:10]
  # ---- y_true
  yt = tf.nn.softmax( y_true )
  bt = tf.argsort(yt,axis=-1,direction='DESCENDING',stable=False,name=None)
  #ct = bt.numpy()
  xct = bt[None,:10]
  # ---- common
  count =  tf.sets.intersection(xcp,xct)
  dcount = tf.sparse.to_dense(count)
  return dcount.numpy()

<ipython-input-46-10646c4f8b46> in custom__error(y_true, y_pred)
     15   count =  tf.sets.intersection(xcp,xct)
     16   dcount = tf.sparse.to_dense(count)
---> 17   return dcount.numpy()
     18
     19

AttributeError: 'Tensor' object has no attribute 'numpy'

I use tensorflow with Google Colaboratory
I have TensorFlow 2.x selected.
I wrote a small error metrics but could not succeed to transform the result to numpy array.
I got AttributeError: 'Tensor' object has no attribute 'numpy'
I thought I could transform my tensor to numpy array with a .numpy() call
def custom__error(y_true, y_pred):
  # ---- y_pred
  yp = tf.nn.softmax( y_pred)
  bp = tf.argsort(yp,axis=-1,direction='DESCENDING',stable=False,name=None)
  #cp = bp.numpy()
  xcp = bp[None,:10]
  # ---- y_true
  yt = tf.nn.softmax( y_true )
  bt = tf.argsort(yt,axis=-1,direction='DESCENDING',stable=False,name=None)
  #ct = bt.numpy()
  xct = bt[None,:10]
  # ---- common
  count =  tf.sets.intersection(xcp,xct)
  dcount = tf.sparse.to_dense(count)
  return dcount.numpy()

<ipython-input-46-10646c4f8b46> in custom__error(y_true, y_pred)
     15   count =  tf.sets.intersection(xcp,xct)
     16   dcount = tf.sparse.to_dense(count)
---> 17   return dcount.numpy()
     18
     19

AttributeError: 'Tensor' object has no attribute 'numpy'

It works fine for me. This usually happens in older version of tensorflow where you have to enable eager execution. Are you sure that tensorflow version is >= 2.x?

Hello abhipn
I wrote
%tensorflow_version 2.x
And got
`%tensorflow_version` only switches the major version: 1.x or 2.x.
You set: `2.x  # this line is not required unless you are in a notebook`. This will be interpreted as: `2.x`.

TensorFlow is already loaded. Please restart the runtime to change versions.

If you want to check
https://colab.research.google.com/drive/14TC0Hgf_aKtSTwlZvUKMlVYZUdvUuVJv?usp=sharing

@Harvey13 Can you provide minimal reproducible notebook so I can execute the code and get the error you are facing?

@Harvey13
Request you to provide colab link or simple standalone code to reproduce the issue in our environment.It helps us in localizing the issue faster.Thanks!

https://colab.research.google.com/drive/12fkayzNa0uOIRkKJYsZ0J7VjwS0P-BXd?usp=sharing

My problem is only inside a callback function (tf backend)
https://colab.research.google.com/drive/1wFKDQjlPuB0ax0g-ZSU8ge1ukzBBn3TR?usp=sharing

Access for everyone with the link

@Harvey13 I was able to replicate the issue and I believe it is not possible to extract numpy arrays in Keras loss functions (or) metrics. You have to operate on tensors using either keras backend functions or tensorflow functions but not using numpy to calculate the loss.

@Harvey13
Can you please provide correct colab link to understand the issue better.Thanks!

@ravikyram
https://colab.research.google.com/drive/1wFKDQjlPuB0ax0g-ZSU8ge1ukzBBn3TR?usp=sharing

I have tried in colab with TF 2.2 and was able to reproduce the issue.Please, find the gist here.Thanks!

I have tried in TF nightly version(2.3.0-dev20200526) and i am seeing below error message.AttributeError: module 'tensorflow.python.framework.ops' has no attribute '_TensorLike'.Please, find the gist here.Thanks!

@Harvey13 Looks like this was resolved. I am not able to reproduce the issue. Can you please check the gist here. Thanks!
Please verify once and close the issue if this was resolved for you. Thanks!

@jvishnuvardhan The gist works fine, even with original custom__error function.
Unfortunatly my own project, no more works, even without numpy() call inside backend function : it's a new bug because it was working fine former the nightlty installed
I tried differents old projects they all have the same error with tf-nightly :
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-45-2a71bdab68f1> in <module>()
----> 1 model = make_model()
      2 print(str(training_data_width) + "=>" + str(target_data_width))
      3 model.compile(loss=custom__loss, optimizer='adam', metrics=['binary_accuracy','accuracy',custom__error])

5 frames
/usr/local/lib/python3.6/dist-packages/keras/backend/tensorflow_backend.py in is_tensor(x)
    701
    702 def is_tensor(x):
--> 703     return isinstance(x, tf_ops._TensorLike) or tf_ops.is_dense_tensor_like(x)
    704
    705

AttributeError: module 'tensorflow.python.framework.ops' has no attribute '_TensorLike'

Message du 06/06/20 09:40> De : "Vishnuvardhan Janapati" > A : "tensorflow/tensorflow" > Copie à : "Harvey13" , "Mention" > Objet : Re: [tensorflow/tensorflow] AttributeError: 'Tensor' object has no attribute 'numpy' (#39817)> >
@Harvey13 Looks like this was resolved. I am not able to reproduce the issue. Can you please check the gist here. Thanks!
Please verify once and close the issue if this was resolved for you. Thanks!
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/tensorflow/tensorflow/issues/39817#issuecomment-640005373", "url": "https://github.com/tensorflow/tensorflow/issues/39817#issuecomment-640005373", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

@Harvey13 When error description include '_TensorLike', then mostly it is due to using mixing functions from keras and tf.keras in the code. Can you please share a standalone code that is throwing an error. Thanks!

@Harvey13 I am closing this issue as you confirmed that the issue was resolved. Thanks!


Enable Main - Manages 3rd Party Slaves.vi dialog with large code clean up

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
The end goal of this PR was to enable out-of-process calls inside of the "Manage 3rd Party ECAT Slaves" dialog.
What it became was much more of a re-write and massive code re-organization, with some bug fixing along the way.
Below is an attempt to describe the changes to aid review:
Major Changes

Re-add Main - Manages 3rd Party Slaves.vi to the Action VIs folder in System Explorer library

This was the last 'broken VI', so delete that virtual folder
Massively clean up diagrams, as many were mangled from resizing other cases over time
Move core "import" functionality to a sub VI (covered below)

Create single-sourced Host - Import ESI File.vi

This replaces the nearly identical logic used in two cases: 'import' and 'upload profile to target'
Dig into sub VIs and replace assumptions of file paths based on vi.lib location:

_ValidateDeviceProfiles.vi uses it to find niECATLVProvider.mxx
_generateProfilePath.vi uses it to build paths for ESI files on the host

Remove most dialogs from inside out-of-process calls

The ECAT sub VIs still allow a pop-up to enter non-standard credentials
This could be replaced by using the password from VeriStand's sysdef in the future

Create two out-of-process applications that are not supported in LabVIEW 2021 64-bit

Import ESI File.vi and Read Target ESI Files.vi
Create calling VIs and application build specifications for both

New sub VI Read ESI Files on RT Target.vi

Combines several sub VIs and calling code into one much simpler VI

New sub VI Read ESI Files on RT Target.vi

Simpler logic than RT file read, but makes the calling diagram easier to follow

Minor Changes

New Utility VI Get LabVIEW Directory.vi

Read a registry key to get the LabVIEW 32-bit install directory
Use this to replace various other means these VIs used to build the same root path

Add more ECAT_InternalSubVIs from vi.lib to the custom device source

Any VIs that built paths based on vi.lib needed to be copied and updated

Change icons on all ECAT_InternalSubVIs to show the SEECD banner to distinguish between those in vi.lib
Remove passwords on all local ECAT_InternalSubVIs VIs
Behavior fix: Only import profiles to RT target from Windows when the VS target is not Windows
Behavior fix: Only read profiles from RT target when sysdef is not set to Windows
Behavior fix: Read host ESI files even if reading RT target files fails
Add an error to throw when unable to read files on the target

Why should this Pull Request be merged?
This PR should do the following:

Allow VS 2021 to build and use this dialog
Massively simplify the codebase
Fix several annoying quirks of the dialog

What testing has been done?
Extensive hand testing in VeriStand 2020 R6 when configured to both Windows and Linux in the sysdef. I used a third-party ESI file to import to both the host and the target, as well as tested when the target's IP address was mis-configured.

[ ] We may want to handle the case where the call to ValidateDeviceProfile() fails due to the .mxx file not existing. This error message would be a good opportunity to clarify which software needs to be installed.
[ ] Can we delete the diagram disable structure in Get Webdav.vi?


Compatibility with postcss/cssnext

Would be awesome to support https://github.com/ebryn/ember-cli-cssnext

Also it will be better to use PostCSS parser, instead of Rework’s css, because of:

PostCSS is faster, that Rework.
PostCSS supports custom at-rules. So it is more future proof.
PostCSS has integration tests. We use many real world sites (GitHub, Twitter, BrowsersHack) to test every commit in PostCSS parser to be sure, that we can parse all of CSS features.
Rework project has no development right now.

Also if we will use PostCSS to transform selectors, we can use same parsed AST for everyone-have Autoprefixer and cssnext. So one CSS parsing step for all CSS tranformation will make CSS processing real faster (CSS parsing is one of biggest step in every tool).

@ai happy to switch parsers. should be easy for anyone to PR this before i get around to it.

Any updates on that? Really looking forward for support of postcss/cssnext.

Can't this issue be closed as #112 was merged or are there still incompatibilities?

Nope this is still a separate issue. #112 just switches the internal compiling from rework to postcss, this there's still work to be done to support ember-cli postcss addons. #123 might solve this though.

CSS Next should be supported in #123 I'll add a test for it when I work on those next week.

Good news! :tada:
I just created a new app from scratch with ember canary and 'ember-routing-routable-components'.
I'm successfully using the following addons and plugins in conjunction with routable components:

webark/ember-component-css#private-class-names
ember-cli-postcss
postcss-cssnext
postcss-easy-import

This is my directory structure:
app
├── components
│   ├── application
│   │   ├── component.js
│   │   ├── styles.css
│   │   └── template.hbs
│   └── login
│       ├── component.js
│       ├── styles.css
│       └── template.hbs
├── login
│   └── route.js
├── models
├── styles
│   └── app.css
├── app.js
├── index.html
├── resolver.js
└── router.js

Just remember to have your component.js like this:
import Ember from 'ember';

export default Ember.Component.extend({
  isGlimmerComponent: true
});

And don't forget to @import "pod-styles"; in your app.css.
Thanks so much! :love_letter:

@buschtoens did you try it with local lookup?

And I'm going to close this ticket then if cssnext is working.

Enabled by default. :smile:


Feature: add eval warnings

Closes #126
Changes:

change footer text (X component(s), X warning(s)), make the text a link to the relevant tab
intercept Alpine's warnings for eval errors
implement initial UI for "Warnings" (only contains eval warnings)
add/update tests

Chore:

move purple colour into Tailwind config
prevent default on tab links
upgrade Cypress

Needs feedback:

do we need to debounce the "scroll to last element"?
should we scroll to last element when changing tabs?
thoughts on using pauseMutationObserver? @SimoTod
design feedback (one for @stephenoldham)
should I take the devOnly checks out? (probably should if we're intending to roll this out, could be a separate PR)

I think it's acceptable to stop it for 10ms because of an explicit user action (showing/hiding errors)

I think it's acceptable to stop it for 10ms because of an explicit user action (showing/hiding errors)

I think it's acceptable to stop it for 10ms because of an explicit user action (showing/hiding errors)

Yeah that's what I was thinking, we only pause things when the user is interacting with the devtools which means they're not likely to be interacting with their page at exactly the same time

I think it's acceptable to stop it for 10ms because of an explicit user action (showing/hiding errors)

Yeah that's what I was thinking, we only pause things when the user is interacting with the devtools which means they're not likely to be interacting with their page at exactly the same time

I'll test this out during the week while working on an Alpine project and give any feedback I come across.
Since this hijacks console.warn, maybe we could make it opt in via a "experimental" setting? That feature is not wired up yet but after we get the settings chrome storage set up it should be trivial. BTW, we could also have a general option like "opt in for all experimental features" and essentially have people beta testing features before they are available to everyone.
I also like the idea of adding a bunch of rules like we discussed here: https://github.com/alpinejs/alpine/discussions/975
I feel like 90% of the issues on Discord can be fixed with a handful of static analysis checks/sniffs. (hmm I wonder if we could parse and check for when a user uses a non-arrow function and tries to access props via this)

I'll test this out during the week while working on an Alpine project and give any feedback I come across.
Since this hijacks console.warn, maybe we could make it opt in via a "experimental" setting? That feature is not wired up yet but after we get the settings chrome storage set up it should be trivial. BTW, we could also have a general option like "opt in for all experimental features" and essentially have people beta testing features before they are available to everyone.
I also like the idea of adding a bunch of rules like we discussed here: https://github.com/alpinejs/alpine/discussions/975
I feel like 90% of the issues on Discord can be fixed with a handful of static analysis checks/sniffs. (hmm I wonder if we could parse and check for when a user uses a non-arrow function and tries to access props via this)

Are we changing window.Alpine.pauseMutationObserver on the user's site? I think it's fine but we should check whether it's already paused and not unpause it in that case.

Are we changing window.Alpine.pauseMutationObserver on the user's site? I think it's fine but we should check whether it's already paused and not unpause it in that case.

Since this hijacks console.warn, maybe we could make it opt in via a "experimental" setting?

Maybe we could, Caleb seems open to add the data I'm parsing out to the error object that gets thrown, so for a future versions of Alpine, we would attach a global error event handler and not hijack console.warn
I've made it so that the console.warn override only happens in version 2.8.0+.

I also like the idea of adding a bunch of rules like we discussed here: https://github.com/alpinejs/alpine/discussions/975

I've created an issue for this https://github.com/alpine-collective/alpinejs-devtools/issues/141

I feel like 90% of the issues on Discord can be fixed with a handful of static analysis checks/sniffs. (hmm I wonder if we could parse and check for when a user uses a non-arrow function and tries to access props via this)

Dunno about that particular one, any JS check would mean we need to create an AST of some sort to inspect the code programmatically. For HTML/attribute stuff I think it's reasonable though, see #141

Since this hijacks console.warn, maybe we could make it opt in via a "experimental" setting?

Maybe we could, Caleb seems open to add the data I'm parsing out to the error object that gets thrown, so for a future versions of Alpine, we would attach a global error event handler and not hijack console.warn
I've made it so that the console.warn override only happens in version 2.8.0+.

I also like the idea of adding a bunch of rules like we discussed here: https://github.com/alpinejs/alpine/discussions/975

I've created an issue for this https://github.com/alpine-collective/alpinejs-devtools/issues/141

I feel like 90% of the issues on Discord can be fixed with a handful of static analysis checks/sniffs. (hmm I wonder if we could parse and check for when a user uses a non-arrow function and tries to access props via this)

Dunno about that particular one, any JS check would mean we need to create an AST of some sort to inspect the code programmatically. For HTML/attribute stuff I think it's reasonable though, see #141

Are we changing window.Alpine.pauseMutationObserver on the user's site? I think it's fine but we should check whether it's already paused and not unpause it in that case.

Good catch
Like I've said in a previous comment, if the user is interesting with the devtools I think it's very unlikely that they're able to interact with their app at exactly the same time so I dunno what would pause the observer, but I'll add it just in case

Are we changing window.Alpine.pauseMutationObserver on the user's site? I think it's fine but we should check whether it's already paused and not unpause it in that case.

Good catch
Like I've said in a previous comment, if the user is interesting with the devtools I think it's very unlikely that they're able to interact with their app at exactly the same time so I dunno what would pause the observer, but I'll add it just in case

I personally disable it on the WordPress admin area as the WP ui does a billion mutations sometimes and it crashes. The check would be useful otherwise it would turn it back on, I think, right?

I personally disable it on the WordPress admin area as the WP ui does a billion mutations sometimes and it crashes. The check would be useful otherwise it would turn it back on, I think, right?

design feedback (one for @stephenoldham)

Belated Happy New Year all 😉
I think leaning as close to the native Chrome console for this would probably make most sense. With some design sprinkles where appropriate. Happy to have a play with some styling if needed.

design feedback (one for @stephenoldham)

Belated Happy New Year all 😉
I think leaning as close to the native Chrome console for this would probably make most sense. With some design sprinkles where appropriate. Happy to have a play with some styling if needed.

@stephenoldham feel free to have a play, I've lifted colours from the existing "components" tab, maybe I should have a lighter background on the "error entries"?

@stephenoldham feel free to have a play, I've lifted colours from the existing "components" tab, maybe I should have a lighter background on the "error entries"?


Provide support for setting cookieLifetime equivalent using Alloy

Currently, there is no function within the Alloy framework to support setting cookie expiration in the same manner as is supported using s.cookieLifetime in AppMeasurement.
Without this functionality in Alloy, we cannot manually set/control the cookie expiration using this solution.

@AdamWadd Can you please explain the use case (or the need) for this feature in Alloy?
This used to be a popular feature when we didn't have consent support, back in the days. Now the lifetime of the cookie is less important because consent takes precedence.
I'd love to learn more, thanks.
@vivasd

Is there any plans to support this feature, my use case has also a very strict guidance for not having cookies that go beyond 365 days.
Specifically, per these docs, there are three cookies with a Max-Age greater than 365 days:

kndct_orgid_identity (395 days)
mbox (2 years)
AMCV_###@AdobeOrg (395 days)

We have also engaged the Adobe Analytics support and they confirmed, as of Sep/17/2024 there is no support for setting the "cookieLifetime" in the Web SDK: https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/config-vars/cookielifetime
The Web SDK does not yet offer customization to the lifetime of cookies that it sets.


Button with phx-click doesn't seem to work within a NavigationLink

I was going through the tutorial building the Cats app, I added the Button in the HStack to mark a cat as "favorite". This worked great until I added the NavigationLink to go to the detail view. Now you can't seem to click on the favorite Button, it will just do the navigation. Here is the render function:
def render(%{platform_id: :swiftui} = assigns) do
    ~SWIFTUI"""
      <List modifiers={navigation_title(@native, title: "Cats!")}>
        <%= for {name, favorite} <- @cats_and_favorites do %>
          <NavigationLink id={name} destination={"/cats/#{name}"}>
            <HStack>
              <AsyncImage url={"/images/cats/#{name}.jpg"} modifiers={frame(@native, width: 100, height: 100)} />
              <Text><%= name %></Text>
              <Spacer />
              <Button phx-click="toggle-favorite" phx-value-name={name}>
                <Image system-name={if favorite, do: "star.fill", else: "star"} symbol-color={if favorite, do: "#f3c51a", else: "#000000"} />
              </Button>
            </HStack>
          </NavigationLink>
        <% end %>
      </List>
    """
  end

Rejecting according to the team

Can we include explanations as to why an issue is being rejected? Especially if someone from outside the team is opening the issue. Just rejecting without explanation is going to lead to people getting upset.

I provided an explanation for the issue and a workaround in a comment above. We are not using that tutorial anymore so it does not need to be updated.

This matches the behavior of SwiftUI, which gives priority to the NavigationLink over the Button.

use highPriorityGesture, a stack with the link and button separated, an overlay on the link, or some other method of giving the button priority


hello, add a vue3 component named "vue-virtual-tree" in tree category

General

✏ Mark the necessary items without changing the structure of the PR template.

[x] Pull request template structure not broken

Type

ℹ  What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[ ] Fix
[ ] Feature

Checklist

ℹ  Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉  Put an x in the boxes that apply.

[x] Title as described
[x] Make sure you put things in the right category!
[x] Always add your items to the end of a list

Open Source

[x] Link description does not contain a link to an author / third-party resource
[x] The documentation (README) contains a description of the project, illustration of the project with a demo or screenshots and a CONTRIBUTING section
[x] The documentation is in English.
[x] The project is active and maintained.
[x] The project accepts contributions.
[x] Not a commercial product

Apps/Websites

[ ] The website is available without errors or ssl certificate problems, and load in a reasonable amount of time.
[ ] The website is using vuejs intensively. It should detect vue with vue-devtools.

If you cannot detect vue with vue-devtools due to work at non public pages (e.g. for enterprise website), you can send Pull Request with screenshot that detected it.

[ ] The website is original and not too simple. For that reason, blogs and simple landing pages are rejected.
[ ] A commercial product using Vue, provided that guests could reasonably check out how Vue was used A commercial product using Vue, provided that guests could reasonably check out how Vue was used (i.e. A headless CMS which uses Vue for the Admin/editor Area and offers a free tier).

I don't think there is any conflict in the code. How can I solve it? Thank you

I don't think there is any conflict in the code. How can I solve it? Thank you

rebases you branch to master

I don't think there is any conflict in the code. How can I solve it? Thank you

rebases you branch to master

Thanks for the answer


Server Initiation Fails

I tried setting up this docker having an I5; 16Gb Ram; Nvidia 840m; with the docker command docker command.txt . After it started downloading the files some Errors occurred and it crashed as seen in the error logs. I cleaned everything up and tried ageing but i got the same error. I cant figure out if it is an error from setting it up wrong.
docker command.txt
console.log
error.log
script.log

SERVER_HOST_REGISTER_ADDRESS must be your public external IP to the Internet, <IP_ADDRESS> is a local IP to your (home) network

Ok, i'll try this, but is it not possible to host it on the Private Network?

Sure, but these is no point in registring your local IP with the master servers.
According to your logs the server is working fine. In console.log the last entry at 22:21:11:358 is a persistence save which occurs way later than the warnings in error.log


Docker pull not working

🐛 Summary
A docker pull command for this skeleton is not working. It is returning a "manifest unknown" response.
To reproduce
Steps to reproduce the behavior:

docker pull cisagov/con-pca-api

Expected behavior
The docker image is pulled.
Any helpful log output or screenshots

There is no latest (the default tag pulled if one is not specified) tag available for that image on Docker Hub. There is no latest tag because that is only used when a git tag is what triggers the workflow and this repository has yet to have a git tag or release created.


[FLINK-16160][table-planner-blink] Fix proctime()/rowtime() doesn't w…

…ork for TableEnvironment.connect().createTemporaryTable()
What is the purpose of the change
Since FLINK-14490, proctime()/rowtime() doesn't work  for TableEnvironment.connect().createTemporaryTable(), The root cause is:

proctime()/rowtime() are used along with DefinedRowtimeAttributes/DefinedProctimeAttribute and ConnectorCatalogTable.  The original code path stores the ConnectorCatalogTable object in Catalog and in validate phrase, the RowType is derived from ConnectorCatalogTable.getSchema which contains time indicator. After FLINK-14490, we store CatalogTableImpl object in Catalog and in validate phrase, the RowType is derived from CatalogTableImpl.getSchema which doesn't contain time indicator.
In SqlToRel phrase, FlinkCalciteCatalogReader converts ConnectorCatalogTable to TableSourceTable and converts CatalogTable to CatalogSourceTable. The TableSourceTable would be converted to LogicalTableScan directly and contains time indicator. Otherwise the CatalogSourceTable would be converted to a LogicalTableScan whose time indicator is erased(by FLINK-16345).
This PR fix it.

Brief change log

instantiate the TableSource in CatalogSchemaTable and check if it's a DefinedRowtimeAttributes/DefinedProctimeAttribute instance. If so, rewrite the TableSchema to patch the time indicator(as it is in ConnectorCatalogTable#calculateSourceSchema)
Avoid erasing time indicator in CatalogSourceTable if the TableSource is a DefinedRowtimeAttributes/DefinedProctimeAttribute instance

Verifying this change
This change added tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@wuchong pls have a look

Hi @docete , the change looks good to me. Could you rebase and resolve the conflicts and open another pull request for 1.10 branch?

rebased. Will open another pr for 1.10 branch soon.

Passed: https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=1680&view=results
Merging...


Del test_with_pir_api

del test_with_pir_api
Pcard-67012

 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.


Implement WasmBoundary for types like String/Vec/str

@fitzgen and I had a fantastic discussion just now about how to implement the WasmBoundary trait for more types. Right now there's a bunch of special casing for vectors, slices, and strings, but that's a bit of a bummer! It'd be best if each type could implement a trait so we could let rustc's name resolution and type resolution figure out what the types are.
This'll be tricky though because types like vectors/slices take two arguments in the ABI. I think though we can develop a solution where a call to JS creates a local stack array of values which we then pass to JS. Similarly there'd be one global stack of values for JS to pass to wasm.
The final tricky part is getting signatures without strings/vectors to not use the stack (to be optimized more in the engine), but I think we can deal with that at compile time by generating code for both and having rustc optimize which one ends up getting run.

Note that we don't actually need a whole stack, just a single stack frame.

Assuming a maximum function arity, of course.

Fixed in https://github.com/alexcrichton/wasm-bindgen/commit/cdbb31f3a99463b57a78382911fd6ea3b8abce54


Do not show dead guides for superseded extensions

Should sort out #1163, but let's wait and see what the CI says.

https://extensions-quarkus-pr-1213-preview.surge.sh/io.quarkiverse.reactivemessaging.nats-jetstream/quarkus-reactive-messsaging-nats-jetstream/ now no longer shows the dead guide.


Clean up long description in PyPI

Currently re-using the README.md...but PyPI doesn't render Markdown : (
https://pypi.python.org/pypi/postman_problems/0.1

example using rst: https://pypi.python.org/pypi/lcinvestor
from https://stackoverflow.com/questions/16367770/my-rst-readme-is-not-formatted-on-pypi-python-org


[issue] Fail to write rows to arangodb in batch when importing dataset with java client concurrently

My Environment

ArangoDB Version:        3.6.13 community edition
Deployment Mode:        Leader/Follower ("Master/Slave")
Deployment Strategy:   Manual Start，arangodb3-3.6.13-1.0.x86_64.rpm
Configuration:               3 nodes (one master and two slave)
Infrastructure:               own
Operating System:       CentOS 7.x
Total RAM in your machine:    64Gb
Disks in use:         SSD
Used Package:     arangodb3-3.6.13-1.0.x86_64.rpm

Component, Query & Data
Affected feature:

Java client parameter prepare and send request:
DocumentImportOptions options = new DocumentImportOptions().waitForSync(true);
options.details(true);
options.onDuplicate(DocumentImportOptions.OnDuplicate.update);
ArangoSerializer.Options serialOptions = new ArangoSerializer.Options().serializeNullValues(true).stringAsJson(true);
DocumentImportEntity retObj = ac.importDocuments(rows, options, serialOptions);

Problem:
the error trace is:
creating document failed with error 'conflict', offending document:  {"xx": xxx, "_from": null, .....}

Expected result:
except write data rows to graph database successfully.
downloaded arangodb source code today, and grep with keyword 'creating document failed with error'
> grep -rn 'creating document failed with error' *
> RestHandler/RestImportHandler.cpp:927:   positionize(i), "creating document failed with error '",

found that the error msg is generated in RestImportHandler.cpp file (line: 927), but it's hard to understood the write logic (wasn't familiar with C++).
My Question:

the reason why throw creating document failed with error 'conflict'?
If the data rows is illegal, hope to provide the conflict conditions for fix error data?

Hope your reply, Thanks.

Hi, Please note that ArangoDB 3.6 has been EOLed for quiet a while now.
Please upgrade to at least ArangoDB 3.10 and check back whether the issue persists.

Thanks for your reply !
Arangodb 3.6.13 had been deployed on product environment for a long time, It's hard to upgrade graph database version.
Reduced the number of write threads to single one, the phenomenon creating document failed with error 'conflict' was disappeared.

V3.6.16 has been the last bugfix release; you should at least consider upgrading to that to get all possible bugfixes.
Closing this issue now.


issues.md file doesn't create at github actions

Should I Add another argument to the LAMS call?

Hi @barak-loc
If you're using LAMS v2, the markdown is no longer the default output mode. Instead, by default errors are output in a human readable to the command line, which you can view by just clicking the ">" expand icon in that screenshot.
(If you do want the old markdown behavior, you can use the --output=... argument, and include markdown as a value in that list. You may have to adapt the rest of your Github action code similarly to the old v1 examples)
I'll mark this as closed, but feel free to respond if you still have any doubts or questions and I will review & respond!

works, thank you


♻ Rework init for use in laminhub

https://github.com/laminlabs/laminhub/issues/1271
This moves all internal utility arguments to kwargs in lamindb_setup.connect.
Adds 2 additional arguments: _user and _write_settings.

_user allows to pass user settings (with access_token) to connect and they are used instead of lamindb_setup.settings.user.
_write_settings when set to False forces connect not to write any settings env files. It is set to True by default for now.

I believe this addresses point 1-2 in the linked issue.

@falexwolf @fredericenard this is ready for a review.

Thx, will address the comments.


Development server fails to start

yarn dev -o

After about 5 seconds,
FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal.
 1: 0x100f45260 node::Abort() [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]

 ERROR  [worker reload] [worker init]Package import specifier "#nitro" is not defined in package /Users/yuichi/Documents/github/longrun/nuxt3-app/node_modules/nuxt3/package.json imported from /Users/yuichi/Documents/github/longrun/nuxt3-app/node_modules/nuxt3/dist/core/runtime/nitro/paths.mjs

  at new NodeError (node:internal/errors:371:5)
  at throwImportNotDefined (node:internal/modules/esm/resolve:442:9)
  at packageImportsResolve (node:internal/modules/esm/resolve:819:3)
  at moduleResolve (node:internal/modules/esm/resolve:973:21)
  at defaultResolve (node:internal/modules/esm/resolve:1080:11)
  at ESMLoader.resolve (node:internal/modules/esm/loader:530:30)
  at ESMLoader.getModuleJob (node:internal/modules/esm/loader:251:18)
  at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:79:40)
  at link (node:internal/modules/esm/module_job:78:36)

 2: 0x100f453e8 node::errors::TryCatchScope::~TryCatchScope() [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
 3: 0x101095c94 v8::V8::ToLocalEmpty() [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
 4: 0x100f41518 node::fs::FSReqPromise<node::AliasedBufferBase<double, v8::Float64Array, void> >::Resolve(v8::Local<v8::Value>) [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
 5: 0x100f49d04 node::fs::AfterStat(uv_fs_s*) [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
 6: 0x1017b2aa4 uv__work_done [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
 7: 0x1017b6240 uv__async_io [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
 8: 0x1017c7fb8 uv__io_poll [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
 9: 0x1017b66d0 uv_run [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
10: 0x100e92ccc node::SpinEventLoop(node::Environment*) [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
11: 0x100fd7768 node::worker::Worker::Run() [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
12: 0x100fda990 node::worker::Worker::StartThread(v8::FunctionCallbackInfo<v8::Value> const&)::$_3::__invoke(void*) [/Users/yuichi/.nodebrew/node/v16.14.2/bin/node]
13: 0x1bb3fa26c _pthread_start [/usr/lib/system/libsystem_pthread.dylib]
14: 0x1bb3f508c thread_start [/usr/lib/system/libsystem_pthread.dylib]

So I'm avoiding it with build & start.

Somtime, This error may also be the case.
ℹ Vite server warmed up in 205ms                                                              14:10:46
ℹ Vite client warmed up in 681ms                                                              14:10:46
✔ Vite server built in 513ms                                                                  14:10:46
✔ Nitro built in 136 ms                                                                 nitro 14:10:46

 ERROR  [worker reload] [worker init]Package import specifier "#nitro" is not defined in package /Users/yuichi/Documents/github/longrun/nuxt3-app/node_modules/nuxt3/package.json imported from /Users/yuichi/Documents/github/longrun/nuxt3-app/node_modules/nuxt3/dist/core/runtime/nitro/paths.mjs

  at new NodeError (node:internal/errors:371:5)
  at throwImportNotDefined (node:internal/modules/esm/resolve:442:9)
  at packageImportsResolve (node:internal/modules/esm/resolve:819:3)
  at moduleResolve (node:internal/modules/esm/resolve:973:21)
  at defaultResolve (node:internal/modules/esm/resolve:1080:11)
  at ESMLoader.resolve (node:internal/modules/esm/loader:530:30)
  at ESMLoader.getModuleJob (node:internal/modules/esm/loader:251:18)
  at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:79:40)
  at link (node:internal/modules/esm/module_job:78:36)

Fixes https://github.com/longrun/tech-blog-vue3-nuxt3/commit/04c1ccfba046524dbfcec5d53084f231e276d953


dual transpiler

An essential item in your strategy should be to transpile from SQL back to PRQL. Since everyone coming to this project is looking for an alternative to their existing SQL, providing a transpilation back to SQL is an undeniable proof of concept. Even without knowing the ins and outs of SQL I could see that PRQL is the way forward, but if and only if it can reproduce my existing code.

Duplicate of #130, let's count your vote there.

@aljazerzen sorry for the noise, I did check the FAQ and the Roadmap and no mention. Perhaps add there too?

Good idea. We'll be discussing roadmap on the next meeting, I'll mention it there.


crash of recent (from June 13 2024 to present) nightly dev builts windows versions of cjxl and djxl

Describe the bug
A clear and concise description of what the bug is.
cjxl.exe and djxl.exe versions  (available in jxl-x64-windows-static.zip) in nightly dev builts from June 13, 2024 crash. Older versions (e.g. June 5, 2024) work fine
To Reproduce
Steps to reproduce the behavior:
For cjxl.exe  and djxl.exe versions from June 13, 2024
cjxl image1.jpg image1.jxl crashes
djxl image2.jxl image2.jpg crashes
but
cjxl -v does not crash and shows verbose as expected
djxl -v does not crash and shows verbose as expected
previous cjxl.exe and djxl.exe work normally
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots or example input/output images to help explain your problem.
Environment

OS:  Windows 10 pro 64

Additional context
Add any other context about the problem here.

Latest release (v.0.10.3) works fine !

Good news.
Perhaps will add some integration test to catch such problems earlier.

cjxl.exe and djxl.exe in the latest nightly dev. built, which was made available after v.0.10.3, continue to crash (and still displays v.010.2). It seems that nightly dev built is late with respect to the official release, which is a bit strange for me.
Beyond this minor point, congratulations for the fantastic work done so far !

Thanks for the report!
Just so I understand correctly:
cjxl image1.jpg image1.jxl
``
and

djxl image2.jxl image2.jpg
both crash at current head, but when you add `-v` to them they don't crash anymore? Or simply the commands

cjxl -v
djxl -v
without any furhter arguments than `-v` don't crash?

What I meant is, from nightly dev builts of June 13 (the previous version, from June 05, works normally)
cjxl image1.jpg image1.jxl crashes
cjxl -v image1.jpg image1.jxl crashes similarly
cjxl -v does not crash and provide verbose normally
Since these initial tests, I made additional one on another PC (also running under windows 10 pro)
The results are a bit different:
cjxl image1.jpg image1.jxl does not crash but generate no output (similar issue mentioned in #3690)
I also tested with a png input, either losslessly (-d 0) or lossy, and got the same issue: no output
The issue is still present for the nightly dev built of July 29
Example of messages
with cjxl 0.10.3
JPEG XL encoder v0.10.3 4a3b22d [AVX2,SSE2]
Note: Implicit-default for JPEG is lossless-transcoding. To silence this message, set --lossless_jpeg=(1|0).
Encoding [JPEG, lossless transcode, effort: 7]
Compressed to 223.9 kB including container
with cjxl nightly dev of July 29
JPEG XL encoder v0.10.2 f7f20ce [AVX2,SSE2]
Note: Implicit-default for JPEG is lossless-transcoding. To silence this message, set --lossless_jpeg=(1|0).
Encoding [JPEG, lossless transcode, effort: 7]
and the program ends without generating any output
Hope this helps

For what it’s worth, it seems to work fine for me on Windows 11.
Does running it through a debugger give any useful information?

I have just made additional tests on another PC, also running under Windows 10 pro. On this PC, no issue.
In summary, the latest nightly dev built versions of cjxl (and djxl as well) on windows 10 pro may crash,  or does not crash but generates no output, or works normally ... quite strange !

Another test with cjxl.exe from nightly dec built of June 29 on a 4th PC running under windows 10 family rather than 10 pro. In this case, no crash but no output file was generate (as in #3690)

We think that the latest nightly build, when it fails, shouldn’t do it silently anymore. Is that the case?

that commit (https://github.com/libjxl/libjxl/commit/18726bbad839c057107877e3654461dcb9759e2d) is still from last week, can you try a more recent one?

Thanks for checking!

Can you try again at current head?

@mo271
New test with the latest night version (August 30 2024), same issue: no output
cjxl image.jpg image.jxl
JPEG XL encoder v0.11.0 f28befa [AVX2,SSE2]
Note: Implicit-default for JPEG is lossless-transcoding. To silence this message, set --lossless_jpeg=(1|0).
Encoding [JPEG, lossless transcode, effort: 7]
... and exit
Recall: v0.10.3 and night version from June 05 work fine

Thank you. Would you be in a position to share one of the images that trigger the issue? Or does it not seem to depend on the image (e.g. on the machine on which it succeeded, did you use the same one)?

Thanks. This is very odd – I can’t reproduce the issue in a fresh 64-bit Windows 10 Pro VM either (also in French), provided that I install the latest Microsoft C++ runtime (otherwise it doesn’t start at all).
(Doing so wouldn’t happen to solve the issue, by any chance, would it?)

@sboukortt
Great suggestion. I installed the latest version of MS C++ runtime lib (14.40) on my computer, which had "only" the 14.36 one. And now the latest versions of cjxl and djxl work fine. I have still to test this on the other computer where cjxl and djxl did crash rather than exiting without generating any output (but only possible next week). If it is confirmed that this issue can only be solved by installing the latest version of MS C++ runtime lib, this should be indicated somewhere in the documentation.

Following #3803, installing them manually should not be necessary anymore:
$ x86_64-w64-mingw32-objdump -p before/bin/cjxl.exe | grep -i dll
DllCharacteristics      00008160
 vma:            Hint    Time      Forward  DLL       First
        DLL Name: KERNEL32.dll
        DLL Name: MSVCP140.dll
        DLL Name: VCRUNTIME140.dll
        DLL Name: VCRUNTIME140_1.dll
        DLL Name: api-ms-win-crt-runtime-l1-1-0.dll
        DLL Name: api-ms-win-crt-convert-l1-1-0.dll
        DLL Name: api-ms-win-crt-stdio-l1-1-0.dll
        DLL Name: api-ms-win-crt-string-l1-1-0.dll
        DLL Name: api-ms-win-crt-filesystem-l1-1-0.dll
        DLL Name: api-ms-win-crt-math-l1-1-0.dll
        DLL Name: api-ms-win-crt-heap-l1-1-0.dll
        DLL Name: api-ms-win-crt-environment-l1-1-0.dll
        DLL Name: api-ms-win-crt-locale-l1-1-0.dll
$ x86_64-w64-mingw32-objdump -p after/bin/cjxl.exe | grep -i dll
DllCharacteristics      00008160
 vma:            Hint    Time      Forward  DLL       First
        DLL Name: KERNEL32.dll

@sboukortt
I have just tested the latest version (3786&bb) on a machine running under windows 10 family with an "old" VC++ runtime lib and this works fine. Great job, thanks
(may be one should not close this post before next monday, when I will be able to test this new version on the computer where cjxl and djxl crashed ... even if I am quite confident it should work fine as well)

Can this be closed then?

@sboukortt
I think it is preferable to wait 3 days (i.e. until monday), when I will be able to test the computer where both cjxl and djxl crash. Currently I was able to test these programs only on computers where the issue was not a crash but no output generated


restRequest path option was deprecated, so it has to change to url.

I didn't realize path was deprecated, what's the rationale there? It was a girder restRequest-specific concept, why does it have to go away?

It was deprecated it in Girder PR #2273.  Perhaps @brianhelba or @jbeezley can explain why they both thought it a good idea.

With the deprecation and without this change, the javascript console is spammed with deprecation warnings (really, one would be enough).

I'm still not convinced the deprecation makes sense, has anyone come to its defense?


cross platform: fix stack/heap overflow (ulong)

ulong (unsigned long) is 4 bytes on Windows while 8 bytes on *nix.
There is/are routines within ChakraCore assume casting from double
to ulong and then reaching to second item [1] is safe. However,
this ends up corrupting stack/heap on *nix.
PAL has a definition for ULONG as (unsigned int) and ULONG is already
widely used. For this reason, replacing all the ulong to ULONG

Generally, this is fine. Couple comments:

Instead of replacing ulong, lets use uint32. We can leave existing instances of ULONG as is, but everywhere you've changed ulong, change it to uint32.
We need to do this for long as well (replace with int32)
In NumberUtilities, consider renaming FDblIsLong to FDblIsInt32.

+1 to avoid long/ulong/LONG/ULONG.
What do you think of int, uint? At least for some places? I understand int32, uint32 are safer. But int, uint look neater...

I'm ambivalent because we also have int64 already so int32 feels more natural, plus int is also not necessarily defined to be the same everywhere (in practice, in all platforms we care about it is, but we once thought the same about long too :smile:)

Okay. I was thinking about this whole night. IMHO lets keep this PR as is and as simple. This doesn't mean that I'm not agree with @digitalinfinity or @jianchun but read the reasons below;
Reasons
1- If we change all the instances of ulong, ULONG to int32, we need to deal with (additional casting, redefining etc.) on Windows for WINAPI
2 - The proposed change is so big, I'm not sure if we have the right reasons to do that? Apart from the look and feel, ULONG should be just fine to let us move on.
3 - If we are going to refactor one type to another, I prefer doing that on master instead of linux branch. Otherwise, we will be keep fixing and maintaining the type diff for all the upcoming merges from master.
4 - This PR/Commit fixes the problem it's after without introducing big changes. Even if we want to refactor all the types, they can be part of a separate and more controlled task. IMO we have more types to refactor.
Apologies for the long read..

As suggested the instances of ulong are replaced with uint32. However I found keeping ULONG matching with the usage on some places hence used ULONG there instead.
Updating long to int32 will be part of another PR so feel free to review this and merge.

@dotnet-bot test Ubuntu ubuntu_linux_debug Ubuntu ubuntu_linux_release please

@dotnet-bot test Ubuntu ubuntu_linux_release please


Reinstate cargo-semver-checks

Problem
Instead of running the checks on every commit, it would be okay to check SemVer compatibility every time a pull request to main is merged.
Proposed Solution
No response
Notes
No response

As cargo-semver-checks does not allow to pass the current version as a parameter, the checks had to be executed on the release-please branch. This however would interfere with the release-please bot. As the create is more or less tested and the version is determined by the conventional commits guidelines, cargo-semver-checks don't need to be reinstated.


qlib demo 运行问题

我从pip和source两种方式安装qlib，source方式显示了一个error，error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/，我把这个问题解决后，使用qlib.__version__可以正常显示qlib的版本，但是当我用命令运行demo（环境是win11 + anaconda），报如下错误：
$ qrun benchmarks/LightGBM/workflow_config_lightgbm_Alpha158.yaml
E:\anaconda\envs\demo\lib\site-packages\arctic_util.py:6: FutureWarning: pandas.util.testing is deprecated. Use the functions in the public API at pandas.testing instead.
from pandas.util.testing import assert_frame_equal
Traceback (most recent call last):
File "E:\anaconda\envs\demo\lib\runpy.py", line 193, in run_module_as_main
"main", mod_spec)
File "E:\anaconda\envs\demo\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "E:\anaconda\envs\demo\Scripts\qrun.exe_main.py", line 4, in
File "E:\anaconda\envs\demo\lib\site-packages\qlib\workflow\cli.py", line 12, in
from qlib.model.trainer import task_train
File "E:\anaconda\envs\demo\lib\site-packages\qlib\model_init.py", line 6, in
from .base import Model
File "E:\anaconda\envs\demo\lib\site-packages\qlib\model\base.py", line 6, in
from ..data.dataset import Dataset
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data_init_.py", line 8, in
from .data import (
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\data.py", line 20, in
from arctic import Arctic
File "E:\anaconda\envs\demo\lib\site-packages\arctic_init_.py", line 6, in
from .store.pandas_ndarray_store import PandasDataFrameStore, PandasSeriesStore, PandasPanelStore
File "E:\anaconda\envs\demo\lib\site-packages\arctic\store_pandas_ndarray_store.py", line 6, in
from pandas import DataFrame, Series, Panel
ImportError: cannot import name 'Panel' from 'pandas' (E:\anaconda\envs\demo\lib\site-packages\pandas_init.py)
(demo)
这是我安装qlib失败的问题还是demo 运行问题？

I think this is caused by the conflict between your newer version of Pandas  and the requirements of Arctic https://github.com/man-group/arctic/blob/master/setup.py#L82
But pip should have solved this issue.
Can you describe  steps to reproduce the error from a clean Python environment?

The steps are as below, and I will create a new python environment to check it.

create a clean conda environment, python 3.7(I see the demo is python 3.7)

Then, I first install qlib with pip, it succeed, but when I run the demo it has error:
$ qrun benchmarks/LightGBM/workflow_config_lightgbm_Alpha158.yaml
[20360:MainThread](2022-01-18 15:19:33,128) INFO - qlib.Initialization - [config.py:384] - default_conf: client.
[20360:MainThread](2022-01-18 15:19:33,138) INFO - qlib.Initialization - [init.py:57] - qlib successfully initialized based on client settings.
[20360:MainThread](2022-01-18 15:19:33,138) INFO - qlib.Initialization - [init.py:59] - data_path={'__DEFAULT_FREQ': WindowsPath('C:/Users/mujou/.qlib/qlib_data/cn_data
')}
[20360:MainThread](2022-01-18 15:19:33,138) INFO - qlib.workflow - [expm.py:282] - No tracking URI is provided. Use the default tracking URI.
[20360:MainThread](2022-01-18 15:19:33,138) INFO - qlib.workflow - [expm.py:318] - <mlflow.tracking.client.MlflowClient object at 0x000002116262ABC8>
[20360:MainThread](2022-01-18 15:19:33,178) WARNING - qlib.workflow - [expm.py:200] - No valid experiment found. Create a new experiment with name workflow.
[20360:MainThread](2022-01-18 15:19:33,188) INFO - qlib.workflow - [exp.py:249] - Experiment 1 starts running ...
[20360:MainThread](2022-01-18 15:19:33,429) INFO - qlib.workflow - [recorder.py:290] - Recorder 9cf5243040d4459faa05c44f6cd2961d starts running under Experiment 1 ...
Please install necessary libs for CatBoostModel.
Please install necessary libs for XGBModel, such as xgboost.
Please install necessary libs for PyTorch models.
[20360:MainThread](2022-01-18 15:19:33,689) INFO - qlib.timer - [log.py:113] - Time cost: 0.000s | waiting async_log Done
[20360:MainThread](2022-01-18 15:19:33,689) ERROR - qlib.workflow - [utils.py:38] - An exception has been raised[ValueError: can't find a freq from [] that can resample to
day!].
File "E:\anaconda\envs\demo\lib\runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "E:\anaconda\envs\demo\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "E:\anaconda\envs\demo\Scripts\qrun.exe_main.py", line 7, in
sys.exit(run())
File "E:\anaconda\envs\demo\lib\site-packages\qlib\workflow\cli.py", line 62, in run
fire.Fire(workflow)
File "E:\anaconda\envs\demo\lib\site-packages\fire\core.py", line 141, in Fire
component_trace = _Fire(component, args, parsed_flag_args, context, name)
File "E:\anaconda\envs\demo\lib\site-packages\fire\core.py", line 471, in _Fire
target=component.name)
File "E:\anaconda\envs\demo\lib\site-packages\fire\core.py", line 681, in CallAndUpdateTrace
component = fn(*varargs, **kwargs)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\workflow\cli.py", line 56, in workflow
recorder = task_train(config.get("task"), experiment_name=experiment_name)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\model\trainer.py", line 166, in task_train
exe_task(task_config)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\model\trainer.py", line 42, in exe_task
dataset: Dataset = init_instance_by_config(task_config["dataset"])
File "E:\anaconda\envs\demo\lib\site-packages\qlib\utils_init.py", line 305, in init_instance_by_config
return klass(**cls_kwargs, **try_kwargs, **kwargs)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\dataset_init.py", line 115, in init
self.handler: DataHandler = init_instance_by_config(handler, accept_types=DataHandler)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\utils_init.py", line 305, in init_instance_by_config
return klass(**cls_kwargs, **try_kwargs, **kwargs)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\contrib\data\handler.py", line 174, in init
process_type=process_type,
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\dataset\handler.py", line 389, in init
super().init(instruments, start_time, end_time, data_loader, **kwargs)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\dataset\handler.py", line 105, in init
self.setup_data()
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\dataset\handler.py", line 525, in setup_data
super().setup_data(**kwargs)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\dataset\handler.py", line 149, in setup_data
self._data = lazy_sort_index(self.data_loader.load(self.instruments, self.start_time, self.end_time))
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\dataset\loader.py", line 136, in load
for grp, (exprs, names) in self.fields.items()
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\dataset\loader.py", line 136, in
for grp, (exprs, names) in self.fields.items()
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\dataset\loader.py", line 211, in load_group_df
instruments, exprs, start_time, end_time, freq=freq, inst_processors=self.inst_processor.get(gp_name, [])
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\data.py", line 1023, in features
instruments, fields, start_time, end_time, freq, disk_cache, inst_processors=inst_processors
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\cache.py", line 408, in dataset
instruments, fields, start_time, end_time, freq, disk_cache, inst_processors=inst_processors
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\cache.py", line 743, in _dataset
inst_processors=inst_processors,
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\cache.py", line 900, in gen_dataset_cache
_calendar = Cal.calendar(freq=freq)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\data.py", line 100, in calendar
_calendar, _calendar_index = self._get_calendar(freq, future)
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\data.py", line 181, in _get_calendar
_calendar = np.array(self.load_calendar(freq, future))
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\data.py", line 620, in load_calendar
backend_obj = self.backend_obj(freq=freq, future=future).data
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\storage\file_storage.py", line 108, in data
self.check()
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\storage\file_storage.py", line 59, in check
if not self.uri.exists():
File "E:\anaconda\envs\demo\lib\site-packages\qlib\data\storage\file_storage.py", line 102, in uri
raise ValueError(f"can't find a freq from {self.support_freq} that can resample to {self.freq}!")
ValueError: can't find a freq from [] that can resample to day!
(demo)
I wan to see which line cause the error, but every line is from the externel lib.

So I think my installation failed before, then I install from the source way in the docs, it has the error:
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/, after I install visual-cpp-build-tools, I solve it, and I can import qlib and print its version

Then I run the demo, get the error presented before.

Did you follow the steps here  to download data?

I'm sorry I didn't prepare the data, but I think the demo video add this step could be better


apcupsd doesn't report Back-UPS ES 600M1 status correctly

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[x] The title contains the plugin to which this issue belongs

Describe the bug
Version 1.1 of apcupsd doesn't report status correctly for USB UPS models such as the APC BE600M1.  For example, MODEL and STATUS are missing, while others such as LOTRANS, HITRANS, and LOADPCT are incorrect:
root@smitingOfElves:/usr/local/etc/apcupsd  # apcaccess status <IP_ADDRESS>:3551
APC      : 001,033,0759
DATE     : 2023-02-06 22:48:50 -0500
HOSTNAME : <snip>
VERSION  : 3.14.14 (31 May 2016) freebsd
UPSNAME  : Back-UPS ES 600M1
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2023-02-06 22:27:28 -0500
MODEL    :
STATUS   :
LINEV    : 0.0 Volts
LOADPCT  : 0.0 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 65.9 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
SENSE    : Unknown
LOTRANS  : -1.0 Volts
HITRANS  : -1.0 Volts
ALARMDEL : Always
BATTV    : 0.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : NO
STATFLAG : 0x05000000
SERIALNO :
BATTDATE :
NOMINV   : 0 Volts
NOMBATTV : 0.0 Volts
END APC  : 2023-02-06 22:48:58 -0500

Per the install log, this is a known bug in apcupsd that requires an additional option in make config:
If connected via USB and apcaccess reports incomplete data consider enabling
the USB_REPORTING options via 'make config'.  This contains an experimental
patch that may fix some USB attach APC UPS. PR #249041

To Reproduce
Steps to reproduce the behavior:

Install apcupd via the plugin manager
Start a shell via ssh
Run apcaccess
Note missing fields from USB UPS
2-3 alternative - access the Services->Apcupsd->Status page

Expected behavior
Expected status should include all status fields:
root@smitingOfElves:/usr/local/etc/apcupsd # apcaccess
APC      : 001,036,0899
DATE     : 2023-02-06 23:17:54 -0500
HOSTNAME : <snip>
VERSION  : 3.14.14 (31 May 2016) freebsd
UPSNAME  : Back-UPS ES 600M1
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2023-02-06 23:17:52 -0500
MODEL    : Back-UPS ES 600M1
STATUS   : ONLINE
LINEV    : 121.0 Volts
LOADPCT  : 10.0 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 65.9 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
SENSE    : Medium
LOTRANS  : 92.0 Volts
HITRANS  : 139.0 Volts
ALARMDEL : 30 Seconds
BATTV    : 13.6 Volts
LASTXFER : Low line voltage
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : NO
STATFLAG : 0x05000008
SERIALNO : 4B2006P25428
BATTDATE : 2020-02-06
NOMINV   : 120 Volts
NOMBATTV : 12.0 Volts
NOMPOWER : 330 Watts
FIRMWARE : 928.a8 .D USB FW:a8
END APC  : 2023-02-06 23:17:55 -0500

Screenshots
N/A
Relevant log files
N/A
Additional context
A rebuild of apcupsd with USB_REPORTING enabled from this FreeBSD port commit fixed the issue in my instance.
Environment
OPNsense 22.7.11_1-amd64FreeBSD 13.1-RELEASE-p5OpenSSL 1.1.1s  1 Nov 2022
AMD GX-420CA SOC with Radeon(tm) HD Graphics (4 cores, 4 threads)
UPS model APC BE600M1

Looks like it's still not quite right even with USB_REPORTING on; it loses STATUS within a few hours.  This might be a problem with the upstream FreeBSD port rather than the plug-in though:
APC      : 001,037,0945
DATE     : 2023-02-11 13:43:00 -0500
HOSTNAME : smitingOfElves.private1.kyengineer.com
VERSION  : 3.14.14 (31 May 2016) freebsd
UPSNAME  : BE600M1
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2023-02-07 20:52:40 -0500
MODEL    : Back-UPS ES 600M1
STATUS   :
LINEV    : 119.0 Volts
LOADPCT  : 11.0 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 62.3 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
SENSE    : Medium
LOTRANS  : 92.0 Volts
HITRANS  : 139.0 Volts
ALARMDEL : 30 Seconds
BATTV    : 13.6 Volts
LASTXFER : Low line voltage
NUMXFERS : 2
XONBATT  : 2023-02-09 06:17:47 -0500
TONBATT  : 0 Seconds
CUMONBATT: 6 Seconds
XOFFBATT : 2023-02-09 06:17:52 -0500

This might be a problem with the upstream FreeBSD port rather than the plug-in though

Yes, I read reports that on Linux it works fine.
Did you build the package specifically for OPNsense or FreeBSD?
Otherwise, I think you should try with NUT instead.


Avoid always loading custom packs

The "sources" setting includes user-selected custom packs, so avoid auto-loading all of them, and instead de-reference their IDs against the known set of custom packs.

Warning: completely untested.


💄 Fix scrollbar on editor title input in Chrome on Windows

closes https://github.com/TryGhost/Ghost/issues/8866

add overflow: hidden to disable scrollbars on editor title input

Coverage remained the same at 73.391% when pulling 8cc6a79cab2a16dd9a5a4717ff26f0d94db82d62 on kevinansfield:fix-windows-chrome-editor-title into 7da3b55384d11e51d3568008f372c3eb73c6e509 on TryGhost:master.


figma file?

Hi!
Is there a Figma file available for Sakai? I've found one here https://sakai.primereact.org/ at the bottom of the menu, but it only has a few components.

Unfortunately not.


⚠ ClamAV has degraded performance

In e110414, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 75 ms

Resolved: ClamAV performance has improved in 1ab7833.


Added CodePen clone project

I have added a project CodePen Clone which is used for testing HTML, CSS and JS Code using React JS and Material UI.
Closes Issue #292

Noting is visible in this Pr.PLease chk once

Noting is visible in this Pr.PLease chk once

@Vikash-8090-Yadav now check if everything is alright?

Make the perfect readme, for reference check the frontend folder.

There's nothing in readme check once.

@Vikash-8090-Yadav now please check is readme visible or not?

Sorry, I couldn't make readme since I found that the text cursor gets disappear after every character. So, now closing this PR.


JB-543 - disable nfts that are sold out

What does this PR do and why?
Closes JB-543
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3826   👈

This comment was auto-generated by Graphite.


virt-operator: Remove explicit subresources permissions

What this PR does / why we need it:
The get verb permissions were only required for a short amount of time
to allow updates from v0.43 and can be removed.
The remaining update verb permissions are actually already included by
the call to getKubeVirtComponentsRules [1] when generating the
virt-operator ClusterRole.  This call pulls in all rules required by
KubeVirt for the operator to use as can be seen by looking at the
generated rbac-operator.authorization.k8s.yaml.in file [2] from a
previous commit to this PR.
[1] https://github.com/kubevirt/kubevirt/blob/c4b6ae63c5a7f642ab86b0755dabca3b814ecb39/pkg/virt-operator/resource/generate/rbac/operator.go#L339-L340
[2] https://github.com/kubevirt/kubevirt/blob/43aa19c2b5417c9843f6f7ed58125391cd79c6af/manifests/generated/rbac-operator.authorization.k8s.yaml.in#L510-L519
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cc @rmohr

/lgtm
Letting @davidvossel approve to have a second confirmation.

/lgtm


Kernel build setup issues

Greetings. I started looking into building a custom kernel for some testing purposes.
I cloned the packaging repo and followed instructions to run 'build-kernel.sh setup'.
I got the following error:

ERROR: failed to find /home/xzr/go/src/github.com/kata-containers/packaging/kernel/patches//../kata_config_version

I suspect the script expects some kind of directory structure to be in place for it to work properly.
I managed to make it work by creating the directory structure in the error and placing the configs folder and kata_config_version in their respective places from the repo. I also modified the script a bit to download the kernel source.
I feel the documentation and possibly scripting could be improved regarding this.

Thanks for raising @xzr!
Could you tal @jcvenegas?

@xzr thanks for create the issue yes, the scripts expect the config and patches be in your gopath
so expect we download the repository doing go get, It make sense to find the patches in a relative directory to the script.

Thanks for the quick reply @jcvenegas !
It's not quite clear what to set the GOPATH variable to though.
I reckon the most common use case for someone trying to rebuild the kernel is that they just clone the packaging repo and follow the instructions. Currently there's no mention about setting up the directory structure in a certain way.


spelling: unpredictable

This fixes some misspellings in Swift test/Sanitizers, it is split per https://github.com/apple/swift/pull/42421#issuecomment-1101092698

@swift-ci smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


Excel resource with multiple worksheets

I'm interested in how people are applying the spec to the case where an Excel workbook (.xlsx) has tabular data in multiple worksheets.
I see this issue (https://github.com/frictionlessdata/datapackage/issues/793) which suggests specifying the sheet name in the dialect attribute. The example provided makes sense but only if there is a single worksheet in the file. I've been considering a case like this:
{
  "profile": "tabular-data-package",
  "resources": [
    {
      "name": "mydata",
      "path": "mydata.xlsx",
      "dialect": {
        "sheet": "sheet1"
      },
   {
      "name": "mydata",
      "path": "mydata.xlsx",
      "dialect": {
        "sheet": "sheet2"
      }
    }
  ]
}

But in the above case there are two resources with the same name and path. I'm not even sure the worksheets should be considered separate resources, as my understanding is that in general a resource corresponds to a single file. I suppose this is not limited to Excel, as there are other file types where multiple tables can be saved in a single file.
I'm very interested if/how others have dealt with this situation. Examples would be very appreciated!

as my understanding is that in general a resource corresponds to a single file

I would say instead in general a resource corresponds to a single table.
When a format stores a single table per file, then yes, there's a 1-1 relationship between resources and files. But in the case of spreadsheets (and databases), where multiple tables are stored in a single file, you'll end up having multiple resources (one for each table) defined using that same file. So the example definition you shared looks good to me!
One thing to be aware of -- version 2 of the datapackage standard uses sheetName instead of sheet. I believe at some point this will be implemented in frictionless-py, but I'm not sure what the timeline is/will be.

Oh oops, I didn't notice the resources in your example also have the same name! You'll want to make those unique within the data package. A naming scheme something like this would do, for example:
{
  "profile": "tabular-data-package",
  "resources": [
    {
      "name": "mydata-sheet1",
      "path": "mydata.xlsx",
      "dialect": {
        "sheet": "sheet1"
      },
   {
      "name": "mydata-sheet2",
      "path": "mydata.xlsx",
      "dialect": {
        "sheet": "sheet2"
      }
    }
  ]
}

Thank @khusmann thinking of a resource as a table instead of a file makes perfect sense, I'll go with something like your example.


Remove automatic dependency updates

Currently the Kuksa approach is to update dependencies (except security related) manually, i.e. we will not updated Linux or Python version just because a new version exists, that is rather a deliberate decision. Currently kuksa.val.services is the only repo where we have general dependency updates, and that does not really makes sense. So I suggest that we remove it for kuksa.val.services
The result of this change is that PRs like #80, #93 and #93 not will be created.
Security-related dependencies may still be updated, that is handled by a separate mechanism.

@SebastianSchildt - any objections removing the automatic dependency updates? Based on previous discussions in team it seems that we do not want it, i.e. we want to stay on a specific Ubuntu/Alpine/python version until we deliberately want to change