Add more explicity project description

This is a great addition to the readme! It really helped me to quickly understand what the project does. However, I would like to correct some spelling mistakes:
Task that extracts all translation keys of an angular-translate project. It searches all views and js scripts to find angular-translate` calls; such as:
* `{{'KEY_IN_VIEW' | translate }}`
* `$translate.instant('KEY_IN_SCRIPT')`

Each found key is then extracted to json files with translations. For each locale defined in the Gruntfile, a separate json is created:

    {
      "KEY_IN_VIEW": "",
      "KEY_IN_SCRIPT": ""
    }

A translation should be provided in the created files. On the next runs `grunt-angular-translate` will not change keys
already translated. It will add keys that were added to the source and remove the ones that are not longer present in the source.

Maybe you would like to add the corrections to your PR.

@SKoschnicke thanks a lot for corrections:) I've updated the PR


fix: Adjust Conversation's CTA modals to consider offerable and offerableFromInquiry

The type of this PR is: Bugfix
This PR actually solves NX-3114
Description
Caught by @lidimayra.
This PR fixed an issue but introduced another problem. This PR should fix that by taking both properties into consideration.
cc @artsy/negotiate-devs

I moved the ticket back to In Review to reflect the current state.


Support setting the --environment flag via env var

Problem description
When running a pixi task in an config that has >1 environment and the task is defined in default env pixi will ask you to specify the environment
$ pixi run test_sdk
  × the task 'install_sdk' is ambiguous
  help: These environments provide the task 'install_sdk': default, engine

        Specify the '--environment' flag to run the task in a specific environment, e.g:.

                pixi run --environment default install_sdk

It would be a nice ux improvement to allow setting the environment flag by means of the PIXI_ENVIRONMENT_NAME env var
$ PIXI_ENVIRONMENT_NAME=default pixi run test_sdk

That will allow a bunch of associated tasks to be more easily coordinated from a higher order place (or using the env var as a matrix in things like github actions)

I'm trying to understand the use-case, as I think it would be more transparent in GitHub actions if you do:
pixi run -e $PIXI_ENVIRONMENT_NAME install_sdk

The problem I see is that people unexpectedly start running with different environments than they expect, thus we would need to add more logging or other logic to make sure that doesn't happen.

Note that once #900 is merged this will work out of the box.

I like this approach since this ensures that you are running the proper commands when you are in pixi shell or you did the activation with eval "$(pixi shell-hook)" and direnv.
Maybe also add the behavior that you don't activate again if the env var is already set? But this might be a bit too much magic...

I think there are two cases:

You already activated the environment through shell-hook or shell, in that case, I also think it makes sense that we default the environment to the currently activated environment.
You have not yet activated an environment. This is the case that @ruben-arts is talking about I think.

We could also look at the PIXI_PROJECT_MANIFEST variable and only if that points to the same path as the current project use PIXI_ENVIRONMENT_NAME as the default. We could also short-circuit activation if the environment is already activated based on that environment variable.
WDYT?

I think as long as we print something when this env var is actually set the "magic" behavior that may exist goes away

We've decided that we want to implement as @baszalmstra describes. Adding the warning as @mariusvniekerk describes is a nice to have.

Fixed in: #1080


script takes input of folder location to clean

User can specify which folder to clean by mentioning its path in config.ini
Eg.
Config.ini:
PLocation: "C:/xyz/folderlocation"

Cool idea @skcy2001 🆒
I wanted to add this feature in it.
While you are at it, can you also:

add the extension options in the config file too? It is currently a dictionary in the script. Instead of this, we can have the script read this from the config file so that the users can change those.
Take the input folder as a command line argument.
Eg. python arrange.py /PATH/TO/CLEAN
If no path is specified, clean the current directory.

If you can do this, please let me know :) 💯

Yep, I will do it.

Check #10 . Did all the changes you mentioned.


netlify command issue with URLs

The order of these commands is giving me trouble when using netlify-cli
Changing to this resolved the issue:
[context.production]
  command = "hugo --gc --minify -b $URL && npm run build:functions"

[context.deploy-preview]
  command = "hugo --gc --minify -b $DEPLOY_PRIME_URL"

[context.branch-deploy]
  command = "hugo --gc --minify -b $DEPLOY_PRIME_URL"

Netlify was printing out --gc as part of the URL path if the URL wasn't specified last.

Fixed with 20bac2a25bcdb3156120afd0d1b6543c0235f3c7 + 9581fc4c44d2fdfe6b6093365fdbf5dcd2b869a2


Fix readme erroneous statement regarding channel pipeline

Fix readme erroneous statement regarding channel pipeline not being thread safe
Motivation:
Readme says channel pipeline is not tread safe which is incorrect
Modifications:
Correct ChannelPipeline description so that it says thread safe.
Result:
Statement regarding channel pipeline will be correct

@swift-nio-bot test this please


Display parameters in svcat describe instance/binding output

When an instance or a binding has parameters set, display in yaml format. Omit the entire section otherwise.
$ svcat describe instance knotted-otter-wordpress-mysql-instance
  Name:        knotted-otter-wordpress-mysql-instance
  Namespace:   default
  Status:      Ready - The instance was provisioned successfully @ 2018-03-21 19:41:13 +0000 UTC
  Class:       azure-mysql
  Plan:        standard100

Parameters:
  firewallRules:
  - endIPAddress: <IP_ADDRESS>
    name: AllowAll
    startIPAddress: <IP_ADDRESS>
  location: eastus
  resourceGroup: default
  sslEnforcement: disabled

Bindings:
                  NAME                    STATUS
+---------------------------------------+--------+
  carolyn                                 Ready
  knotted-otter-wordpress-mysql-binding   Ready

$ ./bin/svcat/svcat describe binding carolyn
  Name:        carolyn
  Namespace:   default
  Status:      Ready - Injected bind result @ 2018-03-21 19:56:07 +0000 UTC
  Instance:    knotted-otter-wordpress-mysql-instance

Parameters:
  foo: bar

$ ./bin/svcat/svcat describe binding knotted-otter-wordpress-mysql-binding
  Name:        knotted-otter-wordpress-mysql-binding
  Namespace:   default
  Status:      Ready - Injected bind result @ 2018-03-21 19:41:20 +0000 UTC
  Instance:    knotted-otter-wordpress-mysql-instance

Closes #1808

I've updated this PR to only show Spec.Parameters and will follow up with one for --external-properties and auto-diffing.


Cookie can't login?

The session cookie from instagram phishlets is not working?
I import the cookie to cookie editor and refresh the login page but
It's doesn't login??
Sorry if I distrub you 😶

i had that prob, i delete all break (new line) maybe this helps you:
on editor after select regex check ,replace all \r\n with nothing , all comes to one line.
if your problem was this kinda,hope be solved.

Let me check if it's the problem
On Thu 25 Apr, 2019, 2:38 AM narcotic401<EMAIL_ADDRESS>wrote:

i had that prob, i delete all break (new line) maybe this helps you:
on editor after select regex check ,replace all \r\n with nothing , all
comes to one line.
if your problem was this kinda,hope be solved.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kgretzky/evilginx2/issues/287#issuecomment-486426733,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ4FXI4ECFBFHTFMQTM55XDPSDD3DANCNFSM4HH4NVVQ
.


Scoper is ignoring closing  tag

I've been using scoper and it has been working well. But today I got a strange behavior that breaks the code. I have:
                <img src="'+imgpath+'" class="extLinkImg">
                <style scoped>
                   .extLinkImg {
                        width: 35px;
                        height: 35px;
                        margin:10px;
                    }
                <\style>
            </a>```

And I see in the console that what is being put in the head <style> is:

```#scoper-2 .extLinkImg {                        width: 35px;                        height: 35px;                        margin:10px;                    }                <style>            </a>```

It seems that scoper is not seeing the ending / in the closing </styling> tag...
I tried the same code inside a wrapping div and is the same. Do you have any clue why this is happening?

Sorry!


[Excel] (requirement sets) Update Preview and Online API lists

Pulling latest from DefinitelyTyped.

Docs Build status updates of commit 01ade21:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/requirement-sets/excel-api-online-requirement-set.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/excel-preview-apis.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 9a44f8b:
:white_check_mark: Validation status: partially passed

File
Status
Preview URL
Details

:x:Error

Details

docs/reference/requirement-sets/excel-api-online-requirement-set.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/excel-preview-apis.md
:white_check_mark:Succeeded
View

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://SiteHelp and include the error report for our team to troubleshoot

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 9a44f8b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/requirement-sets/excel-api-online-requirement-set.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/excel-preview-apis.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 21debbd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/requirement-sets/excel-api-online-requirement-set.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/excel-preview-apis.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 e95d6c0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/requirement-sets/excel-api-online-requirement-set.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/excel-preview-apis.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 7370d48:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/requirement-sets/excel-api-online-requirement-set.md
:white_check_mark:Succeeded
View

docs/reference/requirement-sets/excel-preview-apis.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


Dev/rylengel/point of interest text event handling

PointOfInterest skill update to allow user to navigate full skill with speech or events. Updated the card UI and cleaned up some bugs with tagged issues.

Issue #8
Issue #9
Issue #10
Issue #11


pass option to allow rsync to run as root on target

Using a default AWS EC2 instance and connecting with the ubuntu user I would like to be able to rsync as root so that permissions on target directories can be changed. I think in rsync itself I can pass --rsync-path "sudo rsync" and the ubuntu user would run as root. But can I pass this through the beam options in any way?

The command line option --args <string> allows passing arbitrary arguments to rsync, but it needs to be passed every time you run beam:
beam up something --args="--rsync-path 'sudo rsync'"

Alternatively, you could run pre-deployment commands on the server to set the right permissions:
{
	// ...
	"commands": [
		{
			"command": "sudo do the thing",
			"location": "target",
			"phase": "pre"
		}
	]
}

Allowing to pass rsync params on a per server config would allow this -
See https://github.com/heyday/beam/issues/53

FWIW, in the scenario @rsouthgate mentions, adding a public key to the account you want to deploy as then using that account seems like a better solution (without any other context). I'm hesitant to make it easy to run things as root, since sudo is often not the right solution.

so that permissions on target directories can be changed

Seems like this particular issue is addressed by https://github.com/heyday/beam/pull/57, so I'm closing this for now.


Fix: Updated code for TF2.0 on Colab TPU

Closes #1, #2.
Referring to documentation at https://www.tensorflow.org/guide/distributed_training#tpustrategy,
(for TF 2.0) the necessary lines of code were changed in the TPU example notebook and docs README on this repo.
This was able to fix any errors that occurred specifically by use of TensorFlow 2.0 with Colab TPUs. (CNN trained on Fashion MNIST being used as an example in this repo)

Thank you very much for making the TPU works on Colab with TF2!


fix: avoid build multi-branch at the same time to avoid github limit

Why:

get github sha1 failed when many concurrent builds

How

disperse the trigger time

/litmus

/lgtm

/review default


All property pane fields not fully visible

If I have a lot of properties and groups with in a property pane page, and they do not have show as accordion configured, then the last property field is only half visible.

👍 seen that too. Property pane should have a scroll bar if the contents are longer than window height.

It is supposed to have a scrollbar. We will investigate what is going on. Thanx for the information.

VSO 239946

This is fixed and will be available in the next release.

Closing this issue as it was addressed in Drop #2. Please reopen if necessary.


[Tooltip] immediately disappears after being shown on Firefox v52

Since Firefox update to 52 (64bit) JS-Tooltips no longer work properly. Take a look at Semantic Ui Docs page to see the issue. -> https://semantic-ui.com/modules/popup.html#tooltip
The tooltips disappear immediately after they appear.

Same problem here, just wanted to open an issue-ticket.
Firefox 52 (32 Bit): tooltip expands and hides immediately.
Firefox 47 (32 Bit) or IE 11: tooltip expands and stays visible.

Confirmed on Ubuntu 16.10 (x86_64) with Firefox 52

You probably already have this figured out, but explicitly specifying the "transform" property for the transition instead of saying "all" fixes the issue.
[data-tooltip]:before {
	opacity:0;
	-webkit-transform:rotate(45deg) scale(0)!important;
	transform:rotate(45deg) scale(0)!important;
	-webkit-transform-origin:center top;
	transform-origin:center top;
	-webkit-transition:transform .1s ease;
	transition:transform .1s ease
}
[data-tooltip]:after {
	opacity:1;
	-webkit-transform-origin:center bottom;
	transform-origin:center bottom;
	-webkit-transition:transform .1s ease;
	transition:transform .1s ease
}

Giwayume, great, it works! Thank you!

Just tested in 52.0.2 for Windows 32bit and was unable to reproduce.
Perhaps this was fixed in one of the 2 patches so far? Can anyone confirm

@jlukic Can confirm that 52.0.2 fixed the no-JS tooltips. There’s another issue now: when a tooltip is shown, in some cases it “expands” by 1px either vertically, or horizontally, here’s an example—that’s 32-bit Firefox on Windows 10. Shall we track it separately?

I have 52.0.1 on a VM and it is broken.  I have 52.0.2 on my Windows host machine and it works there.  I think that this is indeed just a browser issue which FF already fixed in a patch.

I'm testing it out now. Hopefully I can repro

I think this is fixed by FF closing issue


HDF5 is a heavy dependency

Today @qingli411 and I attempted to install Oceananigans on his laptop, but ran into a problem when the HDF5 compilation (through julia) stalled for something like 15 minutes. We were only able to proceed by completely removing the dependency of Oceananigans on HDF5 and NetCDF (after which we got the code to run!)
I think we should consider moving heavy dependencies like HDF5 and NetCDF into separate packages (say, OceananigansOutput.jl) to make a simple barebones installation of Oceananigans quick, easy, and painless.

Thanks for bringing this up, didn't realize it could be that bad. I agree it would be nice to have a barebones version of the package. Maybe we can approach this the same way we wanted to approach having "dynamic dependencies" for running examples that depend on Plots.jl (#195). That way, NetCDF.jl and HDF.jl only get installed and built if you decide to read/write NetCDF.
Out of curiousity, is @qingli411's laptop running Windows? Build times on Linux and Mac (e.g. on Travis CI and GitLab CI) tends to be quite reasonable, so I'm wondering if it's a Windows thing.
PS: I'm pretty sure this is also the reason why Appveyor is super slow #89.

It's a Mac. @glwagner, I just tried to install it on my home laptop (also a Mac) by simply add Oceananigans  and the build time of HDF5 is much shorter (~1 min). Not sure what was happening on the other laptop this afternoon...

Thanks @qingli411.
One obvious way to introduce the concept of dynamic dependencies is to break functionality out into multiple small packages (OceananigansPlotting, OceananigansOutput, etc). @vchuravy argued that this is a good philosophy for packages; perhaps even more so for a complex project like this one: we may want to keep the core as simple as possible.

I'm strongly opposed to having multiple small packages.
Maybe sub-modules could be a solution. Loading Oceananigans.Plotting can "dynamically" install Plots.jl, and loading stuff from Oceananigans.Output will dynamically install packages depending on the output writer loaded. We just have to keep things modular and neat/tidy.
If the tests are taking a while, then we could split things up into quick unit tests and more comprehensive integration tests, or we need to pay for dedicate CI resources.

I'm strongly opposed to having multiple small packages.

Why is that, given the benefits?

I'm strongly opposed to having multiple small packages.

Why is that, given the benefits?

Mainly I think we can get all the same benefits by maintaining a single unified and tidy repository with sub-modules. I don't see Oceananigans as a complex project yet, we're barely at 2,500 lines of code (minus turbulence closure operators which aren't integrated yet).
I can see reasons for having a separate repository for examples and tutorials if there are enough of them, but I don't see e.g. the output writers as being logically separate from the main code. As a stand alone package, OceananigansOutput.jl doesn't do anything useful. Something like TurbulenceClosures.jl could though.
Keeping things in tidy submodules within a single repository increases code visibility, which I think is important. When I see a package or framework spread across multiply small packages I find it hard to get an idea about what it can do.
Another nice thing is we currently have "unified versioning" so when releases occur we know everything works together. We don't have to worry about running with Oceananigans v0.x with OceananigansPlotting v0.y and OceananigansOutput#master to fix some issue.
From a development perspective, issues and pull requests are now spread across multiple repositories and we can end up with pull requests that depend on other pull requests in other repositories, e.g. when adding in halo regions the main code got refactored but so did the output writers and plotting code would change as well. We can also end up with multiple test suites that need to pass, plus possibly multiple CI pipelines to manage. So right now it's easy to make atomic changes that touch upon multiple pieces of code (and we'll probably be in this stage where we need to refactor frequently for a while).
I also don't have to git clone a bunch of repositories just to work on a simple example.
But this is getting off-topic.

https://github.com/MikeInnes/Requires.jl ?
On Fri, Jun 14, 2019 at 10:47 AM Ali Ramadhan<EMAIL_ADDRESS>wrote:

I'm strongly opposed to having multiple small packages.
Why is that, given the benefits?
Mainly I think we can get all the same benefits by maintaining a single
unified and tidy repository with sub-modules. I don't see Oceananigans as a
complex project yet, we're barely at 2,500 lines of code (minus turbulence
closure operators which aren't integrated yet).
I can see reasons for having a separate repository for examples and
tutorials if there are enough of them, but I don't see e.g. the output
writers as being logically separate from the main code. As a stand alone
package, OceananigansOutput.jl doesn't do anything useful. Something like
TurbulenceClosures.jl could though.
Keeping things in tidy submodules within a single repository increases
code visibility, which I think is important. When I see a package or
framework spread across multiply small packages I find it hard to get an
idea about what it can do.
Another nice thing is we currently have "unified versioning" so when
releases occur we know everything works together. We don't have to worry
about running with Oceananigans v0.x with OceananigansPlotting v0.y and
OceananigansOutput#master to fix some issue.
From a development perspective, issues and pull requests are now spread
across multiple repositories and we can end up with pull requests that
depend on other pull requests in other repositories, e.g. when adding in
halo regions the main code got refactored but so did the output writers and
plotting code would change as well. We can also end up with multiple test
suites that need to pass, plus possibly multiple CI pipelines to manage. So
right now it's easy to make atomic changes that touch upon multiple pieces
of code (and we'll probably be in this stage where we need to refactor
frequently for a while).
I also don't have to git clone a bunch of repositories just to work on a
simple example.
But this is getting off-topic.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/climate-machine/Oceananigans.jl/issues/284?email_source=notifications&email_token=AA27DYA55SSJKHXQBFUSJDLP2OVODA5CNFSM4HXEYRJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXXAHFI#issuecomment-502137749,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA27DYEHNERHN4MHAGJQZH3P2OVODANCNFSM4HXEYRJQ
.

Thanks @ali-ramadhan, that's helpful.
It does seem that Requires.jl can solve this issue and satisfies @ali-ramadhan's desire for verticality as mentioned in his comment. We could perhaps isolate the output functionality into a submodule (eg, Oceananigans.Output) that is loaded only when HDF5 (for example) is present. Ditto for Oceananigans.Plotting.
I've changed the name of the issue to be more descriptive of the general issue we are discussing (heavy dependencies).

This is resolved, eh?

I think so. HDF5 is no longer a dependency and we can include plotting in the examples using the import pattern you use in deepening_mixed_layer.jl.


Fixed description of the velocity covariance matrix

This change does not affect the layout, only comments are changed.

Yes, true.


License

This looks like a great game and I'm hoping to use it for one of my projects. Would you be open to adding an open source license (e.g. MIT, Apache 2.0, BSD) ?

Oh man, I feel so guilty that I didn't add it from the beginning. Just did it. Enjoy. Send me a link to your project when it will be ready if possible :)


datadog: add dropdown to select host

Description
Adds two dropdown in the preference screen to select the host of datadog api and web for US and EU
Type of change

Bug fix / improvement for somebody else's extension. Extension author: @kudrykv

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast

Also, you should add yourself to the contributors' list 🙂

Added screenshot to the pull request description

🎉


[BUG] after scanning X amount of items, scanner will change tasks or interrupt (+ incorrect scanned quantities)

Current Behavior
After scanning a certain amount of items the software will simply swap to the next scan task (eg. scans only a few artifacts then goes to scan materials), this most commonly happends in the material section, where I have failed to have a successful full scan of all my meterials.
Sometimes I also get this Error:

The quantities shown in the export files are also incorrect.
Expected Behavior
The scanner to not skip rows or items
Reproducing a Behavior
I have no idea how to reproduce the behaviour, and I am unable to include a screen recording since a new issue has risen which I will report shortly.
I am able to provide an export file (inside a zip left in the evidence section) of one of my attempts which resulted in the previously mentioned error.
Device OS
Windows 10
Genshin Impact Version
3.0.0
Inventory Kamera Version
1.3
Screen resolution, screen mode, and UI scale
1920x1080, windowed
Additional notes and remarks
No response
Evidence

genshinData_GOOD_2022_09_07_10_11.zip
Preflight Checklist

[X] I have checked for similar issues in the issue page, and I have not found any similar to mine.
[X] I am using the latest version of the scanner.
[X] I tried setting the scanning delay to maximum, and it still doesn't work.
[ ] I have attached the video recording to the bug report.
[X] I have attached the error log to the bug report.
[X] I am available to later explains the issue.
[X] I have disabled all screen filtering software or plugins (i.e. HDR, Image Sharpening) while scanning.
[X] I use default in-game keybindings or have configured keybindings for the scanner.

Reporting the same problem....seems to happen in the materials section.   Everything is going fine then exits out part way through and then tries to continue on the same section.  Artifact scanning was fine though...just materials.  Noted on this ticket since the issue seems to be similar/same.  PC capture at 2K
Error Log:
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at InventoryKamera.ArtifactScraper.ScanArtifacts(Int32 count)
at InventoryKamera.InventoryKamera.GatherData()
Could not determine Jean's level. Setting to 1.
Failed to parse quantity for TuskOfMonocerosCaeli
Sequence contains no elements
at System.Linq.Enumerable.Aggregate[TSource](IEnumerable1 source, Func3 func)
at InventoryKamera.MaterialScraper.ScanMaterialCount(Rectangle rectangle, Bitmap& quantity)
at InventoryKamera.MaterialScraper.Scan_Materials(InventorySection section, Inventory& inventory)
at InventoryKamera.InventoryKamera.GatherData()
Sequence contains no elements
at System.Linq.Enumerable.Aggregate[TSource](IEnumerable1 source, Func3 func)
at InventoryKamera.MaterialScraper.ScanMaterialCount(Rectangle rectangle, Bitmap& quantity)
at InventoryKamera.MaterialScraper.Scan_Materials(InventorySection section, Inventory& inventory)
at InventoryKamera.InventoryKamera.GatherData()

This issue is quite old. Please let me know if this still exists on recent versions


Request to add my school

WebSite: https://www.deliguori.edu.it/

@L3gendYTs First stage of verification passed, official domain is deliguori.edu.it as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@L3gendYTs Pull request merged. Thank you.


WIP: group_by to evoked.plot_image

And the last one for evoked.plot_image from #5170
Adds a group_by option to evoked.plot_image that allows feeding a dict to axes. I.e., for making a channel selection with make_1020_selection.

The whatsnew entries and python_reference entries are here @agramfort

With this as the last of the 3 patches, it is very easy to make plots like this:

rois = make_1020_channel_selections(evoked.info, midline="12z")

fig, axes = plt.subplots(nrows=3)
axes = {roi: ax for roi, ax in zip(rois, axes.flatten())}
evoked.plot_image(group_by=rois, axes=axes, show=False, show_names='all', colorbar=False)
plt.colorbar(axes["Left"].images[0], ax=list(axes.values()), shrink=.3)

https://8265-1301584-gh.circle-artifacts.com/0/html/auto_tutorials/plot_stats_cluster_erp.html#sphx-glr-auto-tutorials-plot-stats-cluster-erp-py
Example looks good.

Would be super cool if we could get this merged by the weekend :)

ok to merge when Green

@cbrnr fine?

You wanna wait for @mmagnuski?

@mmagnuski would be super nice if you could provide some comments in the next hour or so ...

Merge :)

Thanks @jona-sassenhagen

Great, thanks!

@jona-sassenhagen
Sorry, I was away from github for some time and didn't check notifications.
I am still alive and will be back in about a week. :)


ubuntu22.04 install llvm faild

Description
https://github.com/qicosmos/cinatra/actions/runs/8813963128/job/24192836432?pr=563
E: Failed to fetch https://packages.microsoft.com/ubuntu/22.04/prod/dists/jammy/InRelease  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: The repository 'https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease' is no longer signed.
Repository: 'deb http://apt.llvm.org/jammy/ llvm-toolchain-jammy-17 main'
Description:
Archive for codename: llvm-toolchain-jammy-17 components: main
More info: http://apt.llvm.org/jammy/
Adding repository.
Adding deb entry to /etc/apt/sources.list.d/archive_uri-http_apt_llvm_org_jammy_-jammy.list
Adding disabled deb-src entry to /etc/apt/sources.list.d/archive_uri-http_apt_llvm_org_jammy_-jammy.list
+ apt-get update
Get:1 file:/etc/apt/apt-mirrors.txt Mirrorlist [142 B]
Get:7 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease
Err:7 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease
  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
Hit:2 http://azure.archive.ubuntu.com/ubuntu jammy InRelease
Hit:3 http://azure.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 http://azure.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:5 http://azure.archive.ubuntu.com/ubuntu jammy-security InRelease
Hit:8 https://ppa.launchpadcontent.net/ubuntu-toolchain-r/test/ubuntu jammy InRelease
Hit:6 https://apt.llvm.org/jammy llvm-toolchain-jammy-17 InRelease
Reading package lists...
E: Failed to fetch https://packages.microsoft.com/ubuntu/22.04/prod/dists/jammy/InRelease  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: The repository 'https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease' is no longer signed.

Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Runner Image
  Image: ubuntu-22.04
  Version: 20240422.1.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240422.1/images/ubuntu/Ubuntu2204-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240422.1

https://github.com/qicosmos/cinatra/actions/runs/8813963128/job/24192836432?pr=563
Is it regression?
https://github.com/qicosmos/cinatra/actions/runs/8794320506/job/24133571446
Expected behavior
install clang-17 and clang++-17 ok.
Actual behavior
install failed
Repro steps
git action script:
      - name: Install newer Clang
        run: |
          wget https://apt.llvm.org/llvm.sh
          chmod +x ./llvm.sh
          sudo ./llvm.sh 17

Duplicate of https://github.com/actions/runner-images/issues/9735

How to solve the problem? just happed today


Classes of the com.kazurayam.materialstore.base.materialize package should be moved out of the materialstore project

The packagecom.kazurayam.materialstore.base.materialize contains the following classes:
$ tree com/kazurayam/materialstore/base/materialize
com/kazurayam/materialstore/base/materialize
├── MaterializingPageFunction.java
├── MaterializingPageFunctions.java
├── MaterializingWebResourceFunction.java
├── MaterializingWebResourceFunctions.java
├── SimpleTargetCSVParser.java
├── StorageDirectory.java
├── Target.java
├── TargetCSVParser.java
├── URLDownloader.java
└── URLMaterializer.java

These classes are NOT used by other classes in the materialstore project.
These classes are designed for the UI test projects using Selenium WebDriver or Katalon Studio.
These classes make the materialstore project dependent on miscellaneous external jars (such as, Selenium-java, Apache commons-csv).
It is a good idea to move these classes into the inspectus project. The inspectus project is much closer to the UI test projects.

It should be moved to com.kazurayam.inspectus.materialize package.

Should plan carefully.
If I move the materialize.* classes from the materialstore project to the inspectus project, the VisualInspection* projects will break.
I need to change the VisualInspection* project to use the inspectus project first. After that, I can move the materialize.* classes.

The issue #365 indicates that the classes in the com.kazurayam.materialstore.base.materialize package are not very matured. They need to be refined and tuned more.

I will make a copy of com.kazurayam.materialstore.base.materialize package in the

inspectus4selenium project

Then I will remove the package at ver0.13.1.
Then I will change the VisualInspection* project to use the inspectus4selenium and the materialstre0.13.1.

done


Fix the sign-out redirect URI

The okta backend profile that is active for local development, test and production environments is always pointing to http://localhost:8080 as the sign-out redirect URI. Fix this by setting the correct URI for production environment

f30ac900fc43000e2203c4d987866921560fb334 adds the needed variable that is filled in different ways according to the environment:

GitHub secrets for the pipeline
JVM arguments for the local environment
Heroku config vars for the production deployment


Refactor/reduce complexity

I removed the pr_to_unp parameter that lets the user select how to order the different demographic groups (from most privileged to most unprivileged or the reverse) for two reasons:

It is easy for the user to reverse the order once we have it.
It adds so much complexity to the code.

I also moved the initial computation of the differences or ratios to and independent function (_compute). There are two functions that rely on this method directly (summary and rank). This refactor optimises the code and avoid doing unnecessary competitions that were present in the previous implementation.

Follow PEP8:

line break for long string (use implicit string continuation): wtf is that thing L.62 of metrics.py
Metric should be an ABC
all your classes should inherit your ABC Metric, (FairnessMetricDifference is a Metric, right?)
make your code breath, don't be scared of blank lines
stop using attributes everywhere since you return the value of the attribute anyway (see self.ranking)
ConfusionMetrics.call is awful to look at, refactor and improve. This is not clear what it does.

Applied line break for long strings.
Added ABC abstract class and abstract method in Metric.
Metric, FairnessMetricDifference and FairnessMetricRatio are different base classes that gets inherited by the actual metrics available for the user.
Metric: is for performance evaluation for the different demographic groups.
FairnessMetricDifference: is for fairness metrics that are based on difference for calculating disparity.
FairnessMetricRatio: is for fairness metrics that are based on ratio for calculating disparity.
Added line breaks for readability.
I try to use attributes when I have to access the variable in another method. (Ex: self.ranking is returned by .rank() method and it is used in the .is_biased() method). In other places I do it because of mypy complaints.
Refactored ConfusionMatrix.__call__() and added a comment to explain.

https://github.com/datategy/Fair-Mango/pull/10/files#diff-f60460593beef4b2e9574ac4bd0492afb517eaac1129c634e527dd38109471fdL75-L78
refactor all these functions by using kwargs and silencing mypy


Problems with Delete CV

@MajaDolinar Right now the Delete CV works that it tries to delete all versions with major.minor.x number, but this is not correct as every new translation creates whole new bundle also with patch number included. Actually this approach also breaks the whole system down. It should delete only bundle with major.minor.patch.

@MajaDolinar The delete functionality should be deployed on the dev/staging already. You can test it. Right now it should delete only whole bundle x.y.z (Sl with TL(s)) or of course only TL of specific version.

Closing, resolved.


[BACKLOG-24625] Fix for using variables in json sampling

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/json/core,plugins/get-fields/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/json/core,plugins/get-fields/core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/get-fields/core/src/main/java/org/pentaho/getfields/types/json/JsonSampler.java
  plugins/json/core/src/main/java/org/pentaho/di/ui/trans/steps/jsoninput/JsonInputDialog.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.getfields.types.json.JsonSampler

Line Change: -1.3% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/plugins/get-fields/core/src/main/java/org/pentaho/getfields/types/json/JsonSampler.java

:heavy_exclamation_mark: Unused import - java.io.File. at Line: 36 Column: 8

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/json/core,plugins/get-fields/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/json/core,plugins/get-fields/core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/get-fields/core/src/main/java/org/pentaho/getfields/types/json/JsonSampler.java
  plugins/json/core/src/main/java/org/pentaho/di/ui/trans/steps/jsoninput/JsonInputDialog.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.getfields.types.json.JsonSampler

Line Change: -1.3% :small_red_triangle_down:

@ddiroma


Add package about

Not sure if your intention is for this to be a library and a binary package. You can just write skipExt = @["nim"] in your .nimble file and then you won't need this weird aboutpkg folder (you'll be able to rename to about)


A wave sampler replacing the MIDI output

This is a draft with working drum sound, not really merge-able.
It needs a better drumkit sample set. I just grabbed what I had to make it work.
The sampler is ripped from guts of the Hexpress app and adapted for LOVR.
It doesn't support multiple samples per same trigger, but sampler already supports velocity. A rich drumkit sample set could have multiple samples per kit element and they would be used for different note velocities. The included sample set doesn't have them :(
The sampler has ADSR enveloping which is effectively disabled in the sampler instance settings. It would be useful if you wanted to expand to synths. There is also unused pitch calculation for tonal instruments, these drum samples just have the default pitch.
Code partially implements the same API as RtMidi Lua API as used in the drummer app. For now it is just plugged in place of MIDI driver, but there should probably be a "bus" in between to duplicate the MIDI messages between the two.
Also, I noticed sounds are triggered twice; IMO the second trigger should be a noteOff message instead. You cannot hear them with the sampler because their velocity is zero, but they take up from the sampler pool.
Does it work on your side?

Nice work, thank you! It works on my side (with just a minor fix on line 82: changed Vec3 to lower case vec3).
I was working on supporting build-in sounds but got stuck on trying to find a free drumkit that includes tip/edge & center/rim samples for cymbals/drums, and multiple samples per sound, as you mentioned.
About the sounds getting triggered twice: Since I was only sending MIDI, a noteOn with zero velocity is translated to noteOff effectively, so it didn't matter. But I'll have to change it to work with the sampler (so that MIDIctrl.noteOff gets called).
The implementation I was working on relied on a user preference (in the ui) to either work in MIDI-out mode or build-in sounds. I think it makes more sense this way.

You are correct, both note off and vel=0 note on should stop the sample, I fixed this on the sampler side.
The UI user preference is of course a necessary step. I was proposing a virtual MIDI bus (or router)  because this is the usual mechanism in DAWs. With such decoupling you could also hook up an external MIDI footswitch as additional MIDI source to be used for the kick drum trigger.
Naturally your own implementation will work best for maintaining the code and supporting the features you would like to see.

I'll have a working implementation ready in a couple of days. The hard thing was finding a free drumkit with enough samples per piece. Again thank you so much for the help!

Thanks a lot for the original idea, I finally did an implementation. It isn't as sophisticated but it will do for now. Thank you again!


HARP-9275 DisplacedMesh to support picking of elevated meshes.

Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

Codecov Report

Merging #1417 into master will increase coverage by 0.07%.
The diff coverage is 54.66%.

@@            Coverage Diff             @@
##           master    #1417      +/-   ##
==========================================
+ Coverage   55.63%   55.70%   +0.07%
==========================================
  Files         258      259       +1
  Lines       23812    23878      +66
  Branches     5327     5348      +21
==========================================
+ Hits        13248    13302      +54
- Misses      10564    10576      +12

Impacted Files
Coverage Δ

@here/harp-mapview/lib/VisibleTileSet.ts
73.36% <ø> (+0.06%)
:arrow_up:

...re/harp-mapview/lib/geometry/overlayOnElevation.ts
40.00% <0.00%> (-3.14%)
:arrow_down:

@here/harp-mapview/lib/geometry/DisplacedMesh.ts
43.75% <43.75%> (ø)

@here/harp-mapview/lib/Tile.ts
72.75% <84.61%> (-0.21%)
:arrow_down:

@here/harp-mapview/lib/DecodedTileHelpers.ts
57.05% <87.50%> (+0.50%)
:arrow_up:

...e/harp-mapview/lib/geometry/TileGeometryCreator.ts
41.01% <100.00%> (+0.20%)
:arrow_up:

@here/harp-mapview/lib/poi/PoiRenderer.ts
11.25% <0.00%> (ø)

@here/harp-omv-datasource/lib/OmvDataSource.ts
55.73% <0.00%> (ø)

@here/harp-datasource-protocol/lib/Techniques.ts
71.96% <0.00%> (ø)

@here/harp-datasource-protocol/lib/DecodedTile.ts
26.98% <0.00%> (ø)

... and 9 more

Continue to review full report at Codecov.

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

@harpgl-bot retest this please

@harpgl-bot retest this please


feat: test

:tada: This PR is included in version 0.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


proxychains{,-ng}: swap priority 4 and 5 in get_config_path

Description of changes
Prefer /etc/proxychains.conf to the one in Nix store. Fixes #136093.
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)
[ ] Tested, as applicable:

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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

@ofborg build proxychains proxychains-ng


ur gay

I'm working on a page for it just wait a bit

wait how did that happen, I only edited one thing

becus github gay. are we moving to the .limited domain now? I might have a buyer xd

yes you want the thing to be called succ limited remember

true. should i make a temp site for it?


Inconsistent license of file tools/elfread.c

The file tools/elfread.c mentions its license as GNU GPL. However, the top-level document addresses the MIT License. Would it be feasible to apply the consistent MIT License for elfread?

Thank you for reporting. Fixed.


[master] Bump Mesos to nightly master 3886e2a

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/9f6ccbd41a55846e54297ecb31fddbeee3be50c9...3886e2a0b77a8f8233d95f785ddb55403e638677
https://github.com/dcos/dcos-mesos-modules/compare/885a3c01d048c232f373c832f61403b7578ac605...17e36a905c27008f0c83be44f52bf05091e5fd80

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee


Install HWRaid packages as part of rpc_support

Support has requested that RPC installations receive the most common set of hardware RAID card utilities for diagnostic purposes beyond what is currently installed by default with the OS. This PR introduces two plays which add the RAID utilities package repo and install the megaraid and lsiutil packages by default.
The utilities installed by default are the two most common for RPC installations, but can be overridden with the variable hwraid_apt_packages.
NOTE As of right now, these plays are not running as part of the rpc_support role. I would like support to test these plays in several scenarios before we made the decision to change this. I'm worried that there may be situations where detecting the presence of a tool triggers checks against a RAID card that may not be present. If that is the case, then we will simply require that support override the packages variable at run time, otherwise no packages will be installed at all.
Partial-Fix: #186

glad to see it has keys, seems fine at first glance

:+1:

-1 I'm not clear how this is expected to be used. Assuming the implementation is good, I would say the commit needs a more detailed message and documentation.

@git-harry Thanks for the feedback. I've updated the message. Mind giving it a look?

@tomc603 these are task files not plays/playbooks. How are support expected to run this code when they don't link to main? As it currently is I believe support would need to write their own playbook to make use of this code. What are they testing it on? It sounds like you're trying to introduce an experimental feature, I'm not sure we've taken that approach before. The pull request message has been updated but not the commit message.

@git-harry Sorry, I'm constantly using the wrong words when it comes to tasks inside roles vs plays vs everything. Fixed.
This isn't experimental, support currently use these utilities. Where my concern lies is in scripts that individuals may have which are "too smart"- They check for the presence of a utility and presume that it being there means the hardware it supports is also present.
I suppose this is just me being too gun shy. I'll edit this commit so that the tasks run and the packages are installed. The issue this addresses did request the two most common utilities, so this really is just a case of me overthinking the problem and trying to solve a situation which may not even exist.

@tomc603 ah, okay I understand now. Yeah, I wouldn't over-engineer this. Support have asked for these packages. If it introduces a bug we can deal with it then.

Ok, I think I un-broke the reflog on my side, so everything looks good. @git-harry I've added changes to the tasks/main.yml file to execute the tasks in the raid_preinstall.yml and raid_install.yml files as we discussed. Also cleaned up some of the task names, limited execution to hosts only, and squashed the commits so the PR is clean.

:+1:

@BjoernT Does this look good for you? Just want support eyes on it to be sure.

@BjoernT ping, just need an ack before I push the button

Generally ok but how about hosting the tools on the Rackspace mirrors ?

I think that's a change that'll be needed down the line, merging


Problems with Prism

When launching with Prism Launcher, the game crashes before it can load up. The message that comes with this is the following; "The java binary "" couldn't be found. Please fix the java path override in the instance's settings or disable it."

This is an issue with your java install, please download java 8 and change your java installation in your instance settings, for more help ask the folks at PrismLauncher on how to do this, this is not an issue with the mod pack.


install issue

I found this sample very useful , especially the use of webpack.
However I am facing an issue when i do npm install after cloning .
P.S,  this is happening on a corporate network only. I dot have this issue on my personal machine outside of the corporate network. see the console output below for more info , any idea ?

typings install

typings WARN badlocation "github:Esri/jsapi-resources/3.x/typescript/arcgis-js-a
pi.d.ts" is mutable and may change, consider specifying a commit hash
typings WARN deprecated 9/14/2016: "registry:dt/core-js#0.0.0+20160524134847" is
deprecated (updated, replaced or removed)
typings WARN deprecated 9/7/2016: "registry:dt/dojo#1.9.0+20160521151917" is dep
recated (updated, replaced or removed)
typings ERR! message Unable to connect to "https://raw.githubusercontent.com/Esr
i/jsapi-resources/master/3.x/typescript/arcgis-js-api.d.ts"
typings ERR! caused by self signed certificate in certificate chain
typings ERR!
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: typings install
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'typings i
nstall'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the angular2-esri-example
package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     typings install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs angular2-esri-example
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls angular2-esri-example

@Abexdatl I'm glad you found this useful, and I'm sorry that you're having that install issue.
Looks like your corporate firewall doesn't like the cert on https://raw.githubusercontent.com/Esr
i/jsapi-resources/master/3.x/typescript/arcgis-js-api.d.ts
However, I no longer use Angular (no TypeScript) day to day, so I'm not sure if the way this repository is getting the types is the most up to date way.
You might try installing them via npm as documented here.
Although I'm not actively maintaining this repository, if you do find a better way to install the types I'd gladly accept a pull request.


Update the plugin build

Changes:

update wrapper and wrapper used maven (3.9.2)
set proper prerequisites (aligned with deps)
put all (even transitively incoming) maven deps to proper provided scope
align maven-plugin tools (annotations and plugin) to latest 3.9
migrate off from dead build-api
remove bad (non existent) config
gather all plugin versions to single place (there should be not plugin versions scattered across, simpler to maintain)

Note: downgraded the snapshot dependency to simplify my own life, if this PR is to be merged, the snapshot dependency change should be undone.

@cstamas Can you please go ahead and undo the snapshot dependency change so that the submitted builds will run correctly? I had published the ci.common snapshot to sonatype, so I am not sure why it should complicate things locally to run with it?

done (I use locally MRM)

So I see the following in one of the build logs. I don't understand where some of the old versions are coming in? Should you add your workflow changes to this PR to resolve this? @cstamas

Given warnings are emitted, the maven 3.9.2 seems to be used, but from where come your plugin versions (and those are ancient ones, m-install-p 2.5.2?) I have no idea, as no Maven 3.9.x was shipped with 2.x plugins

Updated PR w/ latest main (workflow) updates


Model changes w.r.t. #1773

Model changes w.r.t. #1773
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPdocs
[x] Unit testing, with >80% coverage
[x] Conforms to style guide

Removing the true in toRawArray will just cause other issues with unintentional overwrites of data.
I don't see how this fixes the required rules at all. Can't accept.

In the stated issue #1773, he is trying to save the null value in the database which expected to throw an error of required field.
But when data is passed from insert method to classToArray, it expects to return only changed values.
The previous and current value of the property is null, hence it is not returning the property as changed value.
Hence error is not getting triggered.


6TA8

Use the preview tab to see the example given below. Edit the relevant information and preview the changes before submitting. You may delete these instructions.

Key
Value

ID
6TA8

Source
Vaaran Bhai Gurdas Ji

Page
25

Line
Awpu gxwie ivgucxw; Awpu gvwey Awpu iswxY [

Correction
THIS ≠ THAT

PROOF (EDITION)
Image:

Correction:
iswxY ≠ is\wxY
Proof:
Vaaran Bhai Gurdaas Ji | November 2011 | Shamsher Singh Ashok | SGPC, Sri Amritsar
Image:


Support dogstatsd origin detection for UDP traffic

I've requested this before through help tickets (156973 and 158135) but I think posting on github to get public +1s will help move this along.
The agent running in kubernetes could gather a lot of useful data from the metrics it takes in via DogStatsD, UDS, Autodiscovery, or another method that I'm not aware of yet, but it doesn't. Metrics from many pods in the same deployment come in and clobber each other. This is a never ending source of misery for my company, and it's making it hard for us to port applications to kubernetes.
What I ask for is that pod and container metadata, such as the cluster name, node name, pod name, container name, etc., as well as labels and a documented set of annotations, be collected by the agent and associated with metrics coming from each pod. I reckon as far as node and pod metadata goes it should be pretty simple, just collect the list of nodes and pods periodically and when a metric comes in from wherever, associated the source with the correct node/pod. Container metadata might be difficult and I understand if you can't provide that, but node/pod metadata is absolutely crucial.
We need this feature so that we can differentiate timeseries coming from different pods and relate that to metrics about nodes. For example if requests per minute starts decreasing from pods on one particular node we can correlate that with resource utilization on the node. Of course we also need cluster name since pod names aren't unique across clusters. In some cases we can use our entrypoint scripts and env vars to get some of this data added to the list of tags we send over statsd but this doesn't cover every case and honestly it's a lot of boilerplate for something the agent should be doing.

Hello @2rs2ts,
Does "metrics coming from each pod" refers to dogstatsd custom metrics? You can expect the following tags to be added to your custom metrics:

AWS/GCP/Azure instance labels, by enabling the crawler integration(s)
host tags, sent by the agent in the host metadata payload:

kubernetes node labels whitelisted in the agent configuration
Agent host tags, set via the DD_TAGS environment variable or the yaml configuration option

container tags, when using origin detection on Unix Socket traffic
ad-hoc tags specified at metric submission

Since Kubernetes does not expose a cluster name, or cluster-level tags or labels, users usually set them as host tags, either configured in the Agent daemonset or assigned to the nodes.
In 6.3.3, in a Kubernetes cluster, the following container tags will be automatically collected by origin detection (the same as are added to Autodiscovery checks):

kube_namespace, kube_deployment, kube_daemonset, kube_stateful_set, kube_container_name
docker_image, image_name, image_tag
pod labels and annotations whitelisted in the agent configuration

We have changes in coming releases to address custom metrics emitted by containers, and we plan to add container_id, container_name, and pod_name in future releases. In the meantime, if any of the currently supported tags are not working, we’ll be happy to help you get them successfully applied to metrics. I recommend support tickets as a medium though, as we’ll need to exchange flares and configuration details.

@xvello Thanks, unfortunately there is a memory leak in 6.3.x so we are stuck not being able to upgrade, fortunately I think our team is going to get on a call with an engineer about that. When we can upgrade I'll test those things and give feedback on whether they're sufficient or not. I appreciate you spelling that all out for me, I wish it was documented on the site though

Hi @2rs2ts ,
I listed 6.3.3 as a habit of listing latest, although all the features I listed were already in 6.2.1. We should be all set to enable them already.
As for the documentation, we revamped https://docs.datadoghq.com/ early this year to increase discoverability of the features, but we still have room for improvement. If you have the time, more detailed feedback on what pages you expected to find links to these features would be very valuable.

@xvello actually we are already using 6.2.1. Sounds like the tags we need are for UDS/AD only, but not DogStatsD. When you said "We have changes in coming releases to address custom metrics emitted by containers" I assume you meant that includes statsd metrics?

@xvello Upon upgrading to 6.4.2 we don't see those tags with the UDP-based StatsD protocol so I suppose the answer to my previous question is no, you didn't mean statsd metrics.
Do you intend to add these tags with the UDP-based metrics? And if so, when?

Hello @2rs2ts
We investigated adding origin detection to UDP traffic, but could not find a consistent way to reliably link a packet to its source container. We cannot rely on the source IP, because there are many situations where multiple containers may share a single IP. For example in Kubernetes, all containers in a pod share the same network interface. hostNetwork mode can further complicate this as well.
This is why we are focussing our efforts on Unix sockets that allow dogstatsd to reliably detect the origin container and tag submitted metrics accordingly.  We do not currently have a plan to bring origin detection to UDP metrics, but are open to reconsidering if we find a reliable solution for linking a container to an incoming udp packet.

@xvello Is there a reason why you cannot provide a reduced feature set for UDP origin detection? For example, maybe you can't detect which container is sending the metrics, but you can tell which pod is. And you can just not support metrics submitted from pods with host networking (which is something people should not be using that often anyway.)

Hi @2rs2ts,
I renamed this feature request, and registered it in our backlog. Unfortunately, I cannot give you a time estimate for the moment.

@ludwikbukowski container_id, container_name and pod_name are not added as tags for Autodiscovery and Origin detection, for now.
I recommend you open a support ticket so we can investigate alternatives and inform you when we make progress on this.

Thanks @xvello, it's fine if you can't give an ETA right now. I'm glad we were able to get this hashed out and triaged! Again, thank you!

Just brief explanation why I'm lacking the feature (just FYI, as a feedback).
I run many pods(X) that run on many nodes(Y, Y<X).
I report the same metrics from the pods. Metrics are being sent to datadog-agents(Y) that shares network configuration with the host. If it happens, that two datadog-agets from the same host recieve metric to report, the metric is being overwritten.
Only tagging the metric with some pod identifies prevent it to happen

^ that is exactly my issue and it's something that I honestly expected I'd get out of the box

@xvello we use kube-router and for us the source IP would reliably identify the source. It would be great to be able to turn on tagging in dogstatsd based on source IP for users where this would be effective. In our case we don't have UDS support in the library we're currently using, so we're stuck with UDP for right now.

Does this with with origin detection? https://github.com/DataDog/datadog-agent/tree/master/Dockerfiles/dogstatsd/socat-proxy

@killcity indeed, using socat as a UDP -> UDS proxy is supported. It is documented here and this image has been created to illustrate this methodology.
Of couse, if socat runs as a sidecar container, the container tags will match it, but all pod tags will be consistent.

I'm running socat as a sidecar and origin detection is indeed working. The problem im running into is visibility down to specific pods. I'd like to see per-pod metrics instead of having them all lumped under one tag. Is this possible? I noticed the docs said that pod name and container name were not included. I think this is a mistake.

@hkaj can you please explain what "pod-level tagging" means? Your link does not explain it.

@killcity could you share your sidecar implementation? I'm running the same setup but can't get the process up because the socket isn't mounted in time. Are you introducing a wait?

@ashwin-subramanian Heres a simple example:
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  labels:
    run: myapp
    env: prod
  name: myapp
  namespace: myapp
spec:
  serviceName: "myapp"
  replicas: 1
  selector:
    matchLabels:
      run: myapp
  template:
    metadata:
      labels:
        run: myapp
    spec:
      securityContext:
        fsGroup: 1000
      volumes:
        - name: dsdsocket
          hostPath:
            path: /var/run/datadog/
        - name: data
          emptyDir: {}
      containers:
      - name: myapp
        env:
          - name: DATADOG_HOST
            value: "<IP_ADDRESS>"
          - name: DD_AGENT_HOST
            valueFrom:
              fieldRef:
                fieldPath: status.hostIP
          - name: DD_AGENT_PORT
            value: "8126"
          - name: DD_AGENT_SERVICE_HOST
            valueFrom:
              fieldRef:
                fieldPath: status.hostIP
          - name: DD_AGENT_SERVICE_PORT
            value: "8126"
        image: myrepo/myapp:latest
        volumeMounts:
        - name: data
          mountPath: /data
          readOnly: false
        imagePullPolicy: Always
        securityContext:
          privileged: true
        readinessProbe:
          httpGet:
            path: /
            port: 9090
          initialDelaySeconds: 360
          periodSeconds: 5
          timeoutSeconds: 10
        livenessProbe:
          httpGet:
            path: /
            port: 9090
          initialDelaySeconds: 360
          periodSeconds: 5
          timeoutSeconds: 10
        resources:
          requests:
            cpu: "15"
            memory: "32000Mi"
          limits:
            cpu: "15"
            memory: "32000Mi"
      - name: socat
        image: datadog/dogstatsd-socat-proxy:beta
        imagePullPolicy: Always
        ports:
          - containerPort: 8125
            name: dogstatsdport
            protocol: UDP
        volumeMounts:
          - name: dsdsocket
            mountPath: /socket
        resources:
          requests:
            cpu: "100m"
            memory: "100Mi"
          limits:
            cpu: "100m"
            memory: "100Mi"
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      accessModes:
        - ReadWriteOnce
      resources:
        requests:
          storage: 20Gi
      storageClassName: mystorageclass

Hi all, quick (belated) update: this was released in agent 6.10, it supports k8s only for now (we have plans for swarm support, but would welcome external contributions if anyone needs this urgently). Please refer to the documentation for details about how to use it, and which client library support it: https://docs.datadoghq.com/agent/kubernetes/dogstatsd/#origin-detection-over-udp

Thats great news!


o=object should not be a file classification.  instead use p=product type and s=sum type

It allows support for unions / variants
More inline with languages that support both concepts.
I went down the wrong trail by choosing object thinking in a product type only mindset.
any time you are making a class, a struct, or a union, you are really creating a new type.
So we have p/s for mathematically backed types and g for data/functions not within a type

we use g,p,s now


Added support for Swarm Mode

Description
Added support for Swarm Mode which starts the necessary processes in order to be part of the Petals Swarm. The User can Enable the mode from Settings. Tauri will spawn a thread that installs the dependencies and runs the python process.
The PR contains all the building blocks in order to implement the complete POC functionality.
Limitations

UI/UX must be drastically improved. No CSS changes have been made.
It currently works only if the User has Python installed on its machine.

@tiero @casperdcl @sekulicd @Janaka-Steph please have a look.

@casperdcl @sekulicd @Janaka-Steph @tiero instead of passing "--public_name", "prem-app" we should pass the User username/identifier (like a nostr pubkey) :)

could just use current username

Good point. I ll apply the changes you suggested above.

I ll address the remaining points in this PR soon. I want first the new services to be working and then I ll move on with this. :)

Missing

[ ] Give the User the possibility to decide which model to contribute to.
[ ] Check if the User can run Swarm mode (only available for Mac users), otherwise don't enable the functionality.
[ ] Give the User the possibility to decide how many blocks to contribute giving some tooltips in terms of how much memory is required per block.

Great job @nsosio, looks good to me. @Janaka-Steph it requires some UI love.
@nsosio I suggest that we also handle the missing pieces:

[ ] Give the user the possibility to pass a name (default: prem-app).
[ ] Python installation as suggested by @casperdcl here.

Yes I'm going to handle also those remaining points🙂 do we want to let the user decide the name or use the whoami output?

I think whoami simplest for now. Let someone open a feature request/PR for customisation later :D

I was proposing to let the user decide and have a default fallback with prem-app. In this way, in the monitor, the Prem App name will appear.

$(whoami)@prem

If they click on<EMAIL_ADDRESS>it will open the mail client? or not? And that email will actually not exists.

Or just whoami@premAI :) not meant to be an email just classic username@host namespacing

Ok, good for me CC @nsosio

I tried cargo tauri dev on Mac M1 and I got this error
cargo tauri dev
     Running BeforeDevCommand (`npm run dev`)

><EMAIL_ADDRESS>dev
> vite

  VITE v4.4.7  ready in 437 ms

  ➜  Local:   http://localhost:1420/
  ➜  Network: use --host to expose
        Info Watching /Users/tiero/projects/prem/prem-app/src-tauri for changes...
   Compiling prem-app v0.0.30 (/Users/tiero/projects/prem/prem-app/src-tauri)
error: failed to run custom build command for `prem-app v0.0.30 (/Users/tiero/projects/prem/prem-app/src-tauri)`

Caused by:
  process didn't exit successfully: `/Users/tiero/projects/prem/prem-app/src-tauri/target/debug/build/prem-app-6084577c84f4c996/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-env-changed=TAURI_CONFIG
  cargo:rerun-if-changed=tauri.conf.json
  cargo:rustc-cfg=desktop
  cargo:rustc-cfg=dev
  path matching bin/python/petals-aarch64-apple-darwin not found.
🚀 A new version of Tauri CLI is available! [1.4.0]

I fixed with npm run prebuild that I noticed has been added in this branch. Please add it to the README too

@filopedraz, @tiero should we update it as user_name@premAI or keep it as user_name? Where user name is what specified by the user (with default prem-app)

@filopedraz, @tiero should we update it as user_name@premAI or keep it as user_name? Where user name is what specified by the user (with default prem-app)

We should start with a default name taken from user-space ie. $whoami@premAI, and not sure how much worth is to allow user to change it 🤔

@tiero it will be a public name. User should be able to provide what they want.

I did little tweaks to UI and compiled also aarch64 version to test for Apple SIlicon, please pull before commiting more work

@tiero it will be a public name. User should be able to provide what they want.

Ok I will reintroduce the Input, but once they start the swarm

Starting the Swarm on any model crashes once click on Start
https://www.loom.com/share/43213eaf03b14a8a840488cf91150a1b

enabled swarm-mode only for aarch64
petals sidecar only for aarch64
added get_username Tauri command retrieving whoami
moved script for petals binary to scripts

CC @filopedraz @casperdcl @tiero

@nsosio LGTM. @tiero can you update the UI accordingly?

Currently does not work on my Mac M1, investigating. @filopedraz If you have time to test on your device let me know if you experience the same.

Just tested, to me works.

working on this in a separate repo (https://github.com/premAI-io/test-app/actions)...
any idea why tauri build fails with "path matching bin/python/petals-aarch64-apple-darwin not found." despite src-tauri/bin/python/petals-aarch64-apple-darwin existing?

It would be nice to move the Petals rust code into its own file rather than in main.rs

follow-up: apparently tauri build --target universal-apple-darwin wants ALL THREE of:

petals-aarch64-apple-darwin
petals-x86_64-apple-darwin
petals-universal-apple-darwin

Just one or two of the above isn't enough.

@casperdcl can we fake them?

CI_build *.dmg + binaries if anyone wants to test things :)


Version 1.1.0

This is the development branch for Version 1.1.0
The headline features are:

Support for Rails' localisation API #69
Allow collection items (radio buttons and check boxes) to be set via Procs #75
Gem configuration #73
Custom localisation scopes via configuration #81
Remove the huge list of required files from lib/govuk_design_system_formbuilder.rb #78

Track the overall progress here.

1.1.0 Beta 3 is out. This completes the work intended for version 1.1.0.
I've tested this locally and Apply's test suite passes with the latest beta. If there are no reports of problems expect an iminenent release.
cc @tvararu, @leeky, @dankmitchell - feedback welcome


A quick question about implementation details

Hi, thanks for your interesting work. I am a bit confused about two settings in your model and I am looking forward to your reply :)

I think according to the text description, you had text encoder and cell encoder participating for pre-training, and these two encoders will be used for zero-shot inference. However, in the zero-shot tutorial you provided, you still use the pubmed data to initialize the text encoder (not the version after your pre-training). Are there any intuitions behind this design?

In the ablation test folder, I can only find one result for L_CTM. Have your tried ablations for L_CC or L_CT? Thanks.

Thank you for your interest in LangCell!

In fact, in the zero-shot tutorial, we use pre-trained checkpoints to initialize the text encoder. pubmedBERT is only used to initialize the tokenizer.

text_pretrained_model = 'microsoft/BiomedNLP-PubMedBERT-base-uncased-abstract-fulltext'
tokenizer = BertTokenizer.from_pretrained(text_pretrained_model)
# ......
text_encoder = MedBertModel.from_pretrained('ckpt/text_bert', add_pooling_layer=True)
# ......

The specific ablation experimental setup can be found in the paper. Due to the huge computational overhead, it is impossible to try all combinations. We verified the contribution of each loss function in a cost-effective manner.


Provide refactor to convert [].forEach to for/for of (And convert back)

Suggestion

🔍 Search Terms
refactor, iterator, for

List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.
✅ Viability Checklist

My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[ ] This wouldn't change the runtime behavior of existing JavaScript code
[ ] This could be implemented without emitting different JS based on the types of the expressions
[ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[ ] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
Provide refactor to convert [].forEach to for/for of (And convert back)

📃 Motivating Example
[].forEach((value, index) => {
  console.log(value, index)
})

// to

var arr = []
for (let index = 0; index < arr.length, index++) {
  let value = arr[index]

  console.log(value, index)
}

// or

for (let index of []) {
 console.log(value) // disallow index here
}

💻 Use Cases

How would this handle return within  a forEach callback vs continue in a for loop, and also what if the for loop contains a break?

How would this handle return within a forEach callback vs continue in a for loop, and also what if the for loop contains a break?

@jgbpercy
I thought we don't need cover 100% scenario. So, we may just deny them.

This would help refactoring old code tremendously. I mostly care about converting forEach to for of.


A minor fix + another translation added

Basically, "checkmate" in Russian is referred as just "mate", so it won't be confused with the actual name of chess, which can literally can be translated as "checkmates". This patch fixes such a problem.
P. S. I bet some other languages might also refer to it as "mate", but I will leave it on you and further research.

Another minor translation issue found. The translation encircled in Red in a "winners" tab better use "Score2" translation instead of "Score1" because score in this case means a H2H score (for non-Swiss) or "pure standings" (for Swiss), and in both cases "счёт" is way more applicable than "оценка" as a translation (although it is still not ideal).

I found another missing translation that seems to be completely missing from every single language...


Re-implement commands in mediawiki-texvc.js like \oiint as big operators

In #1810 , several commands, including \oiint are added to TeX extension mediawiki-texvc.js. But, \oiint was implemented as a macro,
https://github.com/mathjax/MathJax/blob/39c61f62a9a8196e6caa189ff5771ea31b7f7379/unpacked/extensions/TeX/mediawiki-texvc.js#L88-L90
not a big operator.
https://github.com/mathjax/MathJax/blob/39c61f62a9a8196e6caa189ff5771ea31b7f7379/unpacked/jax/input/TeX/jax.js#L537-L540
Therefore, when \oiint is used in display style, it is just in a larger font size (using \huge) and hence ugly, not with the corresponding "bigger" glyph defined in math font.

One reason for the definition is that the MathJax TeX fonts don't include the needed characters; the STIX fonts do, but the MathJax TeX fonts are the default, and defining it in the way that you indicate would mean the symbol would not show up at all for some people.  The authors of the extension probably felt that this was the best compromise between functionality and quality.

Are the MathJax TeX fonts you just mentioned derived from any otf Math fonts, like Latin Modern Math font?

No, they were built using mftrace from the Computer Modern TeX fonts ages ago.

Ok, I see.
Maybe it's time to build the MathJax TeX fonts from Latin Modern Math, for a more complete list of math symbols.

The Latin Modern fonts are supported in the HTML-CSS and SVG output (but not currently the CommonHTML output), but they are not the defaults.  We are in the final stages of a complete rewrite for version 3.0, which has a revised font handling framework.  Currently v3 only supports the current MathJax TeX fonts, but we plan a revamping of the fonts for 3.1, and that will include updating the MathJax TeX fonts.

To record the progress after one year:

The latest release of MathJax is 3.0.5.
\oint is supported as math operator (texClass: TEXCLASS.OP). See related source line.
Extension mediawiki-texvc is not supported, hence \oiint and \oiiint (and some other commands) are not supported in 3.0+.


New Icon design

Dear Lawnchair dev team I want to design icons for the lawnchair launcher is it possible? Because many popular app dynamic icons are missing!

Sure. Check out the guidelines for more information on contributing! Happy designing :)


Add support for broadcasting shapes.

This PR adds functionality to TensorShape to allow for broadcasting. In particular,

TensorShape.broadcast_with(other) returns the shape resulting from broadcasting a tensor of the given shape with a tensor of shape other. It raises a ValueError if the shapes are not broadcastable.
TensorShape.is_broadcastable_with(other) determines whether two shapes are broadcastable
TensorShape.assert_is_broadcastable_with(other) asserts that two shapes are broadcastable

Can one of the admins verify this patch?

https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/framework/common_shapes.py#L501
Do you know why this is different from that?

No, they are in fact identical (up to the implementation).

The term broadcasting describes how NumPy treats arrays with different shapes during arithmetic operations. Subject to certain constraints, the smaller array is “broadcast” across the larger array so that they have compatible shapes. Broadcasting provides a means of vectorizing array operations so that looping occurs in C instead of Python.
It does this without making needless copies of data and usually leads to efficient algorithm implementations. There are, however, cases where broadcasting is a bad idea because it leads to inefficient use of memory that slows computation.
NumPy operations are usually done on pairs of arrays on an element-by-element basis. In the simplest case, the two arrays must have exactly the same shape, as in the following example:
a = np.array([1.0, 2.0, 3.0])
b = np.array([2.0, 2.0, 2.0])
a * b
array([2.,  4.,  6.])
NumPy’s broadcasting rule relaxes this constraint when the arrays’ shapes meet certain constraints. The simplest broadcasting example occurs when an array and a scalar value are combined in an operation:
a = np.array([1.0, 2.0, 3.0])
b = 2.0
a * b
array([2.,  4.,  6.])
The result is equivalent to the previous example where b was an array. We can think of the scalar b being stretched during the arithmetic operation into an array with the same shape as a. The new elements in b, as shown in Figure 1, are simply copies of the original scalar. The stretching analogy is only conceptual. NumPy is smart enough to use the original scalar value without actually making copies so that broadcasting operations are as memory and computationally efficient as possible.


Added a recent leetcode solution

@heeba-khan can you remove the package.json file in the commit :)

Sure! I have removed it now and pushed again. Kindly check.
On Sat, Oct 14, 2023 at 12:34 PM Dixit Tilaji @.***>
wrote:

@heeba-khan https://github.com/heeba-khan can you remove the
package.json file in the commit :)
—
Reply to this email directly, view it on GitHub
https://github.com/dixitt5/CP-Solutions/pull/307#issuecomment-1762671901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2S5QNTIPD6NHU6ID54IUTLX7I2RBAVCNFSM6AAAAAA55EIFOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRSGY3TCOJQGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

I have removed the package.json file. Kindly check.

Sure! I have done it now.Kindly check it.
On Sat, Oct 14, 2023 at 12:34 PM Dixit Tilaji @.***>
wrote:

@heeba-khan https://github.com/heeba-khan can you remove the
package.json file in the commit :)
—
Reply to this email directly, view it on GitHub
https://github.com/dixitt5/CP-Solutions/pull/307#issuecomment-1762671901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2S5QNTIPD6NHU6ID54IUTLX7I2RBAVCNFSM6AAAAAA55EIFOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRSGY3TCOJQGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

I have updated the code and removed package.json . Kindly check.

Thanks for the changes, Merged!


OIDC provider config doesn't work with Google

Might not work with gitlab either
It does work with dex!

Solution might be to make list of scope configurable.

Or --google-scopes etc rather than allowing a generic list of strings as we need to know the correct key to grab the groups from, e.g. "teams".

Any solution for this. I tried to use OIDC with Google auth and this is the message I get.

+1 for GitLab self-hosted, scope groups is missing there:
https://docs.gitlab.com/ee/integration/oauth_provider.html#authorized-applications
When trying to login with GitLab I get:
The requested scope is invalid, unknown, or malformed.
URL is:
https://gitlab.subdomain.tld/oauth/authorize?client_id=XXX&redirect_uri=http%3A%2F%2F<IP_ADDRESS>%3A8080%2F&response_type=code&scope=profile+openid+email+groups&state=XXX

to share our experience - we're on Google for GKE and group-based RBAC in the cluster.  these help us use flux safely across the team and not have to managed gnarly custom users/roles.  but as we were setting up GitOps and excited about it, we tried the OIDC provider -> Google OAuth client, there's no way to grab and assume the group, which means none of our RoleBindings will apply.  the end result is that only the admin user has permissions to the cluster, and all OIDC users do not


[CWS] Do not tag running metrics with internal policies version

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Bluetooth: MCS: Disable OACP checksum support

This is needed to properly initialize media player for GMCS tests. This feature was enabled for OTS tests, but is not needed for GMCS tests and is causing all CAP and GMCS test cases to fail.

#AutoPTS run zephyr OTS/SR/CR/BV-03-C CAP/INI/UST/BV-02-C GMCS/SR/SGGIT/CHA/BV-03-C

AutoPTS Bot failed:
Reason unknown

AutoPTS Bot failed:
Reason unknown

AutoPTS Bot results:
Failed testsCAP     CAP/INI/UST/BV-02-C             BUILD_OR_FLASH ERRORGMCS    GMCS/SR/SGGIT/CHA/BV-03-C       BUILD_OR_FLASH ERROROTS     OTS/SR/CR/BV-03-C               BUILD_OR_FLASH ERROR

AutoPTS Bot results:
No failed test found.
Successful testsCAP     CAP/INI/UST/BV-02-C             PASSGMCS    GMCS/SR/SGGIT/CHA/BV-03-C       PASSOTS     OTS/SR/CR/BV-03-C               PASS

@piotrnarajowski why was this closed?

@Thalley looks like PR https://github.com/zephyrproject-rtos/zephyr/pull/73017 which is already merged contains similar changes

Ah, thanks. Please do add a description when closing PRs in the future :)