Improve monitor creating, handle errors

What is the purpose of the change
Fix the problem that if an exception is thrown when creating a monitor, it is not handled correctly.
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #7867 (c04fc43) into master (2dace54) will decrease coverage by 0.33%.
The diff coverage is 70.00%.

@@             Coverage Diff              @@
##             master    #7867      +/-   ##
============================================
- Coverage     59.60%   59.27%   -0.34%
+ Complexity      556      555       -1
============================================
  Files          1088     1088
  Lines         43854    43800      -54
  Branches       6400     6367      -33
============================================
- Hits          26140    25961     -179
- Misses        14814    14949     +135
+ Partials       2900     2890      -10

Impacted Files
Coverage Δ

.../dubbo/monitor/support/AbstractMonitorFactory.java
80.00% <70.00%> (+1.62%)
:arrow_up:

...a/org/apache/dubbo/rpc/filter/AccessLogFilter.java
28.35% <0.00%> (-50.75%)
:arrow_down:

...va/org/apache/dubbo/rpc/support/AccessLogData.java
53.16% <0.00%> (-37.98%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
68.96% <0.00%> (-27.59%)
:arrow_down:

...rg/apache/dubbo/remoting/utils/PayloadDropper.java
76.92% <0.00%> (-15.39%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
43.47% <0.00%> (-15.22%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
:arrow_down:

...che/dubbo/remoting/transport/mina/MinaChannel.java
35.52% <0.00%> (-10.53%)
:arrow_down:

.../apache/dubbo/rpc/protocol/AsyncToSyncInvoker.java
62.06% <0.00%> (-10.35%)
:arrow_down:

...dubbo/remoting/exchange/support/DefaultFuture.java
77.87% <0.00%> (-9.31%)
:arrow_down:

... and 35 more

Continue to review full report at Codecov.

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


Change to YAML files as config

Hello @kaulketh! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file logger/__init__.py:

Line 6:41: W291 trailing whitespace
Line 7:32: W291 trailing whitespace


on_raw_004 "not enough values to unpack"

ERROR:MyOwnBot:chat.example:Failed to execute on_raw_004 handler.
Traceback (most recent call last):
  File "...pydle\client.py", line 422, in on_raw
    await handler(message)
  File "...\pydle\features\rfc1459\client.py", line 762, in on_raw_004
    target, hostname, ircd, user_modes, channel_modes = message.params[:5]
ValueError: not enough values to unpack (expected 5, got 2)

@bukowa Can you give me some context on how you reached this state?

@theunkn0wn1 its just because
len(message.params) < 5

in my case this happens in welcome message, just before on_connect

insufficient information to reproduce, closing as stale.


Empty metadata for OPTIONS /materialized_view

Materialized views can be queried and that works, but they do not show up in the root list of tables, and if you do an OPTIONS request on one the columns array comes back empty

It seems that materialized views don't appear in the information_schema. To solve this we need to extract metadata from the pg_catalog.
@begriffs is there any particular reason for using the information_schema (besides being more stable across versions) ?

No reason, I think information_schema was the first thing I discovered (probably on stack overflow or something). Switching to pg_catalog is fine by me.

If a regular view appears in the information_schema but materialized views
do not, we may want to raise that issue with the Postgres project. I can't
think of a good reason off hand why that would be the case.
-- Ben
On Sat, Aug 1, 2015 at 11:39 AM, Diogo Biazus<EMAIL_ADDRESS>wrote:

It seems that materialized views don't appear in the information_schema.
To solve this we need to extract metadata from the pg_catalog.
@begriffs https://github.com/begriffs is there any particular reason
for using the information_schema (besides being more stable across
versions) ?
—
Reply to this email directly or view it on GitHub
https://github.com/begriffs/postgrest/issues/242#issuecomment-126861757.

@scherrey the PostgreSQL seem to be aware of the issue: http://postgresql.nabble.com/Re-Materialized-views-WIP-patch-td5740513i40.html
Probably was not implemented yet as the information schema is more of a standards compliance feature and most PG tools actually rely on the pg_catalog.

FYI I believe this was fixed in release v<IP_ADDRESS>

I haven't tested that release, but the changelog only mentions adding materialized views to GET /, the other part of the issue is that OPTIONS requests don't return structure details for them

You're right, I just confirmed it.
GET http://localhost:3000/materialized_view

responds
[
  {
    "version": "PostgreSQL 9.4.1 on x86_64-apple-darwin14.1.0, compiled by Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn), 64-bit"
  }
]

But OPTIONS returns
{
  "pkey": [],
  "columns": []
}

and I'm expecting columns to include version.
The view is defined as
CREATE MATERIALIZED VIEW test.materialized_view AS
 SELECT version() AS version
WITH DATA;

@begriffs any update on this issue?

@rtluckie not yet, but I acknowledge it's a problem. Adding the "bug" label.

Closing this since OPTIONS no longer exists, Everything was moved to openApi response on the /.
Another avenue to implement this using your custom rpc/view with a query similar to this https://gist.github.com/ruslantalpa/b2f10eb1b5f6dd0fc1c154e071a1c91b


Copy statics

Changes in this PR provide access to original static fields for further reusage.
@themr('Foo')
class Foo extends React.Component {
	static propTypes = {
		foo: React.PropTypes.array
	}
	static defaultProps = {
		foo: []
	}
}

@themr('Bar')
class Bar extends React.Component {
	static propTypes = {
		...Foo.propTypes
	}

	static defaultProps = {
		...Foo.defaultProps
	}
}

Technical details:
@themr's injected propTypes go after original so they always override propTypes with "reserverd" keys like theme etc.

👍 !


Make get_snapshot_file() public and more flexible

To make the function usable in another way: Rename _get_snapshot_file() and make the hardcoded .snapshot changeable.

Codecov Report

Merging #173 (7aabc3a) into master (266b73a) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##           master     #173   +/-   ##
=======================================
  Coverage   93.52%   93.53%
=======================================
  Files          42       42
  Lines        1251     1252    +1
  Branches      207      207
=======================================
+ Hits         1170     1171    +1
  Misses         81       81

Impacted Files
Coverage Δ

bx_py_utils/test_utils/snapshot.py
97.33% <100.00%> (+0.01%)
:arrow_up:


[explorer] - various small bugfixes

Description
Describe the changes or additions included in this PR.
Test Plan
How did you test the new or updated feature?

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

Current dependencies on/for this PR:

main

PR #10818   👈

This comment was auto-generated by Graphite.


Fixed README and config path/tag

Fixed typo in README and added tag to config to prevent publish all vendor configs.
Also changed path for default config.

Thank you !


Add perplexity; resolves #35

@swyxio Nearly there with perplexity but for some reason I can't get the submit to work yet

var nativeTextAreaValueSetter = Object.getOwnPropertyDescriptor(window.HTMLTextAreaElement.prototype, "value").set;
nativeTextAreaValueSetter.call(inputElement, 'This should be in state');
const event = new Event('input', { bubbles: true});
inputElement.dispatchEvent(event);
https://stackoverflow.com/a/61110332

just gonna ship this for now, we can add perplexity llama as a separate provider if we feel like it


Wrong sails env after start

debug: Detected Sails environment is "production", but NODE_ENV is undefined.

Fixed in ba293b3


ADBDEV-5579: checking python packages packaged in rpm

PR to run CI with rpm packages instead of packages from pypl.

Failed job Build for ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1387822

And who will maintain these RPMs?


CSVDataset sample misses availableSize() and prepare(Progress progress)

how_to_use_dataset.md contains the sample code CSVDataset. Unfortunately the implementations for availableSize() and prepare(Progress progress) are missing. How would a proper implementation look like?

@deki good catch.
You can find example in this demo: https://github.com/aws-samples/djl-demo/blob/master/malicious-url-detector/src/main/java/com/example/CSVDataset.java#L86
and
https://github.com/aws-samples/djl-demo/blob/master/malicious-url-detector/src/main/java/com/example/CSVDataset.java#L124
Would you mind raise a PR to address this issue?


feat/foundation-complete

I don't know what [flutter_01.png] is ? (I did upgrade Flutter)
Sensor screen needs chart and onChanged/dynamic functionality,
Home screen still needs to initialise better (flashes red screen when opening)
Need to think about saving thirst level and "sensor state" upon reading moisture data for notifications/alerts/icons
Need to think about battery level
Waiting for image routes

Looks amazing!

you probably just fat fingered keys in the flutter console. Respectively:
s: took a screenshot. that's what flutter_01.png comes from.
j: Dump frame raster stats for the current frame. that's where flutter_hank_metrics_01.json comes from.
deleted both files for you and force pushed

fixed the red flashing screen on home screen. basically just initialize mySensors to a empty list. also added some comments as a TODO reminder for both of us in the future


python311Packages.google-cloud-artifact-registry: 1.10.0 -> 1.11.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.google-cloud-artifact-registry is: Google Cloud Artifact Registry API client library
meta.homepage for python311Packages.google-cloud-artifact-registry is: https://github.com/googleapis/google-cloud-python/tree/main/packages/google-cloud-artifact-registry
meta.changelog for python311Packages.google-cloud-artifact-registry is: https://github.com/googleapis/google-cloud-python/blob/google-cloud-artifact-registry-v1.11.0/packages/google-cloud-artifact-registry/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.11.0 with grep in /nix/store/fwirlgfskl56kq5dbisgnc6sfivyllip-python3.11-google-cloud-artifact-registry-1.11.0
found 1.11.0 in filename of file in /nix/store/fwirlgfskl56kq5dbisgnc6sfivyllip-python3.11-google-cloud-artifact-registry-1.11.0

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.dalle-mini
python311Packages.fastai
python311Packages.google-cloud-artifact-registry
python311Packages.k-diffusion
python311Packages.skrl
python311Packages.spacy
python311Packages.spacy-loggers
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.textacy
python311Packages.textnets
python311Packages.wandb
tts

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fwirlgfskl56kq5dbisgnc6sfivyllip-python3.11-google-cloud-artifact-registry-1.11.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.google-cloud-artifact-registry https://github.com/r-ryantm/nixpkgs/archive/13d7669a4a0b954df31af09bf0e54a0e6fde73da.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/13d7669a4a0b954df31af09bf0e54a0e6fde73da#python311Packages.google-cloud-artifact-registry

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fwirlgfskl56kq5dbisgnc6sfivyllip-python3.11-google-cloud-artifact-registry-1.11.0
ls -la /nix/store/fwirlgfskl56kq5dbisgnc6sfivyllip-python3.11-google-cloud-artifact-registry-1.11.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages failed to build:

python311Packages.dalle-mini
python311Packages.k-diffusion
python311Packages.textacy
python311Packages.textnets
tts

8 packages built:

python311Packages.fastai
python311Packages.google-cloud-artifact-registry
python311Packages.skrl
python311Packages.spacy
python311Packages.spacy-loggers
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.wandb

Maintainer pings
cc @samuela for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.google-cloud-artifact-registry is: Google Cloud Artifact Registry API client library
meta.homepage for python311Packages.google-cloud-artifact-registry is: https://github.com/googleapis/google-cloud-python/tree/main/packages/google-cloud-artifact-registry
meta.changelog for python311Packages.google-cloud-artifact-registry is: https://github.com/googleapis/google-cloud-python/blob/google-cloud-artifact-registry-v1.11.1/packages/google-cloud-artifact-registry/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.11.1 with grep in /nix/store/qddlhbky3vq679k9lyvsizv3nj8fg9z4-python3.11-google-cloud-artifact-registry-1.11.1
found 1.11.1 in filename of file in /nix/store/qddlhbky3vq679k9lyvsizv3nj8fg9z4-python3.11-google-cloud-artifact-registry-1.11.1

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.dalle-mini
python311Packages.fastai
python311Packages.google-cloud-artifact-registry
python311Packages.k-diffusion
python311Packages.skrl
python311Packages.spacy
python311Packages.spacy-loggers
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.textacy
python311Packages.textnets
python311Packages.wandb
tts

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qddlhbky3vq679k9lyvsizv3nj8fg9z4-python3.11-google-cloud-artifact-registry-1.11.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.google-cloud-artifact-registry https://github.com/r-ryantm/nixpkgs/archive/a41d4390390708f13c1809ffae94f4d5702ca345.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a41d4390390708f13c1809ffae94f4d5702ca345#python311Packages.google-cloud-artifact-registry

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qddlhbky3vq679k9lyvsizv3nj8fg9z4-python3.11-google-cloud-artifact-registry-1.11.1
ls -la /nix/store/qddlhbky3vq679k9lyvsizv3nj8fg9z4-python3.11-google-cloud-artifact-registry-1.11.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages failed to build:

python311Packages.dalle-mini
python311Packages.textacy
python311Packages.textnets
tts

9 packages built:

python311Packages.fastai
python311Packages.google-cloud-artifact-registry
python311Packages.k-diffusion
python311Packages.skrl
python311Packages.spacy
python311Packages.spacy-loggers
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.wandb

Maintainer pings
cc @samuela for testing.

Failures are expected based on Hydra, with the exception of tts which I could not find in the Hydra jobs tab for some reason.


Fix synopsis remover in importer

MAL updated their "No synopsis" message again.
Ex.
https://hummingbird.me/manga/koi-wa-ameagari-no-you-ni
https://hummingbird.me/manga/youkoso-jitsuryoku-shijou-shugi-no-kyoushitsu-e

Why does xinil have to make it so hard to steal his data!? :+1: LGTM


Improve releasing during v0.11.2

This is now finally there! Merging so that we I can focus on this one next:

https://github.com/dagger/dagger/pull/7082

This weekend is perfect for this type of maintenance work 🧑🔧


Panic on CSPRNG error instead of returning Result

All generate() functions should panic on an error that is returned by fill_bytes() or similar. Generating "non-faulty" random bytes is so important to security, that handling an error arising from this should not be left to the user.
Furthermore, using rand_os also chooses to use a blocking interface in most cases and so this will not be relevant to handle.

Fixed in #69.


v2 is broken on arm64 macOS runners

I tested both self-hosted and GitHub's runners and in all cases when trying to install LLVM action detects x64 instead of arm64:
Run KyleMayes/install-llvm-action@bb56a8457a77b95a5fa576c23731cbb162fd2056
  with:
    version: 17
  env:
    CARGO_INCREMENTAL: 0
    CARGO_TERM_COLOR: always
    RUSTFLAGS: -C strip=symbols -C opt-level=s --cfg aes_armv8
hello
Error: Unsupported version for platform (os=darwin, arch=x64, version=17)!
Checking known assets (os=darwin, arch=x64, version=17)...
    at $73b874f14e970995$export$da446a5ee2572b7 (/Users/runner/work/_actions/KyleMayes/install-llvm-action/bb56a8457a77b95a5fa576c23731cbb162fd2056/dist/main.js:7615:41)
Error: Unsupported version for platform (os=darwin, arch=x64, version=17)!
    at $73b874f14e970995$var$install (/Users/runner/work/_actions/KyleMayes/install-llvm-action/bb56a8457a77b95a5fa576c23731cbb162fd2056/dist/main.js:7633:60)
    at $73b874f14e970995$export$889ea624f2cb2c57 (/Users/runner/work/_actions/KyleMayes/install-llvm-action/bb56a8457a77b95a5fa576c23731cbb162fd2056/dist/main.js:7663:16)
    at $933db609b41224a7$var$main (/Users/runner/work/_actions/KyleMayes/install-llvm-action/bb56a8457a77b95a5fa576c23731cbb162fd2056/dist/main.js:7681:61)
    at Object.<anonymous> (/Users/runner/work/_actions/KyleMayes/install-llvm-action/bb56a8457a77b95a5fa576c23731cbb162fd2056/dist/main.js:7688:1)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
    at Module.load (node:internal/modules/cjs/loader:1091:32)
    at Module._load (node:internal/modules/cjs/loader:938:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)

P.S. Hello :slightly_smiling_face:

The architecture is currently determined by using the arch input if provided, then using NodeJS's process.arch, finally falling back to x64 if process.arch is not available.
So I think this means that process.arch is an empty string instead of "arm64" on these runners and I'm not sure why.
I think I'll need to come up with an alternate fallback for architecture detection.
In the meantime I guess you'll need to explicitly supply arm64 to the arch input.

We have tested and confirmed that console.log(require('node:process').arch); prints arm64 at least on self-hosted runner. I was suspecting that we have accidentally installed x86-64 Node.js on that machine, but then confirmed that the same is happening with official runners too, so it is not our self-hosted environment that is the reason (logs provided are from official runner).

I didn't realize core.getInput from the GitHub Actions library returns an empty string when an option isn't provided 🤦
So const arch = (options.arch ?? process.arch) || "x64"; was always resolving to "x64" since options.arch was always an empty string and ?? only returns the second argument when the first is null or undefined.
In my defense, this is at least half JavaScript's fault, something like this probably wouldn't happen in Rust.
I should have a fix out soon.

Well I have architecture detection working properly now, but the installed Clang binaries aren't runningon the ARM64 macOS runners:
https://github.com/KyleMayes/install-llvm-action/actions/runs/8515915176/job/23324181025?pr=66
dyld[4329]: weak-def symbol not found '__ZnwmSt19__type_descriptor_t'weak-def symbol not found '__ZnamSt19__type_descriptor_t'
/Users/runner/work/_temp/b5afcbc1-d1b9-4e85-b786-8533e2ed7487.sh: line 3:  4329 Abort trap: 6           $CC --version

In my defense, this is at least half JavaScript's fault, something like this probably wouldn't happen in Rust.

Yes, I'm so happy I mostly write Rust these days and don't have to deal with such errors.

Well I have architecture detection working properly now, but the installed Clang binaries aren't running properly on the ARM64 macOS runners:

According to https://discourse.cmake.org/t/cmake-suddenly-stopped-working-macos-sonoma/10303 and https://discourse.llvm.org/t/apples-libc-now-provides-std-type-descriptor-t-functionality-not-found-in-upstream-libc/73881 linked from there it is again some macOS-specific crap.
Looks like environment variables need to be edited for it to work.

Prefixing DYLD_LIBRARY_PATH with /usr/lib seemed to do the trick, it's now working in a standard ARM64 macOS runner.
I've released v2.0.1 with this fix and pointed v2 at that.


Update power-bi-visualization-combo-chart.md

@hongju : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ShannonLeavitt : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Self-generate random strings without going through a UUID.

Description
ActivationIDs are generated via UUID.randomUUID() today. Looking through the code of that you'll notice that it only generates a random hexadecimal String, delimited with dashes. We then proceed to cut out the dashes to end up at our ActivationId format.
We can straight up jump to generate the String ourselves. This even has the added benefit of adding more entropy to that String, because the UUID contains some bytes to determine its version (which are fixed bytes).
Related issue and scope

[x] I opened an issue to propose and discuss this change (#3395)

My changes affect the following components

[ ] API
[X] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[X] "Bug fix" (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[X] I signed an Apache CLA.
[X] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[X] I added tests to cover my changes. (Not necessary as caught by existing tests)
[X] My changes require further changes to the documentation.
[X] I updated the documentation where necessary.

Based on a discussion with @rabbah I benchmarked the code (and vastly improved it). Here are some numbers:
object Bench {
  def test(name: String, count: Int, generator: => String) = {
    println(s"running $name")
    val start = System.currentTimeMillis()
    Seq.fill(count)(generator)
    println(s"took ${System.currentTimeMillis() - start}")
  }

  def main(args: Array[String]): Unit = {
    val secure = new scala.util.Random(new SecureRandom())

    println("warmup")

    test("uuids", 10000, UUIDs.randomUUID().toString.filterNot(_ == '-'))
    test("randomHex", 10000, RandomString.generateHexadecimal(32))

    test("uuids", 10000000, UUIDs.randomUUID().toString.filterNot(_ == '-'))
    test("randomHex", 10000000, RandomString.generateHexadecimal(32))
  }
}

warmup
running uuids
took 142
running randomHex
took 181
running uuids
took 41861
running randomHex
took 31486

You can see that the randomHex code is indeed faster now. This is more about that code not allocating as much garbage though.
@rabbah WDYT? I'm a bit unsure if this is even worth it 😁.

bigger 🐟 in the noise...

Leaving as UUID factory based for now. Reopen if you disagree.


for resources using

i want to ask if you can list resources you are using for your daily learning thx

Hello @rodrigosImposter sorry for the very late response, I will start to adding some links when I remember it 😅, my goal is to continue adding more links in the future. Thank you for see this repository.


Add support for exclude_with and exclude_without

Partial fix for #660.
Make sure that you've checked the boxes below before you submit PR:

[x] Tests exist or have been written that cover this particular change.

Change Details:

Docs are missing
_all functions are missing

Need to reconsider depending on #664
@go-playground/admins if this is considered for merging I'd need some support how to implement the _all functions, particularly how can I retrieve a struct field from the param name?

I feel it should be excluded to be in line with required.

Closing in favour of #665


Base64 pdf

There is way to show PDFs in base64?

Currently there is no such possibility, you have to store it as file


Issue uploading selfie

I haven't been able to pollute my PRs with github selfies ☹ . This is similar to: https://github.com/thieman/github-selfies/issues/81
Browser: Google Chrome: Version 58.0.3029.110 (Official Build) (64-bit)
Version: GitHub Selfies 2.0.3 (downloaded from Chrome Store)
This is the error that appears in the Chrome Console window when I try to take a photo selfie.
Refused to connect to 'https://api.imgur.com/3/upload' because it violates the following Content Security Policy directive: "connect-src 'self' uploads.github.com status.github.com collector.githubapp.com api.github.com www.google-analytics.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-user-asset-79cafe.s3.amazonaws.com wss://live.github.com".

SIMILAR! DO WANT POLLUTION! 💩

Bad news, github blocks all ajax request outside their services/providers: https://github.com/blog/1477-content-security-policy
Which would be the approaches to fix this?
Who is up for telling github to add imgur to connect-src in CSP? :+1:  or :-1:

Fixed by #91.


Improve AccuracyEvaluator

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

Project coverage is 100.00%. Comparing base (5fe5f78) to head (042cc21).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #303   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           99       100    +1
  Lines         2371      2408   +37
  Branches       215       219    +4
=========================================
+ Hits          2371      2408   +37

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


List all clang-format options instead of relying on an upstream formatting style.

This allows for the project to individually tweak formatting options in the future.
The options are as close as I possibly could get to the actual coding style of the project, instead of the Google style.
I compared the number of differences with this shell script;
git checkout src ; clang-format -i src/*.h src/*.cc ;  git checkout src/getopt.h src/lexer.cc src/depfile_parser.cc src/*test*.cc ; git diff | grep -e "+" -e "-" | wc -l

And then compared the final result by hand to ensure nothing particularly egregious was happening.

I actually prefer relying on the Google style. No problem in tweaking formatting options in the future, we just need to add them.

The Google style doesn't accurately represent the actual formatting of the Ninja project.
Also, where the built-in styles actually defined? I was not able to locate them anywhere.

The Google style doesn't accurately represent the actual formatting of the Ninja project.

IMHO it's better not to introduce a "Ninja-style".

Sure. I don't care what style the project has. I care that the style is applied consistently.

If you don't want this change then close the PR.
Otherwise, tell me how I can improve the clang-formatting situation.

Closing then. Don't worry too much about formatting.

If we're not worrying about formatting, then please don't ask me to change the formatting of pull requests that I make in the future.
I'm willing to do the work to get the entire code base formatted properly, but I'm not at all interested in having my PRs nitpicked.
Either all of the code base, or none of it.

No, sorry. There's something in-between.

You misunderstand.
If you're not going to let me either:

Fix the entire codebase, to properly comply with the formatting rules that the project claims to want enforced
Fix the formatting rules to match the codebase

Then I'm going to ignore any future requests to change formatting of code that I submit PRs for, because I see changing individual lines of code at a time as significantly more work than just fixing the codebase.
I'm willing to do the grunt work for getting the formatting under control. I'm also willing to do it incrementally.
If we can come to an agreement to get the project's formatting under control, then while the process for getting the formatting working (which may well take many months, because we apparently can't ever introduce merge conflicts in multiple-years-old PRs) is underway, I'll put up with nitpicking of PRs.
But if we don't have an active effort going on to get the formatting under control, then I'm not going to bother, because as you said, "Don't worry too much about formatting."

that the project claims to want enforced

Where did the project claim that? .clang-format says: "This isn't meant to be authoritative, but it's good enough to be useful. Still use your best judgement for formatting decisions"

The comment in .clang-format is non-actionable. It's lacks meaning to contributors, because all bets are off on whether or not code the contributor submits a PR for will be accepted with, or without, or despite, clang-format being run on the lines that were changed.

Where did the project claim that?

You do, whenever you want to enforce bits and pieces of the partially specified clang-format rules by requiring PRs conform to some, but not all, of the formatting rules.

I think you're referring to my comment in the using-namespace-std PR? The 80 column limit is explicitly mentioned here: https://github.com/ninja-build/ninja/blob/6e02ebc4b5947095fa64b5bf814f14dd6f6f6a9a/HACKING.md#coding-guidelines

Yes, it is.
It's also one of the lines of the clang-format file.
I want to make the project actually compatible with flagrant use of clang-format.
Point me in the right direction.

The project doesn't want to be though.

Why?
What's wrong with using clang-format?

Also, lets be honest here.
When you say:

The project doesn't want to be though.

You mean you don't want the Ninja codebase to be able to be formatted by clang-format automatically.
You're the only maintainer of this project at this time.
Justify why having the project set up so that people can have faith that running clang-format will "do the right thing" is not what you want.

No, I mean the author of those lines in .clang-format.

No, I mean the author of those lines in .clang-format.

That comment was written > 5 years ago.
It's irrelevant.
Both because:

The person who wrote it no longer contributes to the project
Clang-format has become significantly more sophisticated.

It's clear (to me) that the original intent behind the comment was that clang-format at that time was not able to properly capture the comment-author's preferred style. I see no reason why clang-format can't be employed today with significantly better, or even ideal, results.

Justify why having the project set up so that people can have faith that running clang-format will "do the right thing" is not what you want.

It was the policy for the last 5 years, I don't want to change it.
One disadvantage is, that you'll need // clang-format off comments for some special parts of the code.
I also prefer not to touch existing lines, which formatting the whole code certainly would.

It was the policy for the last 5 years, I don't want to change it.

Why?
What kind of policy is:

This isn't meant to be authoritative, but it's good enough to be useful.
Still use your best judgement for formatting decisions: clang-format
sometimes makes strange choices.

It's not a policy.
Your position is "We shouldn't change anything because someone observed 5 years ago that the tool in question might do weird things".
That's not acceptable.

One disadvantage is, that you'll need // clang-format off comments for some special parts of the code.

Aside from the two specific places that I added them to avoid clang-format drastically changing two large blocks of code, I disagree with your observation.
Those two places were:

A large switch case, which I actually thought was improved by clang-format, but predicted would be objected to by you due to the number of lines that were changed all at once. (For what it's worth, that switch case is unweildly anyway, and I'd like to see it broken down into smaller parts).
A large string, which only need to be guarded from clang-format because the project isn't using C++11, which provides raw string literals, which is by far superior to the way the string is currently handled.

So I don't think this is correct at all, clang-format acceptably formats everything in the ninja codebase, aside from that one single string, which would be better as either:

A stand alone file, read in as needed for the test
A C++11 raw string literal

I also prefer not to touch existing lines, which formatting the whole code certainly would.

Why?

To avoid merge conflicts and preserve line history.

To avoid merge conflicts and preserve line history.

Which is why I said we can conduct this process over a period of multiple months.
Personally I don't think there's any value to be found in either avoiding merge conflicts, or preserving line history, but you clearly do, so I'm willing to work with you on this so that everyone wins.

Merge conflicts can simply be resolved, either by the original PR author, or by someone else.
By line history, I assume you mean things like git blame, and similar. While formatting changes can make those slightly more complicated, ultimately there's a lot of negative value in forbidding progress for the sake of such a minor activity.


Allow hiding the sidebar

I'd like a way to be able to hide the services sidebar. Sometimes I'm using a service where I want it to be truly full screen, for example when a video is being streamed. Currently I can remove all other elements on the screen except the sidebar. It's possible to do this using the developer tools, but it'd be much better if there was a feature for it.

Can I work on this?

Of course, go ahead!

Using a push-pin :pushpin: for that in the sidebar would be nice! (as in self-explanatory, maybe) :grimacing:
</feel-free-to-ignore>

I'm sorry, but I have unassigned myself from the issue! It proved to be too much to handle for me. But thank you for your time

This should be fairly easy, though. If you just inject CSS this can be done with something like this:
.sidebar {
    width: 9px;
    transition: all 2s ease-in-out .5s;
    display: block;
}

.sidebar:hover {
    width: auto;
    transition: all 2s ease-in-out .5s;
    display: inline-flex;
}

Of course, that's just a hack. But it proves it's doable even with the simplest approach, even without doing React.
Try harder! :hammer_and_wrench: :construction_worker_woman:

Oh, CSS/React wise sure! It's more getting lost on setting state, doing shortcuts and stuff. I'll try to come up with a simple solution for now then.

For streaming a video, you can simply press f11 to enable fullscreen mode.
Is there still a need for this feature?

@mhatvan At least for my use case it looks like the answer is no. The main trouble I was having before was trying to watch streams being played in Discord through Ferdi, and now when I do that and set Ferdi to be full screen, the rest of the UI disappears except for the video stream.


[feature] [backward-incompat] [null support # 2] Preserve null literal information in literal context and literal transform

This PR preserves the type information of literal in LiteralContext and LiteralTransform.
This means numerical literals will be passed down from broker either as a long or double except for big decimal.
String version of numerical values are not longer accepted. For example, "123" won't be treated as a numerical anymore.

Codecov Report

Merging #10380 (92cbc17) into master (1fce07e) will decrease coverage by 55.08%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #10380       +/-   ##
=============================================
- Coverage     68.82%   13.75%   -55.08%
+ Complexity     5851      231     -5620
=============================================
  Files          2027     1980       -47
  Lines        109891   107816     -2075
  Branches      16685    16468      -217
=============================================
- Hits          75637    14831    -60806
- Misses        28897    91799    +62902
+ Partials       5357     1186     -4171

Flag
Coverage Δ

integration2
?

unittests1
?

unittests2
13.75% <0.00%> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...roker/requesthandler/BaseBrokerRequestHandler.java
46.83% <0.00%> (-22.87%)
:arrow_down:

.../apache/pinot/common/function/FunctionInvoker.java
0.00% <0.00%> (-90.70%)
:arrow_down:

...inot/common/request/context/ExpressionContext.java
0.00% <ø> (-83.34%)
:arrow_down:

...e/pinot/common/request/context/LiteralContext.java
0.00% <0.00%> (-60.53%)
:arrow_down:

...ot/common/request/context/RequestContextUtils.java
0.00% <0.00%> (-65.90%)
:arrow_down:

...java/org/apache/pinot/common/utils/DataSchema.java
0.00% <0.00%> (-80.94%)
:arrow_down:

...pache/pinot/common/utils/request/RequestUtils.java
0.00% <0.00%> (-80.56%)
:arrow_down:

.../parsers/rewriter/CompileTimeFunctionsInvoker.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../pinot/core/common/datablock/DataBlockBuilder.java
0.00% <0.00%> (-76.74%)
:arrow_down:

...org/apache/pinot/core/data/table/TableResizer.java
0.00% <0.00%> (-89.72%)
:arrow_down:

... and 1637 more

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

These changes already include the ones in https://github.com/apache/pinot/pull/10376, right?

I would change the HashCode function, but apart from that, it looks fine to me.
Thanks a lot for the review!


Support multiple entrypoints

Add support for multiple entrypoints. Fix #71.

Perfect! Thanks for the quick addition!


🐛 Bug: "Edit this page" links are broken in projects

Bug Report Checklist

[X] I have searched for related issues and found none that matched my issue.
[X] This is the appropriate issue form for the bug I would like to report.

Expected
In pages like https://www.learningtypescript.com/from-javascript-to-typescript, Edit this page takes you to URLs like https://github.com/LearningTypeScript/projects/tree/main/src/content/external/projects/from-javascript-to-typescript/README.md. That's a 404.
Actual
They should go cross-repo to URLs like https://github.com/LearningTypeScript/projects/blob/main/projects/from-javascript-to-typescript/README.md.
Additional Info
No response

HI @JoshuaKGoldberg, I understand your requirement.
I explored this repository and the projects repository. However, I failed to figure out the place where I can change the link of "Edit this page".
Can you help me out here?

🎉 Great, thanks for taking a look!
Much of the site's UI is configured in the docusaurus.config.js file in the root directory. It's documented here: https://docusaurus.io/docs/configuration & https://docusaurus.io/docs/api/docusaurus-config.
Does that help?

@JoshuaKGoldberg, Thanks it helped.
I created a PR. Please review it and feel free to notify any up-gradation.


settings: rename display_settings to preferences.

Resolves zulip#26874.

This pull request renames remaining template files.
Changed Files:
web/templates/settings/preferences.hbs
web/templates/settings/preferences_emoji.hbs (web/templates/settings/display_setiings_emoji.hbs)
web/templates/settings/preferences_general.hbs (web/templates/settings/display_settings_general.hbs)
web/templates/settings/preferences_information.hbs (web/templates/settings/display_setiings_information.hbs)
web/templates/settings/preferences_navigation.hbs (web/templates/settings/display_settings_navigation.hbs)
web/templates/settings/user_preferences.hbs (web/templates/settings/user_display_settings.hbs)
web/templates/settings_tab.hbs
Fixes: #26874

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

As per the guidelines, "rename" -> "Rename" in the commit message. Looks good otherwise.
I am not sure, but maybe we can rename files like emoji_prefernces instead of preferences_emoji, but you should wait for feedback from Tim or Alya before changing them.

@sahil839 I've updated commit message as per the guidelines.

Looks good to me. @timabbott ready for your review.

Merged, thanks @Jai0401!


rollouts: script to generate rollouts kpt package

Added a script to generate kpt package to deploy rollouts component on any k8s cluster. Also added the kpt package under rollouts/manifests. I am going to follow up with an installation guide.
This will also sets up for releasing the rollouts component.

/cc @natasha41575 @mortent


Replace unsafe.Slice with memory copying to avoid potential fault memory issue

Refactored ListIPForwardRows to copy IP forwarding table rows.
Removed unsafe.Slice and replaced with pointer dereferencing and copying.
This change addresses a potential fault memory issue when iterating through the IP forwarding table.

/test-windows-all

Can this be closed? @XinShuYang

Can this be closed? @XinShuYang

Yes, thanks for the reminder.


Create South Korea crawl list

As we will be testing (issue #9) on South Korea since @atlasharry will be there and there is a South Korea Google VM, it makes sense to also include South Korean sites in the crawl.
@atlasharry will create such list with 525 sites similar to the other crawl lists according to @dadak-dom's protocol. @dadak-dom will provide input on how to create this list.

South Korea's top 525 list is now uploaded to branch 50, along with some scripts to build this list. I will merge this branch into branch 51-prepare-crawler-test-list to make the final test

Sounds good, @atlasharry! Feel free to close this issue if there is nothing more to do.


Add ci / Setup Travis

Fixes #12
Creator

[ ] Build relevant tests if any apply
[ ] Ensure there are no new warnings
[ ] Upload an animated GIF showcasing the solution (if it applies)
[ ] Set a relevant reviewer

Reviewer

[ ] Run test and make sure all tests pass
[ ] Review function and form on iOS
[ ] Review function and form on Android
[ ] Review function and form on Web
[ ] Review new test logic

:shipit: This branch has been deployed to:
exp://exp.host/@conrad-vanl/apollos-add-ci
Download the Expo app and scan this QR code to get started!

:shipit: This branch has been deployed to:
exp://exp.host/@conrad-vanl/apollos-add-ci
Download the Expo app and scan this QR code to get started!

:shipit: This branch has been deployed to:
exp://exp.host/@conrad-vanl/apollos-add-ci
Download the Expo app and scan this QR code to get started!


Module00c TinyResolve: StopIteration

Module00c TinyResolve
When running Module00c-TinyResolve, the following error reported:
Traceback (most recent call last):
  File "/home/luohx/work/SV/gnomad_sv_code/svtk/svtk/cli/resolve.py", line 231, in resolve_complex_sv
    cpx = ComplexSV(cluster, cytobands, mei_bed, SR_only_cutoff)
  File "/home/luohx/work/SV/gnomad_sv_code/svtk/svtk/cxsv/complex_sv.py", line 38, in __init__
    self.resolve(SR_only_cutoff=SR_only_cutoff)
  File "/home/luohx/work/SV/gnomad_sv_code/svtk/svtk/cxsv/complex_sv.py", line 82, in resolve
    self.resolve_translocation()
  File "/home/luohx/work/SV/gnomad_sv_code/svtk/svtk/cxsv/complex_sv.py", line 278, in resolve_translocation
    armA, armB = get_arms(plus, self.cytobands)
  File "/home/luohx/work/SV/gnomad_sv_code/svtk/svtk/cxsv/complex_sv.py", line 650, in get_arms
    return _get_arm(regionA), _get_arm(regionB)
  File "/home/luohx/work/SV/gnomad_sv_code/svtk/svtk/cxsv/complex_sv.py", line 643, in _get_arm
    arm = next(cytobands.fetch(region))
  File "pysam/libctabix.pyx", line 673, in pysam.libctabix.TabixIterator.__next__
StopIteration

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/luohx/software/anaconda3/envs/cromwell/bin/svtk", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/home/luohx/work/SV/gnomad_sv_code/svtk/scripts/svtk", line 67, in <module>
    main()
  File "/home/luohx/work/SV/gnomad_sv_code/svtk/scripts/svtk", line 64, in main
    getattr(cli, command)(sys.argv[2:])
  File "/home/luohx/work/SV/gnomad_sv_code/svtk/svtk/cli/resolve.py", line 481, in main
    for record in resolve_complex_sv(vcf, cytobands, disc_pairs, mei_bed, args.prefix,
RuntimeError: generator raised StopIteration

Here is the command:
bash mantatloccheck.sh std_000.manta.100001.vcf.gz 100001.disc.txt.gz 100001 hg38_v0_sv-resources_resources_v1_mei_hg38.bed.gz hg38_v0_sv-resources_resources_v1_cytobands_hg38.bed.gz

The error is produced by capturing the wrong region that dosen't match the cytoband file.
I check the error line of std_000.manta.100001.vcf.gz file:
#CHROM  POS ID  REF ALT QUAL    FILTER  INFO    FORMAT  100001
chr1    88507127    manta_100001_248    N   [chr17:33736831[N   .   PASS    END=33736831;SVTYPE=BND;CHR2=chr17;STRANDS=--;SVLEN=-1;ALGORITHMS=manta;EVIDENCE=PE;MEMBERS=manta_100001_248	GT:manta    0/1:1
chr1    88507142    manta_100001_249    N   N]chr17:33737644]   .   PASS    END=33737644;SVTYPE=BND;CHR2=chr17;STRANDS=++;SVLEN=-1;ALGORITHMS=manta;EVIDENCE=PE;MEMBERS=manta_100001_249	GT:manta    0/1:1

The pos "33737644" is supposed to be extracted with chr17 but "88507142" is wrongly extracted which causes the bug.
Could you please help me out with this issue?
Thanks in advance!

I happened to notice you have a sample named 100001. We've had numeric IDs cause issues in the past and would strongly suggest you use something like the script in InternalSampleID in GetSampleID.wdl to generate safe internal IDs for processing. There are also issues if any ID is a substring of another or if they contain the string name. If all your ID's are numbers like this, surrounding them with underscores _ may suffice eg _100001_.

@ghzhaole Were you able to work through this error?

Stale issue


Links disappear

Just want to begin with thanking you for putting in work on this.
I'm having some issues with the link disappearing on the image-map after adding the script,

The links work when $(document).ready(function() { is removed.
However, the responsive image mapping still won't work.
This is the used code. (If you find any issues with that).
BEFORE HEAD:

    {{ 'app.js' | asset_url | script_tag }}
    {% if settings.product_slideshow_animation == 'zoom' %}{{ "cloudzoom.js" | asset_url | script_tag }}{% endif %}
    {{ 'option_selection.js' | shopify_asset_url | script_tag }}
    {{ 'imageMapResizer.min.js' | asset_url | script_tag }}
    {{ content_for_header }}

CODE ON PAGE:

					<map name="m_largebanner">
				<area shape="rect" coords="294,352,425,368" href="https://royalstripes.com/collections/ties" title="Ties">
			<area shape="rect" coords="1193,367,971,347" href="https://royalstripes.com/collections/pocketsquares" title="Pocketsquares">
		</map>

Please contact me at,
<EMAIL_ADDRESS>if you want to see the site. (Requires password which can't be shared here.)
Would appreciate the help.
A fee could be payed.
Best Regards,
Robbin.

Hopefully this is fixed in v1.0.2 and v0.6.2 now.


BIGTOP-3171. Update Kafka Puppet module for version 1.1.1

Fixed. Please review @oflebbe

You're right! I've remove that if-else clause. Thanks for the snd. eye!


CIN-01147: Field type icons added to Form labels

resolved comment for outline font awsome icon

@cinchy-yogeshjagtap The boolean icon is not displaying properly - it should be on the far left. It's currently on the right of the field value (checkbox)

Hi @cinchy-m , I have resolved above comment and also made checkbox icon change

should this be pointed to 5.2.1?

or maybe poitned to 5.3?

@alvin-h Thanks. Switched to v5.2.1.

@cinchy-yogeshjagtap The calculated column icon is not displaying correctly. As discussed, this is because the "result type" (useful for/required to render the input type) is being used instead of the "data type" (needed to correctly display the icon).

This PR is complete but we need to update the query for calculated columns to return the field "type", as opposed to the field's "result type".


.xlsx export

I want to automatically create well-formatted tables.
The format needs to be discussed.
The implementation can either be part of the web app or a seperate ".csv-Data + .xlsx-Template -> formatted Table" converter.
Missing entries are:
Breaking points
Crossing points
Train crossings?
Names and contact data of the local guides.

@LeTaPe I assume that we do not need this anymore now with the pdf export, right? Only train crossings is an open point


[Languages] Hands-on Python-based data visualization using Dash Plotly.

Writing sample(s):

Track users of your site using google analytics

Proposal Submission
Proposed title of the article
Hands-on Python-based data visualization using Dash Plotly.
Proposed article introduction
For web analytics, Dash is a Python framework. You don't need to know HTML, CSS, JavaScript, or any other front-end framework or language to build attractive and fast web dashboards with Dash instead. We'll create our own Dash online dashboard as part of this lesson.
Key takeaways

By the end of this lesson learners will be able to:

Understand what exactly Dash Framework is.
Understanding the 3 pillars of Dash Framework.
How to set up Data in Dash
Set-up APP Layout section
Get to know the Plotly Dash community Forum

Article quality
As a result of the extracted information, data visualization helps decision-makers make informed business decisions, increasing customer retention and profits. The necessity to grasp and appreciate Data visualization technologies like Python emerges from this extremely important and in-demand talent. A practical example of how we can visualize data in Dash will be provided in this article.
References
N/A

Thank you for the topic suggestion, however this is a bit outside of our preferred topic areas.
We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
Please feel free to suggest an alternate topic to explore. 🚀


add a security module （#628）

#628
Add security mechanisms, IP whitelists, blacklists, and extended security interfaces.
Extend security by implementing ISecurityPolicy。
@TomPallister Evaluation is feasible, feasible, I add unit test

Security protection extension for Ocelot AuthorizationToken
Ocelot.Security.AuthorizationToken.EntityFramework

Security protection extension for Ocelot AuthorizationToken
Ocelot.Security.AuthorizationToken.EntityFramework

very cool :D

@aqa510415008 thank you for the tests, this is very good. I have merged it now.

@aqa510415008 thank you for the tests, this is very good. I have merged it now.


Mark unused attributes?

I'm wondering if this extension can somehow leverage rnix-lsp to find out which attributes are unused in an expression.
Example:
let a=5; b=true; in b

would mark a as unused.

I've not terribly familiar with language servers but just wanted to add that using nil, as mentioned in #274, marks attributes as unused (see inputs and pkgs in the screenshot below). So my guess is that whatever change needs to happen, should happen in rnix-lsp (though I could be wrong).

As @hall has mentioned, the info would come from LSP servers.


[Bitwarden Vault] Client ID and Client Secret are regularly deleted.

Extension
https://www.raycast.com/jomifepe/bitwarden
Description
Regularly when I open the extension, the Client ID and Client Secret are again required. I'm not sure how those preferences are being lost.
Steps To Reproduce

Open Search Vault
...

That's it.
It could be related to the fact that I synced Raycast on two machines, but that doesn't seem to have an impact on any of my other extension configurations. I have looked through the source code, but nothing jumped out at me as a potential cause.
Current Behaviour
I have to reenter these parameters.
Expected Behaviour
I don't have to reenter these parameters.

Hey, thanks for reporting. This doesn't seem like an extension bug, as we don't have any kind of control over the preferences, so that's most likely related to your setup or Raycast itself.

@raycastbot close this issue


Updates:

Description

Use latest v1.0.0 linuxkit images.
Add images dir with runc and containerd to be able to better control the version.
Use latest upstream init as it has cgroups v2 as the default.
Add dhcp to the linuxkit services so that interfaces stay configured after lease times expire.
Update to latest Docker in Docker version and update linuxkit spec to handle cgroups v2.
Increase the kernel command line parameter size to 4096 bytes to allow for longer things to be passed like certs, etc.
Default to linuxkit 1.2.0 binary as the containerd issues are resolved with the ccgroup v2 changes.

Why is this needed

Fixes: #
How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[ ] added unit or e2e tests
[ ] provided instructions on how to upgrade

What was the motivation for finer version control over runc and containerd?

What was the motivation for finer version control over runc and containerd?

Upstream moves a bit slow for me 😬 , in terms of getting to the latest versions. These additions were helpful in my troubleshooting but im not against removing them entirely if you have some concerns. There's enough trade-offs both ways for me to be fine with either approach.

Presumably you mean upstream linuxkit, not upstream containerd? I.e. you're not trying to get some edge patch from containerd?
Assuming its linuxkit, I'm good with building given we're using official release tags/commits.

Presumably you mean upstream linuxkit, not upstream containerd? I.e. you're not trying to get some edge patch from containerd?
Assuming its linuxkit, I'm good with building given we're using official release tags/commits.

Yeah, upstream linuxkit.


Create GameModel.md

Describing game model with arbitration extension according to #7

Thanks for detailed explanations, I think it worth including them into the main text.

Are we sure that we need to give the client the ability to decide whether to pay or not even if Validator had confirmed results? Maybe if the Client was selecting Validator this step is unnecessary?

Are we sure that we need to give the client the ability to decide whether to pay or not even if Validator had confirmed results? Maybe if the Client was selecting Validator this step is unnecessary?

I think the answer depends on the expected quality of the Validator. If the Client normally brings a Validator from a reputable (but probably costly) third party service, then that Validator would be well suited to represent the Client's interests. That Validator's business model would be to give true results and accumulate business reputation. In that case, the Client's approval of payment could be redundant. However, if the Client merely does a random-style pick from a pool of Validators with open entrance, then it would be safer to retain the Client's right to appeal to Arbitration by not not releasing the payment.

We clearly need to put the model of Client-Validator relations aside. It does not matter to us how the Client selects the validator (or does the validation job by itself) unless it's his responsibility to protect it's interest by a proper Validation work


[Bug Report] Server Crashing on Mod Loading

Describe the bug
Server crashes upon loading 2.0.5 or 2.0.7 version of mod.
To Reproduce
Steps to reproduce the behavior:

Install either version to your servers mod folder
Launch server and inspect that it crashes

Expected behavior
Server should run with the mod and not crash.
Server Software and Version:

Vendor: Fabric
Minecraft Version: 1.18.1

Additional
latest.log

2.0.7 is for 1.18.2. It is not expected to work on 1.18.1. 2.0.5 works on 1.18.1, I see you claim to have an issue with that version, but didn't provide a log. However even with a log, only the latest version of MiniMOTD is supported.

That's really unfortunate, I tried 2.0.5 but it does indeed crash. I'll provide a log.

You need to either downgrade loader to 0.13.x for that version, or manually install the newest adventure-platform-fabric mod


Piper/re organize trinity chain module

built on top of https://github.com/ethereum/py-evm/pull/1343 so ignore the first commit or go review that and I'll get this rebased

What was wrong?
While working on #1299 it became apparent that the way some of the trinity modules were organized was not correct.  This was based on finding places where we ended up with circular imports, or having to do odd import hoop jumping to make things work.
How was it fixed?
Re-organized things.  New modules are:

trinity.initialization
trinity.db.manager
trinity.utils.mp now has the multiprocessing exception data structures.
moved some constants around.

Cute Animal Picture

Ignore this for now.  Still sorting out test failures.

Ok, looks like it's going to go green, :+1: ready for review.

https://github.com/ethereum/py-evm/issues/1352

Another missing test that I previously assumed ethereum/tests covered.


Docs don't have info for the v2 API

@Page- It appears that the v2 API is released, but not documented. We really need to update the docs for it. Am I missing something somewhere?
 Front conversations

@flesler @Page- @zwalchuk a user in gitter has just pointed this out too, and v1 is now really old, we're on v3 about to release v4. How do we get these docs updated?
Do we have a plan for how we're going to manage showing docs for the multiple versions available? Worst case we can get by just showing the newest, imo, but medium-term a versioned docs solution would be nice.

This is something I haven't gotten into but would like learn how to so I can manage it. @Page- please ping if you whenever we could/should update the docs

@flesler @Page- another user has just pointed this out in support, it'd be good to get this updated.

Fixed by #798 ?

The API docs now cover versions v1,v2,v3 and v4

Closing this as up to date with v5 with this PR https://github.com/balena-io/docs/pull/1232


sync main branch to develop branch (#692)

Bump whelk-io/maven-settings-xml-action from 20 to 21

Bumps whelk-io/maven-settings-xml-action from 20 to 21.

Release notes
Commits

updated-dependencies:

dependency-name: whelk-io/maven-settings-xml-action dependency-type: direct:production update-type: version-update:semver-major ...

Bump liquibase-github-actions/drop-all from 4.24.0 to 4.25.0

Bumps liquibase-github-actions/drop-all from 4.24.0 to 4.25.0.

Release notes
Commits

updated-dependencies:

dependency-name: liquibase-github-actions/drop-all dependency-type: direct:production update-type: version-update:semver-minor ...

Bump actions/github-script from 7.0.0 to 7.0.1

Bumps actions/github-script from 7.0.0 to 7.0.1.

Release notes
Commits

updated-dependencies:

dependency-name: actions/github-script dependency-type: direct:production update-type: version-update:semver-patch ...

Bump com.ibm.db2:jcc from <IP_ADDRESS> to <IP_ADDRESS>

Bumps com.ibm.db2:jcc from <IP_ADDRESS> to <IP_ADDRESS>.

updated-dependencies:

dependency-name: com.ibm.db2:jcc dependency-type: direct:production update-type: version-update:semver-patch ...

Bump org.codehaus.mojo:versions-maven-plugin from 2.16.1 to 2.16.2

Bumps org.codehaus.mojo:versions-maven-plugin from 2.16.1 to 2.16.2.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: org.codehaus.mojo:versions-maven-plugin dependency-type: direct:production update-type: version-update:semver-patch ...

Bump org.postgresql:postgresql from 42.6.0 to 42.7.0

Bumps org.postgresql:postgresql from 42.6.0 to 42.7.0.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: org.postgresql:postgresql dependency-type: direct:development update-type: version-update:semver-minor ...

Bump org.firebirdsql.jdbc:jaybird from 5.0.2.java11 to 5.0.3.java11

Bumps org.firebirdsql.jdbc:jaybird from 5.0.2.java11 to 5.0.3.java11.

Release notes
Commits

updated-dependencies:

dependency-name: org.firebirdsql.jdbc:jaybird dependency-type: direct:production update-type: version-update:semver-patch ...

using Codex-/return-dispatch to get the run-id for OSS when a run is triggered (#666)

fix error unexpected end of the stream within a double quoted scalar (#667)

Bump org.xerial:sqlite-jdbc from <IP_ADDRESS> to <IP_ADDRESS>

Bumps org.xerial:sqlite-jdbc from <IP_ADDRESS> to <IP_ADDRESS>.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: org.xerial:sqlite-jdbc dependency-type: direct:development update-type: version-update:semver-patch ...

Bump commons-io:commons-io from 2.15.0 to 2.15.1

Bumps commons-io:commons-io from 2.15.0 to 2.15.1.

updated-dependencies:

dependency-name: commons-io:commons-io dependency-type: direct:production update-type: version-update:semver-patch ...

Bump org.mariadb.jdbc:mariadb-java-client from 3.3.0 to 3.3.1

Bumps org.mariadb.jdbc:mariadb-java-client from 3.3.0 to 3.3.1.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: org.mariadb.jdbc:mariadb-java-client dependency-type: direct:development update-type: version-update:semver-patch ...

Bump actions/setup-java from 3 to 4

Bumps actions/setup-java from 3 to 4.

Release notes
Commits

updated-dependencies:

dependency-name: actions/setup-java dependency-type: direct:production update-type: version-update:semver-major ...

Bump org.apache.maven.plugins:maven-javadoc-plugin from 3.6.2 to 3.6.3

Bumps org.apache.maven.plugins:maven-javadoc-plugin from 3.6.2 to 3.6.3.

Release notes
Commits

updated-dependencies:

dependency-name: org.apache.maven.plugins:maven-javadoc-plugin dependency-type: direct:production update-type: version-update:semver-patch ...

Bump org.postgresql:postgresql from 42.7.0 to 42.7.1

Bumps org.postgresql:postgresql from 42.7.0 to 42.7.1.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: org.postgresql:postgresql dependency-type: direct:development update-type: version-update:semver-patch ...

Bump org.liquibase.ext:liquibase-sdk-maven-plugin

Bumps org.liquibase.ext:liquibase-sdk-maven-plugin from 0.10.22 to 0.10.23.

Release notes
Commits

updated-dependencies:

dependency-name: org.liquibase.ext:liquibase-sdk-maven-plugin dependency-type: direct:production update-type: version-update:semver-patch ...

Bump net.snowflake:snowflake-jdbc from 3.14.3 to 3.14.4

Bumps net.snowflake:snowflake-jdbc from 3.14.3 to 3.14.4.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: net.snowflake:snowflake-jdbc dependency-type: direct:development update-type: version-update:semver-patch ...

DAT-16380 (#673)

using -Dliquibase.sdk.workflowId=run-tests.yml

use sdk-maven-plugin 0.10.23

get liquibase --version

get branch develop

Trigger build

good to merge after resolving the conflict

Conflicts resolved. Please verify


ValueError: Could not find config.json in ....

I'm getting an error sometimes when I try to create a collection in my local
Current Behavior

ValueError: Could not find config.json in [/var/folders/bk/1644ckzd4z1_dg2l6_nrn3cr0000gp/T/fastembed_cache/fast-bge-small-en](https://file+.vscode-resource.vscode-cdn.net/var/folders/bk/1644ckzd4z1_dg2l6_nrn3cr0000gp/T/fastembed_cache/fast-bge-small-en)
Also, this pip install did not work in my local
!pip install qdrant-client[fastembed]
It says zsh:1: no matches found: qdrant-client[fastembed]
Steps to Reproduce

Make sure the Docker is running
To run the server: docker pull qdrant/qdrant docker run -p 6333:6333 qdrant/qdrant

from qdrant_client import models, QdrantClient
from sentence_transformers import SentenceTransformer
df = pd.read_csv('dataset.csv')
client = QdrantClient(":memory:")
client = QdrantClient(":memory:")
client.add(
    collection_name='keyword_function_model',
    documents=df['KEYWORD'],)
print("Completed")

Now, I'm getting this error
ValueError: Could not find config.json in [/var/folders/bk/1644ckzd4z1_dg2l6_nrn3cr0000gp/T/fastembed_cache/fast-bge-small-en](https://file+.vscode-resource.vscode-cdn.net/var/folders/bk/1644ckzd4z1_dg2l6_nrn3cr0000gp/T/fastembed_cache/fast-bge-small-en)
What am I doing wrong.?
Is the docker server statement wrong.?
Why am I able to run it one day and suddenly it just fails on another day.?
My system requirements are:

Python 3.11.5
Apple M1 Pro - 16GB

Please help me with this issue, it's causing a lot of problems

hi @MowlanicaBilla
in zsh you need to use quotes: pip install "qdrant-client[fastembed]", this is the common way to install python packages with extra dependencies in zsh
which fastembed version are you using?
we had some problems with launching models when the model downloading process was interrupted, have you tried removing the cache?

Thanks for the quick reply,  @joein.
I have tried installing pip install "qdrant-client[fastembed]" but still the same error.

I have fastembed==0.2.5 and qdrant-client==1.8.2 versions on my system.
Is this the correct docker image.? docker pull qdrant/qdrant docker run -p 6333:6333 qdrant/qdrant

@MowlanicaBilla  Yes, it is the correct docker image
Could you try removing the path mentioned in the traceback (/var/folders/bk/1644ckzd4z1_.... and so on), so the model could be downloaded again?
Maybe the process of downloading the model had been interrupted and the cache got into a broken state
Btw, the image you're referring to is latest, which is 1.9.0, but you're using qdrant-client==1.8.2
I believe that the situation when the downloading process interruption could prevent the following launches should've been fixed in the latest version of fastembed, update to qdrant-client==1.9.0 and fastembed==0.2.6 might help to avoid such issues in the future.


Add Japanese Leaderboard

Japanese LLMs are typically evaluated on a collection of standard benchmarks. This PR aims to organize these benchmarks into a simple reproducible framework, making it easier to consistently evaluate LLMs on the Japanese language.
Benchmarks:

[x]  jaqket_v2
[x] jcommonsenseqa
[x] jnli
[x] jsquad
[x] marc_ja
[x] mgsm
[x] xlsum
[x] xwinograd

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.mtkachenko seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

It looks like Tasks Modified check will fail as the Rakuten/JGLUE HF dataset uses custom data loader script and, therefore, requires trust_remote_code=True. Could you advise on the best way to handle this issue?

Thanks for the PR. It's ok about the test, I'll update them in a seperate PR. Left a couple of comments mainly about import handling. Also, might be a good idea to create a group config like mmmu, if you think it's appropriate. The main difference between group and tag is that with group you get an aggregate score for all the tasks and can choose if you want to normalize it by total number of samples or number of tasks (weight_by_size True or False)

Thanks for the review, @baberabb. I added a group config for clarity as you recommended and removed the tags as they would conflict.
I don't think it is possible to aggregate the scores across mixed metrics ("acc", "exact_match", "rouge2") with aggregate_metric_list at the moment? Therefore, I haven't included aggregation, though having a single score per leaderboard could be helpful.

Sure thing, @baberabb, updated the task table!


Avoid potential divide by zero when misaligning

Removes possibility for divide by zero if all distances are zero when "misaligning." Also adds some additional error checking

LGTM, no objections to merging.  Just a side note though; usually (if we're not dealing with numpy arrays here) I would explicitly check for a zero denominator and set the value to infinity or otherwise handle that condition more explicitly as using an epsilon can go unnoticed or be confusing if it isn't called out.

LGTM, no objections to merging. Just a side note though; usually (if we're not dealing with numpy arrays here) I would explicitly check for a zero denominator and set the value to infinity or otherwise handle that condition more explicitly as using an epsilon can go unnoticed or be confusing if it isn't called out.

Your comment is making me question whether epsilon needs to be added to the numerator or not (and if that even matters). I was thinking that the values are only needed for relative comparison, so it probably (?) makes sense to operate on non-infinite values, but maybe not?

Edit: I'm suggesting maybe it should just be  probs = [dist/(sum(dists) + eps) for dist in dists]

I think this would be sufficient


Block Texture Variation tutorial seems broken

I am not 100% sure on this but it seems the method of block variation method is broken in 1.16.200.
https://wiki.bedrock.dev/tutorials/block-texture-variation
If someone knows how to make it work or what changed i can help update, but for now it should be removed to reduce confusion or at least marked as non fuctional

Good eye. In general, some tutorials got broken in .200, and nobody seems to have time fixing them.
We should probably remove bloat overall so we can better maintain everything.
Please feel free to remove the page yourself if you feel capable.

PR submitted #282 I updated to a different method, I think this is valuable to keep in the wiki. feel free to close.


AsyncRx.NET: Introduces VirtualTimeAsyncScheduler, TestAsyncScheduler

Background
I've used Rx.NET at an application level for quite a while, I started down this path because I wanted to get familiar with the codebase (read: I have no faffing idea what I'm doing). I saw that the throttle operator wasn't working (#808) and thought that might be a good first contribution. I thought it was just a parameter not being passed through, but I wanted a way of validating it, so I ended up implementing the bits needed to build a test scheduler too.
Value
This PR introduces a virtual time scheduler base which allows for schedulers like test schedulers (included in this PR) and historic schedulers (not included in this PR).
It also fixes the throttle operator and introduces the bits of Microsoft.Reactive.Testing required to test it.
(I can also submit this as two PRs—introducing the test scheduler as one, fixing the throttle operator as another—if preferred.)
Edit: The fix for the throttle operator is in #898.
Questions
Rendezvous, TaskAwaitable
This may not be pertinent to the changes I've made, but I haven't managed to understand quite what the 'rendezvous' bit  is for. (I see it ensures an awaitable's continuation is invoked by the scheduler, but I don't understand the consequences.) Nor when it's supposed to be used. (It looks like it's only used in the Linq layer for most but not every Task-returning function.)
Can anyone clarify this part for me?
Edit: Oh, maybe an Ada kind of rendezvous? I guess I have some reading to do...
Recursive scheduling
I see the IAsyncScheduler deals with schedule functions with a signature like (cancelation, action) -> disposable rather than (scheduler, state, action) -> disposable.
If I understand, the schedulers in Rx.NET allow for recursive scheduling of work. Is that not a thing in AsyncRx.NET or am I misunderstanding how it does that?
Edit: I think this might actually be related to the previous question 🤔
Interfaces
I can imagine there is an argument for strictly matching interfaces so that it's exactly Rx.NET except for the Task-returning bits, but I can also imagine AsyncRx.NET being seen as an opportunity to do away with some legacy which was only retained in Rx.NET for backwards compatibility.
In this PR, there are some places where I deviated slightly from the interfaces in Rx.NET. (I'll highlight the exact deviations with comments.) Please guide me as to whether it is too much (I need to strictly match Rx.NET) or too little (I've brought across some legacy bits which I shouldn't have).
Implementation
A lot of this was copying and pasting from Rx.NET and updating invocations to be Task-returning. I tried to leave the implementation mostly as-is as I assume there were optimization reasons for it being written specific ways.

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

I can also submit this as two PRs

That would be great, if there's a bugfix it should go in separately. Discussion may then continue on your feature PR.

Looks like a good start on bringing these things into Async Rx; thanks for the effort on this.
I suggest we proceed towards feature parity with classic Rx, and consider the duality with IAsyncEnumerable<T> in C# 8.0 after that gets wrapped up. I can pour in some design topics for the work we did here on the "Reactor" service, which also has asynchronous Rx notions (in fact, the work in this repo was a direct consequence of that work, bringing back a core Rx library with async support, without the service portions around it).

I'll revisit this PR hopefully in the not-too-distance future, now that there's a second wave of work on this (after System.Linq.Async has crystallized, among some other reasons that motivated revamping this work).

Hi @NickDarvey, thanks for this contribution. Would you be able to rebase this PR onto the current main branch and resolve the conflicts? I was thinking about tackling the Async-Rx tests to some extent and this could use the schedulers you introduced.


Egress Interface remain in down state with externalippool

Describe the bug

Egress interface shown as down even when ipRanges are in same subnet as Node subnet or otherwise ?
Traffic is going out with actual interface
5: antrea-egress0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
link/ether f2:35:20:81:87:ac brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/32 scope global antrea-egress0
valid_lft forever preferred_lft forever
To Reproduce

configure extermalippool resource with following config
apiVersion: crd.antrea.io/v1beta1
kind: ExternalIPPool
metadata:
name: external-ip-pool
spec:
ipRanges:

start: <IP_ADDRESS>
end: <IP_ADDRESS>
nodeSelector: {}     # All Nodes can be Egress Nodes

create egress resource under egress crd
apiVersion: crd.antrea.io/v1beta1
kind: Egress
metadata:
name: snat-testapp-ip
spec:
appliedTo:
podSelector:
matchLabels:
app: antrea-test-app  ###Select the Pods to which the SNAT Policy will be applied
externalIPPool: external-ip-pool
Expected

Egress interface status should be up
Actual behavior

Versions:

Antrea 2.0/Containerd
Additional context

antrea-egress0 is a dummy interface and supposed to be down by design.
The usage of antrea-egress0 is kind of implementation specific. We can add some docs to clarify it but it's not a bug.

@tnqn ,
antrea-egress0 is a dummy interface, however if the externalippool is not in node's subnet, traffic is stopped (expected) and antrea-egress0 remain in down state, however when externalippool is in same subnet as node's network, traffic is going out, however keeping the antrea-egress0 as down might confuse user as src ip will be of antrea-egres0 interface.
Documentation could help to clarify these.

While using static Egress, when same ip is provided as node's ip, there is no ip assigned to egress dummy interface( antrea-egress0 ), it is expected since ip is already assigned to node's interface, hence can not be reassigned to egress dummy interface
Another candidate for documentation
5: antrea-egress0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
link/ether a2:8d:11:5c:fa:a7 brd ff:ff:ff:ff:ff:ff


Could not hook httpx "event hooks" for debugging

Describe the bug
I like to do deep debugging with the clients generated using openapi-python-client. I would like to see request, response objects for every api call is logged/ dumped for  analysis.
From the httpx documentation, its possible using Event Hooks (https://www.python-httpx.org/advanced/).
But I could not successfully able to hook the events.
To Reproduce
Steps to reproduce the behavior:

def log_httpx_request(request: httpx.Request) -> None:
    print ("*** ", type(request))
    print(f"+++Request event hook: {request.method} {request.url} - Waiting for response")

def log_httpx_response(response: httpx.Response) -> None:
    print ("***", type(response))
    request = response.request
    print(f"+++Response event hook: {request.method} {request.url} - Status {response.status_code}")

...
    client = Client(
        base_url="https://codebeamer.xxx.com/cb",
        headers={"Authorization": "Basic " + base64.b64encode(basic_auth_data).decode("ascii")},
        timeout=10.0,
    )

    client.event_hooks={'request': [log_httpx_request], 'response': [log_httpx_response]}

    version_data = get_server_version.sync(client=client)
...

Expected behavior
HTTPx event hook is working but event hook is not called at all.
Looks like event hooks work with httpx client object but the generated code directly uses "httpx.request" helper function.
Please provide a way to do a full debugging / event hooks.
OpenAPI Spec File
NA
Desktop (please complete the following information):

OS: Ubuntu 22.04.1 LTS
Python Version: Python 3.10.4
openapi-python-client version 0.11.5

It sounds like this will be covered by #202 when implemented, is that correct?

@dbanty , Indeed. #202 would solve this issue as well. Thanks. Shall I close this issue?

I think so, if you wouldn’t mind adding your use case to that other issue as well just to +1 support that would be great.
I feel like enough different people have wanted a feature like that that it should be the highest priority 😅


Adding 'Default Layer' option

This would allow a user to specify a default layer that will be shown every time the Navigator is opened, without having to manually upload it every time.

Hi @wietze - this is a great idea for an enhancement, and thanks for bringing this up. We'll discuss and prioritize this feature request for integration with the Navigator based on how it fits in with our current set of enhancements slotted for our version 2 release.
We also welcome pull requests based on our develop branch if you or anyone else in the community wants to contribute this to the Navigator individually.

While it doesn't exactly match the use case you describe, issue #20 may meet some of the requirements for this issue. Once #20 is implemented you would be able to bookmark the navigator URL with a query-string specifying your desired "default layer."

Is this something that would be configured on an instance-basis, i.e. in the Navigator config file that would apply to everyone who uses that instance?  If so, then an organization hosting a local instance of the Navigator could configure the default layer as they see fit.  Beyond that, is there a need/ability for a per-user default requiring some sort of cookie?

I'm mainly interested in the instance-basis version; for our team it would be great to have our ATT&CK coverage as the default layer, allowing each team member to add their own layers or do their own analysis based on that.
The per-user version would be a nice extra. The aforementioned URL bookmark solution (#20) might cover this use case though.

A solution for this issue has been pushed to the develop branch. You can now add a default layer file to the assets directory and specify the location in the config file. There is more documentation on the README


Consider using ostringstream, it should be more performance-effective for building strings

For example: https://github.com/Azure/azure-sdk-for-cpp/blob/308e5363adaa00ace2f06ff0f1a31747a0a28062/sdk/core/azure-core/src/http/request.cpp#L62-L76
Originally posted by @antkmsft in https://github.com/Azure/azure-sdk-for-cpp/pull/2056#discussion_r608250965

I doubt that. I think string stream is usually slower than string.
Anyway, do some benchmark before making the change in case of any regression.


⚠ Bofrost.at has degraded performance

In b06357a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1498 ms

Resolved: Bofrost.at performance has improved in ed913bb after 13 minutes.


Could you please make this more descriptive?

https://github.com/microsoft/autogen/blob/ef1c3d3f7f46fd7323aeecb7000ad99c43564a75/autogen/retrieve_utils.py#L310
Variable name: query_texts
Variable description: the query texts
Yes, I understand that, but what do you mean by query texts?  Is this a list of strings that are going to be used to query documents?  If so then why do we have a search string?

@thinkall fyi

@tyler-suard-parker thanks for asking, it’s a list of strings, query_texts (List[str]): the query texts. says List[str]. Does it make sense to you?

Sorry, still no.  I understand it is a list of strings, but what is the purpose of the query_texts argument?

It contains the text used for retrieving documents from the database.

@thinkall Thank you.  How is that different from the search string?

@thinkall Thank you. How is that different from the search string?

Thank you @tyler-suard-parker , I get your point. This is not a user-oriented function, if you come to this file from here, search_string (str): only docs containing this string will be retrieved. you may not be so confused.
I'll make a PR to improve the doc_string. Thanks.


fix: delete rest in buttonIcon

Pull Request Test Coverage Report for Build 215

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

Totals

Change from base Build 169:
0.0%

Covered Lines:
1118

Relevant Lines:
1420

💛  - Coveralls

add form and onKeyDown prop to Button and ButtonIcon and all props like ariaExpande, ariaControls that already exists in the ButtonIcon to the Button


Documentation: migrate STM32F0

Summary
Documentation: migrate STM32F0
Impact
Testing
local build

Since documentation ci pass, let's merge it.


Related to readme.md file

you should provide a detailed readme.md file so that others can get some idea about your project's domain. if you don't mind can I update your readme.md file in a better way?

I wish to contribute. Kindly assign this to me.


[Tabs] Allow authors to specify a default selected item #316

Added option to select default active item/tab
Updated unit tests and test content
Added integration test
Fixes #316

Codecov Report

Merging #317 into development will increase coverage by <.01%.
The diff coverage is 83.33%.

@@                Coverage Diff                @@
##             development     #317      +/-   ##
=================================================
+ Coverage          82.22%   82.22%   +<.01%
- Complexity           871      874       +3
=================================================
  Files                 82       83       +1
  Lines               2790     2796       +6
  Branches             517      518       +1
=================================================
+ Hits                2294     2299       +5
  Misses               205      205
- Partials             291      292       +1

Impacted Files
Coverage Δ
Complexity Δ

...sandbox/internal/models/AbstractContainerImpl.java
92.85% <ø> (ø)
7 <0> (ø)
:arrow_down:

...be/cq/wcm/core/components/sandbox/models/Tabs.java
100% <100%> (ø)
1 <1> (?)

...e/components/sandbox/internal/models/TabsImpl.java
85.71% <80%> (-14.29%)
4 <2> (+2)

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 4f65a7d...db7a5f3. Read the comment docs.


refactor cmuarctic dataset unittest

[x] refactor cmuractic dataset.

Closing as there is. a duplicate #1147 . Still, we appreciate your contribution. Thank you.

Closing as there is. a duplicate #1147 . Still, we appreciate your contribution. Thank you.


Can you explain more about no_aug_epochs args ?

I read your paper and got the no_aug_epochs is use to close the mosaic augment. When I look to the code, I got this part for close mosaic and add l1 loss to training.
def before_epoch(self):
    logger.info("---> start train epoch{}".format(self.epoch + 1))

    if self.epoch + 1 == self.max_epoch - self.exp.no_aug_epochs or self.no_aug:
        logger.info("--->No mosaic aug now!")
        self.train_loader.close_mosaic()
        logger.info("--->Add additional L1 loss now!")
        if self.is_distributed:
            self.model.module.head.use_l1 = True
        else:
            self.model.head.use_l1 = True
        self.exp.eval_interval = 1
        if not self.no_aug:
            self.save_ckpt(ckpt_name="last_mosaic_epoch")

I have two questions.
First, Why do you not use mosaic for entries training?
Second, in the paper, it's said you use BCE Loss and IoU Loss. Why do you add l1 loss to training after close mosaic?

@RTae

Mosaic will introduce tons of inaccurate bounding boxes. You can refer to a sample image here:
https://github.com/ultralytics/yolov5/issues/2151
So close the Mosaic will avoid those inaccurate bounding boxes. We have trained with mosaic for 285 epochs, we can still enjoy the gain of Mosaic.

Same reason as mentioned above. Before closing the aug, there are many inaccurate bounding boxes, so using too strong a regression loss will hurt the performance. So we add l1 loss only for the last 15 epochs. But this will only improve the mAP by 0.1~0.2%. Also, you can replace IoU Loss with GIoU Loss after closing mosaic, which will probably give you 0.1% more gain. But overall, these are very trival. So we didn't mention them in our tech report.

@Joker316701882 Thank you, your answer help me a lot to understand yolox. Last, I have some favor to ask you. Do you have any source about anchor-free detector?

@Joker316701882 I'm experimenting with closing mosaic on YOLOv5 like you have with YOLOX, and was wondering if you tried other values in addition to 15, i.e. 30 epochs or 10 epochs?
I was thinking the EMA is in the middle here confusing the close-mosaic effect since changes to the base model will take many iterations to begin to propagate into the EMA, but I don't see any action to take there.

@glenn-jocher Hi. In our experiments, we can observe an immediate improvement on mAP after closing mosaic_aug. It usually achieves the best result between the 5th and 10th epoch after that. We set the default no_aug_epochs to 15 to ensure sufficient iterations on some small customed datasets.
On COCO, it performs similarly when no_aug_epochs is set to 10 and 15. But 5 is a bit worse than 10 and 15 epochs.

@Joker316701882 ok super interesting, thanks! I just started two trainings closing mosaic at 15 and 30, I'll report back my results here.

@Joker316701882 ok my two runs are done, I see the same results as you, immediate improvement for about 5-10 epochs and then a drop.
--close-mosaic 15 peaked 8 epochs after closing, --close-mosaic 30 peaked 10 epochs after closing. This was at --batch-size 128 on COCO for 300 epochs. Both showed about +0.3 mAP bump :)


Github bot is not detecting linked issue

I linked the issue when opening a new PR but still got this message and the check failed

I think this action doesn't exist now


Combine dictionary files into data/

Consolidate dicts/ and data/ directory

@nieldlr

@nieldlr Let me know if any action is needed on my end to merge this change in

@zurawiki this is looking great! Just added one more question regarding the order of merging this PR & #35.

Your preference. I'll rebase either PR
On Mon, Sep 25, 2017, 1:38 AM Niel de la Rouviere<EMAIL_ADDRESS>wrote:

@zurawiki https://github.com/zurawiki this is looking great! Just added
one more question regarding the order of merging this PR & #35
https://github.com/nieldlr/Hanzi/pull/35.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nieldlr/Hanzi/pull/33#issuecomment-331814453, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABZW43lBnz-h5xdQN5c_QrW3p5ZuMFMPks5sl2ZxgaJpZM4OiE2u
.

He, if it helps make a decision, I'd love to get this PR in and then I'll update all the other open PRs to accommodate. I'm looking forward to getting these changes out!

Sweet @zurawiki, let's do this :)


[#104451064] BUGFIX (urgent): There may not be a logged-in user for user updates

This method was assuming that current_user exists, but this method doesn't require login and breaks if called without a current_user.
500s in the logs caused by:
'AnonymousUserMixin' object has no attribute 'email_address'

:+1:


Issues while upgraded from 1.0.1 to 1.0.2

I am getting below issues when i had upgraded
TypeError: ((intermediate value)(intermediate value)(intermediate value) || []).reduce is not a function
or
TypeError: (sources || []).reduce is not a function

eventSources is defined on scope as below
eg: $scope.eventSources = [{"test": 1}]
Any help here would help to proceed further.
Thanks

I have the same problem however I'm using version 1.01.
The exact same code works running in localhost on Windows but throws an error when run on LAN with Ubuntu.

Same error here. Still no clues to fix it?

I had the same problem using version 1.0.2.
I fixed it downgrading angular-ui-calendar to version 1.0.1 and fullcalendar to version 2.3.1.
BTW, I am also using:

angular 1.4.8
jquery 2.1.4
moment 2.10.6

Hope it helps!