Test Case TC05 - Cart Functionality – Finish and Pay - Method Not Allowed Error

Bug Report
Summary: Test Case TC05 - Cart Functionality – Finish and Pay - Method Not Allowed Error
Date: [10-21-23]
Reporter: Jason Lee
Description:
While executing Test Case TC05 - Cart Functionality – Finish and Pay, the test did not pass as expected. The test case involves checking the functionality to finish and pay for items in the cart. Instead of the expected behavior, a "Method Not Allowed Error" occurred during the testing phase.
Test Case Details:
Test Case ID: TC05
Test Case Description: Cart Functionality – Finish and Pay
Test Data: Z: Zoolando, B: Back to the Present
Expected Results: Items should be displayed with payment total.
Actual Results: Method Not Allowed Error – Payment page was incomplete during testing phase.

Click on the Search button.
Input letter in the search box.
Click Search.
Click Add to Cart.
Repeat Steps 3-5.
Click Cart.
Click Finish and pay.
Additional Information:
Browser: Edge
Operating System: Windows 11
Screenshot:

Impact:
This bug affects the ability of users to complete their purchase through the cart functionality, which is a critical part of the system. It prevents users from successfully making a payment for items in their cart.

Payment page accessible as of 9b152746d4dd8f64239b986d218fb37a6cf929ed - not all functionality completed, but page is accessible without error


[Event Request] codeunit 90 "Purch.-Post" - PostResourceLine

Hello,
Please add SrcCode, GenJnlLineExtDocNo, GenJnlLineDocNo, PurchInvHeader, PurchCrMemoHeader, JobPurchLine to arguments of OnBeforePostResourceLine publisher:

@NiroWolfee You help us implementing the requests faster when your request contains AL code copied from VSCode as a text instead of screenshots.


[Bug]: await page.keyboard.press("LeftArrow") not firing!

Bug description
Steps to reproduce the problem:
const puppeteer = require('puppeteer-core');

(async () => {
    const browser = await puppeteer.launch({
        headless: false,
        executablePath: 'C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe',
    });

    const page = await browser.newPage();
    await page.goto("https://youtube.com");
    await page.waitForNavigation();
    await page.keyboard.press("F12");
})();

Puppeteer version
13.1.2
Node.js version
16.13.0
npm version
8.1.0
What operating system are you seeing the problem on?
Windows
Relevant log output
there are no errors in the log it just doesn't press f12

The title says 'page.keyboard.press("LeftArrow") not firing' and the example shows page.keyboard.press("F12"). Are you having issues with LeftArrow or F12?
Are you trying to open Dev Tools with keyboard.press()? It does not work that way. The key press will be sent to the page, but the browser will not open Dev Tools.
You can set devtools to true in the launcher options  to open devtools.

I am trying to press left arrow and then enter, i just used f12 so i can see it better. But nothing works with page.keyboard.press(). I am doing this because when i press the play button on roblox.com, it asks me if i want to launch roblox with a popup.

I also tried using page.on("dialog", () => {}); but it doesnt fire at all

@rubiconjosh  It's because the code is ArrowLeft, not LeftArrow


Suggestions to improve grad videos

I've experimented quite a bit with the extension and ended up in video/gif editor every time, so decided to list some things that seemed annoying yet could probably be easily remedied.
These improvements seem to be trivial:

Option to only output every other frame into video (solves pingpong issue, can technically be done by using even step count)
Option to change interrupt behavior so that last two frames (the unfinished one and final frame, probaby not reached) are not added.
Option to start and finish video at some percentage (20% to 80% tend to be most meaningful for 2-point travel)

And these might be a lot to ask:

Option to output a GIF (pingpong or repeating, with optionally extended durtion of first/last frames)
Option to drop frames that have high similarity (with any reasonable kind of threshold)

Thanks for your attention and kind suggestions~
I would try to fix 1~4 by adding new video export options. As for 5, I will re-enable subseed, you can try that maybe. But still I would highly encourage you to use higher FPS as a work around, or pick only even steps like in suggestion 1.
PS:
I guess that you might be mainly annoyed by the tailing broken or un-consecutive images in the video end? :lol
Because currently this repo is more like an experimental dice-rolling playground than a product-level applet. In this sense, the exported video is exactly a full expriment recording to me, allowing us to check the sampler performance (non-converging ping-pong phenomenon, the converging direction and speed, etc.), hence I did not kick out the bad ones.

I understand that this is an expeiment, but it's very interesting one, absolutely worth exploring more if possible. The conceptual morphing coming out as a result is superior to classic geometric interpolations in many ways. Sadly I don't have a good grasp on what's happening in latent space so I can't give ideas on improving pathfinding, but even in current state, grad is interesting.
Option 5 was more about equalizing velocity of a video that would otherwise get slow down on some state that's spanning wider and takes longer to pass through, which contrasts with rapid changes happening in other frames.

Option 1~4 should be available now in last commit. 😃
I tried a bit on Option 5, but find that the reasonable threshold varies from prompt to prompt, it's not likely to be auto determined without interactive tuning. Currently this script is stateless, and the file exporting could not be separate from the image generating procedure. so I just give up attempts for the moment (
Though the grad mode seems working, it's behaviour is somewhat out of my expectation 🤣
Hence I'm continuing to hack into the samplers. The gradients should be recomputed at each sampling step (current implementation only approximate gradients of the final step), that sounds should be more accurate in my sense.
I will experiment this it in another repo and maybe backport it later.


NETOBSERV-91 crd generate

Call crdoc on make generate
output docs/crd.md
Is it ok to everyone to call go install fybrik.io/crdoc@latest from the makefile or do you have a better way ?

/lgtm, thanks


Property testing for account updates

This adds a quickcheck-style testing lib based on random generation of many examples. The main goal is being able to generate many non-trivial examples of complex structures like account updates. To this end, the testing lib is integrated with the deriver code, so the combinators for account updates don't need to be specified manually.
Why not use an existing property-based testing framework, like fast-check?

integration with deriver code would've been a pain
we would've had to write many generators ourselves, anyway, to create things like random fields or public keys
if you strip away the fancier stuff like shrinking failure cases, it's pretty simple. it's all about creating good random values.
if this is going to be useful outside of mina-signer -- for example, creating transactions that are actually valid on the ledger -- it will need some very custom tooling, which is always simpler to build from scratch than on top of an opinionated lib

Which issue does this solve right now?

testing a much greater variety of zkapp transactions was one of the feedback items form the mina-signer audit, and this will make it very simple and nice to maintain

do we treat this as a prototype and follow up with something more refined? Or just leave it as is? (Which could just mean writing about it or it could entail you or others discovering some different approach taken)

Excellent question. My plan was mainly to use this for some immediate use cases:

generate random valid payments / stake delegations. this is possible already
generate random valid zkapp transactions. this needs just a bit more work because the account update callDepth is a global property of the transaction (so can't be set randomly locally) and because I want to hit cases where the same public key is used several times (won't happen currently because public keys are completely random)
help with negative tests by generating invalid cases.

all of those are easy to solve with minor additions to the current framework. as such, I'm planning to use this as is, with minor changes, and add additional conveniences / use it in more tests as needed in the future.
given all this, I think there's an implicit commitment to this architecture and I should write up a small RFC?

It looks very nicely implemented! I do have a similar concern to Brandon's, namely that we'd be committing a litle too casually to some fairly consequential decisions. I'd like a clearer sense of where we'd use this (all tests, only ones that simulate transactions, ?), and what we'd trade off with other approaches. Something like a smallish RFC would probably be the way forward from here. You up for putting that together?
An interesting thing just happened at the process level. I hope you don't mind me commenting on it here. It's always worth noting instances where work seems to appear unexpectedly like this sudden need for an RFC. It doesn't make the work wrong or bad necessarily, but it does make it surprising. So how could this be less surprising? I like to think of the act of committing to work as occuring in stages that present specific resistance barriers. Quick example: First we add an issue to the backlog, which requires very little work or commitment. We only put in the effort to properly write out clear intentions and value if we believe in that work. Then we only force the tough priority choices if we feel strongly enough to advocate for it happening soon. Only then do we put together design docs and elicit feedback, which is a necessary but fairly expensive process. There are useful barriers to commitment at each stage that focus us on the most important things and mamnage the amount of upfront work required (a clear expression of Just-In-Time from lean production principles). So how does that relate here? We find ourselves at a fairly late stage, committed to fairly expensive work (an RFC) without having benefitted from the preceeding gating steps. By skipping some friction we have lost the opportunity to choose how much effort we should spend.
It may well be that we'd have ended up here anyway and I'm up for quickly putting together a design doc and moving on. Just wanted to point out that we take a bigger gamble than necessary with our effort if we skip those moments of friction along the way. Hope this lands okay and checks out for you! Feel free to query or challenge as always.


Set headers on page frontmatter

Hi!
I have some issues with google analytics on amp pages and I have found a tested solution, but it is necessary to set some headers. I thought about programming a plugin, but I think it would be interesting to incorporate a option for set headers from page frontmatter (https://github.com/getgrav/grav/issues/1591) in the core because amp is something increasingly important.
Google Analytics Client ID In AMP Pages:
https://www.simoahava.com/analytics/google-analytics-client-id-amp-pages/#wp

All rendered output is left to the theme.  If you wanted to automatically output some headers, then it should be done in a plugin, not in Grav core.


3d Model and ImageBasedLighting visibility issue

Hello again :) I've noticed a glitch in the ImageBasedLighting or LightingEnvironment class. When you change model visibility to false and turn it back on in for example 3-4 minutes (that value is random, just turn visibility off for a long period of time), the image based lighting is gone. By gone I mean it's just not rendering anymore. The cubemap texture seem to stay in the LightingEnvironment.main object, but they are not applying on the 3d model anymore.
Cheers!

Hello! Which version of PixiJS did you use when testing this?

Hi, I did some more debugging. The issue happens in all version between 5.0.0 and 6.5.0. My game is using pixi version 5.3.10.

Unfortunately this is a bug in PixiJS versions < 6.5.0. The fix in PixiJS was provided in https://github.com/pixijs/pixijs/pull/8479.
The bug happens on automatic gc inside PixiJS. If you can turn it off it should not happen. Try this in your app and see if it helps (depending on your app you might need to destroy your assets yourself if automatic gc won't do it):
PIXI.settings.GC_MODES = PIXI.GC_MODES.MANUAL

Thank you! I'll look up the fix commit.


It is not possible to test if StreamSink is closed

Hi,
Using StreamController you can test if the sink is closed by checking the isClosed property:
if (StreamController.isClosed) return;

// we push data to the controller

but if we pass StreamSink we can't test if it is closed or not to decide whether to add data or not, there is no StreamSink.isClosed !
regards

Correct.
A StreamSink is a very primitive interface, all push, no obvious state, because it could be a wrapper around something else, and we don't want to force it to maintain its own state.
So no state inspection either.
We're unlikely to change the StreamSink interface without very good reason, since it would break every implementation of it.
So, no plan to change.


 If acpi returns 0% charge, the device is likely a desktop without a battery.
Changes haven't been tested yet, testing yourself would be appreciated!
Fix #526

In the meantime, could I ask for some documentation on how to actually locally run your tests? I just get some npm error about some shintango2 package or something not being installed from ./scripts/tests.sh. I can't seem to install it with npm either.

about some shintango2 package or something not being installed

:laughing: We depend on kward/shunit2 for testing as submodule.

Update submodules in your fork (via git submodule update --init --recursive)

CONTRIBUTING.md#setup
After that npm test should work fine. Let us know if you've any trouble after that.

Any progress on this? I'd like to merge this.

Just waiting for a second person to review, I believe.

@Snuggle good. I'm merging this.
P.S: I'll be grateful for a PR with some tests for battery section.


Update Codebar video for review

Please find attached the edits that I think we need to make in order for the footage to be useable.
0:17 – 1:24 - Giant Toy Meerkats in view / Meerkats on shoulders / Listed companies sign in view so needs removing
1:34 – 3:37 - Giant Toy Meerkats in view / Meerkats on shoulders / Listed companies sign in view so needs removing
3:48 – 3:56 - speaker says “this guy is doing 3 people” so needs removing
3:48 – 8:07 - JHWR (process poster) in view so needs blurring
12:12 – 12:17 - JHWR (process poster) in view so needs blurring
10:11 – 11.56 - Bean Open Banking’ sign in view so needs removing/blurring

Not worth the hassles, decided to record a new video with Codebar


hop-node: Db: Clean up and simplify

Makes transferId required in TransfersDb, with exception to update function which auto assigns it (#344)
Makes transferRootId required in TransferRootsDb,  with exception to update function which auto assigns it (#344)
Simplifies subDbX key update in TransfersDb; the update function is simpler now
Simplifies subDbX key update in TransferRootsDb; the update function is simpler now
Cleans up the false expected timestamped key logs
Removes migration from TransferRootsDb

Added redundant comments/questions on a few upsert functions that I don't totally understand

Thanks, your comments made sense and updates have been made. https://github.com/hop-protocol/hop/pull/351/commits/6fd88c22d80439b9ab8349efbb41c7b7f8b5b1ec

Looks like the the SettleBondedWithdrawal watcher has some non-null assertions that can be removed too 1 2

I actually don't think they can be removed because the transferRootId is from the db Transfer item and not TransferRoot. The transferRootId field has to be optional for Transfer since it only exists after root is committed.

It looks like those logs were completely removed. With these updates, is there no longer the case where there will never be an “expected timestamp key”? If so, how does the very first insert work when there is no timestamp?

Correct, there will never be an 'expected timestamp key' log because it'll be already expected that the timestamp field won't exist during the event db updates in pure sync watcher poller, and the logs can cause confusion. This condition in isItemIncomplete should be true if transferSentTimestamp is missing and incompleteTransfersPollSync should pick it up which runs it through the populateTransferDbItem functions to populate, and it should be clear if there are any errors while populating the timestamp field. Basically I don't think that log is necessary since it'll always log multiple times for every update in pure poll syncer, and there are other logs that log timestamp key errors in sync watcher.

Super loose opinion here, but how do you feel about keeping the migration logic in the constructor and an empty migration() function in the code. Something like the following. The goal here would be so that we don’t forget to add/rm the this.ready = true in the constructor, since it needs to be moved/removed every time a migration is performed. I’ve already forgot to move it once and it cause an hour or two of debugging, so I’m just trying to think of the best way to remove this concern.

I think that's a really good idea. I moved it to the BaseDb and now migration can optionally be implemented in the child classes, without having to deal with the ready flag. https://github.com/hop-protocol/hop/pull/351/commits/6fd88c22d80439b9ab8349efbb41c7b7f8b5b1ec


AM-2936 TEST PR for PR-1689: Test with RAS subchart disabled

Jira link (if applicable)
AM-2936 "Pipeline improvements: reconfigure ORM PREVIEW chart to use an independent version of RAS and JBS"
Change description
Test of #1689 / #1855 with RAS subchart disabled.

NB: This PR is a TEST for #1689 / #1855.
see also:

#1860
#1862

Checklist

[x] commit messages are meaningful and follow good commit message guidelines
[x] README and other documentation has been updated / added (if needed)
[x] tests have been updated / new tests has been added (if needed)
[x] Does this PR introduce a breaking change - NO

Test complete: see evidence in ticket.


Update Composer dependencies (2021-10-17-00-11)

Visual regression test passed!
View the visual regression test report


#define ⇒ enum?

Would you like to replace more defines for constant values by enumerations to stress their relationships?

Feel free to submit to PRs, making sure the values stay the same.


Layout shift in header

There's a layout shift when the logo loads. This can be fixed by giving the img element a width and height, then height:auto in the CSS.
https://user-images.githubusercontent.com/93594/135231891-cc21e70d-e5e4-4e89-b82d-7205a6f47747.mp4

LGTM, but a tweak in https://github.com/GoogleChrome/devsummit/pull/384


NEMS + ATMESH + SCHISM test case

Please update here: @feiye-vims @josephzhang8

@josephzhang8 @platipodium @pvelissariou1
Working to get ATMESH+SCHISM works with multiple cores.

My status on femto and strand is still that it breaks with multiple procs.  Trying to disentangle Takis's cplList issue but having trouble to see where the issue really lies :=(

PLEASE follow up here:
https://github.com/noaa-ocs-modeling/CoastalApp/discussions/150


build: Simple debian packaging for quilt

This patch adds functionality to create debian packaging for quilt
(i.e. a .deb file that can be installed easily by users). Output is
generated within the dist/ directory.
It does not completely comply with debian packaging policy as we
use dependencies that are not in debian yet, and the package is
currently not run through lintian. It should be sufficient for
test distribution for the time being.
Also, we might want to just put this in some sort of build branch or something, since the debian folder can be extra clutter. I don't think this necessarily belongs in master.

@Baisang  I have a few questions and comments, but I don't need to look at it again. @ejj or @kklin might have more of an opinion on the setup, directory structure, and details of the packaging...

We're going to close this for now because we want to distribute binaries through npm at first. Debian packaging doesn't seem worth the overhead right now, especially considering the effort needed to get it merged upstream.


System.InvalidOperationException: Sequence contains no matching element

Describe the bug
When I run EpicPrefill  prefill -f I get the error: "System.InvalidOperationException: Sequence contains no matching element"
Additional Details

Platform you are running EpicPrefill on:

Debian GNU/Linux 11
Linux lancache 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux on bare metal

Discord Username (if you are part of the Lancache Discord Server) : billcat
Region : Central US

Screenshots
user1@lancache:~/EpicPrefill$ ./update.sh
Checking for latest version
Found latest version :  1.1.1
Downloading...
EpicPrefill-1.1.1-linux-x64.zip                      100%[======================================================================================================================>]  12.67M  --.-KB/s    in 0.1s
Unzipping...
Complete!
user1@lancache:~/EpicPrefill$ ./EpicPrefill clear-cache
[10:25:49 AM] Found 3 cached files, totaling 2.61 MiB
[10:25:50 AM] Done!
user1@lancache:~/EpicPrefill$ ./EpicPrefill prefill -f
[10:26:06 AM] Reusing existing auth session...
[10:26:06 AM] Retrieving owned apps
[10:26:10 AM] Loaded new app metadata for 16 apps
[10:26:10 AM] Retrieved 16 apps                                  03.7645
[10:26:10 AM] Starting Satisfactory Early Access
[10:26:10 AM] Downloaded manifest                                00.0498
[10:26:11 AM] Downloading 9.02 GiB
[10:26:11 AM] Detected Lancache server at localhost [<IP_ADDRESS>]
[10:26:17 AM] Finished in 06.3728 - 12.15 Gbit/s
[10:26:17 AM] Starting Satisfactory Experimental
[10:26:17 AM] Downloaded manifest                                00.0437
[10:26:17 AM] Downloading 9.02 GiB
[10:26:23 AM] Finished in 05.9489 - 13.02 Gbit/s
ERROR
System.InvalidOperationException: Sequence contains no matching element
at System.Linq.ThrowHelper.ThrowNoMatchException()
at System.Linq.Enumerable.First[TSource](IEnumerable1 , Func2 )
at EpicPrefill.EpicGamesManager.DownloadMultipleAppsAsync(Boolean downloadAllOwnedGames, List1 manualIds)   at EpicPrefill.CliCommands.PrefillCommand.ExecuteAsync(IConsole console)   at CliFx.CliApplication.RunAsync(ApplicationSchema applicationSchema, CommandInput commandInput) in /D:\a\CliFx\CliFx\CliFx\CliApplication.cs:147   at CliFx.CliApplication.RunAsync(IReadOnlyList1 commandLineArguments, IReadOnlyDictionary`2 environmentVariables) in /D:\a\CliFx\CliFx\CliFx\CliApplication.cs:191
user1@lancache:~/EpicPrefill$

I got the same error - but on a fresh install.

I got the same error - but on a fresh install.

Not the same error - I just didn't have any games on the account

I got the same error - but on a fresh install.

Not the same error - I just didn't have any games on the account

Added a check to make sure that at least 1 game is installed as part of this issue https://github.com/tpill90/epic-lancache-prefill/issues/40

@billthecatt I know its been a year since you opened this, but have you seen this pop up since?

Closed since its been over a year since this was opened, and I haven't received any additional info.  Please feel free to reopen if it happens again.


Cleanup

Follow up #180.

Codecov Report

Merging #185 (2e31982) into master (30fc2b7) will decrease coverage by 0.21%.
The diff coverage is 51.06%.

@@            Coverage Diff             @@
##           master     #185      +/-   ##
==========================================
- Coverage   37.64%   37.43%   -0.22%
==========================================
  Files          86       86
  Lines       10096    10061      -35
  Branches     2119     2118       -1
==========================================
- Hits         3801     3766      -35
+ Misses       6097     6093       -4
- Partials      198      202       +4

Impacted Files
Coverage Δ

neural_sp/bin/asr/ctc_forced_align.py
0.00% <0.00%> (ø)

neural_sp/bin/asr/eval.py
0.00% <0.00%> (ø)

neural_sp/bin/asr/plot_attention.py
0.00% <0.00%> (ø)

neural_sp/bin/asr/plot_ctc.py
0.00% <0.00%> (ø)

neural_sp/bin/train_utils.py
0.00% <0.00%> (ø)

neural_sp/evaluators/accuracy.py
0.00% <0.00%> (ø)

neural_sp/evaluators/character.py
0.00% <ø> (ø)

neural_sp/evaluators/edit_distance.py
2.63% <ø> (ø)

neural_sp/evaluators/phone.py
0.00% <ø> (ø)

neural_sp/evaluators/ppl.py
0.00% <ø> (ø)

... and 42 more

Continue to review full report at Codecov.

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


add platform flag to docker commands to  enable M1 machines

If no flag provided the default platform is used.
For M1 machines it's arm64/v8, not amd64 like for most other devices.
This change will allow to run Makefile on M1 machine without affecting everyone else.

We maintain an internal branch reejig-master for our version. And use master to keep in sync with the upstream.

We maintain an internal branch reejig-master for our version. And use master to keep in sync with the upstream.

Updated


new icons do not display properly even with Nerd font

Hi
A recent commit introduces new icons for the button used to drive the debugger (start, step-over, step-into, ...). For some reason, these characters do not display properly in Windows Terminal using Nerd font.  The previous set of icons, as well as all the other traditional webdev icons, do display properly with this Font.
Do you have any font recommendation to fix this?
Thanks!

Yep see https://github.com/rcarriga/nvim-dap-ui/pull/167#issuecomment-1313291149 :smile:

Great thanks! I'll have a look


Prepare Core libraries for September 2024 release

API change check
API changes are not detected in this pull request.

/check-enforcer override


Add jitter to discovery cache TTL

Is your feature request related to a problem? Please describe.
Right now, nri-kubernetes caches the output of the discovery operations for a certain period of time. However, this TTL is fixed for all instances of the DaemonSet. For clusters with a significant number of nodes, this causes caches to deterministically expire at the same time, which creates bursts of load in the control plane.
Feature Description
We'd like to add some randomness to the expiration of this caches, so it is unlikely that all requests happen at the same time.
As a nice to have, it would be nice to be able to configure:

The TTL itself
The max amount of random deviation from the target TTL

I think there should additionally be maxSurge set on DaemonSet upgrade strategy, because the cache is not persistent anyway, so on restart/update, all instances will be querying at the same time anyway.

Very good point. I wonder though if setting this might have undesired effects in large clusters: Surge of 3 when we have 5 nodes it's not a big deal, but a surge of 3 when there are 1k nodes is relevant as it will take a long time to get data for the whole cluster.
Perhaps we could expose this in the helm chart, so users can tweak it as needed?

I still struggle to figure how to make the jitter configurable and what would be the reasonable approach here.
First decision is, do we want to only reduce (-) the TTL or also increase (-+) it? Only reducing will increase total amount of requests sent, but will guarantee that all nodes re-do the discovery after the TTL, which might be important in alerting etc. Increasing or reducing the TTL randomly will keep the number of requests the same on average, but the total time to refresh all caches won't be fixed, so it's harder to determine.
Second decision is, what % of the TTL the jitter should be. If we randomize from 0 (so jitter 100%), we should get a flat distribution of requests, which is IMO good from scalability point of view, as load remains stable. If we take some smaller value like 10%, then the load is spread over 10% of the TTL, which still makes the load spiky, though not as much.

Those are good points, but I do no think they matter a lot to users. In the end, this cache is not really user-facing, so we won't risk breaking expectations or are forced to provide strong guarantees (as it would be the case if these were an API cache). I would be fine with any approach as long as it is documented next to the parameters the user needs to change.

do we want to only reduce (-) the TTL or also increase (-+) it?

I would prefer +-, because intuitively it will make the real TTL closer to the target value. Additionally, when t → ∞, the average TTL would be exactly the configured value. If we did it one-sided, this would not be the case.

Second decision is, what % of the TTL the jitter should be

Ideally we should make this decision based on:

The time that this request takes
The number of nodes that would be making this request
The target permissive amount of requests we want to be in flight at the same time
Some fancy stats shenaningans and a target likelyhood for that to not happen

Unfortunately we do not have any of this, so I would resort to just guessing. In my extremely subjective view, a default 20% of jitter (+10% and -10%) would be reasonable. Seems small enough to not make users worried, or at least I would not mind this level of uncertainty. Users with bigger clusters might want to play with these two values to their heart's content.

The time that this request takes
Given the frequency of the requests 1/h on a single node by default, I think request time can be ignored here.

The target permissive amount of requests we want to be in flight at the same time

Exactly. So if as an example, we have 1000 notes and all of them do a discovery at the same time, we get 1000 operations, then 1h wait. With jitter from 0, we could spread that approximately to 4 req/s, constantly. For less number of nodes, it would be less.
So, shall we:

call a feature flag TTLJitter
make it 0 by default? Or 20?
make it unsigned

Recent jitter-related PR on K8s: https://github.com/kubernetes/kubernetes/pull/101652

Interesting, I didn't know about apimachinery/wait. Seems like it's a bit tailored to time.Duration though, I'm not sure if it would be more readable than what we do now after all the weird time arithmetic.


ensure 'maxResults' limits the number of suggestions too [not ready]

i would expect setting maxResults to impact how many suggestions are returned, not geocoding matches.
right now, even though 'L.esri.geosearch' passes along a maxResults parameter when ultimately calling the find operation of the World Geocoding Service, since a magicKey is included too, only one candidate is ever going to come back.
this code change has the desired effect of exposing a technique to augment the number of suggestions returned, but needs a little more testing to make sure all is well with the other providers.

okay, the PR got a tad sidetracked, but in my testing i noticed we were not handling custom geocoding services well previously at all.
changes/fixes:

use /findAddressCandidates for custom geocoding services by default
in addition to checking custom geocoding services to see if they support /suggest, also make a point to fetch alternate singleLineAddressField parameter names
checked to make sure candidates have an extent before trying to utilize it
throw a console warning and skip firing a /suggest request when the service doesn't support it.
moved to 'watch' to rebuild source

in addition to getting tests passing, i confirmed manually that both World and legacy custom geocoders can be used successfully directly via Tasks, from Service methods and from the Geosearch control.
maxResults is honored in suggestions, find/findAddressCandidates calls, and featureServices and mapService queries too.
ready for review.


Page misalignment

This is a weird new bug that seems to be a side effect of 46e302c4fb99b7c5957295ccff4ebf2fc5022907. The page is somehow misaligned in my reader. The text is properly aligned at the start of each chapter, then it slowly moves to the left with the next page shifting out from the right, the farther away you move from the chapter start.
It's hard to explain so I took some screenshots instead :

I don't understand why this would even happen in the epub reader since the reader is just supposed to render text.
Hopefully, it makes sense to you.

It kinda does. I've set a global style on body for margin, which I think is getting re-applied on every page.
Can you try a rebuild after removing the following 3 lines from style.css:

https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/style.css#L41
https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/style.css#L113-L114

And see if it fixes the issue? I'll try installing Icecreame over wine to see if I can figure this out better.

Tried it, no change unfortunately.

Try removing the entire body section: https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/style.css#L36-L42
If that doesn't work, it has to be the text-align: justify, which will get us back to the center aligned text. Will see if I can find an epub css template.

Nope, I removed the body and the text-align and it broke the justification but the page overlap remained. I then removed the stylesheet argument and it fixed it (but justify broke of course).
https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/methods.rb#L44
Then I started to progressively delete anything I saw in the css (I don't understand any of it) until it worked.. I had to do a lot of tests before I realized that if I don't delete the ebook from the reader, then empty the trash, then close the app before opening the file, then it would somehow load a cached version of it...
Anyways, I found the faulty line : https://github.com/captn3m0/cosmere-books/blob/46e302c4fb99b7c5957295ccff4ebf2fc5022907/style.css#L108
Just delete that line (which ironically says "increasingly indent" ) and it will fix it!

Thanks for the debug, will commit the fix. (I don't think this should affect the PDF version, but have to confirm)


Support instagram insight/analytics

Hey, any plans to support instagram insight/analytics?

@kevinjon27 not realy sure if this is part of private api. But honestly accepting PR, otherwise no at this moment.


Milestone Report - List and Status of Deliverables

TODOS:

List all deliverables

State the status of deliverables

Add comments on them if needed

Created a table and filled it.

Drew it in Milestone 1 Report page.

Done. Can be checked here.
Note: There are some incomplete deliverables, I will update the status of them when updated.


Improve Passport support for API servers (i.e. avoid unnecessary [client-side] request redirections)

I have been reviewing authentication & authorizations solutions for my AngularJS application, which talks to the server through a REST API. I found two interesting candidates:

Passport has a great design and really clean API, nice work! Unfortunately, it does not provide a good user experience as it relies on client-side redirection for performing authentication with external providers.
Sattelizer for AngularJS provides a good user experience on the client but it requires you to write everything about token exchange, user data extraction and API request authorization on the server (see: https://github.com/sahat/satellizer/blob/master/examples/server/node/server.js#L454).

Why not use the best of both worlds, Satellizer for client-side authentication and Passport for backend token exchange and API requests authorization? Because Passport needs to be decoupled from any unnecessary client redirection.
I believe that the effort to refactor Passport and keep backwards compatibility would be minimal. Decoupling Passport from the client would allow nice integration with 3rd-party libraries (see an example below) as requested by some other users (https://github.com/jaredhanson/passport/issues/334, https://github.com/jaredhanson/passport/issues/318, https://github.com/jaredhanson/passport/issues/336, ...).
Satellizer and Passport integration?
After digging into the source source, I found that passport-oauth2 expects auth code to be present as a query param in the callback URL (https://github.com/jaredhanson/passport-oauth2/blob/master/lib/strategy.js#L140):
if (req.query && req.query.code) { ... }

Satellizer can call the same callback URL but uses POST and body data (https://github.com/sahat/satellizer/blob/master/satellizer.js#L494), which imho is a clean way to delegate access token retrieval by the server.
It would be awesome if this access token exchange logic could be extracted as another Passport middleware, i.e.:
app.post('/auth/facebook/callback', passport.exchange(
    'facebook',
    { session: false },
    function(req, res, err, accessToken, profile, info) {
        ...
    }
));

passport.exchange(...) would be responsible to retrieving the auth code from request (using query params or body data), exchange it for an access token and fetch user profile data.

+1

+1

+1

+111


POJO properties to form properties

Consider the following pojo:
class Pojo {
  String firstName;
  String idNumber;
}

And we would like to map it to x-www-form-urlencoded as:
f_name={firstName}
id_no={idNumber}

We propose to use a property name to form value key mapper as:
class Pojo {
  @FormProperty("f_name")
  String firstName;

  @FormProperty("id_no")
  String idNumber;
}

@xxlabaza please comment if this issue is worth an improvement

@marembo2008 I will take a look at this in the end of the week. Sorry, too much work


Raspberry Pi support

RPi is a pretty commonly held ARM board, support would allow lots of others to test zinc.rs. It would mean adding support for the Broadcom SoC that the RPi uses.

Any chance of moving this forward? Compiling to bare metal Raspberry Pi is definitely possible with Rust (http://blog.thiago.me/raspberry-pi-bare-metal-programming-with-rust/), but without Zinc using plain Cargo it's hard.
Also check out this blog series: http://www.valvers.com/open-software/raspberry-pi/step01-bare-metal-programming-in-cpt1/ and this repository: https://github.com/dwelch67/raspberrypi
I would love to replicate these tutorials in Rust.

I reconsidered my stance that it's out of zinc scope and I'm ok with incoming PRs.


reserved identifier violation

I would like to point out that identifiers like "__MALLOC_HOOK_H" and "_RWLOCK_H_" do not fit to the expected naming convention of the C++ language standard.
Would you like to adjust your selection for unique names?

Thanks for your improvement of affected include guards.


cordova/platforms/android/app/src/main/java/com/google/cordova/plugin/BrowserTab.java:21: error: cannot find symbol import android.support.customtabs.CustomTabsIntent;

cordova/platforms/android/app/src/main/java/com/google/cordova/plugin/BrowserTab.java:21: error: cannot find symbol
import android.support.customtabs.CustomTabsIntent;
                                 ^
  symbol:   class CustomTabsIntent
  location: package android.support.customtabs

cordova/platforms/android/app/src/main/java/com/google/cordova/plugin/BrowserTab.java:104: error: package CustomTabsIntent does not exist
    Intent customTabsIntent = new CustomTabsIntent.Builder().build().intent;

While trying to run this project, already after fixing https://github.com/google/cordova-plugin-browsertab/issues/43.

Issue can be fixed by replacing import android.support.customtabs.CustomTabsIntent; with import androidx.browser.customtabs.CustomTabsIntent;.
We badly need https://github.com/google/cordova-plugin-browsertab/pull/45 to be approved, then it should work out-of-the-box.

Issue can be fixed by replacing import android.support.customtabs.CustomTabsIntent; with import androidx.browser.customtabs.CustomTabsIntent;.
We badly need #45 to be approved, then it should work out-of-the-box.

@danieldanielecki did you got any update on #45 ?

Issue can be fixed by replacing import android.support.customtabs.CustomTabsIntent; with import androidx.browser.customtabs.CustomTabsIntent;.
We badly need #45 to be approved, then it should work out-of-the-box.

@danieldanielecki did you got any update on #45 ?

nope; that's not my PR!

i ending up using after_prepare hook to patch the java file


[NoTicket] hardening of scheduler

Coverage remained the same at 83.942% when pulling c6d06b3f01ffd676c51053c1c0559a58b191bdc7 on NoTicket-Hardening-of-Scheduler into 4482f72e31f1586cf755dc74b1d97cdb20295d61 on master.


Bump mq

Brief description
Bumps mq to use parallel request handling
Checklist

[X] I have built this pull request locally
[X] I have ran the unit tests locally
[X] I have manually tested this pull request
[X] I have reviewed my pull request
[ ] I have added any relevant tests

Demonstration

Pull Request Test Coverage Report for Build 83

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

Totals

Change from base Build 77:
0.0%

Covered Lines:
113

Relevant Lines:
139

💛  - Coveralls


PagedFlux withContext Method

FluxUtil is missing a withContext method that takes and returns a PagedFlux, this prevents async listing operations from passing through user context correctly.
Add a withContext method overload into FluxUtil that takes and returns a PagedFlux.

Closing this as this can use the existing withContext: https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/keyvault/azure-keyvault-secrets/src/main/java/com/azure/security/keyvault/secrets/SecretAsyncClient.java#L691


r3.o.lencr.org

Hi there,
r3.o.lencr.org is a false-positive as this is the OCSP validation server for Let's Encrypt's R3 intermediate certificate.
This results in the webpage depending on a user's browser setting from soft-failing upwards to hard-failing and not loading at all due to an OCSP server error.
Thank you

It is not currently blocked, might have been in an old version of the list


Only say the cache is used if it exists

Codecov Report

Merging #78 (831700d) into main (42bc8ba) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##               main      #78   +/-   ##
=========================================
  Coverage     99.57%   99.57%
- Complexity      448      449    +1
=========================================
  Files            30       30
  Lines          1171     1171
=========================================
  Hits           1166     1166
  Misses            5        5

Impacted Files
Coverage Δ

src/Command/TwigCsFixerCommand.php
97.36% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix bagit rdf importing

summary
the build_metadata method isn't actually parsing anything because the "node_name" being passed into the add_metadata method is a predicate, and not a value.
e.g., the following RDF::Statement would be broken down as follows
<http://5dda1cb48e05/concern/generic_works/bbec3aa4-c5f6-434a-abae-ae8706f062e0> <info:fedora/fedora-system:def/model#hasModel> "GenericWork" .

subject: <http://5dda1cb48e05/concern/generic_works/bbec3aa4-c5f6-434a-abae-ae8706f062e0>
predicate: <info:fedora/fedora-system:def/model#hasModel>
object: "GenericWork"
therefore field_supported?(name)  always fails because field_supported('info:fedora/fedora-system:def/model#hasModel') fails.
demo
sample file
https://drive.google.com/file/d/1k7Vc3xCI7Q02nmIaU81DPwo8V6Kp8IVc/view?usp=sharing
debugging hints that might be useful later

closing the related pr for now since we have not returned to this work. if this work is picked up again, the linked pr can be reopened if desired.


Exception reported

Version: <IP_ADDRESS>; Variant: Installed; Arch: Amd64
Path: C:\Program Files\SyncTrayzor\SyncTrayzor.exe
System.Exception: Unable to find Syncthing at path C:\Users\Jonathan\AppData\Roaming\SyncTrayzor\syncthing.exe
   at SyncTrayzor.Syncthing.SyncthingProcessRunner.Start() in C:\projects\synctrayzor\src\SyncTrayzor\Syncthing\SyncthingProcessRunner.cs:line 104
   at SyncTrayzor.Syncthing.SyncthingManager.<StartAsync>d__120.MoveNext() in C:\projects\synctrayzor\src\SyncTrayzor\Syncthing\SyncthingManager.cs:line 193
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at SyncTrayzor.Utils.SafeSyncthingExtensions.<StartWithErrorDialogAsync>d__0.MoveNext() in C:\projects\synctrayzor\src\SyncTrayzor\Utils\SafeSyncthingExtensions.cs:line 17
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at SyncTrayzor.Pages.ViewerViewModel.<Start>d__39.MoveNext() in C:\projects\synctrayzor\src\SyncTrayzor\Pages\ViewerViewModel.cs:line 305
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

I think the actual problem is that Avast antivirus keeps deleting syncthing.exe?

Yep!
On startup, SyncTrayzor will replace C:\Users\Jonathan\AppData\Roaming\SyncTrayzor\syncthing.exe if it doesn't exist (downgrading it in the process). However if it's deleted after SyncTrayzor starts, that counts as deleting an application's files from under it while it's running, which it's not going to like.
Tell Avast to behave.

Hi, any update?

Well it's been working since I put it in Avast's exception list.  Can the error message be made more obvious?

Potentially. There are plenty of other files which you could delete while SyncTrayzor is running, though, and most of them I wouldn't be able to detect in time to show a nice error message.


Added beets-noimport plugin to the plugins documentation page.

Also edited the file a bit for consistency.

Forgot to pull the newest code, I'll fix this.

Great! Thanks!


ChangeFeedProcessor stops receiving change events and "Owner" set to null in lease container

Describe the bug
I have a CosmosDB SQL API database with multiple containers. 3 of the containers have a single ChangeFeedProcessor each watching for changes, each of these ChangeFeedProcessors are running in a separate task in a dotnet BackgroundService.
The issue that I'm seeing is that 2 of the ChangeFeedProcessor always work correctly. The third seems to work correctly when the application starts up, and it writes the lease to another cosmos container correctly. However after a few minutes it updates the lease container to "Owner": null in the lease container and then stops receiving changes from cosmos.
Expected behavior
ChangeFeedProcessor continues to receive change events from CosmosDB
Actual behavior
ChangeFeedProcessor stops receiving changed events from CosmosDB
Environment summary
SDK Version: <IP_ADDRESS>
OS Version: Windows 10 (19042.1237)

Owner on null means the Processor is releasing the lease.
Make sure you have a global try/catch block inside your delegate function and see if you are throwing unhandled exceptions: https://docs.microsoft.com/en-us/azure/cosmos-db/sql/change-feed-processor#error-handling


Add key hashing to Lookup Intent Parser for perf

Description:
Use hashes as dictionary keys instead of actual strings. This
reduces the size of the model.
Add utility function to handle key deserialization from JSON.
Checklist:

[x] My PR is ready for code review
[x] I have added some tests, if applicable, and run the whole test suite, including linting tests
[x] I have updated the documentation, if applicable

Codecov Report

Merging #766 into feature/lookup_intent_parser will increase coverage by 0.01%.
The diff coverage is 100%.

@@                       Coverage Diff                        @@
##           feature/lookup_intent_parser     #766      +/-   ##
================================================================
+ Coverage                         88.47%   88.48%   +0.01%
================================================================
  Files                                75       75
  Lines                              4711     4716       +5
  Branches                            893      895       +2
================================================================
+ Hits                               4168     4173       +5
  Misses                              401      401
  Partials                            142      142

Codecov Report

Merging #766 into feature/lookup_intent_parser will increase coverage by 0.01%.
The diff coverage is 100%.

@@                       Coverage Diff                        @@
##           feature/lookup_intent_parser     #766      +/-   ##
================================================================
+ Coverage                         88.47%   88.48%   +0.01%
================================================================
  Files                                75       75
  Lines                              4711     4716       +5
  Branches                            893      895       +2
================================================================
+ Hits                               4168     4173       +5
  Misses                              401      401
  Partials                            142      142


Feature/decrease entitlement over time

closes: https://github.com/trustlines-protocol/merkle-drop/issues/22
based on: https://github.com/trustlines-protocol/merkle-drop/pull/27
Only read last two commits.

I would also argue that decayedEntitlementAtTime is  confusing and ambigous, because what it returns is not decayed. entitlementAtTime has been pretty clear to me and doesn't allow much interpretation.

I would also argue that decayedEntitlementAtTime is confusing and ambigous, because what it returns is not decayed. entitlementAtTime has been pretty clear to me and doesn't allow much interpretation.

I changed it because I felt like entitlementAtTime() should return 0 if you are not entitled to anything, which is not what it does, so I wanted to emphasize that what the function does is decaying the entitlement.


Feature request: update install instructions

I spent the last several days with trial and error following the QNAP GUI instructions.  I could get the Homebridge to come up, and I could even see it in the Home App, but I could not get the Home App to connect the Homebridge accessory.
I decided to try the QNAP console instructions.  Five minutes later, everything is up and running and the accessory is connected in the Home app.
I checked the two QNAP containers and the only difference I could find is the network configuration.  The GUI instructions say to put the container in bridge mode, and that doesn't work for me.  The console instructions start the container in host mode, and that is the only difference between the working and not working attempts.
Please either

update the GUI instructions to suggest experimenting with network configs (bridge vs. host)
add a comment to the GUI instructions suggesting people try the console approach if they encounter Home APP connectivity issues

I added the info you suggested.
Thanks for feedback!


Add related posts

[related]
threshold = 80
includeNewer = true
toLower = false
  [[related.indices]]
  name = "sections"
  weight = 100
  [[related.indices]]
  name = "date"
  weight = 10

Click to see Hill for issue #20

Click to see Hill for all issues

created by Async

Added.


fix: Track graphs of item dependencies to find dependency cycles

Description
Problem*
Resolves #1122
Summary*
Adds a dependency graph to catch cases where structs will cyclically depend on one other.
For example, the program:
struct Foo {
    bar: Bar,
}

struct Bar {
    foo: Foo,
}

Will now give the following error:
error: Dependency cycle found
  ┌─ /home/user/Code/Noir/noir/short/src/main.nr:6:1
  │
6 │ ╭ struct Bar {
7 │ │     foo: Foo,
8 │ │ }
  │ ╰─' 'Bar' recursively depends on itself: Bar -> Foo -> Bar
  │

The error is still issued if these are split across separate modules.
Additional Context
Note that self-referential structs like struct Foo { foo: Foo } are not currently caught - we may need a separate check for this.
This error is also only currently possible for cyclic struct dependencies, but once this is merged I'm going to expand this to more PRs to allow for globals and type aliases as well. This would implement https://github.com/noir-lang/noir/issues/1734 as well as a similar feature to allow type aliases to reference other type aliases which is currently disallowed.
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Can you open up an issue for self referential structs?

@kevaundray there is already https://github.com/noir-lang/noir/issues/3490


Black formatter: Support showing the "problems" in the Problems window instead of formatting

A little request/question regarding the integration with black formatter in vscode.
Currently, by default, the command that vscode is running behind the scenes is:
<BLACK_PATH> --diff --quiet <PYTHON_FILE>
Although that the --diff flag is supplied, the file is still being formatted. (I guess that behind the scenes you remove the --diff flag, because black itself doesn't format the code with this flag).
Only showing the diff in the "Problems" window instead of formatting the code can be very useful, mainly in large codebases.

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

Thank you for submitting your feature request and everyone who considered it! Unfortunately this issue did not receive enough votes over the allotted time, and so we are closing the issue.


Can't "get all" from zerochan.net

It keeps saying x number of images already exist, can only download a few images and stops.

Are you logged in to Zerochan?
What tag/search are you trying to download?
Can you provide your log file?
Are you sure those images are just not already in your MD5 list? (cf faq)

I came here to report this as well.

Yes I am, including in grabber through the source options.
twisted_wonderland, official_art. Though I do want only the official art, I did try just "twisted_wonderland" to see if maybe I was putting in multiple tags incorrectly as I'm new to this software. In either case, it downloads around 20-ish files then says it got them all, when it's several hundred images for the set of two tags, and several thousand for the series alone.
I've attached it here. This is from my run of just twisted_wonderland if that matters. It seems to be failing at properly naming the results.
100% sure as this is the first time I've run the software and it's dumping to a new directory I made for collecting the images. and this is the first site I tried.
main.txt

I'll be happy to answer any other questions you may have or help in any way, just let me know. Thanks for looking into this.

@namelessentity Interesting. I just tried and could not reproduce, even with those tags. Could it have been fixed in the nightly version?
I don't remember changing anything though 🤔
I see your log has lots of

[10:01:15.656][Info] File already exists: D:\ImgbrdGrabber\twst.jpg

What filename are you using? Does it also fail when using %id%.%ext%? (I guess you're using %md5%.%ext%)

ETA: Just realized I'm not sure of the etiquette on if I should open a new bug or ride on this one. In other places they've wanted it to stay in the same place, so that's what I did, but if you'd like me to open a new bug ticket, just let me know and I'll do so.

Since it's the same issue, it's better to recycle 😄

So I just tried it again. I WAS using %md5%.%ext%. When I use %id%.%ext%, it extracts all the images perfectly. I didn't update to the nightly version before trying, for the record.

I have similar issue but in my case grabbes save file .jpg on filename template %md5%.%ext
[22:29:14.784][Info] File already exists: [d:\grabber\Yowamushi_pedal\.jpg](file:///D:/grabber/Yowamushi_pedal/.jpg)
[22:29:14.796][Info] Loading image from https://static.zerochan.net/full/12/17/1900862.jpg 1
[22:29:14.796][Info] File already exists: [d:\grabber\Yowamushi_pedal\.jpg](file:///D:/grabber/Yowamushi_pedal/.jpg)
[22:29:14.806][Info] Loading image from https://static.zerochan.net/full/10/17/1900860.jpg 1
[22:29:14.807][Info] File already exists: [d:\grabber\Yowamushi_pedal\.jpg](file:///D:/grabber/Yowamushi_pedal/.jpg)
[22:29:14.821][Info] Loading image from https://static.zerochan.net/full/09/17/1900859.jpg 1
[22:29:14.822][Info] File already exists: [d:\grabber\Yowamushi_pedal\.jpg](file:///D:/grabber/Yowamushi_pedal/.jpg)


improve install procedure

make install.py less verbose on Automatic startup
print only when needed (using run inside print will print empty line if run reported no errors)
dont run git updates from both install.py and main.py - once is enough

Seemed to be working great!

appreciated :) the double-install routine was probably due to a misunderstanding with an install issue clashSAN had for what it's worth lol
and yeah, i'd been meaning to remove those init messages and newlines for a while now, just kept getting put on the backburner


Can't get working with Dispatch and therefore Neomake

Trying to get this.
Have installed those plug-ins, except I working with Ruby, and I'm using the following config:
nmap <silent> <Leader>tn :TestNearest<CR>
nmap <silent> <Leader>tf :TestFile<CR>
nmap <silent> <Leader>ts :TestSuite<CR>
nmap <silent> <Leader>tl :TestLast<CR>
nmap <silent> <Leader>tv :TestVisit<CR>

let test#strategy = "neomake"

if filereadable('dip.yml')
  function! DipTransform(cmd) abort
    return 'dip '.a:cmd
  endfunction

  let g:test#custom_transformations = {'dip': function('DipTransform')}
  let g:test#transformation = 'dip'
endif

This maps to dip which allows me to run commands in Docker as though they were local.

Running with another strategy I get output but I'd rather get this working with Neomake.
No idea what's going on. Hopefully someone can help.

https://github.com/janko/vim-test/pull/425

Not sure why but removing bundle exec with let g:test#ruby#bundle_exec = 0 seems to fix # problem with RSpec.

Trying out with local env now to compare performance.
Dispatch doesn't recognise any combination when running Minitest (see https://github.com/tpope/vim-dispatch/issues/291).
Also running RSpec with bundle exec means for some reason the files don't link up for Neomake.
In summary, Ruby test runners with Dispatch and Neomake don't work. Not sure where the problem is though and I need draw a line fairly soon and revert to running tests in a terminal.

Exhausted my options so going to switch to another strategy for now.

What is the test command that gets generated by vim-test, and what is the Vim compiler you expected Dispatch.vim to activate? If you're using Neovim, you can see the test command printed out in the terminal window name, while for Vim it should be printed on the shell.

Test commands for RSpec will either be bundle exec rspec … or ./bin/rspec … depending on the context. Dispatch picks up the latter OK but not the former. However if I run Dispatch -compiler=rspec … or add bundle exec to Dispatch's compilers, they both work.
Think specifying the compiler's probably the most concise. Maybe vim-test should send this to improve reliability?
With Minitest this was actually partially working, in the same way RSpec is now, when everything was running through Docker but now I moved to local dev it doesn't seem to matter what I do, it doesn't work. The commands are similar except bundle exec ruby -Itest … and ruby -Itest …. Neither of these work with Dispatch (see issue mentioned above).
Seems first sub-issue could be solved by vim-test. Second could be a problem with Dispatch but no idea why it would partially work with Docker and not at all with local env.

@janko the last piece to get vim-test working with NeoMake strategy is here.
Have a hunch vim-test should be sending additional args here.

Been a while since I've looked at this but think the problem was related to this.
Looks like Minitest and RSpec are both working now, closing issue.


Train in spaces

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Replace /posts with list of posts at /@:username

Update styling of user posts lists

Remove /posts url [WIP]

Re


Allow rowsMax to equal rows in TextField

Resolves: #2311

@kevlened Thanks :+1:. The travis fail. It looks like a regression with the react babel plugin.


Add Solr operator site

The site really needs a first apache release (v0.3.0), so it is designed around that being available. Some of the links won't work until that is available.
It currently looks A LOT like the Solr website, I would like to change the colors eventually and possibly have a separate (but related) logo.

Also, I am unsure whether the project needs two SECURITY pages - perhaps the main one can also cover CVEs for the operator, the Dockerfile etc?
A separate NEWS section is perhaps justified for operator, but i'm not 100% convinced? Like the news about operator donated to Solr project seems to me a better fit on the main Solr News page.

I think this "OPERATOR" menu option should come before the download button?

Yeah, I had a hard time with this. I can put it before the Download button.

Once on the sub site....

Completely agree here. Definitely think we should use a different color. Not sure about stacking the menu's though. If you had an idea for that, I'd like to see it for sure!
Will play around with the colors today though and see if something sticks.

Also, I am unsure whether the project needs two SECURITY pages

Fair enough, easily removed.

A separate NEWS section is perhaps justified for operator, but i'm not 100% convinced?

I think it warrants its own news section, but I could be convinced otherwise. I foresee entries for compatibility warnings with new Kubernetes versions, and things like that.

This is one way - different color and a button to the right to get you back. In this screenshot I also removed the SECURITY, PROJECT and DOWNLOAD menus, then it starts to be more distinct already. I'm not suggesting that green color, but just an example for my thinking... And I'm not a designer :)

Ok, I've changed the color to an exact mix of the Solr Color and the Kubernetes Color, and I think it works quite well.
I also added the SOLR TLP button, and removed some things from the menu. For the security, so far I just removed the button. Need some more effort to remove all the places that had the new security feed.
Still think we should have a related but separate Logo for the project, will think on that a bit.

Here you go :) I'm not sure it is advisable to rip it off even if the k8s logo is CCBY licensed :)

Do you have other ideas?

Some other operator logos

Wow nice research. I had an idea of using the kubernetes logo and turning it into sun beams, to mimmick the solr logo. My girlfriend offered to help me mock something up. So we'll see where that goes 😃

Wow nice research. I had an idea of using the kubernetes logo and turning it into sun beams, to mimmick the solr logo. My girlfriend offered to help me mock something up. So we'll see where that goes 😃

A rudder is not that different from sun-beams so should be room for some creativity here. Guess the hexagon shape and the rudder are elements that would hint to k8s. Then you also have the spark from the operator framework logo... A spark from the sun???

That's actually really nice, though it might be weird since we use kubebuilder, not the operator framework.

Haha - true. The two are slowly merging to become one, aren't they? But better stick with k8s elements I guess :) We don't need to have a separate logo for the first versin of the sub page though..

@janhoy, what is the typeface that Solr uses? It looks like you've used it since you added "Operator" in the same lettering.

Check out the style guide at https://solr.apache.org/theme/images/identity/Solr_Styleguide.pdf

I merged main branch into your feature branch and tested the site. The security banner is not triggered on the Operator site, probably because it is looking for solr/security news in the 'articles' variable, which holds only operator news items :)

Weirdly I tried it locally and it looked good to go. I notice that the "Operator" menu item is still there for you, so I'm not sure you are using the latest from my branch.

Do you think this is good to go? (Seeing as the release will be announced tomorrow hopefully)

Perhaps this PR should also add a new section to Solr's frontpage, telling the world about the Solr operator. It could be a "marketing" kind of text, designed to let people know that it is there. And it would link to the sub-site.

This was an earlier comment I had. Any thoughts? Would be nice with some k8s graphics to draw attention to the sub-project.

Sorry for not responding to that, I think it would be a very good thing to add! I'm fine waiting to merge if you want to include that first, but I also think it can be done separately.

It can definitely be done separately - not indending to hold up the release, nor to sit up all night with photoshop :) Also makes sense to wait for the logo vote, and then promote it some more. Also perhaps collaborate with ASF on an official blog post about the new project.

Also makes sense to wait for the logo vote, and then promote it some more. Also perhaps collaborate with ASF on an official blog post about the new project.

Very much agree with both.


SHOW FULL LINKS |  fixes #89

Displays full links instead of default names.

--
PR for fixing #89

@mastrero How links will help the user?
It's looking simple and good without links.

It's not great user experience to have same name for all links.
For example, all links in Website section has Open as default name, But user will only know the website only after clicking.
However my placing website names, the user get to know which website it is. Hence improving the accessibility.


hide map on high zoom level

Please note: issues related to or caused by osmbonuspack will be closed with a
suggested to open the issue at https://github.com/MKergall/osmbonuspack
(feel free to delete whatever doesn't apply)
Issue Type
[X] Question
[ ] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
Description and/or steps/code to reproduce the problem
I use only offline map with max zoom level 9.
Is possible hide map and show only polylines when zoom is greater of 9?
Environment
If it's a bug, version(s) of android this affects:
All
Version of osmdroid the issue relates to:
5.6.5

If you set your own tile provider chain when you hit zoom 9, then reset to make whatever your business rules are, it should be possible.

On attach of fragment I load file with this code:
        File[] list = f.listFiles();
        if (list != null) {
            for (int i = 0; i < list.length; i++) {
                final File fileTemp = list[i];
                if (fileTemp.isDirectory())
                    continue;
                String name = fileTemp.getName().toLowerCase();
                if (!name.contains("."))
                    continue;
                name = name.substring(name.lastIndexOf(".") + 1);
                if (name.length() == 0)
                    continue;
                if (ArchiveFileFactory.isFileExtensionRegistered(name) && name.equals("mbtiles")) {
                    try {
                        OfflineTileProvider tileProvider = new OfflineTileProvider(new SimpleRegisterReceiver(getActivity()), new File[]{fileTemp});
                        readZoomLevel(fileTemp);
                        mapView.setTileProvider(tileProvider);
                        mapView.invalidate();
                        return;
                    } catch (Exception ex) {
                        ex.printStackTrace();
                    }
                }
            }
        }

can you help me with other indication?

You can subclass OfflineTileProvider  and override getMapTile() accordingly (e.g.: return null if zoom is greater than 9).


feat(light): autolight light spell items & lightsource effects

resolves #303
Also adds lightSource predefined effects, and mappings for defining light sources. The effects are sending messages to chat when started & doused, but I have not gotten them hooked up onto the Light Tracker UI yet.

I'll get the lighttracker side of things working before merging this...


👷 Refactor ➾  Replace hand-written Michelson syntax-highlighting grammar file with machine-generated candidate

Replaces hand-written michelson/tmLanguage.json with machine-generated version, which should fix the incorrect regex pattern for bytes literals.
TODO: verify that the replacement is feature-equivalent
🌮 Taqueria PR
🪁 Description
This PR is intended to fix #1730 as well as demonstrate the viability of serving machine-generated grammar files with each Michelson update.
The replacement version is a candidate which may not offer the same level of functionality as the manual version, as some domain-specific knowledge may be infeasible to program into the grammar-file compiler.
🪂 Pre-Merge Checklist (Definition of Done)
🚦 Required to merge:

[x] ⛱ I have completed this PR template in full and updated the title appropriately
[x] ⛵ My code builds cleanly, and I have manually tested the changes
[ ] 🏄♂ Another team member has built this branch and done manual testing on the change
[ ] 🏖 New and existing unit tests pass locally and in CI
[ ] 🔱 The test plan has been implemented and verified by an SDET
[ ] 🦀 Automated tests have been written and added to this PR
[ ] 🐬 I have commented my code, particularly in hard-to-understand areas
[ ] 🤿 Corresponding changes have been made to all documentation
[ ] 🐚 Required changes to the VScE have been made
[ ] 🪸 Required updates to scaffolds have been made
[ ] 🚢 The release checklist has been completed

🛩 Summary of Changes
The only change is an in-place substitution of the contents of the file located at taqueria-vscode-extension/syntaxes/michelson/tmLanguage.json. The new contents were machine-generated by the codec-generator pipeline based on the protocol-specific (Lima-based) type-encoding for the script.prim schema.
The process for generating this file at present and in future is not currently portable/flexible enough to automate. Future work should be done, pending the approval of this PR, to increase the ease with which new version-specific grammar files can be sourced into the repository without requiring manual PRs.
🎢 Test Plan
As this PR affects only the UX of editing michelson source, the primary testing strategy proposed is to visually compare the behavior of the old grammar file and the new one across existing and testing-oriented examples of michelson source files.
🛸 Type of Change

[x] 👷 Refactor ➾  Replace hand-written Michelson syntax-highlighting grammar file with machine-generated candidate

I have read and agree to the CLA

Excellent


#1907 root event query tuning

Closes #1907
This PR implements a more efficient way of retrieving root events for a project/service. Previously, this has been done using an expensive distinct query (to retrieve all available keptnContexts) in the events collection of a project with a subsequent query for each of the returned result.
With the new approach introduced in this PR, I have added a dedicated collection for the root events for each project (one collection per project). This makes retrieving all root events for a project easy, since we can use the same filtering logic as for other queries without using distinct queries.

I'll give the image keptn/mongodb-datastore:bug.1907.20200623.1348 a try.


Support genus names with multiple hyphens; closes #203

This PR addresses issue #203 by supporting the parsing of genus names containing more than one hyphen. It allows for upper- or lower-case subsequent segments (with appropriate quality warnings).

This PR has been updated to support genera with one or two hyphens only (and not more).


conda  parameter error 'conda: error: unrecognized arguments: --no-capture-output'

When I use this command，‘docker-compose up'，there was a mistake. I checked my version of conda, it has the--no-capture-output parameter, I don't know why it can't recognize this parameter when I run this command.
Attaching to matcher-backend-1, matcher-database-1, matcher-frontend-1
matcher-database-1  |
matcher-database-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
matcher-database-1  |
matcher-database-1  | 2023-11-14 17:17:40.592 UTC [1] LOG:  starting PostgreSQL 13.5 (Debian 13.5-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
matcher-database-1  | 2023-11-14 17:17:40.592 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
matcher-database-1  | 2023-11-14 17:17:40.592 UTC [1] LOG:  listening on IPv6 address "::", port 5432
matcher-database-1  | 2023-11-14 17:17:40.595 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
matcher-database-1  | 2023-11-14 17:17:40.598 UTC [26] LOG:  database system was shut down at 2023-11-14 17:13:13 UTC
matcher-database-1  | 2023-11-14 17:17:40.601 UTC [1] LOG:  database system is ready to accept connections
matcher-backend-1   |
matcher-backend-1   | usage: conda [-h] [-V] command ...
matcher-backend-1   | conda: error: unrecognized arguments: --no-capture-output
matcher-backend-1 exited with code 1
matcher-frontend-1  | usage: conda [-h] [-V] command ...
matcher-frontend-1  | conda: error: unrecognized arguments: --no-capture-output

Hi @tanyingjia ,
Thanks for reporting this issue.
I think the problem may be caused by the version of the condaforge/miniforge3 docker image that you are currently using. The conda errors you are seeing are within Docker containers. If you checked your version of conda outside of the containers, the conda version would not necessarily be or act the same.
I tried to fix this problem by specifying tags for the condaforge/miniforge3 base images that Matcher uses. That way, you and I can both try the same image versions to diagnose whether this is the issue. Could you please give the below steps a try, and let me know what happens? When I run the below steps, the matcher application works as expected.

Stop your currently running matcher application and remove the db volumes by running docker-compose down --volumes in the matcher directory. Note this will delete your current matcher DB
Get the updated code, which now has tagged base images: git checkout -b hotfix/conda-image-tag origin/hotfix/conda-image-tag
Build new Matcher docker images starting from the tagged base images: docker-compose build --no-cache
Launch and test the application like normal, with docker-compose up


Facet sorting inoperative

The facet sorting has not been connected up to the new facet display. I pushed the changes before realising this was not complete. Will update.

fixed. forgot to update ticket


command 'vscode.previewHtml' not found

https://github.com/Microsoft/vscode/issues/62630

@aryaminus This is a known issue with the deprecated previewHtml which has been replaced by the WebView API. Here's some snippets from an extension I've updated lately that uses the WebView API to display the JS flowchart: Create WebView / Update WebView Content. I hope this helps to update the Extension.
Meanwhile, @atian25, you can use this extension, as Flowchart is now supported for .js files

This is still an issue which needs to be fixed in this plugin.
@aryaminus Can you please fix this.

Will fix it in a week's span. PRs appreciated


Unable to run workspace-optimizer

Fresh Ubuntu machine on Hetzner with Rust and git.
root@juno:~/cw-plus# docker run --rm -v "$(pwd)":/code   --mount type=volume,source="$(basename "$(pwd)")_cache",target=/code/target   --mount type=volume,source=registry_cache,target=/usr/local/cargo/registry   cosmwasm/workspace-optimizer:0.12.6
1.60.0-x86_64-unknown-linux-musl (default)
cargo 1.60.0 (d1fd9fe2c 2022-03-01)
Building artifacts in workspace ...
Found workspace member entries: ["packages/*", "contracts/*"]
Package directories: ["contracts/cw1-subkeys", "contracts/cw1-whitelist", "contracts/cw1-whitelist-ng", "contracts/cw1155-base", "contracts/cw20-base", "contracts/cw20-ics20", "contracts/cw3-fixed-multisig", "contracts/cw3-flex-multisig", "contracts/cw4-group", "contracts/cw4-stake", "packages/controllers", "packages/cw1", "packages/cw1155", "packages/cw2", "packages/cw20", "packages/cw3", "packages/cw4", "packages/multi-test", "packages/storage-macro", "packages/storage-plus", "packages/utils"]
Contracts to be built: ["contracts/cw1-subkeys", "contracts/cw1-whitelist", "contracts/cw1-whitelist-ng", "contracts/cw1155-base", "contracts/cw20-base", "contracts/cw20-ics20", "contracts/cw3-fixed-multisig", "contracts/cw3-flex-multisig", "contracts/cw4-group", "contracts/cw4-stake"]
Building "contracts/cw1-subkeys" ...
   Compiling cw1-subkeys v0.15.0 (/code/contracts/cw1-subkeys)
error[E0599]: no variant or associated item named `response_schemas` found for enum `cw1_subkeys::msg::QueryMsg` in the current scope
  --> contracts/cw1-subkeys/src/bin/schema.rs:8:5
   |
8  | /     write_api! {
9  | |         instantiate: InstantiateMsg,
10 | |         execute: ExecuteMsg,
11 | |         query: QueryMsg,
12 | |     }
   | |_____^ variant or associated item not found in `cw1_subkeys::msg::QueryMsg<_>`
   |
   = note: this error originates in the macro `write_api` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0599`.
error: could not compile `cw1-subkeys` due to previous error
thread 'main' panicked at 'assertion failed: error_code.success()', src/main.rs:77:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
root@juno:~/cw-plus#

Before you post issue, make sure you are using latest version of packages.
Use 0.12.8.

@ueco-jb ive tried on multiple commit hashes, as I want to verify the checksums given in the releases match

This doesn’t seem correct.
I need to run the version of the workspace-optimizer that was used to create a release at a specific commit.
For contract releases 0.15.1 and 0.15.0 I assumed that was 0.12.6 as per the readme.
Was 0.12.8 used to generate the checksum files for the last few releases?

Was 0.12.8 used to generate the checksum files for the last few releases?

Yes, it was. We forgot to update the README. Our bad!


Integration tests for upgrades

Inspired by the error line 1.966: unknown field name "input" in pps.Input that some customers saw upgrading from 1.4.5 to 1.4.6.
One way to avoid problems like that would be to run a test harness that tries to upgrade a pachyderm cluster. If the upgrade test fails (e.g. can't run pipelines after upgrading) we should make sure to include a migration script with the release.

stale


MMR implementation

[!IMPORTANT]
This PR implements Maximal Marginal Relevance (MMR) in document search, adding mmr_strength parameter and integrating it into search logic and API.

Behavior:

Introduces mmr_strength parameter in BaseDocSearchRequest in Docs.py to control MMR behavior.
Implements MMR logic in maximal_marginal_relevance() in mmr.py.
Integrates MMR in search_user_docs() and search_agent_docs() in search_docs.py.

Search Logic:

Modifies search_docs_by_embedding() and search_docs_hybrid() to adjust k based on mmr_strength.
Adds embedding field to Snippet model in Docs.py and models.tsp.

Dependencies:

Adds simsimd to pyproject.toml for optimized cosine similarity calculations.

Misc:

Updates OpenAPI spec in openapi-1.0.0.yaml to include mmr_strength and embedding fields.

This description was created by  for 75db5a07d9936e9468f5ff8bec57b781dab69a6a. It will automatically update as commits are pushed.

Need to:

[ ] update typespec
[ ] Regenerate code
[ ] Fix failing tests


Error CodeigniterAdapter on tag 2.0.0

I use php 5.6 for my old project, and composer choose package v2.0.0.
I get the error on CodeigniterAdapter.
$query = "Select count(*) as rowcount from ($query)t";
$data = $this->CI->db->query($query, $query->escapes)->result_array();

I know its fixed on v2.0.1. But it require php 7.*.
I want to fix that. But i dont know how to commit to the older tag.

You can install 1.7.1 version by:
composer require ozdemir/datatables:1.7.1


Increment version for kusto releases

Increment package version after release of Azure.ResourceManager.Kusto

API change check
API changes are not detected in this pull request.


Extend 'sidebar-toggle' event to force open state

This extends the 'sidebar-toggle' event of the AppSidebar component, so the opening state of the sidebar can be forced (not just toggled). Done by passing a boolean argument when firing the event. Harmonizes the signature / behavior with the  'app-loading-mask-toggle' event, which does similar things.

Thanks for the review @JakobMiksch. I am going to merge...


feat: add profile for public organization view

Add a section to the public profile of the Hapag-Lloyd organization and explain how to become a member.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Feature add pheno tab to pqtl table

This is no longer needed - this feature is coming as part of the other PR.


Allow dates backlinking to Daily Notes

🔖 Feature description
I would like use due dates as backlinks to daily notes or as inline dataview fields which will allow me to

use dataview to query tasks based on backlinks

I'm aware that I can still query tasks by date even without backlinks, but backlinks provide more accuracy.

Backlinking helps in connecting my daily notes with other notes - which eventually will help in forming an accurate second brain.
This helps in generating an accurate local or global graph

✔ Solution
I would suggest to add a configurable due date format in the settings, so that the user can customize it based on their needs. For example, this is how I like my tasks: - [ ] Test Obsidian Task [due:: [[2023-02-17]]].
So I would like to configure my due date format to be [due:: [[YYYY-MM-DD]]]

@AnweshGangula this seems to be a nice idea. Just curious about couple of points:

do you consider other fields (scheduled, done, ...) to have the dates as links? or it's just that you use only due in your workflow?
why your examples are [due:: [[YYYY-MM-DD]]] and not due:: [[YYYY-MM-DD]]?

On a side note, the date format is a separate discussion/issue.


Add: Partially Build r2/v3

Went through to verify how everything is working.
layout IDs on the From/To page is a critical component within the animation process.


Scripts: Add error-handling to generator scripts

What changed?
Currently the errors inside the plop generator are "swallowed", we are not seeing them in the console (which caused us some headaches while trying to add the new app-scenes template).
This PR is fixing this by logging the generator errors to the console.

Aaa, true! You are right, thanks 👍


SetText() not always rendering new value

Say that there's a text field named "fieldname" that has the value "0".
I now change that "0" to a "1":
lwf.SetText("fieldname", "1");
When calling lwf.GetText("fieldname") it does in fact return "1", so the value is stored successfully, however it is not updated visually.
If I continue to change the valule from 1 to 2 to 3 etc nothing updates visually until 10 is hit. Then it reflects the actual value. But 11, 12 etc is not reflected.
Seems like it only renders the new value of the text field if it has changed in string length?
If I change the x/y position of the MovieClip that contains the textfield it also successfully displays the actual value in the text field.
I assume the problem is just that you've forgotten to set the text field as being "dirty" when a new value is received, unless the new value has a different string length. I haven't exactly worked out how to workaround this problem yet though, I had hoped I could just set the root movie's x property to the same as it was previously but that doesn't make LWF update the visuals unfortunately.

Seems like the problem is in lwf_combinedmesh_text.cs
Inside:
[code]public override void Render(Matrix matrix, ColorTransform colorTransform, int renderingIndex, int renderingCount, bool visible)[/code]
There is the followng:
[code]int z = renderingCount - renderingIndex;
if (m_z != z) {
m_updated = true;
m_z = z;
}[/code]
If I remove the length check the text field works as it should:
[code]int z = renderingCount - renderingIndex;
//if (m_z != z) {
m_updated = true;
m_z = z;
//}[/code]
I don't know why that check is there in the first place (trying to save performance?) but without it things actually work like you'd expect them to. I suggest someone that has more insight than me in LWF removes the check from the source code.

Until this is fixed in LWF here's a workaround:
lwf.SetText(textInstanceName, newText +"!");
lwf.ForceExecWithoutProgress();
lwf.Render();
lwf.SetText(textInstanceName, newText);

This will make sure that the current text value is shown the next time LWF is rendered.


Execute on a Raspberry Pi

I want to know if there is a way to execute on a Raspberry Pi 4

It looks like I can add a build target for armv7l in order to produce a binary that should work on raspberry pi's.  I'll give it a shot tomorrow.

That's cool! Thanks!!

Can you try this build? https://github.com/LN-Juggernaut/juggernaut-desktop/releases/download/0.1.1/Juggernaut-linux-armv7l-v0.1.1.AppImage

Can you try this build? https://github.com/LN-Juggernaut/juggernaut-desktop/releases/download/0.1.1/Juggernaut-linux-armv7l-v0.1.1.AppImage

It's working!!!!
Thanks!!

awesome!


Allow minreal to work with static gain StateSpace objects

Finding this bug is what provoked #107, which this builds on.
This takes the simple option of doing nothing for a static gain.  I didn't investigate the slycot.tb01pd call at all; perhaps it can take a static gain, and there's some other bug lurking in minreal code.

Coverage increased (+0.06%) to 76.065% when pulling fb1e90510b99cefa788a5a40bf5c71cc192fa0ec on roryyorke:ry-ss-static-minreal into d0528fd1c6a607b480483ed1f344a3c98e8ce686 on python-control:master.

Pull request #110 subsumes this one.


The command line  could not be closed while testing the "" by using the NEW release version of TRACI4MATLAB

Hi, Andres Acosta
Thanks for updating  the API!
There is some problem while I was trying to run the test_traci. m after I downloaded the new release version of TRACTI4MATALB.
The problem is shown below:

The other two test examples could run very as the description in the PDF document.
Could you give some suggestion about the problem.

Thanks for pointing out this issue. Changing the port number on line 21 of the traci_test.m file to 8813 should work:
sumoArgs = '--remote-port 8813 --xml-validation never&';
Best Regards.

Andres Acosta, thanks so much!
The test_traci. m work well after modifying the port number!
Best regards!

Dear Jane Cheung.
I also updated the test file.
Best Regards.


Make upcoming Clippy 1.40 happy

The Clippy version shipped with the upcoming 1.40 release will have a few new complaints about our build scripts which this commit fixes.

Pull Request Test Coverage Report for Build 1254

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

Totals

Change from base Build 1250:
0.0%

Covered Lines:
3182

Relevant Lines:
3343

💛  - Coveralls

@Dylan-DPC I had to force-push without changes as one AppVeyor job had a spurious failure again so the review status was reset. :-(

bors: r+

@adamreichold please update the branch to the latest master

@adamreichold please update the branch to the latest master

Rebased onto current master. Sorry for forgetting to tick the "Allow edits from maintainers." checkbox.

@kpp I updated the branch but I cannot reopen the PR because I accidentally deleted the branch before that. Can you or should I create a new MR?

Sorry for forgetting to tick the "Allow edits from maintainers." checkbox.

I try not to use "Update" button because it makes me co-author which is unfair (as for me).

Can you

I can't

Created #405 as a replacement.


[release-v0.26] Remove the GA from upstream

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>as per title
/assign @pierDipi

/lgtm


add saveable option to do nothing for tasks

Took a quick stab at adding another saveable option for tasks. This should use cancel as a saveable option, but this may not be ideal.

This PR fixes #90478

 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.:x: shogerr sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR, however already pushed a fix for this. Sorry!


README: invalid ./kevm prove spec location and nonexistent argument of ./kevm test

In current README.md,
./kevm prove tests/proofs/specs/vyper-erc20/totalSupply-spec.k the location should be tests/specs/......
And also I do not see the entry point of ./kevm test in script, do ./kevm still support the usage of ./kevm test ... ?
(ex: ./kevm test tests/ethereum-tests/VMTests/vmArithmeticTest/add0.json in README.md)
Originally posted by @chenIshi in https://github.com/kframework/evm-semantics/issues/159#issuecomment-493839554

./kevm test is no longer available, all testing is handled in the Makefile.
I've updated https://github.com/kframework/evm-semantics/pull/356 to include these fixes.


[SPARK-14720][SPARK-13643][WIP] Remove HiveContext (step 1)

What changes were proposed in this pull request?
In Spark 2.0 we will have a new entry point for users known as the SparkSession. This class will handle the lazy initialization of the Hive metastore if the user runs commands that require interaction with the metastore (e.g. CREATE TABLE). With this, we can remove the HiveContext, which is an odd API to be exposed to Spark users.
This patch doesn't fully remove HiveContext but does most of the work. A follow-up patch will actually delete the file itself. I've left all the variable naming and any further refactor for later.
How was this patch tested?
Jenkins.

Test build #56166 has started for PR 12485 at commit ce1214d.

Test build #56170 has started for PR 12485 at commit 6019541.

Test build #56174 has started for PR 12485 at commit 75d1115.

Test build #56166 has finished for PR 12485 at commit ce1214d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56166/
Test FAILed.

Test build #56170 has finished for PR 12485 at commit 6019541.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56170/
Test FAILed.

Merged build finished. Test FAILed.

Test build #56174 has finished for PR 12485 at commit 75d1115.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56174/
Test FAILed.

Merged build finished. Test FAILed.

Test build #56249 has started for PR 12485 at commit 0d7309b.

Test build #56251 has started for PR 12485 at commit 575fd47.

Test build #56254 has started for PR 12485 at commit bc35206.

Test build #56251 has finished for PR 12485 at commit 575fd47.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56251/
Test FAILed.

Merged build finished. Test FAILed.

Test build #56249 has finished for PR 12485 at commit 0d7309b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56249/
Test FAILed.

Test build #56254 has finished for PR 12485 at commit bc35206.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56254/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56271/
Test FAILed.

Merged build finished. Test FAILed.

Test build #56273 has started for PR 12485 at commit 303f991.

Test build #56276 has started for PR 12485 at commit b3d23fa.

Test build #56276 has finished for PR 12485 at commit b3d23fa.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait PartitionCoalescer
class PartitionGroup(val prefLoc: Option[String] = None)
trait ObjectProducer extends LogicalPlan
trait ObjectConsumer extends UnaryNode
case class DeserializeToObject(
case class SerializeFromObject(
case class AppendColumnsWithObject(
case class AppendColumnsWithObject(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56276/
Test FAILed.

Test build #56278 has started for PR 12485 at commit ddc752a.

Test build #56273 has finished for PR 12485 at commit 303f991.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56273/
Test FAILed.

Merged build finished. Test FAILed.

Test build #56278 has finished for PR 12485 at commit ddc752a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56278/
Test FAILed.

Test build #56303 has started for PR 12485 at commit 8bf1236.

Test build #56305 has started for PR 12485 at commit 74b105e.

Test build #56303 has finished for PR 12485 at commit 8bf1236.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56303/
Test FAILed.

Test build #56305 has finished for PR 12485 at commit 74b105e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 class Timer(val iteration: Int)
  case class Case(name: String, fn: Timer => Unit)
trait ScalaReflection
trait CheckAnalysis extends PredicateHelper
abstract class SubqueryExpression extends Expression
abstract class PredicateSubquery extends SubqueryExpression with Unevaluable with Predicate
case class InSubQuery(value: Expression, query: LogicalPlan) extends PredicateSubquery
case class Exists(query: LogicalPlan) extends PredicateSubquery
case class FilePartition(index: Int, files: Seq[PartitionedFile]) extends RDDPartition
abstract class OutputWriterFactory extends Serializable
abstract class OutputWriter
case class HadoopFsRelation(
trait FileFormat
case class Partition(values: InternalRow, files: Seq[FileStatus])
trait FileCatalog
class HDFSFileCatalog(
  case class FakeFileStatus(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56305/
Test FAILed.

Hey @andrewor14 - I took a quick look at this. Shouldn't we move the sessionstate stuff in its own pr since it would be easier to get that in and also easier to review?

Test build #56374 has started for PR 12485 at commit 9422128.

Test build #56382 has started for PR 12485 at commit 6e3c366.

Test build #56374 has finished for PR 12485 at commit 9422128.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56374/
Test FAILed.

Test build #56382 has finished for PR 12485 at commit 6e3c366.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56382/
Test FAILed.

Merged build finished. Test FAILed.

retest this please