Exiting LED programming mode, does not light LEDs

@jacoburge I got my pads, thanks, looks good so far.
I haven't tried my changes yet, I'll get to that shortly, after I play a bit.
 I haven't looked at the code yet.
Yes programming mode is dangerous...I lost the above, Undo saved the day :|

!!! Warning !!!   When in the programming modes, TouchPad takes control of your keyboard, this could EDIT or DELETE text or files if you leave this window.   !!! Warning !!!
Now in LED program mode, for command set 4
Touch LEDs to toggle them and swipe down when complete

Hi Michael, glad to hear you got your TouchPad.  The blank display after LED programming is intended.  The LED patterns are really intended for identifying the current mode on startup/switching modes.  This is why they extinguish on the first keypress.  Since the pattern has just been programmed you know what mode your in so displaying it isn't necessary.

OK not a bug, then how about a new feature?
If you were paying attention you'd know which command set you were on.
But if you come back after getting a coffee and the light is pulsing and just want to exit, it would be a handy reminder.
It can't hurt anything, more info is always handy.
I'll have a look at the code some time.

I will implement this at some point, same for the key program mode.


Developer View

Describe the feature
I've come to realise that I rely on /api-docs/ to retrieve things like department and division IDs as I use these within our scripts.
I think it would be beneficial if there was a way to view this in the /admin/values/ screen so that I don't need to run API queries to get ID references. This could be hidden behind a user option if you feel it will clutter normal views.
The Unit and Civilian sections both put the ID in the URL so its much easier to retrieve when viewing them.
Additional Context
No response

I’m not sure what you mean

I’m not sure what you mean

For example divisions:

I need the division ID for "Command & Control" but I cannot view this quickly here, I would need to go to the API and retrieve the ID which is: ckxjneaub6457s41hao6czt39

Ahh, like that. I could show the id no matter what tbh? It doesn’t have to be behind a dev flag

Ahh, like that. I could show the id no matter what tbh? It doesn’t have to be behind a dev flag

Yeah that's great I just didn't know if you had any reservations about cluttering the table/UI. :D


Build for Mac and Linux

Build binaries for Mac and Linux
Test if it works on both

Hello, while I was trying to set up the project locally I noticed Winsound isn't compatible with Linux or Mac (I use MacOS) so could I go ahead and make changes in the project to check the platform and if it is not windows then use an alternative of Winsound.

@memyselfandglitch  yes that would be great!

I am kind of struggling with the threading part. Although it works really well on Windows on Mac there are a lot of issues related to the accessibility of keyboards and key blocking. Is it alright if I make the MacOS part synchronous and Windows would still continue to function the way it is. I have tried to solve it through every way I can think of.

Is it alright if I make the MacOS part synchronous and Windows would still continue to function the way it is.

Yes. @memyselfandglitch

I am on Linux and the error in threading is coming because flaskwebgui can't the browser command as specified in site-packages/flaskwebgui.py, a workaround could be making soft link of browser command to the respective location in flaskwebgui.py. Keyboard is causing error as it requires sudo a possible workaround would be using pynput module.  You can checkout some changes that I did.

@memyselfandglitch I am on Linux and the error in threading is coming because flaskwebgui can't the browser command as specified in site-packages/flaskwebgui.py, a workaround could be making soft link of browser command to the respective location in flaskwebgui.py. Keyboard is causing error as it requires sudo a possible workaround would be using pynput module.  You can checkout some changes that I did.

@memyselfandglitch @datavorous how much progress is there on mac, i can help in a few small things. I'm on an old version of mac (10.15 catalina) so that can help for accessibility across multiple mac versions


HttpsRedirectionMiddleware will not redirect to HTTPS if no port is available

Discussion for: https://github.com/aspnet/Announcements/issues/301

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


Windows 10 CUDA illegal address

When building a release build in Windows 10 with Visual Studio 2017, there are CUDA illegal address errors at runtime.
The errors have been reproduced on @jeremad's machine (GPU: ?) and on @w-m's machine (GTX 980 Ti). Latest graphics drivers are used.
The errors appear when building with CUDA 10.0 and with 10.2.
CUDA 9.2 can't be used, as it is not compatible with the latest Visual Studio 2017 compiler.
Stitching is fine when running a debug build with the same configuration, on the same machine.
The first error that is thrown (uncomment https://github.com/stitchEm/stitchEm/blob/master/lib/src/cuda/error.cpp#L20 and look at the log, not the first error dialog) seems to always be cudaEventSynchronize:

deviceEvent.cpp (24)
deviceStream.cpp (90)

The following CUDA error locations are somewhat random and can be disregarded I think, as the illegal address thing seems to be unrecoverable and is not purged after it's thrown.
Error is thrown both in Studio and Vahana VR.

Some ideas:

try stitching something on the command line (no OpenGL) - bug persists?
try CUDA memory check tools (NSight memory checker?) with videostitch-cmd invocation

Delay load was already disabled in my builds, due to just using CUDA backend (and not OpenCL).
Stitching a simple project on the command line in Release mode fails with the same error -> not an OpenGL issue.
Unit tests in debug mode failing: AutoCropTest and ControlPointConnectivityTest (issue with working directory?).

The following tests FAILED:
16 - ControllerInputFramesTest (Failed)
20 - DrawNumberTest (Failed)
22 - GridTest (Failed)
25 - InputTest (Failed)
51 - StitchOutputTest (Failed)
54 - MappingTest (Failed)
59 - UnpackTest (Failed)
60 - VoronoiTest (Failed)
67 - BlurTest (Failed)
68 - DownsamplingTest (Failed)
69 - FlowBasedBlendingTest (SEGFAULT)
71 - PyramidTest (Failed)
72 - ReduceTest (Failed)
73 - RenderTest (Failed)
74 - SamplingTest (Failed)
75 - SeamTest (Failed)
76 - SpaceTransformTest (Failed)
77 - ProcessorsTest (Failed)
Errors while running CTest
Some failing by not creating the correct output, many failing with the same errors (Illegal address / Launch failure).

Some GPU tests are passing, like StreamTest and SynchroTest. Even running a simple kernel works, SimpleKernelTest passes as well. Ooof...

Fixed through #65.


v0.3.2 - Final Fix extension versions + Fix PhpSpec 2 dependency v0.3.2 + Fix Minimum stability

This PR fixes :

Extension versions (previous setting would still install 0.4.1+ unless specified manually.
The phpspec <3.0 somehow slipped as I was meaning to set it to ~2.0.
Set minimum-stability to stable as this setting would only messup testing of packages while developing this extension (that setting would cause to use dev-master when testing instead of proper versions and I believe was set there by accident by someone who didn't understand it's meaning).

This is for #16 issue which would then be really closed as I've verified everything now.

This should be tagged as v0.3.2


Removing dependency on apache-commons lang 3, adding necessary classes as needed

Added 4 new types of classes to help remove this dependency :

Pair and ImmutablePair
Triple and ImmutableTriple
SerializationUtils
StringUtils

@vinothchandar @bvaradar Please take a pass at this

@vinothchandar updated the diff


Remove conda from ci-tests

Chosen to remove Conda rather than fix it. I think our GH Action should use as many inbuilt features as possible and not introduce dependencies.


Improved login process to have better UX

Tasks done:

[x] o validade fields password and email when are empty
[x] Return feedback when password does not successfull

Coverage decreased (-1.3%) to 73.843% when pulling 3235acebdeb48a502897586c3b57d04129dc60ca on fix-login-process into b6757d52c8b0c8a7fb0a2685adccbcc49bb6b0e6 on master.


When clause contexts supoort check whether the window is remote(SSH) or not

While open a session(remote is macOS) with ssh on Windows, the integrated terminal is ssh, I want add some shortcuts to move cursor around words such as use iTerm2 on macOS, such as:
  {
      "key": "ctrl+left",
      "command": "workbench.action.terminal.sendSequence",
      "args": {
          "text": "\u001bb"
      }, // move cursor to end of line, sends ctrl+e to terminal
      "when": "terminalFocus && isWindows && ConditionCurrentSessionIsRemoteToMac "
  },

Requiring ConditionCurrentSessionIsRemoteToMac because I don't want this shortcuts when open local window.
Could a new feature support this, or any way can work for current version?
Thanks.

You can mostly do this now with:
"when": "terminalFocus && isWindows && remoteName == 'wsl'"

I don't think you can match on the target machine is all.


Split arch_test.h into two files

Split the arch_test.h into

arch_test_priv.h - will contain sections from the current arch_test which is required only when the test is a privileged test. These include

supervisor/user entry/exit macros
supervisor/user trap handler
machine trap handler
interrupt set/clear macros

arch_test_unpriv.h - will contain sections from the current arch_test which is required for normal test execution. These include

instruction macros
migration aliases

@neelgala please check if this would work as you intended -> https://github.com/incoresemi/uatg/commit/bd65ac0f1594a19d08b56619d1d4489d2a589b38


Crash on Teleport to Base

When teleporting to my base from my RFtools mining dimension, either by RFtools teleporter or FTBtools command, the server crashes with this error and I usually can not get back in until a full reset occurs. This crash also happens in singleplayer on the same world. http://pastebin.com/fBSiVXyL

It crashes in Mekanism. Report to them


Make Parcel 2 to work or switch to a different bundler

Elm Designer still uses Parcel 1 for development and build phases.
Parcel 2
As today I have tried unsuccessfully to switch to Parcel 2 (see the parcel2 branch). While running in dev mode everything seems smooth, but when running the "build" command Parcel hangs indefinitely.
We identified the issues being in the terser module which interacts weirdly with the  Parcel's Elm plugin, disabling it (manually) fix things.
So we can wait a bit and hope that Em and Terser work better together or we'll be forced to switch to a different bundler.
Other options
Vite seems very popular these days and it has an Elm plugin (https://github.com/hmsk/vite-plugin-elm) , but I personally never used it, so if you have experience with it let me now.
What do we need?

Elm transformer
Sass compiler (we have Bootstrap sass files to convert into CSS)
Minimal support for static assets (PNG, JPEG and SVG)

Vites great in my experience with it for an elm-spa app so not huge but not trivial either... otherwise webpack is good n' faithful if but a bit crusty around the edges 🤷♂

The issue is fixed. Now we just need to wait for the next release.


[BUG] Inconsistency in PerSegmentModel in-sample predictions with regressors

🐛 Bug Report
Let's look at example:
python
@pytest.mark.parametrize(
    "model, transforms, num_skip_timestamps",
    [
        (CatBoostModelPerSegment(), [LagTransform(in_column="target", lags=[2, 3])], 2),
        (ProphetModel(), [], 0),
    ],
)
def test_forecast_in_sample(model, transforms, num_skip_timestamps, example_tsds):
    ts = example_tsds
    df = example_tsds.to_pandas()

    # fitting
    ts.fit_transform(transforms)
    model.fit(ts)

    # forecasting
    forecast_ts = TSDataset(df, freq="D")
    forecast_ts.transform(ts.transforms)
    forecast_ts.df.loc[:, pd.IndexSlice[:, "target"]] = np.NaN
    # not to fail because of NaNs
    if num_skip_timestamps:
        forecast_ts.df = forecast_ts.df.iloc[num_skip_timestamps:]
    model.forecast(forecast_ts)

    # checking
    forecast_df = forecast_ts.to_pandas(flatten=True)
    assert not np.any(forecast_df["target"].isna())

Look carefully at num_skip_timestamps of CatBoostModelPerSegment and ProphetModel. We have positive num_skip_timestamps for catboost, however it can work with NaNs. Try to set value 0 or 1 and you will see that catboost can't predict first points of the segment. As I understand it is due to the first line of PerSegmentBaseModel._forecast_segment where it makes slice from ts.
If there are no regressors slice gives segment from the beginning. Otherwise it gives segment where at least one feature is not None.
Expected behavior
Behavior is consistent.
How To Reproduce
Look at report.
Environment
No response
Additional context
No response
Checklist

[X] Bug appears at the latest library version

I found a bug that can actually happen because of this:
import pandas as pd

from etna.datasets import TSDataset
from etna.models import CatBoostPerSegmentModel
from etna.pipeline import Pipeline

def main():
    # load data
    timestamp = pd.date_range(start="2020-01-01", periods=3, freq="D")
    timestamp_exog = pd.date_range(start="2020-01-01", periods=6, freq="D")
    df = pd.DataFrame({"timestamp": timestamp, "segment": ["segment_0"] * 3, "target": [1, 2, 3]})
    df_exog = pd.DataFrame(
        {"timestamp": timestamp_exog, "segment": ["segment_0"] * 6, "regressor": [1, 2, 3, None, 5, 6]}
    )
    ts = TSDataset(df=TSDataset.to_dataset(df), df_exog=TSDataset.to_dataset(df_exog), freq="D", known_future="all")

    # fit pipeline
    model = CatBoostPerSegmentModel()
    pipeline = Pipeline(model=model, horizon=2)
    pipeline.fit(ts)

    # forecast
    ts_forecast = pipeline.forecast()
    assert ts_forecast.df.loc[:, pd.IndexSlice[:, "target"]].isna().any().any()

if __name__ == "__main__":
    main()

As we can see, we have NaNs in target column after forecasting. It isn't something we expect.


Performance cliff with large database

We found this a little while ago, see https://github.com/casey/ord/issues/371, but I was hoping to have more information for you before making an issue here. However, I really haven't been able to figure out the issue, so here I am T_T
The mainnet ord database is around 50GiB, and syncs reasonably quickly. It processes one block at a time, without any parallelism, makes one commit per block, and takes around 36 hours to sync when connected to a fully synced bitcoin core node.
The main table is OUTPOINT_TO_ORDINAL_RANGES, which maps outputs, which are a TXID  and a u32 output index, to ordinal ranges, the encoding of which is a little complicated, but are conceptually just (u64, u64) which give the start and size of each ordinal range in the output.
Recently, we added a new table, OUTPOINT_TO_TXID, which required a rebuild of the database. However, when the rebuild was underway, we noticed that it was extremely slow, and would take at least 9 days to sync, and the database was around 80 GiB, and wasn't yet at half-way synced. Each block was taking multiple seconds, as opposed to just a few milliseconds. We stopped the sync, disabled writes to the new table, and re-deployed, and the full sync was pretty quick again.
One thing that struck me was that the server has 64 GiB of RAM, so maybe the performance cliff happens when the database is larger than available RAM. So, we tried building the database on a machine with 1 GiB of RAM, but didn't notice a similar cliff. So it might be that the degradation only happens when the database is large.
Do you have any suggestions for things we might do to figure out to give you more information, and find out if this is redb issue, or if we're just hitting performance limitations of the box we're on?

Hmm, interesting. Ya, a few ideas:

are you running it on Linux? If so, it'd be useful to collect a flamegraph of the perf of a couple insertions that are slow. I use the flamegraph crate (not cargo-flamegraph)
try printing the database stats to see if anything looks terribly wrong. Like if the height is more than log2(number of keys) then something is very wrong. It should be around log base x, where x is around 2000/size_of()
try using atop to see if disk bandwidth or CPU time is saturated. If disk bandwidth is low and CPU time is at 100%, there's probably a bug

Here's the output of ord info on a fully synced mainnet database. The two main tables are block height -> hash and outpoint -> ordinal ranges, and the number of keys in both looks right, so blocks indexed is the number of keys in the first table and outputs indexed is the number of keys in the second table.
blocks indexed: 752920
outputs indexed: 135512466
tree height: 7
free pages: 255940053
stored: 25.6 GiB
overhead: 1.38 GiB
fragmented: 20.63 GiB
index size: 49.25 GiB

Is there anything in this that jumps out at you as suspicious?
This is from an index that hasn't hit the performance cliff yet, so if there's a bug, for example in balancing, it might not be manifesting it yet.

Nope, that all looks quite reasonable.
It's interesting that your sync takes so long. My benchmark writes 1M keys in 1.4secs. So 24+ hours for 135M keys seems kinda slow. How do I run this sync myself?

The 135M keys are just the outputs that remain as of the current chain tip.
It's pretty easy to run! You'll need bitcoin core: https://bitcoincore.org/en/download/
Start and sync a bitcoin node by running bitcoind. Then as the same user, run ord server. ord should automatically find  and auth with bitcoin. bitcoind will take about 1-2 days to sync, and ord can run and will sync at the same time.

If it's reasonably fast, try uncommenting out the cfg in index.rs:
    #[cfg(any())]
    for input in &tx.input {
      outpoint_to_txid.insert(&serialize(&input.previous_output), &txid)?;
    }

On our production server, this makes everything much slower.

When I run ord I get this error:
cberner@vermeer:(master)~/Code/ord$ cargo run --release -- server
    Finished release [optimized] target(s) in 0.10s
     Running `target/release/ord server`
error: Permission denied (os error 13)

Do I need to do something to grant it permission to talk to bitcoind, or use something else?

The 135M keys are just the outputs that remain as of the current chain tip.

Ah right, ok that makes sense. When bitcoind is sync'ing does the tx=10180481 part of each line that it prints indicate the number of transactions that have occurred up to that height?

When bitcoind is sync'ing does the tx=10180481 part of each line that it prints indicate the number of transactions that have occurred up to that height?

Yup, I think so. My synced node just printed tx=762688384, which comports with this graph.

are you running it on Linux? If so, it'd be useful to collect a flamegraph of the perf of a couple insertions that are slow. I use the flamegraph crate (not cargo-flamegraph)

Here's the flamegraph (ran on a Mac) from indexing a few hundred blocks starting from around block 150000 on the bitcoin main chain. Does this look reasonable to you in terms of redb behavior? I couldn't see anything that stood out - seems to spend about 75% of index_ranges time on database operations, thereof 1/3 on insertions, 1/3 on deletes and the rest on getting blocks from bitcoin core - which seems reasonable.

Ya, that looks quite reasonable. Is that before or after the big slowdown?

This is with the "big slowdown" changes backed out, so before the big slowdown.

If it's reasonably fast, try uncommenting out the cfg in index.rs:
    #[cfg(any())]
    for input in &tx.input {
      outpoint_to_txid.insert(&serialize(&input.previous_output), &txid)?;
    }

On our production server, this makes everything much slower.

I uncommented that line and also turned on info level logs. I ran the sync up to block height 392844, and I think I see the slowdown you're talking about. Each transaction has gone from taking 1-10ms to more like 1000ms. However, it looks expected, the number of ordinals being committed in each transaction has gone up to around a million!
[2022-09-08T14:35:39Z INFO  ord::index] Wrote 1146834 ordinal ranges in 1786ms

Could the problem be that around that block height people started using Bitcoin more, and so the ordinals are getting mixed around and so each transaction that gets spent includes a large number of ordinal ranges?

A milling ranges per TX should be a rate exception. We will collect some more stats.

Could the problem be that around that block height people started using Bitcoin more, and so the ordinals are getting mixed around and so each transaction that gets spent includes a large number of ordinal ranges?

That's definitely true, but I don't think it's the source of the slowdown. When this for loop:
for input in &tx.input {
  outpoint_to_txid.insert(&serialize(&input.previous_output), &txid)?;
}

…is enabled it will perform one additional insert per spent output, which doesn't depend on the number of ordinal ranges moving per transaction. So uncommenting it shouldn't cause a slowdown that occurs when the number of ordinal ranges moving per block gets large. Also, without it, the ordinals.com instance syncs reasonably quickly all the way to the chain tip.
Here's a graph of the full mainnet sync, without the slowdown:

So it definitely slows down as blocks get full, but the average stays around 200ms. Here's a zoomed in view of the end:

It's hard to tell, but it looks like the average stays around 200ms/commit.

Ah yes, ok I see. I added a counter for the number of outpoints, and it's only a few thousand per block

Ok, so the good news is I don't think it's a bug in redb, but that's also the bad news =P
I hacked my benchmark to simulate your workload, it assumes each value is 12 bytes * 100 ordinal range = 1.2kb, and after an initial load of millions of pairs, it writes transactions of 5000 outpoints.
I tested against lmdb, with varying sizes for the initial load, and redb performs on par with lmdb (redb seems to scale better actually). However, both of them start to get slow around 8M entries, which is probably around the time that it no longer fits in memory (I have 32GB, but it looks like the OS is only using ~14GB for buff/cache according to free):
1M
redb: Bulk loaded 1000000 items in 4704ms
redb: Wrote 100 individual items in 886ms
redb: Wrote 100 x 5000 items in 13178ms
redb: Removed 500000 items in 2804ms
lmdb-rkv: Bulk loaded 1000000 items in 4892ms
lmdb-rkv: Wrote 100 individual items in 876ms
lmdb-rkv: Wrote 100 x 5000 items in 7687ms
lmdb-rkv: Removed 500000 items in 2618ms

2M
redb: Bulk loaded 2000000 items in 10707ms
redb: Wrote 100 individual items in 912ms
redb: Wrote 100 x 5000 items in 15037ms
redb: Removed 1000000 items in 6295ms
lmdb-rkv: Bulk loaded 2000000 items in 14506ms
lmdb-rkv: Wrote 100 individual items in 971ms
lmdb-rkv: Wrote 100 x 5000 items in 8659ms
lmdb-rkv: Removed 1000000 items in 6173ms

4M
redb: Bulk loaded 4000000 items in 25327ms
redb: Wrote 100 individual items in 898ms
redb: Wrote 100 x 5000 items in 14864ms
redb: Removed 2000000 items in 20850ms
lmdb-rkv: Bulk loaded 4000000 items in 36919ms
lmdb-rkv: Wrote 100 individual items in 869ms
lmdb-rkv: Wrote 100 x 5000 items in 8482ms
lmdb-rkv: Removed 2000000 items in 40537ms

8M
redb: Bulk loaded 8000000 items in 71191ms
redb: Wrote 100 individual items in 1077ms
redb: Wrote 100 x 5000 items in 34156ms
redb: Removed 4000000 items in 510961ms
lmdb-rkv: Bulk loaded 8000000 items in 152380ms
lmdb-rkv: Wrote 100 individual items in 933ms
lmdb-rkv: Wrote 100 x 5000 items in 35490ms
lmdb-rkv: Removed 4000000 items in 515297ms

16M
redb: Bulk loaded 16000000 items in 1029296ms
redb: Wrote 100 individual items in 962ms
redb: Wrote 100 x 5000 items in 117697ms
lmdb-rkv: Bulk loaded 16000000 items in 1267875ms
lmdb-rkv: Wrote 100 individual items in 1042ms
lmdb-rkv: Wrote 100 x 5000 items in 118925ms

There's a bunch of weird stuff here, like remove is much slower than insert, which doesn't really make sense to me. Will need to look into it further.

Ok, actually I think the insert performance does make sense. I tested throughput on my disk (Samsung 980 Pro) with fio and got about 30k IOPS: fio --filename ./junk.dat --eta-newline=5s --name write-test --size=1g --io_size=1g --blocksize=4k --ioengine=libaio --fsync=1000000000000 --iodepth=1 --direct=1 --numjobs=1 --runtime=20 --fallocate=none --rw=randwrite
We can estimate the insert speed by assuming every write goes directly to disk:

assuming the branch pages are half full, each key takes up 52 bytes (key, offset, child ptr, and child checksum [zeros are stored even for 2PC]), then the tree order will be around 40. The exact value isn't that important, since this is a b-tree it'll only change the height by +/- 1
using that we get a tree height of around 5
and now we calculate the total insert time: 16M * 5 / IOPS = 2,666secs. Whereas the measured time is 1,029secs -- presumably faster due to the page cache.
similarly, the per transaction time is expected to be around 833ms. Whereas measured time is around 3secs -- presumably slower due to overhead, such as zeroing out freed pages

Thanks for looking into this!
Ahh, damn, I was hoping for an ez fix bug in redb 😭
I tried to simulate the database running out of memory by building an index that was > 1 GiB of memory on a machine with 1 GiB of memory, but didn't run into a cliff. However, that was a small database, so it seems likely that I might just not have seen enough of a performance difference.


[Bug]: Wording improvement

Installation method
Own AWS account
What happened?
There is a grammar issue on this page.

What did you expect to happen?
I think it should say We can review this in several parts to make sense of it
How can we reproduce it?
Access the page
Anything else we need to know?
No response
EKS version
n/a

Found the same issue in another page

Hi @cemendes thanks for reporting! Can you confirm this PR is fixing the typo you identified? #1051

You are welcome. The PR does fix the issue.


Add Julia 1.0.0-1.3.1

Right now this only supports Julia 1.4.x. We should add support for all previous Julia versions.
I tried this already but ran into some problems, in particular I was not able to compile any Julia version pre 1.4.0 on my build machine.

At the moment this now supports Julia 1.5.1-1.6.1. Those are the only publicly available Julia builds that don't have a broken signature on the binaries. It would still be nice if we could also support all other old versions, but for that we need compiled binaries that don't have the broken signatures on them that the mono signtool creates.


New badge: Github generic issue search badge

:clipboard: Description
This started as a discussion https://github.com/badges/shields/discussions/5943 but I think we've decided this is a good idea, so I'm moving it to an issue. Here's the plan:
In the github front-end, it is possible to construct fairly nuanced issue/PR queries. For example:

is:open is:issue label:core label:bug author:app/sentry-io - open issues with the labels "core" and "bug" opened by sentry-io bot: https://github.com/badges/shields/issues?q=is%3Aopen+is%3Aissue+label%3Acore+label%3Abug+author%3Aapp%2Fsentry-io
is:pr is:closed label:npm-package review:approved author:chris48s - closed PRs labelled "npm-package" submitted by user "chris48s"  with one or more approving reviews: https://github.com/badges/shields/pulls?q=is%3Apr+is%3Aclosed+label%3Anpm-package+review%3Aapproved+author%3Achris48s

We already have a wide variety of github issue badge variants. Rather than gradually implement that syntax one feature request at a time as people want more nuanced queries, lets implement one badge:
Github Issue (with arbitrary query): /github/issue-search?q=...
This would allow us to call for example /github/issue-search?q=repo%3Abadges%2Fshields%20is%3Aopen%20is%3Aissue%20label%3Acore%20label%3Abug%20author%3Aapp%2Fsentry-io
which would execute the GraphQL query
query {
  search(query: "repo:badges/shields is:open is:issue label:core label:bug author:app/sentry-io", type: ISSUE) {
    issueCount
  }
}

Then we can basically say most of our existing issue badge variants are a special case of that in one way or another (certainly all the ones that just display a total). We could either:

Make our existing random mashup of github issue/PR variant badges redirects to preset queries on that general badge or
Continue serving those badges directly without issueing a redirect using a single shared fetch() function and simplify the internals

Either way, we say "no more presets" and any arbitrary query you can make through the GH frontend can also be a badge and we can clean up this mess:

:link: Data
GitHub GraphQL API
:microphone: Motivation

Allow any issue badge for 'number of issues/PRs matching [arbitrary criteria]'
Tidy up our existing pile of github issue badge variants

Follow up: https://github.com/badges/shields/pull/5976#discussion_r548056167

Follow up: #5976 (comment)

What if for the repository-scoped query badges we extended the query to include the repository node? I know that adds an extra point but that will allow us to hook into the errors object on the response and still be able to utilize our transformErrors helper to provide the standard not found errors
query($user: String!, $repo: String!, $query: String!) {
  search(query: $query, type: ISSUE) {
    issueCount,
  }
  repository(owner: $user, name: $repo) {
    name
  }
}

:bulb: Nice solution. I know the entire point of GraphQL is it is flexible enough that you can perform multiple queries at once and do the work of many REST calls in a single query, but I still sometimes have trouble shifting into that mindset.


Implement retries for Artifact GC

If Artifact GC fails, the Pod can do a few retries through some sort of exponential backoff before declaring failure.

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

@dpadhiar I believe we need to call the Backoff function here (you can look to see other places in the code where we call that). You can look up the concept of "Exponential backoff" to see what that's all about if you don't already know.


DiagramCanvas not re-rendering base on Parameter

I have worked on the POC for diagram project here
https://github.com/JanOfOlympus/BlazorDiagramPOC/tree/feature/diagram-poc
here I tie the tab with diagram. I have an issue with diagram rendering here

Click 'CreateDiagram'
Add Node into Tab1
Create another tab (named Tab2)
The Node from Tab1 is also appear on Tab2

Im not sure why the DiagramCanvas is not render base on the CascadingValue here.
Not sure I implement something wrong :(
I have Diagram.razor as parent component and DiagramComponent.razor as child component here
Thank you do much for your reply :)

@JanOfOlympus I cannot see BlazorDiagramPOC, is the repository public?

Hello,
I can't see the repository either.
I'm guessing that you're using the same Diagram instance on both tabs. You should be creating 1 Diagram object per tab so that they are separate.

@flibbertigibbet-uk @zHaytam Ohh I really sorry :( . I already made it public now :)

@zHaytam Hmm ok I'm getting the idea, but I pass the Diagram object as param here so I think it should be new instance? Hmm I'm not sure, I'm very new to Blazor :). I'd be very appreciate if you could guide me. Many Thanks!
I will test your repository tonight. Can you make sure you push everything to feature/diagram-poc?

@zHaytam yep already :)

Found the issue/solution:
<DiagramComponent @key="i.TabId" BlazorDiagram=@(AppState.TabIdAndBlazorDiagrams[i.TabId]) />
```

Notice that in Blazor when you're looping and creating components, you should specify a `@key` so that it can accurately calculate the difference.

![2023-10-23_08-17-20](https://github.com/Blazor-Diagrams/Blazor.Diagrams/assets/34218324/7e5417b5-095a-4d45-912f-20471d9f60d8)

@zHaytam


Error Message: Cannot read properties of undefined

Does this occur consistently?
Repro steps:

Action: appService.Deploy
Error type: TypeError
Error Message: Cannot read properties of undefined (reading 'createClient')
Version: 0.24.7
OS: linux
OS Release: 5.19.0-35-generic
Product: Visual Studio Code
Product Version: 1.75.0
Language: en

Call Stack
extension.bundle.js:2:3774915
fulfilled extension.bundle.js:2:3773586

The fix for this bug has been merged and is waiting to be released in the Azure Resources extension. https://github.com/microsoft/vscode-azureresourcegroups/pull/642

This issue has been fixed by the 0.7.0 release of the Azure Resources extension. Please update the Azure Resources extension to version 0.7.0.


ANL cluster parameter settings

Issue Description
What did you expect to see happen?
It would be good to have a general factory/config file system to handle different cluster job handlers like PBS, torque, etc.
-> A design for this system, like who handles the config files, where are they stored, what is accessible form the RAVEN input file, etc. needs to be thought of.
What did you see instead?
Right now, every new job handler in every new institution has to change the job handler scripts provided by RAVEN.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or improvement?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
[ ] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

Can we have a description of the deviations we need to perform for the new clusters we have experience with?
we can come up with a generalization scheme

In my one experience I had to create a new SimulationMode and a new raven_qsub_script.sh to be compliant with the scheduler (torque instead of pbspro).  The modified files reside on the remote server and are supposedly not maintained by us.

archived


master missing build directory contents

The master branch appears to have a placeholder for the build directory rather than the directory and its contents.
Using the build directory from the stable branch almost works, but cmake stops due to a missing definition for "mz_auto_format".

Sabine,
The build directory on the master branch is a submodule that needs to be pulled first. You will need to do a local clone of the repository and execute git submodule update —init from within your cloned repository.
Regards,
Marius

Hi Marius,
Thanks for the quick response. I tried what you suggested but got an error:
fatal: repository 'https://github.com/mlba-team/mz-cmaketools.git/' not
found
Is the URL for the submodule correct?
Thanks for your help!
Sabine
On Tue, Oct 2, 2018 at 3:33 PM, Marius Zwicker<EMAIL_ADDRESS>wrote:

Closed #5 https://github.com/mlba-team/xdispatch/issues/5.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mlba-team/xdispatch/issues/5#event-1880365092, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ag7VmuDM5i3qDQFBo1IIK4CfOw_L44J4ks5ug82DgaJpZM4XEznJ
.

Sorry for that, said repository had not been mirrored yet. I should all be working now.

Thank you, it is working now!
On Wed, Oct 3, 2018 at 1:19 AM, Marius Zwicker<EMAIL_ADDRESS>wrote:

Sorry for that, said repository had not been mirrored yet. I should all be
working now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mlba-team/xdispatch/issues/5#issuecomment-426524005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ag7VmtRrVfxpHwmvlRAQ85Osk2XhMQZqks5uhFbbgaJpZM4XEznJ
.


mobile android view is "halted" when loading.

The "go to map" should show a loader while waiting for the map to render.

closed by #98


The way Antd is introduced

As an official on-demand introduction, the style does not apply. You can enter the style globally.
em:
In the app.global.css file
  @ import "antd/dist/antd.css";

If so, other ways are welcome

You can take a look at this. https://github.com/amilajack/erb-ant-design-example. Let me know if this works for you. If it doesn't i can reopen

@helpceo I solved by modifying webpack.config.render.dev/prod.js
{
  test: /^((?!\.global).)*\.css$/,
  exclude: /node_modules/,
  use: [
    {
      loader: 'style-loader'
    },
    {
      loader: 'css-loader',
      options: {
        modules: true,
        sourceMap: true,
        importLoaders: 1,
        localIdentName: '[name]__[local]__[hash:base64:5]'
      }
    }
  ]
},
{
  test: /\.css$/,
  include: /node_modules/,
  use: [
    {
      loader: 'style-loader'
    },
    {
      loader: 'css-loader'
    }
  ]
}

<link rel="stylesheet" href="../node_modules/antd/dist/antd.css">   app.html


Meeting 04-03-2019

Community Meeting
Agenda

Percona
https://github.com/sous-chefs/percona/pull/389
~Website style update (@JohnRoesler )~ postponed
Aptly update @Raboo )

new aptly cookbook release?

@tas50 and @josephholsten did anyone make minutes on Tuesday?


Problem comparing json default value in postgresql migrations

Describe the bug
After we created the initial migration for the model with a JSON field that has a default value, all next migrations will attempt to modify the default value to the same one.
To Reproduce
https://github.com/DeityLamb/mikro-orm-issue
Create an entity that has a json field with default value
mikro-orm migration:create
# created first migration

mikro-orm migration:up
# we up migration and not to change anything

mikro-orm migration:create
# a new migration was created that changes the default value to the same

Expected behavior
Do not include changes to default values in migration if they have not been modified.
Versions

Dependency
Version

node
v18.14.2

typescript
^4.9.5

mikro-orm
^5.6.16

postgresql
15.1

Quick inspection
Entity
import { Entity, JsonType, PrimaryKey, Property } from "@mikro-orm/core";

interface UserMetadata {
  value: number;
}

@Entity()
export class User {

  @PrimaryKey()
  public id!: number;

  @Property({ type: JsonType, default: JSON.stringify({ value: 42 }) })
  public metadata!: UserMetadata;
}

Initial migration
import { Migration } from '@mikro-orm/migrations';

export class Migration20230410153819 extends Migration {

  async up(): Promise<void> {
    this.addSql('create table "user" ("id" serial primary key, "metadata" jsonb not null default \'{"value":42}\');');
  }

  async down(): Promise<void> {
    this.addSql('drop table if exists "user" cascade;');
  }

}

All subsequent migrations will include this even if the default value has not been changed.
import { Migration } from '@mikro-orm/migrations';

export class Migration20230410160922 extends Migration {

  async up(): Promise<void> {
    this.addSql('alter table "user" alter column "metadata" type jsonb using ("metadata"::jsonb);');
    this.addSql('alter table "user" alter column "metadata" set default \'{"value":42}\';');
  }

  async down(): Promise<void> {
    this.addSql('alter table "user" alter column "metadata" type jsonb using ("metadata"::jsonb);');
    this.addSql('alter table "user" alter column "metadata" set default \'{"value": 42}\';');
  }

}

default is the runtime value, so not string, but object.

Maybe the diffing does not work correctly for JSON type, it's a bit tricky - there are some changes in master that should help with that. Could you try latest dev version and drop the JSON.stringify?

The development version, unfortunately, does not solve the problem. We anyway cannot pass the object to default field.
Currently, we are converting the object to a jsonb string using JSON.stringify with additional indentations and field sorting.
This is a working solution, but it is difficult to call it reliable.
For my specific case, the ideal approach would be to generate default values based on a deep comparison of both objects.
Perhaps something like this can be made here, i guess
Something like this check:
if (to.mappedType instanceof JsonType && from.default && to.default) {

  // remove single quotes from the start and end of default json
  const normalize = (str: string) => str.replace(/(^'|'$)/g, '');

  const defaultValueFrom = parseJsonSafe(normalize(from.default));
  const defaultValueTo = parseJsonSafe(normalize(to.default));

  return Utils.equals(defaultValueTo, defaultValueFrom);
}

The problem may be much more complex. Unfortunately, I am not familiar with the codebase.

Defaults are compared via prop.defaultRaw, the link you mentioned is not comparing EntityProperty (which has default and defaultRaw) but a Column which only has default (and Column.default is exactly the same as EntityProperty.defaultRaw. And there the value should automatically stringified via the JsonType, but I think I see why it's not working - this seems to be hardcoded only for the ArrayType.
https://github.com/mikro-orm/mikro-orm/blob/master/packages/core/src/metadata/MetadataDiscovery.ts#L969-L971
Once this is fixed, you will most probably need to drop that stringify part.

Same issue when persisting entities.
Example: Mikro-ORM loads entity list via repository.findAndCount() with filled json columns from database. And when I create a new entity and call repository.persist() mikro-orm update previously loaded entities with same JSON values, so I got unnecessary update work. Version is v.5.6.16


fix: lib_url not working with relative file paths

fixes #64
Small breaking change:
allow_lib_overwrite -> lib_overwrite_enabled

Nice one Matt. Appreciate it!


Feature requests: Full exclude

There is missing option to fully disable browser support.

What do you mean? Could you show some examine?

Currently we cannot write 'not ie' to exclude browser support instead of specific versions.
I am sorry, if it is not true, but in postcss autoprefixer throwing an error Unknown browser query ie

Use not ie > 0.
We don’t have a shortcut, because I think it is a bad practice. You should not think about vendors, but think about popularity and other common parameters. IE users deserve Web too :D.


Intellisense not recognizing predefined macros with CMake, Clang and -nostdinc

Bug type: Language Service
Describe the bug

OS and Version: Ubuntu 21.10
VS Code Version:
Version: 1.63.2
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:39:46.686Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.13.0-39-generic
C/C++ Extension Version: 1.9.7
Other extensions you installed (and if the issue persists after disabling them):
ms-vscode.cmake-tools
Workspace: Single project, trivial project with just one trivial source.

C++ compilers provide some predefined macros, like __INT_FAST32_TYPE__ and Intellisense should be able to know that definition. I don't know how Intellisense gets to know the predefined macros; the cmake-tools extension may provide them, the cmake-tools extension may provide the compiler path and the list of arguments used to invoke it, it may even have nothing to do with the cmake-tools extension and Intellisense just does something to get them. One way to get predefined macros is to invoke the compiler, like c++ -dM -E foo.h with a dummy foo.h.
I tested and found out that both Clang 13.0.0 and GCC 11.2.0 provide the same predefined macros for types (except a couple exceptions). Passing the flags -nostdinc and -nostdlib had no effect on this.
However, passing the flag -nostdinc for some target, on the CMakeLists.txt, when using clang, resulted in the predefined macros not being recognized by Intellisense.
The offending CMakeLists.txt:
cmake_minimum_required(VERSION 3.20.0)
project(scratch VERSION 0.1.0)

add_executable(scratch main.cpp)
target_compile_features(scratch PRIVATE cxx_std_20)
target_compile_options(scratch PRIVATE -nostdinc)
# target_link_options(scratch PRIVATE -nostdlib)

main.cpp is a trivial source.
Steps to reproduce

Create a new project, maybe with command Cmake: Quick Start
Add compile option -nostdinc in CMakeLists.txt (like in the code snippet above)
Run vscode command Cmake: Delete Cache and Reconfigure (not sure if necessary)
Run vscode command Developer: Reload Window (not sure if necessary)
On reload, the predefined macros will be highlighted as undefined on the source

Expected behavior
Predefined macros should be recognized, despite passing the -nostdinc option
NOTE: Not sure if this is a bug with this extension or with the cmake-tools extension.

I don't repro the issue without CMake Tools. If I set C_Cpp.loggingLevel to "Debug" I see "  define: __INT_FAST32_TYPE__=int" in the logging. You could also run the C/C++: Log Diagnostics command to check what compiler is being used.

It seems to work for me (Ubuntu 20.04).  Am I missing something?  I also see define: __INT_FAST32_TYPE__=int in my log.  My compiler's a little older (Clang 10), but I can try the newer one if you think that will make a difference.

I found out that the error goes away when I set intelliSenseMode to linux-clang-x64. But if I let cmake-tools configure intellisense, then it changes that setting back to linux-gcc-x64 and the error reappears. Perhaps the error is in detecting Clang13 as a variant of Clang?

Environment

OS and Version: macOS 13.4.1
VS Code Version:
Version: 1.79.2
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06
Date: 2023-06-14T08:58:33.551Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.5.0
C/C++ Extension Version: 1.16.3
Other extensions you installed (and if the issue persists after disabling them): ms-vscode.cmake-tools
Workspace: Single project, trivial project with just one trivial source.

Happens on the __FILE_NAME__ macro
I'm also experiencing this issue. In my case __FILE_NAME__ macro.
It is one of the builtin macros from Clang Language Extensions - Link

Error squiggles on the __FILE_NAME__ macro.

Changing intelliSenseMode to linux-clang-arm64 didn't make any difference.

@Malangcow Your __FILE_NAME issue is not a CMake Tools bug -- it's a bug with the C/C++ extension. Can you file there issue there? https://github.com/microsoft/vscode-cpptools/issues

@Malangcow Your __FILE_NAME issue is not a CMake Tools bug -- it's a bug with the C/C++ extension. Can you file there issue there? https://github.com/microsoft/vscode-cpptools/issues

Got it. I filed a issue here  Intellisense not recognizing predefined macros from Clang #11164

Closing this issue now that it's in C/C++ extension. Thanks!

@gcampbell-msft I believe the original issue is a CMake Tools issue. I was only referencing @Malangcow different issue that got posted to this issue.


Support signed declare transaction

Describe your changes

This PR adds support for signing declare transactions and sending them.
Linked issues

Closes #145
Breaking changes

[ ] This issue contains breaking changes

Thing to consider: with current supported version of the RPC spec, it's impossible to send signed declare transactions. Starknet-jvm will first have to be updated to support RPC 0.2.0 for these to be able to work.

Note that the Rpc provider doesn't support sending signed Declare txs. I've added an error for that so it doesn't fail silently/is ignored. This will have to be addressed once rpc 0.2.1 is supported, shouldn't require any changes to the Account itself however.


Updated docs for 1.1.0 release

Updated the following:

Product snapshot.
Limitation section.
Feedback section.
Configuration section.
Troubleshooting section.
Release Notes.

Thanks @luckyj5


Internal Error: Failed to launch the browser process

运行weread-spy时报错，提示无法打开浏览器，应该是puppeteer的问题，但不知道怎么处理
通过pnpm安装
pnpm v8.4.0
npm v9.5.1
nodejs v18.16.0
Windows10
错误代码
Internal Error: Failed to launch the browser process! undefined
[16308:12068:0508/024016.443:FATAL:chrome_resource_bundle_helper.cc(107)] Check failed: !actual_locale.empty(). Locale could not be found for
Backtrace:
        IsSandboxedProcess [0x00007FFCC20A1062+998194]
        IsSandboxedProcess [0x00007FFCC2E38402+15249106]
        IsSandboxedProcess [0x00007FFCC21311D2+1588386]
        IsSandboxedProcess [0x00007FFCC2132250+1592608]
        IsSandboxedProcess [0x00007FFCC20469A8+627832]
        ChromeMain [0x00007FFCBE7F1E95+3573]
        CrashForExceptionInNonABICompliantCodeRange [0x00007FFCC19FCAC2+24761666]
        CrashForExceptionInNonABICompliantCodeRange [0x00007FFCC19FC764+24760804]
        CrashForExceptionInNonABICompliantCodeRange [0x00007FFCC19FAF5F+24754655]
        CrashForExceptionInNonABICompliantCodeRange [0x00007FFCC19FB21E+24755358]
        ChromeMain [0x00007FFCBE7F133F+671]
        GetPakFileHashes [0x00007FF722EB29FF+6655]
        GetPakFileHashes [0x00007FF722EB1A96+2710]
        GetHandleVerifier [0x00007FF7230235B2+1030434]
        BaseThreadInitThunk [0x00007FFD5E787604+20]
        RtlUserThreadStart [0x00007FFD5F9426A1+33]
Crash keys:
  "reentry_guard_tls_slot" = "unused"
  "variations" = "db59f83a-3f4a17df,8bccc03b-3f4a17df,fabf21f1-3f4a17df,272b4158-3f4a17df,2510663e-73703436,"
  "num-experiments" = "5"
  "switch-27" = "about:blank"
  "switch-26" = "--remote-debugging-port=0"
  "switch-25" = "--user-data-dir=C:\Users\white\AppData\Local\weread-spy\Data\ppt"
  "switch-24" = "--use-mock-keychain"
  "switch-23" = "--password-store=basic"
  "switch-22" = "--no-first-run"
  "switch-21" = "--metrics-recording-only"
  "switch-20" = "--force-color-profile=srgb"
  "switch-19" = "--export-tagged-pdf"
  "switch-18" = "--enable-blink-features=IdleDetection"
  "switch-17" = "--disable-sync"
  "switch-16" = "--disable-renderer-backgrounding"
  "switch-15" = "--disable-prompt-on-repost"
  "switch-14" = "--disable-popup-blocking"
  "switch-13" = "--disable-ipc-flooding-protection"
  "switch-12" = "--disable-hang-monitor"
  "switch-11" = "--disable-extensions"
  "switch-10" = "--disable-dev-shm-usage"
  "switch-9" = "--disable-default-apps"
  "switch-8" = "--disable-component-update"
  "switch-7" = "--disable-component-extensions-with-background-pages"
  "switch-6" = "--disable-client-side-phishing-detection"
  "switch-5" = "--disable-breakpad"
  "switch-4" = "--disable-backgrounding-occluded-windows"
  "switch-3" = "--disable-background-timer-throttling"
  "switch-2" = "--disable-background-networking"
  "switch-1" = "--allow-pre-commit-input"
  "num-switches" = "29"
  "commandline-disabled-feature-5" = "OptimizationHints"
  "commandline-disabled-feature-4" = "MediaRouter"
  "commandline-disabled-feature-3" = "AcceptCHFrame"
  "commandline-disabled-feature-2" = "BackForwardCache"
  "commandline-disabled-feature-1" = "Translate"
  "commandline-enabled-feature-1" = "NetworkServiceInProcess2"

TROUBLESHOOTING: https://pptr.dev/troubleshooting

[16308:12068:0508/024016.443:FATAL:chrome_resource_bundle_helper.cc(107)] Check failed: !actual_locale.empty(). Locale could not be found for
Backtrace:
        IsSandboxedProcess [0x00007FFCC20A1062+998194]
        IsSandboxedProcess [0x00007FFCC2E38402+15249106]
        IsSandboxedProcess [0x00007FFCC21311D2+1588386]
        IsSandboxedProcess [0x00007FFCC2132250+1592608]
        IsSandboxedProcess [0x00007FFCC20469A8+627832]
        ChromeMain [0x00007FFCBE7F1E95+3573]
        CrashForExceptionInNonABICompliantCodeRange [0x00007FFCC19FCAC2+24761666]
        CrashForExceptionInNonABICompliantCodeRange [0x00007FFCC19FC764+24760804]
        CrashForExceptionInNonABICompliantCodeRange [0x00007FFCC19FAF5F+24754655]
        CrashForExceptionInNonABICompliantCodeRange [0x00007FFCC19FB21E+24755358]
        ChromeMain [0x00007FFCBE7F133F+671]
        GetPakFileHashes [0x00007FF722EB29FF+6655]
        GetPakFileHashes [0x00007FF722EB1A96+2710]
        GetHandleVerifier [0x00007FF7230235B2+1030434]
        BaseThreadInitThunk [0x00007FFD5E787604+20]
        RtlUserThreadStart [0x00007FFD5F9426A1+33]
Crash keys:
  "reentry_guard_tls_slot" = "unused"
  "variations" = "db59f83a-3f4a17df,8bccc03b-3f4a17df,fabf21f1-3f4a17df,272b4158-3f4a17df,2510663e-73703436,"
  "num-experiments" = "5"
  "switch-27" = "about:blank"
  "switch-26" = "--remote-debugging-port=0"
  "switch-25" = "--user-data-dir=C:\Users\white\AppData\Local\weread-spy\Data\ppt"
  "switch-24" = "--use-mock-keychain"
  "switch-23" = "--password-store=basic"
  "switch-22" = "--no-first-run"
  "switch-21" = "--metrics-recording-only"
  "switch-20" = "--force-color-profile=srgb"
  "switch-19" = "--export-tagged-pdf"
  "switch-18" = "--enable-blink-features=IdleDetection"
  "switch-17" = "--disable-sync"
  "switch-16" = "--disable-renderer-backgrounding"
  "switch-15" = "--disable-prompt-on-repost"
  "switch-14" = "--disable-popup-blocking"
  "switch-13" = "--disable-ipc-flooding-protection"
  "switch-12" = "--disable-hang-monitor"
  "switch-11" = "--disable-extensions"
  "switch-10" = "--disable-dev-shm-usage"
  "switch-9" = "--disable-default-apps"
  "switch-8" = "--disable-component-update"
  "switch-7" = "--disable-component-extensions-with-background-pages"
  "switch-6" = "--disable-client-side-phishing-detection"
  "switch-5" = "--disable-breakpad"
  "switch-4" = "--disable-backgrounding-occluded-windows"
  "switch-3" = "--disable-background-timer-throttling"
  "switch-2" = "--disable-background-networking"
  "switch-1" = "--allow-pre-commit-input"
  "num-switches" = "29"
  "commandline-disabled-feature-5" = "OptimizationHints"
  "commandline-disabled-feature-4" = "MediaRouter"
  "commandline-disabled-feature-3" = "AcceptCHFrame"
  "commandline-disabled-feature-2" = "BackForwardCache"
  "commandline-disabled-feature-1" = "Translate"
  "commandline-enabled-feature-1" = "NetworkServiceInProcess2"

TROUBLESHOOTING: https://pptr.dev/troubleshooting

    at ChildProcess.onClose (C:\Users\white\AppData\Local\pnpm\global\5\.pnpm\registry.npmmirror.com+@puppeteer+browsers@0.5.0\node_modules\@puppeteer\browsers\lib\cjs\launch.js:262:24)
    at ChildProcess.emit (node:events:525:35)
    at ChildProcess._handle.onexit (node:internal/child_process:291:12)

解决了，参考

Same after update to<EMAIL_ADDRESS>@jackfranklin
Platform: Github Actions, Ubuntu 18.04 Node version: 10.x
What steps will reproduce the problem?
git clone https://github.com/mrdoob/three.js
npm un puppeteer && npm i -D<EMAIL_ADDRESS>npm install
npm run test-e2e webgl_animation_keyframes

What happens instead?
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (/home/runner/work/three.js/three.js/node_modules/puppeteer/lib/Launcher.js:615:20)
    at Interface.helper.addEventListener (/home/runner/work/three.js/three.js/node_modules/puppeteer/lib/Launcher.js:605:56)
    at Interface.emit (events.js:203:15)
    at Interface.close (readline.js:397:8)
    at Socket.onend (readline.js:173:10)
    at Socket.emit (events.js:203:15)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
(node:2839) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2839) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

我也是病急乱投医，分别执行了
npm un puppeteer
npm i -D puppeteer
npm install

不是很懂这些参数的意义，但解决问题了，期待大佬解释一下发生了什么


Remove need for explicit 'this' when vars are used.

In most other OO langs you do not expect to have to declare that you want to access a member when operating inside a member function. At present ulox requires a lot of 'this.' littered throughout.
For classes that make use of vars, we know those exist in advance and can change the resolution lookup to be locals, then instance then enclosing scopes. E.G. none of the following 'this.' should be required.
class T
{
    var a,b,c;
    init(d)
    {
        this.a = d;
    }

    Sum()
    {
        return this.a + this.b + this.c;
    }

    SumSquared()
    {
        return this.Sum() * this.Sum();
    }
}

Proposed implementation: have the compiler resolution check known vars of the current class when resolving names, if it misses local scope but finds a match in the class it is within, automatically insert the opcodes that equate to get or set property instead of a local or upval.

This get's very trick to keep as compile time only when classes can inherit from an unknown identifier.

When this isn't in order and in the same class declar this becomes tricky or impossible without changing the structure or phases of the compiler. Right now you can inher from a class that hasn't been declared yet as it is resolved at runtime, if you could only inher from known classes then we could automatically insert more this..
The other option is to change runtime resolution but that means a compile time will find outter vars and bind to them if shadowing them with a instance var.

An alternate to consider here; how often do we want to access something outside of the instance when in a method? If we FAR more often want locals and instances, we could instead of requiring this. we could introduce something to signify you want an outter?

To consider here is the concept of function (as in procedure) vs method (as in instance method). If that distinction is made clear then when inside a method looksup can be done differently, e.g. if the resolve fails to find a local it inserts the this.

This seems now tightly related to #83

Resolve looks for a local if it finds one returns byte and get local set local
Then looks for an up, if it finds one returns byte and getup set up
else returns byte and get global set global.
We would need to introduce into  current compiler state for functions a lookup step between local and upval that looks for matching name in the type that the method belongs too, if found return byte, get prop, set prop

the altenative here is the vm understanding that global means context, search the instance requesting a context var, if none or not found, search the vm globals.

We now demand that all classes define vars and are frozen before init, so there is no dynamic problem to deal with.
If we wrap all emitpackets that stem from a resolve, we can write the extra bytes first if it returned get_prop.


100 router match iterations

You can in some rare cases get locked out from frontend and admin with the exception "100 route iterations". This hinders fix will hinder it.

@freestream
Thank you for this PR. Can you split this into two commits, one where you add the core file into community and one where you commit the changes. You can see how it is made in the commit history on this project. This makes future updates and reviews easier.

sure, hold one


cookie path not getting saved

Having explicity set up the path as '/' when setting the cookie
cookies.set(name, value, {  path: '/', expires: expires });
when going to mysite.com/page/
then accepting cookies
checking in the browser the cookie path is '/page/' instead of '/'

can you provide additional step to reproduce? I tried but in my enviroment it fine

I also encounter this sometimes. Hard to track down / reproduce what's causing it, but every now and then my app stops working as expected and the culprit is always a cookie with the path set to where the page was loaded, despite my options being hard-coded to use '/' as a path.

Without a way to reproduce it would be hard to solve. Let me know if there is a way.


add the limit, the cursor cannot be set to a negative number

@geky I don't know why it fails(test/coverage), can you help me take a look?

Hey @Johnxjj, sorry about the late response. I think GitHub is just being flaky, it has had some issues this past month. Nothing looks wrong in your PR.
I think because the CI technically "runs in your fork", I can't restart it, but you might be able to if you see a "re-run all jobs" button in the PR's "checks" tab?
If not, touching the last commit should re-run the CI:
git commit --amend --no-edit
git push origin dev-johnxjj --force

I went ahead and touched the commit to restart CI to see if that fixes it, sorry if this causes any issues.

I also went ahead and removed the check when using LFS_SEEK_SET, due to https://github.com/littlefs-project/littlefs/pull/630#discussion_r810581243

Thanks for the PR!


Figure out why 404 isn't working on carebot site

https://github.com/thecarebot/thecarebot.github.io

aaaargh, this took forever. It magically resolved itself.


Does it support distributed transactions?

Does it support distributed transactions?

Hey @Dark1Forest 👋
This is currently not supported by Ent, but you can implement it with custom custom templates.
Closing, but please feel free to join our Discord community in case you need more help with this 😎


fix(steam-deb): Enable 32 bit support by default

Fixes #838

@Henryws handle this. The CI fails due to i386 errors.

@Henryws

I did a test on a virtual machine and it works well
https://bin.snopyta.org/?8096c735389a0c0c#38hMMR5ef3hx4mVkjVrbToenTtjLdjDCmYXMDNzHPAsW

I did a test on a virtual machine and it works well
bin.snopyta.org/?8096c735389a0c0c#38hMMR5ef3hx4mVkjVrbToenTtjLdjDCmYXMDNzHPAsW

Yup, it's an issue with the CI


Add support for /source/fn

I found this while looking at the latest integration test run with the conversion tooling.

 ╭─ Finding outputs from recipe
 │
 ╰─────────────────── (took 0 seconds)
Error:   × Failed to parse recipe

Error:   × Parsing: invalid field `fn`.
    ╭─[12:3]
 11 │ source:
 12 │   fn: ${{ name }}-${{ version }}.tar.gz
    ·   ─┬
    ·    ╰── here
 13 │   url: https://pypi.org/packages/source/${{ name[0] }}/${{ name }}/${{ name }}-${{ version }}.tar.gz
    ╰────
  help: valid fields for URL `source` are `url`, `sha256`, `md5`, `patches`, `file_name` and `target_directory`

It looks like /source/fn is not currently supported. The only reference I see in the current CEPs to this field is in the example for CEP-13
I think this currently causes a few hundred recipes to fail the dry-run build in the integration tests.
Alternatively if this field is not supposed to be supported, this issue can be closed. But we will need to discuss how the field should be handled in the conversion process.
Thanks!

It took me a while to find what the hell fn is supposed to mean, but I just found the docs: https://docs.conda.io/projects/conda-build/en/stable/resources/define-metadata.html#filename
It's "filename".....I guess I've been writing too much rust lately and kept thinking function :P

Here are the contents of the recipe.yaml that caused the above error:
schema_version: 1

context:
  name: boto
  version: 2.49.0

package:
  name: ${{ name|lower }}
  version: ${{ version }}

source:
  fn: ${{ name }}-${{ version }}.tar.gz
  url: https://pypi.org/packages/source/${{ name[0] }}/${{ name }}/${{ name }}-${{ version }}.tar.gz
  sha256: ea0d3b40a2d852767be77ca343b58a9e3a4b00d9db440efb8da74b4e58025e5a

build:
  number: 0
  script: python setup.py install

requirements:
  host:
    - python
  run:
    - python

tests:
  - python:
      imports:
        - boto
      pip_check: false
  - script:
      - if: py2k
        then: asadmin -h
      - s3put -h
      - if: py2k
        then: taskadmin -h

about:
  license: MIT
  summary: Amazon Web Services Library
  description: |
    Boto aims to support the full breadth and depth of Amazon Web Services.
    NOTE: Boto3, the next version of Boto, is stable and recommended for
    general use.
  homepage: https://github.com/boto/boto/
  repository: https://github.com/boto/boto/
  documentation: http://docs.pythonboto.org/en/latest/

I guess from the description in the conda docs (linked above), this field is likely redundant and we could delete it if the filename matches the end of /source/url. In other cases I could throw a warning for a human to correct the issue.

I believe we implemented this as file_name (or maybe filename).
Yes, the fn is pretty confusing :)
And yes, it can be removed if it matches the URL filename.

Ah okay, it is file_name: https://github.com/conda-incubator/ceps/blob/main/cep-14.md#url-source
I'm not sure if we can (or should) modify the CEP, but it might be nice if we include the fn -> file_name in the doc. I think that's how I missed the change when I was looking for it.

For the sake of completeness, it also looks like folder -> target_directory

yep!

I think we can close this, right?


train_latent RuntimeError: cuDNN error: CUDNN_STATUS_MAPPING_ERROR

run the command as below:
python main.py --attribute mouth_slightly_open --outdir output --image input/1815.jpg

in train_latent  function, when i=30 will raise this error!
  File "/home/tf/.vscode-server/extensions/ms-python.python-2023.2.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 124, in _run_code
    exec(code, run_globals)
  File "/home/tf/PycharmProjects/face/gan/MaskFaceGAN/main.py", line 43, in <module>
    trainer.train_latent()
  File "/home/tf/PycharmProjects/face/gan/MaskFaceGAN/trainer.py", line 92, in train_latent
    loss_sum.backward()
  File "/home/tf/miniconda3/envs/py39/lib/python3.9/site-packages/torch/_tensor.py", line 488, in backward
    torch.autograd.backward(
  File "/home/tf/miniconda3/envs/py39/lib/python3.9/site-packages/torch/autograd/__init__.py", line 197, in backward
    Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: cuDNN error: CUDNN_STATUS_MAPPING_ERROR

my python3.9 env:
# Name                    Version                   Build  Channel
pytorch-lightning         1.8.6                    pypi_0    pypi
torch                     1.13.1+cu117             pypi_0    pypi
torchaudio                0.13.1+cu117             pypi_0    pypi
torchmetrics              0.11.0                   pypi_0    pypi
torchvision               0.14.1+cu117             pypi_0    pypi

The stylegan2-ffhq-config-f.pt download from https://zenodo.org/record/4536928#.Y_McH3ZBxPZ
Thank you very much for your reply :heart_eyes: !

Hi,
What is your GPU? Can you paste the output of nvidia-smi? Make sure to
install the appropriate CUDA drivers for your GPU.
Best,
Martin
On Mon, 20 Feb 2023 at 08:26, blakeliu @.***> wrote:

run the command as below:
python main.py --attribute mouth_slightly_open --outdir output --image input/1815.jpg
in train_latent function, when i=30 will raise this error!
File "/home/tf/.vscode-server/extensions/ms-python.python-2023.2.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 124, in _run_code
exec(code, run_globals)

File "/home/tf/PycharmProjects/face/gan/MaskFaceGAN/main.py", line 43, in
trainer.train_latent()

File "/home/tf/PycharmProjects/face/gan/MaskFaceGAN/trainer.py", line 92, in train_latent
loss_sum.backward()

File "/home/tf/miniconda3/envs/py39/lib/python3.9/site-packages/torch/_tensor.py", line 488, in backward
torch.autograd.backward(

File "/home/tf/miniconda3/envs/py39/lib/python3.9/site-packages/torch/autograd/init.py", line 197, in backward
Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass

RuntimeError: cuDNN error: CUDNN_STATUS_MAPPING_ERROR
my python3.9 env:
Name                    Version                   Build  Channel
pytorch-lightning         1.8.6                    pypi_0    pypi
torch                     1.13.1+cu117             pypi_0    pypi
torchaudio                0.13.1+cu117             pypi_0    pypi
torchmetrics              0.11.0                   pypi_0    pypi
torchvision               0.14.1+cu117             pypi_0    pypi
The stylegan2-ffhq-config-f.pt download from
https://zenodo.org/record/4536928#.Y_McH3ZBxPZ
Thank you very much for your reply 😍 !
—
Reply to this email directly, view it on GitHub
https://github.com/MartinPernus/MaskFaceGAN/issues/8, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIZIL5YBZ2MN2WQGC4KVYSLWYMMA5ANCNFSM6AAAAAAVBQSG4I
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Mon Feb 20 17:40:49 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.82.01    Driver Version: 470.82.01    CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce RTX 3090  On   | 00000000:65:00.0 Off |                  N/A |
| 33%   29C    P8    34W / 350W |   2499MiB / 24259MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA GeForce GTX 1080 Ti  On   | 00000000:B7:00.0 Off |                  N/A |
| 47%   20C    P8     8W / 250W |     13MiB / 11178MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

in config.yml,  device modified :
device: cuda:1

Oh,  I found NVIDIA GeForce RTX 3090 runs successfully!

It seems your installed pytorch version requires CUDA 11.7, but yours is
11.4. Could you first try by installing CUDA 11.7 or newer and try again?
Best,
Martin
On Mon, 20 Feb 2023 at 10:45, blakeliu @.***> wrote:

Mon Feb 20 17:40:49 2023
+-----------------------------------------------------------------------------+| NVIDIA-SMI 470.82.01    Driver Version: 470.82.01    CUDA Version: 11.4     ||-------------------------------+----------------------+----------------------+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC || Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. ||                               |                      |               MIG M. ||===============================+======================+======================||   0  NVIDIA GeForce RTX 3090  On   | 00000000:65:00.0 Off |                  N/A || 33%   29C    P8    34W / 350W |   2499MiB / 24259MiB |      0%      Default ||                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+|   1  NVIDIA GeForce GTX 1080 Ti  On   | 00000000:B7:00.0 Off |                  N/A || 47%   20C    P8     8W / 250W |     13MiB / 11178MiB |      0%      Default ||                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
in config.yml, device modified :
device: cuda:1
—
Reply to this email directly, view it on GitHub
https://github.com/MartinPernus/MaskFaceGAN/issues/8#issuecomment-1436645070,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIZIL5YEMBJXDZ4MBI73JKLWYM4K5ANCNFSM6AAAAAAVBQSG4I
.
You are receiving this because you commented.Message ID:
@.***>

Great!
On Mon, 20 Feb 2023 at 10:48, Martin Pernus @.***>
wrote:

It seems your installed pytorch version requires CUDA 11.7, but yours is
11.4. Could you first try by installing CUDA 11.7 or newer and try again?
Best,
Martin
On Mon, 20 Feb 2023 at 10:45, blakeliu @.***> wrote:

Mon Feb 20 17:40:49 2023
+-----------------------------------------------------------------------------+| NVIDIA-SMI 470.82.01    Driver Version: 470.82.01    CUDA Version: 11.4     ||-------------------------------+----------------------+----------------------+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC || Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. ||                               |                      |               MIG M. ||===============================+======================+======================||   0  NVIDIA GeForce RTX 3090  On   | 00000000:65:00.0 Off |                  N/A || 33%   29C    P8    34W / 350W |   2499MiB / 24259MiB |      0%      Default ||                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+|   1  NVIDIA GeForce GTX 1080 Ti  On   | 00000000:B7:00.0 Off |                  N/A || 47%   20C    P8     8W / 250W |     13MiB / 11178MiB |      0%      Default ||                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
in config.yml, device modified :
device: cuda:1
—
Reply to this email directly, view it on GitHub
https://github.com/MartinPernus/MaskFaceGAN/issues/8#issuecomment-1436645070,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIZIL5YEMBJXDZ4MBI73JKLWYM4K5ANCNFSM6AAAAAAVBQSG4I
.
You are receiving this because you commented.Message ID:
@.***>


[BUG][OTHER] Initial ASEA install version truncated from parameter store history

Required Basic Info

Accelerator Version:  v1.2.4
Install Type: Upgrade
Install Branch: Standalone

Describe the bug

if you upgrade (or run the CodePipeline) more than 100 times, the original installation version of ASEA is truncated.
at this time, this is a Developer issue (no prod customer has been through more than ~5 upgrades)
the ASEA version number is sometimes used to change historic functionality for new customer while not breaking existing customers (used extremely rarely)
add a new initial install version parameter in parameter store and populate on all new installs only (i.e. no current version parameter), in addition to the current version parameter
for existing installs, if initial install version parameter is empty or no exist, copy the oldest version from history of current version parameter to the initial install version parameter

Shipping in v1.2.5

Shipping in v1.2.5


minor refactor of DatastoreDao

comment and move stuff around in app.yaml
more comments in pom.xml
Minor refactor of DatastoreDao

@shun-fan PTAL

lgtm


Fix detect_spec_version() with respect to 2.0 bundles

Fixes #541 .
Fix detect_spec_version() such that it uses presence of the "spec_version" property in a bundle to infer spec version, not the property's value.  Update unit tests accordingly.
Content was discovered which consisted of a bundle with spec_version="2.1".  This is (perhaps confusingly) a STIX 2.0 bundle, but it was incorrectly being identified by the library as a STIX 2.1 bundle.  This produced the following error when parsing it:
stix2.exceptions.ExtraPropertiesError: Unexpected properties for Bundle: (spec_version).

because STIX 2.1 bundles don't have a spec_version property.  The object's spec_version property was used to determine that it should not have a spec_version property.  Doesn't make much sense.  With this PR, you get:
stix2.exceptions.InvalidValueError: Invalid value for Bundle 'spec_version': must equal '2.0'.

This is correct: the library defines the spec_version property of STIX 2.0 bundles to have a fixed value of "2.0", since content of other spec versions is not supported in a STIX 2.0 bundle by this library.  This shows the spec version of the bundle was properly detected.

Codecov Report

Merging #542 (b5260c9) into master (17445a0) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #542      +/-   ##
==========================================
- Coverage   87.29%   87.29%   -0.01%
==========================================
  Files         153      153
  Lines       18033    18035       +2
==========================================
+ Hits        15742    15743       +1
- Misses       2291     2292       +1

Impacted Files
Coverage Δ

stix2/test/test_spec_version_detect.py
100.00% <ø> (ø)

stix2/test/v20/test_utils.py
100.00% <ø> (ø)

stix2/test/v21/test_utils.py
100.00% <ø> (ø)

stix2/utils.py
79.32% <100.00%> (+0.20%)
:arrow_up:

stix2/datastore/taxii.py
68.50% <0.00%> (-0.79%)
:arrow_down:

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 17445a0...b5260c9. Read the comment docs.


[NUMBERS-133] Use iteration algorithm from bounded trial division in Primes.nextPrime(int)

I'm not sure if "potentialPrimes" is a good name for the method that generates the iterator, because it doesn't reveal anything about the purpose of the argument (a lower bound). However, "potentialPrimesBeyond" or something similar would be wrong, because the argument itself is also included in the possible range of results. The most descriptive name would be "potentialPrimesGreaterThanOrEqualTo", but this is horribly verbose. "potentialPrimesNotSmallerThan" is only slightly less verbose, and it contains a negation, which is confusing. So I've left it at "potentialPrimes", but any better suggestions are welcome. At least it's a package-private method, so the method name could still be changed any time in the future.

Coverage increased (+0.002%) to 94.257% when pulling 53010235fc00bf6d80a497feb950c5ff3322db14 on Schamschi:NUMBERS-133 into 08962e853b9843d0ad98e66241fef6cc7d69faeb on apache:master.

How about potentialPrimesGTE? The javadoc can just contain (GTE) in brackets after the greater than or equal to text.
GTE

@aherbert That sounds like I good idea. I had also thought about using an abbreviation, but I only considered the one from the LaTeX tag "geq", which would probably have been too LaTeX specific. I don't know how common "gte" is, but chances are it will still prevent more confusion than it causes. Thanks.

@Schamschi  The merge of this has been missed. Would you care to rebase this on the current master?


[Feature] Blue/Green Deployment

Need fiture support blue/green deployment

Hi @abdidarmawan007 thanks for the suggestion. Blue/Green deployment is beyond the scope of this plugin, however this plugin does provide a primitive which could be used in this scenario. I'd suggest taking a look at this article published by CloudBees on the topic: https://www.cloudbees.com/blog/blue-green-deployments-jenkins-and-blue-green-command


How to make fields displayed? (fields omitted)

I want the fields to be displayed. I do not want to open [src] in layers to see the fields. There is no option in the settings for displaying structure fields. Add the ability to enable / disable structure fields.

This is an issue with rustdoc, not with docs.rs. Can you open this issue in https://github.com/rust-lang/rust instead?


Update integration tests to use modern Kafka v3.2

Docker image has been changed from wurstmeister to bitnami because the
former only provides kafka v2.8.
Topic creation has been added to pytest script due to bitnami's image lack of
automatic topic creation.

Codecov Report

Merging #170 (bd2a19b) into main (2a6974c) will not change coverage.
The diff coverage is n/a.


Support for Ubuntu/Debian

Well, it's the most popular and widely used distro, so why not?

Already done in #10


New ipp-1.1 tests: resolve issues...

We have an updated IPP/1.1 test file from one of the GSoC 2018 students:
ipp-1.1.V2.test.txt
Right now I'm seeing some errors when run against ippserver, but we need to resolve whether the issue is in the test file or ippserver:
../tools/ipptool -Itf ../examples/document-letter.pdf -d document-uri=https://ftp.pwg.org/pub/pwg/ipp/examples/originals/document-letter.pdf ipp://localhost:8501/ipp/print ~/Desktop/ipp-1.1.V2.test
"/Users/msweet/Desktop/ipp-1.1.V2.test":
    RFC 8011 section 4.1.1: Bad request-id value 0                       [PASS]
    RFC 8011 section 4.1.4: No Operation Attributes                      [PASS]
    RFC 8011 section 4.1.4: attributes-charset                           [PASS]
    RFC 8011 section 4.1.4: attributes-natural-language                  [PASS]
    RFC 8011 section 4.1.4: attributes-natural-language + attributes-cha [PASS]
    RFC 8011 section 4.1.4: attributes-charset + attributes-natural-lang [PASS]
    RFC 8011 section 4.1.8: Unsupported IPP version 0.0                  [PASS]
    RFC 8011 section 4.2: No printer-uri operation attribute             [PASS]
    RFC 8011 section 4.2.1: Print-Job Operation                          [PASS]
    RFC 8011 section 4.2.3: Validate-Job Operation                       [PASS]
    RFC 8011 section 4.2.5: Get-Printer-Attributes Operation (default)   [PASS]
        color-supported (boolean) = false
        compression-supported (1setOf keyword) = deflate,gzip,none
        document-format-supported (1setOf mimeMediaType) = application/pdf,image/jpeg,image/pwg-raster
        finishings-supported (enum) = none
        ipp-versions-supported (1setOf keyword) = 1.0,1.1,2.0,2.1,2.2
        media-supported (1setOf keyword) = na_letter_8.5x11in,na_legal_8.5x14in,iso_a4_210x297mm
        number-up-supported (integer) = 1
        operations-supported (1setOf enum) = Print-Job,Print-URI,Validate-Job,Create-Job,Send-Document,Send-URI,Cancel-Job,Get-Job-Attributes,Get-Jobs,Get-Printer-Attributes,Hold-Job,Release-Job,Pause-Printer,Resume-Printer,Set-Printer-Attributes,Set-Job-Attributes,Get-Printer-Supported-Values,Create-Printer-Subscriptions,Create-Job-Subscriptions,Get-Subscription-Attributes,Get-Subscriptions,Renew-Subscription,Cancel-Subscription,Get-Notifications,Enable-Printer,Disable-Printer,Pause-Printer-After-Current-Job,Hold-New-Jobs,Release-Held-New-Jobs,Restart-Printer,Shutdown-Printer,Startup-Printer,Cancel-Current-Job,Cancel-Document,Get-Document-Attributes,Get-Documents,Set-Document-Attributes,Cancel-Jobs,Cancel-My-Jobs,Close-Job,Identify-Printer,Validate-Document,Acknowledge-Document,Acknowledge-Identify-Printer,Acknowledge-Job,Fetch-Document,Fetch-Job,Get-Output-Device-Attributes,Update-Active-Jobs,Update-Document-Status,Update-Job-Status,Update-Output-Device-Attributes,Deregister-Output-Device
        pages-per-minute (integer) = 0
        print-quality-supported (1setOf enum) = draft,normal,high
        printer-uri-supported (uri) = ipp://msweet-imac.local.:8501/ipp/print
        reference-uri-schemes-supported (1setOf uriScheme) = ftp,http,https
        uri-authentication-supported (keyword) = none
        uri-security-supported (keyword) = tls
    RFC 8011 section 4.2.5: Get-Printer-Attributes Operation (requested- [PASS]
    RFC 8011 section 4.2.6: Get-Jobs Operation (default)                 [PASS]
    RFC 8011 section 4.2.6: Get-Jobs Operation (requested-attributes)    [PASS]
    RFC 8011 section 4.2.6: Get-Jobs Operation (my-jobs)                 [PASS]
    RFC 8011 section 4.2.6: Get-Jobs Operation (my-jobs different user)  [PASS]
    RFC 8011 section 4.2.6: Get-Jobs Operation (which-jobs=not-completed [PASS]
    Get-Job-Attributes Until Job Complete                                [0001]
        job-state (enum) = processing
    Get-Job-Attributes Until Job Complete                                [PASS]
        job-state (enum) = completed
    RFC 8011 section 4.2.6: Get-Jobs Operation (which-jobs=completed)    [PASS]
    RFC 8011 section 4.2.6: Get-Jobs Operation (which-jobs, requested-at [PASS]
    RFC 8011 section 4.3.3: Cancel-Job Operation (completed job)         [PASS]
    RFC 8011 section 4.2.1: Print-Job Operation                          [PASS]
    RFC 8011 section 4.3.3: Cancel-Job Operation (pending/processing job [PASS]
    RFC 8011 section 4.3.4: Get-Job-Attributes Operation                 [PASS]
    RFC 8011 section 4.2.2: Print-URI Operation                          [FAIL]
        RECEIVED: 93 bytes in response
        status-code = successful-ok (successful-ok)
        EXPECTED: job-uri
        EXPECTED: job-id
        EXPECTED: job-state
        EXPECTED: job-state-reasons
    Print-URI with bad URI: Print-URI Operation                          [FAIL]
        RECEIVED: 93 bytes in response
        status-code = successful-ok (successful-ok)
        EXPECTED: STATUS client-error-uri-scheme-not-supported (got successful-ok)
    RFC 8011 section 4.2.4: Create-Job Operation                         [PASS]
    RFC 8011 section 4.3.1: Send-Document Operation                      [PASS]
    Send-Document missing last-document: Create-Job Operation            [PASS]
    Send-Document missing last-document: Send-Document Operation         [PASS]
    RFC 8011 section 4.3.3: Cancel-Job Operation                         [PASS]
    RFC 8011 section 4.2.4: Create-Job Operation                         [PASS]
    RFC 8011 section 4.3.2: Send-URI Operation                           [FAIL]
        RECEIVED: 0 bytes in response
        status-code = server-error-service-unavailable (Operation now in progress)
        IPP request failed with status server-error-service-unavailable (Operation now in progress)
    Send-URI with bad URI: Create-Job Operation                          [PASS]
    Send-URI with bad URI: Send-URI Operation (bad URI)                  [FAIL]
        RECEIVED: 0 bytes in response
        status-code = server-error-service-unavailable (Address already in use)
        IPP request failed with status server-error-service-unavailable (Address already in use)
    Send-URI with bad URI: Cancel-Job Operation                          [SKIP]
    RFC 8011 section 4.2.7: Pause-Printer Operation                      [PASS]
    Resume-Printer                                                       [PASS]
    RFC 8011 section 4.2.1: Print-Job Operation                          [PASS]
    RFC 8011 section 4.3.5: Hold-Job operation                           [PASS]
    Release-Job                                                          [PASS]
    RFC 8011 section 4.2.4: Create-Job Operation                         [FAIL]
        RECEIVED: 102 bytes in response
        status-code = successful-ok (successful-ok)
        EXPECTED: job-uri
        EXPECTED: job-id
        EXPECTED: job-state
        EXPECTED: job-state-reasons
    RFC 8011 section 4.3.1: Send-Document Operation                      [FAIL]
        RECEIVED: 121 bytes in response
        status-code = client-error-not-possible (Job is not in a pending state.)
        EXPECTED: STATUS successful-ok (got client-error-not-possible)
        EXPECTED: STATUS client-error-document-format-not-supported (got client-error-not-possible)
        EXPECTED: STATUS server-error-job-canceled (got client-error-not-possible)
        status-message="Job is not in a pending state."
    Print-Job with copies                                                [PASS]
    Print-Job with A4 PDF                                                [PASS]
    Print-Job with A4 PDF, Duplex                                        [SKIP]
    Print-Job with US Letter PDF                                         [PASS]
    Print-Job with US Letter PDF, Duplex                                 [SKIP]
    Print-Job with A4 PostScript                                         [SKIP]
    Print-Job with A4 PostScript, Duplex                                 [SKIP]
    Print-Job with US Letter PostScript                                  [SKIP]
    Print-Job with US Letter PostScript, Duplex                          [SKIP]
    Print-Job with Color JPEG on A4                                      [PASS]
    Print-Job with Color JPEG on US Letter                               [PASS]
    Print-Job with Color JPEG on 4x6                                     [SKIP]
    Print-Job with Grayscale JPEG on A4                                  [PASS]
    Print-Job with Grayscale JPEG on US Letter                           [PASS]
    Print-Job with Grayscale JPEG on 4x6                                 [SKIP]
    Print-Job with A4 PDF and Standard Sheet                             [SKIP]
    Print-Job with US Letter PDF and Standard Sheet                      [SKIP]
    Print-Job with A4 PDF and Standard Sheet                             [SKIP]
    Print-Job with US Letter PDF and Standard Sheet                      [SKIP]
    Print-Job with A4 PDF, 2-Up                                          [SKIP]
    Print-Job with US Letter PDF, 2-Up                                   [SKIP]
    Print-Job with A4 PDF, 2-Up                                          [SKIP]
    Print-Job with US Letter PDF, 2-Up                                   [SKIP]
    Print-Job with JPEG on 4x6, Draft Quality                            [SKIP]
    Print-Job with JPEG on 4x6, Normal Quality                           [SKIP]
    Print-Job with JPEG on 4x6, High Quality                             [SKIP]
    Print-Job with A4 PDF, Draft Quality                                 [PASS]
    Print-Job with US Letter PDF, Draft Quality                          [PASS]
    Print-Job with job-hold-until                                        [FAIL]
        RECEIVED: 102 bytes in response
        status-code = successful-ok (successful-ok)
        EXPECTED: job-uri
        EXPECTED: job-id
        EXPECTED: job-state
        EXPECTED: job-state-reasons
    Release-Job                                                          [PASS]
    Print-Job with explicit priority                                     [PASS]
    Print-Job with single-document multiple-document-handling            [SKIP]
    Print-Job with separate-documents-uncollated-copies multiple-documen [PASS]
    Print-Job with separate-documents-collated-copies multiple-document- [SKIP]
    Print-Job with ssingle-document-new-sheet multiple-document-handling [SKIP]
    Print-Job with no finishing                                          [PASS]
    Print-Job with staple                                                [SKIP]
    Print-Job with punch                                                 [SKIP]
    Print-Job with cover                                                 [SKIP]
    Print-Job with bind                                                  [SKIP]
    Print-Job with saddle-stitch                                         [SKIP]
    Print-Job with edge-stitch                                           [SKIP]
    Print-Job with staple-top-left                                       [SKIP]
    Print-Job with staple-bottom-left                                    [SKIP]
    Print-Job with staple-top-right                                      [SKIP]
    Print-Job with staple-bottom-right                                   [SKIP]
    Print-Job with edge-stitch-left                                      [SKIP]
    Print-Job with edge-stitch-top                                       [SKIP]
    Print-Job with edge-stitch-right                                     [SKIP]
    Print-Job with edge-stitch-bottom                                    [SKIP]
    Print-Job with staple-dual-left                                      [SKIP]
    Print-Job with staple-dual-top                                       [SKIP]
    Print-Job with staple-dual-right                                     [SKIP]
    Print-Job with staple-dual-bottom                                    [SKIP]
    Print-Job with two-sided-long-edge side                              [SKIP]
    Print-Job with two-sided-short-edge side                             [SKIP]
    Print-Job with portrait orientation                                  [PASS]
    Print-Job with landscape orientation                                 [PASS]
    Print-Job with portrait orientation                                  [PASS]
    Print-Job with portrait orientation                                  [PASS]
    Print-Job with 600dpi resolution                                     [SKIP]

Summary: 104 tests, 53 passed, 7 failed, 44 skipped
Score: 93%

[master 8a27bf2] Resolve IPP/1.1 test issues (Issue #150)


Removing title field from dropdown in content view

Fixes #1107

@iFlameing Can you resolve conflicts for this one?


Investigate correctness of data, masking, and accuracy in pretraining

Everything seems correct. Word masking, entity masking, and entity spans all behave as expected


Fishing

You guys should add the fishing feature from Sea of Thieves

No, That would be out of scope. I think there are mods already do that.

I'm still looking for one that makes an entity bit the line for you to reel it in


Visual color selection

Thanks for your excellent work!
I have observed that the visualization colors in your work are very attractive. Could you please introduce your visualization methods and color selection?
Thank you!!

Hi, thanks for your interests! We use Mitsuba2 for rendering point cloud, check these out: https://github.com/mitsuba-renderer/mitsuba2 and https://github.com/chrdiller/mitsuba-visualize

Thanks!!


Build failure: rst2pdf

Steps To Reproduce
Steps to reproduce the behavior:

build rst2pdf

Build log
https://gist.github.com/montchr/44485c82b551e8e865eeb302ca107236
Additional context
Nope
Notify maintainers
currently none (formerly marsam)
@tjni (only because you were the last person aside from marsam to touch the code outside of a treewide refactor)
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"aarch64-linux"`
 - host os: `Linux 6.6.0-asahi, NixOS, 24.05 (Uakari), 24.05.20240421.6143fc5`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/6p54rs6k28x3s10clhljpv01jp6x3ibi-cc0ribc27c349w1v2anrby7z8kigy5pq-source`

Add a :+1: reaction to issues you find important.

Should be fixed by #309438