Feature/qt clang integration

Motivation for this change
Starting with version 4.7 clang code model is the default method for supporting QOL services as is:
code completion, syntactic and semantic highlighting, diagnostics with fixits and integrated Clang-Tidy and Clazy checks, follow symbol, outline of symbols, tooltips, renaming of local symbols.
For future releases of qtc clang code model support is esssential need.
Things done

Clang:

Added clazy plugin compilation
Patched clazy CMakeLists.txt for compilation only as plugin in clangtree.
Patched clang driver to include anchors for clang-tidy and clazy plugins this changes still not in trunk for llvm8. Links: archlinux bugtracker, qtc fork of clang

QtCreator:

Updated 4.6.2 -> 4.9.0 (removed by rebase)
Added llvmPackages
Pathched regexp for includes path of clang lib++ (to include paths like libc++-version/include, was libc++/include)
Added llvm/clang dependencies for clang code model
Added substitutes to clang clang*.pr* for qmake to find llvm/clang libraries and includes
Added substitutes to correct clazy plugin name. Bug in archlinux tracker

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

How clang-tools and clang-code-model functionallity was tested

Create shell.nix:

with import <nixpkgs> {};

{
  environment = stdenvNoCC.mkDerivation {
    name = "dev_environment";
    buildInputs = [ qt5.full qtcreator cmake gcc8 clang_8 gdb boost libpqxx xterm bashInteractive llvmPackages.libcxx];
  };
}

Clone test project
Launch nix-shell: nix-shell -I nixpkgs=../nixpkgs --pure --keep LD_LIBRARY_PATH
nixpkgs path is path to my nixpkgs fork with this changes.
Launch qtcreator: qtcreator, if debug of clang-model is needed: QT_LOGGING_RULES=qtc.clang*=true LIBCLANG_TIMING=1 qtcreator
In settings create 2 kits: 1 for clang and 1 for gcc,
Test that project is successfully building with this kits. And that after opening c++ source file there is no popups with errors.
Launch clang tools analysis (In top menu Analysis->Clang-Tidy and Clazy...->Analyze) and check that there is warnings from diagnostic and no errors in application output tab 11:40:47: Clang-Tidy and Clazy finished: Processed 3 files successfully, 0 failed..

Update:
Rebased and tested on 03 june 2019 - reason is qtcreator was updated to 4.9.1 in master.

As i am still newbie to nix and nixos, i have some doubts:

Is it ok to depend on specific version of llvm libraries?
Is it ok to add depends for compiler or should is resolve qtc need for clang plugins some other way?
What is preffered method to change package sources? Instead of substituteInPlace i may create another .patch file.

Is it ok to depend on specific version of llvm libraries?

For something like qtcreator it is probably okay. Usually there are tight version constraints on apps like this anyway.

Is it ok to add depends for compiler or should i resolve qtc need for clang plugins in some other way?

This should be fine. Sometimes we can add runtime search paths for this kind of thing but llvm should be okay.

What is preferred method to change package sources? Instead of substituteInPlace i may create yet another .patch file.

.patch should definitely be used if you have something that is upstreamable. substituteInPlace is probably ok for cases like this where you are putting output paths in the source code. Ideally, packages would have configure options to set things like this (for instance, location of llvm), but it's not always worth maintaining.

Is there a name convention for .patch files?

No, but maybe there should be. If there's an upstream version, try to keep that name though.

Is it ok to depend on specific version of llvm libraries?

For something like qtcreator it is probably okay. Usually there are tight version constraints on apps like this anyway.

Is it ok to add depends for compiler or should i resolve qtc need for clang plugins in some other way?

This should be fine. Sometimes we can add runtime search paths for this kind of thing but llvm should be okay.

What is preferred method to change package sources? Instead of substituteInPlace i may create yet another .patch file.

.patch should definitely be used if you have something that is upstreamable. substituteInPlace is probably ok for cases like this where you are putting output paths in the source code. Ideally, packages would have configure options to set things like this (for instance, location of llvm), but it's not always worth maintaining.

Is there a name convention for .patch files?

No, but maybe there should be. If there's an upstream version, try to keep that name though.

Thank you for your answers.

Removed patch for botan, it's deprecated.

ping @matthewbauer

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review-may-2019/3032/5

After thinking some more about this: @deadloko maybe we should just build Qt's Clang fork separately? I feel that all this patching is quite flaky and more problems may possibly come later (maybe Qt Creator would expect additional information from clazy or something else). OTOH the fork is guaranteed to be good and doesn't require all this patching. One downside is additional compile time and a separate Clang (but I feel closure sizes aren't a problem for Qt Creator).

@abbradar This is one of possible solutions for this. I'll invest some more time to see if it's possible, cause i've never tried to build qtc with qt version of llvm. I'm still have little experience with nix expressions, but, hopefully, i won't need to to write them from scratch. I'd like to have some advice on:

Where should .nix files for this fork reside (pkgs/development/compilers/ is the location that i have in mind)? And how should i name it?
Is it ok to override llvm,clang, etc... for this fork (I think it should be able to build just fine with just src attribute override) or should i use some different approach?

If just an src override to clang would be enough (try it!) I'd put it into a let in Qt Creator's expression. BTW do they have a customized version of LLVM too? I'd try to build just Clang fork first, using system LLVM.

They have whole llvm project (llvm, clang, clang-tools-extra) forked, but i think system LLVM should do just fine.

Little update:
I managed to build clang as qtcreator runtime dependency for clazy and clang-tidy analysis, but i need some time to test it.
Unfortunately clang-lazy -> clazy patch still needed. They fixed it in qtcreator development tree, but it didn't make it into 4.9.1 release. So i would just add comment about it.

@abbradar I would appreciate if you review new changes.

@deadloko I tried to build it but got invalid checksum errors for patches, which is a bad sign:
hash mismatch in fixed-output derivation '/nix/store/6az7n3nyaz6nks71a7z0jhv9mld8lj10-clangtidyclazyrunner.cpp?id=53c407bc0c87e0b65b537bf26836ddd8e00ead82':
  wanted: sha256:1nqpwc6b421rvwv64wbpfaykv7fxrn9r1qrw1xf6cl5hqhnw7y93
  got:    sha256:1rl0rc2l297lpfhhawvkkmj77zb081hhp0bbi7nnykf3q9ch0clh

Can you try redownloading them? I think there was a better way than collecting garbage and building it again recently but not sure.

@abbradar  I fixed hashes for patches, but it's strange behavior.

@abbradar I've tested build on another machine (NixOS too). Build still succeedes.

Sadly I lost ability to build this because I needed to RMA my CPU :D If someone could just build it and verify it starts at least I'd merge.
On June 7, 2019 11:49:29 AM GMT+03:00, Andrew Newman<EMAIL_ADDRESS>wrote:

@abbradar I've tested build on another machine (NixOS too). Build still
succeedes.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/61348#issuecomment-499808476

--
Nikolay.

@abbradar Well, that's unfortunate, hope your cpu replacement soon. =) Also can't you ask borg bot to build this one?
@danieldk @matthewbauer @Ericson2314 may i ask you to provide aid on this one?

I'd just like to run it too but I as I can't and you tested it - let's just check that it builds
@GrahamcOfBorg build qtcreator

Bot's timeout kicked in ;_; Can someone try to build this?

Let's not keep this stalled - you tested it on two machines so this should be enough. Merging, thanks!

For me this version 4.9.1 (on one machine) fails to start with (works fine on another): qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
I want to help but I'm not sure what information to provide here, seeing as working on one but not on another is pretty much against Nix fundamentally (irrespective of versions).

@deadloko I'm trying to update qtc to 4.10.0 but I'm not sure what all needs to change here. Could you list some expected changes and tests (I see one detailed testing procedure you've mentioned in the original comment) that would help me change with enough confidence to create a PR?
Some info if it helps- currently just downloading 4.10.0 gives me a patch already applied error for the accompanying patch, and without it a linking error after an hour of compilation.

@SRGOM There was 3 patches (and some substitutions in nix expressions):

In-tree 0001-Fix-clang-libcpp-regexp.patch - needed for correct clang stdlib support, i assume this is still needed.
Two patches from qtc team to properly compile clazy - most definitely not needed anymore, cause 4.10 should include them.

More info on linking error (console output) would help to solve problem.


Leave comments on published PR to say where they were published

Details

Simplify publish workflow to remove the unnecessary "PR dance" and have OSBotify push new version straight to main. Branch protections were updated accordingly in https://github.com/Expensify/App/issues/38113
Leave a comment on the merged PR to say what version it was published in

Related Issues
didn't create an issue, but the main problem I'm trying to solve is that if an Onyx PR causes a regression it's not obvious which Onyx version is "poisoned", and it takes some investigative work (looking at tag diffs) to figure out what version the PR was published in.
Automated Tests
n/a
Manual Tests
Merge this PR and verify that the publish workflow works as expected and a comment is left on the PR.
Author Checklist

[x] I linked the correct issue in the ### Related Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Created https://github.com/Expensify/App/issues/38113 to update branch permissions

Reopened https://github.com/Expensify/App/issues/38113, but without access to the settings it's hard for me to diagnose


Settings redesign

Main Settings Page
https://user-images.githubusercontent.com/4467863/55691826-bbdf7c00-5967-11e9-87a5-90d34fbae3fc.png
fixes https://github.com/btelman96/letsrobot-android/issues/121

fixes https://github.com/btelman96/letsrobot-android/issues/132

Not sure how to remove duplication issues. I am fine with how the code currently looks, although it would be nice if it was better


[SVTPage] Fix extractor

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

SVT News changed its API similar to SVTPlay
Previously downloading a video resulted in 404 Error (because of api change somewhere in September 2023)
This commit fixes SVTPage extractor to use a new api
Added a new tests and added only_matching tag for the old ones (because videos for the old articles is unavailable anymore)
Fixes #8930
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

@bashonly thank you for your review and for your code snippets, that was really helpful.
And sorry that it took so long for me to update the code.


Changelog and readme updates for the 2.0.0 release

README: update
Includes:

Adding a warning about the TestListener polyfill not (yet) being compatible with PHPUnit 10.
Adding links to the documentation of some assertions, which are documented in the PHPUnit 10 documentation, but were previously undocumented.
Updating all links to the PHPUnit documentation to point to the PHPUnit 10 docs instead of the PHPUnit 9 docs.

Changelog for the 2.0.0 release
Includes updating the VERSION constant in the Autoload class.
Includes minor punctuation fixes to older changelog entries.

coverage: 96.247%. remained the same when pulling f10450976d430fcec0c376fce84d1b6252daf2ca on 2.0/update-readme-changelog into 1521f984953f368f21caeb36dcc2f91d3bc635b0 on 2.x.


Update .travis.yml

Update Go versions and add go_import_path so that Travis can work on forks.

Please follow the format example in the prometheus repo.


add global loader + route loader

Added UX for low latency network

Pre loader (in index.html ~ 2.3kb once builded) which display a loader until the application is ready to start
Smooth loader while lazy loading new routes

Steps to reproduce:

go to the backoffice on chrome
open chrome web developer
go to network tab > switch the throttling selector to "Regular 3G ..."
refresh the backoffice
navigate through pages

there is a css style minified in the index.html file, it's because webpack doesn't compile inline styles on npm run build

Current coverage is 86.69% (diff: 50.00%)

Merging #60 into develop will decrease coverage by 0.21%

@@            develop        #60   diff @@
==========================================
  Files            62         62
  Lines           970        977     +7
  Methods          23         23
  Messages          0          0
  Branches         80         80
==========================================
+ Hits            843        847     +4
- Misses           96         99     +3
  Partials         31         31

Powered by Codecov. Last update 052f00a...6eaa8e4

+1


Maintain a version field, similar to upstream info

Something to consider.
kpt has a nice scheme for versioning packages using tags:
https://kpt.dev/book/03-packages/08-publishing-a-package
However, I'd also like to version variants generated from a cloned package. They specify the version of the upstream package they were derived from, in upstream info, but not their own version.
I tried to use an annotation on the Kptfile to track versions, but without special merge handling, it frequently gets clobbered or conflicts on updates by changes to the version annotation in the upstream package. So, at present, I need to choose a different version annotation key for each level of the derivation tree.
kpt pkg get is like git clone. kpt is missing something like github fork. In the case of versioning, it would give the variant its own version number independent of the upstream package.
This could be added in a layer on top of kpt, similar to how github is a layer on top of git, but it may be worth thinking about a first-class variant-spawning model.

That distinction may apply to other Kptfile fields also, such as functions. Need to think more about inheritance chains though

I think inheritance chains should work, by either replacing or combining upstream and downstream sections, as appropriate.
For instance, upon kpt pkg get and update, upstream functions (new section) and downstream functions (the current pipeline) could be combined into the upstream section of the downstream clone.
This approach could help with #2529.


feat: add i18n support for catalog-import plugin

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

ping


fix duplicate tob and cox loot tracker

closes #4754 for both ToB and CoX

why is this storing looted status in the config?
why are you commiting client jars to the repo?


Hyperledger Fabric WebAssembly chaincode Proposal

+1!

LGTM +1

@kleash could I ask you to squash this into one commit? I'm willing to merge at that point

@ryjones done. squashed all commits into one
Thanks


Node 10.5.x compatibility on CI for tests

Summary
Fixes https://github.com/facebook/jest/issues/6529
jest.mock('fn') does not seem to include fs.ReadStream or fs.WriteStream in the resulting mocked module. This updates the tests to specify them in the mock.
I'm assuming larger work is required in jest-mock to address this directly.
Test plan
All tests pass locally on 10.5.x

Thanks!
While this is better than failing CI, we should probably report it. Maybe it's https://github.com/nodejs/node/pull/20764?

@SimenB ah yeah good call. That does seem relevant.

Codecov Report

Merging #6532 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6532   +/-   ##
=======================================
  Coverage   63.85%   63.85%
=======================================
  Files         234      234
  Lines        8800     8800
  Branches        3        4    +1
=======================================
  Hits         5619     5619
  Misses       3180     3180
  Partials        1        1

Continue to review full report at Codecov.

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

Opened up issue with Node: https://github.com/nodejs/node/issues/21489


archive/tar: Write too long on Windows

OS: Windows 10
Shell: PowerShell Core 7.1
Version: 0.3.6
On Windows, I am running into the following error message when attempting to download a newly-created lambda from my VPS:
PS> cgi-ctl download -l admin -p <mypassword> -u https://<mydomain>.dev -U 93470b46-f74a-4352-9c74-c7bbbfdd5eb9
2021/01/23 07:48:28 login...
2021/01/23 07:48:28 download...
download: -30000: archive/tar: write too long

Is there some combination of options that immediately strikes you as odd here, using SSL and being on Windows maybe?
According to some research this seems to be a common issue in Go, but I have 0 knowledge about the language. If you were to make a release with more verbose error handling then I could provide a more detailed error description :)

Thank you very much for the properly formatted issue!

Code -30000 means that error arrived from RPC, that means exception happen on server side. Could you please give output of sudo lsb_release -a on server? It should print detailed information about OS.
Is it possible that your lambda wrote something on disk during download operation?

Thank you very much for the properly formatted issue!

Code -30000 means that error arrived from RPC, that means exception happen on server side. Could you please give output of sudo lsb_release -a on server? It should print detailed information about OS.
Is it possible that your lambda wrote something on disk during download operation?

Hello, I am having the same problem in a docker setup.
I can successfully download from all newly created templates, except python's.
If I manually delete the venv folder, it works.
Any ideas on how to solve that?
Thanks for this amazing project!


[c++] Move installed header files one level deeper

Issue and/or context:
#1331
Changes:
Move installed header subdirectories into include/tiledbsoma.

Looks good (in a 22.04 container):
/usr/local/include/
└── tiledbsoma
    ├── soma
    │   ├── logger_public.h
    │   ├── managed_query.h
    │   └── soma_array.h
    ├── tiledbsoma
    ├── tiledbsoma_export.h
    └── utils
        ├── array_buffers.h
        ├── arrow_adapter.h
        ├── carrow.h
        ├── column_buffer.h
        ├── common.h
        ├── logger.h
        ├── span
        │   └── span.hpp
        ├── stats.h
        ├── util.h
        └── version.h

4 directories, 15 files
root@b5576e479e01:/work#

Codecov Report
Patch coverage has no change and project coverage change: -11.96 :warning:

Comparison is base (acc4ddd) 65.35% compared to head (a6acfb8) 53.40%.

:exclamation: Current head a6acfb8 differs from pull request most recent head 76ff1ec. Consider uploading reports for the commit 76ff1ec to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1338       +/-   ##
===========================================
- Coverage   65.35%   53.40%   -11.96%
===========================================
  Files          91       61       -30
  Lines        7603     5187     -2416
===========================================
- Hits         4969     2770     -2199
+ Misses       2634     2417      -217

Flag
Coverage Δ

python
?

r
53.40% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 30 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


HTMLRenderer inline mode fix

Proposed changes
Fix the issue with inline floats in read-only mode.
Types of changes

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

Checklist

[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Closing issues

#918

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

v2.0.0
GitHub release

Your semantic-release bot :package::rocket:


New paper request

Can you please add our diffusion paper on medical image reconstruction to your repository.
Learning Fourier-Constrained Diffusion Bridges for MRI Reconstruction

It is now added. Thank you!


Rewrite DynamicValue error handling to Validate

Due to the fact that most if the zio-schema codebase is using Either, there must be .toEither.left.map(_.toString) on the edge.
I've tried to going further than that, but it would require changes in the whole codebase.
Requires: https://github.com/zio/zio-json/issues/771
Fixes #480
/claim #480

@andrzejressel I modified the bounty to $150, can you push Validation all the way through so we can benefit from these accumulated errors past the edge?

Fortunately it does not look that bad in diff view. I have to rewrite examples and add do changes on zio-json and zio-bson

Since I don't have so much time anymore and ZIO-JSON seems to not like accumulation: https://discord.com/channels/629491597070827530/733728086637412422/1113027920420675674 - I'm closing this MR.


How pump inertia and rotation speed relate to the TSNet pump operation parameters

Is there a way to relate pump inertia and rotational speed with pump shutoff/startup period, end open percentage, and the constant? Thanks
Hailiang

TSNet simulates controlled pump operations (shutoff/startup), not shut down due to power failure (for now).
During the controlled operation, the pump operation is defined by the operation curve which characterized how pump speed changes with time, so pump inertia and rotational speed do not come into the picture.
However, if the pump shutdown is due to power failure, then the operation curve(pump speed v.s. time) will be dependent on the pump inertia and rotational speed.

@glorialulu that´s mean the start and shut down controlled could be perform by TSNet.
is that correct?
Also, is possible the shut down due to power failure could be represented including a valve and close very rapidly?
make sense to you?


Reference.read default page size

This PR, adds default value for page size in read function.
If the limit is not defined, it will look for page_size in Table Display annotation, using the current context. Otherwise, it will use "1" as a default page size.
Related Issue: #177

These changes are not relevant anymore.
We decided to not change the default value explicitly, and just expose the default page size as reference.display.default_page_size .


Add a pull request for any problem from Udacity

Updated:
Please add a solution to any problem that you solved on Udacity. Beginners with Git are welcome to add their solution and they may reference this isssue. It stays open so others can come and contribute. Please follow the guidelines in CONTRIBUTING.md while submitting the solution.

Can I help you with this?

Is this still available?

@ows-ali  Can you please explain this issue! I'd like to work on this! Thankyou ;)

is this issue still open? I would like to work on this issue!

ankita0025

is this issue still open? I would like to work on this issue!

yes you can

pls give me chance to do this work i am only here to for learning new thing plss alow me

Hello I am new to open source contribution. Can I please work on this?

Hi! Can I work on this?

can you assign this issue to me

### Is this project is ongoing? Let me know further (DOCS) to contribute on it as "good first issue".

still open ?

Eager to contribute to this project. Kindly assign it to me

/assign


Added compiled variables.tf.json (fix #7)

Terraform version 0.7.* has slightly different behaviour when running terraform get, because it expects:

variable all_amis to be defined
variable all_amis to have value (default or real content)

Now there is a real variables.tf.json, so regeneration of it is not required any more.

Fix for #7

Its probably worth nothing that there still isn't a us-east-2 ami in their JSON file, even though there are ones available in the marketplace.  Not sure when that will be addressed, I was tracking it here: https://github.com/coreos/bugs/issues/1623

Not sure if it would be worth hand coding it?


Cancel ActionPlan

Hi,
What would be the best way to cancel an actionPlan ?
For example, I have a signup screen when I tap the signup button it start a networking call. Now the user is impatient and close the signup screen before the network call finishes. How can I cancel the signUpActionPlan in the view disappear callback ?

There isn't a direct way to cancel a running action plan, but it would be nice to provide some kind of mechanism to support it. The library itself wouldn't be able to do much more than unsubscribe from the optional publisher returned from an action plan, so any internal details of the plan would need to be performed by the developer if needed.
Ideally, I could see the action dispatcher returning a cancellable subscription object when an action plan is performed.
Here's a rough solution I threw together for the interim. Instead of returning a publisher in the action plan it subscribe directly via sink. It then passes the cancellable object to the view as a @State object via a closure.
func signUpActionPlan(username: String, password: String, canceller: (AnyCancellable) -> ()) -> ActionPlan<AppState> {
  ActionPlan<AppState> { store -> () in
    canceller(webAPI.signUp(username: username, password: password).sink { newUser in
      store.send(UserAction.setCurrentUser(newUser))
    })
  }
}

struct MyView: View {

  @MappedDispatch() private var dispatch

  @State private var username: String = ""
  @State private var password: String = ""

  @State private var signUpCancellable: AnyCancellable?

  var body: some View {
    Group {
      /// ...signup form
      Button(action: self.signUp) { Text("Sign Up") }
    }
    .onDisappear { self.signUpCancellable?.cancel() }
  }

  func signUp() {
    dispatch(signUpActionPlan(username: username, password: password) {
      self.signUpCancellable = $0
    })
  }

}

This would solve my issue ! What do you think about having :
view get a [Cancellable] or a "disposeBag"
dispatcher returns Cancellable?
If a cancellable is returned the action is cancellable otherwise not.
View can then, at the library level, save automatically the cancellable if not nuls.
Maybe the api would be cleaner with always returning a cancellable but with an empty cancel function.

I like the idea of returning an AnyCancellable, which can act as an auto-disposable entity similar to using a DisposeBag by simply adding an array to the view via @State. I don't want to require developers to handle the AnyCancellable for every dispatch they perform though.
This may require a new interface to explicitly dispatch action plans that return a cancellable object separate from the existing API.

I added a new method to ActionPlan called sendAsCancellable(_:) to avoid a major refactor that might present a lot of break changes.
You pass the dispatch function from @MappedDispatch to it, and it'll return a new cancellable object:
let actionPlan = signUpActionPlan(
  username: username,
  password: password
)
self.signUpCancellable = actionPlan.sendAsCancellable(dispatch)

It's included in v0.11.2.


Domain Entities - Concrete or Interfaces

https://www.google.com/search?q=interfaces+of+domain+enttiies&oq=interfaces+of+domain+enttiies&aqs=chrome..69i57j0l6j69i61.3560j0j7&sourceid=chrome&ie=UTF-8

https://softwareengineering.stackexchange.com/questions/364431/is-it-acceptable-for-a-domain-entity-to-implement-an-interface


CLOUDSTACK-8606: DB performance impacted due to VM sync.

VM sync. generates a lot of queries on vm_instance table with 'instance_name' as filter. Since the field is not
indexed, these kind of queries will impact DB performance. Added an index for instance_name field.

Nice one! LGTM

@wilderrodrigues Could you please have a look at this PR?

Just had a look. LGTM. Please proceed with the merge.
Cheers,
Wilder


Don't panic when a http.ResponseWriter does not implement CloseNotifier

Instead, provide a variant of instrumentedResponseWriter that does not
implement CloseNotifier, and use that when necessary. In
copyFullPayload, log instead of panicing when we encounter something
that doesn't implement CloseNotifier.
This is more complicated than I'd like, but it's necessary because
instrumentedResponseWriter must not embed CloseNotifier unless there's
really a CloseNotifier to embed.
Closes #828

LGTM

LGTM


WIP: feat(cinema): add Cinema support (file explorer and db explorer modules)

Need to:

Choose an icon
Decide whether this way of cloning the Files module to CinemaFiles is right, or if we should add our changes directly to the original module.
Handle disconnection ?

@NicolasVuaille @mcmigliore


DO NOT MERGEEEEEEEEEEEEEEE

This pull request could not be merged.
Executed by: 0xaf0a837d2c709d33edfd1439e3e0bbc9ac18606b
Transaction hash: 0x2763746b498985246776e62f6dccb33cf8471fcf917f88f5a8834c4a5773188e
Error: Error: Pull request is not mergeable: (SecureSECODAO/SecureSECOPullRequestMerger#12). Mergeable = true, State = blocked


Added encoding support for decimal objects

fixes #4157

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[x] Run pre-commit hooks and fix any issues.

Ill change it to float real quick

hey, can anyone review the changes ?

it's been just 2 hours. people have a real life as well.

I'm sry i thought things are fast around here.

that's usually the case. but as a maintainer this type of comment actually lowers the motivation to review a PR.

okay, Ill keep that in mind. I'll make sure I wont ask around for reviews again. Again I'm sorry if that offended you in anyway


installer ISO incorrect when created via docker run

Issue
There are two ways to get an installer ISO:

make installer-iso in the eve repo, useful to developers, but slow
docker run lf-edge/eve:<version> installer_iso > installer.iso  which is the "official" pre-built way to get it

However, as of the revamp of the installer in #4248 (and some follow-ons), the docker run gives an incorrect ISO. It is bootable, but the grub menu is wrong, and it does not install correctly. The make installer-iso does work.
Cause
When we run make installer-iso, the following happens:

cat installer.tar | make-efi installer (this is make-efi from the image mkimage-iso-efi)
make-efi does cd to a working directory and then tar xf -, i.e. it lays out everything from installer.tar
make-efi creates the EFI boot partition file in the same directory
make-efi calls xorriso to create the ISO from the contents of the working directory

Conclusion: The ISO includes the contents of installer.tar plus the EFI boot image it creates.
When we run docker run lfedge/eve installer_iso, the following happens:

the entrypoint to lfedge/eve is runme.sh so that runs runme.sh installer_iso
runme.sh runs /make-efi installer. This is the same make-efi from the image mkimage-iso-efi, just loaded into the lfedge/eve image when it was built.
make-efi already has /bits and no stream in stdin, so it uses the content of /bits (instead of the layout from installer.tar) for its working directory contents
make-efi creates the EFI boot partition file in the same directory
make-efi calls xorriso to create the ISO from the contents of the working directory

So the process is similar, the problem is the incorrect contents in the docker run scenario.
The installer.tar does not exist inside the lfedge/eve docker image. However, the installer.img is a squashfs with the same contents, and unsquashfs utility exists, so we could probably use that, if we modify make-efi in a way that works correctly.
Proposed Fix
Change runme.sh (the entrypoint in lfedge/eve) that when it calls installer_iso, it changes from:
do_installer_iso() {
  rm -rf /parts
  /make-efi installer
  dump /output.iso installer.iso
}

to:
do_installer_iso() {
  rm -rf /parts
  mv /bits /bits.orig
  mkdir /bits
  (cd /bits && unsquashfs /bits.orig/installer.img)
  /make-efi installer
  dump /output.iso installer.iso
}

make-efi (from the other image) already has logic that says, "if I have /bits, use the contents of that directory, else read stdin". We take advantage of that to move everything out of /bits, get a clean /bits, and load it with the contents of installer.img. That will then have the same contents as if we did cat installer.tar (which we cannot do, because installer.tar is not available. The rest should flow.
I admit, it is a bit messy, but make-efi is used for a lot of different things, and I am wary of changing it to always read stdin. If we could do that, I would remove the entire "read /bits" part of make-efi, and make the runme.sh to just be:
do_installer_iso() {
  mkdir /installerdir
  cd /installerdir && unsquashfs /bits/installer.img
  tar -C /installerdir -cf - | /make-efi installer
  dump /output.iso installer.iso
}

@OhmSpectator @yash-zededa @eriknordmark @christoph-zededa you all had commented on the rework of installer. Can I ask you to take a look at this issue? I am fine doing the fixes, I do want to get comments on the thoughts in the issue before I plow ahead.

Update: I did a long look through eve. The only places that we use make-efi are the following:

directly from within lfedge/eve, i.e. in runme.sh - as referenced above
in the image itself as the entrypoint to lfedge/mkimage-iso-efi

Following the second route, I looked for all references to mkimage-iso-efi:

In the Makefile to indicate that it is a package to build (but not actually executed) - irrelevant
in pkg-deps.mk to indicate its dependencies - irrelevant
in makeiso.sh - it explicitly uses it via streaming a tar into stdin
in parse-pkgs.sh - to create the var MKISO_TAG

Following the last note, looking for all places we use MKISO_TAG:

In pkg/eve, i.e. to copy over the make-efi script

Net result, of all of that is that we use make-efi only in 2 places:

as part of makeiso.sh - tar stream to stdin
as part of lfedge/eve in runme.sh - using the directory where we would prefer to stream it to stdin

As such, I am going to go down the simplification route:

Change mkimage-iso-efi entrypoint make-efi to always expect a tar stream - simpler!
Change runme.sh where it invokes make-efi to pass it the unsquashed filesystem as a tar stream - simpler

This should fix it all.


COMPILE ERROR

Describe your problem here.
Whenever I try to compile 0.7 it gives me this error:
source/states/PlayState.hx:63: characters 14-30 : Type not found : vlc.VideoHandler
source/options/NotesSubState.hx:193: characters 48-60 : flixel.input.mouse.FlxMouse has no field deltaScreenX
source/options/NotesSubState.hx:193: characters 80-92 : flixel.input.mouse.FlxMouse has no field deltaScreenY
source/options/NotesSubState.hx:456: characters 62-71 : flixel.math.FlxPoint has no field degreesTo
source/options/NotesSubState.hx:457: characters 42-46 : flixel.math.FlxPoint has no field dist
source/states/PlayState.hx:778: characters 13-25 : Type not found : VideoHandler
I DONT KNOW WHAT TO DO
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

me and my friend are not able to compile

https://github.com/ShadowMario/FNF-PsychEngine/wiki/Libraries-versions

I'm getting the same error, I've tried what you said and installed all required libraries.


Network structure problem

Thank you for your contribution to this work. I have a question: by incorporating the DICE score between labels as part of the loss function, does this imply that the network is a semi-supervised registration network rather than a traditional unsupervised registration network? I would be grateful for your response.

Yeah, the training approach is NOT unsupervised. To be accurate, MambaMorph is trained in a weak-supervised manner instead of semi-supervised. The definition of weak-supervision is that we don't supervise the model's output (i.e. deformation field in this context) directly, but supervise the label with dice loss.

Thank you for your reply. I noticed that the loss fluctuates significantly while reproducing your work. Is this a normal phenomenon?

If I were you, I would plot the loss of several epochs. Only that I can see the trend clearly.


patch: also write reject file when outputting to stdout

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (d1f0ed2) 89.69% compared to head (01d0d30) 89.69%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #70   +/-   ##
=======================================
  Coverage   89.69%   89.69%
=======================================
  Files          19       19
  Lines        2047     2048    +1
  Branches      873      874    +1
=======================================
+ Hits         1836     1837    +1
  Misses         77       77
  Partials      134      134

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


upgrade: Log the commit hash and directory when upgrading.

Testing plan:
root@alexmv-prod:~# ~zulip/deployments/current/scripts/upgrade-zulip-from-git --remote-url https://github.com/alexmv/zulip.git upgrade-hash
2022-02-16 20:02:41,646 upgrade-zulip-from-git: Fetching the latest commits
2022-02-16 20:02:43,041 upgrade-zulip-from-git: Upgrading to 402f26f850d46bd4265e46d5d7556c7fd754465c, in /home/zulip/deployments/2022-02-16-20-02-41
2022-02-16 20:02:44,580 upgrade-zulip-stage-2: Upgrading system packages...

Because this is before stage 2, upgrading to this branch won't get the behaviour, only upgrading once you're running it.

Nice, merged, thanks @alexmv!


[CONTACT] Using Ocelot in Microsoft Reference Application for Microservices

Hey Tom!
This is Cesar de la Torre, PM at the .NET team.
You might be aware of our guidance/book about microservices and its related reference application, eShopOnContainers.
We were covering API Gateways in the guide/book, but not in the sample application, yet.
But now, we're currently implementing API Gateways for it based on Ocelot, as we find it a good .NET Core based API Gateway, flexible enough, light/lean and OSS. It is still in development, though, still not in the by default branch of eShopOnContainers sample app.
I just wanted to contact you to let you know about it and also to contact your through email so we can discuss more about it, ok?
Please, send me an email to cesardl at Microsoft.com , ok?
Thanks,

@CESARDELATORRE wow that’s is really cool! I am aware of the book and application. I will email you ASAP.

that is really cool

Yep!, I got you email! Let's sync when possible! :)

Excellent I will reply ASAP!


Add Colorado State harvester

Added tests, favicon, and harvester for Digital Collections of Colorado

Coverage decreased (-0.01%) to 93.78% when pulling 6b777dfbfa7b4c7485de84723836073aeee0631d on ag4ml:colostate into 669f933b21b986e6cfe92413dfbb4790d8655634 on CenterForOpenScience:develop.


The leaderboard is missing in https://paperswithcode.com/sota/speech-recognition-on-common-voice-7-0-hausa

Since it gets removed by the officials, we close this issue for now.


Update log-analytics-windows-agents.md

Fixed some typos and DSC configuration.

Hi @alexandair, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@bandersmsft Bill, can you take a look Aleksandar's suggestions and let us know if the changes can be merged?.

Yes, the changes Alexsandar made are fine.

@alexandair Alexandar, thanks for the review and for making those changes. I'll merge them now.


3.2.0 stability

Hi all, which is the stability of this porting of Bobo? Do you plan to release the 3.2.0?

Yes, 3.2.0 is the version that is most stable and will be released when I have determined that there are no significant issues (such as performance problems or memory leaks).
Your analysis will probably be given considerable weight in that regard since there doesn't seem to be much interest so far. But then, this repo hasn't been indexed by Google yet.
I haven't tested every aspect of it, but I have run some tests on a prototype that I made as well as the CarDemo application and all seems well so far. In addition, all unit tests that were ported are passing. Unfortunately, there are some performance tests that I am unable to port because they have dependencies to files that were not checked into the repository, and my efforts to obtain them by contacting John Wang directly didn't pan out.


Options in editor

Live editor now supports the Options work.
This only changes the schema validation and updates the default document to include an example.
There is no additional viz, although it is planned.

sweet!


Version 1.4.3 doesn't seem to be on bower

Trying to install version 1.4.3 via bower doesn't seem to work. Crucially, this is the version that seems to add support for AMD, which we need.

Working on it

Any idea how to publish it on bower? When I search for "lz-string" on bower.io, it shows lz-string updated 5 days ago which is about the same date at which I updated my bower.json file...

I think you just have to make a new tag? I'm not sure, but when you install
from bower it's definitely not the latest version
On 26 April 2015 at 19:42, pieroxy<EMAIL_ADDRESS>wrote:

Any idea how to publish it on bower? When I search for "lz-string" on
bower.io, it shows lz-string updated 5 days ago which is about the same
date at which I updated my bower.json file...
—
Reply to this email directly or view it on GitHub
https://github.com/pieroxy/lz-string/issues/53#issuecomment-96419034.

--
Thanks,
Nathaniel Higgins
http://nath.is
@nathggns http://twitter.com/nathggns

You're right, I forgot to create the GitHub release tag. Sorry about that. This is done.

Can you let me know if everything is alright on your end? Also - could you update the README.md with the instructions on how to install lz-string with bower? Duplicate the "Install via npm" section and just post it as a comment here so I can copy/paste it in README.md. Otherwise I'll do it myself but I don't use bower so I might screw it up.


Unable to tag the image ID to new image

[root@fedora buildah]# ./buildah images
IMAGE ID     IMAGE NAME
b812babf7f65 docker.io/library/redis:latest
b812babf7f65 docker.io/gouyang/redis:latest
b812babf7f65 docker.io/testing/redis:latest
b812babf7f65 docker.io/foo/redis:latest
5965adf86a6e docker.io/library/nginx:latest
223c6ba7409d docker.io/kubernetes/pause:latest
e236280e3ef7 docker.io/library/redis:alpine
a9a3ca121508 registry.access.redhat.com/rhel7/rhel:latest
8dc56e5fe235 docker.io/library/busybox:latest
f8ca008a9d31 docker.io/library/busybox3:latest
d0a32bc20460 docker.io/library/redis2:latest
9334afa88fd3
[root@fedora buildah]# ./buildah  tag 9334afa88fd3 gouyang/nginx
ERRO[0000] error finding local image "9334afa88fd3": unable to locate image: image not known

Any idea how you created an image without a tag?  If you specify the untruncated name does it work?

Any idea how you created an image without a tag?

./buildah bud .

If you specify the untruncated name does it work?

# ./buildah tag 9334afa88fd31ec8f0bff28cd4a435748c22200824337b8bc2818d2363d02d46 gouyang/nginx
ERRO[0000] error finding local image "9334afa88fd31ec8f0bff28cd4a435748c22200824337b8bc2818d2363d02d46": error parsing reference to image "9334afa88fd31ec8f0bff28cd4a435748c22200824337b8bc2818d2363d02d46": invalid repository name (9334afa88fd31ec8f0bff28cd4a435748c22200824337b8bc2818d2363d02d46), cannot specify 64-byte hexadecimal strings

Nalin I am not sure if this is a problem in buildah bud not adding a default tag, or in the lookup function, which is looking for a tag with
docker.io//library/ID/latest

@nalind This is something we need to fix ASAP though. since it can leave your database in a weird state.
Well maybe not that bad since
./buildah rmi ID
Does work.

It works now.
[root@fedora buildah]# ./buildah  images
IMAGE ID     IMAGE NAME
60d97af4c61a docker.io/library/nginx:latest
ca0eec603fc0
[root@fedora buildah]# ./buildah  tag ca0eec603fc0 gouyang/nginx
[root@fedora buildah]# ./buildah  images
IMAGE ID     IMAGE NAME
60d97af4c61a docker.io/library/nginx:latest
ca0eec603fc0 docker.io/gouyang/nginx:latest


RFC: add template-lint command

Sister to https://github.com/ember-cli/ember-cli-eslint/issues/92
Running the linting without running the whole test suite may be beneficial. Returning an error code for failures may help for CIs. I'm not familiar with this codebase, but if it functions like eslint, you may be able to get faster results if you don't have to wait for a complete ember build.

We have a template-lint:print-failures command that already does most of the work. We could extract the commonalities and add a command specifically for exit codes.

template-lint:print-failing, not template-lint:print-failures-

Ahh, sorry about that, thanks for the correction.

Running over one single template would be even more beneficial, to integrate with pre-commit hooks that only check for modified files.

Yep, should be easy to add. The majority of the code is already written. Someone just has to put the pieces together...

Also, FWIW, I believe the actual implementation of this should be a binary in ember-template-lint (not this repo).

Noticed the CLI support landed a while ago in ember-template-lint, any plans on a new release with update ember-template-lint? Or is that something else blocking this?

This landed in<EMAIL_ADDRESS>


August 8 - Nan not found

same a #320

That does it!


Crash during GC

Here is a MRE that sooner or later will produce a segfault on Enzyme v0.11.11:
using Enzyme

f(Y, θ) = abs2(only(Y) - only(θ.a))
g(x) = (a0 = x[1], a = x[2:2], B = x[3:3])
h(x) = sum(abs, g(x).a)
F(x) = f([1.], g(x)) + h(x)

function random_segfault()
    x = zeros(3)
    dx = zeros(3)
    @time Enzyme.autodiff(Reverse, F, Duplicated(x, dx))
    return dx
end

while true
    random_segfault()
end

Here is the stacktrace:

[359205] signal (11.1): Segmentation fault
in expression starting at REPL[9]:1
gc_try_setmark at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gc.c:1972 [inlined]
gc_mark_loop at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gc.c:2579
_jl_gc_collect at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gc.c:3407
ijl_gc_collect at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gc.c:3713
maybe_collect at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gc.c:1083 [inlined]
jl_gc_pool_alloc_inner at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gc.c:1450 [inlined]
jl_gc_pool_alloc_noinline at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gc.c:1511 [inlined]
jl_gc_alloc_ at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/julia_internal.h:460 [inlined]
jl_gc_alloc at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gc.c:3760
_new_array_ at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/array.c:134 [inlined]
_new_array at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/array.c:198 [inlined]
ijl_alloc_array_1d at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/array.c:436
unknown function (ip: 0x7fe4b579a04a)
unknown function (ip: 0x7fe4b57988c8)
macro expansion at ~/.julia/packages/Enzyme/v8XWi/src/compiler.jl:5220 [inlined]
enzyme_call at ~/.julia/packages/Enzyme/v8XWi/src/compiler.jl:4898 [inlined]
CombinedAdjointThunk at ~/.julia/packages/Enzyme/v8XWi/src/compiler.jl:4861 [inlined]
autodiff at ~/.julia/packages/Enzyme/v8XWi/src/Enzyme.jl:215 [inlined]
autodiff at ~/.julia/packages/Enzyme/v8XWi/src/Enzyme.jl:238 [inlined]
autodiff at ~/.julia/packages/Enzyme/v8XWi/src/Enzyme.jl:224 [inlined]
macro expansion at ./timing.jl:273 [inlined]
random_segfault at ./REPL[8]:4
top-level scope at ./REPL[9]:2
jl_toplevel_eval_flex at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/toplevel.c:903
jl_toplevel_eval_flex at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/toplevel.c:856
ijl_toplevel_eval_in at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/toplevel.c:971
eval at ./boot.jl:370 [inlined]
eval_user_input at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/usr/share/julia/stdlib/v1.9/REPL/src/REPL.jl:153
repl_backend_loop at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/usr/share/julia/stdlib/v1.9/REPL/src/REPL.jl:249
#start_repl_backend#46 at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/usr/share/julia/stdlib/v1.9/REPL/src/REPL.jl:234
start_repl_backend at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/usr/share/julia/stdlib/v1.9/REPL/src/REPL.jl:231
_jl_invoke at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gf.c:2758 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gf.c:2940
#run_repl#59 at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/usr/share/julia/stdlib/v1.9/REPL/src/REPL.jl:379
run_repl at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/usr/share/julia/stdlib/v1.9/REPL/src/REPL.jl:365
jfptr_run_repl_61336.clone_1 at ~/.julia/juliaup/julia-1.9.4+0.x64.linux.gnu/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gf.c:2758 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gf.c:2940
#1018 at ./client.jl:421
jfptr_YY.1018_34944.clone_1 at ~/.julia/juliaup/julia-1.9.4+0.x64.linux.gnu/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gf.c:2758 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gf.c:2940
jl_apply at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/julia.h:1880 [inlined]
jl_f__call_latest at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/builtins.c:774
#invokelatest#2 at ./essentials.jl:819 [inlined]
invokelatest at ./essentials.jl:816 [inlined]
run_main_repl at ./client.jl:405
exec_options at ./client.jl:322
_start at ./client.jl:522
jfptr__start_49509.clone_1 at ~/.julia/juliaup/julia-1.9.4+0.x64.linux.gnu/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gf.c:2758 [inlined]
ijl_apply_generic at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/gf.c:2940
jl_apply at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/julia.h:1880 [inlined]
true_main at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/jlapi.c:573
jl_repl_entrypoint at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/src/jlapi.c:717
main at /cache/build/builder-amdci4-4/julialang/julia-release-1-dot-9/cli/loader_exe.c:59
__libc_start_main at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
unknown function (ip: 0x4010b8)
Allocations: 38126042 (Pool: 38085098; Big: 40944); GC: 35
Segmentation fault (core dumped)

Please post the backtrack so that one can more easily take an initial guess as well as verifying that one is working on the same issue.

I added it to the OP

What is your Julia versioninfo()

julia> versioninfo()
Julia Version 1.9.4
Commit 8e5136fa297 (2023-11-14 08:46 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 8 × Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-14.0.6 (ORCJIT, skylake)
  Threads: 1 on 8 virtual cores

I reduced this from a 300LOC example that failed on both Julia 1.9.4 and 1.10.0-rc2. This one seems to work on 1.10.0-rc2, or at least it did not segfault within about a minute. A slightly larger MRE that also fails on 1.10.0-rc2 is the following one:
using Enzyme

function mydot(x::AbstractVector{T}, y::AbstractVector{T}) where T<:Real
    s = zero(T)
    for i in eachindex(x)
        s += x[i] * y[i]
    end
    return s
end

function f(Y, θ)
    return abs2(only(Y) - mydot(θ.a, zeros(4)))
end

function g(x)
    return (
        a0 = x[1],
        a = x[2:5],
        B = x[6:9]
    )
end

function h(x)
    θ = g(x)
    return sum(abs, θ.a)
end

function random_segfault(Y)
    F(x) = f(Y, g(x)) + h(x)
    x = zeros(9)
    dx = zeros(9)
    @time Enzyme.autodiff(Reverse, F, Duplicated(x, dx))
    return dx
end

while true
    model = random_segfault([1.])
end

It also gives a slightly different stacktrace:

GC error (probable corruption)
Allocations: 232976351 (Pool: 232934559; Big: 41792); GC: 331
Array{Float64, (9,)}[0, 0, 0, 0, 0, 0, 0, 0, 0]

thread 0 ptr queue:
~~~~~~~~~~ ptr queue top ~~~~~~~~~~
Array{Float64, (4,)}[0, 0, 0, 0]
==========
Array{Float64, (4,)}[0, 0, 0, 0]
==========
Array{Float64, (4,)}[0, 0, 0, 0]
==========
Array{Float64, (4,)}[0, 0, 0, 0]
==========
~~~~~~~~~~ ptr queue bottom ~~~~~~~~~~

[452519] signal (6.-6): Aborted
in expression starting at REPL[14]:1
gsignal at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
abort at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
gc_dump_queue_and_abort at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:1813
gc_mark_outrefs at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:2508 [inlined]
gc_mark_loop_serial_ at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:2677
gc_mark_loop_serial at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:2700
gc_mark_loop at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:2813 [inlined]
_jl_gc_collect at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:3137
ijl_gc_collect at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:3434
maybe_collect at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:935 [inlined]
jl_gc_pool_alloc_inner at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:1291 [inlined]
jl_gc_pool_alloc_noinline at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:1348 [inlined]
jl_gc_alloc_ at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/julia_internal.h:477 [inlined]
jl_gc_alloc at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gc.c:3486
_new_array_ at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/array.c:134 [inlined]
_new_array at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/array.c:198 [inlined]
ijl_alloc_array_1d at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/array.c:436
Array at ./boot.jl:477 [inlined]
Array at ./boot.jl:486 [inlined]
zeros at ./array.jl:636 [inlined]
zeros at ./array.jl:633 [inlined]
zeros at ./array.jl:631 [inlined]
f at ./REPL[10]:2
F at ./REPL[13]:2 [inlined]
F at ./REPL[13]:0 [inlined]
diffejulia_F_3629_inner_1wrap at ./REPL[13]:0
macro expansion at /home/simone_a/.julia/packages/Enzyme/v8XWi/src/compiler.jl:5220 [inlined]
enzyme_call at /home/simone_a/.julia/packages/Enzyme/v8XWi/src/compiler.jl:4898 [inlined]
CombinedAdjointThunk at /home/simone_a/.julia/packages/Enzyme/v8XWi/src/compiler.jl:4861 [inlined]
autodiff at /home/simone_a/.julia/packages/Enzyme/v8XWi/src/Enzyme.jl:215 [inlined]
autodiff at /home/simone_a/.julia/packages/Enzyme/v8XWi/src/Enzyme.jl:238 [inlined]
autodiff at /home/simone_a/.julia/packages/Enzyme/v8XWi/src/Enzyme.jl:224 [inlined]
macro expansion at ./timing.jl:279 [inlined]
random_segfault at ./REPL[13]:5
top-level scope at ./REPL[14]:2
jl_toplevel_eval_flex at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/toplevel.c:925
jl_toplevel_eval_flex at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/toplevel.c:877
ijl_toplevel_eval_in at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/toplevel.c:985
eval at ./boot.jl:385 [inlined]
eval_user_input at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:150
repl_backend_loop at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:246
#start_repl_backend#46 at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:231
start_repl_backend at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:228
_jl_invoke at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gf.c:3076
#run_repl#59 at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:389
run_repl at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/usr/share/julia/stdlib/v1.10/REPL/src/REPL.jl:375
jfptr_run_repl_91755.1 at /home/simone_a/.julia/juliaup/julia-1.10.0-rc2+0.x64.linux.gnu/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gf.c:3076
#1013 at ./client.jl:432
jfptr_YY.1013_82750.1 at /home/simone_a/.julia/juliaup/julia-1.10.0-rc2+0.x64.linux.gnu/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gf.c:3076
jl_apply at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/julia.h:1982 [inlined]
jl_f__call_latest at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/builtins.c:812
#invokelatest#2 at ./essentials.jl:887 [inlined]
invokelatest at ./essentials.jl:884 [inlined]
run_main_repl at ./client.jl:416
exec_options at ./client.jl:333
_start at ./client.jl:552
jfptr__start_82776.1 at /home/simone_a/.julia/juliaup/julia-1.10.0-rc2+0.x64.linux.gnu/lib/julia/sys.so (unknown line)
_jl_invoke at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/gf.c:3076
jl_apply at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/julia.h:1982 [inlined]
true_main at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/jlapi.c:582
jl_repl_entrypoint at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/src/jlapi.c:731
main at /cache/build/builder-amdci5-4/julialang/julia-release-1-dot-10/cli/loader_exe.c:58
__libc_start_main at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
unknown function (ip: 0x4010b8)
Allocations: 232976351 (Pool: 232934559; Big: 41792); GC: 331
Aborted (core dumped)

<\details>

@simsurace can you add Enzyme.API.printall!(true) after using Enzyme and upload the log, for each MWE

Log from 1.9
sego.txt

You only need the one from 1.10-0-rc2 now?

I think this should fix it: https://github.com/EnzymeAD/Enzyme.jl/pull/1195

I tried the main branch (also EnzymeCore#main) with these examples on my machine, but they still crash Julia. How did you make them work?

Hm the main branch alone should be fine. Can you include the printall log of it now for you?

log.txt

So from the log, it does have the fix for the segfault I had encountered,
so this seems to have a second issue. I’ll see if I can reproduce it.
On Sat, Dec 16, 2023 at 12:29 PM Simone Carlo Surace <
@.***> wrote:

log.txt https://github.com/EnzymeAD/Enzyme.jl/files/13693549/log.txt
—
Reply to this email directly, view it on GitHub
https://github.com/EnzymeAD/Enzyme.jl/issues/1192#issuecomment-1858900848,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJTUXBCCAFYXWASOPEJIYLYJXSBVAVCNFSM6AAAAABAN5BJ3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYHEYDAOBUHA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Ok reproduced and hopefully fixed, it was effectively an extension of the previous GC fix for this: https://github.com/EnzymeAD/Enzyme.jl/pull/1198

Hm something is still going wrong here

Should be fixed by latest jll bump https://github.com/EnzymeAD/Enzyme.jl/commit/38007ced021e021a25982b7e16a65686ead0dcf3

I can confirm that both examples now work flawlessly. Thanks!


AWS SES - Using SMTP

Hi,
Trying to use SES using SMTP Java Mail..  But getting a response -1 error..
Have configured the Test as follows:
LocalStackContainer LOCALSTACK = new LocalStackContainer(localstackImage)
            .withServices(LocalStackContainer.Service.SES)
            .withEnv("SMTP_USER", SMTP_USER)
            .withEnv("SMTP_PASSWORD", SMTP_PASSWORD)
            .withEnv("SMTP_EMAIL", FROM);

Added the environment variables as mentioned on LocalStack documentation but have omitted as using local
Endpoints are coming back as expected..  Also tested with the AmazonSimpleEmailService to verify it is working.
PROVIDER = new AWSStaticCredentialsProvider(new BasicAWSCredentials(LOCALSTACK.getAccessKey(), LOCALSTACK.getSecretKey())

AmazonSimpleEmailService client = AmazonSimpleEmailServiceClientBuilder.standard()
                .withCredentials(PROVIDER)
                .withEndpointConfiguration(LOCALSTACK.getEndpointConfiguration(LocalStackContainer.Service.SES))
                .build();

String sourceEmail = FROM;

VerifyEmailIdentityRequest verifyRequest = new VerifyEmailIdentityRequest().withEmailAddress(sourceEmail);
VerifyEmailIdentityResult verifyResponse = client.verifyEmailIdentity(verifyRequest);

SendEmailRequest request = new SendEmailRequest()
                .withSource(sourceEmail)
                .withSourceArn("").withReturnPathArn("")
                .withReturnPath("")
                .withDestination(
                        new<EMAIL_ADDRESS>"recipient2<EMAIL_ADDRESS>                                .withBccAddresses(new ArrayList()))
                .withMessage(
                        new com.amazonaws.services.simpleemail.model.Message()
                                .withSubject(new Content().withData("Test email").withCharset("UTF-8"))
                                .withBody(
                                        new Body()
                                                .withText(new Content().withData("This is the message body in text format.").withCharset("UTF-8"))
                                                )
                );

try {
    SendEmailResult result = client.sendEmail(request);
    System.out.println(result.getMessageId());
}
catch (Exception ex) {
    System.out.println(ex.getMessage());
}

Which returns a message ID.. :)
Now when I send with with Java Mail:
Session session = Session.getDefaultInstance(mailProperties.getProperties());

Properties props = System.getProperties();
props.put("mail.transport.protocol", "smtp");
// sesPort is obtained from the LOCALSTACK.getEndpointConfiguration(LocalStackContainer.Service.SES).getServiceEndpoint()
props.put("mail.smtp.port", sesPort);
props.put("mail.smtp.starttls.enable", false);
props.put("mail.smtp.auth", false);

// Send the message.
try (Transport transport = session.getTransport()) {
    MimeMessage msg = new MimeMessage(session);
    msg.setFrom(new InternetAddress(FROM));
    msg.setRecipient(Message.RecipientType.TO, new InternetAddress("wayne_gibson@mcafee.com"));
    msg.setSubject("SUBJECT");
    msg.setContent("BODY", "text/html");

    System.out.println("Connecting");

    // Connect to Amazon SES using the SMTP username and password you specified above.
    transport.connect("<IP_ADDRESS>", sesPort, SMTP_USER, SMTP_PASSWORD);

    System.out.println("Sending Email");
    transport.sendMessage(msg, msg.getAllRecipients());
}
catch (Exception ex) {
    System.out.println("The email was not sent.");
    System.out.println("Error message: " + ex.getMessage());
}

It returns with the following error when transport.connect is invoked.
javax.mail.MessagingException: Could not connect to SMTP host: <IP_ADDRESS>, port: 32956, response: -1
	at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2197)
	at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:740)
	at javax.mail.Service.connect(Service.java:366)

Any thoughts, wasn't sure if this is a testcontainers issue or localstack

Look at this example. I'll close it but if you find any issue, feel free to re-open.


24 May 2021 - InnerSource SIG Meeting Minutes

Date
Mon 24 May 2021 - 11am EST / 4pm UK
Untracked attendees

Fullname, Affiliation, (optional) GitHub username
...

Meeting notices

FINOS SIG Leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS SIG meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes
[ ] Update on Maturity Matrix Working Session
[ ] Agenda item 2
[ ] ...
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

WebEx info
Meeting link: https://finos.webex.com/finos/j.php?MTID=m33975a6a163e1319c07e33a06bd3d1d5
Meeting number:<PHONE_NUMBER>
Join by phone (US Toll): +1-415-655-0003
Join by phone (UK Toll): +44-20319-88141
Access Code:<PHONE_NUMBER>
Mailing List
Email<EMAIL_ADDRESS>to subscribe to the InnerSource SIG mailing list.

hello all

Hello

Hello 👋

Hello everyone! :)

Hi everyone

Hello 👋🏻

howdy

Hello everyone!!


I tried selecting 50 values as I need to select almost 100 teams as requirement of using this extension but after adding 50th I got error saying " The value for field 'fieldname' is too long."

Wondering what is the field limit here as with team names with names longer then 6-7 characters it gives this error sometime at 20 or 22nd team added.

thanks for reporting. Could you help us track this down by checking the browser network log (f12 in the browser), and the console log for errors? There should be an error telling us which api that's failing for you.

@adminTI Here you go

Here is the screenshot of error and Network log when add Team 34, works fine until Team 33 roughly which i guess is 262 characters including semicolons added behind scenes via code, So I am not sure if its Devops String limitation causing this


Millisecond formatter do not work properly

If I use a formatter like this "yyyy-MM-dd HH:mm:ss.SSS" the milliseconds section (SSS) is not properly formatted.
Example:
var outputDatestring = "2015-03-25T13:43:00.123+0000";
var date = new Date(outputDatestring);
console.log($.format.date(date, "yyyy-MM-dd HH:mm:ss.SSS"));

This code logs the following result (my browser is in GTM+01:00, so the hour is correct, but not the milliseconds section):
2015-03-25 14:43:00. Eu
Expected result:
2015-03-25 14:43:00.123

hi @GianlucaVagnoni
Indeed, it does not seem to be working with your outputDatestring  format.
There are some examples with SSS, in case you change your input format.

Hi @GianlucaVagnoni
Unfortunately, your input format does not seem to be in the expected input list.
From where is that format coming from?

Hi,
That format is called ISO 8601, which is one of the most common formats used for serialization/deserialization of Date objects as a string in JSON format.
There is also another common ISO 8601 format:
"2015-03-25T13:43:00.123Z"
...which is what javascript outputs with toISOString()
new Date().toISOString()
"2020-03-25T19:21:42.398Z"

Regards.


Flatten import structure

Removes visible modules (leaving types) to make the documentation clearer.
This is a breaking change and may require crate users to update their code

An alternative here, which might be preferred, is to keep using the nested structure, but make it private and add re-exports. Probably doesn't matter too much though.

wat you are suggesting

Exactly what you did, sorry :pensive:.


Allow simple logger level config to support "OFF"

Fixes #2818
Problem:
DefaultLoggingFactory doesn't allow for OFF to be configured as a logger level in the simple config case. Example:
logging:
  loggers:
    "com.example.my.logger": OFF

results in "Unsupported format of logger".
Solution:
Updated the if check to accept boolean values since OFF is translated to false in YAML and use existing toLevel method that properly handles boolean as Level.OFF.
Result:
OFF will be allowed as a logger level in the simple case without requiring it to be quoted.

If you do hit this issue, a temporary workaround is to write OFF in double quotes:
"my.logger": OFF #Doesn't work
"my.logger": "OFF" #Works!

@GuiSim Thanks for pointing this out.
The issue is that YAML up to version 1.2 interprets the string OFF (without quotes) as a boolean value (false). 🙄

A Boolean represents a true/false value. Booleans are formatted as English words (“true”/“false”, “yes”/“no” or “on”/“off”) for readability and may be abbreviated as a single character “y”/“n” or “Y”/“N”.

https://yaml.org/type/bool.html


Send named pipe name to roslyn and razor

Update Roslyn to: https://dev.azure.com/dnceng/internal/_build/results?buildId=2484529&view=results
Update Razor to: https://dev.azure.com/dnceng/internal/_build/results?buildId=2484091&view=results

@ryzngard looks like there is some issue with override completion on .net8 linux (consistently failing).  Most likely caused by some roslyn change.  I don't think I'll be able to look until next week (I'm out starting early afternoon tomorrow).  I'm not sure the insertion can go in with the bug

@ryzngard looks like there is some issue with override completion on .net8 linux (consistently failing).  Most likely caused by some roslyn change.  I don't think I'll be able to look until next week (I'm out starting early afternoon tomorrow).  I'm not sure the insertion can go in with the bug

Can you force merge or do I need to ask a higher authority (as if there is one 😅)

@ryzngard looks like there is some issue with override completion on .net8 linux (consistently failing).  Most likely caused by some roslyn change.  I don't think I'll be able to look until next week (I'm out starting early afternoon tomorrow).  I'm not sure the insertion can go in with the bug

Can you force merge or do I need to ask a higher authority (as if there is one 😅)

I can force merge this, but I don't think we should.  There is definitely a regression caused by the roslyn changes that breaks override completion on linux.  Until we figure out why and to what extent, I don't think we can release a change with this.

Oh sorry, misread on mobile. Understood. I'll see if I can take a few minutes to look otherwise I can coordinate with you


Update dependency handlebars to v5 for mdman.

What does this PR try to resolve?
issue #13238

update dependency handlebars 4.5.0 -> 5.0.0
fix code to fit the changes of Handlebars API
RenderError::new() is deprecated. Use RenderErrorReason instead

How should we test and review this PR?
pass all tests in /crates/mdman/tests

Thanks!
@bors r+

:pushpin: Commit 06201b989209698eeec23fe4fa6399c2186ef928 has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit 06201b989209698eeec23fe4fa6399c2186ef928 with merge d069c2419ba810c416024fe52dbcbdf1cb051676...

:broken_heart: Test failed - checks-actions

@bors retry
macOS: The hosted runner encountered an error while running your job. (Error Type: Disconnect).

:hourglass: Testing commit 06201b989209698eeec23fe4fa6399c2186ef928 with merge 87eb374d499100bc945dc0e50ae5194ae539b964...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 87eb374d499100bc945dc0e50ae5194ae539b964 to master...


sum losses before backward

When the number of output channels is higher than one, the loss.backward() will return an error.
This small fix makes sure that this doesn't happen by calling loss.sum().backward() to make it compatible to multiple outputs

This change relates to issue #292

It depends on the loss function you're using. If you're using one of the losses from neuralop.losses, e.g. LpLoss, you need to provide the loss with dimensions over which to reduce. This is controlled by the parameter reduce_dims. Take a look in LpLoss.reduce_all (line 104 of neuralop.losses.data_losses.py).

Thank you for the explanation!


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

TagBot fix

TagBot retry

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111868

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111882

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111936

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111960

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/112086

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/112156

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/112163

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/112413


Update shards to 0.8.1

shards 0.8.1 fixed critical issue.
i see that OS X version (from brew) already use 0.8.1, but linux release in https://github.com/crystal-lang/crystal/releases, still use 0.8.0

We will solve a couple of regressions in the next few days and release 0.25.1 with an updated shards probably during next week.
As a quick workaround shards can be checked out and built from source.
Given that there are some regressions present and it’s not just the shards issue I think is the best alternative regarding timing for everybody.

Closing. This is related to distribution. Next release will have it, and should arrive quickly.


PDF templates

It could be great to have a format to upload custom PDF template or something. The case is: names localisation. My API is described in Russian so I would like to have translated headers (like "index", "Request", "request body" etc in generated PDF.

okay, I would bring the localization topic up with the team and look into how best we can address this. Meanwhile can you tell me how do you plan to show the data-types and formats like string, int, float, double, uuid, array, boolean... etc
Should they be translated or they would be shown as is ?

localization is now possible (from release 1.1.1)
Refer to the API on how to provide localization


Slow ajax response

Why using CI 3 the response it is very slow (> 3 Second) to get the json data by using jquery autocomplete. im already test my application with similar code using CI 2 but it only takes respond in shortly 1 Second even less.
here my simple server side code :
function kode_area_tag()
    {
    $list = array();
    $post = trim($this->input->post('query'));
    $sql = "SELECT nama from view_area where nama like '%$post%'";
    $query = $this->db->query($sql);
    foreach ($query->result() as $row)
    {
        array_push($list, $row->nama);
    }
    echo json_encode($list);
}

as addition, i tested it with pdo also but still get very slow respond

After couple of hours, searching for this problem. i think its the problem of the database configuration. I should set the parameter -> pconnect : TRUE


test: add tests to blas/ext/base/dnansumkbn

Resolves #3046
Description

What is the purpose of this pull request?

This pull request:

Add test case for blas/ext/base/dnansumk and dnansumk-native.js

Related Issues

Does this pull request have any related issues?

This pull request:

resolves #3046

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md

@stdlib-js/reviewers

check the contributing guidelines

accidently closed PR

/stdlib merge

/stdlib help

/stdlib lint-autofix

@saurabhraghuvanshii Thank you for opening this PR; however, as is, we cannot accept it. The current PR makes several undesired stylistic changes and does not follow our style guidelines or the dominant conventions used throughout the project.
While the PR does add additional tests, those cannot be merged until the various stylistic changes are reverted.

Hii @kgryte if I follow your guidelines of styles and improved it , can be it merged

@saurabhraghuvanshii Yes, this PR should be on the pathway to being merged. However, you should also see https://github.com/stdlib-js/stdlib/pull/3051/files which implements a very similar set of changes. You should replicate those changes here.

@kgryte ok sir

@kgryte sir , change blas/ext/base/dnansum by refrence #3051 , If any change requires I will do
and Thanks for your valuable time

/stdlib lint-autofix

@kgryte thanks sir


update(userspace/libscap): Add missing Windows libraries.

windows_hal.c requires netapi32.dll and iphlpapi.dll.
Signed-off-by: Gerald Combs<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
This ensures that we link with required system libraries on Windows.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: geraldcombs
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @geraldcombs. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Thanks for your continuous work on stepping up windows support!
/ok-to-test

This should have been included with #300; sorry about that.

No problem! :)

LGTM label has been added.  Git tree hash: 7807a609cec9eea3113b78b690a473057ca7bf10

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, geraldcombs
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, geraldcombs
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment