Does not work with Logitech Litra Beam LX

I see that the code does not have support for the Litra Beam LX. I tried connecting to it by adding it to the driver file but the HID values are incorrect so all readings from it are wrong. I do not have any experience with brute forcing HID codes. Could someone who has experience with bruteforcing HID values help me out?

Thank you! I tested it and it works perfect! I'm not sure how the changes affect support for the other litra products and am unable to test it. Hopefully the changes can be merged with no issues.
Your wrapper is definitely better than any of the others I've seen so far :)

@jbsparrow That's great news! I'll take a look at this over the next few days and will add Beam LX support to this package for the basic features - would you be willing to test it once I have some working code? 😊

I would be glad to test it!

Hi @timrogers and @jbsparrow ! Thank you for creating this extremely helpful wrapper and I'm glad to see that my (quite dirty 😅) fork is helping, I created it in a rush for a Hackathon 🙈 Unfortunately I think that my changes might break compatibility with the standard Litra Beam/Glow as I had to change a couple of HID bytes in almost every function to make it work on the Beam LX. Let me know if that's the case and if I can be of any help! Best

Hi @timrogers and @jbsparrow ! Thank you for creating this extremely helpful wrapper and I'm glad to see that my (quite dirty 😅) fork is helping, I created it in a rush for a Hackathon 🙈 Unfortunately I think that my changes might break compatibility with the standard Litra Beam/Glow as I had to change a couple of HID bytes in almost every function to make it work on the Beam LX. Let me know if that's the case and if I can be of any help! Best

No worries at all - your fork had the all-important research on the HID bytes, and I've written this PR to send the right bytes based on the device ☺ Thank you for figuring out the hard bits!


Set imap_folder_list_limit from admin interface

The imap_folder_list_limit is not settable from the web interface.
A friend has 245 folders and the default limit is to 200.
Also, there is no message telling users they have too much folders and all cannot be displayed.
But first, making this parameter available to modification from web interface would be a nice thing.
Thanks

Hi,
Thanks for this, but how can I test this change by cloning from master?
I guess I have to "build" something, like for minifying javascript components, but how do you accomplish that?
Thanks

I guess I have to "build" something.

Yes.
cd /var/www/rainloop/
npm install gulp -g
npm install
gulp


output plddt?

Hi. Does omegafold outputs plddt for confidence? How can I have access to it?

Hi!
Yes it does! Just as in Readme.md, the model outputs its confidence in the place where b_factors would normally be in .pdb files!


ENH: tutorials / special doc needed

We should have a few extended docs/ tutorials, maybe in the FAQ section on at least the following topics:

epochs selection and event handling (see #1963)
artefact removal
group statistics (make explicit 2 (spatial /  no spatial prior) X 2 (F/T-test) API, clarify TFCE (it's not another test, but an enhancement method)), clarify that despite t-test inputs, spatio-temporal permutation clustering is not parametric and alos it does not give a multiple comparison corrected t-map, which means it's not just a thresholding to a parametric stat. Also add recent insights on decoding stats. Discuss repeated measure designs and options (hierarchial subtraction with t-test, rANOVA, etc.)
...

cc @wmvanvliet @kingjr @mainakjas @jona-sassenhagen @teonlamont

Rolling into #1495


Feature/syntax checker

Preparing to a new release thats include

Syntax check (big thanks to @pocket7878 PR #3 )
Upgrade dependencies

@pocket7878 your review would be highly appreciated :)

Hi @dsvictor94 and @pocket7878, I started using Promela for an academic study and I was curious if this PR is going to be merged?

Sorry for the probably too long delay @claudiopedrom, but I am merging now and try to publish a new version

Thanks @dsvictor94 , I really appreciate your work! The extension was very useful for me 👏


Travis doesn't run charrua-core tests.

I've just noticed that travis is not running charrua-core tests, PACKAGE=charrua-core never shows up in travis.
Take a look at this:
https://travis-ci.org/mirage/charrua-core/builds/260962785

Fixed in #74, sorry for the delay in reviewing!


revert PR #1569

It caused build break and didn't work with OOP JIT

@Krovatkin FYI. It passed CI few months ago... but I guess it breaks Linux now.

@MikeHolman yes, it's fairly old 👴  I should've closed it since we are thinking to fold this item into WASM.SIMD feature work.

Ok. Feel free to reopen it or wait to fold it into simd wasm work.


⚠ Secret Website 3 has degraded performance

In baa2f69, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2801 ms

Resolved: Secret Website 3 performance has improved in b0f16be.


Supporting optional AAD-first auth + encrypting sessions and links

This change allows for a new configuration property, AUTHENTICATION_SCHEME, which defaults to 'github' but also permits a value of 'aad'. With AAD-first auth, instead of the user workflow being to first sign in with GitHub and then with Active Directory, instead they are sent through the AAD dance first, and then GitHub.
Going forward the URL for the app immediately authenticates, if it is not already, instead of showing a "homepage" or "landing page".
This change adds encryption support for GitHub tokens (both a user's public-scope and increased-scope version) and Active Directory tokens stored in the Passport Session (which we back with Redis). Also, encryption support for user links (source of truth), for GitHub tokens - this is the first time we are also storing user tokens inside our user links, to help with offering a GitHub-second authorization story
This PR also includes Azure KeyVault support. Secret values such as key encryption keys for key wrapping, authenticating with Redis, storage, or other services can therefore flow in easily, with better compliance. A new keyvault: scheme is introduced for settings where the KeyVault URI needs to flow all the way into logic. Key vault custom tags (user-defined) can also be select for configuration values, allowing for even simplifier configuration.
Business rule introduced when using AAD-first:

This change requires that a site configured with 'aad' authentication first (not the default, only an opt-in) will only allow a single GitHub account per corporate identity. Note that this business rule is just our call; it would be relatively easy to offer a "GitHub user selector" choice in the interface and use that to set session values, but for now we are keeping it simple. Users who already have multiple GitHub identifies stored with us will be asked to consolidate upon trying to use the portal again.
After this change, the default logger implementation no longer shows user-identifiable usernames in the streaming log. A new configuration value, SITE_SHOW_USERS, can bring this functionality back if needed. The default changes here to better protect users.

Other changes worth noting:

Refactors Passport authentication to support hoisting authorizations into the primary authentication user's session; simplifies code
Adds an entity encryption implementation that uses AES 256 key wrapping with a set of key wrapping keys, per-entity, per-row 256-bit AES content encryption key that uses AES_CBC_256, and then per-column initialization vectors. Implementation is roundtrip-compatible with the official Azure storage team's implementation of table entity encryption for .NET and Java. Adds a new open source dependency, node-jose, which offers A256KW wrapping functionality.
Scrubbing is performed on "secret" configuration values using a double-back routine at initialization. This allows for including a scrubbed, safe configuration instance for debugging when needed in views without leakage concerns.
Errors that happen during app initialization now propagate, ignoring and canceling other routes along the way
Touched files get cleaner ES6 in many cases
Adds code linting with eslint
Moves to 2-space indentation per consensus

Hi @jeffwilcox, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;


[Feature]: generic Conn context

Description of new feature
Would be great if the Conn was a generic interface.
Like:
// ConnG is a generic interface of underlying connection.
type ConnG[Ctx any] interface {
	Reader
	Writer
	Socket

	// ================================== Non-concurrency-safe API's ==================================

	// Context returns a user-defined context.
	Context() (ctx Ctx)

	// SetContext sets a user-defined context.
	SetContext(ctx Ctx)
	...
}

// Conn is an interface that provide a most general Conn interface with an `interface{}` context.
type Conn ConnG[any]

This'll allow users avoid many conversions (and many small allocs) when context used.
This is a breaking change, but in soft manner. Since you can maintain the ConnG and the Conn separately and the Conn will be almost identical to current Conn that use interface{} to a context.
You can get incompatibility here, but mostly in advanced use-cases when some tool rely on the Conn internal representation.
Also, the change will require the golang version bump to 1.18. You can also maintain compatibility if you leave the original Conn implementation and guard it via build tags.
Scenarios for new feature

For those who do not use context — nothing changes. They'll still use Conn and nothing should changes for them.
For those who use an interface{} as Context. Same as above.
For those who want use own context - nothing changes except elimination all of the conversions from an interface{} to the own type.

Breaking changes or not?
Yes
Code snippets (optional)
No response
Alternatives for new feature
None.
Additional context (optional)
Good example of same change can be found here.

这个应该不太好做。需要兼容go原生的context

// 	import "context"
//
// 	// User is the type of value stored in the Contexts.
// 	type User struct {...}
//
// 	// key is an unexported type for keys defined in this package.
// 	// This prevents collisions with keys defined in other packages.
// 	type key int
//
// 	// userKey is the key for user.User values in Contexts. It is
// 	// unexported; clients use user.NewContext and user.FromContext
// 	// instead of using this key directly.
// 	var userKey key
//
// 	// NewContext returns a new Context that carries value u.
// 	func NewContext(ctx context.Context, u *User) context.Context {
// 		return context.WithValue(ctx, userKey, u)
// 	}
//
// 	// FromContext returns the User value stored in ctx, if any.
// 	func FromContext(ctx context.Context) (*User, bool) {
// 		u, ok := ctx.Value(userKey).(*User)
// 		return u, ok
// 	}
估计只能用go 目前推荐的方式


Fix who is method.

Closes https://github.com/apache/incubator-openwhisk-catalog/issues/233.

@jasonpet @houshengbo can you review?


Html Meta Data

As the library stands, users cannot add their custom meta information to the <head> of their web apps. New methods for adding header content are needed. Currently the library only supports adding and setting style sheets and loading js from the header.

Meta tag can now be added to the document header


Don't attempt to set status after sending JSON body successfully

Resolves https://github.com/istio/istio/issues/14374

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: esnible
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: diemtvu
If they are not already assigned, you can assign the PR to them by writing /assign @diemtvu in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

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

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

Needs approval from an approver in each of these files:

pilot/OWNERS [howardjohn]

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


Kitematic goes crazy when I just suspend and resume windows

Hey Guys,
Wanna check if anybody has the same issue as me, on just suspending windows and resuming it. Not sure if kitematic or virtual box problem.

It's unfortunately a Vbox issue, where the networking bit isn't always brought back up properly. Shutting down kitematic+VM and restarting them does the job.


Condition for CodeQL Analysis Task DevOps YAML Pipeline

Hello,
I have managed to integrate GHAS for Azure DevOps into all my yaml pipelines.
I wanted to find out if there is a way to halt the pipeline or skip a task in the same pipeline if the Advanced Security Perform CodeQL analysis task does/does not find any vulnerabilities?
When the Advanced Security Perform CodeQL analysis task detects any vulnerabilities we see the below in the task pipeline run -
Analyzing CodeQL execution results.
The Analyze task succeeded without any issues.
When the Advanced Security Perform CodeQL analysis task detects no vulnerabilities we see the below in the task pipeline run -
Analyzing CodeQL execution results.
The CodeQL analysis has successfully completed, however no violations were detected for the following language(s): 'csharp'.
If you think there should be violations, please refer to this document for troubleshooting https://aka.ms/codeQL-no-result
I thought about using the variable below, which is set by default in the Advanced Security Perform CodeQL analysis task, as a condition in the same yaml pipeline on whether or not a subsequent task(s) should run but this variable is always set to true so I cannot use it and the SARIF file is still generated even if there are no vulnerabilities, which is fine.
##[debug]Processed: ##vso[task.setvariable variable=advancedsecurity.codeql.results.published;isOutput=false;issecret=false;]true
Is there a way to check/read the SARIF file, if it does have any sort of information in there regarding the detection of any vulnerabilities or something along those lines, in the Advanced Security Perform CodeQL analysis task? This is to determine if the task has or has not detected any vulnerabilities. By this I mean if I can check in a subsequent task in my yaml pipeline the output of the Advanced Security Perform CodeQL analysis task if it has or has not detected vulnerabilities and then I can set a custom variable or use some builtin variable relating to the task for a condition or something which can be used to run a subsequent task(s) or to log an error message etc.?
To try and explain better of what I am trying to achieve, I am currently doing something similar with the Advanced Security Dependency Scanning task whereby I am reading the log file from the task which actually states if any vulnerabilities have been found. For example, the log file contains the below if vulnerabilities have been found,
[WRN] Dependency Scanning has detected
Depending on whether or not the Advanced Security Dependency Scanning task has detected any vulnerabilities, I can set a custom variable which I can use in subsequent task(s) in the same yaml pipeline, for example, forcing the pipeline to complete with issues if there are any dependency vulnerabilities detected.
If you can provide any ideas on how I can achieve what I am trying to do that will be greatly appreciated.
Apologies if I have not raised this is the correct place. If you can redirect me that would be great.
Thank you.

The gating sample is an alternative way to handle this. It calls the alert API after the SARIF has been parsed by the Advanced Security Service.  This can be an advantage because there may be alerts that have been previously dismissed as false positive that would be noise to block on.  The raw SARIF that is generated by code scanning won't be aware of the state of the alert, but the API will be able to handle this.

Hi,
Thank you for the suggestion. I will try this out and check if I can get it working for my use case.
Thank you.

Hi,
Please can you confirm what his does useDatabaseProvider=true?
In the gating.ps1 script, line 33.
$url = "https://advsec.dev.azure.com/{0}/{1}/_apis/AdvancedSecurity/Repositories/{2}/alerts?useDatabaseProvider=true" -f $orgName, $project, $repositoryId
Thank you.

useDatabaseProvider=true

This is legacy and should be the default going forward.  An artifact from the preview days of the API 💟.

Got it, thanks. I had excluded it in the URL and noticed the results returned are the same.
The script works great, I have tweaked it to suit our needs and currently testing.
I noticed there are pr-gating scripts, would that add annotations to Pull Requests if Advanced Scanning does detect any vulnerabilities?
Thank you.

Looks like I needed to use the continuationToken parameter in the API call. But still doesn't make sense for some repositories showing more or less alerts in the portal vs API.

I think I may have fixed this. I added an "unknown" severity type which seems to do nothing when running the script locally but when the script is run in AzDO it returns a number higher than what is actually found.


Conflict with the OptixRender

In the renderTwoBounce.py, I notice the cmd call the OptixRenderer assign the mode as 7.
        if opt.forceOutput:
            cmd1 = '%s -f %s -o %s -c %s -m 7 --forceOutput' % (renderProgram, xmlFile, output, camFile )
        else:
            cmd1 = '%s -f %s -o %s -c %s -m 7' % (renderProgram, xmlFile, output, camFile )

However, the OptixRenderer, it seems do not have mode 7 but only have mode 0 to 6
In createGeometry.cpp
           if(!shape.isLight ){
                if(mode == 0){
                             .....
                }
                else if(mode == 1){
                ...........
               }
               ........
                else if(mode == 6){
                   ........
                }
                else{
                    std::cout<<"Wrong: Unrecognizable mode!"<<std::endl;
                    exit(1);
                }
            }

It seems mode 7 can output all results but it not implemented in the OptixRenderer. Should I just use mode 6?

Hi @arkgao,
Thanks for your interest in our work. Could you try transparentShape branch?

There is only one branch('master') in this repository, do you mean the main repository of the paper TransparentShapeReconstruction?

No, I mean the OptixRenderer.

Got it! Thank you!


New project upcoming today - CSS Minifier with cool UI/UX

New project upcoming tonight.
Tech stack: HTML/ CSS/ JS

go ahead @vaibhavHere
by the way are you sure its js project ? if not then please create this issue and  make PR on  https://github.com/arpit456jain/Amazing-Css-Effects  don't wait for assigning


dubbo: fix unexpected exception for null but with attachments response type

Commit Message: dubbo: fix unexpected exception for null but with attachments response type
Additional Description:
When dubbo providers response null value but with attachments, the error body length check will result in an unexpected exception.
And this PR fix it.
**This bug is reported by the @zhnxin in the #19635. But @zhnxin is unresponsive, so I pick this up to complete this fix.
Thanks a lot to the @zhnxin. 🌷 **
Risk Level: Low.
Testing: Added.
Docs Changes: N/A.
Release Notes: N/A.
Platform Specific Features: N/A.

Hi, @lizan, please take a look at this when you have free time. Thanks. 🌹

@zyfjeff PTAL


Can't see favicon when using Microsoft Edge

I copy the example code in the README, it works well in Chrome and IE, but fail to show favicon in Edge

Searching for your issue on the web seems to indicate Edge does not show the favicon for sites loaded from localhost. Are you trying the example from localhost or from your remote server?

@dougwilson Thanks, this is exactly why Edge does not show the favicon


Using highlight in statusline causes window to not react to scrolling

Steps to reproduce

Install Lightline (https://github.com/itchyny/lightline.vim). I just put in under ~/.vim/pack/... using the standard Vim package installation method. (I'm using the latest commit, b02ef0d, in case other versions don't exhibit this behavior)
Launch Vim.
Make sure mouse is enabled by doing :set mouse=a.
Enter :put =range(1,100) to fill some text. (Or just open any file)
Enter :bot sp to open a new split at the bottom. Right now there should be two splits, with the active window at the bottom.
Position the mouse cursor on the top window (which is not active). Attempt to scroll using mouse wheel.

Expected behaviour
The window does not react to mouse wheel. However, if you click on it, or move the active window to it somehow, it will immediately be repainted with the correctly scrolled position. That's because the window was indeed scrolling, but didn't properly repaint itself.
Version of Vim
9.0.0233
Environment
OS: macOS 12.5.1
Tested on regular Vim on terminal and also in MacVim.
Logs and stack traces
No response

I wanted to find a more concise repro but was failing at it. The issue here is related to 65ed136844f (v8.0.1164). Basically, Lightline is calling some hi link commands within statusline itself, which causes redraw_all_later to be called which tries to update must_redraw and the window's w_redr_type. The logic introduced in v8.0.1164 tries to set it back, but is a little buggy and not properly restoring the state.
In particular, the bug here is that if you search for \<curwin\> =  within the function (build_stl_str_hl), you will find that inside the handling of case STL_VIM_EXPR: // '{', it temporarily sets curwin to the current window before executing, and so if that window's w_redr_type gets change, the restoration code at the bottom would not be sufficient in properly restoring the state.

The patch that seems to fix this issue is as follows, but honestly this feels a little fragile due to how much build_stl_str_hl seems to try to prevent the recursive draw from happening but that could really happen from anywhere.
diff --git a/src/buffer.c b/src/buffer.c
index 314ab64b2a..8c17584560 100644
--- a/src/buffer.c
+++ b/src/buffer.c
@@ -4240,6 +4240,7 @@ build_stl_str_hl(
     stl_hlrec_T *sp;
     int		save_must_redraw = must_redraw;
     int		save_redr_type = curwin->w_redr_type;
+    int		local_save_redr_type;
     int		save_KeyTyped = KeyTyped;

     if (stl_items == NULL)
@@ -4653,8 +4654,21 @@ build_stl_str_hl(
 	    if (curwin != save_curwin)
 		VIsual_active = FALSE;

+	    local_save_redr_type = curwin->w_redr_type;
+
 	    str = eval_to_string_safe(p, use_sandbox, FALSE);

+	    // When inside update_screen we do not want redrawing a statusline, ruler,
+	    // title, etc. to trigger another redraw, it may cause an endless loop.
+	    //
+	    // We already restore the cached must_redraw / curwin->w_redr_type
+	    // at the end of the function, but here, since we change curwin
+	    // temporarily, we have to restore it locally.
+	    if (updating_screen)
+	    {
+		curwin->w_redr_type = local_save_redr_type;
+	    }
+
 	    curwin = save_curwin;
 	    curbuf = save_curbuf;
 	    VIsual_active = save_VIsual_active;

I could submit a pull request for this, but I'm still trying to figure out how to generate a small enough repro case, and/or a test case that could regression test this (since I don't really have a smaller repro than just "install LightLine and let it do its highlight linking thing")

The patch that seems to fix this issue is as follows, but honestly
this feels a little fragile due to how much build_stl_str_hl seems
to try to prevent the recursive draw from happening but that could
really happen from anywhere.
diff --git a/src/buffer.c b/src/buffer.c
index 314ab64b2a..8c17584560 100644
--- a/src/buffer.c
+++ b/src/buffer.c
@@ -4240,6 +4240,7 @@ build_stl_str_hl(
     stl_hlrec_T *sp;
     int		save_must_redraw = must_redraw;
     int		save_redr_type = curwin->w_redr_type;
+    int		local_save_redr_type;
     int		save_KeyTyped = KeyTyped;

     if (stl_items == NULL)
@@ -4653,8 +4654,21 @@ build_stl_str_hl(
 	    if (curwin != save_curwin)
 		VIsual_active = FALSE;

+	    local_save_redr_type = curwin->w_redr_type;
+
 	    str = eval_to_string_safe(p, use_sandbox, FALSE);

+	    // When inside update_screen we do not want redrawing a statusline, ruler,
+	    // title, etc. to trigger another redraw, it may cause an endless loop.
+	    //
+	    // We already restore the cached must_redraw / curwin->w_redr_type
+	    // at the end of the function, but here, since we change curwin
+	    // temporarily, we have to restore it locally.
+	    if (updating_screen)
+	    {
+		curwin->w_redr_type = local_save_redr_type;
+	    }
+
 	    curwin = save_curwin;
 	    curbuf = save_curbuf;
 	    VIsual_active = save_VIsual_active;

I could submit a pull request for this, but I'm still trying to figure
out how to generate a small enough repro case, and/or a test case that
could regression test this (since I don't really have a smaller repro
than just "install LightLine and let it do its highlight linking
thing")

Well, it's indeed strange that when dealing with the status line for
"wp" the redraw type of "curwin" is saved and restored.
I wonder what happens if the redraw type of "wp" is saved and restored
only?  Or both?  There is no test that covers this.
--
TALL KNIGHT: When you have found the shrubbery, then you must cut down the
mightiest tree in the forest ... with a herring.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

I think the core issue here is that must_redraw is saved and restored at the bottom of the function. must_redraw is kind of the maximum of all the windows' w_redr_type, so if you save/restore must_redraw you technically need to save all the windows w_redr_type as well to maintain a consistent state. The current code is only saving curwin->w_redr_type for convenience, but as we can see here other windows' w_redr_type can be modified as well. I think just saving wp's w_redr_type may not be enough actually, if the statusline evaluation is doing even more funky stuff and switches window but that seems like a bad practice to begin with.

Ok, your solution does sound better than just patchwork restoring the different w_redr_type (albeit more involved). And I agree that a sort of broken statusline redraw is better compared to a broken inconsistent internal state (and statusline plugin authors can always work around the recursive redraw limit).
I tested the latest commit and it fixes the bug that I reported (I can scroll and see live update on the top window now), so feel free to close this issue as the bug is resolved as far as I am concerned.


Spatial Awareness Demo throws errors when playing from editor

Does this affect the legacy HoloToolkit (master) or the Mixed Reality Toolkit (mrtk_release)?
Mixed Reality Toolkit
Describe the bug
Lots o'errors when playing Spatial Awareness demo in editor.

To Reproduce
Steps to reproduce the behavior:

Open Spatial Awareness Demo in the editor
Enter play mode
See errors

Expected behavior
No errors, or at minimum a "fake mesh" to use or a warning about needing to run on device.
Mixed Reality Toolkit Release Version
Stabilization

Hmm, after restarting the editor, I wasn't able to get this again.
Sorry about the false alarm.


Cache dialyzer artifacts

See https://github.com/CrowdHailer/raxx/pull/151 for context

So this build took 13 minutes. Are we expecting the next one will be a bunch faster

Yes. The way it works is caches are built per-branch (with master as fallback) and the cache configuration needs to be present in order for the cached files to be uploaded.
So in this case, if there was another commit on this branch, it should be faster. Also, once this gets merged, it's going to be a slow build on master, but all subsequent ones are going to be quick.


Change mirrors and make it easier for end users to switch

Closes #81
General usage for allowing the end user to specify a mirror to use:
$ python3 -m gutenberg.acquire.text 2701 moby-raw.txt
INFO:rdflib:RDFLib Version: 4.2.2
http://aleph.gutenberg.org/2/7/0/2701/2701.txt

$ python3 -m gutenberg.acquire.text --mirror http://mirrors.xmission.com/gutenberg/ 2701 moby-raw.txt
INFO:rdflib:RDFLib Version: 4.2.2
http://mirrors.xmission.com/gutenberg/2/7/0/2701/2701.txt

$ GUTENBERG_MIRROR=http://mirrors.xmission.com/gutenberg/ python3 -m gutenberg.acquire.text 2701 moby-raw.txt
INFO:rdflib:RDFLib Version: 4.2.2
http://mirrors.xmission.com/gutenberg/2/7/0/2701/2701.txt

$ GUTENBERG_MIRROR=http://mirrors.xmission.com/gutenberg/ python3 -m gutenberg.acquire.text --mirror http://eremita.di.uminho.pt/gutenberg/ 2701 moby-raw.txt
INFO:rdflib:RDFLib Version: 4.2.2
http://eremita.di.uminho.pt/gutenberg/2/7/0/2701/2701.txt

(the printed URI is just for the example, won't happen in real usage)
I've also added an additional exception in using an invalid mirror (ie, URI doesn't exist, forbidden, etc):
python3 -m gutenberg.acquire.text --mirror http://www.gutenberg.lib.md.us 2701 moby-raw.txtINFO:rdflib:RDFLib Version: 4.2.2
usage: text.py [-h] [--mirror MIRROR] etextno outfile
text.py: error: Could not reach Gutenberg mirror 'http://www.gutenberg.lib.md.us'. Try setting a different mirror (https://www.gutenberg.org/MIRRORS.ALL) for --mirror flag or GUTENBERG_MIRROR environment variable.

And if you use a good mirror, but the etext does not exist (this will return an empty message in current version):
python3 -m gutenberg.acquire.text<PHONE_NUMBER>11 moby-raw.txt                                                                                [10:14:10]
INFO:rdflib:RDFLib Version: 4.2.2
usage: text.py [-h] [--mirror MIRROR] etextno outfile
text.py: error: Failed to find<PHONE_NUMBER>11 on http://aleph.gutenberg.org.

Coverage decreased (-0.6%) to 95.852% when pulling ea6369a82130eadce79082a8c6e15517978b5fa0 on issue_81 into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Not sure the best way to test this, open to suggestions.

You could try fetching something by literally using example.com as a mirror.

That would test the case where the mirror exists, but text itself couldn't found, but I couldn't seem to get a good test of "the mirror doesn't exist, it fails", but I guess that might just be something screwy with my network settings affecting python.

Perhaps something like thismirrordoesntexist.com?

Weirdly:
>>> import requests
>>> response = requests.head("http://thismirrordoesntexist.com")
>>> response.ok
True
>>> response.status_code
301

I'm going to have to figure out what's going on with my network stack, so I cannot write tests at this time.

Coverage increased (+0.3%) to 96.767% when pulling 8304af2f526fa5ae1b65c9fba38e5c14993ce795 on issue_81 into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage decreased (-0.03%) to 96.391% when pulling a5ff33b60223435d2867ae1c010576c5addd7b81 on issue_81 into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage increased (+0.3%) to 96.767% when pulling fce957aeaa6f02592bb840499f0f6d0fd1ca33f0 on issue_81 into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage increased (+0.3%) to 96.767% when pulling fce957aeaa6f02592bb840499f0f6d0fd1ca33f0 on issue_81 into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Coverage increased (+0.3%) to 96.767% when pulling fce957aeaa6f02592bb840499f0f6d0fd1ca33f0 on issue_81 into 4fd78daf0c0872bafe45002b3db0a009ac5084f7 on master.

Changes Unknown when pulling 8aa9a261e6168a66a21c7498797a5eeaef9e9bfa on issue_81 into ** on master**.

Changes Unknown when pulling 8aa9a261e6168a66a21c7498797a5eeaef9e9bfa on issue_81 into ** on master**.

Changes Unknown when pulling 8aa9a261e6168a66a21c7498797a5eeaef9e9bfa on issue_81 into ** on master**.

Changes Unknown when pulling 8aa9a261e6168a66a21c7498797a5eeaef9e9bfa on issue_81 into ** on master**.

Changes Unknown when pulling 8aa9a261e6168a66a21c7498797a5eeaef9e9bfa on issue_81 into ** on master**.

Changes Unknown when pulling 8aa9a261e6168a66a21c7498797a5eeaef9e9bfa on issue_81 into ** on master**.

I think this @coveralls comment spam could be turned off, especially when it's so useless ("changes unknown"?) but keep the status API:

https://coveralls.io/github/c-w/Gutenberg/settings

@hugovk Sounds great, please do turn off the spam :)

@c-w I don't have the rights for this repo, please can you do it?

@hugovk Should be done now.


tunneling?

any good way for tunneling domestic relays to foreign servers other than cdn? specifically working on XrayR ws protocol.

No need for additional tunnel just use dstnat in iptables


Gradle Tooling API 7.3.3 failed to resolve due to variant selection

Trying to upgrade from org.gradle:gradle-tooling-api:6.7.1 to org.gradle:gradle-tooling-api:7.3.3 fails with an error

Cannot choose between the following variants of org.gradle:gradle-tooling-api:7.3.3

Expected Behavior

Upgrade should be successful
Current Behavior

Upgrade fails with the following error:

What went wrong:
Execution failed for task ':lib:resolveAndLockAll'.
Could not resolve all files for configuration ':lib:default'.
Could not resolve org.gradle:gradle-tooling-api:7.3.3.
Required by:
project :lib
Cannot choose between the following variants of org.gradle:gradle-tooling-api:7.3.3:
- javadocElements
- shadedRuntimeElements
- sourcesElements
All of them match the consumer attributes:
- Variant 'javadocElements' capability org.gradle:gradle-tooling-api:7.3.3:
- Unmatched attributes:
- Provides org.gradle.category 'documentation' but the consumer didn't ask for it
- Provides org.gradle.dependency.bundling 'external' but the consumer didn't ask for it
- Provides org.gradle.docstype 'javadoc' but the consumer didn't ask for it
- Provides org.gradle.status 'release' but the consumer didn't ask for it
- Provides org.gradle.usage 'java-runtime' but the consumer didn't ask for it
- Variant 'shadedRuntimeElements' capability org.gradle:gradle-tooling-api:7.3.3:
- Unmatched attributes:
- Provides org.gradle.category 'library' but the consumer didn't ask for it
- Provides org.gradle.dependency.bundling 'shadowed' but the consumer didn't ask for it
- Provides org.gradle.jvm.version '6' but the consumer didn't ask for it
- Provides org.gradle.libraryelements 'jar' but the consumer didn't ask for it
- Provides org.gradle.status 'release' but the consumer didn't ask for it
- Provides org.gradle.usage 'java-runtime' but the consumer didn't ask for it
- Variant 'sourcesElements' capability org.gradle:gradle-tooling-api:7.3.3:
- Unmatched attributes:
- Provides org.gradle.category 'documentation' but the consumer didn't ask for it
- Provides org.gradle.dependency.bundling 'shadowed' but the consumer didn't ask for it
- Provides org.gradle.docstype 'sources' but the consumer didn't ask for it
- Provides org.gradle.status 'release' but the consumer didn't ask for it
- Provides org.gradle.usage 'java-runtime' but the consumer didn't ask for it

Context

We're using gradle-tooling-api in our organization for various Gradle related tasks.

Your Environment
MacOs. Project is a Java library with Gradle 6.7.1. Also tried with Gradle 7.4.2.

Sorry that you're having trouble with Gradle!
Your issue lacks information about how to reproduce the problem you're having. A reproducer project can really help us track down and fix your problem quicker.  We may also be able to suggest workarounds or ways to avoid the problem if we can reproduce it.
This issue will be closed after 7 days, unless you can provide more information.

The problem is that I can't upload more because this is confidential and I am unable to reproduce it.
Is there any reason why would it work with 6.7.1 but not with 7.3.3 or any other 7.x with the errors I mentioned earlier?

I had a peek at the module files:
diff --git a/gradle-tooling-api-6.7.1.module b/gradle-tooling-api-7.3.3.module
index fe08934..162c696 100644
--- a/gradle-tooling-api-6.7.1.module
+++ b/gradle-tooling-api-7.3.3.module
@@ -3,15 +3,14 @@
   "component": {
     "group": "org.gradle",
     "module": "gradle-tooling-api",
-    "version": "6.7.1",
+    "version": "7.3.3",
     "attributes": {
       "org.gradle.status": "release"
     }
   },
   "createdBy": {
     "gradle": {
-      "version": "6.7",
-      "buildId": "pqevr7whdrbktcxw37jxqjuix4"
+      "version": "7.3.2"
     }
   },
   "variants": [
@@ -25,13 +24,33 @@
       },
       "files": [
         {
-          "name": "gradle-tooling-api-6.7.1-sources.jar",
-          "url": "gradle-tooling-api-6.7.1-sources.jar",
-          "size": 4559417,
-          "sha512": "f586302b13b46013ec194a0a969f098c66dcd2a92becccc5804b7657cd4077275fea38845cf2a74cb2f6f92368aef7550e9a1d59a71ad18ab6529a4b0861d714",
-          "sha256": "3ee4d2b465e0ce8130a47e2cbd01de25b9f0c7573f8f178d5bf701bb0dee1727",
-          "sha1": "6bb367bd2250232fed43b51d567e30c55a242c6d",
-          "md5": "ba86b7a5b2fffbcbf5f79e8c451ec9e9"
+          "name": "gradle-tooling-api-7.3.3-sources.jar",
+          "url": "gradle-tooling-api-7.3.3-sources.jar",
+          "size": 4925565,
+          "sha512": "7f538dc6bab341c364669d4da2ae39149bb00126d66f6156462c588e9026611e8159d7646354c0b87461f00c55655474622d16eb818b7635ee4c5f98ded2c5b2",
+          "sha256": "20d5318b87252470dd052bf2ab386c04b1434317e0e350fb7005a20598e77656",
+          "sha1": "f8a18ee06e9e59b118a38abb0234031d569b9335",
+          "md5": "a3c9bb61c9501ccf3c2f22286e4db700"
+        }
+      ]
+    },
+    {
+      "name": "javadocElements",
+      "attributes": {
+        "org.gradle.category": "documentation",
+        "org.gradle.dependency.bundling": "external",
+        "org.gradle.docstype": "javadoc",
+        "org.gradle.usage": "java-runtime"
+      },
+      "files": [
+        {
+          "name": "gradle-tooling-api-7.3.3-javadoc.jar",
+          "url": "gradle-tooling-api-7.3.3-javadoc.jar",
+          "size": 1830324,
+          "sha512": "dda581a7f64c28cdc23a0b4e38169a97d955d1c03429df518ead4fcaccaad27f1cea0c0575ea5ccd83bf981b5c6f24e3cbc91a3aa9d54a115ca72f69c9ef9f39",
+          "sha256": "a7abdeddb6320d2dc8e6abc985139dc41058f8292fd265f46f8acc674f6bed68",
+          "sha1": "90a2209bc79c489302068b40958511288964b175",
+          "md5": "b770aa0075d65b3ee7b922c45b5bb378"
         }
       ]
     },
@@ -49,19 +68,19 @@
           "group": "org.slf4j",
           "module": "slf4j-api",
           "version": {
-            "requires": "1.7.28"
+            "requires": "1.7.30"
           }
         }
       ],
       "files": [
         {
-          "name": "gradle-tooling-api-6.7.1.jar",
-          "url": "gradle-tooling-api-6.7.1.jar",
-          "size": 2039090,
-          "sha512": "dc4389bd982720f0d4bd88d35889f586e0c6af056de892386bcb75964c5ae43622824eb5b38c3ea0013cec386a78d5730db29bcb2e6e05b2814b197a8e2d0c05",
-          "sha256": "57222e4264e83a81588b01db1e501d2d33e6cce59df7358a2e734ba6490bbef2",
-          "sha1": "5b67bea26af6a5fb5ff131381a0ff55f89d68cfc",
-          "md5": "ac491964f81d509bfd9280c22eaebcc1"
+          "name": "gradle-tooling-api-7.3.3.jar",
+          "url": "gradle-tooling-api-7.3.3.jar",
+          "size": 2418751,
+          "sha512": "514eac4cc1133ab1c569f24e7d414d547a80e03ef108beca4b6d71727873ad0bb8436c8ec77058acc8716f417136b6e62ffb61a0a223a2e32f5b3bfdd42bd062",
+          "sha256": "44bf7e8a2857d0f4929b79f91a045d81222565a8c6dea5e5ac1c1466d494e022",
+          "sha1": "03f1ed82080c9add4e0ef06d2da06cf309427336",
+          "md5": "55ea496184ac03cc2ca1ed61d3067878"
         }
       ]
     }

Here, the significant addition is the javadocElements capability, but I'm unsure (as there were two already: sourcesElements and shadedRuntimeElements) how an additional capability would cause an issue here.
I understand your confidentiality requirements, but I see it improbable that we will try to make this reproducer ourselves from such little information ourselves.
cc @gradle/bt-support, any ideas?

Reproduced on gradle 7.5.1:
build.gradle:
configurations {
    implementation.extendsFrom implementationLib
}

dependencies {
    implementationLib "org.gradle:gradle-tooling-api:7.4.2
}

jar {
    configurations.implementationLib.collect { it.isDirectory() ? it : zipTree(it) }
}

Side note: if I use implementationLib gradleApi() it works fine.

Sorry for the late reply.
We believe this issue is no longer relevant. Please file a new issue if necessary.

The original issue most probably is caused by a lack of variant attributes defined on configurations being resolved. Modern Gradle requires attribute definitions, so it shouldn't be a problem anymore.


program is taking too long to execute and not taking any input from user

Type: Bug
In my VsCode application, whenever I run any c++ program that takes input from user, it simply doesn't run and too long time. It displays the running status like
[Running] cd "e:\CODING VS\C++\Basics" && g++ test_1.cpp -o test_1 && "e:\CODING VS\C++\Basics"test_1
It keep displaying this and doesn't proceed until I manually stop the execution. The code is absolutely fine and has no error. Earlier it was working fine. After I uninstalled and reinstalled the VSCode and added my github account to it , this problem is occurring.
I am very coonfused now. Please provide a valid and good solution.
Thanks
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-11300H @ 3.10GHz (8 x 3110)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.79GB (4.29GB free)

Process Argv
--crash-reporter-id 9f7d4e53-7283-4c04-8bdc-672b8205bcf9

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

code-runner
for
0.12.2

cmake-tools
ms-
1.17.17

cpptools
ms-
1.20.5

cpptools-extension-pack
ms-
1.3.0

java
red
1.30.0

cmake
twx
0.0.17

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.3.1

vscode-java-debug
vsc
0.57.0

vscode-java-dependency
vsc
0.23.6

vscode-java-pack
vsc
0.26.0

vscode-java-test
vsc
0.41.1

vscode-maven
vsc
0.44.0

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
chatpanelt:31048053
dsvsc021:30996838
g316j359:31013175
pythoncenvptcf:31049071
fchga941:31046352
pythonprc:31047982
dwnewjupyter:31046869
26j00206:31048877

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I have now updated the VSCode to latest version, but the problem still continues. What to do?

You can file an issue with more detail on the C++ debug extension repo


bug: prerelease hook uses patch version for minor/major releases

The prerelease hook is not receiving any info what kind of release it is processing.

solved in https://github.com/davidsneighbour/dotfiles/releases/tag/v2024.2.0 by making commit-and-tag-version authority to version numbers.


Use in a recyclerview item

Hi, this is a very cool work and I love it.
Is it safe performance-wise to use in a recyclerview item?
Thanks!

Hey @adigunhammedolalekan !
Generally speaking: yes, it is safe. But there is one point that should be considered:

use textView#setSpannableFactory on a TextView that is used in adapter

private static final NoCopySpannableFactory FACTORY = new NoCopySpannableFactory();

@NonNull
@Override
public Holder onCreateViewHolder(@NonNull ViewGroup parent, int viewType) {

    final Holder holder = new Holder(inflater.inflate(
            R.layout.adapter_markdown,
            parent,
            false));

    // set SpannableFactory when your view is inflated
    // this will reduce the amount of copying that TextView executes by default
    holder.textView.setSpannableFactory(FACTORY);

    return holder;
}

private static class NoCopySpannableFactory extends Spannable.Factory {
    @Override
    public Spannable newSpannable(CharSequence source) {
        return source instanceof Spannable
                ? (Spannable) source
                : new SpannableString(source);
    }
}

Other than that follow the regular steps when working with a RecyclerView and TextView:

cache as much as possible
for example, you can parse and create markdown CharSequence before sending to an adapter (by calling Markwon.markdown(configuration, markdown).
if you evaluating markdown lazily (parsing when the first time item is requested), do not forget to cache SpannableConfiguration and Parser (when not specified explicitly these 2 classes will be created implicitly anyway) and re-use them between calls

if you are still not happy with performance you can try relatively new thing called prefetch text (quick search will get you some results)

Great! Very well explained, Thanks


BaseData Implementation Issue?

After having an issue with a LiveTrade being placed, I am wondering if there is possibly an issue with the BaseData Implementation section. I am glad to share more information if needed

There are no known issues with BaseData in live trading.


Ensure launcher icon/shortcuts work after upgrade to 1.5

Since FileManagerActivity has moved, it is possible that launcher shortcuts are broken.
Check and fix if necessary.

@veniosg this seems to be working fine, although I suggest adding an <activity-alias> to avoid cases like these in the future!

To confirm, did you install 1.4.6, created a shortcut to a file and dragged
the launcher icon on the home screen, updated to latest master and both
shortcuts still worked?
On Tue, 12 Dec 2017, 8:54 am Pavlos-Petros Tournaris, <
<EMAIL_ADDRESS>wrote:

@veniosg https://github.com/veniosg this seems to be working fine,
although I suggest adding an  to avoid cases like these
in the future!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/veniosg/Dir/issues/72#issuecomment-350985914, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABmcZPKS6-6_HR8X6oIs7Rn-y0dYNpuiks5s_j8-gaJpZM4QemI2
.

Certainly not  😂  Will do tomorrow now that I know the flow :P

Sorry for the unclear description! 😁
On Tue, 12 Dec 2017, 3:37 pm Pavlos-Petros Tournaris, <
<EMAIL_ADDRESS>wrote:

Certainly not 😂 Will do tomorrow now that I know the flow :P
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/veniosg/Dir/issues/72#issuecomment-351088504, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABmcZIb1cCpggyCchLYLbSUd27eV2ufJks5s_p3RgaJpZM4QemI2
.


Summaries updates - to 'strongly recommended' and with a best practice

Related Issue(s): #820 #965
Proposed Changes:

Made summaries to be 'strongly recommended' and explained them a bit more
added a best practices section on summaries.

PR Checklist:

[x] This PR is made against the dev branch (all proposed changes except releases should be against dev, not master).
[x] This PR has no breaking changes.
[x] I have added my changes to the CHANGELOG.
[x] This PR affects the STAC API spec, and I have opened issue https://github.com/radiantearth/stac-api-spec/issues/101 to track the change.

Wordsmith edits incorporated, thanks!


why the dacinvi table name have no prefix!

the dacinvi table name have no prefix!
that make the table name very confused when multi system use the same db!
every system can has a table named dashboard,user...

It doesn't sound like Davinci's problem.


Improve saveload docs and add example

r? @omni-viral

@omni-viral Thanks for the review!
bors r+


Controlled value

Hi. Is it possible to change the slider value programmatically? Or do you plan to implement the value prop as controlled value? Thanks

I don't understand the question. If you change the value prop, it will change the slider representation, doesn't it? If you have an issue please provide a snack or a codesandbox to demonstrate the issue.

https://snack.expo.dev/@jb5/slider Here is a simple snack. Clicking the buttons changes the value, but the slider doesn`t move.

Fixed in V. 5.6.2
Tell me if it's ok for you.
Thanks a lot for your feedback.

Works great! Thank you very much for superfast update!

You're welcome. I don't know how I missed that in the last release.


add wso2 is key manager client connector implementation

Purpose

To connect wso2 IS as an external key manager for APIM

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Extend the functionality of AMDefaultKeyManagerImpl and provide WSO2 IS related configuration elements.

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


feat: support ollama batch processing embeddings

feat: support batch embedding with ollama
Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for validating the changes?
[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description
Add support for batch embedding with ollama api

[Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added
Support for batch embedding in a single ollama request
Removed
RAG_EMBEDDING_OPENAI_BATCH_SIZE environment variable

[List any removed features, files, or functionalities]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]
changed RAG_EMBEDDING_OPENAI_BATCH_SIZE to RAG_EMBEDDING_BATCH_SIZE

Screenshots or Videos

I would love to see this PR finalized and hopefully merged. Thanks @Peter-De-Ath for the effort!

Rebase wanted here!

LGTM, Thanks!


FIX BLOCK DESTROY TIME

HELLO!
 YOU FUCKEN RUINING BEST APP FOR MCPE MODDING AND LEAVING US WITH USELESS JSON BEHAVOUR PACKS WITH NO REAL POSSIBILITIES! JUST STOP IT!

CHIIIL WITH THE CAPS MAH FREIND!!1!
Anyways, Mojang is releasing updates faster than many servers and apps can catch up to. Give @zhuowei a break dude.

You can't expect all apps to be without bugs. Zhuowei doesn't get a chance to update as fast. Remember, he works alone unlike many other companies like Mojang. Please remove this issue as it has already been mentioned previously.


[INLONG-1889] add Inlong-sort-standalone module structure

Title Name: [INLONG-1889]Inlong-Sort-Standalone add Inlong-sort-standalone module structure.
for such sub-module:

sort-standalone-common: protocol POJO.
sort-standalone-dist: build product directory.
sort-standalone-source: different consumer sources and different sort sinks.

Fixes #1889
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

Codecov Report

Merging #1913 (a01dd5f) into master (1a905c6) will decrease coverage by 0.00%.
The diff coverage is n/a.

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

@@             Coverage Diff              @@
##             master    #1913      +/-   ##
============================================
- Coverage     12.26%   12.26%   -0.01%
- Complexity     1155     1157       +2
============================================
  Files           413      413
  Lines         35225    35225
  Branches       5542     5542
============================================
- Hits           4322     4320       -2
  Misses        30133    30133
- Partials        770      772       +2

Impacted Files
Coverage Δ

.../java/org/apache/flume/sink/tubemq/TubemqSink.java
51.42% <0.00%> (-4.00%)
:arrow_down:

.../producer/qltystats/DefaultBrokerRcvQltyStats.java
45.31% <0.00%> (+1.17%)
:arrow_up:

.../client/producer/qltystats/BrokerStatsItemSet.java
72.09% <0.00%> (+4.65%)
:arrow_up:

Continue to review full report at Codecov.

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


Include 'prebuilt/source-built/' packages in prebuilt report

These are different than the prebuilts acquired from the NuGet gallery, since they can in theory be taken from an N-1 build, and they are at least known to have been built during the online source-build build.
Reasons to reduce this set of packages:

Make the set of packages pulled in from N-1 smaller, to simplify.
Reduce the size of our online-built tarball artifact by not including some packages.

As of https://github.com/dotnet/source-build/pull/781#issuecomment-422945569 these prebuilts were ~330 MB.

Once these are reported, it'll be easier to tell what we have to do to get them from an N-1 build and force the repos to use them instead of the version checked in. (Right now prebuilt/source-built/ packages will be used if the version happens to match what the repo asks for, but we don't force version uptake like we do during PVP flow.)

[Triage] This has been implemented some time ago - https://github.com/dotnet/installer/blob/fb1775d03b6b1fda596c97aed2d63389e6b7c713/src/SourceBuild/tarball/content/tools-local/init-build.proj#L213


Figure out why AV selector no longer works in Firefox

Right now, it immediately crashes because there's a React render loop.
If you remove the setVideoId(defaultVideo) etc calls, that removes the initial infinite loop, but trying to change either the audio or video device causes it to rerender itself like 5 times and doesn't actually change the device.
This works in Chrome and Safari. No idea why Firefox is broken.
I feel like I'm dangerously close to burnout, so punting on this, even though it's bad :(

I think this is..."fixed"? As in I made a change to just not force a default selected device, it seems to have worked and I was able to chat using Firefox during the meetup, and I didn't notice any adverse effects.
I think I'd need somebody with multiple video & audio devices on their machine connected to try this in Firefox but it definitely works for a sample size of n=me.


Extend backend to directly serve JSKOS

Calling the application with additional query parameter format should directly serve JSKOS data in selected form.

format=jskos|json|jsonld for JSKOS
format=turtle|rdfxml|ntriples for RDF serialization

RDF serialization (that is other serialization formats than JSON-LD and NTriples) might also be done in jskos-server (https://github.com/gbv/jskos-server/issues/31) but jskos-web should better do the conversion in its  own backend.
Backend might also help to support #6 by serving a custom App.vue.

Will be implemented in https://github.com/gbv/jskos-proxy instead.


Setting light brightness not working

I have commissioned an ESP32-C3-DevKitM-1 using the latest Lighting App version available as of creating this issue on the Nabu Casa example site, and have setup Home Assistant 2022.9.6 with v0.3.0 of the server add-on and integration.
When setting the device's brightness, Home Assistant will show an error "Failed to call service light/turn_on. Command failed: unknown_error.".
Home Assistant logs:
Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/matter_experimental/light.py:66
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 8:15:00 PM (22 occurrences)
Last logged: 8:31:13 PM

[140326497279600] Command failed: unknown_error
[140325869626480] Command failed: unknown_error
[140325869882144] Command failed: unknown_error
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1738, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1775, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 676, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 931, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 713, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 535, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/config/custom_components/matter_experimental/light.py", line 66, in async_turn_on
    await self._device_type_instance.send_command(
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/model/device_type_instance.py", line 56, in send_command
    return await self.node.matter.client.driver.device_controller.send_command(
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/model/device_controller.py", line 138, in send_command
    return await self._async_send_command(
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/model/device_controller.py", line 228, in _async_send_command
    return await self.client.async_send_command(
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/client.py", line 122, in async_send_command
    return await future
matter_server.client.exceptions.FailedCommand: Command failed: unknown_error

Add-on logs:
2022-09-22 20:26:15 77f1785d-matter-server matter_server.server.server[121] INFO [139757767085456] Deserialized message: CommandMessage(messageId='1a6780f56ab647ac94a5ba164b5dce5e', command='device_controller.SendCommand', args={'nodeid': 4335, 'endpoint': 1, 'payload': LevelControl.Commands.MoveToLevelWithOnOff(level=66, transitionTime=None, optionsMask=0, optionsOverride=0)})
2022-09-22 20:26:15 77f1785d-matter-server chip.CTL[121] INFO Found an existing secure session to [1:00000000000010EF]!
2022-09-22 20:26:15 77f1785d-matter-server matter_server.server.server[121] ERROR [139757767085456] Error handling message: CommandMessage(messageId='1a6780f56ab647ac94a5ba164b5dce5e', command='device_controller.SendCommand', args={'nodeid': 4335, 'endpoint': 1, 'payload': LevelControl.Commands.MoveToLevelWithOnOff(level=66, transitionTime=None, optionsMask=0, optionsOverride=0)})
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/matter_server/server/active_connection.py", line 94, in _run_handler
    await handler(self, msg)
  File "/usr/local/lib/python3.9/dist-packages/matter_server/server/active_connection.py", line 207, in _handle_device_controller_SendCommand
    result = await self.server.stack.device_controller.SendCommand(**msg.args)
  File "/usr/local/lib/python3.9/dist-packages/chip/ChipDeviceCtrl.py", line 892, in SendCommand
    res = ClusterCommand.SendCommand(
  File "/usr/local/lib/python3.9/dist-packages/chip/clusters/Command.py", line 170, in SendCommand
    payloadTLV = payload.ToTLV()
  File "/usr/local/lib/python3.9/dist-packages/chip/clusters/ClusterObjects.py", line 192, in ToTLV
    return self.descriptor.DictToTLV(asdict(self))
  File "/usr/local/lib/python3.9/dist-packages/chip/clusters/ClusterObjects.py", line 186, in DictToTLV
    self.DictToTLVWithWriter('', None, data, tlvwriter)
  File "/usr/local/lib/python3.9/dist-packages/chip/clusters/ClusterObjects.py", line 180, in DictToTLVWithWriter
    field.PutFieldToTLV(field.Tag, val, writer,
  File "/usr/local/lib/python3.9/dist-packages/chip/clusters/ClusterObjects.py", line 79, in PutFieldToTLV
    raise ValueError(
ValueError: Field .transitionTime.transitionTime was not optional, but encountered None

Nothing appears in the device logs.

Interesting. The spec makes it sound like it's not required

…

Will now just always add a transition time


Errors encountered when evaluating results

Running inference.py appears to work as expected on the provided example, i.e.
python -m inference --protein_ligand_csv data/protein_ligand_example_csv.csv --out_dir results/user_predictions_small --inference_steps 20 --samples_per_complex 40 --batch_size 10 --actual_steps 18 --no_final_step_noise
but when trying to run evaluate_files.py on this sample output, errors arise with regards to reading the molecules and finding directories for the complexes (which are all located in data/PDBBind_processed after being downloaded from zenodo and unzipped). Would you happen to know why these errors are arising on these seemingly standard inputs and fixes to this issue? An excerpt from the error code is displayed below:
(diffdock) [abhi@gpu-1-dy-g4ad4xlarge-1 DiffDock]$ python evaluate_files.py --results_path results/user_predictions_small --file_to_exclude rank1.sdf --num_predictions 40
Reading paths and names.
  0%|                                                      | 0/363 [00:00<?, ?it/s]Can't kekulize mol.  Unkekulized atoms: 7 8 9 10 11
RDKit was unable to read the molecule.
Using the .sdf file failed. We found a .mol2 file instead and are trying to use that.
Did not find a directory for  6qqw . We are skipping that complex
Did not find a directory for  6d08 . We are skipping that complex
Did not find a directory for  6jap . We are skipping that complex
Did not find a directory for  6np2 . We are skipping that complex
Did not find a directory for  6uvp . We are skipping that complex
Did not find a directory for  6oxq . We are skipping that complex
Did not find a directory for  6jsn . We are skipping that complex
Did not find a directory for  6hzb . We are skipping that complex
Can't kekulize mol.  Unkekulized atoms: 7 8 9 10 11
RDKit was unable to read the molecule.
Using the .sdf file failed. We found a .mol2 file instead and are trying to use that.
Did not find a directory for  6qrc . We are skipping that complex
Did not find a directory for  6oio . We are skipping that complex
Did not find a directory for  6jag . We are skipping that complex
Can't kekulize mol.  Unkekulized atoms: 0 1 2 3 4 5 14 15 16
RDKit was unable to read the molecule.
Using the .sdf file failed. We found a .mol2 file instead and are trying to use that.
Did not find a directory for  6moa . We are skipping that complex
Did not find a directory for  6hld . We are skipping that complex
Did not find a directory for  6i9a . We are skipping that complex
Did not find a directory for  6e4c . We are skipping that complex
Did not find a directory for  6g24 . We are skipping that complex
Did not find a directory for  6jb4 . We are skipping that complex
Did not find a directory for  6s55 . We are skipping that complex
  5%|██▏                                         | 18/363 [00:00<00:01, 175.38it/s]Did not find a directory for  6seo . We are skipping that complex
Can't kekulize mol.  Unkekulized atoms: 12 13 14 15 16 17 18 20 21
RDKit was unable to read the molecule.
Using the .sdf file failed. We found a .mol2 file instead and are trying to use that.
Did not find a directory for  6dyz . We are skipping that complex
Did not find a directory for  5zk5 . We are skipping that complex
Did not find a directory for  6jid . We are skipping that complex
Did not find a directory for  5ze6 . We are skipping that complex
...

This may potentially be related to an earlier error en route to generating the language model embeddings:
(diffdock) [abhi@gpu-1-dy-g4ad4xlarge-7 diffdock]$ python datasets/pdbbind_lm_embedding_preparation.py
  0%|                                        | 10/19120 [00:00<22:45, 14.00it/s]encountered unknown AA:  PTR  in the complex  3kxz . Replacing it with a dash - .
  0%|                                        | 12/19120 [00:00<22:11, 14.35it/s]encountered unknown AA:  TPO  in the complex  1re8 . Replacing it with a dash -
...

I have encountered the same problem. Have you found a solution to this issue yet?

Running inference.py appears to work as expected on the provided example, i.e.
python -m inference --protein_ligand_csv data/protein_ligand_example_csv.csv --out_dir results/user_predictions_small --inference_steps 20 --samples_per_complex 40 --batch_size 10 --actual_steps 18 --no_final_step_noise
but when trying to run evaluate_files.py on this sample output, errors arise with regards to reading the molecules and finding directories for the complexes (which are all located in data/PDBBind_processed after being downloaded from zenodo and unzipped). Would you happen to know why these errors are arising on these seemingly standard inputs and fixes to this issue? An excerpt from the error code is displayed below:
(diffdock) [abhi@gpu-1-dy-g4ad4xlarge-1 DiffDock]$ python evaluate_files.py --results_path results/user_predictions_small --file_to_exclude rank1.sdf --num_predictions 40
Reading paths and names.
  0%|                                                      | 0/363 [00:00<?, ?it/s]Can't kekulize mol.  Unkekulized atoms: 7 8 9 10 11
RDKit was unable to read the molecule.
Using the .sdf file failed. We found a .mol2 file instead and are trying to use that.
Did not find a directory for  6qqw . We are skipping that complex
Did not find a directory for  6d08 . We are skipping that complex
Did not find a directory for  6jap . We are skipping that complex
Did not find a directory for  6np2 . We are skipping that complex
Did not find a directory for  6uvp . We are skipping that complex
Did not find a directory for  6oxq . We are skipping that complex
Did not find a directory for  6jsn . We are skipping that complex
Did not find a directory for  6hzb . We are skipping that complex
Can't kekulize mol.  Unkekulized atoms: 7 8 9 10 11
RDKit was unable to read the molecule.
Using the .sdf file failed. We found a .mol2 file instead and are trying to use that.
Did not find a directory for  6qrc . We are skipping that complex
Did not find a directory for  6oio . We are skipping that complex
Did not find a directory for  6jag . We are skipping that complex
Can't kekulize mol.  Unkekulized atoms: 0 1 2 3 4 5 14 15 16
RDKit was unable to read the molecule.
Using the .sdf file failed. We found a .mol2 file instead and are trying to use that.
Did not find a directory for  6moa . We are skipping that complex
Did not find a directory for  6hld . We are skipping that complex
Did not find a directory for  6i9a . We are skipping that complex
Did not find a directory for  6e4c . We are skipping that complex
Did not find a directory for  6g24 . We are skipping that complex
Did not find a directory for  6jb4 . We are skipping that complex
Did not find a directory for  6s55 . We are skipping that complex
  5%|██▏                                         | 18/363 [00:00<00:01, 175.38it/s]Did not find a directory for  6seo . We are skipping that complex
Can't kekulize mol.  Unkekulized atoms: 12 13 14 15 16 17 18 20 21
RDKit was unable to read the molecule.
Using the .sdf file failed. We found a .mol2 file instead and are trying to use that.
Did not find a directory for  6dyz . We are skipping that complex
Did not find a directory for  5zk5 . We are skipping that complex
Did not find a directory for  6jid . We are skipping that complex
Did not find a directory for  5ze6 . We are skipping that complex
...

This may potentially be related to an earlier error en route to generating the language model embeddings:
(diffdock) [abhi@gpu-1-dy-g4ad4xlarge-7 diffdock]$ python datasets/pdbbind_lm_embedding_preparation.py
  0%|                                        | 10/19120 [00:00<22:45, 14.00it/s]encountered unknown AA:  PTR  in the complex  3kxz . Replacing it with a dash - .
  0%|                                        | 12/19120 [00:00<22:11, 14.35it/s]encountered unknown AA:  TPO  in the complex  1re8 . Replacing it with a dash -
...

I have encountered the same problem. Have you found a solution to this issue yet?

Not yet — I have not explored solutions for this issue further at this time

I also have the same errors. Hopefully, this issue could be solved soon.

Same issue

Maybe check the directory of input, if the name of folder is the sequence like '6q36' but not numbers or other things.

This sounds to me like there were issues when running inference.
Then the results were not placed in “--out_dir results/user_predictions_small”
Then they are not in the list when listdir lists that directory and that message is thrown.
Would you mind checking if the issue was during inference and the results from inference were never placed in "results/user_predictions_small".
If that is the case, it would be useful to see the error during inference that causes the complex to be skipped.

This sounds to me like there were issues when running inference. Then the results were not placed in “--out_dir results/user_predictions_small” Then they are not in the list when listdir lists that directory and that message is thrown.
Would you mind checking if the issue was during inference and the results from inference were never placed in "results/user_predictions_small". If that is the case, it would be useful to see the error during inference that causes the complex to be skipped.

If I look in my results dir, I see that the inferred results are written to numbered folders ( there are directories called 0,1,... ) Instead, the evaluate_results script assumes that these folders have been named using a different scheme. See also the issue https://github.com/gcorso/DiffDock/issues/125


Retry markdown-link-check on failure

I don't usually do this, but it often gets status 0 on:
https://www.csail.mit.edu/person/charles-e-leiserson
Instead of manually re-running the workflow, which I've been doing,
perhaps the retrying can be automated (and specific to the
link-testing step).

wretry.action is not propagating the failure, so I don't know if that's a bug in the action or if I am using it incorrectly, but this cannot be merged.
(The failures at the end were when I took out retry.action to verify that my test change should produce failure.)


implement pagination for list of contributors

later the list of contributors might be bigger and it would be nice to have a pagination just to make nicer to read
The pagination was already implemented on camerapps whose code base is located here

It is now a matter of copying and pasting that functionality from the camerapps code base and integrate it here.

Which list are we talking about please? Could we please have the link where it is displayed?

Sorry for the late reply, I did not see your message. I referred to the list of contributors that you can see the image bellow.

The pagination was already implemented on camerapps whose code base is located here

Thanks. I was able to find the page and implement the pagination. Could you please check my PR #17 ?

Resolved by #17


Bump xdita grammar to latest, v0.3.0

Description
Bumps xdita grammar files to latest from lwdita OASIS repo
Motivation and Context
Updates embedded lightweight dita grammars
How Has This Been Tested?
Unit tests
Type of Changes
Version bump for dependency
Documentation and Compatibility
Covers all changes to grammar since 2018 package, which could be lengthy; may want to focus on latest?
This is technically backwards incompatible with previous one, they removed support for some elements
Checklist

My code follows the code style of this project.

https://github.com/dita-ot/dita-ot/wiki/Java-Coding-Conventions
https://github.com/dita-ot/dita-ot/wiki/XSLT-Coding-Conventions
https://github.com/dita-ot/docs/wiki/coding-guidelines

I have updated the unit tests to reflect the changes in my code.

Tested by running distribution build from this branch and using that to build output from the bundled XDITA samples:
build/tmp/dist/bin/dita \
-i build/tmp/dist/plugins/org.oasis.xdita/samples/remotelighting.ditamap \
-f html5

❌ Build fails with multiple errors:
 [gen-list] [DOTX008E][ERROR] File 'file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/hdita/intro-product.dita' does not exist or cannot be loaded.
 [gen-list] [DOTX008E][ERROR] File 'file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/mdita/intro-product.dita' does not exist or cannot be loaded.
 [gen-list] [DOTX008E][ERROR] File 'file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/xdita/led-specs.dita' does not exist or cannot be loaded.
   [filter] file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/xdita/max-number-bulbs.dita:13:73: [DOTJ075W][WARN] Absolute link 'https://www.youtube.com/embed/B7NNYE-G6x0' without correct 'scope' attribute. Using 'scope' attribute value 'external'.
   [conref] file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/mdita/led-specs.md:23:1: [DOTX010E][ERROR]: Unable to find target for conref="intro-product.dita#intro-product/warning".
   [conref] file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/hdita/considerations.html:599:8: [DOTX010E][ERROR]: Unable to find target for conref="intro-product.dita#intro-product/warning".
[topicpull] file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/mdita/product-specs.md:8:5: [DOTX031E][ERROR]: The file ../xdita/led-specs.dita is not available to resolve link information.
     [xslt] file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/xdita/max-number-bulbs.dita:12:15: [DOTX074W][WARN]: No formatting defined for unknown class attribute value "- topic/desc ".
     [xslt] file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/hdita/intro-network-lighting.html:152:12: [DOTX074W][WARN]: No formatting defined for unknown class attribute value "- topic/title ".
     [xslt] file:/[…]/build/tmp/dist/plugins/org.oasis.xdita/samples/hdita/considerations.html:152:12: [DOTX074W][WARN]: No formatting defined for unknown class attribute value "- topic/title ".

Either the samples have not been updated to keep pace with recent changes to the grammar files, or the toolkit is not processing them correctly.
For example, the first error is looking for an XDITA file samples/hdita/intro-product.dita that does not exist in the HDITA folder, but there is one at xdita/intro-product.dita.
PDF builds throw similar errors w/r/t missing files & conref targets:
build/tmp/dist/bin/dita \
-i build/tmp/dist/plugins/org.oasis.xdita/samples/remotelighting.ditamap \
-f pdf

But there's also a new error here:
[topicpull] A source of type net.sf.saxon.lib.EmptySource is not supported in this environment

Not sure if @jelovirt or @robander will recognize from the errors whether the problems are in the source files or the toolkit's parsing, but this might not be ready to ship as is.

Most of the issues @infotexture seem related to this issue -- https://github.com/oasis-tcs/dita-lwdita/pull/112
I've updated the samples and rebuilt the zip

Also noticed that this creates the unversioned subfolder plugins/org.oasis.xdita whereas the previous version used org.oasis-open.xdita with a version suffix, but since most of the other plug-ins in the distribution package use unversioned folders, I assume this change is intentional.

Updated the zip attached to the release in the lwdita repo, so that it keeps the same style as today (plugin folder includes version number).


Rework Reload Script.

This change should get Substrate completely working after jailbreak without the need to reload the System or Apple Watch LaunchDaemons and should have no regressions. It should also speed up the process going from tapping "go" after a reboot back to the jailbroken state since it reduces the number of daemons that need to be loaded/reloaded.
I noticed @kpwn's concern about reloading daemons in my pull request for the HDMI fix, and I thought: "What if instead of reloading so many daemons and risking breaking things, we only reloaded the daemons we really needed to reload?"
@coolstar gave me the idea for this approach. He said he had been doing something like this on iOS 9.3.3 to fix things when Substrate failed, so it should always work to get Substrate going.
I've tested this on my iPad Pro and iTouch 6G (both iOS 10.2), and Substrate is still working correctly, HDMI adapter is still working, and I have not noticed any other issues. The process of going from the unjailbroken state after reboot back to the jailbroken state is also sped up on both my devices. I don't have an Apple Watch, however, so I am unable to test that. :/
I'm making this pull request seeking additional testing (especially of Apple Watch interactions) and approval of the overall approach. I admit I do not fully understand how the exploits work, and if there is a need to unload/reload other daemons that I have not observed, I will gladly add them back. I just realized from my experiments to figure out how to fix HDMI that the basic exploit still works without reloading daemons. Thx.

I always thought the reloading-userland-part was necessary to inject substrate into every process and enable hooking lowlevel-stuff.

@eriksmets I don't think as much is necessary as you might think. Go ahead and give this a try and see if any hooking actually breaks . . .

@ReddestDream have iPhone 5S, iPhone 6S, and an iPad Air 1 but no Apple Watch. Would you like me to test the new commit?

@timonline Sure. Thx.

@ReddestDream seems fine on IP6S+ and the HDMI adapter works

@ReddestDream first time it successfully jailbroke and tweaks were working however, as soon as the screen turned off i couldn't turn it back on. I could however, still SSH to it.
Had to force reboot and re-jailbreak, this time worked fine. Even tested turning the screen off, back on and re-entering the password

@timonline Ah. Okay. Maybe it was just a fluke. Thanks for checking. :)

@ReddestDream no problem

Absolutely no.

@kpwn Why not?

@kpwn If you do not agree with this approach, I think you should give your point of view rather than answer "No"

This is absolutely not OK to do, breaks a lot of tweaks, is not proper, ijap00 level stuff, etc etc etc

@kpwn Okay. I get that. What tweaks does it break? I can test them and unload/reload the needed daemons.
I'm just thinking that perhaps limiting what we reload out of /System/Library/LaunchDaemons will prevent issues like the one I found with the HDMI adapter . . .

see, both the only-reload-what-is-needed and reload-all-but approaches work in theory, but in practice they are both wrong. I can argue that the former is however even more wrong than the latter. A semi-tether jailbreak should guarantee a full userland reload.

@kpwn Okay. I get your point. If you can fix AMFI so that userland can be fully reloaded without breaking anything, that's cool. I was just worried that we would see more issues creeping up with "minor" daemons like what I found with fud/HDMI . . . :/

@kpwn Thank you for explaining us the situation, I'm looking forward for another AMFI patch.
We are here to help, just ask for testing if you need us.

We are here to help, just ask for testing if you need us.

👍


[HOLD #12054] [$1000] Conversation DM bounces, flickers, and lags when scrolling downward in a long chat

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Expected Result:
Scrolling through a chat DM should be smooth (doesn't bounce, flicker, or lag) regardless of conversation length.
Actual Result:
The chat DM bounces when scrolling downward in a long conversation.
Action Performed:

Open the Expensify.cash app on an Android device
Navigate to a chat DM that has a long conversation of back and forth.
Scroll upwards for a few seconds.
Stop scrolling upward, and then slowly scroll downard at a reading speed.

Note: lag and flickering behavior is especially worsened if you:

Scroll slowly by tapping and releasing your finger each time (i.e. after each scroll downward, lift your finger, wait a moment, and then repeat...)
Fully expand the keyboard and scroll downward slowly.

Workaround:
You can still scroll, but it's a poor UX and the scroll should be smooth.
Platform:

Where is this issue occurring?
All platforms

Web
iOS
Android
Desktop App
Mobile Web
Version Number: 1.0.65-0
Notes/Photos/Videos:
https://user-images.githubusercontent.com/44479856/115792143-beb73900-a397-11eb-9183-c9f9dc35da61.mp4
Expensify/Expensify Issue URL: https://www.upwork.com/jobs/~0140ca576a3b244cff
View all open jobs on Upwork

From @quinthar https://expensify.slack.com/archives/C01GTK53T8Q/p1619067337008500

ISSUE: scrolling backwards seems to work great, but when you scroll forwards it Jitters all over the place. It's very hard to describe, but it's perfectly reproducible on android. Just go into a long conversation, scroll back a few pages, and then scroll forward slowly, and it bounces all over the place.

Triggered auto assignment to @mateocole (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Triggered auto assignment to @ctkochan22 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Labels look good

@ctkochan22 bouncing back to you - do you think this can be worked on by a Contributor?

@mallenexpensify Shoot sorry. Yes I think so.

Thanks @ctkochan22 , in the future, if a contributor can work on an issue apply the External issue so it can be posted to Upwork. Adding it now.

Triggered auto assignment to @michaelhaxhiu (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Will post today.

Just tested on my Android, and I was able to reproduce successfully. Posted to Upwork as of right now ✅ .

Triggered auto assignment to @Julesssss (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

CC @kidroca, as he had some ideas for these improvements here. Perhaps you would be interested in this issue?

I don't think this is related to cache.
When I studied the effects of virtualization I came to a similar situation when I had a large chat: https://github.com/Expensify/Expensify.cash/issues/2629#issuecomment-832516464
My theory (short version)
For big chats you reach the virtualization window boundary
As you scroll down an item is removed from the top
Another item is added on the bottom
Native, does not provide getItemLayout to the flat list
It has to put the item, render it and then shift content if it has to (only when scrolling down)
Implementing a fast getItemLayout would probably be hard.
There's an open ticket about a replacement of the FlatList component which might solve the problem here entirely
In theory this should be recreatable on iOS as well, maybe the list handles better there as the devices are beefier.
Any chance someone could try this on the oldest iPhone supported?

Any chance someone could try this on the oldest iPhone supported?

This would be good to ask in #expensify-open-source I think, as we have more eyes and exposure there. Can you post it there @kidroca? I agree with the idea of seeing if old iOS devices are included in the scope of the issue.

@kidroca @michaelhaxhiu
Here's a test running on an old iPhone 5s.
https://user-images.githubusercontent.com/53711423/122099933-f6b38900-cde8-11eb-85a5-ec7a9b97f9ec.mov
It's from the build in the app store, so probably a few versions behind our main. Feels smooth on iOS and doesn't flicker.

@rdjuric thank you! Can you try once more, but this time expand our keyboard and scroll downward slowly? If it behaves the same, no need to record another vid.

@michaelhaxhiu Sorry! Forgot about the expanded keyboard 😅
https://user-images.githubusercontent.com/53711423/122101860-2d8a9e80-cdeb-11eb-872f-c0458940cc47.mp4
The issue does happens on iOS. I was also able to reproduce it while scrolling up the chat, not only down, seems to happen whenever the FlatList render new items. It stops flickering when we approach the end (or beginning) of the chat, as the FlatList doesn't need to render any new items.

Any takers on this issue so far?

IMO this should wait the result of #2985
I don't see an easy fix and this might result in double or unnecessary work if the chat scrolling implementation is to be rehauled
Proper Bidirectional scrolling implementation should fix the current issue

Applying the planning label till https://github.com/Expensify/Expensify.cash/issues/2985 is released.

Still waiting on https://github.com/Expensify/Expensify.cash/issues/2985

Still waiting on https://github.com/Expensify/Expensify.cash/issues/2985

Still waiting on https://github.com/Expensify/Expensify.cash/issues/2985

@Julesssss, @michaelhaxhiu it looks like no one is assigned to work on this job.
Please double the price or add a comment stating why the job isn't being doubled.

Still blocked. Can I just close this GH since we are already tracking this in E/App here?
https://github.com/Expensify/Expensify/issues/167383

Still on hold.

Rory started working on https://github.com/Expensify/App/issues/2985 and will post an update sometime early this week.

Awaiting an update from Rory on https://github.com/Expensify/App/issues/2985, which Jeremy requested yesterday (September 8 2021).

Rory is making good progress on bi-directional scrolling, and working with Kidroca on https://github.com/Expensify/App/issues/2985

Issue is blocked currently

No change

Issue is still on hold due as we're awaiting the outcome of this issue: #2985

It looks like a solution is not far away in the parent issue.

Still keeping this one in the ol' holster until parent GH is complete.

Still waiting on the above

Luca & Rory are making gradual progress on the blocker GH. 🤞

Still blocked.

Blocked still

Hold

Still held

still holding on https://github.com/Expensify/App/issues/2985

Not overdue

Still on hold

Still holding

still holding

This is holding on birectional scrolling still.

Didn't we complete the bidirectional scrolling issue, so can't this come off hold now or are we actually held on comment linking or something?

Yeah agreed, I don't think this issue should on hold anymore.

Ugh damn, definitely got confused by the titling of https://github.com/Expensify/App/issues/2985 (which is actually about comment linking).

Going to take the liberty to price this at $500 to start. cc @kidroca in case you want to close a cold case 🕵 💼

@Expensify/applause Can someone please test this issue again to ensure it's still reproducible on Android?

Thanks for getting this one going again!

I was able to recreate this on Android Emulator
Checkout around the 4th and the 20th second marks:
https://user-images.githubusercontent.com/12156624/194669183-750c04a3-a022-443e-8997-eed8900ad361.mp4
I'm not sure what causes this, but it's probably related to virtualization and items being rendered outside the view window
As we scroll down actions are removed from the top and added to the bottom which causes a flicker, but it's very hard to recreate and trace

but it's probably related to virtualization

Does that invalidate the reproduction, or suggest that the problem still exists? I just reproduced it on iOS device (latest version) in a DM with a colleague. I can't upload the video because it has some sensitive internal information... but working on reproducing again in a test env where I can share the video. But safe to say - this definitely still exists and needs to be fixed.

I agree this happens pretty frequently, and in fact, I can produce it in either scroll direction pretty easily on a chat that has lots of history. Here's an example with Concierge.
https://user-images.githubusercontent.com/1127863/194794715-671f49d1-62bd-4552-89bb-ff50c7f09f96.mov

I'm not sure if this is resolvable Externally at this point in time, but I think it's valuable to figure it out and pay any parties who help us confirm. cc @Julesssss

@michaelhaxhiu we have quite a few reproductions, let's leave the issue open and see if we receive any proposals.

@michaelhaxhiu

but it's probably related to virtualization

Does that invalidate the reproduction video in any way?

No, I'm just thinking of what might be causing the problem
We can test whether it's virtualization related, by disabling virtualization for the inverted list, though this might have a big performance hit and make it impossible to scroll anyway
Since it happens on iOS as well I lean towards virtualization and/or how we render report action items - rendering an item adjusts the virtual list on the fly (item scroll position, list scrollable height), because the list has no idea how big is a comment before it render it
@JmillsExpensify

I agree this happens pretty frequently, and in fact, I can produce it in either scroll direction pretty easily on a chat that has lots of history.

Your case might be related to this ticket

https://github.com/Expensify/App/issues/7860

@kidroca Oh thanks, that one wasn't on my radar. Hopefully we'll start to get movement on it soon since we've started work on comment linking, which blocks it in turn.

Doubling price to $1000, and re-surfacing this comment:

I'm not sure if this is resolvable Externally at this point in time, but I think it's valuable to figure it out and pay any parties who help us confirm.

Given that we seem to be unholding #7860, should we now put this issue on [Hold] since it will likely be solved by that issue? That's an epic proposal that is going to be broken down into 4-5 separate issues.

@JmillsExpensify my only hesitation is assuming this will certainly be fixed by #7860.
Or perhaps better - we can directly ask @LucioChavezFuentes if they agree that this problem will be fixed via their proposal in https://github.com/Expensify/App/issues/7860.

Adding Hold to GH title as we are tracking this issue as part of https://github.com/Expensify/App/issues/12054

Or perhaps better - we can directly ask @LucioChavezFuentes if they agree that this problem will be fixed via their proposal in https://github.com/Expensify/App/issues/7860.

On Web I'm sure this problem will be fixed with my proposal. But in Android and IOS can't reproduce the problem. Need to make more tests on these platforms. Do the lists with issues have images?
By the way, what 'DM' means?

@LucioChavezFuentes ah sorry, DM = direct message

Still held.

Same same melvin

Held still. Keeping assigned while I'm OOO for 1.5 weeks. If this becomes unblocked please re-assign a new BZ @Julesssss

Still held

No change

on hold

Stillllll held

Held stilll

onhold

What's our plan for #12054? Do either of you know?

bumped the linked issue for an update

We seem held up on the contributor.

Posting internally to see if we ought to revise our gameplan or hold course.
https://expensify.slack.com/archives/C01SKUP7QR0/p1677692378964509

On hold

Still in progress...
Janic from Margelo mentioned:

I had a look, the solution here https://github.com/Expensify/react-native-web/commit/ab2ebd84250d60598e69f24c7289aafd1e82f659 seems good and what the maintainer of RN web is looking for.
The main idea is to fix RN web behaviours to match RN exactly to fix the issues with virtualized list instead of patching virtualized list to work with rn web behaviours.

Further updates in the linked hold issue this week.

Seems like the contributor has merged 3 PRs related to pagination! I think we are now waiting for another PR and then for the upstream library to be updated.

Progress is 📈 . Waiting for the fix to merge upstream at this point per https://github.com/Expensify/App/issues/12054#issuecomment-1505811916

Seems stuff is still progression, and we are very close! Let's see next week if this is ready 🐣

@Julesssss and @Santhosh-Sellavel just to confirm, is this still held? I'm having a hard time following if this is a blocker or not?

Yeah we're now holding on the RN library bump.

No movement, still held.

Same same.

Held

Still on hold

same same

Note: I'm preparing to go OOO for ~2 weeks, and making this Monthly because I doubt it'll get finished while I'm gone. When I return I'll flip it back to Weekly and oversee it.

Back from OOO, switching back to Weekly to monitor this and not let it collect dust.

BLOCKED

Still blocked

Still holding on pagination https://github.com/Expensify/App/issues/12054

I'm re-assigning this as part of my preparation for Sabbatical (starting tomorrow). Next steps:

This GH is stagnant and on hold till Pagination is in motion https://github.com/Expensify/App/issues/12054.
Labelling monthly for that reason

Still on hold

This has been open for 2.5 years, does this need to be open? 😅

Lol, probably not? We can always reopen if someone raises this again

Haha okay


Lay the groundwork for dynamic user themes.

This PR lays the groundwork to allow dynamic user themes by replacing our hardcoded colors in the tailwind config with CSS custom properties. At the moment, we're just using our existing "default" theme. A theme would consist of both a "light" and "dark" set of colors.
This PR does not add the actual functionality to allow the user to change the colors, but that will be straightforward. We could surface the functionality in settings and stick their theme colors in the settings store for the groups or talk desks. We could also just store their theme settings in localStorage on the browser (via zustand and persist).
Only outstanding issue I've found is the GroupHeader SidebarItem not highlighting properly. @jamesacklin, you worked on that, is there something I'm missing there?

Won't delete the branch, just closing the PR for now.


Question: why use both dotenv and webpack 2 --env?

Why not just:
{
  "development": "node ./tools/development/server",
  "build": "npm run clean && webpack --config ./tools/webpack/client.config.js && webpack --config ./tools/webpack/server.config.js",
  "prestart": "npm run build",
  "start": "node build/server/main.js"
}

and let the .env manage the NODE_ENV thing, like the other variables?
Its just a question trying to understand if there are any reason about that. Thanks!

The prestart script is just an idea of the moment, just to ensure that npm start will have the build first

It's an interesting questiom, thanks!
I shall def give this some thought.
Simplification is always appealing. :-)

So, in my project, I can safely put NODE_ENV into the .env file right?

Yep, there is no reason for you not to. :-)
I haven't had time to go through this all yet, but I will let you know when I have.

Hi @cloud-walker
Eventually looked at this.  My thinking for having the NODE_ENV be controlled via the webpack config rather than the .env file is that it gives us the capability to easily run the project in development or production mode per environment.  I like to be able to run both on my development environment for example.
I am going to close this for now.  If you did end up adding NODE_ENV to your .env file please let me know how your experience was and if you had to make another other changes to the workflow.
Thanks