Embedding API V3 applyFilterAsync throws service registry error

Hi I'm using Embedding API V3 latest with Connected Apps to host embeds from Tableau Server on a Angular SPA. Whenever I try to call applyFilterAsync a strange internal-error: Service not registered: filter-service is thrown and filters do not get applied.

If I have the exact same setup but host a public Superstore example dashboard. No error is thrown.

Looking into the source code, I think the issue lies within how API Service Registry is set up during initialization. In screenshot 1, the global __tableauApiServiceRegistry object contains 2 ServiceRegistryImpl objects where the first one only includes notification-service and the second one contains filter-service. applyFilterAsync first checks if filter-service is registered in the service registry and hence throws an error
In screenshot 2, however, __tableauApiServiceRegistry contains exactly 1 ServiceRegistryImpl object and it has filter-service in it. Therefore it has no problem finding it and applying filters.
If in my case if I manually reassign the 1st index ServiceRegistryImpl to overwrite the 0th index one, no error is thrown and the filter works. But I feel like I shouldn't have to mess with the inner workings of the library and suspect it's either a bug or something about my Tableau Server configuration/Connected Apps setup that caused initialization to not happen properly. Can you provide some support/insights here? Thanks

Hello, is there any support on this? We worked with the Tableau Support team on this but it's beyond their scope

Hi @shengc5 , thank you for raising this issue. Could you please provide some more details that will help us repro this issue consistently:

The version of the tableau server you are running.
A complete code snippet that shows the sequence of steps that lead to this error. I see that there are some snippets in the screenshot above, but complete snippet will help us get a complete picture.

Hello, our enterprise instance is on Tableau Server Version: 2022.1.9 (20221.22.1108.1355) 64-bit Windows and the client library is pointing to tableau.embedding.3.latest.js (is there a way to find our the specific minor version number by inspecting the file itself?)
There isn't much logic else other than the API call to get the Connected Apps jwt token. Rest of the code snippet should be almost identical to Tableau tutorials on how to apply interactive filters.
Ps: the dashboards I'm having issues with contain highly confidential data so I had to redact the server name/workbook URL. Let me know if there is a private, secure way to show debugging info directly with the team. Thanks

Hi @shengc5, I was unable to repro this on the tableau server version mentioned above. Could you join our dataDev slack channel (https://tabsoft.co/JoinTableauDev). We get gather some more repro steps there.

@shengc5, You could also share the code and clear out the src url as well as the Connected app secrets if that makes it easier.

Can you add my email<EMAIL_ADDRESS>to the channel? Unable to join it.
Also with regards to code, everything was there in the screenshot; one  component and 4 lines of code taken from the official docs with minor modifications

Hey @shengc5 , looks like you are part of the channel now and have started similar thread there as well.

Hey @shengc5 , looks like you are part of the channel now and have started similar thread there as well. Some thoughts:

Could you share your current network trace. Might be useful to see if there is some timing issue.
Could you confirm that you are making your calls inside the firstInteractive event. Not sure if that will fix your issue but it is worth trying that out if you haven't already.

Closing due to age and reproducibility.


add failed tests file support

Changes proposed in this PR

add support for writing out failed test names to a file

Why are we making these changes?
can use to mitigate flaky integration tests. allows re-running only the failed tests

Will merge when checks are green

@dposada green now


Implement User Apps changes for CreateCommand

I'm not too sure on the naming of the set / add methods

The set_ methods should have the prefix removed, to follow CreateMessage::embed and it's footsteps.


[flutter_plugin_tools] Migrate 'test' to new base command

Migrates test to the new package looping base command.
Refactors the bulk of the logic to helpers for easier understanding of the flow.
Part of flutter/flutter#83413
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Note that unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[x] All existing and new tests are passing.

This is probably the simplest command we have, and it hadn't been migrated, so that works out well as an intro to these refactors :) I think the only context you'll need here is to look at https://github.com/flutter/plugins/blob/master/script/tool/lib/src/common/package_looping_command.dart
Note that this is divided into two commits: the first is just a simple local refactor to pull the bulk of the logic into helpers and do some minor cleanup on them (e.g., using if in lists instead of the older method of conditional add calls in more places). The second is the migration itself, and should be very simple to follow given the first commit (I originally did them the other way, but the diffs weren't very good due to the whitespace changes + cleanup).


python311Packages.pyrisco: 0.5.7 -> 0.5.8

Diff: https://github.com/OnFreund/pyrisco/compare/v0.5.7...v0.5.8
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 257595 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.risco
python310Packages.pyrisco
python310Packages.pyrisco.dist
python311Packages.pyrisco
python311Packages.pyrisco.dist


Fix support for aliased time.Time types

Fixes detection of aliased time.Type types
Allows to validate fields with type:
type CustomTime time.Time

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.

@go-playground/validator-maintainers

Coverage decreased (-0.03%) to 75.102% when pulling f3fa470b434fa3f115ac244db1a51de3259975e0 on lafriks-fork:fix/time_convertable into 88976f39f600bb3979de1ae5efdfd9cff2cf10f1 on go-playground:master.


Immediate input prompt for chained tasks

Is it possible to run a task and enter its input before its dependency task has run and finished. Example tasks.json is below but my problem is that vscode waits for Stop containers task to finish before prompting for container-name. My motivation here is to not wait for containers to stop to enter desired container name.
After searching,I couldn't find a way to do it but it would be nice to have.
{
	"version": "2.0.0",
	"tasks": [
		{
			"group": "test",
			"type": "shell",
			"label": "Run Container",
			"command": "docker-compose  -f 'docker-compose.yaml' up -d --build ${input:container-name}",
			"dependsOn": ["Stop containers"]
		},
		{
			"group": "test",
			"type": "shell",
			"label": "Stop containers",
			"command": "docker-compose  -f 'docker-compose.yaml' down"
		}
	],
	"inputs": [
		{
			"id": "container-name",
			"description": "Container Name:",
			"default": "app",
			"type": "promptString",
		}
	]
}

Found out that requiring that input in the Stop containers task achieves this. It doesn't prompt recurrently.
{
	"group": "test",
	"type": "shell",
	"label": "Stop containers",
	"command": "echo ${input:container-name}; docker-compose  -f 'docker-compose.yaml' down"
}

Or basically adding two commands in the Run Containers command value.


ICC warnings about uninitialized variables

Original issue: https://charm.cs.illinois.edu/redmine/issues/359

Intel's compiler makes the following series of complaints when I use it to build charm:
AdaptiveLB.C(108): warning #592: variable "lb_type" is used before its value is set
    CkPrintf("AdaptiveLB> Previous LB %d\n", lb_type);
                                             ^

AdaptiveLB.C(119): warning #592: variable "comm_refine_ratio" is used before its value is set
      } else if (comm_refine_ratio <= 1.01) {
                 ^

AdaptiveLB.C(123): warning #592: variable "comm_ratio" is used before its value is set
      } else if (comm_ratio <= 1.01) {
                 ^

AdaptiveLB.C(138): warning #592: variable "refine_max_avg_ratio" is used before its value is set
      } else if (refine_max_avg_ratio <= 1.01) {
                 ^

AdaptiveLB.C(142): warning #592: variable "greedy_max_avg_ratio" is used before its value is set
      } else if (greedy_max_avg_ratio <= 1.01) {
                 ^

Original date: 2013-12-11 19:17:45

Ping. Could you please clean this up, so that we avoid the possibility of erratic behavior under icc?

Original date: 2013-12-13 18:46:27

Thanks!


chore: log to a blob that can be downloaded

[!NOTE]
Not be merged until web3inbox core released as latest, not canary.

Description

Log to an array
Allow the array to be downloaded as blob (file)
Add UI button to download it
Inject method to download it into window (just in case the UI is unresponsive or something)

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

This is awesome!!
Left some requests, also:

Does the SDK support dumping logs from third-party apps or does it require this harness here? Goal would be to be able to dump logs from third-party apps using the SDK w/o them needing to implement stuff.

Next we should pull this SDK version into GM dApp and just have it work. And a similar approach for Web3Modal/sign client/etc.

Since the log dump may be truncated, should we prefix the log dump with some important "global" info such as client ID, token, any other state information?

Are all the log entries prefixed with a timestamp?

The SDK allows them to pass a custom logger. The reason I did not include this in the docs is depending on their environment this might not work. Eg, RN vs Browser environments or if for any reason the SDK was used on node.
Added
Added

Closing in favor of solution in JS core.


A much practical example showing how let bootstrap.native works with npm, browserify, babelify.

var bsn = require("bootstrap.native");
var browser = require("mock-browser");
global.window = browser.createWindow();
global.document = browser.createDocument();

// Now it's safe to use bootstrap.native and expecting the properties to be the actual component classes.
var Button = bsn.Button(); // Create the button class and return it.

var $btn = document.createElement("button");
var myButton = new Button(... $btn and options ...); // Create a button and do a test.

Hi,
Right now I'm working on the Webinterface of a device. Because I've gone a long way with browserify, npm and babelify only (without Bootstrap or JQuery). And need the rocking feature that bootstrap.native delivered. After about 3 hours brain burning, I even can not add a dummy button from it. The code above is part of the howto. It just not helpful enough for me.
Is there someone would like to give me a more practical example?

I believe @RyanZim has an idea about that, I'm not with this stuff anyways ;)

Yeah, docs need updated. Will do a PR.
Try this:
// Load bootstrap.native
var bsn = require("bootstrap.native");
// This will get the data- attributes working

// If you need custom code:
var myButton = new bsn.Button(document.getElementById('button')); // etc.

You probably won't need custom code unless you're dynamically adding elements to the DOM.

Thanks @RyanZim, a life saver ;)

Super Cool!, Thanks @RyanZim !
I write acutally modules in Javascript. And call them when I need them. All coponents are defined in javascript like:
let btn = document.creatElement("button");
btn.innerHTML = "Hey thednp";
mainDom.appendChild(btn);

So when I do the trick like you said: I can't just appenChild() the from new bsn.Button(btn) wrapped myButton anymore. Chrome told me:
Uncaught TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.
It's pretty interesting! Because of the state-of-the-art javascript stuffs, I just get less interest in web developing... : (

OK, if you're creating elements, you'll want to do something like:
let btn = document.creatElement("button");
btn.innerHTML = "Hey thednp";
btn.id = "myBtn";
mainDom.appendChild(btn);
var myButton = new bsn.Button(document.getElementById("myBtn"));

That should work.
I'm not sure if new bsn.Button(btn) would work before calling appendChild(); try this and see if it works:
let btn = document.creatElement("button");
btn.innerHTML = "Hey thednp";
btn.id = "myBtn";
var myButton = new bsn.Button(btn);
mainDom.appendChild(btn);

If both methods work, the second one is preferable.

Hi @RyanZim @thednp ,
you are awesome! Since the project I'm working on have to run with hardwares that only available in my working places. I will tell you the result morning...
Thanks again for the support! Hopefully I can use bootstrap.native in it.

@Gfast2 we're glad we could help

	let bsn = require('bootstrap.native');

	let button = document.createElement('button');
	button.id = 'btnTest';
	button.className = 'btn btn-default';
	button.innerHTML = 'Hello Bootstrap.Native';

	rows[10].appendChild(button);
	containerDom.appendChild(rows[10]);
	dom.appendChild(containerDom);

	// Create a button:
	var btn = new bsn.Button( /*document.getElementById("btnTest")*/button );
	btn.className = 'btn btn-danger';

	/*
	<button type="button" id="myButton" data-toggle="button" data-loading-text="Loading..." class="btn btn-primary" autocomplete="off">
  		Loading state
	</button>
	*/

After about 20 minute exploration. I figure out, I have to append the elements on the site first, then I am permitted to wrap it into new bsn.Button(). By the way I've to define some css class for this button before, If not chrome will give me other Errors, too.
After the initialization, I've tried to change the class of the bootstrap.native button. But without success.
I'm thinking about trying other frameworks, but I need bootstrap stuff a lot. So I just can't actually write them all...
So thank you again. I'll keep on tuning.

@Gfast2 you actually have access to the button, but your lines should look like this:
    // Create a button:
    var btn = new bsn.Button( /*document.getElementById("btnTest")*/button );
   btn..btn.className = 'btn btn-danger'; // notice the additional btn

The this of your invocation holds track the element in this.btn, I think you can investigate the code and learn more what you can actually do.

@thednp thanks again! It WORKS beautifully!!!
Now I'm start to trying arguments to the button, to let it do the trick like in the example...
<button type="button" id="myButton" data-toggle="button" data-loading-text="Loading..." class="btn btn-primary" autocomplete="off">
        Loading state
</button>

If you have time, you can write it here. If not, I'd try to figure it out myself.

Can you clarify your question, I cannot figure out what you're after.

Yes. My question is:
if you define a button within the <> fashion. The parameter like data-toggle="button" or data-loading-text="Loading..." will have no problem what so ever. But if you do it in other way like we said:
btn.btn.className = 'btn btn-default';
You don't have the chance to define the others. For instance:
btn.btn.data-toggle = "button"; will be not comipled.
So I'm still tunning around...

The Button script has 2 features:

set button state
toggle radios and checkboxes

It doesn't have, also the original script to my knowledge, a way to toggle classes.

@thednp Thanks. I'm still fighting with it.If I get the answer eventually. I'd write here.

After such a long time. I decided to not use this framework.
I even try to inject a button into a td of the table. It still not works at all. Pretty frustrated.
let bsn = require('bootstrap.native');
let newLine = createTD();
newLine.innerHTML = "<button type='button' id='myButton' data-toggle='button' data-loading-text='Loading...' class='btn btn-success' autocomplete='off'>Loading state</button>";
rows[10].appendChild(newLine);

dom.appendChild(containerDom);

It's not most fascinating thing in the world, it's an open source project. If you can find a way to make it work share it with us, because there's nothing else like it.


change(tests): Obtain lightwalletd tip from logs instead of grpc

Motivation
Close https://github.com/ZcashFoundation/zebra/pull/7335
Solution
Get the tip from the lightwalletd logs. Currently a draft to see if the CI passes.
Review
I guess how we get the block can be improved, it is a bit fragile but i think whatever improve will not remove the fact that we are relying on a specific well formed log line from lightwalletd.
Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?

[ ] Does it change concurrent code, unsafe code, or consensus rules?

[ ] How do you know it works? Does it have tests?

Follow Up Work

So I'm going to approve this PR now, and hope it passes and merges.

The update sync passed CI and saved a cached state:
https://console.cloud.google.com/compute/imagesDetail/projects/zfnd-dev-zebra/global/images/lwd-cache-7507-merge-3df0524-v25-mainnet-tip-u-000145?hl=en&project=zfnd-dev-zebra
The heights were updated and recorded in the labels correctly:

So this PR should merge once the other tests pass.


Stuck on booting pongos TVos 16.6

Device
Apple TV A1625
Version
tvOS 16.6
Passcode?

[ ] Passcode is enabled.

Start going into detail..
Jailbreak process start but stuck on booting pongos
Familiarity with palera1n

[X] I am familiar with palera1n and how to use it!

Familiarity with CLI

[X] I am familiar with the command-line!

Solution found and working : in terminal type control x, then enter, then type exit, then enter
And repeat the process at the beginning

Glad you were able to figure out your issue!


openfst: 1.6.7 -> 1.6.8

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/openfst/versions.
These checks were done:

built on NixOS
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstarcsort had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstclosure had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstcompile had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstcompose had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstconcat had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstconnect had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstconvert had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstdeterminize had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstdifference had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstdisambiguate had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstdraw had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstencode had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstepsnormalize had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstequal had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstequivalent had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstinfo had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstintersect had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstinvert had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstisomorphic had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstmap had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstminimize had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstprint had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstproject had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstprune had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstpush had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstrandgen had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstrelabel had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstreplace had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstreverse had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstreweight had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstrmepsilon had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstshortestdistance had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstshortestpath had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstsymbols had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstsynchronize had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fsttopsort had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstunion had a zero exit code or showed the expected version
0 of 37 passed binary check by having a zero exit code.
0 of 37 passed binary check by having the new version present in output.
found 1.6.8 with grep in /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8
directory tree listing: https://gist.github.com/12e73cab8efbc1c63a2ba5e087454914
du listing: https://gist.github.com/0fad2edab1e90571b66bb61e3fe3b01e

meta.description for openfst is: '"Library for working with finite-state transducers"'.
cc @dfordivam for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout acaf1c8416db20fa745b885b421ce2789a4ce35b && nix-shell --pure -I nixpkgs=. -p openfst

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: openfst
Partial log (click to expand)

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

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

Success on x86_64-linux (full log)
Attempted: openfst
Partial log (click to expand)
shrinking /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstcompose
shrinking /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstdifference
shrinking /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin/fstrelabel
shrinking /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/lib/libfst.so.11.0.0
shrinking /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/lib/libfstscript.so.10.0.0
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/lib  /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8/bin
patching script interpreter paths in /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8
checking for references to /build in /nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8...
/nix/store/wsx1ziwkccvj1mk0b647cc0syfkzpinf-openfst-1.6.8

Success on aarch64-linux (full log)
Attempted: openfst
Partial log (click to expand)
shrinking /nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8/bin/fstcompile
shrinking /nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8/bin/fstclosure
shrinking /nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8/bin/fstarcsort
shrinking /nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8/lib/libfstscript.so.10.0.0
shrinking /nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8/lib/libfst.so.11.0.0
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8/lib  /nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8/bin
patching script interpreter paths in /nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8
checking for references to /build in /nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8...
/nix/store/3n4xifwzkca91hv9b2r873awq9r8wqg2-openfst-1.6.8


Convert files legend into an info box

This is a currently just a proposal. It's not ready for implementation until we remove the Question label. I'd like at least @corylown and @JohnMarkOckerbloom to weigh in on whether this seems useful, though feedback from anyone is welcome.
Problem
We currently show a legend that is intended to help the user understand what the icons we use for file status mean. We display this legend immediately before the table of files on the Upload files page for a stream, and the table of files on the Activity page:

Because some of the status explanations are sort of long, it's not a very attractive legend, it wraps at viewports smaller than XL, and the longer entries make quickly scanning the list a bit harder. I'm also wondering, since we recently added some wording to a couple of the entries to be more clear, if we might want to be even more clear about the details of some of the possible file statuses.
At the same time, I suspect that any user of the POD UI who looks at the files table on a regular basis internalizes the icon meanings after a while, and then for that user the unattractive legend is just a distraction.
Proposed solution
We might be able to do the following by converting the legend into an info box (Bootstrap card):

Provide more space for longer explanations, in case we think it would be useful to be more descriptive for any status
Hide the legend from the knowledgeable user (I suggest the box is expandable/collapsible, and collapsed by default), reducing the visual distraction

Example of default collapsed state
I think we'd want to display the box collapsed by default, since it seems reasonable to expect that a returning user might not need to see the legend very often. If they do it's just one click to expand.
I'd also suggest we make the whole card header the trigger for the expand/collapse action, since the icon can be pretty distant from the card heading text on wider viewports and thus less noticeable. (I don't love About file status as the heading text but we can work on that.)

Example of open state
Because the user is intentionally expanding the box, I worry less about the vertical space it takes. So I've used a new line for each file status. In my mockup this arrangement results in a lot of wasted horizontal space but I think we can consider writing expanded explanations for any status that might need it, which would use more of that horizontal space. Or, if we don't have useful expanded explanations, we could try to use a two-column layout within the box.

@ggeisler I like this proposal to move the status icon details into a collapsed but expandable info box.

Does the collapsed info box take up substantially more vertical space than the existing horizontal-row legend, though?  (As Gary points out, it does when the window's narrow enough and the line wraps, but even on my 13" laptop that doesn't happen until I make my browser window smaller than usual; and I suspect that most people using this interface would be using a laptop or monitor-equipped computer rather than a mobile device or something else with a small browser window.)
Because this is most likely to be needed by new users, who also might not notice things they have to make extra clicks to see, I do have a slight preference for showing brief labels by default on one line if it fits.  (I've seen some interfaces that will have an element fully displayed at wide widths and then auto-collapse it into an expandable element at narrow widths, but I don't know how easy that would be to do cleanly here.) But it's not an especially strong preference, so I'm willing to yield to UX expertise judging otherwise.  Note that we can also potentially include a link to more detailed explanations in the documentation wiki if that seems appropriate.

The collapsed info box would require about the same vertical space as the current legend. The advantages of it over the legend in that regard are 1) it wouldn't wrap on narrower viewports, and 2) it would be less visually distracting for the user who already understands the file status info.
However, I do think @JohnMarkOckerbloom has a good point about most users of POD likely to be using a wide-enough viewport to not see the current legend wrapping. With the ubiquity of mobile devices today, it's generally good practice to not assume users won't be using a mobile device, but the user base of POD is somewhat unique and I agree we can be pretty confident most of the time they won't have a narrow viewport.
I think the deciding factor on which way to go might be: given the extra space the info box approach offers, would you take advantage of this by providing more detailed text for one or more status states? If you can't think of additional text about file statuses you think would be helpful for the user in the info box, it probably isn't worth the effort to implement the box. I might just remove the bolding from the legend text to reduce its visual impact a bit. It'll still be kind of ugly, but maybe that would be sufficient (again, though, that is assuming there is no additional text we could add to help the user better understand the different possible file statuses).

I think it's possible we would want to provide more detailed explanations for each status if we had the space in an info box to do so. That would likely be based on further feedback from POD users. One approach would be to for now remove the bolding from the legend to reduce its visual impact and if we find that more detailed information is needed we move to the info box approach.

Sure, that sounds fine to me. I'll take care of the bolding issue when I make another pass at some visual design tweaks.


Initial rerender

Based on: https://github.com/conda-forge/conda-smithy-feedstock

All checks passed, looks good. Merging.

Thanks Tom. I think we'll need to build a few more dependencies (whatever are listed in the https://dev.azure.com/nsls2forge/nsls2forge/_build/results?buildId=3261&view=logs&j=1bf226d3-0e2f-52d8-fa93-7d9e633347b3&t=ec8d466d-e3b4-5115-4f06-222398f91e6c&l=740 building log). There are quite a few coming from conda-forge. This can be rerendered with the update from https://github.com/nsls-ii-forge/event-model-feedstock/pull/24 (I can do it now).


Supports the InternVL multimodal large model

Can it support the InternVL multimodal large model, which currently ranks first in the MMMU open source ranking.
https://github.com/OpenGVLab/InternVL/

MMMU

Up

+1

+1

Based on the internal information I have, new version releases will continue in the second half of the year, so we also expect to directly support the new ones. Of course, if you are interested in submitting PRs to support existing versions, contributions are welcome.

duplicate https://github.com/sgl-project/sglang/issues/1042 Close this for now. Thanks!


Use a fork of SwiftyUserDefaults adapted to ScreenSaverDefaults

SwiftyUserDefaults is a much more pleasant way of dealing with user defaults than what's in our code right now. But it would have to be adapted for use with ScreenSaverDefaults.

This is probably not worth the effort of forking for this purpose.


OCPBUGS-13776: Remove lingering DPU_IP references

/jira refresh

Sorry my grep didn't catch this. Thanks! /lgtm

@wizhaoredhat can you give another lgtm? bot didn't catch your previous attempt.

/lgtm


"top 5 channels" figures from gridsearch are sometimes empty

Good:

Bad:

I believe the blank version is caused by this error in the .trace.txt
kymata-core/kymata/math/vector.py:10: RuntimeWarning: divide by zero encountered in divide
  x /= np.sqrt(np.sum(x**2, axis=-1, keepdims=True))
kymata-core/kymata/math/vector.py:10: RuntimeWarning: invalid value encountered in divide
  x /= np.sqrt(np.sum(x**2, axis=-1, keepdims=True))
~/.cache/pypoetry/virtualenvs/kymata-core-9z-PYDBX-py3.11/lib/python3.11/site-packages/numpy/core/_methods.py:118: RuntimeWarning: invalid value encountered in reduce
  ret = umr_sum(arr, axis, dtype, out, keepdims, where=where)
kymata-core/kymata/entities/sparse_data.py:37: RuntimeWarning: All-NaN slice encountered
  channel_min = nanmin(log_pmatrix, axis=1)
kymata-core/kymata/entities/expression.py:127: UserWarning: Supplied data contained nans. These will be replaced by p = 1 values.
  warn("Supplied data contained nans. These will be replaced by p = 1 values.")
kymata-core/kymata/entities/sparse_data.py:37: RuntimeWarning: All-NaN slice encountered
  channel_min = nanmin(log_pmatrix, axis=1)

I'm not exactly sure which cause the issue.


[AAP-9301] Added msg/var support in debug action

https://issues.redhat.com/browse/AAP-9301
The debug action supports msg and var attributes to display single/multiple messages or variables akin to ansible debug builtin. The msg supports an array of messages.
This removes the need for a separate echo command. The echo is equivalent to
action:
   debug:
     msg: .....

@Alex-Izquierdo Changeling updated

@Alex-Izquierdo @ttuffin Please review I had to rebase to align changes in CHANGELOG.md


Update search examples for Purview Catalog

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run

Hi @ruowan @raych1, I want to update some examples for Purview Catalog. Could you please help me review this PR? I have no clues why the model validation and breaking change validation fail. Thanks.

/azp run

@jianyexi , can you have a look at breaking change and lintDiff exceptions?

@jianyexi Jianye Xi FTE , can you have a look at breaking change and lintDiff exceptions?

Seems schema validator will check the "location" in the example should match  "^(http|https)://.*", just fix the example I commented can resolve the exception

@jhendrixMSFT , I just realized this PR is data plane PR and I was assigned incorrectly.  Can you please review this PR and follow up on it?


Schedule Time Block for Event Screen - View Availability

package.json

Pinned Prettier to version 3.1.1 due to CI issues with version 3.3.3

pnpm-lock.yaml

update lockfile to match package.json

timeUtils.ts

Created a separate utility file to handle time arrays used in earliestTime and latestTime dropdowns and the range of times to populate availability grid rows
rearranged order in days array to [Sun,Mon,Tue,Wed,Thu,Fri,Sat] in dateUtils.ts

EventForm.tsx

Removed "Create Event" button and replaced it with "Add Availability" button
Removed handleSubmit prop
Refactored and utilized timeUtils.ts for handling time arrays in earliestTime and latestTime dropdowns

AvailabilityGrid.tsx

Added availability grid with cell selection/deselection and drag selection/deselection functionality
Added days of the week columns and time row headers to the grid that grow/shrink based on selection
Added “Create Event” and “Cancel” placeholder buttons for availability

Responses.tsx

Added a responses section that updates when the user signs in and adds their time slot availability

page.tsx

Added sign-in modal where the user provides their name
Added handleResponse function to save the list of responders
Fixed overall UI issues

Create Event - User fills out Event form inputs

Create Event - User clicks "Add Availabilty" button and pop up modal asks for user sign in

Create Event - User adds their availability in the grid and clicks "Create Event" button to save

Create Event - Event is successfully created and Responses section updates

Prettier fail :(


Tableau doesn't recognize the data source type "Clickhouse_ODBC"

Hi Folks,
I used the latest version of the "clickhouse-odbc" driver from the link: https://github.com/ClickHouse/clickhouse-odbc/releases. I also used the connector "clickhouse-tableau-connector-odbc" as per the instruction listed out here: https://github.com/Altinity/clickhouse-tableau-connector-odbc. After doing this, I can able to access and visualize clickhouse data using Tableau Desktop.

Problem:
When I try to publish to Tableau Server, I got the following error:

Could you please advice me what the issue is and what I can try to resolve this issue?
Thanks,
Fasil

@Fasilbeyene
I think that this problem is not related to odbc driver and should be posted in this repo
https://github.com/Altinity/clickhouse-tableau-connector-odbc
Most likely its because both ClickHouse ODBC driver and connector should be installed on Tableau Server.

@Fasilbeyene
I think that this problem is not related to odbc driver and should be posted in this repo
https://github.com/Altinity/clickhouse-tableau-connector-odbc
Most likely its because both ClickHouse ODBC driver and connector should be installed on Tableau Server.

Both (driver and connector are installed in Tableau server (Linux), as explained in the link you provided.

anyone know what is the solution for this

what Tableau server do you use?
did you use latest connector version from
https://github.com/Altinity/clickhouse-tableau-connector-odbc/releases
what do you see in Tableau server log?

what Tableau server do you use?
did you use latest connector version from
https://github.com/Altinity/clickhouse-tableau-connector-odbc/releases
what do you see in Tableau server log?

Thanks! Dima! Just to clarify , we need to have the ODBC driver for clickhouse
https://github.com/ClickHouse/clickhouse-odbc/releases
AND
we need to have the connector installed in the proper directory (windows vs. linux)
https://github.com/Altinity/clickhouse-tableau-connector-odbc/releases
Restart Tableau server.
No need to specify ip,port,username, password, etc.
Thanks!
JC


Mr  Ally

Am a slim person, and am working with many peoples in different places, I had the tangible focus to be come a successful in features ,so am also a man of my mind. Big projects was on my neck and a lot of ideas of different businesses too,but I founded my self at zero level,am looking for ways out from this situations........Am in needs of your full support help me out of this.

با سلام و خسته نباشید  ما به زبان انگلیسی وارد نیستیم اشتباه میکنیم لطفا فارسی به زبانها اضافه کنید

به زبان فارسی اضافه کنید


Open in Editor bombs in Ubuntu 20.04

The default Emacs invocation, "::<column", is incorrect.  I added
"alt-editor.args": "+{line}:{column} {filename}"

to my ~/.config/Code/User/settings.json.  But, it still bombs:
Can't open the file /home/jsung/.config/Code/User/settings.json:11:38: Error: Command failed: emacs +11:38 /home/jsung/.config/Code/User/settings.json Backtrace: emacs[0x5194a2] emacs[0x4febb1] emacs[0x517874] emacs[0x517aad] emacs[0x517b2d] /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7f2293aab3c0] /lib/x86_64-linux-gnu/libc.so.6(+0x18e7b8)[0x7f22939047b8] /usr/lib/x86_64-linux-gnu/libpng16.so.16(+0x1d79d)[0x7f229657c79d] /usr/lib/x86_64-linux-gnu/libpng16.so.16(+0xd538)[0x7f229656c538] /usr/lib/x86_64-linux-gnu/libpng16.so.16(+0xd9d8)[0x7f229656c9d8] /usr/lib/x86_64-linux-gnu/libpng16.so.16(+0xdcbb)[0x7f229656ccbb] /usr/lib/x86_64-linux-gnu/libpng16.so.16(png_process_data+0x3b)[0x7f229656ceab] /snap/code/71/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so(+0x2cd9)[0x7f228cee9cd9] /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0(+0x10281)[0x7f2295900281] /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0(gdk_pixbuf_loader_close+0x175)[0x7f2295900b15] /...
The Emacs X window does pop up, but then it closes immediately, and I get the "Can't open the file" notification.
If I copy and paste the command onto a command line, it works just fine.
I see the "docs: describe emacsclient config" pull request.  It works if I have an Emacs session I "M-x server-start" already, but it doesn't work, for me at least, if I didn't.
This is on Ubuntu 20.04.


Update reingestion workflows to load and report data

Fixes

Fixes #615 by @stacimc
Description

This PR:

refactors the regular provider workflow factories slightly to make it possible to separate out the ingestion steps (pulling & loading data) from the reporting step (notify slack)
updates the reingestion_workflow dag factory to include the loading steps, and to report a single slack notification with summed data at the end
temporarily updates the schedule interval for reingestion workflows from @daily to @weekly, so that we can get a sense of how long they take when we roll them out and adjust more easily. I expect we may need to tweak the configurations.

A reingestion workflow will look like this:

Don't panic 😄 To make it easier to see what's going on, I've altered the workflow configuration for Wikimedia here to generate a smaller number of reingestion days. You can see that each node in the graph represents an ingestion workflow for a particular day in the past. The suffix for the taskgroup is the day_shift (so ingest_data_day_shift_32 is ingesting data for 32 days in the past).

Here's how I altered the configuration to get that graph:
ProviderReingestionWorkflow(
        dag_id="wikimedia_reingestion_workflow",
        ...
        daily_list_length=2, # Only generate 2 ingestion days with a day_shift 1x
        one_month_list_length=2 # Only generate 2 ingestion days with a day_shift 30x
)

The daily_list_length, weekly_list_length and so on tell the DAG factory how many taskgroups to generate at each level. So if you have daily_list_length = 3, taksgroups for the day_shifts 1, 2, and 3 will be generated at that level. If you have weekly_list_length=3, you'll generate 3 new taskgroups for day_shifts counting by 7, starting at the last day_shift in the previous level (3) -- so 10, 17, 24.
Between each level is a 'gather' task which acts as a gate. All the ingestion tasks in partition 0 must complete before gather_partition_0 can run; only then are partition 1 ingestion tasks processed. There is one partition for each of the day shift multipliers (ie partition 0 is today, partition 1 is daily shifts (if any are configured), then weekly shifts and so on).
When all of the tasks are completed, a single report_load_completion reports a summary of the sum of all the pull_data durations, as well as the sum of all the record_counts (total number upserted, total duplicates, etc).
REVIEW GUIDE
This is a big PR, but many of the changes are refactoring of types or the addition of tests/docstrings. I am happy to find a way to split this if necessary for review, though. Here's my review guide by file:

DAGs.md: auto-generated docs for the reingestion workflows
common/loader/reporting.py: updates to the reporting tool to aggregate data for multiple ingestion tasks
common/loader/storage/* and provider_data_ingester.py: all changes to these files are done to append the ingestion date as a suffix to the tsv filenames for dated DAGs. This is necessary because reingestion tasks can run concurrently, so we can get collisions on tsv filenames when just using the execution date.
provider_dag_factory.py: the bulk of the work. This refactors the existing factories to split out ingestion and reporting tasks, and uses this to create new reingestion workflows.
provider_*workflows.py and provider_*_workflow_factory.py: minor cleanup, renames reingestion dags to use the word "reingestion" for clarity
tests/*: new and updated tests

NOTES
The regular provider flows for Europeana and Flickr are not yet enabled. Their reingestion workflows should NOT be turned on until they have been refactored, and the 'regular' provider workflow is confirmed to be working.
The TSV filenames for all regular provider workflows remain the same. For reingestion workflows, they are further partitioned by the reingestion date (the day for which data is being processed), in order to prevent collisions when reingestion for multiple days run at once. An example tsv filename for wikimedia_reingestion_workflow is: wikimedia_reingestion/year=2020/reingestion=2022-07-22/wikimedia_image_v001_20220922230222.tsv.
Testing Instructions

Verify that a few regular provider DAGs, in particular Wikimedia Commons, runs normally. You'll notice they look slightly different as the ingestion steps are now in a task group.
Run the wikimedia_reingestion_workflow. To make this quicker, you can try:

Setting a global ingestion_limit variable to something like 250 so that ingestion for each day completes early
Reducing the number of days to reingest by editing the configuration, as described above ^

Inspect the report_load_completion content for the wikimedia reingestion flow, as well as a 'normal' DAG to make sure they look correct with & without aggregation.

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@stacimc Is this PR blocked on #614?

This is in draft pending the completion of the v1.3.0 milestone - once that's complete this can be rebased and undrafted!

This took some effort to rebase 😅 but is now working again. I've tested Wikimedia and its reingestion workflow, and both are running well!

I'll address the To Do items now, and there'll be some code cleanup needed after the rebase.

Leaving myself some notes:

Update terminology everywhere to "reingestion" workflows as opposed to "ingestion", which is confusing (all provider DAGs are ingesting...)
Need to think about how to report duration for reingestion flows. Currently it's summing the duration for each of the individual pull tasks, but some of these may actually be running simultaneously. Is that valuable information?

Okay, last bit of feedback addressed. The biggest thing was related to this comment thread, but I'm just going to flag this at the top level for visibility, cc @AetherUnbound:
The tsv filenames no longer append the date to the end for dated DAGs. They should work exactly as they used to for all normal flows, and for reingestion flows we add one final partition to the prefix with the ingestion date. I've tested Wikimedia and Wikimedia Reingestion, and this is what they look like:
# wikimedia_commons_workflow
wikimedia_commons/year=2020/month=11/wikimedia_image_v001_20220922230222.tsv

# wikimedia_reingestion_workflow
wikimedia_reingestion/year=2020/reingestion=2022-07-22

Note that for reingestion, it's partitioned by year and not by month. That is because I temporarily have set the reingestion flows to run weekly instead of daily. When they get turned back on to the daily schedule, the further partitioning will be added automatically.
Sorry that took awhile to get to; the templating gave me a ton of grief!

As difficult as that templating was to figure out, I really like the new prefix

Agreed, it was definitely worth it! Much cleaner and more organized. Thanks everyone for the reviews :)


Ability to support Secure Enclave for Private Keys

Feature description

I have noticed that it isn't possible to use the faceID to generate the authentication key. It is possible with the competitor's application termius, but only with ecdsa (P256) and not with ed25519. Authenticating using physical keys through FIDO2, finger print on macBooks, or FaceID, is possible through the webauthn API. The web site webauthn.io provides a demonstration. The benefit is that the private key is stored in a secure place and can't be copied. There is also no need for passphrase as the access is controlled by biometric control. You probably already know about it. Just wanted to make sure.

By Christophe via email
Yes I’m aware about the Secure Enclave of Apple devices and I will implement it in future release.
I can’t tell you any ETA but I will try to do my best Christophe.
Related to Ability to support 2FA with FIDO2 (e.g. yubikeys) : #697

So basically we need the following in private keys:

[x] Add via paste
[x] Import from a file
[x] Generate and save to a file/exportable storage
[ ] Generate Secure Enclave/Keychain-based key, backup-enabled (IIRC, it's kSecAttrAccessibleWhenUnlocked)
[ ] Generate  Secure Enclave/Keychain-based key, non-exportable (IIRC, it's kSecAttrAccessibleWhenUnlockedThisDeviceOnly)
[ ] Add existing FIDO2 key
[ ] Register new FIDO2 key

Thank you for your wonderful app!

Thanks a lot for your support Simon @tushev 🙏
About secure enclave : Need to work a lot on the underlying SSH library because the secure enclave doesn't provide the pkey but instead can make only operations on it to proceed the cryptographic verifications.
About FIDO2 keys : don't have found - yet - how to make a communication with these devices as WebSSH is running under Mac Catalyst framework. If you have any docs about them and Mac Catalyst, please share.

Hey there!
I was actually about to raise an issue but it looks like there's already issues for this!
I use an application called Secretive for MacOS that interacts w/ the secure enclave. The private key is never exposed, so you actually can't copy it out of the enclave.
An agent runs, and it exposes the public key (which you can then copy over to whichever server you manage):

You can integrate touchID/apple watch integration (which is set through the secretive app itself) when you actually setup the key:

Then, in the ~/.ssh/config file, you add a line like so, which integrates to the socket that the secretive "agent" is running on, passing the auth into the secure enclave for validation of the private key:
Host *
        IdentityAgent /Users/kadar/Library/Containers/com.maxgoedjen.Secretive.SecretAgent/Data/socket.ssh

If you can add this feature to WebSSH to support this directive in the ssh config file (which it doesn't seem to do right now), I'd purchase your app immediately :) This is honestly my blocker at the moment, because it's so convenient (and secure) to use TouchID to authenticate each time I ssh into a remote host, and I'd love to see if WebSSH can somehow link into this well-established app.

@kmanwar89 Thank you so much for considering WebSSH and for your strong feedback about Secretive 🙏
To support Secretive I need to work on #754 and it's not trivial as it could sound
Definitively will make another eye on it because could be great as you said

Thank you so much for responding so quickly! I thought to offer Secretive as a partial solution to at least prevent you from having to figure out the mechanism for interacting with the Secure Enclave.  Best of luck and please let me know if you are looking for a beta tester :)


Layouts should not mutate data.

This will be a breaking change, but I think we really want hierarchy layouts to be immutable—to return a copy of the hierarchy with the layout’s computed coordinates applied, rather than setting the computed coordinates directly on the input hierarchy. Given that the semantics of node.copy are already defined, this should not be difficult to do. It shouldn’t be hard to implement resquarify, since it can read the input node._squarify and set the output node._squarify.
Probably this means that node.sum and node.sort should return copies of the hierarchy, too, making everything immutable.

Just a note on this, we're doing layouts on 250,000 nodes. If this was immutable, it would add a lot of GC and memory overhead


Replace TravisCI with GitHub Actions

This mimics the Travis pipeline as close as I could, somewhat arbitrarily picking Mongo 4.0 as I couldn't find that noted anywhere.
Example run here: https://github.com/duffn/slack-ruby-bot-server-stripe-sample/actions/runs/2477812442
Closes #12

Thanks! Let's simplify this a bit. Take a look at https://github.com/dblock/slack-sup/blob/master/.github/workflows/test.yml that uses some plugins for Geckodriver and such?

Yeah, that's better, thanks for the example. Updated.

Merged, really appreciate you doing this, thanks!

@duffn if you have cycles, there are other projects in this org that could use the same ❤

Sure, I saw a few others. I can take a look.


.NET NUGET Packages do not appear to be published and/or public

.NET NUGET Packages do not appear to be published and/or public

@UPSMichael, Is there something I might be missing here? I cannot find this on NUGET.org. I've contacted UPS help desk about this, but wanted to reach out directly here.

Hi @jbrown29 , thanks for reaching out. These packages are not published at nuget.org, but rather they are located here at GitHub. In order for the command to add the package to your project to work you will first need to add GitHub packages as a source. Here is a link to some information from GitHub about doing this. By default, .Net uses nuget.org to fetch any nuget packages you install. This should fix your issue.

Hi @jbrown29 , thanks for reaching out. These packages are not published at nuget.org, but rather they are located here at GitHub. In order for the command to add the package to your project to work you will first need to add GitHub packages as a source. Here is a link to some information from GitHub about doing this. By default, .Net uses nuget.org to fetch any nuget packages you install. This should fix your issue.

your "here" link is broken

Hmmm, I'll edit it for future views, but here's the link.
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry


Feature request: Allow to set export interval per metric

Hello,
I would like to suggest a feature. It would be to allow to set an export interval (reporting interval) with the same kind of filter used for the include flag.
For example, according to a global 60s export interval, I want to be able to export a custom metric data point only once per 300s/5mn. Because this metric varies little (eg: from 80% to 90% takes 4h).
With this feature, I will be able to optimize the Stackdriver costs (less datapoints, decrease the bill) for my metrics according to my business/technical needs.
Regards,
Sébastien

Thanks to have linked my feature request to the PR.
FYI I think my request is not covered by the PR. Even if a user is aware about the Stackdriver metrics billing rules and he/she accepts to pay, it is better to provide a way to push only useful data.
Using filters to decide which metrics to push is one option.
Providing a way to manage the rate per metric could be an other option.
Hope this helps to better understand the need.
Regards

@sdenef-adeo We understand that the PR was to advise the users of the costs they may incur, while your FR is to actually control those costs. That PR was referencing your FR and others as evidence that this is a real issue users face. We are currently looking into this problem from many angles, but don't have any updates on an actual solution yet.


Encode/Decode access token

The access token contains extra data (including refresh token and expiry) that is required. Loading from file does not work without this data. Added json_encode/json_decode wrappers.

I signed it!

FYI, I realise why this didn't work for me, it was because the Google API Client in v2.0 changed how the access token was returned.
See Upgrading notes from Google-Api-Php-Client
Will probably still need updating for future users.


Joystick connections/disconnections not detected

This is on the latest Sierra and High Sierra, with an Xbox 360 controller connected to a USB-C port (using a USB-A to USB-C adapter) on a MacBook Pro 2017 model.
The controller must be connected on application startup (found using glfwJoystickPresent). Any controllers connected after startup are not detected (the callback is not triggered), and neither are disconnections of controllers detected initially (e.g., the joystick callback does not appear to function on MacOS).
It seems that a controller must be connected before glfwInit is called for it to be detected. I was able to work around this error by re-initializing GLFW in an update loop every second (this application is solely for gamepad input). Using this method, I can successfully detect connections and disconnections (though I must manually call glfwJoystickPresent during this phase for known controllers to decide if they have been disconnected.

this application is solely for gamepad input

For joystick connection events to be delivered on macOS (and Windows), the main thread message queue must be polled. Try calling glfwPollEvents at regular intervals instead of reinitializing the whole library.

glfwPollEvents is already being called in the update loop. I still have to re-initialize the library for the connected state of joysticks to change.

Apologies. I should have run code before replying.
This should be fixed now with 77879736af21941a522e538a87af787fe86c648b.

Have similar problem on Windows... Disconnection is reported in the callback passed through glfwSetJoystickCallback, but there are no reconnections...

@TheDonsky That sounds like it might be a separate bug. If it's still happening, please open an issue for it. I'll need the version of GLFW and Windows and if possible the controller model and if it's wired or not.

@TheDonsky That sounds like it might be a separate bug. If it's still happening, please open an issue for it. I'll need the version of GLFW and Windows and if possible the controller model and if it's wired or not.

Controller is a regular Xbox 360 wireless controller, with the standard receiver, Microsoft sold;
Windows: Build 19043.1052 (Windows 10 Home);
GLFW: 3.3.2
Exact "symptoms" are as follows:
I have a functioning input, as long as the joystick is already connected when I first call glfwInit();
If I disconnect the controller, glfwSetJoystickCallback correctly reports the event and, naturally, my input module goes silent for the device.
Problem starts, when I reconnect the controller or simply connect it after glfwInit: glfwSetJoystickCallback reports nothing and glfwJoystickPresent/glfwGetGamepadState calls do not give me anything useful any more.
Project is not "tied" to the above version, so if it's likely fixed in the latter version, I can test with the new build without too many complications; Also, I've tested the same on my linux(Ubuntu) machine and the same code works perfectly fine there (same version). So, this makes it a Windows-only issue for me
For additional insights, feel free to look at the exact code, in case it helps:
https://github.com/TheDonsky/Jimara/blob/main/Source/Jimara/OS/Window/GLFW/GLFW_Window.cpp (line 34 for glfwSetJoystickCallback);
https://github.com/TheDonsky/Jimara/blob/main/Source/Jimara/OS/Window/GLFW/GLFW_Input.cpp (line 359 onward for gamepad state);
Behavior can be observed from any test case, that creates a window and displays some amount of 3d graphics (for example, https://github.com/TheDonsky/Jimara/blob/main/Source/Jimara-Tests/Components/MeshRendererTest.cpp but I think you probably won't need to build it, but anyway...)

@TheDonsky I can't reproduce that with the controllers I have but it sounds like a real bug, although different from this one. Please open a new issue for it. You description above is really good so you can re-use that.

@elmindreda I opened an issue: https://github.com/glfw/glfw/issues/1926
I also added a link to a screen recording of the bug "in action"; will test with a newer GLFW build as well when possible and report if it's fixed

Update: I checked 3.3.4 binaries as well and the issue persists


Add clearAllowance to ERC20

an internal function such as _clearAllowance() may be useful when a transaction requires a certain amount of token be approved for transfer but, in some cases, transfers none or a fraction of the approved amount.
This issue was reported in the LevelK audit.

@elopio In the given case, what will be the functionality of _clearAllowance()? Please add a bit more detail.

Hey @Aniket-Engg, this issue is tagged for more discussion. We'll add more details when during the next following weeks when we have time to analize it. If you have ideas, feel free to throw them in here.

Actually i was looking to know the motivation behind the suggestion of this function so that i can brainstorm it.

This can already be accomplished by calling approve(0). I'm not sure if the proposed function would add any other functionality that I'm not seeing.
@cwhinfrey Could you expand on this a bit?

@frangio Our thinking was that ERC20 subclasses may want to zero out an account's allowance, even if that account is not msg.sender. A real-world use case for this is now escaping me though. It may make sense to hold off until one comes up.

This can be achieved via ERC20._approve(), introduced in v2.2.0.


sails.getBaseUrl() is deprecated

warn: sails.getBaseUrl() is deprecated and will be removed in Sails v1.0.  See http://sailsjs.org/documentation/reference/application/sails-getbaseurl for more info.

It sure is.

I don't know why the links keep changing on the Sails website. The correct URL for getBaseURL is http://sailsjs.org/documentation/reference/application/sails-get-base-url


[release-1.19] Make authz policy update log less noisy

Manual cherrypick required.
#49601 failed to apply on top of branch "release-1.19":
Applying: make ap update less noisy
Using index info to reconstruct a base tree...
M	pilot/pkg/model/authorization.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/model/authorization.go
CONFLICT (content): Merge conflict in pilot/pkg/model/authorization.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 make ap update less noisy
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

I t hink it's not available in 1.19 yet.


silhouette for each ship

I see you can also find the silhouettes for each ship in ffg's squadronbuilder, maybe this can be added to each ship?
I'll start already, using a tag like "silhouette" and add the url for each item.

the pull request has been made, maybe there can be some scripting for gathering the images as well?, just like the scraping script?


Initialize Script Command

Adding an initialize script command will make getting started a bit easier. Specifically, I want to support a couple things:

Set up the config.ini file if not present.
Use a data/custom_components.json file to create a custom components module that can contain all components that are desired.

File format:
[
    {
        "component": "batcher",
        "type": "single",
        "module": "autotransform.batcher.single",
        "class": "SingleBatcher",
        "package": "AutoTransform"
    },
    ...
]

The values above would be replaced with the custom component's values (i.e. input if it's an input component).
The initialize script would also pip install the required packages. We could create a schema index like PyPI that would make it easy for share and distribute schemas/components.

Also interested in using this to set up the workflow files and stuff to set up the repo.


Autopairs for triple backticks

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.pairs
Description
Single back tick(`) outputs double backtick (``) but adding another
backtick(third) should output 3 more backticks for codeblocks.
code line
code
block

Thanks for suggestion, but no, this won't get implemented. mini.pairs is intended to work only for single "open" and "close" characters. I feel that snippets are better for this kind of task.

Thanks for suggestion, but no, this won't get implemented. mini.pairs is intended to work only for single "open" and "close" characters. I feel that snippets are better for this kind of task.

What snippets?
Is there an alternative to triple backticks?

I meant that functionality of "Type something which expands to ``` ``` or similar" is more suited for snippets (predefined and configurable set of expandable text). More info:

https://github.com/L3MON4D3/LuaSnip
https://github.com/rafamadriz/friendly-snippets (in particular this snippet, which you can modify to your taste)

I meant that functionality of "Type something which expands to ``` ``` or similar" is more suited for snippets (predefined and configurable set of expandable text). More info:

https://github.com/L3MON4D3/LuaSnip
https://github.com/rafamadriz/friendly-snippets (in particular this snippet, which you can modify to your taste)

Using snippets feels like an overkill. I will stick to nvim-autopairs for now
but I'd love to see this functionality getting implemented in mini.pairs.

Hi, in the case for triple backticks, if I input the third backtick, can mini.pairs ignore it and not insert the fourth backtick?

Hi, in the case for triple backticks, if I input the third backtick, can mini.pairs ignore it and not insert the fourth backtick?

Unfortunately no. See this comment.

hmm I got it that we can't work with pairs of triple backticks. But can we ignore the second pair of single backticks? Like mini.pairs already ignore ' after a letter.
Right now, after ``, if I hit ` again, I get 4 backticks and my cursor is between the third and fourth backtick.

hmm I got it that we can't work with pairs of triple backticks. But can we ignore the second pair of single backticks? Like mini.pairs already ignore ' after a letter.
Right now, after ``, if I hit ` again, I get 4 backticks and my cursor is between the third and fourth backtick.

Ah, sorry, I misread my own comment.
But the answer is still a no, because 'mini.pairs' "knows" only about single character to its left and single character to its right when making a decision whether to insert a pair or not. So having a logic "if there are two backticks to the left then insert single backtick" is not designed to be done in 'mini.pairs'.

got it! tks for the reply and for all the plugins

Hey @georgeguimaraes , maybe this solution makes your life a little easier
https://github.com/echasnovski/mini.nvim/discussions/255
        ['`'] = { action = 'closeopen', pair = '``', neigh_pattern = '[^\\`].', register = { cr = false } },

This would avoid the fourth backtick

@Susensio Love that solution, allows for pair, but not 4th backtick when doing triples. Thanks for sharing! I think this could be useful in default config to. What you think @echasnovski? 🙏

@Susensio Love that solution, allows for pair, but not 4th backtick when doing triples. Thanks for sharing! I think this could be useful in default config to. What you think @echasnovski? 🙏

I don't think it is that useful as default, as it makes typing 6 backticks (which are needed to designate a codeblock) less comfortable. The fact that it can be configured that way should be enough.

Hey thanks for the reply @echasnovski! That's fair!
The thing I'm finding is that without that config, it doesn't complete the final three ticks, it only complete one fourth tick, if that makes sense. This is with standard markdown treesitter parser that ships with the official nvim-treesitter repo. Is this how it behaves for you?

Hey thanks for the reply @echasnovski! That's fair!
The thing I'm finding is that without that config, it doesn't complete the final three ticks, it only complete one fourth tick, if that makes sense. This is with standard markdown treesitter parser that ships with the official nvim-treesitter repo. Is this how it behaves for you?

Yes, it does. The reason is that 'mini.pairs' "knows" only about cursor's single character neighborhood (by design for easier code/logic and better performance) and it can insert only two-character pair (left and right). So it can not (and will not) work with triple backticks.
Here is the use case which I meant in "... it makes typing 6 backticks ... less comfortable":
https://github.com/user-attachments/assets/39063a24-c58b-4f05-8cae-eeb5dd46db86
But a long standing suggestion is to use snippets for this type of functionality. With builtin vim.snippet it can be achieved with vim.snippet.expand('```\n$0\n```').


Direct YouTube URIs don’t return in expected results

I’ve seen a similar issue in a closed issue but there was no solution posted and the link to the bug fix that was supposed to resolve it has already been implemented.
I’ve attempting to search via various methods; yt: within the search field, ['youtube:']: as the {search}.uris etc… and although is absolutely searches YouTube, the result is never what is expected. As an example:
I’m attempting to track down specifically https://www.youtube.com/watch?v=BXpdmKELE1k
Searching for it using “Swedish House Mafia - Save The World” and “Swedish House Mafia - Save The World SHMVEVO” (the addition of it uploader) results in 5 items but none of which are the expected on.
Searching for “BXpdmKELE1k” or the full link results in some Digimon song… completely incorrect.
Another example of this is https://www.youtube.com/watch?v=ukNOaKeUEQY where the URL and video ID result in “I’m a hipster” (granted, somewhat relevant if you know the band but beside the point)
As for versions, all are latest and the only bizarre thing that may be different is I’ve manually updated the “backend_internal.py” for that most recent “unquote_plus” issue since the force update of pafy didn’t change it.

Have you been able to look into this at all?

Mopidy 3 / Mopidy-Youtube 3 (using bs4 backend):

first hit on search for “Swedish House Mafia - Save The World”  or “BXpdmKELE1k” is youtube:video/Swedish House Mafia - Save The World (Official Video).BXpdmKELE1k

first hit on search for "https://www.youtube.com/watch?v=ukNOaKeUEQY" is youtube:video/San Cisco - Awkward.ukNOaKeUEQY

I assume those search results are all as expected, so closing issue.


Report name

I'd recommend not to name the report ZABAPGIT.

I've made the adjustment to ZABAPGIT_FULL. Good idea.


Stable?

Hi,
I'm about to use this package in a big project, as it's referred by jwt-auth that we wanted to use anyway, this package seemed very useful for us. This package is being developed since 2014, when i look to the past, there are some peaks in development, at this moment it's quit, does that mean everything runs smooth? If so, why isn't there a stable version yet? in the installation docs there's still the message: "At this time the package is still in a developmental stage and as such does not have a stable release. You may need to set your minimum-stability to dev.".
Why?
Bart

Also really interested is the answer for the same question. Hope @jasonlewis or @hskrasek will pay attention on this issue to answer it.

#1383

Not stable yet. More details here #1436


Tokenise parser

Closes #144

Coverage decreased (-2.8%) to 77.586% when pulling 8cc2cac6e5b1e210f8d5e1e6c37c5cfdf05c7775 on tokenise-parser into 5c2a65d4ba50611fdf42f12b252a20bfc255be13 on master.

Coverage decreased (-0.7%) to 79.685% when pulling 8cc2cac6e5b1e210f8d5e1e6c37c5cfdf05c7775 on tokenise-parser into 5c2a65d4ba50611fdf42f12b252a20bfc255be13 on master.

reviewed

Coverage decreased (-0.5%) to 79.844% when pulling b1c70992e9e2d6a8f080a8bdf9c3857d691ff3ef on tokenise-parser into 426109169d3f8e5e9f0497e3d34527205331f242 on master.


Use ChooseHostInterface method to fetch PublicAddress

Use a better logic to fetch interface for PublicAddress.
ChooseHostInterface will check if the nic is up and will ignore docker0.

@thockin  part of https://github.com/GoogleCloudPlatform/kubernetes/issues/3681

I found out why the integration test is failing after i figured out the 2 nics for the travis-ci setup .
1)interfaces = lo
IP =<IP_ADDRESS>/8  UP=true ,  !loopback=false
2)interfaces = venet0
IP =<IP_ADDRESS>/32 UP=true  !loopback=false
both are loopback for more info look here http://tools.ietf.org/html/rfc3330#<IP_ADDRESS>/32
The logic I have is  if (nic.IsUP && !nic.Loopback) select nic;
Since both are loopback it fails.

@thockin apologies for all the commits ,But Had to figure out what was the network config for the test which failed.

Can you take a look at #4218 - they are the same issue on different components - both trying to choose the best public IP.
I think we have a better answer than this - I pasted a play link in #4218 that looks at the route tables to figure out which NIC hosts the default gateway.  PTAL?  If we think that is good enough to try, I or you can patch that in and see what Travis has to say about it...

@thockin thanks
I made few modifications , Can you please check this. http://play.golang.org/p/X4HZGnwd_M
Are you using "route -n" command ? I am not able to see the same routing fields which you see in your code.Which OS are you using ?
"route -n" returns same output on F21/Ubuntu14/Centos7/CoreOS/RHEL Atomic
#4218 talks only proxier.go code this problem exists in apiserver too.
I think that it is better if master.go and proxier.go uses ChooseHostInterface method to pick a NIC.
Although we have removed the randomness by choosing the nic with gateway everytime ,we still have to give override feature so that traffic can be just confined to a single subnet.
I will test locally and in travis to see if it breaks anything.
btw mostly the nic with gateway is the public IP of the system.Do we really have to pick the public IP nic ?
The automatic discovery seems kinda difficult.For example if there exists a alias IP on eth0 , the code picked aliasIP as the publicAddress but later the alias IP can be easily removed with system restart.And then a new IP would be picked by the daemon.So I feel having --bind-to as an interface name helps in the clarity.

The file input was /proc/net/route - should be stable across kernel
versions and distros.
I agree that we should use the same heuristic to choose the default public
interface in both master and proxy.  Before we invest too heavily in coding
this up I wanted to get a first-pass sanity check from people.  I feel like
this will be more stable overall, but I am a bit worried about it is true
multi-NIC environments (e.g. one internal NIC and one public NIC - will we
end up choosing the public?)  I guess that is what the override is for.
On Mon, Feb 9, 2015 at 9:17 AM, sub-mod<EMAIL_ADDRESS>wrote:

@thockin https://github.com/thockin thanks
I made few modifications , Can you please check this.
http://play.golang.org/p/X4HZGnwd_M
Are you using "route -n" command ? I am not able to see the same routing
fields which you see in your code.Which OS are you using ?
"route -n" returns same output on F21/Ubuntu14/Centos7/CoreOS/RHEL Atomic
#4218 https://github.com/GoogleCloudPlatform/kubernetes/issues/4218
talks only proxier.go code this problem exists in apiserver too.
I think that it is better if master.go and proxier.go uses
ChooseHostInterface method to pick a NIC.
Although we have removed the randomness by choosing the nic with gateway
everytime ,we still have to give override feature so that traffic can be
just confined to a single subnet.
I will test locally and in travis to see if it breaks anything.
btw mostly the nic with gateway is the public IP of the system.Do we
really have to pick the public IP nic ?
The automatic discovery seems kinda difficult.For example if there exists
a alias IP on eth0 , the code picked aliasIP as the publicAddress but later
the alias IP can be easily removed with system restart.And then a new IP
would be picked by the daemon.So I feel having --bind-to as an interface
name helps in the clarity.
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/4115#issuecomment-73548822
.

ok i need to check if /proc/net/route  is there on rh-atomic host
On my k8 cluster in the cloud, right now the code picks the public NIC.Because nic0 is used for public acess and other nics are used as management subnet, hadoop cluster subnet etc.I think this should not happen.
So What i need now is override feature --bind-to to select the k8-subnet of my choice, and the public Address should belong to this nic belonging to k8-subnet.(which depending on situations could be anything)

What cloud?
On Mon, Feb 9, 2015 at 10:22 AM, sub-mod<EMAIL_ADDRESS>wrote:

ok i need to check if /proc/net/route is there on rh-atomic host
On my k8 cluster in the cloud, right now the code picks the public
NIC.Because nic0 is used for public acess and other nics are used as
management subnet, hadoop cluster subnet etc.I think this should not happen.
So What i need now is override feature --bind-to to select the k8-subnet
of my choice, and the public Address should belong to this nic belonging to
k8-subnet.(which depending on situations could be anything)
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/4115#issuecomment-73560580
.

So we have 2 issues here
1)" common way for all kube daemons to be configured , for ex using --bind-to "
https://github.com/GoogleCloudPlatform/kubernetes/issues/3861
which could be a NIC name/IP address/Subnet
it has an implication that if the interface changes IP the daemon will adapt, whcih maynot be true.
for example as mentioned  by @thockin if a host uses DHCP  and you --bind-to-interface=eth0, and then eth0 gets a new IP.
But i assume that if interface changes IP, we need to do a restart host and then the new change are reflected across all nodes
2)discovery heuristics
Figure out which IP to use incase of multi nic cluster.
option1 : choose the nic with gateway
In worst case : take all the available nics and start removing from them bridge nics , p2p nics , alias nic ,docker nic , virb0 nic...etc. then one among the rest of the candidate nic can be used

@thockin can you please take a look

@thockin @brendanburns can you please take a look

Thanks for integrating my sketch and fleshing it out.  Can I trouble you for some tests with varying "route -n" results that tickle the various modes?
Once this is in, we can switch the proxy to use it, too.

@brendanburns @thockin Kindly review

rebase?

@thockin rebased . Not sure why build fails . It works for me.

Change LGTM.
Shippable says:
Auto-merging pkg/master/master.go
CONFLICT (content): Merge conflict in pkg/master/master.go
Automatic merge failed; fix conflicts and then commit the result.

@thockin does it look ok now?


Add PatrickXYS as approver

I've continuously working on kfctl and AWS will at least be supporting kfctl in short-term,
meanwhile, we'll help community bring back kfctl + manifest E2E test which consumes AWS resources.
Here is my contribution list:
https://github.com/kubeflow/kfctl/pulls/Jeffwan

/cc @Jeffwan @animeshsingh @crobby @yanniszark @vpavlin

/lgtm

Thanks for the contribution.
/approve


Wrappers around loops are not extracted with [@"substitute"]

The following doesn't extract. What I want is to inline for' and then have the special handling of C.Loops, without having to mark the wrapper as unfold (since its purpose is to ease verification).
module Extract_for_wrapper

open C.Loops
open FStar.HyperStack.ST

// unfold does work, but is undesirable for verification
[@"substitute"]
let for' = for

let for'_noop (n:UInt32.t) : Stack UInt32.t
  (requires (fun h0 -> True))
  (ensures (fun h0 r h1 -> r == n)) =
  let _ = for' 0ul n (fun h i -> True) (fun i -> ()) in
  n

To compile this, use krml -skip-compilation extract_for_wrapper.fst. Note that it requires $KREMLIN_HOME/kremlib on the include path to verify with F*.

inline_for_extraction now produces the correct code for this:
λ ferrous kremlin → λ git master* → cat Extract.c
#include "Extract.h"

uint32_t Extract_for__noop(uint32_t n1)
{
  for (uint32_t i = (uint32_t )0; i < n1; i = i + (uint32_t )1)
  {

  }
  return n1;
}

cc @protz


Error

saad@DESKTOP-D5T7V90:~/keyhunt$ ./keyhunt -f ./addresses.txt
Setting search for btc adddress
init bloom filter for 77 elements
error bloom_init
saad@DESKTOP-D5T7V90:

Hi, please update your copy of this repo to the last version: I update  and solved that bug 16 minutes ago.


Failure about unzipping the demo_1k.zip

Dear, I fail when I unzip the demo_1k.zip after I run the command  cat demo_1k_part* > demo_1k.zip_. And the error appears like
Archive:  demo_1k.zip
fatal error: read failure while seeking for End-of-centdir-64 signature.
  This zipfile is corrupt.
unzip:  cannot find zipfile directory in one of demo_1k.zip or
        demo_1k.zip.zip, and cannot find demo_1k.zip.ZIP, period.

Do you meet the problem? Is there any wrong thing or I run it wrong?
Thanks

Hi, we're currently reviewing the files to ensure if there's any file missed. We should have this resolved shortly and we'll update as soon as possible.

Hi, we're currently reviewing the files to ensure if there's any file missed. We should have this resolved shortly and we'll update as soon as possible.

Thanks a lot.

Hi, it appears that the files are correct and complete. You can try re-downloading these files.


Ready to release/deploy.

Need to change also package name "org.livingdocumentation" -> "io.github.livingdocumentation"


Feat: Scroll to the top button

Describe the feature
Want to add scroll to the top button to move to the top of the page easily.
Please assign this task to me
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@dwivedishrey I want to contribute to the project  , please assign me this under GSSOC'24

Assigned @dwivedishrey
Make sure to star the repo before working on it! Happy open-source contributing!

Hello @anuragverma108 , could you please assign this issue to me? I believe my skills are well-suited to address it. Thank you!


GPU out of memory problem

I have a problem when trying to use external memory with my GPU.
As I could learn from the docs, My Iterator is just like:
class MyIterator(xgboost.DataIter):
def init(self, raw_data):
self.raw_data = raw_data
self.data_len = int(len(raw_data[0]) / 10)
self._it = 0
super().init(cache_prefix=os.path.join('.',
os.path.basename(os.path.realpath(file)) + '.cache'))
def next(self, input_data):
    print(self._it)
    if self._it == 10
        return 0
    if self._it < 9:
        X = self.raw_data[0][self._it * self.data_len : (self._it + 1) * self.data_len]
        y = self.raw_data[1][self._it * self.data_len : (self._it + 1) * self.data_len]
    else:
        X = self.raw_data[0][self._it * self.data_len:]
        y = self.raw_data[1][self._it * self.data_len:]
    input_data(data=X, label=y)
    self._it += 1
    return 1

def reset(self):
    self._it = 0

The raw_data above is a tuple of np.array.  I was trying to split my data into 10 batches, considering that  would be fit for my GPU memory. However, it doesn't work. My data is like a 1e6*6500 np.array.  My RAM is 1T.  My GPU memory is 24G, which is absolutely enough for 10% of the data. I even tried set the subsample=0.1 and sampling_method='gradient_based'. However, I still got out of memory problem.
I don't if I tried the right way.  I want to use GPU to train my data without enough GPU memory but with totally enough RAM.
Did I use model mistakenly? And what should I do to train?
I would be really grateful to receive your apply!
And below is my version information:
Python version:3.8
CUDA:12
xgboost:1.7.6
GPU: 4090

Could you please share the data type you used for the numpy array?

Sure, the data type is np.float32. almost every column is not sparse. And I set max_bin=128

Thank you for sharing, could you please also share the size of each batch?

In the 'Iterator.next', X in Input_data(X,y) is about 1.2e56500, while y is about 1.2e51

I can see the memory spike. I will work on it after some other priorities. We still have a lots of work pending for external memory before removing the experimental tag.

Note to myself: The GPU sketching can be memory hungry. The sketch container reached 18 GB memory after the final batch of the data.

I am experiencing the same issue as the original poster. Are there any known workarounds or potential solutions, such as switching to Dask, that have been identified?

I am experiencing the same issue as the original poster. Why does the gpu's memory footprint increase as the data set grows, not as the batchsize grows, even with the use of external iterative loaders in xgboost

GPU is a special case for external memory, I'm doing a lots of experiments for the next release, see if I can get make some progress.

GPU is a special case for external memory, I'm doing lots of experiments for the next release, see if I can get make some progress.

Thank you very much. Hope some progress will be achieved.


fix: simplify bucket.on parameter names

Copying the comments on the node-sdk PR: https://github.com/nitrictech/node-sdk/pull/186#discussion_r1203881391

There are also two print statements that weren't caught in a previous PR that should be removed in the on() function.


Add Finnish translation

thanks for your PR @Anvo54!
I'm just sorry it took thaaaat long to merge it in!
Released in version 4.9.0 (Vue 3)


No hover cursor on website icon and icon click not redirecting to homepage

Bug Report
Steps
1.) Open the website.
2.) Hover over the website's icon (located in the header or elsewhere).
3.) Notice that the cursor does not change to a pointer.
4.) Click on the icon.
5.) Observe that the user is not redirected to the homepage.
Expected Result
• The cursor should change to a pointer when hovering over the website's icon, indicating it is clickable.
• Clicking on the icon should navigate the user to the homepage.
Actual Result 💣
• The hover cursor does not change to a pointer.
• Clicking the icon does not redirect the user to the homepage.
Version
v3.0.0-beta.2
Testcase
https://codesandbox.io/p/sandbox/semantic-ui-react-forked-shn7lp

Hi, just to clarify, the icon does not indicate that it is clickable, and clicking it does not redirect the user as expected. I tested this on Brave version v1.70.126 on Windows 11.
I would love to work on this issue and contribute a fix. If possible, could you please assign this issue to me? If you need any more information or further testing, feel free to ask!
Thanks for looking into this!


CI: improvements

An issue to track the various improvements that would be nice to have as part of the CI

[ ] Run clippy (needs some fixing probably in gir to avoid including unused stuff)
[ ] Run non-sys build/tests with the highest vX_Y version feature possible
[ ] Run -sys tests, see #2 for details

[ ] graphene-sys (broken)
[ ] gio-sys
[ ] glib-sys
[ ] gtk-sys fails currently
[ ] gdk-sys the tests takes way too long (not sure why?)
[ ] pango-sys fails due to mismatched version constants, they should be ignored first

[ ] Add a windows job
[ ] Add a macos job
[ ] Nightly docs
[ ] Run generator & then git diff

See https://github.com/gtk-rs/gtk-rs/issues/54 for the -sys tests problems.


Many eBooks are in EPUB format。I hope this project can support it

rt

added epub support

well done!