All pages after page 1 are balnk in long strip reading modes

Steps to reproduce

Open any manhwa
reading mode is long strip/ long strip with gaps.
Scroll down

Expected behavior
Read Normaly

Actual behavior
Blank pages after page 1

![IMG-20241028-WA0006](https://github.com/user-attachments

/assets/dd2ff3b1-4c36-43a2-9a6e-731e76912f06)

Crash logs
No response
Mihon version
0.17.0
Android version
Android 8.0.0
Device
Samsung Galaxy S7 edge
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.17.0.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

We need someone patient who is affected with the issues to help out with the diagnosis. Please come to our discord server if you wish to help.

I've been facing the same problem after the update which made me stop reading for 2. I've tried changing settings but the issue is still there. I ask the developers to please fix this issue ASAP.

I only noticed this issue with very few webtoons, sometimes affecting one chapter but not others. In some cases like Magic Emperor, ch 610 (manga demon source) the issue is a constant flickering as you scroll down that may be fixed by zooming out. In others like The Last Adventurer, ch 41 I think, from Asura source, the black was like a big gap between the images. I don't remember if it had flickering as well, but I can probably check.

This is replicate of https://github.com/mihonapp/mihon/issues/1390. None of the suggested workarounds work.

On Samsung Galaxy 2016, I also have the same issue. If the problem is device being old, then how come on 0.16.5 version we do not have this exact problem? Split image doesn't solve the problem, neither downloading the images ahead. The paged reader doesn't bring smooth experience for Webtoons and many manhwas. Something in version 0.17 broke the reader, and it is a pitty since we cannot update mihon app beyond 0.16.5 anymore.
Would it be possible to add a button that reverts the reader to its 0.16.5 version for older devices? Or alternatively, a "long strip legacy" as an extra option for people like us.


Recreate Yelp's email template

New login to your Yelp account.eml.zip

It can close because it was done, it remains to go up in production.
This is updated in react-email-apps.


Add data migration for dos entries in lots table

Add data migration so can be certain lots are consistant through all the enivironments.

This should probably go in after https://github.com/alphagov/digitalmarketplace-api/pull/295, with the lot-framework relationship defined.

Tested locally and does the job. @carolinegreen @robyoung If you're happy with mine and @TheDoubleK’s earlier commits then this is :+1:.

I think after removing the enum check in those 3 tests, you can also remove the bootstrap_dos() method entirely now.

Yep we should definitely be able to :fire: :fire: :fire: bootstrap_dos() from the tests everywhere.


ValidationError: Child2.rel is not initialized, define it as 'rel = new Collection(this);' when using STI and 'problematic' relation is defined on other child

Describe the bug
When querying table, that uses STI, with QueryBuilder things broke up and orm starts complaining about uninitialized relation, although it is initialized and defined, but on other children
Stack trace
ValidationError: Child2.rel is not initialized, define it as 'rel = new Collection<Child1Specific>(this);'

    at Function.fromCollectionNotInitialized (/home/k/WebstormProjects/mikro-orm/packages/core/src/errors.ts:32:12)
    at EntityValidator.validateCollection (/home/k/WebstormProjects/mikro-orm/packages/core/src/entity/EntityValidator.ts:106:29)
    at /home/k/WebstormProjects/mikro-orm/packages/core/src/entity/EntityValidator.ts:13:14
    at Array.forEach (<anonymous>)
    at EntityValidator.validate (/home/k/WebstormProjects/mikro-orm/packages/core/src/entity/EntityValidator.ts:11:16)
    at SqlEntityManager.merge (/home/k/WebstormProjects/mikro-orm/packages/core/src/EntityManager.ts:479:20)
    at SqlEntityManager.map (/home/k/WebstormProjects/mikro-orm/packages/core/src/EntityManager.ts:446:17)
    at /home/k/WebstormProjects/mikro-orm/packages/knex/src/query/QueryBuilder.ts:389:34
    at Array.map (<anonymous>)
    at QueryBuilder.getResultList (/home/k/WebstormProjects/mikro-orm/packages/knex/src/query/QueryBuilder.ts:389:16)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at Object.<anonymous> (/home/k/WebstormProjects/mikro-orm/tests/issues/GH8455.test.ts:93:21)

To Reproduce
Steps to reproduce the behavior:

Run test case GH997.test.ts

Expected behavior
Should work like it works without QueryBuilder
Versions

Dependency
Version

node
v12.14.1

typescript
4.0.5

mikro-orm
4.2

mysql
dunno

You can test it before the actual release via 4.2.4-dev.71 (playing around with nightlies curretly, in future this will be shipped around 6 am, but now you are lucky enough to have it right after build :P).

You can test it before the actual release via 4.2.4-dev.71 (playing around with nightlies curretly, in future this will be shipped around 6 am, but now you are lucky enough to have it right after build :P).

Great! I'll check it later today :)


[write-fonts/gvar] repro shared tuples unstable order

Reproduce and fix https://github.com/googlefonts/fontc/issues/647#issuecomment-1892034218

https://github.com/googlefonts/fontations/actions/runs/7528580955/job/20491085359?pr=756
failures:

---- tables::gvar::tests::shared_tuples_stable_order stdout ----
thread 'tables::gvar::tests::shared_tuples_stable_order' panicked at write-fonts/src/tables/gvar.rs:1270:13:
assertion `left == right` failed
  left: [[-1.0], [1.0]]
 right: [[1.0], [-1.0]]

I can confirm this enables reproducible builds for Oswald. I tested rebuilding a hundred times and fontc always produces exact same bytes for gvar, previously it would fail about 50% of the times.


Fix typographical error(s)

@andrewliebchen, I've corrected a typographical error in the documentation of the reacticons project. Specifically, I've changed becasue to because. You should be able to merge this pull request automatically. However, if this was intentional or if you enjoy living in linguistic squalor, please let me know and create an issue on my home repository.

:+1: I'm a terrible speler. Thanks!


fix: autotypeing with libportal

Fixes #229. Tested via the Flathub package.

Thanks for the PR and apologies for not getting back earlier!


Revoke

[Enter feedback here]
At the end of the video she stated that for items like view that are already established you don't need to make changes and you can use REVOKE for previous views and sql statements, can you explain that more

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

ID: d200cb5d-8f70-87c5-2437-c54701f7681f
Version Independent ID: df184959-2b22-4796-c0b1-0a8ad91be35a
Content: Column-level security for dedicated SQL pool - Azure Synapse Analytics
Content Source: articles/synapse-analytics/sql-data-warehouse/column-level-security.md
Service: synapse-analytics
Sub-service: sql-dw
GitHub Login: @julieMSFT
Microsoft Alias: jrasnick

Thank you for your detailed feedback.  We are looking into the issue, and we will respond when we have more information.

We have assigned the issue to the content author . They will evaluate & do the needful as appropriate

#assign:nanditavalsan

@nanditavalsan Please review this git issue.

Hi @shellypa, sorry for the delay in response here, this just isn't the best place to ask questions like this. GitHub issues are more for docs updates and corrections. In general, REVOKE removes a GRANT or DENY.
#please-close

#reassign:WilliamDAssafMSFT


Upgrade to Typescript 3

Augur Core wont build with Typescript 3 currently, but it may not be too bad.
...
Scratch that, it doesn't even work in 2.9.2 which is the version we use in Augur Node.
Fixing the issues.
-pgebheim
...
@pgebheim what's the status on this one? Should this be in 'ready for dev' since there are still issues you need to fix? Or have they been fixed already?
-sharkcrayon
...
Sorry, I just handled the upgrade to 2.9.2 within my mono-repo update.
Still haven't done v3.
-pgebheim
...
@achapman Is this something that we should still do?
-adrake33
...
Yea this would still be nice to do. Not high priority but still relevant
-nuevoalex

Already done.


Add tutorial for using localization site

Add to README.md
Screenshots
Full-cycle walkthrough
Choosing locale
Understanding MISS/IDEN/OUTD
Making changes, adding translations
Exporting to messages.json
Submitting PR

Fixed.


Add Razer Mamba TE layout and full support

List any issues that this PR fixes: fixes #1543
This pull request proposes the following changes:

Adds the Razer Mamba TE
Replace the if statements to a switch to improve performace and have a cleaner code

Known issues/To do:

[x] Integration of Lightning Wrapper/Chroma Lightning
[x] Some LEDs won't look in HD because when the bitmap accuracy is in "Fine" they don't light up because of the LED size; Workaround for this is make them "6.1" of size

Ready for review


fix(clerk-js): Avoid the use of fragment for redirectWithAuth

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[x] npm test runs as expected.
[x] npm run build runs as expected.

Are we ok with removing the fragment here? If so, let me know so I can go ahead and update the tests!

@desiprisg Can you share more details about this one please? Not sure I get the solution!

@SokratisVidros I made the changes to keep the hash. Please take a look.

@desiprisg regarding this fix, wouldn't it make sense just to remove this line?

@SokratisVidros This function did not change, so why would we remove the comment there?


asciinema: 2.4.0 -> 3.0.0-rc.3

This works and builds. Not ready to be merged yet, since we currently have to disable tests for it to build, and I'd prefer to wait for the stable release rather than using a release candidate. However, we've done the work here of swapping to Rust instead of Python, due to the package being rewritten.
If anyone is able to help debug why it's failing tests, I'd appreciate it! This is the error output I'm getting:
running 17 tests
test asciicast::tests::accelerate ... ok
test asciicast::tests::limit_idle_time ... ok
test asciicast::tests::open_v1_minimal ... ok
test asciicast::tests::open_v2_minimal ... ok
test asciicast::tests::open_v1_full ... ok
test asciicast::tests::open_v2_full ... ok
test asciicast::tests::write_header ... ok
test encoder::raw::tests::encoder_impl ... ok
test asciicast::tests::writer ... ok
test encoder::txt::tests::encoder_impl ... ok
test tty::tests::parse_color ... ok
test util::tests::utf8_decoder ... ok
test pty::tests::exec_basic ... FAILED
test pty::tests::exec_no_output ... ok
test pty::tests::exec_winsize_override ... ok
test pty::tests::exec_quick ... ok
test pty::tests::exec_extra_env ... ok

failures:

---- pty::tests::exec_basic stdout ----
thread 'pty::tests::exec_basic' panicked at src/pty.rs:463:9:
assertion `left == right` failed
  left: []
 right: ["foo", "bar"]
stack backtrace:
   0:     0x5555555fe7f6 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h9754a6437f1de22a
   1:     0x5555556552fb - core::fmt::write::hb706a393bb60a06f
   2:     0x555555606949 - std::io::Write::write_fmt::h45bf4fee0184c1a6
   3:     0x555555634d76 - std::panicking::default_hook::{{closure}}::h227952daede9dd84
   4:     0x555555634a36 - std::panicking::default_hook::h31626ee1feb8ee2a
   5:     0x5555555a2e6a - test::test_main::{{closure}}::hb863b6e1cc3ca57a
   6:     0x555555635516 - std::panicking::rust_panic_with_hook::h76d2aa694a00748e
   7:     0x5555555feff7 - std::panicking::begin_panic_handler::{{closure}}::h8855a344ffa1638b
   8:     0x5555555fea09 - std::sys::backtrace::__rust_end_short_backtrace::h3110d0cbfbf26886
   9:     0x555555634eb4 - rust_begin_unwind
  10:     0x5555555730e3 - core::panicking::panic_fmt::h3af706d0346c1c60
  11:     0x5555555733be - core::panicking::assert_failed_inner::h7817d57f580e4b84
  12:     0x55555556d9d3 - core::panicking::assert_failed::h37124c8def20a075
  13:     0x55555558dcb8 - asciinema::pty::tests::exec_basic::h1bd0e43fd651dc17
  14:     0x5555555943a9 - core::ops::function::FnOnce::call_once::h2533eae5be349a34
  15:     0x5555555a8a2b - test::__rust_begin_short_backtrace::h32dbc76e3657b1e4
  16:     0x5555555e13f2 - test::types::RunnableTest::run::hbd37082e743ae77e
  17:     0x5555555a8bd1 - test::run_test_in_process::ha03e943838708deb
  18:     0x5555555b110f - std::sys::backtrace::__rust_begin_short_backtrace::ha10de4c6e83c53f7
  19:     0x5555555b1895 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h338bbb43d876641d
  20:     0x555555607b6b - std::sys::pal::unix::thread::Thread::new::thread_start::h87241c7e32b9860b
  21:     0x7ffff7d49d02 - start_thread
  22:     0x7ffff7dc93ac - __GI___clone3
  23:                0x0 - <unknown>

failures:
    pty::tests::exec_basic

test result: FAILED. 16 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

https://github.com/NixOS/nixpkgs/pull/342425

https://github.com/NixOS/nixpkgs/pull/342425

Ah, must have missed that in my search! It looks far better setup than mine, so I'm happy to close this.

@llakala you could've added yourself as a maintainer in this pr itself when doing the update instead of a separate pr #354625
but I think you can ask AndersonTorres to become a co-maintainer on matrix, discourse or on the https://github.com/NixOS/nixpkgs/pull/342425 pr


Remove humanize string

Fix key / value translation
https://symfony.com/doc/current/best_practices.html#use-keys-for-translations-instead-of-content-strings

Hey,
Behaviour is the same as Symfony form.
->add('foo') will create an entry with key "foo" and a label with humanized name "Foo"
If you want to change label use `->add('foo')->label('label.foo')

Ok ! My bad... it's good, thx :)


Expose ledger types PParams and PParamsUpdate with support code

Changelog
- description: |
    Expose ledger types `PParams` and `PParamsUpdate` with support code
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - improvement    # QoL changes e.g. refactoring
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context
This a a simplified version of https://github.com/input-output-hk/cardano-api/pull/182 with all the refactoring, newtype wrapper and aeson instances removed.  The removed commits were mainly to facilitate the custom aeson instances which during discussions were determined to not be needed.
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] The change log section in the PR description has been filled in
[ ] New tests are added if needed and existing tests are updated.  These may include:

golden tests
property tests
round trip tests
integration tests
See Running tests for more details

[ ] The version bounds in .cabal files are updated
[ ] CI passes. See note on CI.  The following CI checks are required:

[ ] Code is linted with hlint.  See .github/workflows/check-hlint.yml to get the hlint version
[ ] Code is formatted with stylish-haskell.  See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
[ ] Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7

[ ] The changelog section in the PR is updated to describe the change
[ ] Self-reviewed the diff

These are intended to be used by the CLI.


Runaway exception "A fatal error occured.  Zcoin can no longer continue safely and will quit".

Windows (10) / Running a node via VPS with 55GB SSD and 2048MB memory / OS Ubuntu 19.04 x64
I have deleted and reinstalled the wallet several times.  I have tried ./zcoin-qt.exe -reindex and thats when I get the error message.  When I click on the wallet.exe it shows the wallet is trying to load however, then it disappears.  The wallets block status in putty is up to date.   Even though the wallet startup display disappears after I receive the error message, I can see,
"Zcoin Core (GUI node for Zcoin)" running in task manager.

Hi, could you give details on what you were doing in the wallet before the error occured?

Closing this issue as no response. Please reopen if still an issue and replicable.


Import unifi_video

Hi there,
can you help and describe how to setup the correct path?
Is there any module which needs to be installed?
python luca.py
Traceback (most recent call last):
File "luca.py", line 2, in
from unifi_video import UnifiVideoAPI
ImportError: No module named unifi_video
Thanks
Luca

You probably just need to add the folder to your path.  You can add this line (edit to match where you pulled this project to) to your bash profile or just run before you run the script.
export PYTHONPATH=~/git_repos/unifi-video-api

@EagleOne42's suggestion should work.
You could also just clone the repo to your project root. Inside your project directory:
git clone https://github.com/yuppity/unifi-video-api.git

and then either remove the repo and pluck out the unifi_video package:
mv unifi-video-api/unifi_video . && rm -r unifi-video-api

or, alternatively, symlink the package path (assuming you're on *nix):
ln -s unifi-video-api/unifi_video .

So, to get setup, run either of these two command sequences inside your own project:
git clone https://github.com/yuppity/unifi-video-api.git && \
mv unifi-video-api/unifi_video . && rm -r unifi-video-api

git clone https://github.com/yuppity/unifi-video-api.git && \
ln -s unifi-video-api/unifi_video .

@xxxlucaxxx  feel free to open a new issue if you're still having problems.


Thoughts on an orElse/unwrapOrElse equivalent?

I'm liking the lib so far! What are your thoughts on orElse methods? Right now if I want to have errors fallback I do:
const res = fn().chain(
  (x) => Result.ok(x),
  () => otherFn()
);

But that could be made a little more ergonomic if it was something like:
const res = fn().orElse((err) => otherFn());

Or the equivalent unwrap:
const val = fn().unwrapOrElse((err) => otherFn());

I get that it's a balance of keeping the lib small and having things be ergonomic - rust has soo many Result methods 😆

how would unwrapOrElse work? what would be the type of val in an error scenario?
is the idea that unwrapOrElse would always throw in the error case? if not, how do you handle the fact that val continues to live on in outer scope in an error situation?
i like the idea of these ergonomics but i don't see anyway to not return control to the outer scope unless you are always throwing after otherFn() is called.


from dgcnn_util import pointnet_fp_module

from dgcnn_util import pointnet_fp_module,I do not find the function of pointnet_fp_module in dgcnn_util.

Hi,can you send me your visualization of segmentation on s3dis to my email?such as mangy ply files.

Hi, it's quite sample, the code will generate obj files for prediction results and ground truth, then you just need install MashLab to open it. That's it.

Hi, it's quite sample, the code will generate obj files for prediction results and ground truth, then you just need install MashLab to open it. That's it.

ok,I will try to run it. but I try to run DGCNN code about semantic segmentaion,I meet this problem,do you know why?
InternalError (see above for traceback): Blas xGEMM launch failed : a.shape=[1,4096,3], b.shape=[1,3,4096], m=4096, n=4096, k=3
[[Node: MatMul = BatchMatMul[T=DT_FLOAT, adj_x=false, adj_y=false, _device="/job:localhost/replica:0/task:0/device:GPU:0"](ExpandDims_1, transpose)]]
[[Node: adj_conv2/bn/cond/add_1/_223 = _Recvclient_terminated=false,


Remove JSON support

We need to switch the sample app over to XML.

But we don't support XML on new API's Why would we encourage it?

The ISO spec itself doesn't give official support for JSON. We're working on getting that added to 15143-3 and reintroduce JSON support at that time.

Oh, I didn't notice this sample is for THAT api. Carry on


NIFI-11787: Add Min Inflate Ratio property to ConvertExcelToCSVProcessor

Summary
NIFI-11787
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[x] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

Closing this as there is no desirable solution from the NiFi side, will revisit if a Jira is filed and resolved in Apache POI or some other desirable solution presents itself.


Websocket support: Do not remove websocket upgrade headers

This is the first of the PRs for enabling websocket support in Envoy.
Currently, we strip upgrade and connection headers. For websocket support, we need to allow these headers to pass through if Connection: upgrade and Upgrade: websocket.
c.f. #319

Here is the reference branch with the entire websocket code:
https://github.com/lyft/envoy/compare/master...amalgam8:envoy-websocket

PTAL


Add abbreviation/alternative words for commands

Users can now use abbreviations or alternative words when typing commands.
e.g. users can use 'find' or 'f' or search.
All commands are case insensitive now.

tests not working at d9e8d0b007e1a6df1e21bff501deaafc43dae104


Not sure how to apply hidden class anymore

@chrisvfritz
Earlier, we created this awesome hidden_class helper:
def hidden_class
  if params.values.any? { |val| !val.empty? }
    ''
  else
    'hidden'
  end
end

This is no longer working, because empty forms still contain captures and template parameters, like this: /form/news?&captures=news&template=news. Now the div I want to hide is always present, because params is never empty.
How can I create a conditional for "the only parameters present are captures and template" instead of "any parameter is present"?

What if you update params.values to (params.values - ['captures', 'news'])?


remove async keyword since mocha does not run the tests correctly.

We have recently found that mocha test runs on travis ci are faulty on 2 counts

Sometimes mocha does not fail when

Automation for azure-sdk-for-node

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

@sergey-shandar @olydis - Please review.
FYI, this PR is supposed to fail as it will detect 4 failures in syntax mode. It should be merged if the PR fails and not merged if the PR passes.


Incremental parsing: Where's the push version?

The promotional materials cite "incremental parsing" but where is the interface that lets me call into the parser with a buffer at a time?
I see the "pull" interface where it reads from a stream - where's the push?

Do you mean the line

Aaron Burghardt implemented code to parse streams incrementally. Furthermore, he greatly improved the parser class by allowing the definition of a filter function to discard undesired elements while parsing.

?

I think so. What I'd like is to declare an object that holds the parser state, and then call it one or more times with buffers holding pieces of the incoming JSON stream until the serialized JSON is complete. Then take ownership of the tree from the parser.

The mentioned paragraph refers to the parser from std::istream. There, it is possible to call the parser multiple times on a stream and read a JSON value each. See #367 for details.
Your described usecase is interesting, but currently not possible.

Fair enough. Note that reading from std::istream is "pull" parsing (the parser requests buffers until the parse is complete)

Alright - I never "promised" push parsing. ;)

Context: I am looking for a JSON pull parser to use as an example in my HTTP library Beast (being proposed for Boost). I want to show how you can declare a custom "Body" type which parses incoming JSON from HTTP requests on the fly. Hence the need for a push parser that operates incrementally on buffers.
Believe it or not, NONE of the JSON libraries that I have found with my Google searching have pull parsing as a feature! If yours was the first, I could feature your library in my examples :)
Beast:
https://github.com/vinniefalco/Beast/

I understand. The "issue" is, that I aim for an intuitive API and currently I tried not to expose the parser class to the user, so I am not sure whether such a parser would really benefit this library.

I think this is nothing I can realize right now.

#623 discusses a restructuring of the parser class. Maybe this issue can be reviewed there as well.

Related: #971

Someone can always work around it by 'pushing' it to a suspending iterator in another thread, or in a coroutine via Boost.Fiber or Boost.Coroutine2 or whatever as well.


Better search capabilities

What are you trying to do?
I want better search capabilities for https://search.maven.org/
Including:

filters: be able to filter search results based on certain criteria. Like "updated>=2018-01-01"
items-per-page should be customizable. Should allow me to view at least 100 per page.

What feature or behavior is this required for?
I want better search capabilities for https://search.maven.org/

How could we solve this issue? (Not knowing is okay!)
See above

Anything else?
No

@kristof9851 thank you for creating this, and my apologies for the delayed reply. Looking further into this we found that this would require some Back End changes to allow filtering on specific criteria.
This project is specifically related to the Front End of Search Maven Org, when we start looking into improving our Back End servers we will hopefully address this as well.
For allowing to view more then the current items-per-page in a customizable way, we current are following the same as what the classic is doing, but would not appose a customizable way to change that. A PR for it would be greatly appreciated :-)
For now closing this, I did add a specific label that allows us to come back and review any changes we need to make once we updated out Back End.


qa_crowbarsetup: Create keypair for magnum

Magnum uses a key called "default" for the tempest tests.
Create this key.

+1


Add ratchet tree extension to managed group

This PR adds the ratchet tree extension to the  ManagedGroup config and adds an integration test.
This is likely to be rewritten once we tackle extension for good, but for now it just aligns ManagedGroup with MlsGroup in that regard.

Can you file a follow-up to add a builder pattern or some other constructor for the GroupConfig? This is getting ugly.

Good point! #415


new changes to dev

@akhanf can you merge this in? I don't have permission since the branch exists on your fork

closing this without merging, since I rebased in my PR..


Update description as suggested in #482

Update description for "clock" to make the task clearer. I have added more detail to the instructions, and have tried to give an example for every instruction.
I would further like to add an explanation of the modular arithmetic mod 24 that they will need to use, as this task should be a programming exercise, not a mathematics exercise. I would appreciate advice about whether this is appropriate.

I accidentally merged something that I didn't mean to, hopefully my solution to the problem can still be approved, sorry!


The trust_metric test is failure

What happened:
$ make ci

running 19 tests
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
thread 'tokio-runtime-worker' panicked at 'exec queue dropped!', /rustc/75e1463c52aaea25bd32ed53c73797357e561cce/src/libstd/macros.rs:13:23
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
test trust_metric_all::mempool::should_report_good_on_valid_transaction ... ok
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
thread 'tokio-runtime-worker' panicked at 'metadata should not be none', /workspace/source/built-in-services/metadata/src/lib.rs:26:34
test trust_metric_all::mempool::should_be_disconnected_for_repeated_exceed_tx_size_limit_only_within_four_intervals ... ok
thread 'tokio-runtime-worker' panicked at 'exec queue dropped!', /rustc/75e1463c52aaea25bd32ed53c73797357e561cce/src/libstd/macros.rs:13:23
test trust_metric_all::mempool::should_be_disconnected_for_repeated_exceed_cycles_limit_only_within_four_intervals ... ok
thread 'tokio-runtime-worker' panicked at 'exec queue dropped!', /rustc/75e1463c52aaea25bd32ed53c73797357e561cce/src/libstd/macros.rs:13:23
test trust_metric_all::mempool::should_be_disconnected_for_repeated_wrong_chain_id_only_within_four_intervals ... ok
test trust_metric_all::should_have_working_trust_diagnostic ... ok
test trust_metric_all::trust_metric_basic_setup_test ... ok
thread 'tokio-runtime-worker' panicked at 'get report: Unexpected("rpc to /rpc_call/diagnostic/trust_report [ProtocolError] Kind: Network Error: Internal(RpcTimeout(None))")', tests/trust_metric_all/mempool.rs:251:37
thread 'trust_metric_all::mempool::should_be_disconnected_for_repeated_timeout_larger_than_gap_only_within_four_intervals' panicked at 'test pass: JoinError::Panic(...)', tests/trust_metric_all/mod.rs:35:9
test trust_metric_all::mempool::should_be_disconnected_for_repeated_timeout_larger_than_gap_only_within_four_intervals ... FAILED
thread 'tokio-runtime-worker' panicked at 'get report: Unexpected("rpc to /rpc_call/diagnostic/trust_report [ProtocolError] Kind: Network Error: Internal(RpcTimeout(None))")', tests/trust_metric_all/consensus.rs:164:37
thread 'trust_metric_all::consensus::should_be_disconnected_for_repeated_malicious_new_height_broadcast_within_four_intervals' panicked at 'test pass: JoinError::Panic(...)', tests/trust_metric_all/mod.rs:35:9
test trust_metric_all::consensus::should_be_disconnected_for_repeated_malicious_new_height_broadcast_within_four_intervals ... FAILED
thread 'tokio-runtime-worker' panicked at 'get report: Unexpected("rpc to /rpc_call/diagnostic/trust_report [ProtocolError] Kind: Network Error: Internal(RpcTimeout(None))")', tests/trust_metric_all/consensus.rs:126:37
thread 'trust_metric_all::consensus::should_be_disconnected_for_repeated_undecodeable_choke_within_four_intervals' panicked at 'test pass: JoinError::Panic(...)', tests/trust_metric_all/mod.rs:35:9
thread 'tokio-runtime-worker' panicked at 'fetch trust report: Unexpected("rpc to /rpc_call/diagnostic/trust_report [ProtocolError] Kind: Network Error: Internal(RpcTimeout(None))")', tests/trust_metric_all/mod.rs:137:30
thread 'trust_metric_all::should_be_disconnected_for_repeated_s_strategy_within_17_intervals_from_max_score' panicked at 'test pass: JoinError::Panic(...)', tests/trust_metric_all/mod.rs:35:9
test trust_metric_all::should_be_disconnected_for_repeated_s_strategy_within_17_intervals_from_max_score ... FAILED
test trust_metric_all::should_able_to_reconnect_after_trust_metric_soft_ban ... ok
thread 'tokio-runtime-worker' panicked at 'exec queue dropped!', /rustc/75e1463c52aaea25bd32ed53c73797357e561cce/src/libstd/macros.rs:13:23
test trust_metric_all::consensus::should_be_disconnected_for_repeated_undecodeable_choke_within_four_intervals ... FAILED
test trust_metric_all::consensus::should_be_disconnected_for_repeated_undecodeable_qc_within_four_intervals ... ok
test trust_metric_all::should_be_disconnected_for_repeated_bad_only_within_four_intervals_from_max_score ... ok
test trust_metric_all::consensus::should_be_disconnected_for_repeated_undecodeable_proposal_within_four_intervals ... ok
test trust_metric_all::mempool::should_be_disconnected_for_repeated_wrong_signature_only_within_four_intervals ... ok
test trust_metric_all::mempool::should_be_disconnected_for_repeated_timeout_smaller_than_latest_height_only_within_four_intervals ... ok
test trust_metric_all::consensus::should_be_disconnected_for_repeated_undecodeable_vote_within_four_intervals ... ok
test trust_metric_all::mempool::should_be_disconnected_for_repeated_wrong_tx_hash_only_within_four_intervals ... ok
test trust_metric_all::should_keep_connected_for_z_strategy_but_have_lower_score ... ok

failures:

failures:
    trust_metric_all::consensus::should_be_disconnected_for_repeated_malicious_new_height_broadcast_within_four_intervals
    trust_metric_all::consensus::should_be_disconnected_for_repeated_undecodeable_choke_within_four_intervals
    trust_metric_all::mempool::should_be_disconnected_for_repeated_timeout_larger_than_gap_only_within_four_intervals
    trust_metric_all::should_be_disconnected_for_repeated_s_strategy_within_17_intervals_from_max_score

test result: FAILED. 15 passed; 4 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '-p muta --test trust_metric'
Makefile:19: recipe for target 'test' failed
make: *** [test] Error 101

What you expected to happen:
The make ci is completed
How to reproduce it (as minimally and precisely as possible):
$ git clone https://github.com/yejiayu/muta
$ git checkout -b test-ci
$ make ci

Anything else we need to know?:
Environment:

MutaChain version or commit hash (MutaChain -V):
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:

/cc @zeroqn

/cc @zeroqn


enable ruff with a somewhat minimal configuration

As @caseyjhol noticed the code currently reflects a lot of my personal preferences. In order to get some consistency I thought about adding ruff via pre-commit with a somewhat minimal configuration.
Currently this is not enabled in CI but I just want to know if this is a good idea or not.
@caseyjhol What is your opinion on this?

I haven't had a chance to fully look this over, but I think something like this would be great and definitely improve DX.

In the beginning I also thought that matching the function name 1:1 would be the best option. After working a bit in the mjml source code I decided that camel case is just too painful as it looks too alien in Python. In the end if all camel-case names are converted into snake-case the mental mapping should be pretty fast as well (e.g. fooBar() → foo_bar()).
With .get_attr() I went down a slippery slope: I found that "in that special case" .get_attribute() was pretty long and a shorter method name makes it easier to see what output data is created instead. I could see that we should .get_attribute() but I really would like to use snake-case instead of camel-case.


Todo

Hello
I have added the code for adding todo and displaying it
The user can also delete it

Good Job @Gauravtb2253 but you forgot to add the access part.How the user will be able to access it??

Also do you have more issues to solve
I can do it

Also do you have more issues to solve I can do it

#142  #141 or feel free to add some other feature or whatever you think would be good.

Good Job @Gauravtb2253 but you forgot to add the access part.How the user will be able to access it??

I didnt get the access part Can you pls explain

You haven't added any button in the frontend for the route you the added in the backend.How someone will access it??

Good Job @Gauravtb2253 but you forgot to add the access part.How the user will be able to access it??

I didnt get the access part Can you pls explain

You haven't added any button in the frontend for the route you the added in the backend.How someone will access it??

When the user is logged in there is a plus sign shown in the navbar
From there user can see all todos and add or delete them


Add auto_verify flag in present-proof protocol

Signed-off-by: DaevMithran<EMAIL_ADDRESS>Fix https://github.com/hyperledger/aries-cloudagent-python/issues/1698

Thanks!


[stable/jaeger-operator] Allow creating jaegers in any namespace

FEATURE REQUEST:
Allow creating jaeger instances in any namespace using the jaeger-operator
Currently jaeger-operator refers to metadata.namespace while setting the WATCH_NAMESPACE variable. This implies creating jaeger instances only in the same namespace as the operator. Another limiting factor that would have to change is the usage of a Role instead of ClusterRole.
My question is - is this behaviour intentional and what is the reasoning behind it?
I'm happy to provide necessary changes to fulfil this request. The way I would approach is by allowing to choose between a clusterwide and namespaced deployment. First would allow the operator to watch all namespaces and create a ClusterRole for it to be able to create the necessary resources, while the latter would require a list of namespaces and create a Role for each. The list could by default contain only metadata.namespace if backwards compatibility is desirable.

@mihau no reason. I will work on that to make it available to any namespace

@cpanato I can fix that in the evening, my goal with this issue was to see if there isn't any specific usecase for how it's working right now. Also what is your stance on backwards compatibility here ? I'd prefer to break it and make the operator clusterwide by default.

@mihau no reason. go for it
just make sure to document if there is a breaking change

@cpanato let me know your thoughts on the PR.


introduction to Vim

Looks good so far, we should edit the additional resources we use before merging though

Perhaps we could add a few images to help make things more clear

Sounds good, I'll add an image for the modes for the moment

Looks good, let me fix the diagram issue and I'm good to merge, check over it after too


[Feature Request] Optional sorting by chronological, file size, & alphabetical options.

Chronological would be especially useful for those of us that love to test those new models that are coming out daily these days.
And thank you for this extension!

@JasonHoku This commit contains the sort option. Hope it works like you expected.

It works great! Thank you!

File size would be quite nice as well because often peoples largest models are their best/favorite models ^_^

Sure, no problem. Check the latest commit.


Change expected::Result to outcome::result in hexutil and related places

Description of the Change
Use outcome::result instead of obsolete expected::Result.

Benefits
In new code that uses outcome::result it is quite inconvenient to work with old code that uses expected::Result. This changes fix it.

Possible Drawbacks
If replacement was correct (and tests make sure that it was), then there should be none.

Codecov Report

Merging #72 into master will decrease coverage by 1.23%.
The diff coverage is 44.76%.

@@            Coverage Diff            @@
##           master     #72      +/-   ##
=========================================
- Coverage   79.73%   78.5%   -1.24%
=========================================
  Files         118     119       +1
  Lines        3647    3689      +42
=========================================
- Hits         2908    2896      -12
- Misses        739     793      +54

Impacted Files
Coverage Δ

test/core/libp2p/peer/peer_info_test.cpp
100% <ø> (ø)
:arrow_up:

core/common/buffer.hpp
100% <ø> (ø)
:arrow_up:

test/core/common/hexutil_test.cpp
75% <ø> (ø)
:arrow_up:

core/libp2p/multi/multibase_codec.hpp
100% <ø> (ø)
:arrow_up:

test/core/common/buffer_test.cpp
100% <ø> (ø)
:arrow_up:

test/core/libp2p/multi/multiaddress_test.cpp
100% <ø> (ø)
:arrow_up:

test/core/libp2p/peer/peer_id_test.cpp
100% <ø> (ø)
:arrow_up:

...p2p/multi/multibase_codec/multibase_codec_impl.hpp
100% <ø> (ø)
:arrow_up:

test/core/common/blob_test.cpp
82.35% <0%> (ø)
:arrow_up:

test/core/libp2p/multi/multihash_test.cpp
54.54% <0%> (-45.46%)
:arrow_down:

... and 13 more

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 c195f05...4f7bac3. Read the comment docs.


Locale options?

I think it's better to add locale options considering dayjs already have it, so other timezone can use relative time format too.
Thanks!^^

Per the dayjs documentation, a custom locale can be imported and set as the default locale. I've updated the docs to reflect this.


noncebuild.py

Is your feature request related to a problem? Please describe.

Describe the solution you'd like:

Describe alternatives you've considered:

Additional context:

it is a problem , i have to go to many di


Cannot build the code in Win10

I cannot build this repo in Win10, maybe you could move it to windows. Thank you.
Regards,

Hi @Micalson I don't use Windows a lot so it will be difficult for me to make the port. Feel free to make a pull request with the improvements!
Thanks! :)

@h3ct0r I will have a try.

Hi @h3ct0r , where is the dataset including ellipse? maybe you could upload some images for testing.
Thank you.

It should be fairly straight-forward to set this up in a Docker environment if you really want to run it from Windows but don’t want to go through the process of getting it to work on MSFT C++. You might have to build an interface to expose a port or something.


$PropertyType doesn't type check literal values

/* @flow */

type Action = {
 type: 'App/INIT'
};

// number. This type is incompatible with string literal `App/INIT`
const actionTypeA: $PropertyType<Action, 'type'> = 1;

// No error
const actionTypeB: $PropertyType<Action, 'type'> = 'FOO';

Expected: actionTypeB should fail its type check.

Looks like a dupe of https://github.com/facebook/flow/issues/3374


KubernetesClient cannot fetch action logs correctly

when action pod's log prints like below cases:

some timestamp return 8 digit nanoseconds

2020-07-17T07:28:01.911401988Z log start
2020-07-17T07:28:01.911428485Z undefined
2020-07-17T07:28:01.91164149Z XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX
2020-07-17T07:28:01.911659266Z XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX

in this case, the 2020-07-17T07:28:01.91164149Z would be parsed to 2020-07-17T07:28:01.091164149Z and will be filtered out as it's older than last timestamp, but actually it should be parsed to 2020-07-17T07:28:01.911641490Z

the logs can be unordered

2020-07-17T07:28:02.387244404Z log start
2020-07-17T07:28:02.387326085Z undefined
2020-07-17T07:28:02.387331028Z XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX
2020-07-17T07:28:02.387293122Z XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX

in this case the last log's timestamp is older than the third line, and so it will also be filtered out

In both cases, the KubernetesClient will try to fetch log again and again to get enough log sentinels but always got empty lines returned until timeout(2 seconds)
We can do a benchmark to reproduce this error

@jiangpengcheng is this now fixed?

yes, I will close this


Elasticsearch 5.6.16 shutdown after few seconds of usage

Info:

Docker version ($ Docker version 19.03.4, build 9013bf5):
Laradock commit (04c6aaf (origin/master, origin/HEAD) Merge pull request #2215 from stefnats/gearman):
System info (Mac):
System info disto/version:  (Mac Os Catalina version 10.15)

Issue:

Elasticsearch shutdown after few minutes of using it from my app

Expected behavior:

Elasticsearch should work just fine without shutting down
Reproduce:

Elasticsearch Dockerfile
ARG ELASTICSEARCH_VERSION
FROM docker.elastic.co/elasticsearch/elasticsearch:${ELASTICSEARCH_VERSION}

EXPOSE 9200 9300

In docker-compose.yml
### ElasticSearch ########################################
    elasticsearch:
      build:
        context: ./elasticsearch
        args:
          - ELASTICSEARCH_VERSION=${ELASTICSEARCH_VERSION}
      volumes:
        - elasticsearch:/usr/share/elasticsearch/data
      environment:
        - cluster.name=${ELASTICSEARCH_CLUSTER}
        - node.name=${ELASTICSEARCH_NODE}
        # - bootstrap.memory_lock=true
        - "ES_JAVA_OPTS=-Xms1g -Xmx1g"
        # - cluster.initial_master_nodes=${ELASTICSEARCH_NODE}
        - http.cors.enabled=true
        - http.cors.allow-origin=*
        - xpack.security.enabled=false
      ulimits:
        memlock:
          soft: -1
          hard: -1
      ports:
        - "${ELASTICSEARCH_HOST_HTTP_PORT}:9200"
        # - "${ELASTICSEARCH_HOST_TRANSPORT_PORT}:9300"
      depends_on:
        - php-fpm
      networks:
        - frontend
        - backend

In .env
### ELASTICSEARCH #########################################
ELASTICSEARCH_VERSION=5.6.16
ELASTICSEARCH_HOST_HTTP_PORT=9200
# ELASTICSEARCH_HOST_TRANSPORT_PORT=9300
ELASTICSEARCH_CLUSTER=dockstack-cluster
ELASTICSEARCH_NODE=dockstack-node

Error logs:
view error logs

I installed version 7.1.1, and had a problem with max_map_count I have solved by: run sudo sysctl -w vm.max_map_count=262144


Isolate environment in python operator

This PR fixes an issue with the current usage of exec and opens up the possibility to de-uglify the python operator implementation.

From a user perspective I would have expected to import os anyway in this case.

the only possible concern is that previously code could implictly use the existing imports as in
python "self.x = os.environ['foo']"

From a user perspective I would have expected to need to import os anyway in this case.


ACL operators need to be made stateless to avoid runtime initialization overhead

Output of 'strings libarm_compute.so | grep arm_compute_version':
arm_compute_version=v23.11 Build options: {'Werror': '0', 'debug': '0', 'neon': '1', 'opencl': '0', 'embed_kernels': '0', 'os': 'linux', 'arch': 'armv8a', 'build': 'native', 'multi_isa': '1', 'fixed_format_kernels': '1', 'openmp': '1', 'cppthreads': '0'} Git hash=b'add70ace1e57f65d1ae4d0cedaec6e4578cf87ff'
Platform:
AWS c7g.16xl
Operating System:
Ubuntu 22.04

Problem description:
One of the important optimizations for better inference performance is to cut down the kernel initialization overhead. This can be achieved by caching the operator after first time initialization and reuse it across similar tensor shapes.  Today it's not possible to cache ACL operator because they maintain the workspace state along with the initialization and the workspace is specific to the gemm operation.
The requirement is to make the operators stateless so that they get initialized once and reused across multiple gemm operations of the same shapes.
more details are in this oneDNN discussion: https://github.com/oneapi-src/oneDNN/pull/1455#discussion_r979043207

Hi @snadampal
Thanks for raising this. We will discuss the feature request with the team.

We are about to start the exploratory work for 24.05 to integrate two oneDNN primitives convolution and matrix multiplication to use existing non-public ACL API for using stateless object in order to better understand what (if any) requirements are necessary on ACL side. Once that work is done we plan to address any changes in ACL for 24.08 release and port the rest of oneDNN primitives. We expect the work to be done by 24.11.
As the most of the work that will start will initially be oneDNN specific we will link to this issue PRs from oneDNN to track progress.


Added Azure.ServiceBus.MinTLS

PR Summary

Fixes #1777
Added Azure.ServiceBus.MinTLS rule.
This rule checks for that service bus namespaces uses minimum TLS 1.2 version.
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] Change is not breaking
[x] This PR is ready to merge and is not Work in Progress
Rule changes

[x] Unit tests created/ updated
[x] Rule documentation created/ updated
[x] Link to a filed issue
[x] Change log has been updated with change under unreleased section

Other code changes

[ ] Unit tests created/ updated
[ ] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

@BernieWhite
:shipit: or some adjustments to be carried out?

@BernieWhite
Adjusted, think we're set for merge now.


Accessing resource in custom header

Do you want to request a feature or report a bug?
feature
What's the current behavior?
I want to add some functionality (button or inputs) to day header. When button clicked, I need to pass date and resourceId to my function. Date is already passed to custom header but I cannot access resourceId.
What's the expected behavior?
components={{
  day: {
     header: ({date, label, localizer /* resource may be added here */}) =>

{moment(date).format("DD/MM/YYYY")}

              <button onClick={() => this.doSomething(date, resourceId)}></button>

  }
}}

Have you found any solution to that?

Sorry for late reply...
As workaround, I had put resource id to element, then queried the element from dom.
resourceTitleAccessor={(resource) =>
...
}
day: {     header: ({date, localizer}) => (<CustomInput />) }
class CustomInput extends Component {
componentDidMount() {
    this.resourceId = this.myDiv ?
                            Number(this.myDiv
                                .closest('.rbc-time-header-content')
                                .querySelector('.custom-resource-header')
                                .id)
                            : undefined;
}

render() {
     return (
 this.myDiv = ref}>...
);
}

}


SSH key support

The rule is working fine but I'd like to use it also with an identity file.
Would you mind a PR on this topic?
The aim is to support authentication via an SSH public/private key pair.
If it's ok for you then there is already an implementation in #15

I know it's a little old (and using junit4) but I find a way to use a public key:
download the source (only one file) from the git and add to 'startServer' after 'setPort':
        SimpleGeneratorHostKeyProvider keyPairProvider = hostKeyPath != null ? new SimpleGeneratorHostKeyProvider(hostKeyPath)
                : new SimpleGeneratorHostKeyProvider();
        server.setKeyPairProvider(keyPairProvider);
        server.setPublickeyAuthenticator(new AuthorizedKeysAuthenticator(new File(hostKeyPath.toString())));

of course, add  private Path hostKeyPath = null in the variables and a setter:
```
public FakeSftpServerRule setHostKeyPath(Path hostKeyPath) {
this.hostKeyPath = hostKeyPath;
if (server != null)
restartServer();
return this;
}

@Assafkalfa I do not remember how the code under test was working but the test was implemented quite simply:
	@Rule
	public final FakeSftpServerRule sftpServer = new FakeSftpServerRule();

	@Test
	public void should_send_file() throws Exception {
		// add identity
	        Path authorizedKeysPath = Paths.get(FtrServiceTest.class.getResource("/unit-test-user.pub").toURI());
	        sftpServer.addIdentity("jon.snow", authorizedKeysPath);

		// call code under test

		//check
		assertTrue("remote file not found", sftpServer.existsFile("/666_myfile.txt"));
	}

It was a one time usage so I cannot help you on other usage of this component.


Improve descriptions for analytical OData annotations

@UweSchwerk @voicis could you please have a look at this proposal?

changeset is missing or should this change not trigger the release of a new version of the module?

@tobiasqueck Done

@tobiasqueck : any idea what causes the failures? I.e. git cannot checkout code...
Could it be because PR is based on forked repo ?

@tobiasqueck : any idea what causes the failures? I.e. git cannot checkout code... Could it be because PR is based on forked repo ?

Yes, there still is the issue with the pipeline when running from a fork. I'd recommend that @UweSchwerk creates a new branch in the original repo, and then @stewsk creates a new PR from his branch to the new one. Then merge it and wait for the pipeline to go green in the new branch.

New PR: https://github.com/SAP/open-ux-tools/pull/1749


Fix file-changes-action error

fixes file-changes-action error
Run<EMAIL_ADDRESS>Error: undefined
Exception: {
  "error": "404/HttpError",
  "from": "undefined/Error",
  "message": "There was an error getting change files for repo:free-programming-books owner:EbookFoundation base:0000000000000000000000000000000000000000 head:660e45f2a326dfa11d511aabfdfb51c44c15a94c",
  "payload": {
    "name": "HttpError",
    "status": 404,

Is the current push error on #5199 still relevant?
Warning: Received event from pull_request, but also received a before(660e45f2a326dfa11d511aabfdfb51c44c15a94c) or after(53910ae949e9cb6710f4c096dd6ffdf2203a42bd) value.
 I am assuming you want to use a Push event but forgot something, so I'm giving you a message.
(node:2432) UnhandledPromiseRejectionWarning: Error: {"error":"500/TypeError","from":"sortChangedFiles","message":"There was an issue sorting files changed.","payload":"{}"}
    at run (/home/runner/work/_actions/trilom/file-changes-action/v1.2.3/dist/index.js:1:19989)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:2432) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2432) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Error: There was an issue sorting changed files from Github.
Exception: {
  "error": "500/TypeError",
  "from": "sortChangedFiles",
  "message": "There was an issue sorting files changed.",
  "payload": "{}"
}```

hmm looks like downgrading from 1.2.4 to 1.2.3 for file-changes-action made us incompatible with some recent-ish github api changes and it looks like the solution was to just use 1.2.4
we can try putting it back to 1.2.4 and see if the original issue reappears. might just be a glitch with githubs ci system like we saw in #5200
i hate to erode our confidence in getting consistent test results by having to run-recheck again but this feels like a github infrastructure issue


What are required dependencies?

I followed the readme but after adding
    <PackageReference Include="Liquid.Serverless.AzureFunctions" Version="2.0.2-alpha" />

the sample doesn't compile
error CS0234: The type or namespace name 'Context' does not exist in the namespace 'Liquid.Core' (are you missing an assembly reference?)
error CS0234: The type or namespace name 'Telemetry' does not exist in the namespace 'Liquid.Core' (are you missing an assembly reference?)
error CS0234: The type or namespace name 'DependencyInjection' does not exist in the namespace 'Liquid.Core' (are you missing an assembly reference?)
error CS0246: The type or namespace name 'ILightContext' could not be found (are you missing a using directive or an assembly reference?)
error CS0246: The type or namespace name 'ILightTelemetry' could not be found (are you missing a using directive or an assembly reference?)

looks like Serverless works only with <PackageReference Include="Liquid.Core" Version="2.0.2-alpha" /> but all other packages already updated to 2.1.0.
It's very hard to figure out what depends on what.
There also seems to be a hard dependency on appsettings.json not covered in wiki
System.Private.CoreLib: The configuration file 'appsettings.json' was not found and is not optional.

but azure functions don't use appsettings.json


Convert s_agent_rewards to a policy and the three s_total_reward mechanisms to just take it in as an input

The four functions are just copies of the same exact code returning different things. Really inefficient and dangerous to not having changes updated in all places

sgtm


Renaming InternalDataStore/InGame/Resources to Resources_RENAMED causes editor exceptions and prevents project view from drawing in 2.71

I renamed the resources folder that I think DCS uses since I dont need it and it was adding a ton of stuff to my headless server builds.  Doing so caused exceptions when running (even an empty scene) and also prevented the project view from being drawn at all.
Repro:

Open up new project with UMA
Open empty scene
Rename InternalDataStore/InGame/Resources to Resources_RENAMED
Run empty scene
Note exceptions, project view doesn't draw anymore

NullReferenceException: Object reference not set to an instance of an object
UMA.UMAEditorUtilities.DrawItems (System.String guid, UnityEngine.Rect selectionRect) (at Assets/UMA/Core/Scripts/Editor/UMAEditorUtilities.cs:74)
UnityEditor.ProjectBrowser.OnGUIAssetCallback (System.Int32 instanceID, UnityEngine.Rect rect) (at C:/buildslave/unity/build/Editor/Mono/ProjectBrowser.cs:613)
UnityEditor.IMGUI.Controls.TreeViewController.DoItemGUI (UnityEditor.IMGUI.Controls.TreeViewItem item, System.Int32 row, System.Single rowWidth, System.Boolean hasFocus) (at
The exception is on line:
AssetItem ai = UMAAssetIndexer.Instance.FromGuid(guid);
because the singleton doesn't exist.
Adding this trivially resolve the issue;
        if (UMAAssetIndexer.Instance == null)
            return;

This change is included in pull request 139.


*: update dependencies

Mostly for gRPC. Now it supports server side interceptor. We can do rate limiting / logging at RPC level easily now.

lgtm

lgtm after test passes. thanks.

Seems like we need to wait for protoc-gen-gogo update. The gRPC change requires some change of generated code.

This is blocked on https://github.com/gogo/protobuf/issues/169.

Closing via https://github.com/coreos/etcd/pull/5159.


Waiting for viewDidAppear: call on the view controller.

Please find the log file below:
earlgrey.log
I'm having a problem that framework is not able to find the accessibility element on view controler and throws timeout giving the output in the logs.
One of the messages in the log is this one:
GREYAppStateTracker" : "Waiting for viewDidAppear: call on the view controller. Please ensure that this view controller and its subclasses call through to their super's implementation. Waiting for UIView's draw/layout pass to complete. A draw/layout pass normally completes in the next runloop drain.
I have checked and view controller class uses super.viewDidLoad().
I have found the way to make the test pass by adding
        GREYConfiguration.sharedInstance().setValue(false, forConfigKey: kGREYConfigKeySynchronizationEnabled) to the setUp method but I read it's not recommended with EarlGrey as it disables Synchronization.
but when I set this to true tests are failing.
Any ideas what might be the issue?
Thanks,
Bart

You checked viewDidLoad but did you also check that it calls super’s viewDidAppear

Fixed!  super.viewDidLoad(animated) wasn't being called in func viewDidLoad


Make Azure DevOps project public

I'm opening this up for discussion.
What are the pro's and con's of making the Azure DevOps project (the one that is building the container images) public? Read more about public projects here

The current build is running in an organization that is inappropriate for a public project. We are looking into migrating to an appropriate Azure DevOps org.

the pipelines are public and can be accessed here > https://dev.azure.com/ms/azure-databricks-operator


Using Huggingface Estimator - exec: "serve": executable file not found in $PATH

I've successfully used the Sagemaker (2.69.0), Huggingface (4.10) and Tensorflow (2.5) libraries to complete training a model, initiated as follows:
model_name = 'bert-base-cased'
import datetime
ct = datetime.datetime.now()
current_time = str(ct.now()).replace(":", "-").replace(" ", "-")[:19]
training_job_name=f'finetune-{model_name}-{current_time}'
print( training_job_name )

from sagemaker.huggingface import HuggingFace

# hyperparameters, which are passed into the training job
hyperparameters={'epochs': 1,
                 'train_batch_size': 16,
                 'eval_batch_size' : 32,
                 'model_name': model_name
                 }

huggingface_estimator = HuggingFace(entry_point='train.py',
                            source_dir='./scripts',
                            instance_type='ml.p3.2xlarge',
                            instance_count=1,
                            role=role,
                            transformers_version='4.10',
                            tensorflow_version='2.5',
                            py_version='py37',
                            hyperparameters = hyperparameters)

# starting the train job with our uploaded datasets as input
huggingface_estimator.fit({'train': training_input_path, 'test': test_input_path}, job_name=training_job_name)

The training script starts with the usual argument parsing and log configuration. It differs from the samples as it adds some additional layers to the model for fine tuning. It also freezes all the layers in the base bert-base-cased model (to avoid OOM issues, with GPU memory, when training)
base_model = TFAutoModel.from_pretrained(args.model_name)
    tokenizer = AutoTokenizer.from_pretrained(args.model_name)

    # lock base model layers so only the additional task specific layers are
    # changed. Trying to get past OOM blocker
    for layer in base_model.layers:
        layer.trainable=False

    # two input layers, we ensure layer name variables match to dictionary keys in TF dataset
    input_ids = tf.keras.layers.Input(shape=(512,), name='input_ids', dtype='int32')
    mask = tf.keras.layers.Input(shape=(512,), name='attention_mask', dtype='int32')

    # we access the transformer model within our bert object using the bert attribute (eg bert.bert instead of bert)
    embeddings = base_model.bert(input_ids, attention_mask=mask)[1]  # access final activations (alread max-pooled) [1]
    # convert bert embeddings into 5 output classes
    x = tf.keras.layers.Dense(1024, activation='relu')(embeddings)
    y = tf.keras.layers.Dense(5, activation='softmax', name='outputs')(x)

    model = tf.keras.Model(inputs=[input_ids, mask], outputs=y)

    # fine optimizer and loss
    optimizer = tf.keras.optimizers.Adam(learning_rate=args.learning_rate)
    loss = tf.keras.losses.CategoricalCrossentropy()
    acc = tf.keras.metrics.CategoricalAccuracy('accuracy')
    model.compile(optimizer=optimizer, loss=loss, metrics=[acc])

    # Preprocess train dataset
    train_features = {
        "input_ids": train_dataset["input_ids"],
        "attention_mask": train_dataset["attention_mask"]
    }
    tf_train_dataset = tf.data.Dataset.from_tensor_slices((train_features, train_dataset["labels"])).batch(
        args.train_batch_size
    )

    # Preprocess test dataset
    test_features = {
        "input_ids": test_dataset["input_ids"],
        "attention_mask": test_dataset["attention_mask"]
    }
    tf_test_dataset = tf.data.Dataset.from_tensor_slices((test_features, test_dataset["labels"])).batch(
        args.eval_batch_size
    )

    # Training
    if args.do_train:

        train_results = model.fit(tf_train_dataset, epochs=args.epochs, batch_size=args.train_batch_size)
        logger.info("*** Train ***")

        output_eval_file = os.path.join(args.output_data_dir, "train_results.txt")

        with open(output_eval_file, "w") as writer:
            logger.info("***** Train results *****")
            logger.info(train_results)
            for key, value in train_results.history.items():
                logger.info("  %s = %s", key, value)
                writer.write("%s = %s\n" % (key, value))

    # Evaluation
    if args.do_eval:

        result = model.evaluate(tf_test_dataset, batch_size=args.eval_batch_size, return_dict=True)
        logger.info("*** Evaluate ***")

        output_eval_file = os.path.join(args.output_data_dir, "eval_results.txt")

        with open(output_eval_file, "w") as writer:
            logger.info("***** Eval results *****")
            logger.info(result)
            for key, value in result.items():
                logger.info("  %s = %s", key, value)
                writer.write("%s = %s\n" % (key, value))

    # Save result
    model_dir = f'{args.model_dir}/00000001'
    model.save(model_dir)
    tokenizer.save_pretrained(model_dir)

I can successfully download the trained model from S3, unzip it in terminal on the SM notebook instance and then load the model directly with Tensorflow to perform inference operations.
import tensorflow as tf

model = tf.keras.models.load_model("/home/ec2-user/SageMaker/00000001")

So the model seems to have trained correctly and works. However, when I try and deploy as an SM endpoint:
from sagemaker.estimator import Estimator

# job which is going to be attached to the estimator
old_training_job_name='finetune-bert-base-cased-2021-12-08-20-18-18'

# attach old training job
huggingface_estimator_loaded = Estimator.attach(old_training_job_name)

# get model output s3 from training job
huggingface_estimator_loaded.model_data

This works and displays the expected display for the model_data, but then:
predictor = huggingface_estimator_loaded.deploy(1,"ml.g4dn.xlarge")

Eventually fails. The Endpoint view in AWS console says: "The primary container for production variant AllTraffic did not pass the ping health check. Please check CloudWatch logs for this endpoint."
Looking into the logs for the endpoint, I see the message repeated 100 times or so:
"exec: "serve": executable file not found in $PATH"
Is this a bug in the Huggingface Docker image, as the only help I've seen for this type of error relates to people hand rolling their containers incorrectly. Or is there some issue in the way that I'm training and saving the model that causes this issue? I've been able to successfully deploy an endpoint with huggingface using the standard samples, so I wonder if this issue is to do with the extra layers that I added to the model? If that's the case I'd love to know how to fix this and this issue would then be a request for more useful logs or errors messages to debug these scenarios.
Thanks!

Hello @brett--anderson,
Could you share the cloudwatch logs from the endpoint? They should include why the endpoint creation failed.
But I am not sure if the "zero-code" deployment works. The Zero-code deployment feature is built on top of the pipelines from transformers and since you are using a custom model it might be possible that you need to provide your own custom inference.py.
P.S. is there a reason why you are creating a custom model, the layers you add are pretty similar to the TFAutoModelForSequenceClassification from transformers.

Hey @brett--anderson
Sounds good happy to help you when you have question about the custom inference.py. You can find more documentation at https://huggingface.co/docs/sagemaker.
We also have a course for transformers created and maintained by the Open Source team at https://huggingface.co/course/chapter1/1.


encoding/csv: unhelpful error location with badly quoted fields

I'm working with hundreds of 100,000+ line tsv files. They contain quotes in inappropriate places, so I am using LazyQuotes. However, somewhere in the guts of a few of the files, there are quotes at the beginning of a field, which breaks csv.Reader. That is #6287. When that happens, and LazyQuotes is on, the reported error location is at the very end of the file. See https://play.golang.org/p/y0jOObyBTV for an illustration of this.
However, if I turn LazyQuotes off, I get an error location on some other quotes that do no harm (with LazyQuotes on). I am left with an unreadable file that I cannot even fix manually, since there are some errors somewhere in hundreds of thousands of lines, but encoding/csv does not tell me where.
The error reported when LazyQuotes is on should probably at the beginning of the field in question if EOF is reached.
Also related: #3150.
I have some workarounds available. Just adding this to the list of encoding/csv quote issues. :)

Am I missing something, or does LazyQuotes break even if the quote isn't at the beginning of the field? E.g. https://play.golang.org/p/COB-5LuVeg

For ErrFieldCount (which seems to be the problem child here) the column is always reported as 0 to make it clear that the whole record is the problem. I think the bigger problem here is the reported line. In the code from the playground link above, the Reader reads until EOF which is in line 5, but the record starts in line 3 and the other lines shouldn't even be part of the line. This could be solved by tracking the line a record started on and using this for errors instead.

/cc @bradfitz @pborman

I send a change which improves the issue described here by reporting the line where a record started, as proposed in my first comment. With this the Reader still reports column 0 for ErrFieldCount, but it should be much easier to find the problems in the files.

5d14ac74f614631a38be95cc9724ff38068c6c76 was just merged, so with tip the code from the play ground example now reports
line 3, column 4: extraneous " in field
line 3, column 0: wrong number of fields in line

This seems much better to me, since it now reports the correct line. The column is still 0, but this is an explicit design choice and I think that in this case (ErrFieldCount) there isn't much value to the exact column when we already have the line.

@nussjustin seems good enough to me. Thanks!


Support basic mutability

Codecov Report
Attention: 13 lines in your changes are missing coverage. Please review.

Comparison is base (b0faece) 81.03% compared to head (b2e0b6d) 81.07%.

Files
Patch %
Lines

src/Escalier.TypeChecker/Infer.fs
74.35%
10 Missing :warning:

src/Escalier.Parser/Parser.fs
97.67%
1 Missing :warning:

src/Escalier.TypeChecker/Env.fs
66.66%
1 Missing :warning:

src/Escalier.TypeChecker/Visitor.fs
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #123      +/-   ##
==========================================
+ Coverage   81.03%   81.07%   +0.04%
==========================================
  Files          19       19
  Lines        5806     5856      +50
  Branches      747      761      +14
==========================================
+ Hits         4705     4748      +43
- Misses       1101     1108       +7

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


Daeladus + Other Wallets Unable to send $ADA to wallet address to change Pledge

The wallet address on pools uses the oldest address, I've had too many transactions on my old address and I am now unable to send myself more than 1800 ADA to change my Pledge. I don't want to send multiple small transactions and get all those fees.
The only solution I see is creating an entirely new hardware wallet and sending the ADA to that wallet. But considering my pool is setup with my hardware wallet I do not want to do that at the moment (just creates possible chances of mistakes etc) and hope there is a fix to this problem.
I've tried every wallet, adalite, yoroi, daeladus. Unable to send more than 1800 ada to myself. Too many transactions is the error. I had an NFT sale which was on that address, bad idea on my part, but I don't think this should be the case...

Here is the thread I created on the Cardano Forums
https://forum.cardano.org/t/transaction-too-big-due-to-too-many-inputs/71637

Let me see if I got this straight:

You have a personal wallet with many NFTs
You want to send ada from that wallet to your stake pool's pledge address
Daedalus and other wallets allow you to create only a transaction of 1800 ADA

If my understanding is correct, I would say your real problems are the NFTs and that you should first try to move all of them into a different wallet or at least group them in the existing wallet. Daedalus and other wallets are never limiting your transactions by amount. Your only limitation is the UTXO fragmentation and the NFTs count.

There is only a few nfts in that wallet. The problem is I did a NFT sale of 999 so I had many Ada transactions not nfts.
Sent from my iPhone

On Sep 6, 2021, at 05:54, Nikola Glumac @.***> wrote:

Let me see if I got this straight:
You have a personal wallet with many NFTs
You want to send ada from that wallet to your stake pool's pledge address
Daedalus and other wallets allow you to create only a transaction of 1800 ADA
If my understanding is correct, I would say your real problems are the NFTs and that you should first try to move all of them into a different wallet or at least group them in the existing wallet. Daedalus and other wallets are never limiting your transactions by amount. Your only limitation is the UTXO fragmentation and the NFTs count.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

It sounds like a cardano-wallet issue.
@diicasses please share the logs.
@rvl can you please transfer this ticket to https://github.com/input-output-hk/cardano-wallet repo?

How do I share the logs?
Sent from my iPhone

On Sep 7, 2021, at 03:54, Nikola Glumac @.***> wrote:

It sounds like a cardano-wallet issue.
@diicasses please share the logs.
@rvl can you please transfer this ticket to https://github.com/input-output-hk/cardano-wallet repo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


Incompatible with IDEA 2020.3

Incompatible with IDEA 2020.3

@AprilViolet, thanks! We will release an updated version soon.

We've released a new version of the plugin that is compatible with 2020.3. Also, it provides a possibility to check the refactorings in pull requests.


Add missing external to rollup config

This adds date-fns/_lib/format/longFormatters to externals array. Otherwise the built file would contain this dependency and at would fail if bundled using rollup because of Object.defineProperty(t, { __esModule: true }) call where t would be undefined

I posted alternative solution here: #1907

Do you have a preferred way of fixing this?

Merged #1907


Allow to explicit use userMenu in the theme configuration

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Proposed changes
Allow using userMenu explicitly in the theme configuration by enabling to set to true or false and have the expected behavior of show and hide the user menu.

Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[x] I have added suitable unit tests to cover the new/changed functionality

Coverage decreased (-0.04%) to 69.11% when pulling fa84c4e4613a67c5dc066cbde1a4793a6376c22e on kelvininc:user_menu_theme_improvement into c433f736a5b7d3182f3a538a129fea2f6b4350d7 on node-red:master.


inappropriate message to refresh browser

I get this message immediately after refreshing the browser.

The addons dropdown looks like this:

If I log out and log back in, the addon appears to be normal.  Perhaps that should be the message?

Handled on #185

Handled on #185


tests: email/password confirm user

Create tests for email/password confirm user tokens and auto confirm user.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
400

Relevant Lines:
427

💛  - Coveralls


slowMo not working

My root jest-puppeteer.config.js:
const isDev = true

module.exports = {
  server: {
    command: 'node puppeteer/server.js',
    port: 1337,
  },
  launch: {
    // dumpio: true,
    slowMo: 1200,
    headless: !isDev,
    executablePath: isDev ? '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' : undefined,
  },
}

But no slowMo detected: tests are executed as fast as possible, nothing can be observed. Is there any secrets on how to switch on the slowMo flag?

I just tested it and it does not work, it should be a Puppeteer issue because, all options specified in launch are passed to Puppeteer.launch, is this option working without Jest Puppeteer?

You can also set the slowMo property in the options object parameter for puppeteer.connect. I believe this is missing in the PuppeteerEnvironment class where puppeteer.connect is called.


include the notion of "paragraph" and user defined words-separator

in xedit, ctrl-up send you to the cursor to the next white line before the current paragraph,
ctrl-down does the same, but in the opposite direction, hence goes to the white line right after the current paragraph.
Currently, seems like micro doesn't have the notion of "paragraph", only "words" and characters.
Also, would be nice if the user could choose characters to include as word-separators. At least I couldn't see it in settings.json
So as lone '_' aren't counted as words, for instance. Very nice feature it would be.

Huh? Micro already has paragraph movement. Alt-Shift-{ (previous) and Alt-Shift-} (next)

Huh ? But it's not lised in ":help keybindings" !
Plus, with a French keyboard, that comination is horrendous. But I
wouldn't mind if I could change it. Really, I do not see it, no
"paragraph" related action. Have you added it recently ?
2017-12-28 17:26 UTC+01:00, sum01<EMAIL_ADDRESS>
Huh? Micro already has paragraph movement. Alt-Shift-{ (previous) and
Alt-Shift-} (next)
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/zyedidia/micro/issues/968#issuecomment-354315124

Yes the ParagraphPrevious and ParagraphNext actions were recently added. They are very simple notions of a paragraph -- simply jump to the next empty line. They were implemented in ec221c0bc403b3501ff046b146573cdfd6640465 and mentioned in the changelog for 1.3.4. They should also be listed in help keybindings. Perhaps you have an older version?

it seems. No problem, I'll rebuild it. What a delight to see a program
in growing up !
What happens when there are several empty lines ? Does it go to the
next non empty line ?
And what do you think of my other proposition, the user-defined
word-separator (or paragraph-separator, by the way) ? Does it seem
doable with time ? It would be extremely useful. Especially with
dealing with strange languages' character sets, or strange config
files whose syntax is unknown to micro.
2017-12-29 17:14 UTC+01:00, Zachary Yedidia<EMAIL_ADDRESS>
Yes the ParagraphPrevious and ParagraphNext actions were recently added.
They are very simple notions of a paragraph -- simply jump to the next empty
line. They were implemented in ec221c0bc403b3501ff046b146573cdfd6640465 and
mentioned in the changelog for 1.3.4. They should also be listed in help keybindings. Perhaps you have an older version?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/zyedidia/micro/issues/968#issuecomment-354465683

With several empty lines it stops at the first one it finds.
I think your proposition wouldn't be too difficult to implement (paragraph separator would be easier). I'm just wondering what the use-case for a word separator would be.

If my coding style implies letting ony user defined identifiers (like
type names) to begin with capital characters, I could jump from one
type/variable name to another easily. And have multiple shortcuts for
jumping to either '(' or '' or anything you want, would be very nice,
depending on the particuliar language being programmed in.
I can see lots of use cases. Things emacs users probably do all the
time, but the world could get rid of bloatware like emacs and still
provide that feature ;-)
2017-12-31 17:55 UTC+01:00, Zachary Yedidia<EMAIL_ADDRESS>
With several empty lines it stops at the first one it finds.
I think your proposition wouldn't be too difficult to implement (paragraph
separator would be easier). I'm just wondering what the use-case for a word
separator would be.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/zyedidia/micro/issues/968#issuecomment-354614161

You can just use CtrlF and find what you need, no?
I guess if you really wanted to, you could use this bookmarks plugin, but I haven't tried it so it might not be what you want.

That plugin seems cool, but you guessed right, not quite my point.
control-f in no good either, since usually, there will dozens of such
places in a code. Those are language keywords, they are meant to be
written many many times... to do ctrl+f each time, considered keywords
are in tens of place throughout a code, would be a hassle.
Maybe it's already possible, to record (easily, without lua code
please ;,,) a "find x" action and bind it how you want ?
2018-01-01 19:49 UTC+01:00, sum01<EMAIL_ADDRESS>
You can just use CtrlF and find what you need, no?
I guess if you really wanted to, you could use this bookmarks
plugin, but I haven't
tried it so it might not be what you want.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/zyedidia/micro/issues/968#issuecomment-354669088

I don't think you do it all in bindings.json, since you can't make it type letters.
A plugin could probably do that, and I don't think it would be too hard to make either.


IOS里pod update 支付宝插件出现错误

Your questions.

Environment.

Mobile model: iphoneX
Mobile system: iOS 11
Dev platform: mac
Node: v8.9.2
Npm: 4.6.1
Ruby: 2.5
eros verison : 2.0.8 beta 3

What do you think may be caused by the analysis of the problem.

Reappearance of the problem (It's best to have a screenshot).

去支付宝插件提isuess，不是我们维护的

打扰了


Delete .zip from /tmp after load to free space (slim_handler=true)

Context

Currently, when using slim_handler=true, the project source zip file at /tmp/my_project.zip is not deleted after it is extracted.
Projects that download additional dependencies (tensorflow/sklearn models, binaries, video, etc) at runtime can burn through the available 500 mb pretty quickly and throw OSError resource exhausted errors.
What are your thoughts on deleting the project zip file after it's been decompressed?
I'll submit a PR if approved.

Fantastic idea

I changed a bit more than originally proposed.
In case it isn't clear why I didn't just os.remove('/tmp/project.zip') at the end of zappa.handler.load_remote_project_zip please see below
tl;dr

The punchline is that you can always deploy your resource files with zappa deploy rather than downloading them from s3 in application code.

Scenario - Deployment source is ~60MB and resources (models, etc) are ~300MB
Lets say, the resulting zip file with source and resources came to 350MB
Currently, the deployment would fail because slim_handler tries to store project.zip (350MB) and the unzipped folder (360MB) in /tmp (500MB) at the same time. Bolting os.remove('/tmp/project.zip') onto the end of load_remote_project_zip doesn't help because the failure occurs before we get that far.
The most common way around that issue is to copy the large resource files to s3 independently and write a bunch of boilerplate in your application to put them in the right place when you have a cold start.
As written, #1022 tries to store project.zip in-memory (failing over onto /tmp). In that case, if the lambda instance has enough memory, you can deploy any zip file that decompresses into < 500MB. The punchline is that you can always deploy your resource files with zappa deploy rather than downloading them from s3 in application code.
Additionally, you know in advance if your deployment is going to fit in Lambda. If your local project folder is < 500MB and the instance's memory size > ~530MB, its going to fit.


feat: Add KubeOps

Add KubeOps

[ ] You've read the Contributor Guide and Code of Conduct.
[ ] You've included unit or integration tests for your change, where applicable.
[ ] You've included inline docs for your change, where applicable.
[ ] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Summary of the changes
This changes contains added source code for KubeOps.
Description
The files added are regarding KubeOps which contains entities, CRDs and other C# files. Almost all the source code was written by @keithlogan94
Fixes #138

@AndrewBabbitt97  ready for review again.

Simple two changes, not sure why these were added after the previous review as they were never requested to be added

Otherwise LGTM

Simple two changes, not sure why these were added after the previous review as they were never requested to be added

I believe I added it at the time to allow default values element in the associated class.


browser+proxy: prequire error plugin-k8s TypeError: "fs.closeSync is undefined"

regression caused by https://github.com/IBM/kui/pull/1814/files#diff-434b9b38d58b07cacd3865f5668bd929R19


Loading modules / themes from additional folder

The current module harvester looks into the modules folder, but not at sub folders or specific other folders.
I would like to set harvesting to look at additional folders (but without making changes to the orchard code)
Justification:
I would like to organize my modules (and contributions etc) in separate folders so they can be managed more conveniently by their own git or other managers and not interfere with the full project git.

So,
in the OrchardStarter class where are autofac container registrations exists code:
builder.RegisterType<ModuleFolders>()
       .As<IExtensionFolders>().SingleInstance()
       .WithParameter(new NamedParameter("paths", new[] { "~/Modules" }));

I think you can override ModuleFolders class by your custom simple module but I'm not sure if SuppressDependency attibute will work.
But it seems to me that you can also take advantage of autofac modules and re-register ModuleFolders with your new implementation.

Thanks Ermesx,
It seems like the natural thing would be to add some settings to ~/config/host.config , unfortunately I am not that familiar enough with autofac so I would appreciate an advice about how to do this.
The other option would be to add this setting to web.config (or to ModuleFolders class) and make a small change to the harvester - but before burdening people with another PR I would like to make sure first that I am not missing a trivial solution.

Duplicate of  #5019.

@qt1 It seems you have good experience on this topic.
I'm looking for a way to load themes from sub directories of Media folder because i want to hold themes per tenant.
I would like to allow users to change the theme of their site. I think this is very useful feature.
Can you help me please?

@armanforghani You can configure which themes are available per tenant using the Themes field in the Settings.txt file of your tenant. E.g.
State: Uninitialized
Themes: ThemeA, ThemeC
Name: MyTenant
...

Hope that helps.

@sfmskywalker Thank you but it is not what i want. I want the users be able to write their themes. In other words i want Orchard Harvester also searches Media folder for overridden templates.
I used IShapeTemplateHarvester and IShapeTemplateViewEngine but they work for view templates and not for shape templates. Ex. Index.cshtml has been found in Media folder but Menu.cshtml has not been found.

Having write access to executable code seems to me like a security risk.
The code in cshtml can access everything and is not limited to specific tenant access. Anyone that can write cshtml is effectively a superuser and can mess things up for all other tenants (e.g. have unlimited access to the database).

I understand your concern but i will only allow liquid markup instead of razor. It has limited access.

In principal it can be done - try adding the path to web.config .
I would, however, consider writing a specific module that will handle the functionality and the security. The current harvester/loader would just load everything in its path so setting up the security (and prevent bypassing it) will be tricky at best..

I don't want to share media themes for all tenant. Each tenant should have access to its theme in media folder of that tenant.

You can still limit theme access by the landlord so each tenant will be able to select only to the theme(s) it can access for writing.

I know i can limit access to the theme but this does not cover my needs.
I want the user be able to overwrite some templates of install theme or develops a theme from scratch.
I'm looking for a way like MediaTheme in DotNest sites.


Why postAgent ran without any event in

I has a postAgent Schedule 6am, my configuration items are as follows:
{
  "post_url": "xxxx",
  "expected_receive_period_in_days": "10",
  "content_type": "json",
  "method": "post",
  "payload": {
    "msgtype": "markdown",
    "markdown": {
      "content": "# {{ title }}{% line_break %}{{ content }}"
    }
  },
  "headers": {},
  "emit_events": "false",
  "no_merge": "false",
  "output_mode": "clean"
}

I set up a Sources for this postAgent, which does not have event emited every day, so sometimes the payload will be empty, but the agent will run.
what's wrong with my configuration?

Don't schedule the agent if you don't want it to run by itself on that schedule. The postagent will run when it receives the event from the source-agent.


Add benchmarking using arbitrary fuzzing

This is the start of my very roundabout way to get back to #444, where we really need a benchmark that captures something other than JSON-like-RON to ron::Value. I hope to upgrade our arbitrary fuzzer to use proper typing to generate an arbitrary data structure and its corresponding Serialize and Deserialize implementation. For a new PR, we would then first run the fuzzer, then extract the corpus for the arbitrary target, and then benchmark serialising and deserialising based on these examples. Ideally, the current main branch would also be pulled in again and run on these benchmarks as well to provide an automatic comparison.
This will probably take me several weekends to fully implement, but I hope it will finally give us the needed insights to land #444 with the best perf-maintainability tradeoff.

[ ] I've included my change in CHANGELOG.md

Codecov Report
Patch coverage: 71.05% and project coverage change: +0.01 :tada:

Comparison is base (94a5ce9) 85.24% compared to head (023758e) 85.26%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #465      +/-   ##
==========================================
+ Coverage   85.24%   85.26%   +0.01%
==========================================
  Files          62       62
  Lines        7830     7838       +8
==========================================
+ Hits         6675     6683       +8
  Misses       1155     1155

Impacted Files
Coverage Δ

src/ser/mod.rs
71.17% <71.05%> (+0.27%)
:arrow_up:

... and 1 file 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.

?r @torkleyy @manunio This PR became quite big and contains several parts:

upgrade the arbitrary fuzzer to fuzz any serde data types and values (excluding anything requiring attributes)
fix any bugs discovered by the fuzzer so far
small code style improvements along the way

If you have some time, I'd appreciate any feedback you can give on this PR - thanks in advance!

P.S. the benchmarking CI test is expected to still fail since it cannot yet compare against the benchmark on the main branch, which is only added in this PR


Add sequence ports to non-constant CallBasic VS nodes

Fixes #10440.
Screenshot:

Lgtm

Hope it get merged soon ;p

Apologies, this is not the right fix. Sequence ports are missing on functions with const cast. The problem
is that built-in functions are all const for some reason. When fixed, this will work. I'm working on it.


Executable fixes

Fixes the "Execute" permission missing from the binary files and adds a working freetype6.dll.

I accidentally included the commit from #8. It shouldn't be too much of a hassle though.

Just a heads up I had to replace your Roboto font. You unfortunately did not subtract from the decal id to get the images causing the image labels to error in some cases. I uploaded a fixed copy but I don't have the patience you do so it is only 4 styles.

Ah, sorry about that. I could set up a script to scrape the proper IDs though.

A little update on that; I did manage to scrape the IDs, and the updated script is available on my fork of this. Sadly I'm having issues with Roblox refusing to replicate the ModuleScript over the network due to it being too big. (> 1,5 MB) I might work something out though, maybe I'll split it to multiple ModuleScripts.

I'll look into changing the font builder to split it up in the future. Are you sure the limit is 1.5 mb?

I'm not sure what the limit is, but the script is a little over 1*,*5 MB which is too much.


prevent quic-go from building on Go 1.17

It looks like Go 1.17 won't introduce any changes to the structs for which we assert that they're identical between qtls and crypto/tls. That means that in principle, it would be possible to build quic-go using Go 1.17. We should prevent this, as users might expect Go 1.17 crypto/tls to take effect, which they don't as long as we don't create an updated qtls version.
cc @mvdan
The error message will look like this:
❯ go1.17 test
# github.com/lucas-clemente/quic-go/
internal/qtls/go117.go:3:1: expected 'package', found "quic-go doesn't build on Go 1.17 yet."

That's a clever way to give a useful compiler error

Thanks. Actually, I was hoping that there is an even more direct way to print that error (without the expected 'package', found ...).