Mozilla Firefox policy errors

Describe the bug
After running this script, Firefox reports errors for the applied policies.
Here is a screenshot of the policy errors:

Sorry, I totally forgot to mention which Windows version and Firefox version I'm running.

We believe we've identified the errors. We're testing now and should have a new update soon.
@BoxedLight
In the mean time, please run the following to clear your local gpo policies and then reboot your system.
Get-ChildItem -Path "HKLM:\SOFTWARE\Policies" -Recurse | Remove-Item -Force -Recurse
Get-ChildItem -Path "HKCU:\SOFTWARE\Policies" -Recurse | Remove-Item -Force -Recurse
Get-ChildItem -Path "$env:windir\System32\GroupPolicy" -Recurse | Remove-Item -Force -Recurse
gpupdate /force

Alternatively, you can restore to the system restore point that our script takes prior to making changes.

Ah, okay then. I was about to test your script on a different system with english as main language. Also i noticed that DNS over HTTPS keeps turning itself off after each firefox restart. I've looked into the policy registry and saw that your script sets the registry key at "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\Firefox\DNSOverHTTPS" DWORD "Enabled" to "1".
I'm not sure if I'm interpreting it correctly. Is your script supposed to enable DoH or disable it? Because by looking at the registry key I assume it's supposed to enable DoH.
I guess i could fallback to Windows' network settings and add my own DNS there. I am just wondering why in Firefox DoH keeps turning off after restart.

Ah, okay then. I was about to test your script on a different system with english as main language. Also i noticed that DNS over HTTPS keeps turning itself off after each firefox restart. I've looked into the policy registry and saw that your script sets the registry key at "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\Firefox\DNSOverHTTPS" DWORD "Enabled" to "1".
I'm not sure if I'm interpreting it correctly. Is your script supposed to enable DoH or disable it? Because by looking at the registry key I assume it's supposed to enable DoH.
I guess i could fallback to Windows' network settings and add my own DNS there. I am just wondering why in Firefox DoH keeps turning off after restart.

Yeah, the script implements enterprise guidelines.
You should be using system dns and not browser. Additionally, we implement the DoD STIGs, which mandate that setting.
If you want DNS/TLS or DNS/HTTPs, and you should, doing it in browser isn't supported.
For enterprises it's because they want to be able to see where you're going. But for everyone else, it's just better to have it run on a system level than just your browser.

Just finished testing the changes. I believe we've fixed them all.  @BoxedLight
Give us a little to update this repo and we'll @ you again when it's done.
We have up update multiple repos with these changes.

@BoxedLight  https://github.com/simeononsecurity/Windows-Optimize-Harden-Debloat/commit/411b18090d48085704aeba7cbcfaabed74e9197d
Fixes have been made. Please run the script again.

i ran the powershell one-liner (iwr -useb 'https://simeononsecurity.ch/scripts/windowsoptimizeandharden.ps1'|iex).
This time I used a different system with english as main language and different Windows 11 edition.
Unfortunately, the errors regarding group policies still remain.

i ran the powershell one-liner (iwr -useb 'https://simeononsecurity.ch/scripts/windowsoptimizeandharden.ps1'|iex).
This time I used a different system with english as main language and Windows 11 Enterprise edition.
Unfortunately, the errors regarding group policies still remain.

The other group polices work just fine in Firefox. So I don't know what happened there. On both Windows 11 Pro and Enterprise its a complete clean install. I ran your script as soon as Windows was done installing itself and the drivers.
![1](https://github.com/simeononse

curity/Windows-Optimize-Harden-Debloat/ass
![3](https://github.com/simeononsecurit
![4](https://github.com/simeonons

ecurity/Windows-Optimize-Harden-

Debloat/assets/115804951/14fa850c-f9cf-4926-89b3-e14973cb84ca)
y/Windows-Optimize-Harden-Debloat/assets/115804951/c9610d6f-7543-4242-b37d-6c97d81b098a)
ets/115804951/db5423ef-572f-489a-9846-630494e67cbd)

Yeah @BoxedLight
I've cleared out all of those urls in the policies.
So that means that you've still got some configurations in your firefox policies file.
Write-Host "Reversing the FireFox STIGs changes" -ForegroundColor Green

    # Remove the Firefox configuration files from Program Files directories
    $firefox64 = "C:\Program Files\Mozilla Firefox"
    $firefox32 = "C:\Program Files (x86)\Mozilla Firefox"

    If (Test-Path -Path $firefox64) {
        Remove-Item -Path "$firefox64\defaults" -Force -Recurse
        Remove-Item -Path "$firefox64\mozilla.cfg" -Force
        Remove-Item -Path "$firefox64\local-settings.js" -Force
        Write-Host "Firefox 64-Bit Configurations Removed" -ForegroundColor Green
    }
    Else {
        Write-Host "FireFox 64-Bit Is Not Installed" -ForegroundColor Red
    }

    If (Test-Path -Path $firefox32) {
        Remove-Item -Path "$firefox32\defaults" -Force -Recurse
        Remove-Item -Path "$firefox32\mozilla.cfg" -Force
        Remove-Item -Path "$firefox32\local-settings.js" -Force
        Write-Host "Firefox 32-Bit Configurations Removed" -ForegroundColor Green
    }
    Else {
        Write-Host "FireFox 32-Bit Is Not Installed" -ForegroundColor Red
    }

should clear it up but you may have to uninstall firefox and reinstall it as well.

Good to know then. I've looked into the browser extensions that your script was enforcing. HTTPS Everywhere seems to have been taken down from the Mozilla extension store. "https://addons.mozilla.org/firefox/downloads/file/3574076/https_everywhere-2020.5.20-an+fx.xpi" just points to a blank page.
With Cookie Autodelete and History Autodelete, I think the problem is the version number.
I edited the registry keys for both extensions to the most recent version number and after opening Firefox, it installed the 2 extensions without problems and the errors regarding the extensions were gone.
So for Cookie Autodelete and History Autodelete I think you have to update the version number in the XPI-URL. As for HTTPS Everywhere... well. The URL points to a blank page and searching for it on addons.mozilla.org returned nothing. I guess HTTPS Everywhere is gone for good then.

Yes @BoxedLight  I've already handled that in the updates. Your box just didn't get it.
Try the script I added above to clear those Firefox policies and rerun the script.

That stuff is handled in this file primarily
https://github.com/simeononsecurity/Windows-Optimize-Harden-Debloat/blob/master/Files/FireFox Configuration Files/distribution/policies.json

There is overlap with the gpos.
But the way I understand it is that these config files overrule those options.
But I did make the appropriate changes there as well.

Just did the same on my Windows 11 Enterprise system. Complete clean re-install. Exactly the same result.

I think we got it this time.
We usually import our gpos into a fresh domain controller for editiing.
This time however, we ran into a weird bug where when we made the edits they didn't actually save when we closed the window.
Uploading some changes momentarily that should work.

@BoxedLight try now

Actually that was not it.
Seems we had those settings duplicated in another policy that they shouldn't have been in

@BoxedLight
Ok should be fixed now.
Try again

Very nice.
No more policy errors in Firefox.
Also, I'm very impressed that you've managed to bring back HTTPS Everywhere. I couldn't find it on the Mozilla addons page. Anways. Issue's finally resolved.
Thank you for your efforts. I really apprechiate it.


feat(docs): add english documentation

Issue #, if available:
Closes #1
Description of changes:
Adds English Documentation
Rendered
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM. Let me merge this.


feat: merge utility for pbin files

See also #22.
This got solved by introducing another entrypoint next to the existing ones for indexing and packing.
Since the amount of entrypoints grew quite a lot, I decided to create a respective subgroup, rename the existing entry points and update / add documentation when using it from CLI.
The utility itself currently works single threaded, but streamed, so we don't risk a memory leak, when merging very large datasets.
A small benchmark indicates:
When using two 200k sample encoded pbin files (each 355 mb respectively), the utility requires overall less than 8 seconds. However 5 seconds are required overall to initiate the python process itself (loading torch and other heavy stuff). Therefore less than 3 seconds is more realistic. A more detailed analysis was not made.

It is important to note that this branch is based on #40, since it uses a lot of the included features and changes. Therefore it might be easier to review this in comparison to the state in #40 instead of main. Alternatively, wait until #40 was merged and compare again against main

second reviewer @le1nux

Great job.

I changed the source perf/benchmark-datasets-again-megatronlm to check the changes and now changed it back to main, in case anyone wonders.
I added a comment: It might be you do some redundant file exist checks
I like you check if the same tokenizer is used
I like the extensive tests. Makes it easier to read and ensure robustness.

Overall: Approved as soon as redundant checks are clarified ;-)


Metadata update for PostgreSQL Java SDK

Removing rogue metadata
ms.prod: azure
ms.technology: azure

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/postgresql.md
:white_check_mark:Succeeded
View (azure-java-stable)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Bug] Incorrect API values after type AgentStateType update

Hi there,
I'm writing to report that I've encountered an issue when using the AgentStateType enum in the latest API version.
    "amazon-connect-streams": "^2.14.6",

enum AgentStateType {
    /** The agent state hasn't been initialized yet. */
    INIT = "init",

    /** The agent is in a state where they can be routed contacts. */
    ROUTABLE = "routable",

    /** The agent is in a state where they cannot be routed contacts. */
    NOT_ROUTABLE = "not_routable",

    /** The agent is offline. */
    OFFLINE = "offline",

    /** The agent is in a system state. */
    SYSTEM = "system",

    /** The agent is in a error state. */
    ERROR = "error",
  }

The type has been updated but the underlying values haven't been updated in the library
   * enum AgentStateType
   */
  connect.AgentStateType = connect.makeEnum([
    'init',
    'routable',
    'not_routable',
    'offline'
  ]);
  connect.AgentStatusType = connect.AgentStateType;

so this value connect.AgentStateType.SYSTEM equals undefined.

any idea when we can expect a new release with this fix?


Orm.pool() method improvements

it would be cool to treat this method differently depending on if it was called with a class or an instance of the class
so, if it was called with just the class then nothing would change, but, if it is called with an instance then the Pool instance will have that instance already in its cache:
class Foo(Orm): pass

Foo.pool() # nothing changes, it returns an empty Pool instance

f = Foo.create()
f.pool() # the Pool instance contains f instance at f.pk

this might not be worth doing since if the Orm instance doesn't have a pk then it can't be put into the OrmPool instance, and I'm not sure I want this method to return 3 different states to save one query


Enable processing of DSL .deface files

Implementation for Rails 6 only loads the .rb files. DSL .deface overrides were ignored.

Thanks for resolving this issue. The patch has been integrated into the plugin.


Do not merge. CI memory issue. Test the default RAM size

[citest pending]

[citest bad]

[citest pending]

I think we can close this PR

[citest pending]


"ng serve --prod --build-optimizer" live-reloads cause Javascript error in browsers

Versions
Angular CLI: 1.6.3
Node: 8.9.3
OS: win32 x64
Angular: 5.1.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.6.3
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.3
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.4.2
webpack: 3.10.0

Repro steps

ng new repro-app
ng serve --prod --build-optimizer
Add css to styles.css in VS Code and save.
While the project is rebuilding, also change and save index.html.
Inspect browser console for error output
Subsequent rebuilds still throw the error even if only changing one file at a time.

Observed behavior
The first build is served with no issue. The third build generates an error, which is below.
CLI Output
 ng serve --prod --build-optimizer
****************************************************************************************
This is a simple server for use in testing or debugging Angular applications locally.
It hasn't been reviewed for security issues.

DON'T USE IT FOR PRODUCTION!
****************************************************************************************
** NG Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
Date: 2018-01-08T21:34:33.896Z
Hash: dcf6fdafe5526d65c989
Time: 19290ms
chunk {0} polyfills.61df7d7ec492d95bb0b2.bundle.js (polyfills) 61.2 kB [initial] [rendered]
chunk {1} main.da0014a7afa74a009599.bundle.js (main) 293 kB [initial] [rendered]
chunk {2} styles.7603117359b5a8dffd89.bundle.css (styles) 105 bytes [initial] [rendered]
chunk {3} inline.d3c0cf3dc365c4d3fdfc.bundle.js (inline) 1.45 kB [entry] [rendered]

webpack: Compiled successfully.
webpack: Compiling...

Browser Console Stack Trace
Uncaught TypeError: (void 0) is not a function
    at Object.cDNt (main.2d2b3f0de20dee881539.bundle.js:1)
    at o (inline.a443620b1a7e83c745b9.bundle.js:1)
    at Object.0 (main.2d2b3f0de20dee881539.bundle.js:1)
    at o (inline.a443620b1a7e83c745b9.bundle.js:1)
    at window.webpackJsonp (inline.a443620b1a7e83c745b9.bundle.js:1)
    at main.2d2b3f0de20dee881539.bundle.js:1
cDNt @ main.2d2b3f0de20dee881539.bundle.js:1
o @ inline.a443620b1a7e83c745b9.bundle.js:1
0 @ main.2d2b3f0de20dee881539.bundle.js:1
o @ inline.a443620b1a7e83c745b9.bundle.js:1
window.webpackJsonp @ inline.a443620b1a7e83c745b9.bundle.js:1
(anonymous) @ main.2d2b3f0de20dee881539.bundle.js:1

Desired behavior
The rebuilt webapp should be served on every rebuild.

any progress now?
I meet this problem too...and set "sourceMap" as true to debug it, it show this error"TypeError: (void 0) is not a function" in " observers.es5.js.pre-build-optimizer.js:38:47".
error generated in the last second line code.
MutationObserverFactory.prototype.create = /**
* @param {?} callback
* @return {?}
/
function (callback) {
return typeof MutationObserver === 'undefined' ? null : new MutationObserver(callback);
};
MutationObserverFactory.decorators = [
{ type: Injectable, args: [{ providedIn: 'root' },] },
];
/ @nocollapse / MutationObserverFactory.ngInjectableDef = ɵɵdefineInjectable({ factory: function MutationObserverFactory_Factory() { return new MutationObserverFactory(); }, token: MutationObserverFactory, providedIn: "root" });
return MutationObserverFactory;
}());

As it is something different as this problem, I open another issue #14384

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


RL2 ContextBuilder

An issue to discuss to discuss the Context Builder API and implementation.

public interface IContextBuilderBundle
{
function install(builder:IContextBuilder):void;
}
public interface IContextConfig
{
function configure(context:IContext):void;
}
public interface IContextExtension
{
function install(context:IContext):void;
function initialize():void;
function uninstall():void;
}
I am finding it less than obvious what belongs in a bundle vs. a config vs. an extension. And the ContextBuilder code for managing these 3 things has some duplication. Also, ConfigManager and ExtensionManager have some duplication and feel a bit like busywork.
I have a naive thought that some of these could be replaced with prescriptive commands with [Inject] points and an interface that indicates the thing can be installed/uninstalled. I hope we can reduce the number of concepts and types a bit. Just a gut thing; could be wrong.

IContextConfig, IContextBuilderBundle, IContextExtension, ExtensionManager etc, are monsters and I apologise for their existence. They are the shameful remnants of one of my failed attempts at solving a couple of problems.
Essentially, extensions and bundles need a way to hook in to the builder/context life-cycles in order to configure things at different stages of the build process.
Sometimes these extensions only need to know when the builder/context entered into a specific phase.
For example, an extension that simply wants to put a mapping into the injector must, at the very least, wait for an injector to be available and finalised before it can safely do.
An extension that depends on services offered by another extension can only configure itself when those services have been made available (mapped into the injector).
And there are times when an extension needs to be able to suspend the build at a particular point and wait for a file or module to load, or some other asynchronous process to complete.
The lolcode presently residing in my portion the repo attempts to offer this functionality by providing interfaces that the builder/"extension manager" can call into at various stages of the build. It is absolutely, stunningly horrendous. At the time I just wanted something smallish that didn't require metadata processing or a flow control library, and wouldn't force us into building an object definition registry. I was trying to keep it small, but just made a mess - although it did give a better feel for the problem. I'm trying out a new approach tonight/tomorrow, will see how that goes. The new approach is not at all directly related to any of these async JavaScript libraries:
Promises/A spec
http://wiki.commonjs.org/wiki/Promises/A
task.js (Promise/A)
http://taskjs.org/
https://github.com/mozilla/task.js/blob/master/lib/task.js
jQuery Deferred (Promise/A)
http://api.jquery.com/category/deferred-object/
https://github.com/jquery/jquery/blob/master/src/deferred.js
https://github.com/jquery/jquery/blob/master/test/unit/deferred.js
async
https://github.com/caolan/async
https://github.com/caolan/async/blob/master/test/test-async.js
when.js
https://github.com/briancavalier/when.js
https://github.com/briancavalier/when.js/blob/master/when.js

Anything that works beats what doesn't work or hasn't even been started :)
No shame in having used the more obvious solution to get to a point where we have tests that a more elegant solution can be built to pass. I think that's what we've done everywhere isn't it?
I also think that once you appreciate that an extension and a config have a key difference, and that a bundle is just a grouping of extensions into 'features' or 'flavours' for convenience, there's a pretty low cognitive overhead to the current solution - I know it wasn't immediately obvious to Robert what the 3 do, but I'd bring to his attention NativeSignal as another non-intuitive but useful distinction... ;) Sometimes there just isn't a norm-speak term with enough precision to get the job done without a little explanation. (Though I agree we should strive to find them where they exist).
As far as I'm concerned:
MyAppConfig
MediatorMapExtension
ClassicRobotlegsBundle
go most of the way to indicating the differences.
But - if there's a new shiny solution coming - great!
Sx
On 4 Jan 2012, at 00:03, Shaun Smith wrote:

IContextConfig, IContextBuilderBundle, IContextExtension, ExtensionManager etc, are monsters and I apologise for their existence. They are the shameful remnants of one of my failed attempts at solving a couple of problems.
Essentially, extensions and bundles need a way to hook in to the builder/context life-cycles in order to configure things at different stages of the build process.
Sometimes these extensions only need to know when the builder/context entered into a specific phase.
For example, an extension that simply wants to put a mapping into the injector must, at the very least, wait for an injector to be available and finalised before it can safely do.
An extension that depends on services offered by another extension can only configure itself when those services have been made available (mapped into the injector).
And there are times when an extension needs to be able to suspend the build at a particular point and wait for a file or module to load, or some other asynchronous process to complete.
The lolcode presently residing in my portion the repo attempts to offer this functionality by providing interfaces that the builder/"extension manager" can call into at various stages of the build. It is absolutely, stunningly horrendous. At the time I just wanted something smallish that didn't require metadata processing or a flow control library, and wouldn't force us into building an object definition registry. I was trying to keep it small, but just made a mess - although it did give a better feel for the problem. I'm trying out a new approach tonight/tomorrow, will see how that goes. The new approach is not at all directly related to any of these async JavaScript libraries:
Promises/A spec
http://wiki.commonjs.org/wiki/Promises/A
task.js (Promise/A)
http://taskjs.org/
https://github.com/mozilla/task.js/blob/master/lib/task.js
jQuery Deferred (Promise/A)
http://api.jquery.com/category/deferred-object/
https://github.com/jquery/jquery/blob/master/src/deferred.js
https://github.com/jquery/jquery/blob/master/test/unit/deferred.js
async
https://github.com/caolan/async
https://github.com/caolan/async/blob/master/test/test-async.js
when.js
https://github.com/briancavalier/when.js
https://github.com/briancavalier/when.js/blob/master/when.js

Reply to this email directly or view it on GitHub:
https://github.com/robotlegs/robotlegs-framework/issues/32#issuecomment-3348548

My new approach is in place and feels fairly resolved. Closing this for now, feel free to re-open.


typo fix show frontends doc typo

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Avoid duplicate instance names in variable fonts

Description
Added check to avoid duplicate instance names in variable fonts
To Do

[x] update CHANGELOG.md
[ ] wait for checks to pass (except github/pages, which is stuck)
[ ] request a review

I don't understand the CI error unfortunately :/
The whole doc basically doesn't pass pylint

************* Module fontbakery.profiles.googlefonts

Lib/fontbakery/profiles/googlefonts.py:4644:-1: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation)


Add a MongoDB credentials provider

Add a MongoDB credentials provider to provide credentials from another source than the MongoDB connection url.
The provider is called only if there is no credentials in the Mongo connection url.
By default, the provider provides no credentials.

merged. Thanks.


Formal grammar spec for prql

A formal grammar specification would allow others to easily create parsers, do you have a preference PEG or BNF ?

Once syntax has an initial decision, I can take up an ANTLR parser

Thanks for opening the issue @qorrect !
My initial plan was to write a parser in nom, which I've heard great things about and had good initial experiences with. As you can see, it's not much at the moment.
I think a formal grammar would be useful, and the language is developed enough to start on that if someone wants to have a go. I would vote to go for a PEG grammar given the language is relatively simple™, and if we pursue the nom route it'll be broadly compatible.
As ever, open to feedback! Thank you!

With a formal grammar you could generate a syntax diagram #1810.


ChatGPT API

There is a remote API that you can use with the API token that you can get from your account.
It is part of the OpenAPI API. The completion is now free, but these APis are not cheap. OpenAPI Playground. The completion API conditions.
The general FAQ about ChatGPT is a must read.

Completion endpoint: https://api.openai.com/v1/completions
POST sample:

{
    "prompt": "from when is the more recent data that you have?",
    "model": "text-davinci-003",
    "temperature" : 1,
    "stop": "",
    "max_tokens": 1024
}

Completion endpoint response:

{
    "id": "cmpl-6lOTgQpJO7QJTyNyuoPNoKfDVOMaA",
    "object": "text_completion",
    "created":<PHONE_NUMBER>,
    "model": "text-davinci-003",
    "choices": [
        {
            "text": "\n\nThe most recent data we have varies depending on the specific dataset and source. Please contact us if you require more specific details.",
            "index": 0,
            "logprobs": null,
            "finish_reason": "stop"
        }
    ],
    "usage": {
        "prompt_tokens": 11,
        "completion_tokens": 27,
        "total_tokens": 38
    }
}

Doc

What are the limits of this endpoint?
What are the params? The implication of using different models?
Which other points exist?

Interesting:

Can I use output from ChatGPT for commercial uses?
Subject to the Content Policy and Terms, you own the output you create with ChatGPT,
including the right to reprint, sell, and merchandise – regardless of whether output was generated through a free or paid plan.
But it seems the completions API has different rules than the ChatGPT. We must recheck it.

Great, the accountability of my use of the API:


Testing PR CI

Updating Metrics server to see if TestGrid runs.

the testgrid spec appears to be the following:
{
    "kind": "Installer",
    "apiVersion": "cluster.kurl.sh/v1beta1",
    "metadata": {
        "name": "test",
        "creationTimestamp": null
    },
    "spec": {
        "kubernetes": {
            "version": "latest"
        }
    }
}

(and is the same for both runs)
So I think there's something going on here - maybe the testgrid CLI needs to be updated to use the new spec?

the testgrid spec appears to be the following:
{
    "kind": "Installer",
    "apiVersion": "cluster.kurl.sh/v1beta1",
    "metadata": {
        "name": "test",
        "creationTimestamp": null
    },
    "spec": {
        "kubernetes": {
            "version": "latest"
        }
    }
}

(and is the same for both runs)
So I think there's something going on here - maybe the testgrid CLI needs to be updated to use the new spec?

@laverya good find. The new spec should be gettting passed into the CLI but I'll have to debug.

@laverya good find. The new spec should be gettting passed into the CLI but I'll have to debug.


code hangs during slice registration

After adjusting the slice alignment and pressing 'h' to register the slice, the code hangs in allenAtlasBrowser, when doing this operation:
 trans = double(roipoly(uint8(ud.ref)));
Is this expected? How long should it take to run?

This is because the code wait for the user to draw a polygon. I'll update the documentation.


AttributeError: 'Namespace' object has no attribute 'transcoded_video_path'

After trying to run command:
python main.py -ntm -iv w_original.MP4 -tv w_placebo.mp4 -ssim -psnr
Get this error:
Traceback (most recent call last):   File "/home/vm/video-quality-metrics/main.py", line 300, in <module>     output_folder = f"[VQM] {Path(args.transcoded_video_path).name}"                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'Namespace' object has no attribute 'transcoded_video_path'. Did you mean: 'transcoded_video'?

Hey there! It seems that the error is due to the transcoded_video_path attribute not being defined in the argument parser. From your command, it looks like you might have intended to use -tv for the transcoded video file.
Could you check if the argument parser in main.py defines transcoded_video_path or if it should be transcoded_video instead? You might want to replace args.transcoded_video_path with args.transcoded_video in line 300.

Well, I took this command from very first example here and then did not change anything in main.py, so it's as well default. Basically tried to run mint command wirh mint installation, but with error. :-)
I am no coder unfortunately, it took me a while to get it "running" up to this point, but I am not sure how definition should look like in main.py.
I see only args.transcoded_video_path  and not args.transcoded_video in main.py

@gedimiz Fixed  🙂
If you pull the latest code and run python main.py -ntm -iv w_original.MP4 -tv w_placebo.mp4 -ssim -psnr it should work. Let me know if you run into any other issues or if you have any questions.


multi: always fail pending htlcs on commitment confirmation

In this commit, we address a TOOD, and end up fixing a lingering bug related to commitments on chain. Before this commit, it was possible that lnd would unnecessarily cause an incoming link to force close on chain if the outgoing link was in an indeterminate state. We fix this issue by always checking for HTLCs that we need to time out on the incoming link based on all valid commits. With this fix, we'll no longer go to chain unnecessarily which wastes chain fees and may also increase off-chain HTLC fail delays.
Fixes #2045.

Updated with a new commit structure to ensure each of them compile.

PTAL @cfromknecht @joostjager!

PTAL @joostjager @cfromknecht

PTAL @cfromknecht @joostjager


Mathematical expression for first and last of integer types does not support parentheses to ensure the order of operations

When defining the lower and upper bound of an integer, sometimes you want to use parentheses to establish the order of operations. When checking the specification, the following error occurs:
model: error: last of "XXX" contains variable
To work around this, I just do the math offline and sub in the values. However, those magic numbers without comments make it more difficult to reason about the specification. Also, often times interface documents for binary protocols define ranges as mathematical expressions and I find it nice to verbatim put those in my specifications.
It would be nice to support parentheses in mathematical expressions.

Actually ... I think I misunderstood a bit of the level RecordFlux works at and the use of the Opaque type. I was trying to define all my fields in RecordFlux! I have a better understanding now the gist of it, so I'm not sure if this is relevant or not anymore.


Remove serverless function components

Closing in favor of https://github.com/webhintio/online-service/pull/521


Nested Child spans are not getting parented correctly

Please answer these questions before submitting a bug report.
What version of OpenTelemetry are you using? 0.15.0
What version of Node are you using? v14.15.5
Please provide the code you used to setup the OpenTelemetry SDK : https://github.com/mnadeem/nodejs-opentelemetry-tempo
What did you do? Created Child Spans
const doSomeWorkInNewNestedSpan = (parentSpan) => {
    const childSpan = tracer.startSpan('doSomeWorkInNewNestedSpan', {
        parentSpan, attributes: { 'code.function' : 'doSomeWorkInNewNestedSpan' }
    });
    childSpan.setAttribute('code.filepath', "test2");
    //Do some work
    doSomeHeavyWork();
    childSpan.end();
}

If possible, provide a recipe for reproducing the error.:  Follow the guidelines in https://github.com/mnadeem/nodejs-opentelemetry-tempo
What did you expect to see?   Nested Child spans should be parented correctly
Something like this nested and stair cased (from https://github.com/mnadeem/boot-opentelemetry-tempo)

What did you see instead? Nested child spans are not parented correctly

Additional context
Add any other context about the problem here.

Using parent option in tracer.startSpan has been removed via #1612 because it was removed from the spec.
It's needed to use context for this. Either passing it manual like here or using context.with() as shown here.
There might come helpers to ease this (see #1923).

I am getting TypeError: _api.default.setSpan is not a function any help would be greatly appreciated
1

2
import opentelemetry, {context, getSpan } from '@opentelemetry/api';

    const childSpan = tracer.startSpan('doSomeWorkInNewSpan', {
        attributes: { 'code.function' : 'doSomeWorkInNewSpan' }
    });

    opentelemetry.context.with(opentelemetry.setSpan(opentelemetry.context.active(), childSpan), () => {
        console.log('Client traceId ', span.context().traceId);
    });

TypeError: _api.default.setSpan is not a function
    at doSomeWorkInNewSpan (E:\githubRepos\nodejs-opentelemetry-tempo\src\/server.js:44:46)
    at E:\githubRepos\nodejs-opentelemetry-tempo\src\/server.js:33:5
    at Layer.handle [as handle_request] (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\layer.js:95:5)
    at next (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\route.js:137:13)
    at Route.dispatch (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\route.js:112:3)
    at E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\@opentelemetry\plugin-express\build\src\express.js:182:41
    at Layer.handle [as handle_request] (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\layer.js:95:5)
    at E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\index.js:281:22
    at Function.process_params (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\index.js:335:12)
    at next (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\index.js:275:10)

Seems something is wrong with our imports here. Looks like you use import but not typescript. I assume some other transpiler is used here.
can you reproduce this by using plain JavaScript or Typescript?

I am using Babel https://github.com/mnadeem/nodejs-opentelemetry-tempo/blob/main/package.json
I don't have project setup for typescript, further I would have to learn Typescript

I never used babel so can't help here. But I think instead _api.default.setSpan it should be _api.setSpan so it's related to import and this is where babel does some magic in your sample.

If I do it little differently
import opentelemetry, {context, getSpan } from '@opentelemetry/api';

What about import { setSpan, getSpan } from '@opentelemetry/api';?

const opentelemetry = require('@opentelemetry/api');
const {context, getSpan } = opentelemetry;

app.get('/health', (req, res) => {
    const parentSpan = getSpan(opentelemetry.context.active());
    doSomeHeavyWork();
    doSomeWorkInNewSpan(parentSpan);

    return res.status(200).send({ message: "Health is good" });
});

const doSomeWorkInNewSpan = (parentSpan) => {

    const ctx = opentelemetry.setSpan(opentelemetry.context.active(), parentSpan);
    const childSpan = tracer.startSpan('doWork', undefined, ctx);

    childSpan.setAttribute('code.filepath', "test");
    doSomeHeavyWork();
    doSomeWorkInNewNestedSpan(childSpan);
    childSpan.end();
}

I am not getting exception now, however nested span is not working now as well.
Note: the version is 0.15.0

Following does not give any error, however same result as above
import { context, setSpan, getSpan } from '@opentelemetry/api';

app.get('/health', (req, res) => {
    const parentSpan = getSpan(context.active());
    doSomeHeavyWork();
    doSomeWorkInNewSpan(parentSpan);

    return res.status(200).send({ message: "Health is good" });
});

const doSomeWorkInNewSpan = (parentSpan) => {

    const ctx = setSpan(context.active(), parentSpan);
    const childSpan = tracer.startSpan('doWork', undefined, ctx);

    childSpan.setAttribute('code.filepath', "test");
    doSomeHeavyWork();
    doSomeWorkInNewNestedSpan(childSpan);
    childSpan.end();
}

Here is the output of consoleexporter
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'middleware - query',
  id: 'f74fcf045a928b0c',
  kind: 0,
  timestamp:<PHONE_NUMBER>985924,
  duration: 312,
  attributes: {
    component: 'express',
    'express.name': 'query',
    'express.type': 'middleware'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'middleware - expressInit',
  id: '75eb87b09dd84165',
  kind: 0,
  timestamp:<PHONE_NUMBER>991599,
  duration: 303,
  attributes: {
    component: 'express',
    'express.name': 'expressInit',
    'express.type': 'middleware'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'middleware - <anonymous>',
  id: '67b78f1fe81d7024',
  kind: 0,
  timestamp:<PHONE_NUMBER>994591,
  duration: 206,
  attributes: {
    component: 'express',
    'express.name': '<anonymous>',
    'express.type': 'middleware'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'middleware - jsonParser',
  id: '336f1d7900ccbfb7',
  kind: 0,
  timestamp:<PHONE_NUMBER>997762,
  duration: 222,
  attributes: {
    component: 'express',
    'express.name': 'jsonParser',
    'express.type': 'middleware'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'middleware - corsMiddleware',
  id: 'dd3071dd37a2f3d4',
  kind: 0,
  timestamp:<PHONE_NUMBER>001133,
  duration: 490,
  attributes: {
    component: 'express',
    'express.name': 'corsMiddleware',
    'express.type': 'middleware'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'middleware - addCorsHeaders',
  id: '0abaa3c0fdc3bb81',
  kind: 0,
  timestamp:<PHONE_NUMBER>004420,
  duration: 153,
  attributes: {
    component: 'express',
    'express.name': 'addCorsHeaders',
    'express.type': 'middleware'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'middleware - addTraceId',
  id: '21fdc5ad584db508',
  kind: 0,
  timestamp:<PHONE_NUMBER>006335,
  duration: 80,
  attributes: {
    component: 'express',
    'express.name': 'addTraceId',
    'express.type': 'middleware'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'middleware - measureRequestDuration',
  id: 'c9b8a360ed6028f9',
  kind: 0,
  timestamp:<PHONE_NUMBER>009802,
  duration: 86,
  attributes: {
    component: 'express',
    'express.name': 'measureRequestDuration',
    'express.type': 'middleware'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'request handler - /health',
  id: '20cdf60888bf948a',
  kind: 0,
  timestamp:<PHONE_NUMBER>012158,
  duration: 16,
  attributes: {
    component: 'express',
    'http.route': '/health',
    'express.name': '/health',
    'express.type': 'request_handler'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'doSomeWorkInNewNestedSpan',
  id: 'f6c5672875accd06',
  kind: 0,
  timestamp:<PHONE_NUMBER>015718,
  duration: 213,
  attributes: {
    'code.function': 'doSomeWorkInNewNestedSpan',
    'code.filepath': 'test2'
  },
  status: { code: 1 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: '13bed0fa605b94f1',
  name: 'doWork',
  id: '6966619959f1ca61',
  kind: 0,
  timestamp:<PHONE_NUMBER>015104,
  duration: 3764,
  attributes: { 'code.filepath': 'test' },
  status: { code: 1 },
  events: []
}
{
  traceId: 'afbfcb316fd995d365ed894b0b7e0202',
  parentId: undefined,
  name: 'HTTP GET',
  id: '1e8ffac029ab260c',
  kind: 1,
  timestamp:<PHONE_NUMBER>983562,
  duration: 39472,
  attributes: {
    'http.url': 'http://localhost:5555/health',
    'http.host': 'localhost:5555',
    'net.host.name': 'localhost',
    'http.method': 'GET',
    'http.route': '/health',
    'http.target': '/health',
    'http.user_agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36',
    'http.flavor': '1.1',
    'net.transport': 'IP.TCP',
    'net.host.ip': '::1',
    'net.host.port': 5555,
    'net.peer.ip': '::1',
    'net.peer.port': 55604,
    'http.status_code': 304,
    'http.status_text': 'NOT MODIFIED'
  },
  status: { code: 0 },
  events: []
}
{
  traceId: 'be4f519b1f0075825e9427ff2b98d2d4',
  parentId: undefined,
  name: 'GET /health',
  id: '13bed0fa605b94f1',
  kind: 1,
  timestamp:<PHONE_NUMBER>984685,
  duration: 44070,
  attributes: {
    'http.url': 'http://localhost:5555/health',
    'http.host': 'localhost:5555',
    'net.host.name': 'localhost',
    'http.method': 'GET',
    'http.route': '/health',
    'http.target': '/health',
    'http.user_agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36',
    'http.flavor': '1.1',
    'net.transport': 'IP.TCP',
    'net.host.ip': '::1',
    'net.host.port': 5555,
    'net.peer.ip': '::1',
    'net.peer.port': 55604,
    'http.status_code': 304,
    'http.status_text': 'NOT MODIFIED'
  },
  status: { code: 0 },
  events: []
}

in your last sample the implementation of doSomeWorkInNewNestedSpan is missing. If it is still implemented as in the initial post it can't work as you don't pass the child span via context nor is it set active.

Thanks a bundle @Flarna
It is working like a charm now

@Flarna
Any help on Approach # 2 , utilizing context.with
doSomeWorkInNewNestedSpan should be parent of doSomeWorkInNewNested2Span
const doSomeWorkInNewNestedSpan = (parentSpan) => {

    const ctx = setSpan(context.active(), parentSpan);
    const childSpan = tracer.startSpan('doSomeWorkInNewNestedSpan', {
        parentSpan, attributes: { 'code.function' : 'doSomeWorkInNewNestedSpan' }
    }, ctx);

    childSpan.setAttribute('code.filepath', "test2");
    //Do some work
    doSomeHeavyWork();
    doSomeWorkInNewNested2Span(childSpan);
    childSpan.end();
}

const doSomeWorkInNewNested2Span = (parentSpan) => {
    const childSpan = tracer.startSpan('doSomeWorkInNewNested2Span');
    context.with(setSpan(context.active(), childSpan), () => {
        logger.info('Client traceId %s:%s', childSpan.context().traceId, childSpan.context().spanId);
        childSpan.end();
    });
}

That is not the care write now

Try context.with(api.setSpan(api.context.active(), span), doSomeWorkInNewNested2Span);.

Thanks a bundle @Flarna
Working like a charm now.
https://github.com/mnadeem/nodejs-opentelemetry-tempo This would be helpful for folks understanding Opentelemetry and using BabelJs and Grafana Tempo

We are discussing/working on a convenience API for this that will make this api.withSpan(span, doSomeWorkInNewNested2Span) which should make this less confusing for new users.
I am also working on a new documentation which should simplify these common use cases.

FWIW I'm a Node.js programmer of 10 years, spent an hour reading this thread and many others + docs, and still cant figure out how to make child span link properly to parent.

FWIW I'm a Node.js programmer of 10 years, spent an hour reading this thread and many others + docs, and still cant figure out how to do something as simple (or should be simple) as making a child span link properly to parent.

Any progress on this? Literally same here, some working code-snipped would help

What's wrong with this sample?

That is actually what I was looking for (and have basically since implemented).  Most of the examples I was seeing relied on the use of context.with which due to the nature of my code I could not use.  Thanks

Takeaway here I guess is to add documentation to the website


HBASE-28839: Handle all types of exceptions during retrieval of bucket-cache from persistence.

During the retrievel of bucket-cache from persistence, it was observed that, if an exception, other than the IOException occurs, the exception is not logged and also the retrieval thread exits leaving the bucket cache in an uninitialised state, leaving it unusable.
This change, enables the retrieval thread to peint all types of exceptions and also reinitialises the bucket cache and makes it reusable.
Unfortunately, the exception was seen due to a parallel execution of eviction during the execution persistence of backing map. Hence, this use-case may not be tested via a unit test.
Change-Id: I81b7f5fe06945702bbc59df96d054f95f03de499

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 26s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 24s

master passed

+1 :green_heart:
compile
3m  8s

master passed

+1 :green_heart:
checkstyle
0m 37s

master passed

+1 :green_heart:
spotbugs
1m 34s

master passed

+1 :green_heart:
spotless
0m 45s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 58s

the patch passed

+1 :green_heart:
compile
3m  3s

the patch passed

+1 :green_heart:
javac
3m  3s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 35s

the patch passed

+1 :green_heart:
spotbugs
1m 38s

the patch passed

+1 :green_heart:
hadoopcheck
11m  2s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

-1 :x:
spotless
0m 39s

patch has 23 errors when running spotless:check, run spotless:apply to fix.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  0s

the patch passed

+1 :green_heart:
compile
1m  0s

the patch passed

+1 :green_heart:
javac
1m  0s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed

+1 :green_heart:
shadedjars
5m 24s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
261m 58s

hbase-server in the patch passed.

287m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6250

JIRA Issue
HBASE-28839

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 0670fdd50f43 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 43cf0ad590393a2a03caad8fc3320c62ad98bb1d

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/1/testReport/

Max. process+thread count
4962 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 27s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m  5s

master passed

+1 :green_heart:
compile
3m  4s

master passed

+1 :green_heart:
checkstyle
0m 35s

master passed

+1 :green_heart:
spotbugs
1m 30s

master passed

+1 :green_heart:
spotless
0m 43s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 56s

the patch passed

+1 :green_heart:
compile
3m  1s

the patch passed

+1 :green_heart:
javac
3m  1s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 34s

the patch passed

+1 :green_heart:
spotbugs
1m 35s

the patch passed

+1 :green_heart:
hadoopcheck
10m 46s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 41s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s

The patch does not generate ASF License warnings.

35m 53s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6250

JIRA Issue
HBASE-28839

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux bf2096f482da 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / daa93dc1c617d0a4542c25bc67cdd639298ce74c

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
84 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/2/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

We should rather understand and solve the trigger, than put this bandaid here.
@wchevreuil , Unfortunately, since the exception gets missed and is not printed. Hence, hence, to understand this further, we need this change which will print the exception that is being missed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 17s

the patch passed

+1 :green_heart:
compile
1m 18s

the patch passed

+1 :green_heart:
javac
1m 18s

the patch passed

+1 :green_heart:
javadoc
0m 39s

the patch passed

+1 :green_heart:
shadedjars
7m  8s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
284m  7s

hbase-server in the patch passed.

315m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/2/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6250

JIRA Issue
HBASE-28839

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux c528b0b76d6e 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / daa93dc1c617d0a4542c25bc67cdd639298ce74c

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/2/testReport/

Max. process+thread count
5091 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 43s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 42s

master passed

+1 :green_heart:
compile
4m 27s

master passed

+1 :green_heart:
checkstyle
0m 55s

master passed

+1 :green_heart:
spotbugs
2m 20s

master passed

+1 :green_heart:
spotless
1m  8s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 52s

the patch passed

+1 :green_heart:
compile
4m 21s

the patch passed

+1 :green_heart:
javac
4m 21s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 48s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 1 new + 5 unchanged - 0 fixed = 6 total (was 5)

+1 :green_heart:
spotbugs
2m 27s

the patch passed

+1 :green_heart:
hadoopcheck
15m 43s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

-1 :x:
spotless
0m 48s

patch has 53 errors when running spotless:check, run spotless:apply to fix.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  4s

the patch passed

+1 :green_heart:
compile
0m 59s

the patch passed

+1 :green_heart:
javac
0m 59s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed

+1 :green_heart:
shadedjars
5m 22s

patch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m  8s

the patch passed

+1 :green_heart:
compile
1m 44s

the patch passed

+1 :green_heart:
javac
1m 44s

the patch passed

+1 :green_heart:
javadoc
0m 56s

the patch passed

+1 :green_heart:
shadedjars
9m 12s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
353m 24s

hbase-server in the patch passed.

391m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/5/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6250

JIRA Issue
HBASE-28839

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux e45e962ea747 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / c5275f0cf9d18946d5bc52cd90cd4ba2deef2a1b

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/5/testReport/

Max. process+thread count
4833 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/5/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 28s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m  8s

master passed

+1 :green_heart:
compile
3m 11s

master passed

+1 :green_heart:
checkstyle
0m 36s

master passed

+1 :green_heart:
spotbugs
1m 31s

master passed

+1 :green_heart:
spotless
0m 43s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  3s

the patch passed

+1 :green_heart:
compile
3m 12s

the patch passed

+1 :green_heart:
javac
3m 12s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 36s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 3 new + 5 unchanged - 0 fixed = 8 total (was 5)

+1 :green_heart:
spotbugs
1m 39s

the patch passed

+1 :green_heart:
hadoopcheck
11m 26s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

-1 :x:
spotless
0m 37s

patch has 45 errors when running spotless:check, run spotless:apply to fix.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  1s

the patch passed

+1 :green_heart:
compile
1m  0s

the patch passed

+1 :green_heart:
javac
1m  0s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed

+1 :green_heart:
shadedjars
5m 26s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
228m 18s

hbase-server in the patch passed.

253m 17s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/6/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6250

JIRA Issue
HBASE-28839

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 10505b58ba54 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 533b590080e2ce7f6860aab1f1b4c98c51bdb901

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/6/testReport/

Max. process+thread count
4900 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/6/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 29s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m  8s

master passed

+1 :green_heart:
compile
3m  6s

master passed

+1 :green_heart:
checkstyle
0m 35s

master passed

+1 :green_heart:
spotbugs
1m 33s

master passed

+1 :green_heart:
spotless
0m 44s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 55s

the patch passed

+1 :green_heart:
compile
3m  6s

the patch passed

+1 :green_heart:
javac
3m  6s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 35s

the patch passed

+1 :green_heart:
spotbugs
1m 36s

the patch passed

+1 :green_heart:
hadoopcheck
10m 48s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 42s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 13s

the patch passed

+1 :green_heart:
compile
1m  1s

the patch passed

+1 :green_heart:
javac
1m  1s

the patch passed

+1 :green_heart:
javadoc
0m 28s

the patch passed

+1 :green_heart:
shadedjars
5m 53s

patch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 12s

the patch passed

+1 :green_heart:
compile
1m  2s

the patch passed

+1 :green_heart:
javac
1m  2s

the patch passed

+1 :green_heart:
javadoc
0m 29s

the patch passed

+1 :green_heart:
shadedjars
5m 53s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
219m 52s

hbase-server in the patch passed.

245m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/8/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6250

JIRA Issue
HBASE-28839

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux cbcb8dc0e810 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 409554d3fa2a161780e0e209acacc8297ac8a24b

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/8/testReport/

Max. process+thread count
5266 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/8/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

Hi @wchevreuil, the failing test seems to have passed in the the rerun.
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6250/8/testReport/org.apache.hadoop.hbase.security/TestSecureIPC/
I have addressed your review comments. Please take a look.
Thanks,
Janardhan


Updated longestItem + tests

Description

In continuation of #711, here is the updated snippet and the additional tests that we need.
What does your PR belong to?

[ ] Website
[x] Snippets
[ ] General / Things regarding the repository (like CI Integration)
[x] Tests

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (non-breaking improvement of a snippet)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have checked that the changes are working properly
[x] I have checked that there isn't any PR doing the same
[x] I have read the CONTRIBUTING document.

From what I can tell it's working as intended


update django-cors

Update django-cors

With https://github.com/ome/omero-web/pull/359, cors-headers will no longer be required.

Merging and tagging 5.14.0
Webtagging and tagsearch have been removed for the time being since the app are not compatible with Django 3.2.x


Can't pipe infinite data to lolcat

With cat you can do this to get boring infinite white text:
cat /dev/random | base64 | cat

However, when doing the same with lolcat, it never shows any awesome rainbow colored output:
cat /dev/random | base64 | lolcat

I havethe same problem,

cat /dev/urandom | base64 | lolcat

doesn't work for me, no output.
This issue is closed, i just found it because I'm having troubles running another program in terminal, and getting awesome rainbow colored output while piping it through lolcat ...
why does it work for you, @m-o-e ?
Are there settings in terminal I have to adjust?!

There are certain versions of base64 that buffer all input before doing anything.
Does this one work for you: cat /dev/urandom | hexdump | lolcat ?

thank you for helping a newbie @m-o-e : )
this one works for me!
So I guess https://github.com/houeland/kolproxy from @houeland doesn't give me live-lolcat greatness, because of its "buffer design"?! It's a shame 🙈


Please Merge System Tray Patched , Useful for Multiple Apps with sys tray icon

I did a manual , patching on this .... Ive tested this to work on my machine...

I already said I don't want this and closed all the other issues and PRs you opened on this same topic.
When you already have an extensible status bar, there is no real point in adding a redundant extra status bar type, especially given that the entire point of dwm and well, all my dotfiles is a minimal system. Minimalist programs and those that embed themselves in system trays instead of closing when you tell them to close are totally non-overlapping. Not accommodating these programs is a feature.
I've seen many people run egregious programs in builds based on my system that make me wonder why they aren't just using GNOME. I don't care and am not bothered---people can do what they want, but I'm not going to add this huge feature into my own build because I know that I will never, ever benefit from it (but will probably be highly annoyed by it). It will also incentivize tinkerers to not thinker, and just look for system tray programs that could be replicated by either a line of shell script or that are just unnecessary.
I don't even mind the occasional PR that fixes some issue caused by some dumb idiosyncratic GUI program by adding environmental variables, but this is way beyond that. If people want the feature, they can use the patch or this branch. No way I'm adding this to the default build---I've been too lenient on feature bloat anyway.


Questions about Camera Intrinsics and mesh data

Thanks for your great work!
I have two questions:

How you get the Camera Intrinsics of wild datasets (e.g. COCO)

How you get the SMPL parameters of wild datasets, it seems that you just use h36m to supervise the Virtual Markers?

Hi, thank you for your interest, and sorry for the late reply.

For the COCO dataset, we use the annotations provided by I2L-MeshNet. They use SMPLify-X to get the pseudo-GT label including the camera parameters, and SMPL parameters, as mentioned here.  For other wild image inputs, we estimate the camera intrinsics according to the image size.

During the model training process, we use the official SMPL GT parameters provided by the H36M dataset and 3DPW dataset to supervise 3D virtual marker estimation. For the MPI-INF-3DHP dataset, SMPL GT labels were not provided, so we only use its 3D pose labels. The COCO dataset and UP-3D dataset are both 2D datasets and their pseudo-SMPL GT parameters are obtained by SMPLify-X and SMPLify, respectively. Since we find that these fitted meshes are not accurate, we only use the 2D projections and supervise the first two dimensions of the virtual marker estimation. We've detailed these datasets in the supplementary.


Ubuntu 16.04 / SR300 Installation Issues

Required Info

Camera Model
SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 16.04

Kernel Version (Linux Only)
4.4.0-24-generic #43-Ubuntu

Build System
Makefile

Hi,
On a fresh Ubuntu 16.04 installation, running the example programs I get the below screenshot. Depth and Infrared streams seem to be invalid. The depth window keeps flashing. I have a pretty good USB3 card, one of the industrial ones that has a separate controller behind each port. Any idea how to fix it?

Hi @alperaydemir -- these issues seem consistent with an issue in the patched uvcvideo driver. Can you re-run the patching script for 16.04 again (and make sure to sudo modprobe uvcvideo at the end).

@ddiakopoulos - I am seeing a similar issue using an F200 with the stock 16.04 kernel (4.4.0-24-generic #43-Ubuntu SMP). That camera seems to work fine with librealsense in windows 8.1.
Perhaps I'm misunderstanding the installation guide but the guide says:

For Ubuntu 16.04 -- No kernel patch is needed for the R200 camera
is this true for the other cameras as well?

Kernel in 16.04.xx
No action required. Ubuntu 16.04 beta2 and newer already contains the patch

What patch should be used?
FYI my camera is running Firmware version: <IP_ADDRESS>
and my kernel is 4.4.0-24-generic #43-Ubuntu SMP
here is some dmesg output
[  604.620170] usb 6-2.1: Product: Intel(R) RealSense(TM) 3D Camera (Front F200)
[  604.620172] usb 6-2.1: Manufacturer: Intel(R) RealSense(TM) 3D Camera (Front F200)
[  604.620175] usb 6-2.1: SerialNumber:<PHONE_NUMBER>07
[  604.623465] uvcvideo: Found UVC 1.10 device Intel(R) RealSense(TM) 3D Camera (Front F200) (8086:0a66)
[  604.626407] input: Intel(R) RealSense(TM) 3D Camer as /devices/pci0000:00/0000:00:03.0/0000:04:00.0/usb6/6-2/6-2.1/6-2.1:1.0/input/input18
[  604.627444] uvcvideo: Unknown video format 5a564e49-2d90-4a58-920b-773f1f2c556b
[  604.627450] uvcvideo: Unknown video format 495a4e49-1a66-a242-9065-d01814a8ef8a
[  604.627455] uvcvideo: Unknown video format 52564e49-2d90-4a58-920b-773f1f2c556b
[  604.627460] uvcvideo: Unknown video format 49524e49-2d90-4a58-920b-773f1f2c556b
[  604.627464] uvcvideo: Unknown video format 49564e49-57db-5e49-8e3f-f479532b946f
[  604.627469] uvcvideo: Unknown video format 494c4552-1314-f943-a75a-ee6bbf012e23
[  604.627777] uvcvideo: Found UVC 1.10 device Intel(R) RealSense(TM) 3D Camera (Front F200) (8086:0a66)
[  604.630329] uvcvideo: Unable to create debugfs 6-5 directory.
[  604.630591] input: Intel(R) RealSense(TM) 3D Camer as /devices/pci0000:00/0000:00:03.0/0000:04:00.0/usb6/6-2/6-2.1/6-2.1:1.2/input/input19
Thanks
Luke

so my issue was an unpatched uncvideo module. there is a patch file scripts/patch-uvcvideo-16.04.simple.sh which does that patching. Note that you will need to enable src repos in your /etc/apt/sources.list.

Hi @alperaydemir any update?

Hi, yes I confirm my issue is the same as @bloyl. The scripts somehow didn't patch the uvcvideo module and I used a pre-compiled version somebody in the office had, which seemed to do the trick.
The installation instructions are somewhat unclear since they say that no kernel update needed for 16.04 but this isn't my experience. I had to get the 4..4.0-040400 kernel.
Therefore I'm closing this issue but somebody should probably go through in the installation steps and verify what's wrong (or right) there.

Actually one step ahead of you @alperaydemir -- fixed in 9a00ba53458fd1a094aba3c600d5dafc71a4d927. The instructions were indeed wrong.

Installation.md now directs global installation of the UVC patch for 16.04.  My understanding was that SR300 required the uvc patch, but R200 did not - is this not correct?  Assuming it is correct would it not be better to note the UVC patch as a dependency for SR300 only?

Hi, what happens if you run the patch, will it have a negative impact on R200?

Ubuntu 16.04 cherrypicked the publicly available upstream patch for R200 camera, therefore no kernel patching is required for R200 camera.  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557138
The F200/SR300 cameras still require an additional patch regardless of OS. Maybe somebody would upstream those patches, also?

The F200/SR300 cameras still require an additional patch regardless of
OS. Maybe somebody would upstream those patches, also?

I guess I should probably be the one to do this? The patch in the scripts
directory has my comments so I'm actually an upstream author from Intel as
far as the F200 patch.

@mattcurfman yes, from that cherry-pick request, the R200 (ds4) patch will be available in 16.04 but it is not available as part of the current linux-lts-xenial package. The cherrypick exists in the Proposed branch (https://wiki.ubuntu.com/Testing/EnableProposed) and will not be available in the Updates branch until 16.04 LTS gets its first point release (16.04.1, on July 21st 2016 according to https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule)

Hi i have a really simple question, for your ubuntu 16.04 LTS, are you running it on virtual machine? I used the virtual box but ubuntu even didnt detect my sr300.


kafka: Remove old versions

Keeping latest two + latest 0.x and latest 1.x
Removed 0.9, 0.10, 1.0, 2.0

Motivation for this change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

From upstream:

What Is Our EOL Policy?
Given 3 releases a year and the fact that no one upgrades three times a year, we propose making sure (by testing!) that rolling upgrade can be done from each release in the past year (i.e. last 3 releases) to the latest version.
We will also attempt, as a community to do bugfix releases as needed for the last 3 releases.

Given the release dates of all these old versions, they should indeed be EOL.
@NeQuissimus maybe it needs a mention in 20.03 release note with a link to upstream documentation regarding upgrades ?
[http://kafka.apache.org/23/documentation.html#upgrade]

this needs a rebase

This should probably be merged into 20.03.

Is this ready to merge?

What would be needed to merge this ? If it is the alias thing, i can do. Same if this need a note in the changelog ? Let try to merge this for everyone sanity

What would be needed to merge this ? If it is the alias thing, i can do. Same if this need a note in the changelog ? Let try to merge this for everyone sanity

If you want to take this PR over. Just do something like here: https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/aliases.nix#L705

I am closing this as it is very stale. Somebody interested in removing old Kafka versions is welcome to submit a new PR.


GemFire blog g4k8s-basic-client switch from geode to gemfire

Switch from geode to gemfire (despite credential requirement) for the client

Hi @danielramirez0 , one more edit to this blog post following a request from management. 🤞 there won't be more 🙂


Adding Databricks Azure tokens (Bearer token) support. (Issue #121)

Issue #121 : Support Azure AD Tokens instead of PAT tokens
PAT vs Azure AD tokens - PAT tokens are workspace specific and usually have a long expiry. Azure AD tokens expire within a few hours and the same token will work across all workspaces with SSO enabled.
The NodeJS SQL driver was extended to support Azure AD tokens.
Description of change:

Introduces useAADToken in connection options.
When useAADToken=true, the PlainHTTPAuthentication class will send a Bearer authorization header with the Azure AD token, instead of the Basic authorization header when using a PAT token.
Unit tests extended for PlainHTTPAuthentication for Azure tokens.
E2E tests extended to support AAD Tokens

Workaround:
To use AAD token - you can tweak (@databricks/sql 1.1.1) as follows to use Azure AD tokens.
const { DBSQLClient, auth } = require('@databricks/sql');
// Patch to Databricks SQL driver to send Azure AD token as Bearer token.
Reflect.defineProperty(auth.PlainHttpAuthentication.prototype, 'getToken', {
  value: function () {
    return `Bearer ${this.password}`
  }
})

// Use normally - replacing token with your AAD token.

Submitted by:
Divya van Mahajan<EMAIL_ADDRESS>

Closed. Incorrect branch. Will resubmit.


Interpreter fails when trying to load CenterNet(Java API)

I have created an android example app and I am trying to run CenterNet(320x320, 512x512, 640x640).
When I run this model(trained):
centernet_320x320.zip in CPU works fine, but when I try to run with GPU Delegate I get the following error:
java.lang.RuntimeException: java.lang.IllegalArgumentException: Internal error: Failed to apply delegate: Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors.
When I run this two models(pre trained):
centernet_model_test_640x640.zip
centernet_model_test_512x512.zip
They work in CPU and GPU.
Now, when I try to run the same models in a Qualcomm device for better performance, for the first model I get the same behavior and for the two pre trained models when I run them in CPU they work(the output is good), but when I run the same model in QC GPU the output of the models is not correct. (its just weird when the same model in CPU gives good predictions and in GPU it gives really bad predictions)
    implementation 'org.tensorflow:tensorflow-lite:2.3.0'
    implementation 'org.tensorflow:tensorflow-lite-gpu:2.3.0'

I have tried with 2.3.0 , 2.4.0 and 2.5.0 and I get the same behavior.

in the centernet 320x320, you have bunch of subgraphs.  try to remove those.
i'm not really sure the centernet models run on the GPU as I see bunch of incompatible ops.  do you have any logs?

Hi @impjdi,
The two pre trained models (512x512, and 640x640) in the first device (RK chip) worked on GPU, I am assuming this because the interpreter time dropped almost by 50% (from 1.2 seconds/frame to 0.6 seconds/frame) and the output was correct.
But when I change the device(Qualcomm) interpreter time drops but the output is not correct.
The only change here is the GPU of the device :/
I can't find any useful logs because there isn't any warning or crashes of interpreter.

Hi @ArtanBerisha1! Have you checked these thread yet ?


Update Site users page

There's currently a Site users page (/site_users) that I believe is only accessible to POD Admins. Below is a suggested redesign for this page.

[ ] A: The topbar navigation link "Users" should only be visible to superusers/POD Admins (this might already be the current behavior).
[ ] B: Rename the page heading to "Manage users" from its current "Site users"
[ ] The main updates in this issue are with this table, primarily adding/rearranging columns. Note that there is a related issue (#539 and #578) for the Organization users page, which includes a similar table. Since that work appears to be largely done, we might want to borrow the updated table code from that issue (not only to make development more efficient but to ensure the user seems a consistent pattern for managing users in both places). There are some differences in the two tables, though.
[ ] C: The current Site users table shows, in the first column, the user's name if it exists, otherwise the user's email address. I'm suggesting we break those into two distinct columns. Email address is required, so the first column always contains that. If the user provided a name, that goes in the second column, otherwise it is blank. The value in the first column can continue to be a mailto: link.
[ ] The current table shows, in the first column, the user's job title if it exists, in parenthesis. I suggest we drop that from this table (it is still visible in the Organization users page, where it might have more value).
[ ] D: Add a new column Organization. Link the organization value to the default tab/page of that organization's "Manage organization" page (see #539).
[ ] E: The current Site users table includes a final column that has buttons that either promote or demote a user from the POD admin role. This Superuser? column is intended to do the same thing, but using a checkbox/toggle instead of a button.
[ ] F: When we change the buttons to checkboxes in the Superuser? column, I think we might need to submit any changes to the checkbox, rather than that action taking place immediately. Assuming that's true, add a submit button with the label Update users.

For consistency with the internal role names, let's refer to the admin role as "POD Admin" in the UI (instead of of superuser).

@corylown does this mean we should also refer to the org admin role as "Org owner"?

nvm, saw your comment on #578

@ggeisler since there's no "remove user" button here, does that mean:

the only place to get rid of a user account is on an organization's users page
clicking the "remove user" button on the organization users page doesn't just remove the association between that user and the organization — it deletes the account entirely

@thatbudakguy

the only place to get rid of a user account is on an organization's users page

Yep. I originally had it on the site users page, but I'm not sure it's a good idea to offer the same feature in two places within the application. It likely just leads to someone getting confused over whether they are different somehow. And since a user must belong to one and only one organization, removing the user on the organization users page feels like the most direct place to do it; otherwise an org admin who is not a POD admin would have to ask a POD admin to remove the user from their organization.

clicking the "remove user" button on the organization users page doesn't just remove the association between that user and the organization — it deletes the account entirely

Right, the user belongs to that organization and only that organization and the org admin has decided to remove that user, so they are removed from POD entirely. The only downside of that I see is if an existing POD user is switching organizations, but that seems like a rare enough case that removing them from POD and then inviting back to POD to their new organization is not unreasonable. (This wouldn't be as reasonable if we kept track of user-specific activity data or preferences, but we don't.)
But let me know if either of those answers doesn't make sense to you.


Test hydration modes

Shows why https://github.com/phpstan/phpstan-doctrine/pull/588 should be merged
Supersedes https://github.com/phpstan/phpstan-doctrine/pull/587

Thank you.


refactor: how to represent parameters in genesis

I would like for parameters to look like this:
  "parameters": [
    {
      "sumeragi": {
        "block_time_ms": 2000
        "commit_time_ms": 4000
      }
    },
    {
      "block": {
        "max_transactions": 512
      }
    },
    {
      "transaction": {
        "max_instructions": 4096
        "smart_contract_size": 4194304
      }
    },
    {
      "executor": {
        "fuel": 55000000
        "memory": 55000000
      }
    },
    {
      "smart_contract": {
        "fuel": 55000000
        "memory": 55000000
      }
    }

Originally posted by @mversic in https://github.com/hyperledger/iroha/pull/4812#discussion_r1668502409

@Erigara Just to ensure, is this referring to data_model::parameter module?

in genesis/src.lib.rs

Is it going to be reflected in the schema somehow? Would be great to see a proposal for that before merging the change.

Is it going to be reflected in the schema somehow? Would be great to see a proposal for that before merging the change.

Yes, there is type RawGenesisTransaction in the schema, it will be changed accordingly (https://github.com/hyperledger/iroha/pull/5020/files#r1736862760)


Page revalidation seems to be broken/add support for revalidation of globals

Currently the page revalidation doesn't work for some reason.

Fixed in #160


Testing oppiabot reacting to template

Overview

This PR fixes or fixes part of #[fill_in_number_here].
This PR does the following: This is a simple PR.

Essential Checklist

[ ] The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
[x] The linter/Karma presubmit checks have passed locally on your machine.
[ ] "Allow edits from maintainers" is checked. (See here for instructions on how to enable it.)

This lets reviewers restart your CircleCI tests for you.

[ ] The PR is made from a branch that's not called "develop".

PR Pointers

Oppiabot will notify you when you don't add a PR_CHANGELOG label. If you are unable to do so, please @-mention a code owner (who will be in the Reviewers list), or ask on Gitter.
For what code owners will expect, see the Code Owner's wiki page.
Make sure your PR follows conventions in the style guide, otherwise this will lead to review delays
Never force push. If you do, your PR will be closed.

Adding a description

Checking the linter and karma checklist.

Checking the allow maintainers to edit checklist.

No comment from oppiabot since the required items are checked.


Hugo Module Imports: Allow version reference in module config.

The problem
For now it is not possible for a Hugo Module to enforce a version for its imports from its config.yaml.
# currentmodule/config.yaml
module:
  imports:
  - path: github.com/whodat/hugo-anothermodule

Which means, any Hugo projects importing currentModule will end up with the latest version of anotherModule unless they manipulate the go.mod file with hugo mod get -u or by hand.
Which means, the maintainers of currentModule have no way, unless through documentation, to ensure their users are using the right, tested, validated version of anotherModule.
Currently
Current behaviour imports the latest version of any module whose path is added to the module.imports array and records it on the upmost project's go.mod require statements.
Proposal
I think we could add another key "version" the the imports entries which could now only support latest or a string matching a symver tag/release.
(Other variations, like >1.0.2 <=2.3.4 or 3.3.x would be welcome but really not that important at the moment.)
# currentmodule/config.yaml
module:
  imports:
  - path: github.com/whodat/hugo-anothermodule
    version: v0.1.3

# hugo-website/config.yaml
module:
  imports:
  - path: github.com/thatteam/hugo-currentmodule
    version: latest

So, when we do the validation in Hugo, we know the running version (e.g. v0.72.0), but we have no current way of checking if that is the "latest" without "looking it up" from somewhere (e.g. GitHub).

if that is the "latest" without "looking it up" from somewhere

I assumed latest would essentially be the current behaviour, with seemed to me to fetch the latest release or latest master's head if no release/tag found.

OK, I totally misunderstood what this was all about.
There are some issues with this, though, which makes it tricky:

go.mod will always be the holder of the version information.
This means that config.toml and go.mod can easily go out of sync.
Also, if set to latest, that would mean that we would have to do a update check for those every time hugo is run.

As to 3) I just added that as "info", I don't see a real problem with it, I guess many would want that behaviour. But 1 and 2 are real problems.

Yes I understand.

Somewhat related, not worth opening a separate issue:
The compatibility warning message
is not really helpful. It does not point to the module that causes the issue. If e.g. one module in the dependency graph requires hugo extended, there is no easy way to figure out the module that causes the warning.
Apart from that -- the required new feature would potentially raise the same "dependency hell issues" we observe in the npm ecosystem. Maybe it would be best to just stick with "latest by default". This could help to foster a hugo module ecosystem that does not run into the very same problems (scores of stale/orphaned dependencies) because everybody would be forced to get their stuff up-to-date and/or contribute to upstream to keep these up-to-date.


[SAS-67] Add date_joined field to admin email export

This field is required for the Girl Effect dashboard.

Thanks! Somebody once told me about applying the the scouts rule of leaving the campsite cleaner than you found it to code and I think that's a nice analogy :)


[F] Fix clicking lollipop multiple times is allowed during request

https://t.me/c/1656800117/302

That’s a great job! Thank you!!


React mixin clone error

Hi guys, I'm using this wonderful library but I'm having some issues with the group clone option.
This is an excerpt from the code:
var CouponList = React.createClass({
  mixins: [SortableMixin],

  sortableOptions: {
    group: {
      name: 'organize',
      pull: 'clone'
    },
    animation: 200,
    ghostClass: 'sortable-ghost'
  },
});

and
var BookCategoryDiscounts = React.createClass({
  mixins: [SortableMixin],

  sortableOptions: {
    group: 'organize',
    animation: 200,
    ghostClass: 'sortable-ghost',
    filter: '.btn-danger'
  },
});

After dropping an item from the first list into the second one I get this:
Uncaught Error: Invariant Violation: ReactMount: Two valid but unequal nodes with the same `data-reactid`:

this is because there are 2 duplicate items in the first list (same data-reactid) and of course the 'cloned' item in the second..
Sorry I'm newbie, what am I doing wrong?

You are not a newbie. This reaction wasn't considered by making the mixin, i think. I will take a look at it, maybe it is fixed easily.

Thank you @ChiefORZ, that would help me a lot!

Create example on jsbin.com (draft)

here you go http://jsbin.com/vaqolejixi/edit?js,output

Dear all! Meteor is moved to the separate repository. If this issue is still actual, please create it there once again and this rojects needs a maintainer:

ES2015+: https://github.com/SortableJS/react-sortablejs 🆘
mixin: https://github.com/SortableJS/react-mixin-sortablejs


identify students with multiple submissions

To help identify students with multiple submissions, two print statements are added in assignments/models.py:
1.) When syncing submissions
2.) When uploading submissions to canvas.
Example terminal output for such a student:
"*Multiple submissions found in database for student with canvas_id: John Doe"

Looks good!


afterEach conditional error hook breaks stats and error reporting

Prerequisites

[x] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
[x] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
[x] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[x] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend avoiding the use of globally installed Mocha.

Description
Trying to fail a test with this.test.error() causes the test to be reported twice, as failed and as success
Steps to Reproduce
Run the test at:
https://github.com/mochajs/mocha/wiki/HOW-TO:-Conditionally-fail-a-test-after-completion
Expected behavior:
  something
    ✓ should one
    1) should two

  1 passing (16ms)
  1 failing

Actual behavior:
  something
    ✓ should one
    ✓ should two
    1) should two

  2 passing (11ms)
  1 failing

Additional information
There seems to be a fix in this rejected pull request
https://github.com/mochajs/mocha/pull/1944
Related to issue #1635

Hello! Can you please reopen this, since #3362 was reverted? I am still facing this issue.

By the way, the same problem happens with beforeEach:
beforeEach(function() {
	try {
		assert.strictEqual(true, false);
	} catch (err) {
	 	this.test.error(err);
	}
});

it('foobar', function() {
	assert.strictEqual(true, true);
});

Output:
      1) foobar
      √ foobar


Network tools not kicking players

nt_minplayercount set to 23

I fixed this already but I can't push my changes @leighmacdonald

Why do I have to open a pull request for peer review to change a setting?


Add documentation for NetlinkTimeout Felix config param.

Description

Documentation for the new NetlinkTimeout flag introduced by https://github.com/projectcalico/felix/pull/1526.
(Shouldn't be merged until after the above PR is merged.)
Todos

[x] Tests (N/A)
[x] Documentation
[x] Release note

Release Note

None required

LGTM!

@bcreane @fasaxc @neiljerram Is this OK to merge then?

OK great, thanks @bcreane . 👍  @fasaxc can you port these changes to the 2.6 directory and squash your commits? Would be good to merge this. Thanks!


[Bug] If you hide ALL LLMs using the pop-up panel, the interface goes completely blank with no way to regain control

Describe the bug
Hide all LLMs in pop-up menu and the UI goes completely blank with no access to controls to bring anything back. I'm going to have to uninstall/reinstall
To Reproduce
Hide all LLMs in pop-up menu
Expected behavior
with no LLMs selected, I expect to at least have a control to reinstate the LLMs
Screenshots
not helpful, just a blank white square
Desktop (please complete the following information):

OS: Windows 11
GodMode Version: 1.0.0-beta.9

Additional context
none

ouch! will take a PR to add a check. in the meantime you can reset it with cmd+shift+A!


High CPU usage on windows desktop

I'm running the vanilla flutter-desktop-embedding demo app (the counter) on windows.
CPU utilization hovers around 33% but occasionally shoots up to over 40%. For a trivial app that's idling this seems pretty high. Is there any way to reduce this?

This is a duplicate of #30730


Horizontal and vertical item spacing

I separated the item spacing into horizontal and vertical to allow for better layout customization.

I created separate properties because I don't think of the spacing as a size and didn't want to overload CGSize to mean something else. But if people prefer it as CGSize I'll change it.
Also, as I've been playing with the spacing I think I want to change it based on portrait or landscape. The margins as well. I'm currently abusing GMGridView:sizeForItemsInInterfaceOrientation: to change these settings but maybe there should be a separate delegate call for that. And I'm not sure if it should be the data source delegate so a new layout delegate? Any preferences? Or is that the correct place to change things.


MM-34718: fix incident welcome when filtering

Summary
When the incident list loads, check for incidents without filtering to reliably decide when to show the welcome screen.
(master is failing spuriously right now, but the specific test in question passes locally for me.)
Ticket Link
Fixes: https://mattermost.atlassian.net/browse/MM-34718

/update-branch

/update-branch

Error trying to update the PR.
Please do it manually.

/update-branch


How to get connected Socket's Id?

Cant seem to find socket's Id when its connected e,g on web client:

but same doesnt work using this library:

On reconnection, socket stops sending data due to some reason so matching the Id on game & server is needed to check whats happening.

Any idea how to get id ?


[BUG] - Serializer problem for constant pulse

Describe the bug
If there is constant pulse in the experiment, serializer cannot deserialise the compiled experiment properly. It will return an error __init__() missing 1 required positional argument: 'mixer_type'
The error is expected to be the consequence of release 1.3, although we are testing in 1.4
To Reproduce
Steps to reproduce the behavior:

Define pulse sequence...
Execute on hardware / in emulation ...
Do additional steps...
See error

run the following notebook in the laboneq example folder. it is modified from basic experiment
serializer_error.zip
Expected behavior
A clear and concise description of what you expected to happen.
Code & Screenshots
If possible, add example code or serialized LabOne Q data objects, like the Experiment and DeviceSetup, that allow us to reproduce the behavior.
If applicable, add screenshots to help explain your problem.
Versions used:

laboneq 1.4
zhinst-core 22.8
others

Context

[ ] Do you know a workaround for the issue? If yes, please provide a short description.
[x] Does the issue block your experiments?

If the compiled experiment does not go through the serializer, there won't be an error

Hi Yuan, thanks for reporting, looking at fixing this ASAP.

does this mixer_type for pulse should be considered when we define the experiment, or this should be handled by laboneq? I did not see any instructions/examples for this.

fixed in 1.5, closing this issue