How to use gt center or gt extreme and so on for testing?

In the bottom of table 1, it shows the performance of testing with gt center and gt extreme and so on. How to implement that in your code?

Hi,
Thanks for your interests in our work. My implementation is a little bit hacky and I haven't included it in this repo. You will need to modify many files. Basically, you will need to pass flags in test/coco_extreme.py and nnet/py_factory and call a new forward pass in models/py_utils/exkp.py like the following (not cleaned-up version):
    def gt_validate(self, xs, targets, **kwargs):
        image = xs[0]
        gt_t_heat = targets[0]
        gt_l_heat = targets[1]
        gt_b_heat = targets[2]
        gt_r_heat = targets[3]
        gt_ct_heat = targets[4]
        gt_t_regr = targets[5]
        gt_l_regr = targets[6]
        gt_b_regr = targets[7]
        gt_r_regr = targets[8]

        inter = self.pre(image)
        outs  = []

        layers = zip(
            self.kps, self.cnvs,
            self.t_heats, self.l_heats, self.b_heats, self.r_heats,
            self.ct_heats,
            self.t_regrs, self.l_regrs, self.b_regrs, self.r_regrs,
            self.ct_regrs
        )
        for ind, layer in enumerate(layers):
            kp_, cnv_                          = layer[0:2]
            t_heat_, l_heat_, b_heat_, r_heat_ = layer[2:6]
            ct_heat_                           = layer[6]
            t_regr_, l_regr_, b_regr_, r_regr_ = layer[7:11]
            ct_regr_                           = layer[11]

            kp  = kp_(inter)
            cnv = cnv_(kp)

            if ind == self.nstack - 1:
                t_heat, l_heat = t_heat_(cnv), l_heat_(cnv)
                b_heat, r_heat = b_heat_(cnv), r_heat_(cnv)
                ct_heat        = ct_heat_(cnv)

                t_regr, l_regr = t_regr_(cnv), l_regr_(cnv)
                b_regr, r_regr = b_regr_(cnv), r_regr_(cnv)
                ct_regr        = ct_regr_(cnv)

                # outs += [t_heat, l_heat, b_heat, r_heat, ct_heat,
                #          t_regr, l_regr, b_regr, r_regr, ct_regr]
                # outs += [gt_t_heat, gt_l_heat, gt_b_heat, gt_r_heat, ct_heat,
                #          t_regr, l_regr, b_regr, r_regr, ct_regr]
                # outs += [t_heat, l_heat, b_heat, r_heat, gt_ct_heat,
                #          t_regr, l_regr, b_regr, r_regr, ct_regr]
                # outs += [gt_t_heat, gt_l_heat, gt_b_heat, gt_r_heat, gt_ct_heat,
                #          t_regr, l_regr, b_regr, r_regr, ct_regr]
                outs += [gt_t_heat, gt_l_heat, gt_b_heat, gt_r_heat, gt_ct_heat,
                         gt_t_regr, gt_l_regr, gt_b_regr, gt_r_regr, None]
                if DEBUG:
                    _debug(image, outs[0], outs[1], outs[2], outs[3], outs[4])
                    #  _debug_regr(image, t_regr, l_regr, b_regr, r_regr, ct_regr)

            if ind < self.nstack - 1:
                inter = self.inters_[ind](inter) + self.cnvs_[ind](cnv)
                inter = self.relu(inter)
                inter = self.inters[ind](inter)

        return self._decode(*outs[-10:], **kwargs), None

Thanks for your reply.
By the way, I think my neg_loss implement is faster than yours:
def _neg_loss(preds, gt):

    pos_inds = gt.eq(1).float()
    neg_inds = gt.lt(1).float()
    num_pos  = pos_inds.float().sum()
    neg_weights = torch.pow(1 - gt, 4)

    loss = 0
    for pred in preds:
        trans_pred = pred * neg_inds + (1 - pred) * pos_inds
        weight = neg_weights * neg_inds + pos_inds
        all_loss = torch.log(1 - trans_pred) * torch.pow(trans_pred, 2) * weight
        all_loss = all_loss.sum()

        if num_pos > 0:
            all_loss /= num_pos

        loss -=  all_loss
    return loss

Hi,
Thanks very much for the feedback of the focal loss implementation. It can be extremely helpful to this project. However, according to my test, it is not significantly faster than my original implementation (<1%). How faster is it in your environment?

Well, I test it with original CornerNet code. My code is:
def _neg_loss(preds, gt):
    pos_inds = gt.ge(1.).float()
    neg_inds = gt.lt(1.).float()

    num_pos  = pos_inds.float().sum()
    neg_weights = torch.pow(1 - gt, 4)

    loss = 0
    for pred in preds:
        st = time.time()

        trans_pred = pred * neg_inds + (1 - pred) * pos_inds
        weight = neg_weights * neg_inds + pos_inds
        all_loss = torch.log(1 - trans_pred) * torch.pow(trans_pred, 2) * weight
        all_loss = all_loss.sum()

        if num_pos > 0:
            all_loss /= num_pos
        print('  my neg_loss : {}, using time: {}.'.format(all_loss, time.time() - st))

        st = time.time()

        pos_loss = torch.log(pred) * torch.pow(1 - pred, 2) * pos_inds
        neg_loss = torch.log(1 - pred) * torch.pow(pred, 2) * neg_weights * neg_inds

        pos_loss = pos_loss.sum()
        neg_loss = neg_loss.sum()

        all_loss = pos_loss + neg_loss
        if num_pos > 0:
            all_loss = all_loss / num_pos

        print('your neg_loss : {}, using time: {}.\n'.format(all_loss, time.time() - st))

        loss -=  all_loss
    return loss

And the results are:

I think it's slightly faster than your implementation. Maybe not significantly, but it must be faster.

Thank you for your reminding. I add torch.cuda.synchronize() before print:
    torch.cuda.synchronize()
    print('  my neg_loss : {}, using time: {}.'.format(all_loss, time.time() - st))

    torch.cuda.synchronize()
    print('your neg_loss : {}, using time: {}.\n'.format(all_loss, time.time() - st))

And results are:


Use different endpoints

Checked that this libs s3 endpoint is
s3.amazonaws.com
Following this document,
http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region
needs to be set differently depending on the region.

Interesting, will take a look. Thanks

+1

this can now be closed https://github.com/benjreinhart/react-native-aws3/pull/20

Yep, I'll close it when the next version is released, which should be in a bit


Multiple inputs with the same name bug

When you have multiple input fields with the same name, like radio buttons for example, you are getting one ngModel controller for each input. But, when you addressing this field by name, like this: formName.fieldName, you are getting a reference to the last ngModel controller.
The problem is that this controllers doesn't know about each other and do not coordinate their state. And from the user perspective they must have a shared state.
>> The bug is illustrated here <<
In the provided example, I'm trying to detect pristine state of the gender radio field, but I'm getting incorrect result, since I'm getting pristine state not of the entire radio group but only of the last radio button in the group.
From the end-user perspective this can be considered a real bug.
As a solution to this problem, maybe we should use a single ngModel controller for all inputs with the same name, or probably better, to synchronize the state of ngModels from the same group, so properties like $pristine would be consistent.

Do you know what? I think what we need to do is implement a ngRadioGroup directive. The problem is that ngModel is supposed to map one-to-one with a form field but that radio buttons don't constitute a single field in a form but part of a field.  A single radio button on its own has no real meaning.
Let's implement ngRadioGroup for 1.5 - any thoughts?

I'm not a big fan of radioGroup directives or contructs in general, because they don't go along well with how HTML works. Coul we cook up something that does the grouping internally? Or exposes an extra radioGroup controller?


ArrayHelper::getValue does not throw as documented

What steps will reproduce the problem?
var_dump(\yii\helpers\ArrayHelper::getValue('test', 'someProp', 123));

What is the expected result?
InvalidParamException thrown.
What do you get instead?
No exception, output: 123.
Yii version: 2.0.10
    /**
     * Retrieves the value of an array element or object property with the given key or property name.
     * ...
     * @param array|object $array array or object to extract value from
     * ...
     * @throws InvalidParamException if $array is neither an array nor an object.
     */
    public static function getValue($array, $key, $default = null)

confirmed.
This method should throw an exception when the $key does not exist in the object / array (shown by the corresponding tests)

Current behavior would return the fedault value instead if an exception

My bad, missread the issue.

should throw an exception when the $key does not exist in the object / array (shown by the corresponding tests)

Does not sound right to me and not found in tests.

@SilverFire
What is the rationale for not erroring out when first argument is neither array nor an object? IMO when this method is called like this it means something not right and it is better if it manifests with error than silently works in a way that does not really makes sense.

Erroring for non-array will break BC for cases, when $array is null, for example.

Does not sound right to me and not found in tests.

https://github.com/yiisoft/yii2/blob/master/tests/framework/helpers/ArrayHelperTest.php#L719
https://github.com/yiisoft/yii2/blob/master/tests/framework/helpers/ArrayHelperTest.php#L729

It's an error thrown by object of Post1 class as a result of access to property that does not exist

it was added in 9e66e08bc7ee3480504418f011150a76c94b9782 (#802) not sure why. seems accidentally added.

it was added in  9e66e08  (#802) not sure why. seems accidentally added.

Judging by that diff you might as well say that
 } else {
    return $default;
}

was added accidentally at the end of getValue() function. Notice how original version of getValue() from that diff while not throwing exception would still error out (with PHP error) when first argument is neither array nor object.
Currently, getValue() is documented as follows:
@param array|object $array array or object to extract value from

When doing coding according to documentation, you cannot call getValue(123, 'test', 'default') and expect it to return 'default'.
Documentation aside, I highly doubt that in existing code like:
getValue($somevar, 'test', 'default');

the author of the code actually EXPECTED to get 'default' when $somevar is null, integer or alike. I highly doubt that in existing places using getValue() it would make any sense for the first argument to be anything other than array or object. Again, IMO it is better to error out saying "hey, look, $array is invalid so there might be something wrong in the code where the value of $array has originated from" rather than silently ignoring the problem as if nothing happened.
As for the BC breaking. First, it is yet has to be proven that any code in Yii relies on getValue(123, 'test', 'default') returning 'default' (and even if there is such code it should be analyzed and fixed accordingly). Second, if the user code relied on such behavior of getValue() it was written in violation of getValue() documentation and you cannot talk about backwards compatibility with such code.

Digging into this again I found that the last return $default; is not added by accident but is valid for retrieval of nested items, e.g. getValue($array, 'test.name', 'default'); should return 'default' if the key test does not exist but also if name does not exist in test. However this allows weird things like:
$array = [];
getValue($array, 'test.name', ['name' => 'hi']); // returns "hi"

I think this should be refactored and tested better in 2.1.

e963b2a broke BC, now we can't use null (which is often used) as 1st argument. I think this is not a correct way

@filipchuk this change is already considered as BC breaking, thank you for confirmation.
Related: https://github.com/yiisoft/yii2/issues/13248

@SilverFire Thank you for quick reaction!

You're welcome


Use full path in all macro usage of Result

Apparently when someone uses a custom Result type and then uses some of these macros, they can get type conflict errors.
(Thanks @josibake for finding this using the sha256t_hash_newtype macro.)

utACK https://github.com/rust-bitcoin/rust-bitcoin/pull/2355/commits/aa6e5cd3424e2055fa3d083846a11c554fbcb732
Thanks for the quick fix! I'll try to test this later and verify it fixes the issue I was having

Also concept ACK backporting if needed.

@stevenroose @apoelstra tested your change and was still having the issue; found the offender in hashes/src/utils.cpp and added the following line:
https://github.com/josibake/rust-bitcoin/commit/c01dcff378995e5fd363a6d1cef75cad2c128353
Once I added that commit on top of yours, works like a charm! I noticed there are quite a few other places where macro rules are defined (just grepped for macro_rules! and I suspect this same issue will pop up in those places as well, but that's a much bigger refactor.

@josibake oh, oops!
Can you open a new PR with this extra commit?

@apoelstra yep! I went ahead and added absolute paths to (hopefully!) all the macros here: https://github.com/rust-bitcoin/rust-bitcoin/pull/2356

Oh nice, I'd never thought of this. It almost needs to be a crate wide policy for all public macros, or even a hard personal rule for all Rust devs.

I always do it but occasionally some slip through.

I always think to do it, but usually get lazy and think "welll this macro will only be used locally" and then later I make it public.
I think we should make it a written policy in this crate.

Oh, I've never once thought about Result clashing - my bad it would seem then. Lesson learned.


Build compose, isStamp, isComposable to the module root

This allows require('stampit/compose'), require('stampit/isStamp'), require('stampit/isComposable').

Grammatically, it should be 'all ... create', not 'all ... creates'
On 2016-09-20 10:38, Daniel K. wrote:

@FredyC requested changes on this pull request.

In docs/API.md
https://github.com/stampit-org/stampit/pull/233#pullrequestreview-760301:

Chaining methods
-Chaining stamps always creates new stamps.
+All the methods always create new stamps.
"All these methods /always/ creates new stamps." ... not sure why
you've removed "s", but that was correct actually ;)

In docs/API.md
https://github.com/stampit-org/stampit/pull/233#pullrequestreview-760301:

-const MyStamp = stampit()
-.methods({
+const MyStamp = stampit() // new stamp
+.methods({ // new stamp

I would say "creates new stamp" at least, otherwise it might look
confusing for people looking at examples first.

------------------------------------------------------------------------

In docs/API.md
<https://github.com/stampit-org/stampit/pull/233#pullrequestreview-760301>:

> @@ -526,14 +547,16 @@ const obj = stampit()
  bar: 'bar'
})
.compose(concreteStamp, additionalStamp, utilityStamp)
-.create();
+.create(42, 511, 3.14);

Uhh, how these number are helping to explain anything? Since there is
no reference to these in the example, it's just bogus and useless here ;)

------------------------------------------------------------------------

In docs/API.md
<https://github.com/stampit-org/stampit/pull/233#pullrequestreview-760301>:

>    * `import {statics} from 'stampit'`
  * `const {statics} = require('stampit')`
-* New utility function `isComposalbe`. Can be imported in any of the above ways.
-* New methods on stamps, as well as new shortcut methods on stampit, as well as new options to `stampit()`: `initializers`, `properties`, `deepProps`, `deepProperties`, `deepStatics`, `conf`, `configuration`, `deepConf`, `deepConfiguration`, `propertyDescriptors`, `staticPropertyDescriptors`
+* New utility function `isComposalbe`. Can be imported separately: `require('stampit/isComposable')`.

Typo: isComposable ;)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/stampit-org/stampit/pull/233#pullrequestreview-760301>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKTA1_doprtRtGqGixWsNYK4aGUAqvToks5qr-_agaJpZM4KBlat>.

--

@dpatte Ok, thanks for correction.

Pushed few more minorish changes. Will merge that in few hours if no reviewers come.


Make uptime generation optional

I'd like my benchmark tool to create the exact number of packets it says it will; the extra uptime thing is not necesarry for what I'm doing, so I added an option to turn it off.
Testing
Without -uptimeenable we send exactly 1 message per batch
[csibbitt@laptop telemetry-bench (csibbitt-make-uptime-optional) ]$ ./telemetry-bench -hostprefix test054- -hosts 1 -plugins 1 -instances 1 -verbose -timepermesgs 1 -send 2 -interval 1 amqp://localhost:5672/collectd/telemetry/
Send 1 metrics every 1 second(s)Total sent (0)0, total 0, 0 ack'd
Generated 1 metrics in 310.856µs
(0): Sent 1 metrics in 762.978582ms, ( 762978.582 uS per metric )
Total sent (0)1, total 1, 1 ack'd
Generated 1 metrics in 215.545µs
(0): Sent 1 metrics in 77.173µs, ( 77.173 uS per metric )
done...

With -uptimeenable we send 2 messages per batch
[csibbitt@laptop telemetry-bench (csibbitt-make-uptime-optional) ]$ ./telemetry-bench -hostprefix test055- -hosts 1 -plugins 1 -instances 1 -verbose -timepermesgs 1 -send 2 -interval 1 -uptimeenable amqp://local
host:5672/collectd/telemetry/
Send 1 metrics every 1 second(s)Total sent (0)0, total 0, 0 ack'd
Generated 2 metrics in 666.808µs
(0): Sent 1 metrics in 781.763239ms, ( 781763.239 uS per metric )
(0): Sent 1 metrics in 388.377µs, ( 388.377 uS per metric )
Total sent (0)2, total 2, 2 ack'd
Generated 2 metrics in 290.356µs
(0): Sent 1 metrics in 78.575µs, ( 78.575 uS per metric )
(0): Sent 1 metrics in 263.718µs, ( 263.718 uS per metric )
done...

I checked in prometheus, and in the second case I see the uptime metric, whereas in the first case I don't.

This will conflict with my other PR #8 . It will be easiest to merge that one first I think.

 Fixes to telemetry-bench for use in perf testing


Import.meta doesn't work on TS

What should I do??

import.meta only works in ESM. With your current setup, you already have __dirname available.

real

import.meta only works in ESM. With your current setup, you already have __dirname available.

my man


Refactor worker implementations around a CRUD interface

This should be enough to cover what's needed for #6.
I defined a CRUD behaviour on all workers, and then pulled everything out which could be. The advantage is that TTL is checked in a single place only (bar take/3 in local.ex). It also cuts down on a fair amount of duplication.
This PR will also catch #10 and make it far easier to implement #11.

Coverage remained the same at 100.0% when pulling 4b6aeb2454a20caa9730ec79065dc8d8c3fc2f19 on issue-6 into 9443af441e81916f59d640f805e843739532896f on master.

Coverage remained the same at 100.0% when pulling c10c22dc1646865758da875ccb3d0b362a70af1d on issue-6 into 9443af441e81916f59d640f805e843739532896f on master.

Coverage remained the same at 100.0% when pulling eefc9b16f804a8a275afce2f09aa0170396c2346 on issue-6 into 9443af441e81916f59d640f805e843739532896f on master.


History changes

Pull request closed. Another pull request submitted with the commits squashed and with the fixed conflicts. #22


[base-ui][Button] disabled prop not being passed across Next.js SSR

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/p/sandbox/brave-darwin-9999s3
Steps:

Make a new next.js project using the "pages" router
Install @mui/base
Add a disabled Button: <Button disabled>button</Button>
Run the project
Load the page
View the page source

Current behavior 😯
The button has the Mui-disabled class, but does not have the disabled prop. This causes a moment on page load where the button is pressable, and also causes a flash of styles when using the :disabled selector.
Expected behavior 🤔
The button should have the disabled prop.
Context 🔦
I'm trying to make a custom Button component styled using the :disabled pseudo-class, but when I load a page with a pre-disabled button it flashes the non-disabled styles for the fraction of a second between when the page loads and when hydration finishes.
Your environment 🌎

npx @mui/envinfo
  System:
    OS: macOS 13.5.2
  Binaries:
    Node: 18.14.0 - ~/.nvm/versions/node/v18.14.0/bin/node
    Yarn: 1.22.19 - ~/<path to project>/node_modules/.bin/yarn
    npm: 8.19.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 116.0.5845.140
    Edge: Not Found
    Safari: 16.6
  npmPackages:
    @emotion/react:  11.11.1
    @mui/base: 5.0.0-beta.14 => 5.0.0-beta.14
    @mui/types:  7.2.4
    @mui/utils:  5.14.8
    @types/react: 18.2.8 => 18.2.8
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 5.1.3 => 5.1.3

@simon-abbott Thanks for reporting this ~ I can reproduce it in the playground with JS disabled in devtools:
import * as React from 'react';
import { Button } from '@mui/base/Button';

export default function Playground() {
  return (
    <React.Fragment>
      {/* doesn't work */}
      <Button className="test-button" disabled>
        Button
      </Button>
      {/* works */}
      <button className="test-native-button" disabled>
        button
      </button>
    </React.Fragment>
  );
}

@gzrae @mj12albert @danilo-leal we would like to pick this up

I faced the same problem in #39838.


Cant find Maui-check after installing

I'm unable to find or execute maui-check.
OP: macOS BigSur 11.4
As a default I am using the fish shell:

You can invoke the tool using the following command: maui-check
Tool 'redth.net.maui.check' (version '0.4.2') was successfully installed.

~/Downloads  maui-check                                                        31s  Thu May 20 11:14:57 2021
fish: Unknown command: maui-check

After that I have tried the same thing instead with the zsh shell:

mvg@maxs-bigmac Downloads % dotnet tool uninstall -g Redth.Net.Maui.Check
Tool 'redth.net.maui.check' (version '0.4.2') was successfully uninstalled.

mvg@maxs-bigmac Downloads % dotnet tool install -g Redth.Net.Maui.Check
You can invoke the tool using the following command: maui-check
Tool 'redth.net.maui.check' (version '0.4.2') was successfully installed.

mvg@maxs-bigmac Downloads % maui-check
zsh: command not found: maui-check

I have installed the SDK: 3.1.408, 5.0.202 and 6.0.100-preview.4.21226.14 over Visual Studio

If you're just using the default location, they should end up here on macOS: $HOME/.dotnet/tools
You likely do not have this on your PATH environment variable.
https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools#install-a-global-tool


Create an npx command to validate plugins

Similar to npx @grafana/create-plugin or npx @grafana/sign-plugin, it would be very useful to have a command to validate a plugin. Then we could add it to package.json and run yarn validate (for example) to test our plugins locally before pushing to a repository.

Available here https://www.npmjs.com/package/@grafana/plugin-validator
Documentation on usage pending here https://github.com/grafana/plugin-validator/pull/88

Great, thank you! I'm trying it out now, I think I just figured it out. These are the commands I used.
cp -r dist ventura-psychrometric-panel
zip -r ventura-psychrometric-panel.zip ventura-psychrometric-panel
npx @grafana/plugin-validator@latest -sourceCodeUri file://. ventura-psychrometric-panel.zip

And this is the output following:
warning: Binary for osv-scanner not found in PATH
detail: osv-scanner executable must be in your shell PATH.
error: Plugin version 1.0.0 is invalid.
detail: The submitted plugin version 1.0.0 is not greater than the latest published version 2.0.1 on grafana.com.
error: Valid license not found
detail: The provided license is not compatible with Grafana plugins. Please refer to https://grafana.com/licensing/ for more information.
warning: unsigned plugin
detail: MANIFEST.txt file not found. Please refer to the documentation for how to sign a plugin. https://grafana.com/docs/grafana/latest/developers/plugins/sign-a-plugin/

I'm not sure what osv-scanner is. Am I missing a dependency? I am on MacOSX 13.2.1 by the way.
You might want to add some steps in the README on how to run this locally. I might still not have it completely correct, so feel free to correct me.
cp -r dist ${PLUGIN_ID}
zip -r ${PLUGIN_ID}.zip ${PLUGIN_ID}
npx @grafana/plugin-validator@latest -sourceCodeUri file://. ${PLUGIN_ID}.zip

I updated the readme to have information about how to run the command: https://github.com/grafana/plugin-validator#with-npx
osv-scanner is a security tool to review your dependencies. you can install it if you want but it is optional https://github.com/google/osv-scanner
if you run the validator with docker you'll have all the security tools installed already.

I updated the readme to have information about how to run the command: https://github.com/grafana/plugin-validator#with-npx

I saw this - but it only shows how to do it for a previously published version on GH. I want to run it locally before pushing the code. I'm assuming I did it correctly since I got the output I was expecting.

@6nv ah! I understand. Your instructions are about running the validator in your local development environment. Please feel free to submit a PR updating the README and I'll be happy to review it and merge it.

Will do, thanks! @academo


Android: add better nullability checks for nullability annotations added in NDK 26

This is needed because Bionic recently added a bunch of these annotations. I made sure this pull doesn't break anything by testing most of it with the previous NDK 25c also. I used this patch with others to build the Swift toolchain for my Android CI, finagolfin/swift-android-sdk#122, and the Termux app for Android, which now uses NDK 26b.
@drodriguez or @compnerd, please review.

@parkera, any further feedback here?

Now that swift-foundation was merged, this pull no longer applies cleanly to that rewrite. Instead, I have modified or removed portions of this pull based on the review comments here and applied it to the release/6.0 branch in #5010 instead, where swift-foundation will presumably not be merged also.
Once that's in 6.0, I will rework this pull for swift-foundation and make the necessary changes here also. My answers to the review comments above will now address what I changed for #5010.

Some of these are no longer needed after the re-core and other changes, others have been submitted again in #5024 and my pull for that, hyp#1.


JDK 11: Remove JavaDoc Links

Hello @mjiderhamn,
since the first PR I've opened for Java 11 compatibility (#87) looks really cluttered, with multiple commits to the same file that sometimes revert each other, I'm splitting the changes into smaller PRs.
Here, I've removed the links to some packages in some JavaDoc comments, because these packages cannot be accessed directly anymore in with Java 11.

Hi, thanks for your reply!
With the links in place, some tests error with the message "Missing code implementation in the compiler" when I run them locally in Eclipse or with mvn test. This does not seem to affect the Travis builds, however.
So I guess it is not neccessary to change this, since I could just remove the links when developing locally and put them back in place before committing - This is probably a matter of opinion, if it is better to have the links in place to conveniently browse the documentation but having to go through this additional step every time.

It works on Travis because JavaDoc is never built there since the build is called like this
./mvnw install -DskipTests=true -Dmaven.javadoc.skip=true -B -V
./mvnw test -B

as explained in Travis Java Documentation.


unable to pay

it always shows Youve exceeded the bank limit for this payment Retry with a small amount
BTW i selected only 1 rs

This issue is part of bank upi service, we are just creating upi link


[Meetingsapps][Responsebody][1609300]

Incorporated changes for issues 2823, 2873 and 2856. Please review.

Docs Build status updates of commit 606c6d5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 30313d0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 104cf83:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d720796:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
:warning:Warning
View
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md

Line 36, Column 282: [Warning-file-not-found] Invalid file link: '~/assets/images/apps-in-meetings/plusbutton.png'.
Line 57, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 77, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 135, Column 122: [Warning-bookmark-not-found] Cannot find bookmark '#participant-roles-in-a-meeting' in 'apps-in-teams-meetings/teams-apps-in-meetings.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b10991e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/assets/images/apps-in-meetings/plusbutton.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit db658c5:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ddbbb09:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


PDFLoader: empty pages in pdf returns Document with undefined pageContent

Im getting
TypeError: Cannot read properties of undefined (reading 'includes')
In RecursiveCharacterTextSplitter.splitText
it's because some of my PDF data has empty pages and the PDF loader is returning undefined pageContent
I guess PDFLoader should check content.items length and do something if it's zero.

@nfcampos Without empty pages we can't know the real page number of a PDF.


[SPARK-37253][PYTHON] try_simplify_traceback should not fail when tb_frame.f_lineno is None

What changes were proposed in this pull request?
This PR aims to handle the corner case when tb_frame.f_lineno is None in try_simplify_traceback which was added by https://github.com/apache/spark/pull/30309 at Apache Spark 3.1.0.
Why are the changes needed?
This will handle the following corner case.
Traceback (most recent call last):
  File "/Users/dongjoon/APACHE/spark-merge/python/lib/pyspark.zip/pyspark/worker.py", line 630, in main
    tb = try_simplify_traceback(sys.exc_info()[-1])
  File "/Users/dongjoon/APACHE/spark-merge/python/lib/pyspark.zip/pyspark/util.py", line 217, in try_simplify_traceback
    new_tb = types.TracebackType(
TypeError: 'NoneType' object cannot be interpreted as an integer

Python GitHub Repo also has the test case for this corner case.

https://github.com/python/cpython/blob/main/Lib/test/test_exceptions.py#L2373

None if frame.f_lineno is None else

Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A

cc @HyukjinKwon

Test build #145020 has started for PR 34530 at commit e7a1f50.

Test build #145020 has finished for PR 34530 at commit e7a1f50.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49492/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145020/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49492/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49492/

Merged to master, branch-3.2 and branch-3.1.

Thank you, @HyukjinKwon !


Template Strings - Confusing Example

GET`http://foo.org/bar?a=${a}&b=${b}
    Content-Type: application/json
    X-Credentials: ${credentials}
    { "foo": ${foo},
      "bar": ${bar}}`(myOnReadyStateChangeHandler);

I don't understand this example; can we have more explanation on this? Otherwise it looks bugged for me.

The template strings could be passed to a function, and it's called Tagged template strings.
See a demo (could run on FF35+)
// Define a function to compile strings
function GET (strings, ...values) {

  /**
    Array [
    "http://foo.org/bar?a=", "&b=", "
    Content-Type: application/json
    X-Credentials: ", "
    { "foo": ", ",
      "bar": ", "}"
    ]
    */
  console.log(strings);

  // Array [ 1, 2, "TOKEN", "FOO", "BAR" ]
  console.log(values);

  /**
   "http://foo.org/bar?a=1&b=2
        Content-Type: application/json
        X-Credentials: TOKEN
        { "foo": FOO,
          "bar": BAR}"
  */
  return strings[0] + values[0] +
         strings[1] + values[1] +
         strings[2] + values[2] +
         strings[3] + values[3] +
         strings[4] + values[4] +  strings[5]
}

// Variables
var a = 1, b = 2, credentials = 'TOKEN', foo = 'FOO', bar = 'BAR';

// Invoke the GET function and pass the template strings
GET`http://foo.org/bar?a=${a}&b=${b}
    Content-Type: application/json
    X-Credentials: ${credentials}
    { "foo": ${foo},
      "bar": ${bar}}`

goo explanation

@chuyik Thanks!

The original example in the post actually has one additional interesting element that isn't captured in @chuyik's implementation example.
Tagged templates can return any kind of object, not just a string.  In this example, the GET tag returns a function which makes a request to the provided URI with a callback myOnReadyStateChangeHandler passed to the function.


custom css variable don't override all styles

Steps to reproduce
Link to live example: (required)
https://stackblitz.com/edit/github-j7eeqn?file=src%2Ftheme.tsx
Steps:

run the project

Current behavior
I overwrote the
--mui-palette-primary-main with custom color
but icons and Switch components still show the default
Expected behavior
the --mui-palette-primary-main color should be applied to all components
also in order to override the style I had to use !important is this correct or I'm doing something wrong
Context
No response
Your environment
No response
Search keywords: css variables

I'm referring to https://mui.com/material-ui/customization/css-theme-variables/usage/#getting-started
that explicitly says
import { ThemeProvider, createTheme } from '@mui/material/styles';

const theme = createTheme({ cssVariables: true });

function App() {
  return <ThemeProvider theme={theme}>{/* ...your app */}</ThemeProvider>;
}

:root {
  --mui-palette-primary-main: #1976d2;
  --mui-palette-primary-light: #42a5f5;
  --mui-palette-primary-dark: #1565c0;
  --mui-palette-primary-contrastText: #fff;
  /* ...other variables */
}

so I still think there is a bug with the disabled Switch component.
regarding the icons problem I realised that I need to use theme.var in order to access the variable value

That CSS snippet is an example of the CSS generated by configuring your colors in createTheme, you're not meant to manually import a css file like that ~


Don't show foreign key links to tables the user cannot access

Spotted this problem while working on this plugin:

https://github.com/simonw/datasette-public

It's possible to make a table public to any users - but then you may end up with situations like this:

That table is public, but the foreign key links go to tables that are NOT public.
We're also leaking the names of the values in those private tables here, which we shouldn't do. So this is a tiny bit of an information leak.
Since this only affects people who have configured a table to be public that has foreign keys to a table that is private I don't think this is worth issuing a vulnerability report about - I very much doubt anyone is running Datasette configured in a way that could result in problems because of this.

Relevant code: https://github.com/simonw/datasette/blob/fbcb103c0cb6668018ace539a01a6a1f156e8d6a/datasette/views/table.py#L1132-L1149

Should I put the permission check in that undocumented datasette.expand_foreign_keys() method? I think so - it should accept request.actor as one of its arguments.

I ran this:
datasette content.db -p 8043 -m fk-auth.yml --root

Against this YAML:
databases:
  content:
    tables:
      users:
        allow:
          id: root

And it worked as it should - here's a screenshot of an anonymous user and a root user viewing the same page:

This fix didn't work on Datasette Cloud. I used /-/permissions to debug it and saw this:

Only checking view-table is not enough: for my instance on Datasette Cloud the view permission check that should have failed was for the database or instance.

To test that locally, use this YAML instead:
databases:
  content:
    allow:
      id: root
    tables:
      releases:
        allow: true

And:
allow:
  id: root
databases:
  content:
    tables:
      releases:
        allow: true


Add us coverages

Re-run this please

I think there’s a bunch of copies of Milwaukee running. It can take 6 hours to cache, so this might take a while.

Re-run this please


Fix typo

Fix a typo where argument had "file" instead of "files".   The plural is what was defined previously in the api and is what Database expects.

@wangyinz I think I made this fix backwards.   Looking back in the repository I think we may have used storage_mode=="file" instead of storage_mode=="files" that this set of commits was trying to impose.
I think this needs to be backward compatible.  If you confirm my observation that it seems we used the singular (i.e. "file") before I'll drop this branch and fix it the other way.

yeah... that's right. It's always been "file" here.


Fix time selection of groundwater levels and quality.

Time format changed because of AQCU Java side.
https://github.com/USGS-CIDA/AQCU/pull/473

Coverage remained the same at 87.428% when pulling a4f59555ebe45ae45494629b1c0916abfaa8279f on dpattermann-usgs:master into cbb4ed4d3ea56e9479ea12807c0512852f2fa5f4 on USGS-R:master.


Contribute camel-raspberrypi component

Got an camel-raspberrypi component here https://github.com/gautric/camel/tree/master/components/camel-raspberrypi
I also an camel-device-io component ready but it isn't full ready yet

Whoa sounds good. Also your excellent blog, we should remember to add that as part of the docs, or refer to it from the website.

If you want I can push my work asap

I've created new issue (#3) for the camel-device-io component.
I will also talk to Geert Schuring - he worked on camel-serial and camel-thinkerforge components.

@gautric I will create a basic structure for the project and ping you. Then you could contribute the RPi component. This is awesome stuff! :)

what about the license ? GPL/ASF/EPL ?
your choice will be mine ;-)

I suggest ASL2 which is also used by many other oss projects. And other projects that some of us work on such as fabric8 hawtio forge, and more and more jboss projects pickup asl over gpl etc.

Yeah, ASL2 FTW!

Here [1] is the Maven module for the IoT related components. Feel free to add RPi component there!
[1] https://github.com/camel-labs/camel-labs/tree/master/iot/components

Hi Greg. I see that you started to contribute the component to the project. Please let us know, when it is ready. Thanks!

I have fixed parent and groupId of the component. I have also imported Camel BOM (2.15.1) into our BOM.

pi4j project releases 1.0 version (http://pi4j.com/#News__Announcements) but pom and jar aren't yet available at Maven central.

pi4j project changes to LGPLv3 License

GPIO should works fine for Digital, Analog and PWN
IRRπ (in real raspberry π), I just tested it with Digital Input and Output

@gautric Can you add the component documentation here [1]?
[1] https://github.com/camel-labs/camel-labs/tree/master/iot#camel-raspberry-pi-component

Is there any additional work related to this component? Any chance to get the docs for the component? I can help with the documentation if needed :) .

@hekonsek I am working on ;-)

Oh cool, just can't wait to brag about the cool stuff we got :) .

Can we close this one in 0.0.0 release?

@gautric Can I close this one? Is the basic version of the component and docs ready?

impl gpio ok, doc ok,
impl i2c ok, doc ok
we can close it for basic version

Great! Thanks Greg! You can always add new stuff in the coming version (and I hope you will ;) ).


numa_available() return 0

Have wsl2 installed
Have docker desktop installed on windows
Have docker installed in Ubunut-20.04 on wsl using Docker server on windows host
Run numactl --show in wsl :

$ numactl --show
physcpubind: 0 1 2 3 4 5 6 7
No NUMA support available on this system.`

Create docker container via wsl with installed numa libraries
Create simple test-case and compile in wsl :

#include <numa.h>
#include
int main()
{
auto n = numa_available();
std::cout  << "numa_available=" << n << "\n";
return 0;
}

Run ./test_numa in wsl :

$ ./test_numa
numa_available=-1

Run ./test_numa in docker image :

$ docker run -it -v pwd/:/app --entrypoint /app/test_numa 53fda3c718da
numa_available=0

Thanks for sharing the issue. For troubleshooting and support, please try the Docker Community Slack or Forums:

https://dockercommunity.slack.com/
https://forums.docker.com/


Allow Multiple Roles for Users

#454
You should now be able to assign multiple roles to a user without the app breaking.
Changelog:

user now has a new property called 'roles' instead of 'role'
Merged UserMinSerializer and MemberSerializer together (They looked too similar)
RoleSerializer no longer loads permissions
Merged RoleSerializer and RoleMinSerializer (other than one loads permissions. they're very similar)
User now has a permissions property (to avoid duplicate permissions through multiple roles)
The check to see if the user is a government user has been moved from the role and into the user as a property called 'isGovernmentUser'
Added helper function in the front-end to get the role name
Added test for the helper function

Good catch on those. This simplified the checks better. I'll see if I can add a test.


Add payment events API endpoint to reporting page

Context
We're missing the GET /v1/payments/paymentId/events endpoint in the tech docs (it's including in our Swagger file/API browser).
Changes proposed in this pull request
Add documentation on getting payment events to the Reporting page.
Guidance to review
Please check if factually correct.

Hi @alexbishop1 - there were a couple of tweaks to this in 2i. When you have time, would you mind taking a look and checking you're still happy? You can see the changes in https://github.com/alphagov/pay-tech-docs/pull/403/commits/40b7da9dd34627d5715b6047fa966d9e9453334a


When renaming link files the .lnk extension gets removed

Description
When renaming link files the .lnk extension gets removed
Steps To Reproduce

Click on a .lnk file
Press F2 to rename
Rename it anything

Expected behavior
The .lnk file extension stays
Files Version
1.5
Windows Version
21H1
Relevant Assets
No response

This has been fixed in the current insider builds and will be available for v2


linux_hardkernel_4_14: 4.14.165-172 -> 4.14.180-176

Motivation for this change
Things done

Compiled and booted the kernel natively on an Odroid HC2. The warm reboot bug when using quiet is still there and also seems to happen with the default of loglevel=4, but loglevel=7 acts as a workaround.
Also cross-compiled the kernel on x86_64, but did not try booting that one.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nixpkgs-review --run "nixpkgs-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
[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/415

FYI: I'm still running that version on my machine - latest nixpkgs I've compiled it on is 26fd4a9a484f401c3daf8bebc1360fab62248b3a, however, I've since added some kernel config options to my NixOS config to disable a bunch of features not needed on the Odroid HC1/2.

@Patagonicus does this help with the many packages marked as broken?

@tomberek I doubt it has any influence on it - nothing should use this kernel by default, e.g. the sd-image-armv7l-multiplatform will use the regular kernel. But that seems to be broken by including zfs while zfs is marked broken on armv7 …


nixos/switch-to-configuration: Few minor/medium improvements

Motivation for this change
Changeset is probably best reviewed by commit. In the order from oldest to newest:

Add a test for targets (people seem to like test coverage)
Ignore some keys in the [Unit] section of units. Should cut down even more on unnecessary service restarts
Fix a minor bug that I introduced regarding activation script restarts. See the commit message for details
Fixes #116735, so cc @kaldonir (and maybe @tfc?)

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[x] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Fixes https://github.com/NixOS/nixpkgs/issues/116735, so cc @kaldonir

Thank you for taking a look at this! I'm actually not 100% sure this issue still applies to the specific combination of the gitlab-runner and docker services, because in our deployments, we had enabled systemd.services.gitlab-runner.restartIfChanged for unrelated reasons in the meantime. But it looks like a sensible fix in any case.
We had been seeing a kind of similar issue with .automount and .mount units, though: https://github.com/NixOS/nixpkgs/issues/155485. Would that issue be resolved with these changes as well?

No, but I already have yet another patchset in the pipeline that fixes some mount/automount stuff ;)
There is no PR for that yet because it depends on this PR and I didn't want to bloat this one even more

I also rebased in support for RefuseManualStart and X-OnlyManualStart when starting a non-reloadable unit, including a test case.
If nobody has objections, I'm inclined to merge this weekend.
@GrahamcOfBorg test switchTest

This seems to break biosCdrom https://hydra.nixos.org/build/169207916/nixlog/16

The single quotes around @installBootLoader@ clash with the single quotes in the default value https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/system/activation/top-level.nix#L233

Thank you for letting me know. If nobody is faster than me, I'll do a fixing PR first thing tomorrow morning


Running a job with input sources against v2 api returns unexpected error

Steps to reproduce:
job.yaml:
name: A Simple Docker Job
type: batch
count: 1
tasks:
  - name: My main task
    inputsources:
      - source:
          type: urlDownload
          params:
            url: https://gist.githubusercontent.com/enricorotundo/990f0ad01a50d08dfb580e4ad404870e/raw/aa6934257351a0da93f1e740c72f27128590cebc/foo_data.txt
        target: /inputs
    engine:
      type: docker
      params:
        Image: ubuntu:latest
        Entrypoint:
          - /bin/bash
        Parameters:
          - cat /inputs/foo_data.txt > /outputs/foo_data.txt

command:
bacalhau job run job.yaml

error:
bacalhau job run job.yaml
Job successfully submitted. Job ID: j-dddd5135-0cf3-4498-ac59-c8a8f018e7bb
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):

	Communicating with the network  ................  done ✅  0.0s
	   Creating job for submission  ...  🐟      ...           0.5s
Error submitting job: Error getting job: Get "http://bootstrap.production.bacalhau.org:1234/api/v1/orchestrator/jobs/j-dddd5135-0cf3-4498-ac59-c8a8f018e7bb": dial tcp <IP_ADDRESS>:1234: co	   Creating job for submission  ...       🐠 ...           0.6sfailed to print job execution: failed getting job executions: Get "http://bootstrap.production.bacalhau.org:1234/api/v1/orchestrator/jobs/j-dddd5135-0cf3-4498-ac59-c8a8f018e7bb/executions": dial tcp <IP_ADDRESS>:1234: connect: connection refused

Can you replicate that locally and not on <IP_ADDRESS>?

In ToLegacyStorageSpec it uses the upper case key when extracting from the params.
URL:           storage.Params["URL"].(string),

Changing url to URL in the job fixes the problem.
We should probably ensure that the keys in params are always stored (and retrieved) in a specific case.


[SDP-1245] Invalidate Circle Distribution Account Status upon receiving a 401/403

What
[TODO: Short statement about what is changing.]
Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]
Checklist
PR Structure

[ ] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR title and description are clear enough for anyone to review it.
[ ] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[ ] This PR adds tests for the new functionality or fixes.
[ ] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[ ] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[ ] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[ ] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[ ] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[ ] This is not a breaking change.
[ ] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[ ] Does the deployment work after merging?

Something went wrong with PR preview build please check

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr338.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr338.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr338.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr338.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr338.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr338.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr338.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr338.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr338.previews.kube001.services.stellar-ops.com


maintainers: remove pesterhazy

Their last commit was caf43ad5af9 from 2015.
Thank you for your contributions.

Motivation for this change
I've noticed this during #122811.
Things done

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

[ ] 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 nixpkgs-review --run "nixpkgs-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.

cc @pesterhazy

Thanks @primeos 😄


Automate/Formalize the OT signup process

Currently the way to get OT tokens is to fill out a google docs survey and then wait for a human to eventually read your request and send you an email.
I'd suggest that this be changed in the following fashion:

provide a real website/service
automate token issuance
document the OT trial token API so it can be automated by website authors

We're currently working on this but it's taking a little longer than we had originally expected! We'll have a console online providing this function as soon as possible!

Closing as we now have a website that provides fully automated self-service: https://developers.chrome.com/origintrials
At this time, we do not intend to provide an API for web developers to automate registration and token generation.


[Datafactory]Move files and  added maxRowPerFile/fileNamePrefix

Move 5 files from Extensions folder to Models folder

added maxRowPerFile/fileNamePrefix to tabular format settings： https://github.com/Azure/azure-rest-api-specs/pull/10666

cancel


Spyder Removed ENTIRE directory

Issue Report Checklist

[x ] Searched the issues page for similar reports
[x ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ x] Could not reproduce inside jupyter qtconsole (if console-related)
[ x] Tried basic troubleshooting (if a bug/error)

[ x] Restarted Spyder
[x ] Reset preferences with spyder --reset
[x ] Reinstalled the latest version of Anaconda
[x ] Tried the other applicable steps from the Troubleshooting Guide

[x ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
All files (100+) were removed from Spyder directory after crash ( I don't know what caused the crash).
The files are not viewable through windows explorer
All that remains are .pngs and pickled files. i.e. any script, module, packages, etc. is gone. Including the folder itself.
Files are not in Recycling Bin.
Restarting computer doesn't show directories either.
I'm wondering if there is any autosave directory I can look in? The folder structure was also removed. i.e. - there aren't a bunch of empty folders, the folders are gone as well.
 The folder structure was also removed. i.e. - there aren't a bunch of empty folders, the folders are gone as well.

Yes, there is. Simply restart Spyder again and it'll show you the files that you can recover.

Closing due to lack of response.


Load config and plugins from project host

The sidekick config is currently stored in the author's bookmarklet URL. When an update to the config is required, e.g. to make use of a new feature, authors are asked to update their bookmarklets (i.e. replace it with a new one). Even though the sidekick redirects them to the right URL to get the fresh bookmarklet, it is still a manual task.
The sidekick also makes a request to the project host to see if there are any custom plugins to load.
In order to avoid manual bookmarklet updates in the future, both the sidekick config and plugins could be loaded from a single config file located on the project host.

file located on the project host.

i.e. github delivered through helix? eg: https://main--repo-owner.hlx.page/helix-sidekick.json ?

I was thinking more of a JS file e.g. https://main--repo-owner.hlx.page/tools/sidekick/config.js so customers can specify listeners for custom buttons.
Example:
// window.hlx.initSidekick(config) is provided by the sidekick app.js loaded prior to this file
window.hlx.initSidekick({
  project: 'Test Project',
  host: 'www.foo.bar',
  hlx3: true,
  byocdn: true,
  plugins: [
    {
      id: 'test',
      button: {
        text: 'Test',
        action: (evt) => {
          console.log('test');
        },
      },
    },
  ],
});

:tada: This issue has been resolved in version 3.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Azam dbt training

Closing, as our training sessions have completed. Follow-on work will happen in new PRs tackling specific issues. Thanks @AzamBeg-Caltrans


Mercy can't slingshot when GAing while hovering

Created by: MaxwellJung

mentioned in merge request ow1_emulator_backup!424

moved from ow1_emulator_backup#531


[WIP] Fix entire packages. Fixes #29

This is a work in progress for fixing #29, by giving it an entire package to build at once.

Makes more sense to focus on #50


Mocha drive letter case sensitivity bug

I found a mocha bug that is fixed with the following hack, so you might want to add this to your sample index.ts files:
export function run(testsRoot: string, cb: (error: any, failures?: number) => void): void {
    // Create the mocha test
    const mocha = new Mocha({
        ui: 'tdd'
    });

    if (process.platform === 'win32') {
        // workaround for https://github.com/microsoft/vscode-test/issues/134
        // see also https://github.com/mochajs/mocha/issues/4851
        testsRoot = testsRoot.toLowerCase();
    }

Hello folks,
Is there a release of @vscode/test-cli planned soon to benefit from this fix?
Thanks

0.0.10 was released with this fix

I see that the Extension Test Runner version 0.0.10 has been released, but I don't see a release of the @vscode/test-cli npm package. Will that also be released any time soon?
Thanks

Ah, sorry, forgot to trigger the build for that. Should be out in a few minutes.


Add support for FiveM a multiplayer framework for GTA 5

it's already done here: https://github.com/LiquidObsidian/fivereborn-query
you just need to implement it to your code

This looks identical to the quake2 protocol, except the status header has been substituted with getinfo


Fixed ResetType

Fix of issue #3465

Docs Build status updates of commit aafb4a5:
:clock10: Full build: the average full build time is 14 min(s) 16 sec(s), this is based on the last 295 build(s) for this repository.

Docs Build status updates of commit aafb4a5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Reset-CsRoutingGroup.md
:white_check_mark:Succeeded
View (skype-ps)

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.

Docs Build status updates of commit 455f407:
:clock10: Full build: the average full build time is 14 min(s) 15 sec(s), this is based on the last 300 build(s) for this repository.

Docs Build status updates of commit 455f407:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Reset-CsRoutingGroup.md
:white_check_mark:Succeeded
View (skype-ps)

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.


Support "leading from" sytnax?

I've had (what I think is) a very clever idea to improve SQL (bare with me, I know that sounds mad 😱).
It's as simple as this: we move the "FROM" clause to the start of select statements, so:

SELECT foo, bar FROM spam becomes FROM spam SELECT foo, bar
SELECT * FROM my_table becomes FROM my_table SELECT *
SELECT x FROM my_table WHERE y=1 becomes FROM my_table SELECT x WHERE y=1
SELECT x FROM (select ...) as t becomes FROM (select ...) as t SELECT x
etc... you get the idea

This has two big advantages:

It's mean SQL language servers can be much much more helpful — it becomes possible to suggest column names in the SELECT clause because the user has already provided the table name — e.g. we can make sensible suggestions at FROM my_table SELECT a[CURSOR]
It's (arguably) easier to read - example: "We got roads, concrete, plumbing and calendars from the Romans" is quite hard to interpret the first time you read it because you need to keep all the things in your head without knowing the context, while "From the Romans we got roads, concrete, plumbing and calendars" is much easier to understand because you already have the context of the Romans when you read/hear the list. The same goes for FROM users SELECT id, name, created_at. The point is that SELECT ... FROM ... syntax follows some natural language which only puts the "from" at the end to developer suspense, at the cost of less easy understanding, we don't want suspense, we want ease

I also think it would make CTEs read much better: with t as (select 1 as a) from t select a since using t is directly after the CTE.
Unlike alternatives to SQL like PRQL and EdgeQL:

there's no new language to learn — it's still SQL with one small alteration
it's completely backwards compatible — SELECT foo, bar FROM spam still works fine, you just get to use FROM spam SELECT foo, bar if you like
no new parser is required, or decisions on how exactly to reinvent everythingelse, it's just an optional increase in flexibility in an existing parser, e.g. sqlparser-rs

So here's my feature request: an optional flag (allow_leading_from) which allows the FROM clause to come before SELECT. It can even be a feature so it's compiled out for those who don't want it.
WDYT?

See https://duckdb.org/2023/08/23/even-friendlier-sql.html#from-first-in-select-statements

Oh nice, I had no idea.

Thanks @adriangb, now I can just make the feature request "support duckdb 'from first' syntax".

I have a branch that supports this, I'll create a PR when I have time.
Some related link

HN thread on similar issue
PR adding  this to DuckDB https://github.com/duckdb/duckdb/pull/5076


ADVI diagnostic

Summary:
Add PSIS diagnostic for ADVI .
Description:
This paper proposes PSIS diagnostic for ADVI: Yuling Yao, Aki Vehtari, Daniel Simpson, and Andrew Gelman (2018). Yes, but Did It Work?: Evaluating Variational Inference https://arxiv.org/abs/1802.02538
Currently ADVI samples N draws from the approximate distribution and outputs those. In addition lp__ column is inserted, but it has all 0's (it seems stansummary requires lp__ column).
To follow the current design with stansummary, what we propose is

[x] after ADVI finishes, compute lp__ and lg__ (log density of of the approximation) in stan/src/stan/variational/advi.hpp

[x] output lp__ and lg__ along with parameter sample (for lp__ provide values instead of 0's and add lg__ column). Something needs to be added also in stan/src/stan/services/experimental/advi/meanfield.hpp

[ ] add algorithms for computing khat and neff in services

[ ] Given the output we can compute diagnostic afterwards, e.g., using stansummary for CmdStan

for simplicity we would implement this first for CmdStan (needs separate issue), ie, modify stansummary to output diagnostics cmdstan/src/cmdstan/stansummary.cpp

Note that initially we start just computing the diagnostics, but eventually we can use diagnostics to improve the algorithm.

@yao-yl is working on this, but I can't assign this issue for him

I do not know why I cannot get assigned or self-assigned. But yes, I am working on this. I have implemented this in cmdstan and will try to add it in rstan.

I think you need to be added as a collaborator to be assigned---I think  @syclik and @seantalts have the permissions to do that for you.

Weird! I'll look into it.

@yao-yl I was thinking about assigning myself, but it appears you've already implemented this:

I have implemented this in cmdstan

We can do separate PR's for each interface.
Want to drop me the code and I can go ahead and integrate it and write appropriate tests?

I just updated the issue. 2 first things are in stan. Next thing would be to implement khat and n_eff in services.

Where can I find the algorithms?

To compute khat I'm using Zhang and Stephens section 4?

The reference I know for ADVI eval with k-hat is Yao et al..

You can use the R code as a reference implementation https://github.com/stan-dev/loo/blob/master/R/gpdfit.R
It follows Zhang and Stephens , but uses numerically more stable computations plus weakly informative prior.

and then for Neff?

For Neff see the variance formula which is last equation on page 4 in https://arxiv.org/abs/1507.02646
and for the reference code see https://github.com/stan-dev/rstan/blob/develop/rstan/rstan/R/stanmodel-class.R#L288 lines 288-304


CSS: standardize identity icon display

Description
Small CSS changes to standardize displays of creatibutors' identity icons between views --  landing page view,  public search results view,  and dashboard view.  This affects the spacing between the name and the icon, the spacing between the name-icon groups, and the size of the icons.
Checklist

[x] I'm aware of the code of conduct.
[x] I've created logical separate commits and followed the commit message format.
[ ] I've added relevant test cases.
[ ] I've added relevant documentation.
[ ] I've marked translation strings (for relevant code).
[x] I've followed the CSS/JS and React guidelines (for relevant code).
[x] I've followed the web accessibility guidelines (for relevant code).
[x] I've followed the user interface guidelines (for relevant code).
[x] I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
[x] I've NOT included third-party code (copy/pasted source code or new dependencies).

Screenshots of the 3 views to compare:

Addresses https://github.com/inveniosoftware/invenio-theme/issues/282

@lhenze I'm closing this PR and taking it here https://github.com/inveniosoftware/invenio-app-rdm/pull/1641/files because it needed a rebase and I did not want to push force to you branch, just in case 😇 . You are still the author of the commit, just being merged in another PR.


Migrate browser implementation from the qrcode-reader package to jsQR

The package qrcode-reader is deprecated and recommends switching to jsQR, which also happens to be written in TypeScript.

@bitjson do you know when this migration will be done?

I don't know of anyone working on it currently. You're welcome to pick it up!


I have two internet connections
DSL vendor : Airtel (Have no issues) on all platforms windows, ubuntu and mac
Fiber vendor : BSNL (my dynamically assigned  ip now is <IP_ADDRESS>) causes issue only on ubuntu 16.04 (also tried live version; same issue)

Using fresh ubuntu 16.04
Connected with specific internet vendor BSNL(assigned me dynamic ip this time <IP_ADDRESS> and confirmed issued again). I am adding my ip if this issue is something related to CDN. Every thing works with other dsl vendor.
Can't do docker pull on only dockerhub images; hangs indefinitely without error
**Can't login at hub.docker.com; hangs indefinitely and keeps showing logging in ** - Chrome inspect shows 502 gateway error

Thx and let me know if you wanna know something else as problem is pretty tricky.

This might be an issue with the MTU, can you try running the docker daemon with --mtu=1450 and see if that helps?

Ping @jas99

@justincormack @thaJeztah
Hi guys
Sorry for late reply
From yesterday it seems to be healed(both pulling and login to dockerhub are working) and I wasn't able to test at 1450 mtu thus.
I am gonna close this issue for now; if you guys have follow up question be my guest :smile:
Thx

Thank you @jas99 !


Cronjob configuration ruby2.2 full path

It seems that ruby2.2 resides outside PATH when running a cronjob in WebFaction, so it would be safer to change the documentation to advise people to call ruby2.2 using its full path in the system installation, which is /usr/local/bin/ruby2.2.
The cronjob command would be:
PATH=$PATH:$GEM_HOME/bin GEM_HOME=$HOME/.letsencrypt_webfaction/gems RUBYLIB=$GEM_HOME/lib /usr/local/bin/ruby2.2 $HOME/.letsencrypt_webfaction/gems/bin/letsencrypt_webfaction --account_email<EMAIL_ADDRESS>--domains [yourdomain.com,www.yourdomain.com] --public ~/webapps/[yourapp/your_public_html]/
(I just noticed that my certificates were not being updated due to a failure to execute ruby2.2)

Huh. Good catch. On my system, the PATH is /usr/bin:/bin.
However, $GEM_HOME is defined in the following stanza and doesn't include Ruby…
I'd imagine that the correct PATH would be: PATH=$PATH:/usr/local/bin.
I'll add that to the readme. Thanks!

Thank you so much!  Keep the amazing tool.


Support publishing packages with repository links

Feature Description
Currently if you follow:
https://docs.gitea.com/usage/packages/maven
It suggests you publish packages to:
https://gitea.example.com/api/packages/{owner}/maven
This publishes packages at the user/org level and does not make an association with the underlying repository, you must go to:
https://gitea.example.com/{owner}/-/packages/maven/{publication-name}/settings
And set the repository link manually, this can become very tedious, I suggest being able to publish to another URL to automatically create these repository links.
https://gitea.example.com/api/packages/{owner}/{repo}/maven
Could create the same publication but automatically create the repo link, thus preventing the manual step.
It looks like Github manages this quite differently than Gitea does:
https://docs.github.com/en/actions/publishing-packages/publishing-java-packages-with-gradle#publishing-packages-to-github-packages
But similarly to the above does have the repo name in the publication endpoint.
Screenshots
No response

duplicate of: https://github.com/go-gitea/gitea/issues/28808


Delete GSOC.md (issue template)

GSoC 2022 is now complete - we can re-add this file later if needed for next year.

Merging this in. We can re add this next year if we do GSoC again.


[Feature request]  Azure OpenAI Assistants

Hi, Microsoft has released Assistants API on Azure.
I hope it will be supported on langchain.
https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/openai/openai-assistants/README.md
https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/assistants

Hi,
I found get it works in Azure OpenAI Assistant Api with 'openai' package.
https://github.com/openai/openai-node/issues/701
This issue's comversation about azure assistant API in openai package example.
So I close this issue and thank you for langchain.js every contributors.

Any update on this? I am still not seeing support for Azure OpenAI Assistants. Anyone else?

Same here, it's the main limitation keeping me from migrating to LangChain


Fix typing on convert classmethod to work with subclassing

The convert classmethod needs to use a TypeVar for subclasses to be typed properly.

thank you for contributing!


[MWPW-134982] Template Redirect and Render Fix

Descriptions:
Search page: We now include tasksx to be part of targetUrl consideration. Also finished some authoring work in metadata sheet search page row that was missing in locales.
Template X: Stop redrawing templates when the props and props.filters aren't changed.
Resolves: MWPW-134982
Test URLs:

Before: https://main--express--adobecom.hlx.page/express/templates/?lighthouse=on
After: https://mwpw-134982--express--adobecom.hlx.page/express/templates/?lighthouse=on

Codecov Report

Merging #175 (f8bd9f6) into stage (136cd97) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            stage     #175   +/-   ##
=======================================
  Coverage   35.38%   35.38%
=======================================
  Files          27       27
  Lines        9490     9490
=======================================
  Hits         3358     3358
  Misses       6132     6132

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


[feat]: /docs/components/number-ticker - StartValue

Is your feature request related to a problem? Please describe.
Always starts from zero. It would be nice if we can provide a starting value
Describe the solution you'd like
<NumberTicker startValue={50} value={100} />

Describe alternatives you've considered
N/A
Additional context
N/A

Can you please assign it to me?

@PraveenShinde3  - Could you also address the value with commas, or would that be a separate issue?

I have made a change, so that we can give a custom "start value"
For example : in following demo i have set the startValue to "500" and value to "1000" and for decimal the startValue is "3.99" and value to "8.67"
https://github.com/user-attachments/assets/780c256e-df2f-4701-af3d-ba3b1c27cc40

@dinbtechit what exactly is the issue with commas?

@dinbtechit what exactly is the issue with commas?

Oh I did not realize. The comma's were already taken care of. I am curios what does it look like for large numbers...
<NumberTicker startValue={'168,500.10'} value={'170,500.99'}

this is how it looks as per your given startValue and value
the code would be something like this
<NumberTicker startValue={168500.1} value={170500.99} decimalPlaces={2} />
https://github.com/user-attachments/assets/10b30bd3-e4ef-436d-801a-febd827c2c3a

this is how it looks as per your given startValue and value
the code would be something like this <NumberTicker startValue={168500.1} value={170500.99} decimalPlaces={2} />
Screen.Recording.2024-11-29.210929.mp4

That looks freaking good!! Great job! thanks @PraveenShinde3

Hoping this PR gets approved 🤞

Hey, we discussed this and decided not to add props like that for now. Instead, we plan to set a custom duration for each numberTicker component so they can finish at their own pace (or simultaneously) if needed. Thanks for the feedback! If we decide to add this props in the future, we'll reopen the discussion.


Add tool to sign messages

Summary

A new "sign a message" mini-app!
Motivation and Context

Some use cases, like sign-in-with-Ethereum, requires signing a message with the private keys usually managed by MetaMask, Ledger, etc. This mini-app allows the user to sign an arbitrary message with their preferred wallet.
How Has This Been Tested?

Manually tested and signatures are being generated properly.
Screenshots (if appropriate):

Types of changes

[x] 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.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Metrics
Actual effort: 1h

feature ACK


UI input element constraints

As a developer, I am required to restrict the user to a set a valid conditions for each input element as defined in the project plan.
Input Element(s)

[ ] #46
[ ] #47
[ ] #48
[ ] #49

Researching UI/UX design guidelines for implementing the required elements. Collaborated with neighbor (Davide Farnocchia) on my proposed solution for deriving and constraining the Mission Sol input element; the mission sol requires a "zero hour". Davide confirmed my calculation and provided some useful resources for further understanding the timestamps in the MEDA data.
{t:240}

All tasks complete.


METRICS: P1 : Build PowerBI Template for Virtual Assistant

Plan

Ryan going to create PowerBI for Virtual Assistant.
Convert based on Virtual Assistant spec and what's directly usable from other customer engagements.

Duplicate of #5148


White background for output cells with ipywidgets

For #9517

Codecov Report

Merging #10750 into ds/ipyWidgets will not change coverage by %.
The diff coverage is 0.00%.

@@              Coverage Diff               @@
##           ds/ipyWidgets   #10750   +/-   ##
==============================================
  Coverage          60.74%   60.74%
==============================================
  Files                580      580
  Lines              31454    31454
  Branches            4473     4473
==============================================
  Hits               19107    19107
  Misses             11375    11375
  Partials             972      972

Impacted Files
Coverage Δ

src/client/datascience/jupyter/jupyterSession.ts
59.59% <0.00%> (ø)

...ascience/jupyter/liveshare/guestJupyterNotebook.ts
9.37% <0.00%> (ø)

Continue to review full report at Codecov.

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


Get-UserRightsAssignment - Remote Identity references could not be translated on Local

Exception on Translate. The NT SERVICE\MSSQLSERVER, NT SERVICE\SQLSERVERAGENT , etc could not be translated. Is there a way to have these appear correctly as opposed to only showing a SID.
get-userrightsAssignment -UserRightsAssignment SeAssignPrimaryTokenPrivilege -Computer remoteserver

Received Results
Name       : S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003
SID        : S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003
DomainName :
Error      : Exception calling "Translate" with "1" argument(s): "Some or all identity references could not be translated."
Type       : Unknown

Expected Results
Name       : NT SERVICE\MSSQLSERVER
SID        : S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003
DomainName :
Type       : NotAdministrative
Error      :

I tried the below and it does work while running on the remote machine.
(New-Object System.Security.Principal.SecurityIdentifier('S-1-5-80-4121710933-1810356231-1548310709-4180092075-1007940561')).translate( [System.Security.Principal.NTAccount] )

The code below from the .NET library appears to be failing here because it is performing the translation on the local machine. And maybe this Issue should be moved there?
https://github.com/EvotecIT/LocalSecurityEditor/blob/ceeaf74083d228853b3203875316f4a5fe365bd2/LocalSecurityEditor/LsaWrapper.cs#L166C35-L166C35
Is there a way to create the SecurityIdentifier on the remote easily with Win32 or the like as opposed to opening a new remote connection?

Sorry I've missed this.
The fix for this is in:

https://github.com/EvotecIT/PSSharedGoods/blob/master/Public/Converts/Convert-Identity.ps1
https://github.com/EvotecIT/PSSharedGoods/blob/master/Public/Converts/ConvertFrom-SID.ps1

Do you have any other missing GUIDs that needs resolving?

So Named Instances have their own SID as well. And there is SSRS, SSIS, Full Text, etc. SSIS and SSRS all have different versions too. We can only maintain a list? Named instances would be NT SERVICE\MSSQL$INSTANCENAME which could be any instance name. You can have multiple instances on my machine too.

I played with this a bit trying to generate the SID based on a name and so far I am failing. Will play more, but if you have logic that matches the results when you query them manually I would be happy to get it ;)

Ok,
function New-NTServiceSid {
    [cmdletBinding()]
    param (
        [Parameter(Mandatory)][string]$serviceName
    )

    $serviceName = $serviceName.ToUpper()
    $sha1 = [System.Security.Cryptography.SHA1Managed]::new()
    $hash = $sha1.ComputeHash([Text.Encoding]::Unicode.GetBytes($serviceName))

    $sid = "S-1-5-80"
    for ($i = 0; $i -lt 5; $i++) {
        $part = [BitConverter]::ToUInt32($hash, $i * 4)
        $sid += "-" + $part
    }

    return $sid
}

New-NTServiceSid -ServiceName 'ADSync'
New-NTServiceSid -ServiceName 'SQLTELEMETRY'
New-NTServiceSid -ServiceName 'SQLTELEMETRY$VEEAMSQL2016'
New-NTServiceSid -ServiceName 'SQLTELEMETRY$VEEAMSQL2016$VEEAMSQL2016'
New-NTServiceSid -ServiceName 'himds'

Could you test this with your service names you have? The problem I have it works for ADSync and himds, but not for 'MSSQLSERVER' so I am not sure if it's just this one or something is off.


Mark TSHashTable non-copyable.

Ping @SolidWallOfCode @jacksontj

FreeBSD build failed! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/253/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/151/ for details.

[approve ci] Starting another build, FreeBSD git repo was wedged.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/154/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/256/ for details.


Support update/upgrade of downstream package

We want to allow users to upgrade a downstream packages. This requires:

Being able to find out whether the upstream package has a newer revision.
Being able to find all direct downstream packages of package that is based on an older revision of the current package.
Update a package to a specific revision (or latest) of the upstream package.

Finding the upstream porch package from an existing package is not completely straightforward, as the upstream information is only available in the Kptfile, i.e. in the content of the package. We need to make sure we have a good way for finding the upstream porch package from an existing porch package.
For actually doing the update, we need to see how well that fits with the KRM API provided through the aggregated API server. We could also consider implementing it with a CRD and controller
Ref: https://github.com/GoogleContainerTools/kpt/issues/3189

We have completed all the features in this issue, so closing it.


Upload confirmation

Epic

Story

As a user of Swarm, I want to know that my upload request reached it's destination, such that I am assured of successful upload (use tags)
Background

@jmozah

@acud , you put this one as blocked by #118. What is, in your opinion, the added value of this epic over #118?


Running greed fails with assert w3.is_connected()

I just installed greed and tried running it on a sample contract.
The installation instructions were clear, and the setup worked like a charm; the only hiccup was changing analyze_hex.sh contract.hex to analyze_hex.sh --file contract.hex.
But when running greed I get the following python stacktrace:
$ greed ./greed/ --debug
DEBUG | greed.project | All sanity checks passed in 0.0001s
Traceback (most recent call last):
  File "/home/raoul/.virtualenvs/greed/bin/greed", line 122, in <module>
    main(args)
  File "/home/raoul/.virtualenvs/greed/bin/greed", line 33, in main
    assert w3.is_connected()
AssertionError

I'm a little stuck here. Any ideas?

Hi Raoul,
I have addressed this in the latest commit (b61c81bd).
The reason you see that error is that for some of our analysis (mostly in memory/partial_concrete_storage.py) we use a web3 endpoint to read on-chain data. This is not really needed in the script you are using so making it optional seems a good idea. Thanks for reporting this!

It seems a good idea to also add a warning in the partial concrete storage instead of crashing. Will add this :)

That was quick 🚀 I can confirm the error is gone, thanks guys!


⚠ Jenkins Plugins Artifactory has degraded performance

In 967fd0b, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 2623 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 8acdaf6 after 23 hours, 21 minutes.


[stable/prometheus] prometheus server doesn't start in K8S with PodSecurityPolicy activated

BUG REPORT
When Prometheus is use in a secured K8S with podSecurityPolicy runAsNonRoot
the init-chown-data cannot be launch as it need to be root
so the container still stay not initialized.
We need to have an option to enable or not the init-chown-data
see also https://github.com/helm/charts/issues/8126
What happened:
prometheus server doesn't start
What you expected to happen:
prometheus server starts
How to reproduce it (as minimally and precisely as possible):
use a K8S with podSecurityPolicy runAsNonRoot
Anything else we need to know:
If I remove the init-chown-data from deployment the prometheus server start

The option already present


Computational Resource Cost Table/Figure

Make a table/figure showing the relationship between raw data size and memory cost/running time. Using a fixed resource allocation. (e.g., 20G memory, 10CPU). Sample figure can be Table 3 in YAMP paper

Total number of files (including 1/6 first/second group positive/negative/blank samples)
Total size of raw data
Running time
Virtual Memory Consumption

12
0.8G
2h 12m 13s
40.63G

24
1.6G
3h 10m 22s
43.07G

36
2.4G
4h 12m 25s
45.63G

48
3.3G
5h 01m 08s
47.41G


Rewrite queue

The problem
The old queue package has some legacy problems:

complexity: I doubt few people could tell how it works.
maintainability: Too many channels and mutex/cond are mixed together, too many different structs/interfaces depends each other.
stability: due to the complexity & maintainability, sometimes there are strange bugs and difficult to debug, and some code doesn't have test (indeed some code is difficult to test because a lot of things are mixed together).
general applicability: although it is called "queue", its behavior is not a well-known queue.
scalability: it doesn't seem easy to make it work with a cluster without breaking its behaviors.

It came from some very old code to "avoid breaking", however, its technical debt is too heavy now. It's a good time to introduce a better "queue" package.
The new queue package
It keeps using old config and concept as much as possible.

It only contains two major kinds of concepts:

The "base queue": channel, levelqueue, redis

They have the same abstraction, the same interface, and they are tested by the same testing code.

The "WokerPoolQueue", it uses the "base queue" to provide "worker pool" function, calls the "handler" to process the data in the base queue.

The new code doesn't do "PushBack"

Think about a queue with many workers, the "PushBack" can't guarantee the order for re-queued unhandled items, so in new code it just does "normal push"

The new code doesn't do "pause/resume"

The "pause/resume" was designed to handle some handler's failure: eg: document indexer (elasticsearch) is down
If a queue is paused for long time, either the producers blocks or the new items are dropped.
The new code doesn't do such "pause/resume" trick, it's not a common queue's behavior and it doesn't help much.
If there are unhandled items, the "push" function just blocks for a few seconds and then re-queue them and retry.

The new code doesn't do "worker booster"

Gitea's queue's handlers are light functions, the cost is only the go-routine, so it doesn't make sense to "boost" them.
The new code only use "max worker number" to limit the concurrent workers.

The new "Push" never blocks forever

Instead of creating more and more blocking goroutines, return an error is more friendly to the server and to the end user.

There are more details in code comments: eg: the "Flush" problem, the strange "code.index" hanging problem, the "immediate" queue problem.
Almost ready for review.
TODO:

[ ] add some necessary comments during review
[ ] add some more tests if necessary
[ ] update documents and config options

Code coverage:

How does this PR handle when elasticsearch temporarily restart?

How does this PR handle when elasticsearch temporarily restart?

[This PR] keeps using old config and concept as much as possible.

So, is it breaking or not? Does it remove any setting?

It removes a lot, these options should have been removed in 1.18, but they haven't.

"Deprecated fallback for %s queue length [%s] %s present. Use [queue.%s] LENGTH. This will be removed in v1.18.0"


Replace std::io with std::old_io.

This is needed to compile with nightly rustc. See: http://internals.rust-lang.org/t/psa-io-old-io/1403

Thanks!


how to run the simulation example？

./run ./bellcanada_dynamic_2_0.ini
dirname--------->.
OMNeT++ Discrete Event Simulation  (C) 1992-2019 Andras Varga, OpenSim Ltd.
Version: 5.6, build:<PHONE_NUMBER>30a193, edition: Academic Public License -- NOT FOR COMMERCIAL USE
See the license for distribution terms and warranty disclaimer

Setting up Qtenv...

Loading NED files from .:  4
Loading NED files from ../src:  13

<!> Error: The following NED types could not be fully resolved due to a missing base type or interface: ieee8021cb.frer.TSNRelay, ieee8021cb.spb.ExtendedMACTable, ieee8021cb.spb.SPBEtherEncap

i meet some problem when i run the example, Does anybody know why that is?

Hello Reihold,
Could you please also check the configuration I described in issue #1. The problem may also stem from that you are using OMNeT++ v5.6 but I implemented the project in v5.5.1 with INET v3.6.7 as it is described in the respective paper.
Best


"Create Segment" disappears when deleting last segment

How are you running Flagsmith

[ ] Self Hosted with Docker
[ ] Self Hosted with Kubernetes
[X] SaaS at flagsmith.com
[ ] Some other way (add details in description below)

Describe the bug
Self-explanatory, watch this video:
https://github.com/Flagsmith/flagsmith/assets/829698/cea98bee-4e4d-48dd-8235-3cf9c91c73e6
Steps To Reproduce
Watch video above.
Expected behavior
...
Screenshots
No response

The replication I believe is when you actually have a feature-specific segment leftover.


evaluator: errors in list values ignored in default selection

What version of CUE are you using (cue version)?

$ cue version
cue version v0.0.0-20220912105017-e5f21dbb163c

       -compiler gc
     CGO_ENABLED 1
          GOARCH arm64
            GOOS linux
             vcs git
    vcs.revision e5f21dbb163c8b864dc1e518dc86e16d8aa0bbf9
        vcs.time 2022-09-12T10:50:17Z
    vcs.modified false

Does this issue reproduce with the latest release?
Yes
What did you do?
exec cue eval x.cue
cmp stdout stdout.golden

-- x.cue --
zones: domain_name: "a.com"

x: *[zones.domain] | [...string]
y: *zones.domain | string
-- stdout.golden --
zones: {
    domain_name: "a.com"
}
x: []
y: string

What did you expect to see?
Passing test.
What did you see instead?
> exec cue eval x.cue
[stdout]
zones: {
    domain_name: "a.com"
}
x: [zones.domain]
y: string
> cmp stdout stdout.golden
--- stdout
+++ stdout.golden
@@ -1,5 +1,5 @@
 zones: {
     domain_name: "a.com"
 }
-x: [zones.domain]
+x: []
 y: string

FAIL: /tmp/testscript2783301736/repro.txtar/script.txtar:2: stdout and stdout.golden differ

Note that the expectation that the value of x be [] is an artefact of cue eval "losing" the constraint [...string].

Marking as a blocker for https://github.com/cue-lang/cue/issues/1828, because without this fix we can't easily validate the correctness of the fixes for https://github.com/cue-lang/cue/issues/1828.


[WIP] feat(nfs volume): allow non-root applications to access nfs-share volume

Signed-off-by: mittachaitu<EMAIL_ADDRESS>Pull Request template
Why is this PR required? What issue does it fix?:
This PR is required to set group ID on nfs-share volume.
Setting group ID on nfs volume allows non-root users(who
has supplemental group ID matching to nfs group ID) to
access nfs volume. It fixes #46
What this PR does?:
This PR allows specific non-root applications to access nfs volume.
Does this PR require any upgrade changes?:
No
If the changes in this PR are manually verified, list down the scenarios covered::
Yes,

Provisioned NFS volume by setting FSGID and volume got successfully created.
Deployed an application that runs as a non-root user on the above NFS volume and
it is unable to access volume.
Deployed another application by setting supplemental group ID(i.e FSGID) and it is
able to access volume.

Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[ ] Fixes #
[ ] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #52 (16a7c77) into develop (489da0d) will decrease coverage by 0.15%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop      #52      +/-   ##
===========================================
- Coverage    48.46%   48.31%   -0.16%
===========================================
  Files           18       18
  Lines         1595     1600       +5
===========================================
  Hits           773      773
- Misses         778      783       +5
  Partials        44       44

Impacted Files
Coverage Δ

...tes/api/core/v1/podtemplatespec/podtemplatespec.go
41.86% <0.00%> (-0.74%)
:arrow_down:

Continue to review full report at Codecov.

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

Looks good. Need to follow up with updating the docs on how to use this feature.

I will take doc changes as separate PR