User and Group management page for JupyterHub

There needs to be a way to associate metadata with user/groups and edit those values:
Example user cases:

https://github.com/yuvipanda/jupyterhub-ssh we would like to associate ssh public/private keys with user
https://github.com/Quansight/qhub-cloud/blob/dev/qhub/template/{{ cookiecutter.repo_directory }}/templates/jupyterhub_config.py.j2#L27 we need to associate a uid/gid to groups etc.

Would be nice to have api endpoints that expose:

public information about a user that is accessible to anyone
secrets that can be create/update/deleted I'm inspired by https://docs.github.com/en/rest/reference/actions#secrets

We can envision with secrets an admin / user of a group could add environment variables that then get set on the launched jupyterlab or dashboard.

Jupyterhub_ssh simplest case:

jupyterhub_config.py needs to import a custom handler, which in turn imports a UserMetadata ORM model. This gives us an extra table in the JupyterHub database, and give it the same key as the User table.
Add a UI handler for a new User Metadata page(s) so we can enter metadata attributes for any user, probably stored in JSON form in the DB, but with individual entries on different rows in the UI. e.g. enter 'jupyterhub_ssh_publickey' for a user.
Add a handler for the REST API to get metadata for a named user

Note that in order to simplify the import process in JupyterHub, it would be easier not to have a direct ORM link between User and UserMetadata.
Assuming jupyterhub_ssh is able to call our API, this should be sufficient if e.g. we wanted to store a 'jupyterhub_ssh_enabled' flag as user metadata, and then change jupyterhub_ssh so that it checks this flag for a user before allowing access (via password token) or not.
However, for access via SSH private key, I'm not sure if the above is sufficient at scale - that the user identity won't be known unless jupyterhub_ssh can look up a user based on the public key stored in metadata value. i.e. it may need to map from public key to user, rather than just user to metadata value.
If this is the case, then it might be possible to run an extra REST endpoint to do that lookup, perhaps caching all metadata values in memory.
I haven't thought yet about adding encryption for secrets.
For the uid look up case:
I've perhaps misunderstood, but I'm not sure how this could work as JupyterHub UserMetadata - surely mapping from user to uid needs to happen well before JupyterHub even exists, at the qhub render stage?


macOS Sequoia 15.1 Beta UnableToLoadSymbol

thread 'main' panicked at /Users/andrewgazelka/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tango-bench-0.6.0/src/dylib.rs:62:60:
called `Result::unwrap()` on an `Err` value: UnableToLoadSymbol(DlSym { desc: "dlsym(0x7d0b1660, tango_count): symbol not found" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: bench failed, to rerun pass `--bench paletted_container`

https://github.com/andrewgazelka/palette
running
cargo bench -- compare

Can you please provide the output of following command:
$ nm -g [path-to-bench-bin] | grep _tango

Path to benchmark is usually in target/release/deps/ and printed by cargo bench command before running the benchmark.

Most probably the problem is that there is no build.rs with following content as required by the docs.
fn main() {
    println!("cargo:rustc-link-arg-benches=-rdynamic");
    println!("cargo:rerun-if-changed=build.rs");
}

fn main() {
    println!("cargo:rustc-link-arg-benches=-rdynamic");
    println!("cargo:rerun-if-changed=build.rs");
}

Ah yea that looks like it resolved it. Previously seemed like
rustflags = ["-Zexport-executable-symbols"]

got away with it on macOS without running the build script but potentially it wasn't applied correctly or macOS changed 🤷♂. Regardless, I was doing it different than the recommended way on macOS anyway, so I will close this.

One valuable lesson to learn I think is providing clear error messages to the user. I created #38 to address this issue. Thank you for your feedback.

I'm running into a similar issue on Linux:
thread 'main' panicked at /home/USER/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tango-bench-0.6.0/src/dylib.rs:62:60: called Result::unwrap()on anErr value: UnableToLoadSymbol(DlSym { desc: "/home/USER/Documents/best-combination/src-tauri/./target/benchmarks/best-combination.patched: undefined symbol: tango_init" })
My build.rs looks like this:
fn main() {
    println!("cargo:rustc-link-arg-benches=-rdynamic");
    println!("cargo:rerun-if-changed=build.rs");
    tauri_build::build()
}

and the benchmark file like this:
use std::hint::black_box;

use best_combination_lib::{
    best_combination_all, best_combination_multi_1, best_combination_multi_2,
    best_combination_single, load_data,
};
use betting_game_data::Data;
use tango_bench::*;

fn best_combination_benchmarks() -> impl IntoBenchmarks {
    let data: &'static Data = Box::leak(Box::new(load_data()));

    return [
        benchmark_fn("benchmark_single", |b| {
            b.iter(|| best_combination_single(black_box(data)))
        }),
        benchmark_fn("benchmark_multi_1", |b| {
            b.iter(|| best_combination_multi_1(black_box(data)))
        }),
        benchmark_fn("benchmark_all", |b| {
            b.iter(|| best_combination_all(black_box(data)))
        }),
        benchmark_fn("benchmark_multi_2", |b| {
            b.iter(|| best_combination_multi_2(black_box(data)))
        }),
    ];
}

tango_benchmarks!(best_combination_benchmarks());
tango_main!();

I'm running:
cargo export target/benchmarks -- bench --bench=best-combination  and then cargo bench -q --bench=best-combination -- compare ./target/benchmarks/best-combination similar to the example in the README.
I'm not very familiar with dynamic linking and this CLI, so any help would be appreciated!


Remove unwanted text in replication

Sometimes gems add any messages to output on initialization phase.
For example, erubis gem add ** Erubis 2.7.0" or newrelic add Cannot find or read newrelic.yml.
This noise breaks down dump loading.
I've fixed this situation. All previous output will be ignored in dump. And only result will be in output.

Merged. Thanks!


Add field and model in modelviz

Related to #1537.
I also added model as it is the same deal than the fields.

Coverage decreased (-70.2%) to 0.0% when pulling 17e48332569e28a15b610eb33880343c7c2f526e on Gagaro:master into 4c6f653713da1e50d23b88e36a2b3c0c69fe3fb9 on django-extensions:master.

Because the generation of the data and the retrieval of the data are two distinct things, the best way I found is to drop the field and model values from the data when we get it if is for a JSON export.

Thanks !


Duplicated tabs

In "View your personal notifications" section I see 2 previous version tab

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

ID: c2fdc7bf-dd88-5f39-cfaf-77dca428990e
Version Independent ID: c939066c-c671-7f50-3ba3-9916b0f4cd4c
Content: Manage personal notification settings - Azure DevOps
Content Source: docs/notifications/howto-manage-personal-notifications.md
Product: devops
GitHub Login: @chcomley
Microsoft Alias: chcomley

@turibbio Thanks for the heads up. Currently working on it and will push a fix to master today. Thanks again!


Put more info in the __repr__ of SOMA objects.

This adds more information to the general __repr__ of SOMA objects, including their open mode and status, and slightly reformats the representation of collections.
It also ensures that repr will work on objects and collections that have been closed, and that repr will only recurse into sub-elements of a collection that have already been opened (so it doesn't eagerly open up an entire collection tree).

Yet another entry from the List Of Things I Notice While Doing Other Things.

Codecov Report
Base: 79.75% // Head: 90.71% // Increases project coverage by +10.96% :tada:

Coverage data is based on head (81e364f) compared to base (badb5d6).
Patch coverage: 96.55% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #912       +/-   ##
===========================================
+ Coverage   79.75%   90.71%   +10.96%
===========================================
  Files          72       30       -42
  Lines        3689     2015     -1674
===========================================
- Hits         2942     1828     -1114
+ Misses        747      187      -560

Flag
Coverage Δ

python
90.71% <96.55%> (+0.04%)
:arrow_up:

r
?

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

Impacted Files
Coverage Δ

apis/python/src/tiledbsoma/collection.py
92.57% <96.00%> (+0.73%)
:arrow_up:

apis/python/src/tiledbsoma/tiledb_object.py
95.89% <100.00%> (+0.17%)
:arrow_up:

apis/python/src/tiledbsoma/tdb_handles.py
93.19% <0.00%> (-0.69%)
:arrow_down:

src/rinterface.cpp

inst/tiledb/include/tiledb/schema_base.h

inst/tiledb/include/tiledb/query_condition.h

inst/tiledb/include/tiledb/utils.h

R/TileDBGroup.R

R/utils-arrow.R

inst/tiledb/include/tiledb/config.h

... and 35 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I don't have a better idea - and really like the speed and overhead improvements. So am approving the PR. Just wanted to point out a sharp edge in the UX of this change.

There’s definitely no perfect solution here. The inconsistency is a bit strange, but the alternative is, in the worst case, “I tried to print this thing and it started reading from disk / made a bajillion network requests and took 10 seconds”.
This makes me think that in the future an “always open everything eagerly” knob (possibly in the context) or just an “open everything in this collection” method might be useful but that’s neither here nor there.

This makes me think that in the future an “always open everything eagerly” knob (possibly in the context) or just an “open everything in this collection” method might be useful but that’s neither here nor there.

Here are options I see:

print only the children of the collection.  Always fast, always consistent.
Current implementation - opportunistically print cached grandchildren, etc.   Always fast, sometimes 'huh'?
Do fast & dirty in the repr (i.e. option 1), but have a verbose method (mohr_repr()) that prints entire tree and does greedy open if data not cached
Control behavior of repr #3 with a flag, toggling between modes

nothing brilliant - really different strokes for different use cases.


19042.662 20H2 Release preview not working

Hello to all.
I'm windows insider on release preview channel and i received silently an update to 19042.662.
So the last rdpwrap.ini stopped working.
I thought i'd let everybody know.

Just temporary workaround:
Uninstalling KB4586781 will revert to 10.0.19041.630 that works with rdpwrap.ini  of 2020-11-01 version.

If you are tracking a release preview version of windows, then you should also be tracking a ini file repo that also tracks these versions, like this one : https://github.com/sebaxakerhtc/rdpwrap.ini

Thanks @tomkanok & @robbak for the advices which i followed. For the moment i don't see other solutions.

Could be related (also a KB patch): https://github.com/stascorp/rdpwrap/issues/1223

2020-11 Cumulative Update Preview for Windows 10 Version 20H2 for x64-based Systems (KB4586853] is what breaks RdpWrap. The other updates that were released Tuesday are fine with RDPWrap, removing KB4586853 and rebooting allows listener to work. I see threads stating the .ini should not need to change, however the latest .ini that has worked for months no longer work with KB4586853.


[android] Set headers, content type and cookies for the server request

Hi,
I read about the limitations of android not calling the JS callback. So, I looked into your source code and found this inside the src/android/LocationUpdateService.java:
DefaultHttpClient httpClient = new DefaultHttpClient();
HttpPost request = new HttpPost(url);
DefaultHttpClient httpClient = new DefaultHttpClient();
HttpPost request = new HttpPost(url);

JSONObject location = new JSONObject();
location.put("latitude", l.getLatitude());
location.put("longitude", l.getLongitude());
location.put("accuracy", l.getAccuracy());
location.put("speed", l.getSpeed());
location.put("recorded_at", l.getRecordedAt());
params.put("location", location);

StringEntity se = new StringEntity(params.toString());
request.setEntity(se);
request.setHeader("Accept", "application/json");
request.setHeader("Content-type", "application/json");
Log.d(TAG, "Posting to " + request.getURI().toString());
HttpResponse response = httpClient.execute(request);

Here, the request method (POST), the content type (application/json) and the params are set to fixed values / a fixed structure. It would be awesome, if that could be more flexible.
The background is, I have to deal with an (rather old and weird) existing server api, that only accepts Content-Type: application/x-www-form-urlencoded, the content itself is therefore not json but in the form field[subfield1]=somevalue&field[subfield2]=foobar and it uses cookies for authentication.
So, is it possible, to integrate such a flexibility into your project? At a glance, the features would be

setting a custom structure/format how data is passed to the server (passing a custom structure AND a format like json or form encoded to the android api)
set custom headers
add cookies for authentication

FYI Android has been completely refactored

No more in-plugin HTTP -- plugin now executes your Javascript callback, just like iOS
Significantly improved battery performance

http://christocracy.github.io/cordova-background-geolocation/


ADC (Automatic Deep Compression) example + features, tests, bug fixes

This is a merge of the ADC branch and master.
ADC (using a DDPG RL agent to compress image classifiers) is still WiP and requires
An unreleased version of Coach (https://github.com/NervanaSystems/coach).
Small features in this commit:
-Added model_find_module() - find module object given its name
-Added tests:
test_summarygraph.py: test_simplenet() - Added a regression test to target a
bug that occurs when taking the predecessor of the first node in a graph
test_ranking.py - test_ch_ranking, test_ranked_channel_pruning
test_model_summary.py - test_png_generation, test_summary (sparsity/
compute/model/modules)

add channel ranking and pruning: pruning/ranked_structures_pruner.py
Add a CIFAR10 VGG16 model: models/cifar10/vgg_cifar.py
Thinning: change the level of some log messages – some of the messages were
moved to ‘debug’ level because they are not usually interesting.
Add a function to print nicely formatted integers - distiller/utils.py
Sensitivity analysis for channels-removal
compress_classifier.py – handle keyboard interrupts
compress_classifier.py – fix re-raise of exceptions, so they maintain call-stack

Bug fixes in this commit:

Thinning bug fix: handle zero-sized 'indices' tensor
During the thinning process, the 'indices' tensor can become zero-sized,
and will have an undefiend length.  Therefore, we need to check for this
situation when assessing the number of elements in 'indices'
Language model: adjust main.py to new distiller.model_summary API

Unfortunately, this is an example of a feature branch gone wild.  Too many unrelated, or semi-related, features and bug-fixes creeped into this branch, making it bloated and risky to merge back into 'master'.
I hope I've learned my lesson :-)


KSM tuning

We set KSM settings (when available) from cc-proxy.
Our default setting is the aggressive one, as we're trying to share as much memory as possible. The default KSM setting knob can be selected from the cc-proxy command line (cc-proxy -ksm)
The initial KSM settings are restored when the proxy terminates.

Coverage decreased (-8.7%) to 65.521% when pulling f2c222db6d0d82aa5c1e7c336b81555e8b8813ec on sameo/topic/ksm into d7a4dd8ad3213355f6621193bf050839d084d00d on master.

Looks good. Can you add some unit-tests though? An 8.7% coverage drop is quite a lot.

Coverage decreased (-10.9%) to 63.361% when pulling 59392a6248326087158857236795bd6a477ee2d5 on sameo/topic/ksm into d7a4dd8ad3213355f6621193bf050839d084d00d on master.

Coverage decreased (-10.9%) to 63.361% when pulling 59392a6248326087158857236795bd6a477ee2d5 on sameo/topic/ksm into d7a4dd8ad3213355f6621193bf050839d084d00d on master.

I guess this won't work if ksmd is not running, do you plan to validate that? or how you plan to address the case where CONFIG_KSM=n ?

Coverage decreased (-10.6%) to 63.677% when pulling 12277b4591c9595872217d4a0345c7b899a3fb31 on sameo/topic/ksm into d7a4dd8ad3213355f6621193bf050839d084d00d on master.

@devimc

I guess this won't work if ksmd is not running, do you plan to validate that? or how you plan to address the case where CONFIG_KSM=n ?

isKSMAvailable() tracks if KSM is supported and the code is a NO-OP if it's not.

@sameo yes, but you are not validating ksmd is running, do you think checking /sys/kernel/mm/ksm/run could be a good idea?

@devimc If ksmd is not running, we turn it on with our first ksmTune.

Coverage decreased (-10.8%) to 63.464% when pulling aa4a4504d85ba8852666475f75dab12e914dbc7f on sameo/topic/ksm into d7a4dd8ad3213355f6621193bf050839d084d00d on master.

Coverage decreased (-10.8%) to 63.464% when pulling aa4a4504d85ba8852666475f75dab12e914dbc7f on sameo/topic/ksm into d7a4dd8ad3213355f6621193bf050839d084d00d on master.

If ksmd is not running, we turn it on with our first ksmTune.

I think it that would merit a comment explaining this behaviour as it isn't actually that obvious.

Coverage decreased (-11.07%) to 63.184% when pulling 4a3c6126f91188de706ffbcb5c6efd767293bb40 on sameo/topic/ksm into c0805cc0d7a3cf5632159efbd00b412386006dd5 on master.

Coverage decreased (-4.7%) to 69.587% when pulling 7fa7dd963bf89c24b34ed5780c62ccefbbf4ac21 on sameo/topic/ksm into c0805cc0d7a3cf5632159efbd00b412386006dd5 on master.

Coverage decreased (-4.7%) to 69.587% when pulling 7fa7dd963bf89c24b34ed5780c62ccefbbf4ac21 on sameo/topic/ksm into c0805cc0d7a3cf5632159efbd00b412386006dd5 on master.

@sameo is this PR stable for (re)review now?
I'll note, the CIs seem to have failed on CRIO tests (test instability I suspect) /cc @chavafg

Coverage increased (+0.3%) to 74.587% when pulling 0af63039470851a4a7ae85e58d19d04ca31cdbe3 on sameo/topic/ksm into c0805cc0d7a3cf5632159efbd00b412386006dd5 on master.

Coverage decreased (-4.7%) to 69.587% when pulling 135a69d8c4638f30c7ac9ef68035d70efe9694c8 on sameo/topic/ksm into c0805cc0d7a3cf5632159efbd00b412386006dd5 on master.

Coverage decreased (-4.4%) to 69.862% when pulling 8b574605fd1df3381a5472893d43142e2fc8ab3e on sameo/topic/ksm into c0805cc0d7a3cf5632159efbd00b412386006dd5 on master.

Coverage decreased (-4.4%) to 69.862% when pulling 8b574605fd1df3381a5472893d43142e2fc8ab3e on sameo/topic/ksm into c0805cc0d7a3cf5632159efbd00b412386006dd5 on master.

Coverage decreased (-4.4%) to 69.862% when pulling 8b574605fd1df3381a5472893d43142e2fc8ab3e on sameo/topic/ksm into c0805cc0d7a3cf5632159efbd00b412386006dd5 on master.

Coverage decreased (-4.8%) to 69.412% when pulling 493cc30cf9e8adcb4e127ee79b0b26920a648ab9 on sameo/topic/ksm into c0805cc0d7a3cf5632159efbd00b412386006dd5 on master.

Coverage decreased (-5.2%) to 69.097% when pulling 49d9b71d8f084c98951874e4136b368b9f5c4bd9 on sameo/topic/ksm into a1225105804b27ff80529beab0602d0a41c7d74f on master.

Coverage decreased (-5.2%) to 69.097% when pulling 49d9b71d8f084c98951874e4136b368b9f5c4bd9 on sameo/topic/ksm into a1225105804b27ff80529beab0602d0a41c7d74f on master.

Coverage decreased (-5.2%) to 69.097% when pulling 86419930b748f964b5bbc2610efe86c3907d011e on sameo/topic/ksm into a1225105804b27ff80529beab0602d0a41c7d74f on master.

Coverage decreased (-5.2%) to 69.097% when pulling 86419930b748f964b5bbc2610efe86c3907d011e on sameo/topic/ksm into a1225105804b27ff80529beab0602d0a41c7d74f on master.

Coverage decreased (-4.9%) to 69.7% when pulling 1e1a6d755cd947dc9070c6cb1a24f5c0ff0c704c on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-4.9%) to 69.7% when pulling 1e1a6d755cd947dc9070c6cb1a24f5c0ff0c704c on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-4.9%) to 69.7% when pulling 1e1a6d755cd947dc9070c6cb1a24f5c0ff0c704c on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-1.8%) to 72.807% when pulling 053c3fd253ccf63fcac4279aebba44a04f155986 on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

@grahamwhaley Now with KSM tuning docs: https://github.com/clearcontainers/proxy/pull/118/files#diff-9d79245b4e2f89a795cb731140d6f1be

Coverage decreased (-2.1%) to 72.474% when pulling 19f287c2c42d2458b08d24295c4c77b405428d40 on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-2.1%) to 72.474% when pulling 19f287c2c42d2458b08d24295c4c77b405428d40 on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

@iphutch Could you please review the ksm.md file ?

Coverage decreased (-1.4%) to 73.21% when pulling 1566c6fd206941a43bdd6d84386ee40e5ffdcb15 on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-0.4%) to 74.187% when pulling 628c10d6f9940517b1706bc26c8c45dc26649e2f on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-0.4%) to 74.187% when pulling 628c10d6f9940517b1706bc26c8c45dc26649e2f on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-0.4%) to 74.187% when pulling 6a9b0ad0a6ddaf04f672d692cde1ef3a504ec4bd on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

@iphutch thanks for the review. I think I addressed all your comments, could you please review again?

Coverage decreased (-0.1%) to 74.458% when pulling be7ebc9cfa78e325cd26a01d3d30a4fe6973ebd9 on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-0.1%) to 74.458% when pulling be7ebc9cfa78e325cd26a01d3d30a4fe6973ebd9 on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-0.1%) to 74.458% when pulling be7ebc9cfa78e325cd26a01d3d30a4fe6973ebd9 on sameo/topic/ksm into 79ff321da6d34682fea11a47dff0e5ca72c20a01 on master.

Coverage decreased (-0.07%) to 74.187% when pulling f344c1c9fb4dace1b4c5168e1035a77650b72e57 on sameo/topic/ksm into e9cee5aa68bf2b5dd28b062f2fd67b98df3d0a6c on master.

Coverage decreased (-0.07%) to 74.187% when pulling 9889d95ab249d4cb7ee424c206353d087d9716f5 on sameo/topic/ksm into e9cee5aa68bf2b5dd28b062f2fd67b98df3d0a6c on master.

Coverage decreased (-0.07%) to 74.187% when pulling 9889d95ab249d4cb7ee424c206353d087d9716f5 on sameo/topic/ksm into e9cee5aa68bf2b5dd28b062f2fd67b98df3d0a6c on master.

Coverage decreased (-0.07%) to 74.187% when pulling 9889d95ab249d4cb7ee424c206353d087d9716f5 on sameo/topic/ksm into e9cee5aa68bf2b5dd28b062f2fd67b98df3d0a6c on master.

Coverage decreased (-0.07%) to 74.187% when pulling 94dde7b5af087167913f4fea57ccf9a10012a82a on sameo/topic/ksm into e9cee5aa68bf2b5dd28b062f2fd67b98df3d0a6c on master.

Coverage decreased (-0.07%) to 74.187% when pulling 94dde7b5af087167913f4fea57ccf9a10012a82a on sameo/topic/ksm into e9cee5aa68bf2b5dd28b062f2fd67b98df3d0a6c on master.

Coverage decreased (-0.07%) to 74.187% when pulling 94dde7b5af087167913f4fea57ccf9a10012a82a on sameo/topic/ksm into e9cee5aa68bf2b5dd28b062f2fd67b98df3d0a6c on master.


typo: extensibilty -> extensibility

@nschonni : Thanks for your contribution! The author, @alexhomer1, has been notified to review your proposed change.


Allow to decide which signatures to verify by inspecting all signature parameters

Also bump version to 0.15.1 and bring README up to speed.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

70 of 70 (100.0%)  changed or added relevant lines in 6 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 93.233%

Files with Coverage Reduction
New Missed Lines
%

src/NSign.Abstractions/Signatures/SignatureComponent.cs
3
83.52%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
2465

Relevant Lines:
2678

💛  - Coveralls


fixed: quote command and args if needed

fix execCommand() function on win32 env

LGTM
this issue caused by followings.
https://github.com/nodejs/node/issues/7367
https://nodejs.org/dist/latest-v8.x/docs/api/child_process.html#child_process_spawning_bat_and_cmd_files_on_windows


fix issue #51

compile with Vaadin 24.1.0
using ColumnPathRenderer explicitely
extend exception log with key for column with missing value

The code format settings are still modified by my IDE, despite my 2 additional commits. I assume, this was done during the commit phase, so sorry for that. I do not want to alter your file/code format settings.

Thanks for your contribution. We will merge it to a new major version of the add-on, targeting Vaadin 24 (The current version attempts to be compatible with "23.1+" and it's quite difficult to implement such low level hacks while supporting a broad range of framework versions).

Thanks again! The fix has been released in version 2.0.0.


add BracketHighlighter as default setup pack

More and more student is having unnecessary error for not closing their brackets, this additional package can help them to notice them easily

Totally agree, thanks for contributing 🙏


Align jackson-dataformat-xml version with Quarkus jackson

Example builds failed, but that's expected as we need to bump the project version(s) on that side since we did the release.
Hence merging this PR...


update to scalajs 1.1.1

I am updating the library to scalajs 1.1.1
because I need it for my app.
this is one of my first tries on github.
Sorry if I am doing wrong, I will try to make it better if something bad happens.
I am not sure if the pull request was made by the way. :P
but in my local the lib is working with scalajs 1.1.1

Awesome, thank you! The PR looks really good :+1:
I just added some small comments to fix.


Scoreboard larger width adjustments

Not sure if you ever had/noticed this problem with the SaarCTF, but with this years FAUST CTF with 8 services even on a Full HD screen the rightmost service is not visible. Therefore I propose two changes to make horizontal scrolling less often needed:

Limit the visual length of a teams name. While it is also useful to limit the length of a team during registration, currently when there is one team (or troll) with a very long name, the whole scoreboard accommodates for that and wastes horizontal screen space. Therefore we limit the size which the Team Name column can grow to and hide the overflow with ellipsis.
If you want to see the full untruncated name you can now use the tooltip. Also move the tooltip button to be always right aligned. This way all 'i's are in one nice column. Note: The Name on the Team Page is not truncated as this only annoys the team itself.
Make the chart on the Team Page sticky so that it stays in place when horizontally scrolling.
Make the first two column of the scoreboard (rank and team) sticky. To make this visually appealing this does need some fixing however:

The borders will not be drawn with border-collapse: collapse (source). To fix this revert back to border-collapse: separate and hide the top and left borders.
Add a right side shadow to the columns. Make the bottom shadow of the sticky header row one elevation (from material design) higher
To fix the right side shadow in firefox which would leak over to the previous and next row use clip-path
Darkmode!

Thank you for all the work!
So far we provided the "slim mode" in the menu for this issue - but your solution is much cleaner and more user-friendly.

Btw, I added two more changes that might be interesting for you:

we added a small "scoreboard by" hint on the bottom of the page. It could replace the hint in the header that you used for Faust CTF.
we finally decided the a license for this project (MIT)

Best
Markus


save model parameters

hello,
I would like to start by thanking you for your amazing effort in this library.
I would like to suggest a feature or collaborate in some way to add this feature, but first I wanted to make sure that I was really unable to find it. I was wondering if there is a save_model feature or save model weights or state_dict so the trained model can be deployed or retrained on other dataset
Thanks again for your time and efforts

what I implemented on my local copy, if you agree or no problems found in my code
I can open a PR

# Existing imports
class DeepSVDD(BaseDeepAD):
     # Existing code
    def save_model(self, save_path):
        """
        Save the trained model to a file.

        Parameters
        ----------
        save_path : str
            The path where the model will be saved.
        """
        super().save_model(save_path)

    def load_model(self, load_path):
        """
        Load a pre-trained model and its relevant information.

        Parameters
        ----------
        load_path : str
            The path from which the model will be loaded.
        """
        super().load_model(load_path)

AND in the BaseDeepAD class

# Existing imports

class BaseDeepAD(metaclass=ABCMeta):
     # Existing code

    def save_model(self, save_path):
        """
        Save the trained model to a file.

        Parameters
        ----------
        save_path : str
            The path where the model will be saved.
        """
        if not os.path.exists(save_path):
            os.makedirs(save_path)

        model_info = {
            'model_name': self.model_name,
            'data_type': self.data_type,
            'network': self.network,
            'seq_len': self.seq_len,
            'stride': self.stride,
            'epochs': self.epochs,
            'batch_size': self.batch_size,
            'lr': self.lr,
            'device': self.device,
            'contamination': self.contamination,
            'n_ensemble': self.n_ensemble,
            'verbose': self.verbose,
            'random_state': self.random_state
        }

        model_state = {
            'net_state_dict': self.net.state_dict(),
            'criterion': self.criterion,
            'decision_scores_': self.decision_scores_,
            'labels_': self.labels_,
            'threshold_': self.threshold_,
            'epoch_time': self.epoch_time
        }

        save_info_path = os.path.join(save_path, 'model_info.pth')
        save_state_path = os.path.join(save_path, 'model_state.pth')

        torch.save(model_info, save_info_path)
        torch.save(model_state, save_state_path)

        print(f"\nModel saved successfully at {save_path}\n")

    def load_model(self, load_path):
        """
        Load a pre-trained model and its relevant information.

        Parameters
        ----------
        load_path : str
            The path from which the model will be loaded.
        """
        model_info_path = os.path.join(load_path, 'model_info.pth')
        model_state_path = os.path.join(load_path, 'model_state.pth')

        model_info = torch.load(model_info_path)
        model_state = torch.load(model_state_path)

        self.model_name = model_info['model_name']
        self.data_type = model_info['data_type']
        self.network = model_info['network']
        self.seq_len = model_info['seq_len']
        self.stride = model_info['stride']
        self.epochs = model_info['epochs']
        self.batch_size = model_info['batch_size']
        self.lr = model_info['lr']
        self.device = model_info['device']
        self.contamination = model_info['contamination']
        self.n_ensemble = model_info['n_ensemble']
        self.verbose = model_info['verbose']
        self.random_state = model_info['random_state']

        self.criterion = model_state['criterion']
        self.decision_scores_ = model_state['decision_scores_']
        self.labels_ = model_state['labels_']
        self.threshold_ = model_state['threshold_']
        self.epoch_time = model_state['epoch_time']

        # Build the network based on the loaded model information
        network_params = {
            'n_features': self.n_features,
            'n_hidden': self.hidden_dims,
            'n_output': self.rep_dim,
            'activation': self.act,
            'bias': self.bias
        }

        if self.network == 'Transformer':
            network_params['n_heads'] = self.n_heads
            network_params['d_model'] = self.d_model
            network_params['pos_encoding'] = self.pos_encoding
            network_params['norm'] = self.norm
            network_params['attn'] = self.attn
            network_params['seq_len'] = self.seq_len
        elif self.network == 'ConvSeq':
            network_params['seq_len'] = self.seq_len

        network_class = get_network(self.network)
        self.net = network_class(**network_params).to(self.device)
        self.net.load_state_dict(model_state['net_state_dict'])

        print(f"Model loaded successfully from {load_path}")

Hi @elsheikh21,
Thank you so much for your interest! It is a very fantastic feature.
I have carefully reviewed your proposal. It is good in general, but there are still some issues. The Deep SVDD class has a parameter named c which is the hypersphere center in the representation space. It will be assigned after fit. Different algorithms may have different in-class parameters. So, I think it may trigger some unexpected error.
If you want to deploy the trained model, one simple way is to save the whole class via pickle.
Please see a single example below.
model = DeepSVDD()
model.fit(x_train)

import pickle
with open('save_file.pkl', 'wb'):
    pickle.dump(model)

with open('save_file.pkl', 'rb')
    model_load = pickle.load(f)
model_load.decision_function(x_test)

@xuhongzuo Thanks for your kind words, I will use your proposed solution and when it works, I will open a PR with it.
Thanks again and have a great day

@xuhongzuo
I opened a PR for this issue, with the save and load methods loaded into the BaseClassAD
and It just came to my mind, on creating an example with the methods used in code, let me wdyt? and I am waiting for your feedback/comments if there are any


Cannot set Image from Camera on Nexus 5?

Hello i just implement , but thi is Cannot set Image from Camera on Nexus 5. how to fix it ?

not enough info


perf: [LG]Improve the performance of parsing long body

Description
Improve the performance while a normal template contains long body.
update the botbuilder-lg version in composer. The time of a 4M file parse is reduced from 42s to 10s

Task Item
#minor
refs https://github.com/microsoft/botbuilder-js/pull/3593

Screenshots

Coverage remained the same at 50.555% when pulling e4dd84daeffc314b1e94644574c4cec58d72befa on lei9444:lgperf into 6728c56d26807d74d3e35d49afa72e25a7cfdce4 on microsoft:main.


couldn’t find key brand in dynamic object

Hello,
When we use trackPurchaseEvent function, we got this error if we don't provide some of optional arguments.
This error has been occurred only on Android and it's perfectly fine on iOS.
If we provide all of the arguments, it works.

Would you please tell me the best practice?
Thanks.

Hi @einsub
As you say you need to provide all arguments. At the moment the implementation for both iOS and Android doesn't do any key-checking in the incoming dictionaries.
A possible enhancement here would be to see if the key exists before retrieving and adding it to the ecommerce-product that is tracked.


getContent tries to parse response as JSON even when request asks for raw data

When we add the Accept header with 'application/vnd.github.v3.raw+json' we are expecting raw data back; but the response handler still tries to parse as JSON and when it fails and returns an error.

This is happening to me also.

This was fixed in a1115dc

This is still happening when using getBlob, when the contents of the blob is a markdown file. I have the Accept header set to application/vnd.github.v3.raw
The result I get Error: Unexpected token #
The raw file is just:
# Android-App

I've added a getRawBlob example here. Let me know if it doesn't work for you.

Thank you. I tried that, and while I can get the data out of the response, the err object is as follows:
{ [Error: Unexpected token #]
  defaultMessage: 'Internal Server Error',
  message: 'Unexpected token #',
  code: '500',
  status: 'Internal Server Error',
  headers: undefined }

Got it, I'll take a look.

Thank you. It just makes it harder to work with Promises (bluebird.promisifyAll()) in this case, since the getBlobAsync() function, with the Accept header set to application/vnd.github.v3.raw will reject.


Tighten OpenEBS RBAC permissions.

What problem is being solved
The default set of RBAC permissions that comes with OpenEBS is very broad: it allows cluster-wide access to all core objects, ability to exec into any container and so on which can pose a security risk.
How this change solves the problem
This change updates both openebs-operator.yaml and the Helm chart in an attempt to limit OpenEBS permissions in the following ways:

Restrict CRUD permissions for core objects to OpenEBS specific namespace.
Allow read-only access to some cluster-wide objects.
Allow cluster-wide access to OpenEBS specific resources.
Remove seemingly unnecessary permissions (more on that below).

Notes
Note that I've removed a few permissions such as "ingresses", "horizontalpodautoscalers" and a couple of others that seemed unnecessary - I searched through OpenEBS code and couldn't find any mention on those being used in any way - but if they are in fact needed for some use-cases, I'd be happy to bring them back (maybe a comment/explanation on what they're used for would be in order).
I have run a few tests with Local Provisioner (both host path and device modes) and cStor engine after making these changes and things worked fine. It would be helpful to run this through your CI as well to make sure nothing is missed.
Let me know what you think.

@r0mant thanks for doing this, we are checking some of the permission issue related to Jiva and other k8s distribution including like GKE, openshift, AKS etc.
We will get back to you with changes if any thing required here.

@r0mant sorry for the delay, started looking into the above changes, the RBAC clusterwide permission for all the k8s resources has been limited to openebs namespace , which will not work in case of Jiva and Local-PV as they can be deployed in any namespace as well, other then openebs.
I am currently looking into this and will get back with more comments.

Some more updates based on GKE and  openshift  based clusters:

Able to create cStor volumes successfully in openebs namespace.

Able to create local PV using hostpath successfully.

Unable to provision jiva volumes in any namespace other than openebs

Unable to provision localPV using device.

( specific to openshift) Admission webhook crashing due to permission issue required to set the  deployemnt ownerReference inn webhook resoureces in openshift based clusters

F1227 01:08:13.164069       1 main.go:85] failed to create validator{openebs-validation-webhook-cfg}: validatingwebhookconfigurations.admissionregistration.k8s.io "openebs-validation-webhook-cfg" is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on: , <nil>failed to initialize validation server

When provisioning fails, the controller tries to patch that information onto the PVC. This will result in
'events "demo-vol1-claim.15e612138a6253cb" is forbidden: User "system:serviceaccount:openebs:openebs-maya-operator" cannot patch resource "events" in API group "" in the namespace "giri"' (will not retry!)

So we will need patch permission also for updating the events.

For fixing the issues observed with Jiva, the following enhancements have to be made to the provisioners:

Set the DeployInOpenEBSNamespace as default for Jiva Storage Classes.
Once upgraded to the new version with reduced RBAC policies, API server will not be able to operate on the Jiva volumes created in another namespace. So Jiva pods should be migrated from application namespace to openebs namespace prior to upgrading with the changes in this PR.

Keeping this on hold, to ensure backward compatibility is maintained.
However for fresh installations, the steps provided in this PR are good as long as the Jiva Storage Classes are configured with "DeployInOpenEBSNamespace" property as follows:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: jiva-pods-in-openebs-ns
  annotations:
    openebs.io/cas-type: jiva
    cas.openebs.io/config: |
      - name: DeployInOpenEBSNamespace
        enabled: "true"
provisioner: openebs.io/provisioner-iscsi

@prateekpandey14 @kmova Were the backward compatibility issues for deploying jiva in openebs fixed?


Overnight, unable to use localhost 4200 on Dev Containers

Command
serve
Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I have a VSCode dev container running several angular projects (ESbuild and Webpack).
Last night, I was able to access localhost:4200 (tunneled through the VSCode Dev Container) but this morning, I need to set the --host <IP_ADDRESS> flag.
I have tried a very simple node express server (just simply serving the phrase hello world on localhost:4200 inside the container and it works fine.
Minimal Reproduction
To reproduce:

Create and open a NodeJS VS Code dev container

mcr.microsoft.com/devcontainers/typescript-node:1-20-bullseye

npm install -g @angular/cli
ng new
ng serve

Expect:

Host PC should access localhost:4200

Actual:

Connection hangs (timeout in curl and chrome)

Workaround:

Set host to <IP_ADDRESS> on the dev server inside the container

Exception or Error
Web server times out

Your Environment
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 17.3.6
Node: 20.12.0
Package Manager: npm 10.5.0
OS: linux x64

Angular: 17.3.6
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.6
@angular-devkit/build-angular   17.3.6
@angular-devkit/core            17.3.6
@angular-devkit/schematics      17.3.6
@schematics/angular             17.3.6
rxjs                            7.8.1
typescript                      5.4.5
zone.js                         0.14.5

Anything else relevant?
No response

Duplicate of https://github.com/angular/angular-cli/issues/27439
See: https://stackoverflow.com/questions/77110607/frontend-app-running-inside-docker-container-not-accessible-from-browser/77111001 and https://github.com/vitejs/vite/discussions/6146 for more info.

Thanks @alan-agius4. But this affects the webpack server also, or, are they related? I have projects that use both esbuild and webpack.

This effects both vite and webpack-dev-server.


"error": "access_denied", "error_description": "Your credentials aren't allowed"

POSTMAN
POST
http://localhost:8000/auth/convert-token
Body
x-www-form-urlencoded
client_id=<client_id>
client_secret=<client_secret>
token=<(jwt credential from the frontend)>
grant_type=convert_token
backend=google-oauth2

same issue here on calling `convert-token'

This is not replicable. Please add more information.

React frontend side library used is @react-oauth/google.
    console.log(response)
    var decoded = jwt_decode(response.credential);
    console.log(decoded)
    googleBackCall(decoded,response)
  }

<GoogleOAuthProvider clientId="xxxxxxxxxxxxx.apps.googleusercontent.com"> //I put actual double checked client id
                <GoogleLogin
                  onSuccess={responseGoogle}
                  onFailure={() => console.log("login cancled")}
                  onError={() => {
                    console.log('Login Failed');
                  }}
                />
              </GoogleOAuthProvider>```
onSuccess an API call is made to the Django backend to get backend application token,
```js import axios from 'axios'

const googleLogin = (accessToken,response) => {
   console.log(accessToken)
axios.post('http://localhost:8000/auth/convert-token',{
    token: accessToken.jti,
    email:accessToken.email,
    first_name:accessToken.given_name,
    last_name:accessToken.family_name,
    backend: 'google-oauth2',
    grant_type: 'convert_token',
    client_id: 'LFG6fbrrKKowufV4Bm6e5JFGGw3xLdcnktG5kg',
    client_secret: 'MeKZwqp9f5iBD1sncIRb7r4hrYCvl51y2Tb1oQezuxO04Cb0sJAtEazQu5yYiqUx83v7zZhDzVquBTw2GkY6LfvVqNxufPSVhHm4jTGIdclqRGu0Ow8lLO0wu3bmV7'
})
.then((res)=>{
    localStorage.setItem('access_token',res.data.access_token)
    localStorage.setItem('refresh_token',res.data.refresh_token)
})
}

export default googleLogin```

backend social login is handled by `drf_social_oauth2`.
The expected behavior is on login from the frontend in Google, an user should be created in the backend.
I have verified the models, serializers, and other backend stuff including settings.py
The error is the response of API with the status `400 Bad Request` and response `{error: "access_denied", error_description: "Your credentials aren't allowed"}`
Payload is something like this
![image](https://github.com/wagnerdelima/drf-social-oauth2/assets/63193129/1b715eb1-7f93-46aa-9418-7669db6f8161)

-- google["credential"] ( JWT Token )
curl -X POST -d "grant_type=convert_token&client_id=11&client_secret=11&backend=google-oauth2&token=<google_token>" http://localhost:8000/auth/convert-token
I have google jwt token which I am passing above curl command , but it is giving the same error as above
--  {"error":"access_denied","error_description":"Your credentials aren't allowed"} on drf-social-auth2.
Same token when i use with from google.oauth2 import id_token , it works good.
requested to provide a quick resolution on this

Facing the same issue, would like it to be reopened


Support fetching docker images from V2 registries

Motivation for this change
The stock dockerTools in nixpkgs support fetching docker images from a V1 docker registry and not a V2 registry; dockerTools pull the whole docker image into the nix store instead of pulling the layers, config, and manifest into the nix store and compositing the image on the fly. This is problematic because dockerTools only work with an out-of-date docker registry version and they are inefficient; inefficient because multiple docker images sharing base layers do not take advantage of deduplication in the nix store.
hocker and the fetchdocker utilities fix these issues. hocker implements its own client against the docker distribution REST API and it does not use the docker client or docker daemon to pull an image from a registry. Each utility of hocker is designed to do one thing well, this translates naturally to a set of Nix functions that produce derivations that fetch docker image layers, the docker image configuration json, and produce an image compositor script. The image compositor script assembles the downloaded and the generated pieces of the docker image from the nix store, streaming it to stdout as a tar archive for use with docker load.
Things TODO next, after merging

[ ] Write a tutorial
[ ] Contribute a manual entry

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[X] macOS
[X] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

CC: @fpletz @grahamc

Note that the cabal tests for hocker are failing because I didn't correctly include the tests data dir in hocker's cabal file. I have this fixed and am releasing to Hackage soon.
I discovered this by building the nixos test myself off of this branch which means I think the nixos test on this PR isn't included in the checks run by CI.
@grahamc is there anyway to mark small or light-weight nixos tests on a PR as required for merge?

The fixes for the tests have been uploaded to hackage so the next time the hackage packages are updated the nixos test in this PR should be working (I will double check it.)

I've run the included nixos test and verified it works.

Ping 👍 am interested in using this as well

@GrahamcOfBorg test hocker-fetchdocker

Failure on aarch64-linux (full log)
Partial log (click to expand)
Package ‘jailbreak-cabal-1.3.2’ in /var/lib/gc-of-borg/nix-test-rs-4/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-4/pkgs/development/haskell-modules/hackage-packages.nix:120699 is not supported on ‘aarch64-linux’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Partial log (click to expand)
while evaluating the attribute ‘drvPath’ at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/lib/customisation.nix:179:13:
while evaluating the attribute ‘drvPath’ at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/lib/customisation.nix:146:13:
while evaluating the attribute ‘buildCommand’ of the derivation ‘vm-test-run-test-hocker-fetchdocker’ at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/pkgs/stdenv/generic/make-derivation.nix:148:11:
while evaluating the attribute ‘buildCommand’ of the derivation ‘nixos-test-driver-test-hocker-fetchdocker’ at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/pkgs/stdenv/generic/make-derivation.nix:148:11:
while evaluating the attribute ‘buildCommand’ of the derivation ‘nixos-vm’ at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/pkgs/stdenv/generic/make-derivation.nix:148:11:
while evaluating the attribute ‘buildCommand’ of the derivation ‘nixos-system-machine-18.03.git.010a831’ at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/pkgs/stdenv/generic/make-derivation.nix:148:11:
while evaluating ‘optionalString’ at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/lib/strings.nix:138:26, called from /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/nixos/modules/system/activation/top-level.nix:40:9:
while evaluating the attribute ‘closure’ of the derivation ‘initrd’ at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/pkgs/stdenv/generic/make-derivation.nix:148:11:
while evaluating anonymous function at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/pkgs/build-support/closure-info.nix:9:1, called from /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/pkgs/build-support/kernel/make-initrd.nix:33:13:
assertion failed at /var/lib/gc-of-borg/.nix-test-rs/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/ogden/pkgs/build-support/closure-info.nix:11:1

Not sure why @GrahamcOfBorg is failing but this works for me. :+1:
cc @grahamc

Thank you @fpletz!

Is this possibly a Nix 2 vs. Nix 1 problem?

@grahamc I'm not sure, I will test it tomorrow morning using Nix 2 to be sure.


Implementation of Service Worker

This is not the final implementation..

[ ] Need to come up with API for Service Worker.
[ ] sw.js should be served from the current directory.
[ ] what if one of the fragment is down/timed out?

closing this in favor of #84 .. Track the progress there.


RFC: Commit vendor

Inspired by https://groups.google.com/forum/#!topic/istio-dev/vpz5w1C-C_0
This is an initial approach to have the vendor dir checked in. It brings the benefit of a totally reproducible and offline build. The normal workflow for building Istio with this feature in would be just 1) Download it (tarball tgz for example) and 2) run make. It should work out of the box in an offline system.
It's worth noting that other [big] projects like kubernetes do this way. I believe it brings more pros than cons (like a bigger repo).
Thoughts?

@jwendell: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
f9ef67a4702207df7f45ba94288114be07a4d675
link
/test istio-pilot-e2e

prow/e2e-smoke.sh
6404dacda3b19bcade024df1fd10281989d0b07a
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
f9ef67a4702207df7f45ba94288114be07a4d675
link
/test istio-pilot-e2e

prow/e2e-smoke.sh
6404dacda3b19bcade024df1fd10281989d0b07a
link
/test e2e-smoke

prow/istio-presubmit.sh
5fe5d10b78fafac5ddefc82b84f8651c88e7d3a1
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
6404dacda3b19bcade024df1fd10281989d0b07a
link
/test e2e-smoke

prow/istio-presubmit.sh
5fe5d10b78fafac5ddefc82b84f8651c88e7d3a1
link
/test istio-presubmit

prow/istio-pilot-e2e.sh
6404dacda3b19bcade024df1fd10281989d0b07a
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
b3b67c652e728ff8618eb9a9dd791d6c8df506a9
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
305eb31f25f345301ade212aeaab7e4cb0a71e75
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

here is the alternative: #3348 - 8mbytes sub module - PTAL

@jwendell: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
be5a87f1d689ada66e5305ec0bdf028565ccfb7d
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

It appears this comes down to a question of trade-offs, i.e. is it worth checking in the vendor directory to istio/istio and keeping things simple or modifying the build process to support sub-modules and coordinating releases across multiple repos.
We were supposed to discuss this in yesterday's call but did not manage to do so as it was pushed down the agenda, it would be good to make this a high priority issue on next week's agenda if we cannot get a consensus through these discussions.

Noted and agreed. We should get a closure since it has been dragging for
weeks. I will put this as the first agenda next week
On Feb 9, 2018 7:51 AM, "Kevin Conner"<EMAIL_ADDRESS>wrote:

It appears this comes down to a question of trade-offs, i.e. is it worth
checking in the vendor directory to istio/istio and keeping things simple
or modifying the build process to support sub-modules and coordinating
releases across multiple repos.
We were supposed to discuss this in yesterday's call but did not manage to
do so as it was pushed down the agenda, it would be good to make this a
high priority issue on next week's agenda if we cannot get a consensus
through these discussions.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/2691#issuecomment-364472318, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AeRtkNcGU5xK2LJx0cuKIr_AjHrGEMcFks5tTGlugaJpZM4RjxU-
.

there is no “modifying the build process” difference between submodule or direct checkin - either way a small change is needed

@jwendell: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
0b9a7ad32a51857ae4811c028d87678d1d9b5b34
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ldemailly Unfortunately I believe you are missing some important aspects but I will try to elaborate on the problems with submodules on the other PR.
I also don't believe they both require changes, with the submodule approach you will have to modify the scripts to use git rather than dep however when committing to the same repo they should work without any necessary changes.  Of course submodules also changes the developer flow which could lead to more serious issues but please take a look at the other PR and comment there.

the current istio build has a bunch of dep run logic which will need to be removed/moved to a separate target either way (when a dependency update is needed instead of mandatory to build)

@jwendell: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
0b9a7ad32a51857ae4811c028d87678d1d9b5b34
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
c3dc50bda7543f2d353ccb7dcfd75bd5f6065984
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
0b9a7ad32a51857ae4811c028d87678d1d9b5b34
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
c9aa8615532a70a8208d0a4788d8506e764c6b1d
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for having brought up the issue !
Fixed through #3348  #3678 #3697
and the growing https://github.com/istio/istio/wiki/Vendor-FAQ


Dashboard > Edit Profile and Private Messages Cleanup

When you're logged in as an administrator, clicking "My Account" in the header gets you to edit your profile within the Dashboard theme. But the header looks weird.
Let's make it match the black header found on Welcome and Waiting for me. Make sure this is also the case on Edit Profile and Private Messages.
Additionally, let's make sure the private messages view screen uses BS4 markup, including fixing the tabs by including the proper tab-pane markup. Make sure that composing and sending and reading private messages looks good in BS4.

(ò_ó)

(ò_ó)

This has already been taken care of in #8918

This has already been taken care of in #8918


How to remove the semicolon

How to remove the semicolon ？

Hi,
instead of removing semicolon I just set my VSC to autoFix linter issues on save:
"eslint.autoFixOnSave": true,
 "eslint.validate": [
        {
            "language": "html",
            "autoFix": true
        },
        {
            "language": "vue",
            "autoFix": true
        },
        {
            "language": "javascript",
            "autoFix": true
        },
        {
            "language": "javascriptreact",
            "autoFix": true
        }
    ],

this way, semicolons are left alone or removed depending on my project's eslint configuration.
Hope it helps.

@afontcu thanks for the nice suggestion. I consider this as a nice solution.
As described in #16 I had to make a choice when created the snippets. At that point the majority of the people include the semicolons. Or at least this was my sense.
Now I see that this changes. So I might remove all semicolons in a future release if more people ask for it.

+1

I love this extension but found myself hitting End and Backspace after using any snippets since I use the StandardJS style which enforces not using semicolons - I have published a fork of this with semicolons removed :sparkles: GitHub || Extension

semi is the rule that governs semi colons be or not to be.

I even added a note on the readme about the fork extension that doesn't include the semicolon.

Use https://github.com/jmsv/vscode-javascript-standard instead

Search VS Code settings or open ~/.config/Code/User/settings.json and set "javascript.format.semicolons": "remove",
Then rightclick a JS file open in the editor and "Format Document With..." "TypeScript and JavaScript Language Features (default)" or simply press the assigned shortcut.

adding this "eslint.codeActionsOnSave.mode": "problems" to settings.json  did it for me.


sniper no longer works due to get being deprecated

needs an update for whatever is replacing get

this hack is dead. last time they did anything with it was before python 3.9.


A simple example for a beginner

Hello.
Where can i find an example of:

a client sending a message to the server
a server sending a broadcast to the clients

i want to understand how to simply ping a server or send a "Hello world" to anyone that is connected.
thank you in advance.

I'm not sure you are aware, but there is the USAGE.md file, which goes through the basic usage of the library.

thank you!, i indeed didnt knew... sorry for my ignorance!


Transition service groups to a persistent data store (comparable to the service endpoints store)

Service group files loaded on demand has been one of the more painful complexities for running contracts. This commit introduces a persistent database comparable to the database used to store service   endpoints. The new groups database is stored at the location specified in the ['Service', 'GroupDatabaseFile'] configuration entry.
The service groups commands were all updated to accommodate the new style. These are SIGNIFICANT changes. To ensure that correctness has not been compromised, a new test was added for storage groups.
Finally, the persistent database required updating several other tests.  This change is, for the moment, a "functionally correct" change to the tests (meaning that all tests now use the correct service groups commands) but there is significant room for cleaning up the process.
Note that this will require changes to the test scripts for PDO contracts (and the notebooks that set up the service groups). The correct approach would be (for tests) to invoke the site-configuration.psh script in place of the create-service-groups script. And a future jupyter notebook will create an interface for managing the database more explicitly.

No particular comments about the PR itself, but more a high-level question.
While client, eservice and pservice are core components of PDO, the service group concept appears to be a useful tool to put things together and create interesting tests and use cases. The question is: are service groups the way PDO will be deployed and used, or is it just one integration approach?

groups are useful for clients not just tests. they bundle a bunch of configuration that would otherwise have to be specified independently. they are strictly a client tool. and... anyone can replace our current client libraries with their own, if they choose. if you completely replaced the python client with a javascript one, would keep groups? maybe.


Function signatures of dependently typed functions are not correct in completions, hover and signature help

Description:
Consider array:map() and array:reduce() functions.
Completions

Signature Help

Those function signatures doesn't reflect the parameters of the function type parameters required by those functions.
Steps to reproduce:
See description
Affected Versions:
2201.1.1-SNAPSHOT

This issue is blocked by #37123.

After the fixes made for the issue #37123 now the signatures are suggesting correctly.

@LakshanWeerasinghe Awesome.. @dulajdilshan is there a way we can improve the array:Type val (parameter of the function parameter)? Because we know the type arr and we should replace arrray:Type with the member type of the array. It will be a good addition if we can do so.
If SemanticAPI isn't able to, we should try that in LS side.

After using selecting this completion item, when user get the function Snippet suggested by us it is suggesting something this.
arr.'map(function (array:Type t) returns array:Type1 {
        return ;
    })

IMO if we improve this snippet it will be more useful to the user.
arr.'map(function (string  a) returns string {
        return a;
    })

WDYT @IMS94?

@LakshanWeerasinghe this is very useful. +1. Shall we create an issue for this and track that?

@LakshanWeerasinghe Awesome.. @dulajdilshan is there a way we can improve the array:Type val (parameter of the function parameter)? Because we know the type arr and we should replace arrray:Type with the member type of the array. It will be a good addition if we can do so.
If SemanticAPI isn't able to, we should try that in LS side.
@mohanvive WDYT?

It seems like, the type-param is not resolved correctly. Need to have a look in Semantic API level

Checked and applied a fix in the TypeParamResolver in the Semantic API.
The return type of the type ref is set with the bounded type. The function parameters needs to be checked and fixed in invokable type symbols.


Adding email by default to Cargo.toml can be a privacy issue

I just realized after somebody else told me, that my email was visible on the git repo. It was added automatically to Cargo.toml - It's an email I don't like to be public-facing. Not sure why putting the email on the file is necessary.

IIRC, we use the same email as configured in Git by default; presumably, all of your commits also have the same email? If not, the bug is probably there.

But I think I can hide the email from being public in Github?

I don't think that's true, as it's part of the hash, so you'd never be able to work with anyone at least. Just pulling a random commit, https://github.com/madprops/armtrak/commit/4c426293dd115f465c40a13f5de0b88c4b79ea4f.patch, lists madprops<EMAIL_ADDRESS>-- is that the email you're intending to keep hidden?


Adds ReAddPlatform option

Adds option to prevent cordova platform rm as prep stage to prevent engine settings overrides in config.xml.

Thanks for the PR @bayssmekanique ! <3
We'll review it and release a new version ASAP! :)

This does not resolve the issue the same way it does with the steps-cordova-archive as the Ionic CLI behavior does not pull in the engine attribute.
I am testing with Waracle's branch and having success, so that would be the recommended approach.


The type or namespace name 'Codice' could not be found

I have just freshly installed the plugin using the Git URL and Unity Package Manager and upon the project building I get the following:
Library\PackageCache\com.edgegap.unity-servers-plugin\Editor\EdgegapWindowV2.cs(11,7): error CS0246: The type or namespace name 'Codice' could not be found (are you missing a using directive or an assembly reference?)
Unity version: Unity 6 (6000.0.29f1)
EdgeGap plugin version: 3.0.7

resolved by #27


Added is_string: false to active_days_limit config entry

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
Fixing https://github.com/fastlane/fastlane/issues/10752
Description
Added is_string: false to active_days_limit config entry

I signed it!

I signed it!


Fix a minor typo in chapter 16

This is a fix for a small typo in chapter 16 notebook.

Good catch, thanks!


Allow running command containers as non-root user with EBS backed (and other) workspace volumes

When using a storage provisioner, such as aws-ebs-csi, the default permission mask for the volume mount is 755 and there's no way to change it.
That means when you specify a workspace from one of these provisioners you get a volume owned by root, which is not-writable by non-root users:
config.yaml snipped
config:
  agent-config:
    hooksVolume:
      name: buildkite-hooks
      configMap:
        defaultMode: 493
        name: buildkite-agent-hooks
  workspace-volume:
    ephemeral:
      volumeClaimTemplate:
        spec:
          accessModes: ["ReadWriteOnce"]
          resources:
            requests:
              storage: 1Gi
    name: workspace-volume

configMap pre-checkout hook:
#!/bin/sh

ls -l /
ls -l /workspace
ls -l /workspace/sockets || true

This means using a command container that has the USER set to something other than root isn't possible.
Firstly our agent can't start, because it needs access to write a job-api socket file. You get:
Error: Error setting up Job API: creating job API server: creating socket server: creating socket directory: mkdir /workspace/sockets: permission denied

This can be worked around by mounting an in-memory container to the /workspace/sockets directory with the following config snipped:
  pod-spec-patch:
    containers:
      - name: container-0
        volumeMounts:
          - name: socket-dir
            mountPath: /workspace/sockets
    volumes:
      - name: socket-dir
        emptyDir:
          medium: Memory

But the command container still has no ability to write to /workspace directory, which is a common use case.
We already handle this issue within the checkout container by ensuring all files are created as the same user as the SecurityContext provided https://github.com/buildkite/agent-stack-k8s/blob/main/internal/controller/scheduler/scheduler.go#L837-L838
But since the volume as mounted as 755, the checkout container has no permission to write to the directory.
I tried to patch this by telling the checkout container to change ownership of the directory to the relevant user before it changes users,
                checkoutContainer.Args = []string{fmt.Sprintf(`set -exufo pipefail
 addgroup -g %d buildkite-agent
 adduser -D -u %d -G buildkite-agent -h /workspace buildkite-agent
+chown -R %d:%d /workspace
 su buildkite-agent -c "%s && buildkite-agent-entrypoint bootstrap"`,
+                       podGroup,
+                       podUser,
                        podGroup,
                        podUser,
                        gitConfigCmd,

But it causes the agent to fail to start with:
2024-12-13 04:00:30 INFO   Build Path doesn't exist, creating it (/workspace/build)
fatal: failed to create builds path: mkdir /workspace/build: permission denied

So I landed on this solution, copying the existing implementation that checkout uses to ensure it runs as root then chown the directory in the init container.
Result:

@DrJosh9000 thanks, I've marked this as ready for review


feat(dashboards): add datasets field to DashboardInfo aspect

This PR adds an optional datasets field/relationship to the DashboardInfo aspect and a corresponding tab in the UI of the dashboard. To preseve the current behavior the tab with the consumed datasets is only shown if there are any datasets which are directly consumed by the dashboard (the charts tab is hidden if there are only datasets and no charts for the dashboard available). The tab with the consumed datasets shows only the datasets which are directly consumed by the dashboard, not the datasets which are consumed by a chart which is used in the dashboard (this is another reason why the tab with the datasets should not be shown if there are no datasets which are directly consumed by the dashboard).
Why do we need this extra field/relationship? In some dashboarding tools there is no dedicated object which could represent a chart or it is technically not possible (or way too complex in terms of effort) to extract such information from the source system (or manually maintain it). For instance in SAP Lumira or SAP Analytics Cloud there are no dedicated information about a chart available, only information about the data source (i.e. an SAP BW Query) or the model in SAP Analytics Cloud are available. Therefore for each dashboard one or many unnecessary "dummy" charts have to be created without any added value (and of course these dummy charts are visible in the UI which is not really nice when there are also dashboarding tools which are supporting the extraction of chart enities).
Please let me know if something is missing in the implementation as this is my first contribution which adds something to an (existing) aspect (and the UI). I have tried to understand and follow the implementation of the charts and some local testings are looking good, but who knows if I haven't forgotten something. 😁
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues (if applicable)
[x] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[x] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@Masterchen09 Looks like there's just one remaining conflict - otherwise LGTM. If we can fix that up we are good to go.

@jjoyce0510 I have rebased the branch and the remaining merge conflict in tableau_mces_golden.json should be solved. :-)


Feature/improve epg id matching

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@6538afa). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main       #31   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         3
  Lines           ?       164
  Branches        ?         0
========================================
  Hits            ?       164
  Misses          ?         0
  Partials        ?         0

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 6538afa...f6937a6. Read the comment docs.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@6538afa). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main       #31   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         3
  Lines           ?       164
  Branches        ?         0
========================================
  Hits            ?       164
  Misses          ?         0
  Partials        ?         0

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 6538afa...f6937a6. Read the comment docs.


Support fixed position for prototypes

I am...
| -------------------------------------------------------------------------------------------------

Requesting a new feature

Proposal/Feature-request:
Would be great to support some kind of version of position: fixed; to be used in Sketch prototypes. Fixed position translates nicely to Sketch's Fix position when scrolling. This would allow for having bottom navigation tab bars, etc in prototypes.
React Native doesn't support position: fixed; though, so if the same component/styling is used in a React Native app, it may break it. Some alternative ideas that should solve that:

Create a new react-sketchapp only styling prop: e.g. prototypePosition: 'fixed'
Use position: 'fixed', but document that this could be platform specific (`position: Platform.OS === 'sketch' ? 'fixed' : 'relative')
Implement a new ScrollView component, and have an Artboard prop that makes anything not inside this component fixed. Not sure how much value this would have though for code re-use between web and React Native though when components like FlatList are more likely to be used.

I think the easiest is to extend the flow prop to include fixOnScroll (or something similar). Would there be any downside? It's already Sketch specific

Hmm, that could work. flow requires targetId, target and animationType at the moment and will register a flow connection if it's truthy, so would need to make them optional and return only { isFixedToViewport } if target is missing.

Yeah. I like having all of them in a flow namespace so that the API surface doesn't expand too much. If Sketch decides to add more stuff related to prototyping later, we can stick it in there as well

Great, will open a PR then. Maybe worth creating a new docs page on prototyping too? I think it's an interesting use-case for React Sketch.app – creating Sketch Cloud web or Sketch Mirror prototypes for React Native codebases.

Sounds good. Your react-sketchapp-router could be a good addition to that page


[Bug]: Relica get's primary before being fully replicated

Is there an existing issue already for this bug?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[X] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[X] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
<EMAIL_ADDRESS>Version
1.23.2
What version of Kubernetes are you using?
1.28
What is your Kubernetes environment?
Other
How did you install the operator?
Helm
What happened?

Setup Cluster(2 node) without import section and this writes into a bucket
Realize import was missing and now bucket already includes
Create New Cluster(2 node) with import section and using the same bucket
Realize cluster doesn't writes into non empty
Update to max_connection and change the bucket name to an empty path
Replica get's killed and Primary starts writing into bucket
Replica is ready and Primary get's killed which takes some time
During this time data is upload from primary to the bucket and replica did start replicate from bucket
Primary is killed and Replica get's primary
Now i saw replica doesn't include all data
I killed the new Cluster started again.

Cluster resource
No response
Relevant log output
logs can be provided via email.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Re: item 1 - import is optional, the cluster is started and the archive is written. So up to item 4 it is a user problem, which is documented. You should simply erase the content in the bucket and restart the operation.
In my opinion we should not complicate the behaviour of the operator to improve this - which IMHO it is an initialization error which makes the cluster invalid and requires full rebuild.

I saw the cnpg.io/skipEmptyWalArchiveCheck annotation and wasn't sure if it would clear the wal archive. It might help to describe that you can clear wal if you see this problem.
see two solutions, don't mark the cluster ready for production workload until initialize is done with the managed services. Or add a line to the production guide what to check before letting production workload on the database.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1943 ms

Resolved: Bofrost.at performance has improved in 3648e23 after 14 minutes.


Allow non-members to view delve-dev's mailing list

Would it be feasible to relax the view permission on the delve-dev mailing list, so people aren't required to have a Google account just to view it?
eg this is what I get when trying to access the page:

I'm in favor.

Done, settings on mailing list have been updated.

Awesome, thanks @derekparker.  Now I can follow along with how things are going. :smile:


upgrade nPrint requirement v1.1.1 -> v1.1.3

I noticed that nPrint has put out a couple releases since this requirement was last set.
Good to pull in those improvements.

And, I'd mentioned that v1.1.1 was misreporting its own version. v1.1.3 appears to have corrected this.
Note, however, that I'm still seeing this message when I run nPrint:
error while trying to create ''

And so, for example with a directory, this is repeated across my terminal for every PCAP file that nprintML processes. (It's not great.) That said, there doesn't appear to be any profound harm to it.
(Happy to note this over in the nPrint repository, if that's helpful. Like I said, it's not the biggest deal, but I think worth bringing to your attention – and resolving, either here or there, sooner or later.)


[Bug] persist_docs not working for seeds

Is this a new bug in dbt-bigquery?

[X] I believe this is a new bug in dbt-bigquery
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
The descriptions for the seed and columns are not being persisted to BQ when using the appropriate config.
seeds:
  [<resource-path>](https://docs.getdbt.com/reference/resource-configs/resource-path):
    +persist_docs:
      relation: true
      columns: true

Expected Behavior
The descriptions are populated at the object and column level for the seed in my dbt project.
Steps To Reproduce

Use the yaml below to persist_docs for seeds

seeds:
  [<resource-path>](https://docs.getdbt.com/reference/resource-configs/resource-path):
    +persist_docs:
      relation: true
      columns: true

Run dbt seed
View descriptions in BQ for that seed

This may have something to do with the size of the seed though.  From @mikealfare "It might also have something to do with the fact that tables are sharded in BQ, and we only pull the column descriptions from the most recent shard (because they can change)."
Relevant log output
No response
Environment
- OS:
- Python:
- dbt-core:
- dbt-bigquery:

Additional Context
No response

It looks like we persist top-level descriptions for seeds, but not column-level descriptions:
https://github.com/dbt-labs/dbt-bigquery/blob/b7bb0bc0818644617b8c10eb0723560ce98147a5/dbt/include/bigquery/macros/materializations/seed.sql#L20-L23
I'm not sure why that is - this implementation goes way back:

https://github.com/dbt-labs/dbt-core/pull/2601

@jtcohen6 that's interesting, I was able to persist my column descriptions:

@jtcohen6 @amychen1776 My customer is asking if we're able to prioritize this at all?


[NEW ICONS]: Skeleton UI & Jetpack Compose

Add New Icon(s)
Icon Details

Icon ID
Icon

skeletonui-auto

skeletonui-dark

skeletonui-light

jetpackcompose-auto

jetpackcompose-dark

jetpackcompose-light

Notes

Skeleton UI is an UI toolkit for Svelte and Tailwind, that allows you to create adaptive and accessible interfaces for web apps of any shape or size.
Jetpack Compose is a modern toolkit for building native Android UI, designed to simplify and accelerate UI development on Android.

Closing
Jetpack Compose

Closes #91

Checklist

[x] Added icon(s) to the appropriate directory
[x] Updated documentation with the new icon(s)
[x] Verified the icon(s) display correctly
[x] If the icon has light and dark, verified the auto switch works correctly

1 commit behind, can you update you fork, then I will merge your PR.


Fix build

@tsloughter it looks like the build is broken after merging #94. Running make currently yields and doesn't run all the tasks:
cp -R /Users/jberg/code/open-telemetry/opentelemetry-configuration/validator/../schema /Users/jberg/code/open-telemetry/opentelemetry-configuration/validator/

Any idea what's up?

There's some other things failing as well:

https://github.com/open-telemetry/opentelemetry-configuration/actions/runs/10638140808/job/29493474553?pr=115
https://github.com/open-telemetry/opentelemetry-configuration/actions/runs/10638140806/job/29493474573?pr=115

Why didn't this cause the PR checks to fail?

Why didn't this cause the PR checks to fail?

The build never calls make by itself - it always calls some more specific task.


[FEATURE REQUEST] Spectator-Like Underground Rendering During Noclip

I am not experienced enough to know if this is possible, however if you noclip into the ground and try to view underground voids / structures, things unload in a way that that simply doesn't happen when you are in spectator mode.
I feel it would be a lot smoother and more comparable to the concept of "spectator mode but creative" if you can actually see underground in the same manner!

P.S. I really love this mod, you have done wonders and everything about it is very clean indeed. The button effects are just amazing lol.

P.S. I really love this mod, you have done wonders and everything about it is very clean indeed. The button effects are just amazing lol.

I've noticed this but assumed it was something to do with Sodium. Will look into this more closely.

I've noticed this but assumed it was something to do with Sodium. Will look into this more closely.

Fix finally released with v1.2.3 after hitting various bumps and being pulled away for various things today.

Fix finally released with v1.2.3 after hitting various bumps and being pulled away for various things today.


fix bug

here can lead to memory leaks

Thanks for the report.  I think that we in fact need to round up instead of using <=.  I applied a patch that does that, crediting this pull request:


Task/minimize config buildpaths

Moves the buildPaths config into implicit as part of the bootstrap.js
While I was in there, I also added a quick mkdir:init before analyze, as currently if you run analyze without having built the site it chokes on the lack of build/reports.

I've updated the test/test_assets/Gruntconfig.json to strip out the buildPaths, as I'd thought we were still using the example/Gruntconfig.json for that.
For testing, how about we take a less e2e approach by loading a tailored Gruntconfig.json and verifying the config values we end up with after bootstrap?


2-d kernel generation

We need to be able to generate a 2-d grid of regular samples of the convolution functions.
The 2-d convolution function is typically separable, i.e. func2d(x,y) = func1d(x)*func1d(y)
We should be able to generate kernels at differing sub-pixel offsets, and with optional oversampling.
See also: Python reference implementation, unit tests.

Implemented, see https://github.com/SKA-ScienceDataProcessor/FastImaging/blob/8654dc34393fe29f94bffd002da0cad9d4e6fafa/src/libstp/gridder/gridder.h
However, I'm pretty sure oversampling doesn't work; this line doesn't make sense:
https://github.com/SKA-ScienceDataProcessor/FastImaging/blob/8654dc34393fe29f94bffd002da0cad9d4e6fafa/src/libstp/gridder/gridder.h#L126