Dask tutorial with operator created only once

Some modifications were introduced to tutorial 04. Now the Operator is created only once and it is reused for the modeling of all the shots and the gradient computation. In this way, there should not be memory issues.

@mloubout :

But overall I think this is a way to "hide" a memry issue that the clear_cache PR is trying to fix in a better way IMO

it's a different issue: https://github.com/opesci/devito/issues/845

Now it is a memized function so it won't re-generate and re-compile anything but because you are on a different node the actual c-file does not exist.

This assumes no shared filesystem. I see no obvious reason why we shouldn't do this when we have a shared file system.
There are scenarios where we have no choice but to do this - e.g. intel compiler license only available on login nodes.

But overall I think this is a way to "hide" a memry issue that the clear_cache PR is trying to fix in a better way IMO

The solver class has its own issues that are not related to clear_cache. This is avoiding those issues by not creating more than one solver.
The idea of reusing Operator objects has been a key assumption in Devito for a long time but the examples all create new Operator objects very actively, so I think this modification is a step in the right direction.

@navjotk @mloubout
can you provide a summary? where do we stand now this PR ?

Hi guys,
Rhodri asked me to help out with this tutorial. I read through this thread and had a look at the current version, but can you summarize what the current issues are that are still outstanding?
I think the way the functions are currently set up to compute the functional value and gradient in parallel generally make sense. Namely setting up the solver inside each respective (serial) function call. I'm personally not a big fan of passing only a dictionary called params to the fwi_gradient_i function. Speaking from my own experience, I think these dictionaries tend to end up as a graveyard for all kinds of parameters and it's not always clear what is overwritten inside the function or what information is redundant. I think it's cleaner to have an objective function that takes a set of well defined input arguments, namely something like observed_data, rec_geometry, src_geometry, src_wavelet, model, which would be all the necessary information to evaluate the fwi objective function. But I understand it's a matter of personal taste and may not be something we want to change at this point.
Anyway, please let me know how I can help out!

Hi guys,
Rhodri asked me to help out with this tutorial. I read through this thread and had a look at the current version, but can you summarize what the current issues are that are still outstanding?
I think the way the functions are currently set up to compute the functional value and gradient in parallel generally make sense. Namely setting up the solver inside each respective (serial) function call. I'm personally not a big fan of passing only a dictionary called params to the fwi_gradient_i function. Speaking from my own experience, I think these dictionaries tend to end up as a graveyard for all kinds of parameters and it's not always clear what is overwritten inside the function or what information is redundant. I think it's cleaner to have an objective function that takes a set of well defined input arguments, namely something like observed_data, rec_geometry, src_geometry, src_wavelet, model, which would be all the necessary information to evaluate the fwi objective function. But I understand it's a matter of personal taste and may not be something we want to change at this point.
Anyway, please let me know how I can help out!

Hi @philippwitte ,
Thanks for agreeing to help out! So first of all, if there are any improvements or restructuring you'd like to add to the notebook please feel free to be creative and incorporate any adaptions you'd like to see.
Aside from that, in the current notebook there are various grammatical mistakes that need fixing and the instances where object properties are being overwritten need to be fixed etc.
With regards to the discussion between @navjotk and @mloubout, I'll try and speak with Navjot today and get back to you with any fixes/adaptations he'd like to see.
And to give you some context, this notebook will be used as the basis for an FWI 'challenge' for workshop participants who don't wish to get involved in the GPU hackathon.

What's the plan on this, and considreing the new version of the Dask tuto @philippwitte made for oghpc

So what's the plan for this one?

I don't even remember where we stand with this one :grimacing:
I think we should first of all rebase it on latest master as there are conflicts with the current Dask tutorial.
@mloubout @rhodrin this is what @ofmla originally wrote in the description of this PR:

Now the Operator is created only once and it is reused for the modeling of all the shots and the gradient computation. In this way, there should not be memory issues.

going back to the very beginning -- do we all agree that this is a step we want to make to improve things?

do we all agree that this is a step we want to make to improve things?

I think it's worth a notebook, but i'd say a separate one as both ways have their merits. So I would say close this PR and open a new one with a new notebook.

do we all agree that this is a step we want to make to improve things?

I think it's worth a notebook, but i'd say a separate one as both ways have their merits. So I would say close this PR and open a new one with a new notebook.

So, what you got in mind, @mloubout @FabioLuporini ? maybe I can help

Probably just rename the notebook (like ..._dask_pickle_op.ipynb and rebase would be a good start.

@mloubout @FabioLuporini I rebased as suggested and created a new notebook 12_pickle_dask_op.ipynb with a brief introduction. I kept much of the original notebook, but I can add more explanatory comments If you want. The notebook deliver broadly the same results as 04_dask.ipynb.

I think once @FabioLuporini comments are answered, should be GTG. Can you open an issue about the src/rec_position shape problem and assign it to me.

Following the convention used throughout devito/examples, we should name the new notebook as "04_dask_pickling.ipynb". And since it's an extension of 04_dask.ipynb, we should rip off most of the (now redundant) explanations, and add a short section at the beginning explaining what the delta between 04_dask and 04_dask_pickling is.

I renamed the tutorial and add a short paragraph that explains the differences between both tutorial  04_dask and 04_dask_pickling. I hope you like it, anyway, if more changes are needed let me know

Said that, I super like the idea of moving this to a new notebook. I think we're right on track towards merging

Merged.


*: fetch forecasts using the latest product API

hooks: use a mapping custom for options
This is common in all of the react-query documentation for capturing
options passed to a query. No reason we should buck the trend.
Signed-off-by: Steve Kuznetsov<EMAIL_ADDRESS>
*: fetch forecasts using the latest product API
Ultimately, we will need two types of views:

"show me the currently-valid products for a zone"
"show me the valid products for a zone at some point in the past"

Due to quirks of how the date filtering works on the products API from
the NAC (filtering on the publication date, not the date for which the
product is valid), we need to split these cases up. This PR does the
first pass to allow us to fetch the currently-valid forecast.
Follow-up PRs will:

update our routes to not contain a date, and resolve "now" when we're
in the component
add a new route for a particular time in history
add warnings & synopses to the data we fetch for a forecast date

Signed-off-by: Steve Kuznetsov<EMAIL_ADDRESS>

@floatplane updated the function to be clearer, added tests

@floatplane blargh, startOfDay() is locale-specific too. Fixed.

if you fix up commits and force push then I have to look at the whole diff again 😢


Remove deprecated workqueue argument: NoLocationUpdate

This argument was replaced more than 6 months ago by NoInputUpdate and NoPileupUpdate.
Thus I'm removing this code.
I've also updated the json file with workqueue elements that had only the deprecated arg. Both args were added and kept the same default value (False).

test this please

Why is the updated Jason file 60k lines longer?

Because I pretty dumped it, in case someone needed to look at one "document" structure. Maybe it's not a good idea and I should just dump without indent (single line)?

It's fine. One thing I'd suggest is using options like
json.dump(lookup, mockData, indent=1, separators=(',', ': '), sort_keys=True)
which will keep the size a bit smaller and keep things sorted. Then future diffs won't be as large

Json file updated as you suggested.

@ticoann good to be merged


Solve ScopedName different of css-loader and css-modules-require-hook on Windows

due to this code of css-loader
https://github.com/webpack-contrib/css-loader/blob/d3a0a3c59f4de1b48c5011abbd1ca565b1be3760/src/utils.js#L76 and generic-names https://github.com/css-modules/generic-names/blob/2.0.0/index.js#L37
the relative path of generic-names 2.0.1 is same as css-loader, but now css-modules-require-hook use version 1.0.3, please upgrade generic-names

@sullenor any plans to merge in the fix, or delegate the ownership of NPM package to somebody else (say, to me?) to get this fixed?

Nevermind, I just forked the library and upgraded it myself. Anybody interested, you'll find it here<EMAIL_ADDRESS>


[Qualification]: Support confirmation for PowerFlex CSI-2.11.0 on OCP 4.17

Operating System
Ubuntu 18.04.6 LTS
Container Orchestrator
OCP 4.17
Storage Platform
PowerFlex
Protocol
iSCSI
Relevant log output
root@inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone:~/workspaces/cert-csi# ./cert-csi test vio --sc mcp-pf-fs-storageclass
[2024-09-11 00:35:00]  INFO Starting cert-csi; ver. 1.5.0
[2024-09-11 00:35:00]  INFO Using EVENT observer type
[2024-09-11 00:35:00]  INFO Using default config
[2024-09-11 00:35:00]  INFO Successfully loaded config. Host: https://api.c4-raven.racka01.local:6443
[2024-09-11 00:35:00]  INFO Created new KubeClient
[2024-09-11 00:35:00]  INFO Running 1 iteration(s)
......
[2024-09-11 00:37:11]  INFO Avg time of a run:   113.14s
[2024-09-11 00:37:11]  INFO Avg time of a del:   12.03s
[2024-09-11 00:37:11]  INFO Avg time of all:     130.53s
[2024-09-11 00:37:11]  INFO During this run 100.0% of suites succeeded

root@inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone:~/workspaces/cert-csi# ./cert-csi test scaling --sc mcp-pf-fs-storageclass
[2024-09-11 00:47:18]  INFO Starting cert-csi; ver. 1.5.0
[2024-09-11 00:47:18]  INFO Using EVENT observer type
[2024-09-11 00:47:18]  INFO Using default config
[2024-09-11 00:47:18]  INFO Successfully loaded config. Host: https://api.c4-raven.racka01.local:6443
[2024-09-11 00:47:18]  INFO Created new KubeClient
[2024-09-11 00:47:18]  INFO Running 1 iteration(s)
......
[2024-09-11 00:48:37]  INFO Avg time of a run:   45.08s
[2024-09-11 00:48:37]  INFO Avg time of a del:   12.04s
[2024-09-11 00:48:37]  INFO Avg time of all:     79.37s
[2024-09-11 00:48:37]  INFO During this run 100.0% of suites succeeded

root@inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone:~/workspaces/cert-csi# ./cert-csi test snap --sc mcp-pf-fs-storageclass --vsc vxflexos-snapclass --size 8Gi
[2024-09-11 00:51:34]  INFO Starting cert-csi; ver. 1.5.0
[2024-09-11 00:51:34]  INFO Using EVENT observer type
[2024-09-11 00:51:34]  INFO Using default config
[2024-09-11 00:51:34]  INFO Successfully loaded config. Host: https://api.c4-raven.racka01.local:6443
[2024-09-11 00:51:34]  INFO Created new KubeClient
[2024-09-11 00:51:34]  INFO Running 1 iteration(s)
......
[2024-09-11 00:52:20]  INFO Avg time of a run:   29.19s
[2024-09-11 00:52:20]  INFO Avg time of a del:   12.03s
[2024-09-11 00:52:20]  INFO Avg time of all:     45.24s
[2024-09-11 00:52:20]  INFO During this run 100.0% of suites succeeded

root@inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone:~/workspaces/cert-csi# sudo ./cert-csi test multi-attach-vol --sc mcp-pf-fs-storageclass --block
sudo: unable to resolve host inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone
[2024-09-11 20:48:44]  INFO Starting cert-csi; ver. 1.5.0
[2024-09-11 20:48:44]  INFO Using EVENT observer type
[2024-09-11 20:48:44]  INFO Using default config
[2024-09-11 20:48:44]  INFO Successfully loaded config. Host: https://api.c4-raven.racka01.local:6443
[2024-09-11 20:48:44]  INFO Created new KubeClient
[2024-09-11 20:48:44]  INFO Running 1 iteration(s)
......
[2024-09-11 20:50:25]  INFO Avg time of a run:   25.05s
[2024-09-11 20:50:25]  INFO Avg time of a del:   12.04s
[2024-09-11 20:50:25]  INFO Avg time of all:     100.19s
[2024-09-11 20:50:25]  INFO During this run 100.0% of suites succeeded

root@inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone:~/workspaces/cert-csi# ./cert-csi test ephemeral-volume --driver csi-vxflexos.dellemc.com --attr ephemeral-config.properties
[2024-09-11 23:38:46]  INFO Starting cert-csi; ver. 1.5.0
[2024-09-11 23:38:46]  INFO Using EVENT observer type
[2024-09-11 23:38:46]  INFO Using default config
[2024-09-11 23:38:46]  INFO Successfully loaded config. Host: https://api.c4-raven.racka01.local:6443
[2024-09-11 23:38:46]  INFO Created new KubeClient
[2024-09-11 23:38:46]  INFO Using default number of pods
......
[2024-09-11 23:42:04]  INFO SUCCESS: EphemeralVolumeSuite in 3m17.311014769s
[2024-09-11 23:42:04]  INFO Trying to connect to cluster...
[2024-09-11 23:42:04]  INFO Created new KubeClient
[2024-09-11 23:42:04]  INFO During this run 100.0% of suites succeeded

root@inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone:~/workspaces/cert-csi# ./cert-csi test clone-volume --sc mcp-pf-fs-storageclass
[2024-09-11 02:00:42]  INFO Starting cert-csi; ver. 1.5.0
[2024-09-11 02:00:42]  INFO Using EVENT observer type
[2024-09-11 02:00:42]  INFO Using default config
[2024-09-11 02:00:42]  INFO Successfully loaded config. Host: https://api.c4-raven.racka01.local:6443
[2024-09-11 02:00:42]  INFO Created new KubeClient
[2024-09-11 02:00:42]  INFO Running 1 iteration(s)
......
[2024-09-11 02:01:18]  INFO Avg time of a run:   18.11s
[2024-09-11 02:01:18]  INFO Avg time of a del:   12.03s
[2024-09-11 02:01:18]  INFO Avg time of all:     35.17s
[2024-09-11 02:01:18]  INFO During this run 100.0% of suites succeeded

root@inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone:~/workspaces/cert-csi# ./cert-csi test  expansion --sc mcp-pf-fs-storageclass --intialSize 8Gi --expandedSize 16Gi
[2024-09-11 02:03:56]  INFO Starting cert-csi; ver. 1.5.0
[2024-09-11 02:03:56]  INFO Using EVENT observer type
[2024-09-11 02:03:56]  INFO Using default config
[2024-09-11 02:03:56]  INFO Successfully loaded config. Host: https://api.c4-raven.racka01.local:6443
[2024-09-11 02:03:56]  INFO Created new KubeClient
[2024-09-11 02:03:56]  INFO Running 1 iteration(s)
......
[2024-09-11 02:05:52]  INFO Avg time of a run:   99.24s
[2024-09-11 02:05:52]  INFO Avg time of a del:   12.03s
[2024-09-11 02:05:52]  INFO Avg time of all:     115.46s
[2024-09-11 02:05:52]  INFO During this run 100.0% of suites succeeded

root@inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone:~/workspaces/cert-csi# ./cert-csi test provisioning --sc mcp-pf-fs-storageclass --podNum 3 --volNum 10
[2024-09-11 02:08:21]  INFO Starting cert-csi; ver. 1.5.0
[2024-09-11 02:08:21]  INFO Using EVENT observer type
[2024-09-11 02:08:21]  INFO Using default config
[2024-09-11 02:08:21]  INFO Successfully loaded config. Host: https://api.c4-raven.racka01.local:6443
[2024-09-11 02:08:21]  INFO Created new KubeClient
[2024-09-11 02:08:21]  INFO Running 1 iteration(s)
......
[2024-09-11 02:09:11]  INFO Avg time of a run:   23.61s
[2024-09-11 02:09:11]  INFO Avg time of a del:   12.05s
[2024-09-11 02:09:11]  INFO Avg time of all:     49.32s
[2024-09-11 02:09:11]  INFO During this run 100.0% of suites succeeded

root@inner-jumpjerry-day1-pool-28737191-28757062-2111-vclone:~/workspaces/cert-csi# ./cert-csi test blocksnap --sc mcp-pf-fs-storageclass --vsc vxflexos-snapclass --size 8Gi
[2024-09-11 23:17:59]  INFO Starting cert-csi; ver. 1.5.0
[2024-09-11 23:17:59]  INFO Using EVENT observer type
[2024-09-11 23:17:59]  INFO Using default config
[2024-09-11 23:17:59]  INFO Successfully loaded config. Host: https://api.c4-raven.racka01.local:6443
[2024-09-11 23:17:59]  INFO Created new KubeClient
[2024-09-11 23:17:59]  INFO Running 1 iteration(s)
......
[2024-09-11 23:20:20]  INFO Avg time of a run:   63.43s
[2024-09-11 23:20:20]  INFO Avg time of a del:   12.04s
[2024-09-11 23:20:20]  INFO Avg time of all:     140.37s
[2024-09-11 23:20:20]  INFO During this run 100.0% of suites succeeded

Additional Details
No response

Hi @Y0NG-WANG. we appreciate your contributions. Thank you!


docs(install): change bridge bundle resources

Version 0.17.1 added style for chip and range :+1:

You're right, thanks! :smiley:
I've had the feeling that I forgot something important..
I wonder if we can change this somehow so that users don't need to add this. Maybe add these to build resources. At least, that works for webpack.

Coverage remained the same at 95.154% when pulling 977646891d26b9cafdfadb9b6973d3c27caafcec on Ullfis:aurelia-cli-docs into 99d9fabb1af3ede9b5525f7bd6747184ebd05dcd on aurelia-ui-toolkits:master.

I just tried to change the bridge bundle resources in this project and it worked!

      {
        "name": "materialize-bundle.js",
        "dependencies": [
          "jquery",
          {
            "name": "materialize-css",
            "path": "../node_modules/materialize-css/dist",
            "main": "js/materialize.amd",
            "deps": [
              "jquery"
            ]
          },
          {
            "name": "aurelia-materialize-bridge",
            "path": "../node_modules/aurelia-materialize-bridge/dist/amd",
            "main": "index",
            "deps": [
              "jquery"
            ],
            "resources": [
              "**/*.{css,html}"
            ]
          }
        ]
      },

<EMAIL_ADDRESS>

:tada:

Confirming that it works in 2 other aurelia-cli projects.

That did not always work, right?
I hope it stays as it is now. ;-)

It didn't work at all earlier :)
Trying to amend doc changes

Coverage remained the same at 95.154% when pulling 8b213f80309f25887ed690c337bdb5dad0181797 on Ullfis:aurelia-cli-docs into 99d9fabb1af3ede9b5525f7bd6747184ebd05dcd on aurelia-ui-toolkits:master.

Thanks!
I'd like to put these docs into a GitBook so that we don't have to update (build, bundle, upload) the app everytime the docs change.

Unhandled rejection Error: src/../scripts/materialize-bundle.html HTTP status: 404

I wonder why it's trying to load that..

Strange. I have not had that error. Latest cli version? Dropped node_modules and reinstalled? Do this project run?

I will try deleting node_modules and reinstall. Did not yet try running your project but copied the aurelia.json.

Your project runs perfectly. 👍
Hmm, I guess I need to compare now.

The first difference seems to be windows path seperators and you're using typescript. 😃
Interesting...

Seems to be some kind of fallback request when anything is not found in the bundle.
I removed the wildcards and put everything back in, then added chips and range css and it worked.. Very strange.
Now, my global aurelia-cli is different from my local one. I'll try upgrading both now.

I've noticed the trace stopping at:
Tracing aurelia-materialize-bridge/collection/collection-item...

With your project it traces all exports.

Very strange. I cant think why it should be different. I will try an esnext cli project later.

I'll try and generate a new project after upgrading everything.

Okay, I'm giving up for today..
Does this project run for you?
I must be overlooking something..

https://github.com/aurelia/webpack-plugin/issues/11

Also, only typescript type (option 2) with the command "au new" works. First default option does not.

I don't know if that's true but if it is, that may be a reason (and everybody else in the world would create TS projects 😂 ).

esnext
...
Tracing aurelia-materialize-bridge/click-counter...
Tracing aurelia-materialize-bridge/breadcrumbs/breadcrumbs...
Tracing aurelia-materialize-bridge/breadcrumbs/breadcrumbs...
Tracing aurelia-materialize-bridge/card/card...
Tracing aurelia-materialize-bridge/card/card...
Tracing aurelia-materialize-bridge/carousel/carousel...
Tracing aurelia-materialize-bridge/carousel/carousel-item...
Tracing aurelia-materialize-bridge...
Tracing text...
...

and so on. It compiled and I could start browser but missed components, so page wouldn't load.
I had to add all resources before it worked. One interesting thing.. I forgot to set stub to false (after adding all components) and it worked anyway. I did not add aurelia-validation on this test.

I've noticed that, too as you know..
This also happened with a TypeScript project. So, validation..?
@JeroenVinke mentioned an issue where he found out that matching all resources timed out. That would fit the "randomness" of this problem.

I have created https://github.com/aurelia/cli/issues/368

I changed build script on the typescript project so it clean the output folder and copy scripts during first build. After that I had to add back bridge resources to make the project run.
Build time related?

It works for me with the changes from Jeroen's PR here:
https://github.com/aurelia/cli/pull/369

Works for me 2. Both typescript and esnext cli project.

Great!
I will wait for the PR being merged. In the meantime I moved the installation instructions to GitBook docs:
https://www.gitbook.com/read/book/aurelia-ui-toolkits/materialize-bridge-docs
These instructions include chip and range.
Will update the app when I come home in a few hours.

0.21.0 is out with the fix 🎉

So strange; Looks like I'm having this same issue in 0.24.0

So strange; I'm having the same
Unhandled rejection Error: src/../scripts/materialize-bundle.html HTTP status: 404 but in 0.24.0

@DarienFord This is usually a follow-up error, I've seen it frequently when files are missing from the bundle. There should be another error message with the "real" error. Could you check that and post the error if I'm right? 😃


Revert MetadataJCP2022 to its original state for controls

See https://github.com/broadinstitute/jump-profiling-recipe/pull/10.
The controls use a mapper to match the profiles. The profiles are reverting this. The mapper ought to track that.

New databases include this (8cfa222f64d40f11c1618949e4370aa8c762b512)


Julia v0.5, other fixes

Just opening this PR (#187) directly from @ScottPJones's repo so that he can update directly.

Submitted on behalf of @ScottPJones. @rawls238 @DanielArndt can you guys take a look and merge if acceptable? I'm being distracted by becoming a father and trying to get back to work.
Copy and paste from https://groups.google.com/forum/#!topic/julia-dev/_A3_HMK4EIw:
While trying to get Gadfly.jl working (and eliminating the many warning messages that come up simply trying to do "using Gadfly" under v0.5),
I ran into the following problem in DataStructures.jl/src/accumulator.jl, that I'd like some guidance on.
The Accumulator type is simply a wrapper around a Dict.
The issue is that in v0.5, there is a warning, because there is an outer constructor defined, which simply takes a dictionary passed as an argument, copies it,
and then calls the inner constructor, however, this also overwrites the inner constructor's method, so it is no longer accessible.
Further down, in the two places where the the Accumulator constructor is used, there are explicit copies, so in fact, the dictionary gets copied twice, unnecessarily.
This seems like a bug, where somebody added the outer Accumulator constructor in order to ensure that a copy was always made, but neglected to remove the copy from places where it was done explicitly.
Should the simple fix of simply removing the outer constructor with the extra copy, which also prevents the overwriting warning be done,
or rather change to using only inner constructors, which force any dictionaries to be passed to always be copied? (IMO, it would be better to leave any copying
up to the caller, and document that the dictionary passed to Accumulator will be modified.
I have already made a branch that fixes this and a couple other bugs, in https://github.com/ScottPJones/DataStructures.jl/tree/spj/fixv05.
I would have submitted a PR, however, due to current circumstances, since DataStructures.jl is in JuliaLang, I am unable to do so.
Scott Paul Jones

Looks good to me. This does slightly change the behaviour of the constructor which might be controversial, so I'll leave it up for comment for a bit. Specifically, if @lindahua has time to weigh in since he wrote the original code specifically to do this.
If you can squash the last commit (reverting the comment) into the first where it was introduced that's preferable, but I don't think it's a big deal.

The change you merged in was already submitted upstream by another channel, so I can no longer merge this. If you rebase off master, and remove that last merge this should be good to go.


Setting startLanguage will jump scroll the page because of custom click event

When using the startLanguage option to force one of the subtitle tracks as default, it triggers a custom click event which will affect the scrollY of most browsers. So when a video exists halfway down the page, upon loading, it immediate jumps to the video because the browser thinks it was clicked.
The affected code is on line 2610 of mediaelement-and-player.js
var event = (0, _general.createEvent)('click', target);
target.dispatchEvent(event);

Issue seems to be in https://github.com/mediaelement/mediaelement/blob/06135fc02b67ad8eca0553f04b37c6e8bdc676c6/src/js/features/tracks.js#L470-L475

This appears to be fixed by inserting
e.preventDefault() into mediaelement/srv/js/features/tracks.js  on line 208.
Which allows the selected track to be changed but prevents the default click action.
I've only done cursory testing of this; it's adequate for my needs but I'm not sure how robust it is.
Will submit a PR once I've tested it a bit more.

`#```


Update SPEC.md

Small typos

Thanks for the patch and apologies for getting to this out of order - I think you will need to rebase against master as some of these have been resolved.

I am going to rebase and merge this myself now.

Merged most of the typos at 9b7889b. I am fine discussing the PATH thing but it should be an explicit PR about it.

@AXGKl Would you mind starting a new PR about this PATH thing?


As a Partner/Data owner I want to track usage of data to enable collaboration opportunities and feedback for providers ..so that I  know how data are being used and this can be used to further demonstrate the value of the JCDP

original id#94
Same theme as ticket id#17
id 17 is about tracking access.
This is about tracking uses
also #170

Depends what it is means with track, if it is to count the number of times data were downloaded then it is possible.

see #45 as a way of the provider tracking data use (for restricted data only) and then see DOI tickets for open data

see #45 as a way of the provider tracking data use (for restricted data only) and then see DOI tickets for open data

Cover in comms strategy once the way forward is identified

duplicate of #126 -dashboard. closed


Companion Regularly Loses Connection with ATEM Mini Pro

I have 2.1.1 (238f21c-2605) of companion and as the title said I'm using it with an ATEM Mini Pro.  I had borrowed an ATEM Mini previously to test out and recently swapped in the Mini Pro.
What happens is a continuous cycle of Companion losing the connection for a short time, and then quickly reestablishing.  Companion is running on a Pi4 and both have static IPs.
I have so far tried deleting the instance and loading a new one, changing from Auto to Mini Pro and back, which when on Auto I get:

instance(atem): Connected to a ATEM Mini Pro, but instance is configured for Mini Pro. Change instance to 'Auto Detect' or the appropriate model to ensure stability.

I am using USB to send video, but disconnecting that has no effect on the connectivity.  When it is connected, it works fine.  But in the fits of it losing the connection it won't respond to inputs from the Companion interface.

So I think I've determined this to be due to a subpar wifi signal.  I initially discounted that possibility since I am using Companion to control the ATEM, OBS, and Lightfactory via UDP commands and everything else worked fine.  I ended up relocating the Pi and moving into better line of sight with the router improved the connectivity.


I fully followed tutorial, but getting errors

I have followed this tutorial https://docs.medusajs.com/tutorial/creating-your-medusa-server and readme of this repo https://github.com/medusajs/admin
I have been getting errors from the very beginning, and also I am not able to create any products.
On page load:

When creating a product:

I am not sure what I am doing wrong

I also tried using that docker-compose file, but having problems with PostgreSQL (but I am able to connect with dbeaver without any issues)

@olivermrbl I am still getting the same errors. I did packages updates. Just resolved docker-compose issue.

Hey @vavdav! I mistakenly closed your issue - sorry. The 401 error you are seeing when opening admin is because you are unauthorized. The error modal looks more dangerous than it is. You can close it down and sign in with<EMAIL_ADDRESS>// supersecret. The error 500 probably stems from the fact, that you do not have a file service installed. File services are responsible for the hosting of product images. You can check out our guide on adding a file service plugin here.
Will reopen until we've resolved your issues 👍

Oh thanks @olivermrbl . It was not clear to me from the guide that I have to setup the file service. I also tried https://docs.medusajs.com/how-to/create-medusa-app without success.
I will check it.

@olivermrbl I'm also running into a 401 issue.
I get this error which crashes the server after trying to open the page.
I've followed both the Quickstart Guide and Using create-medusa-app pages - both lead to the same issue.
Error: You must provide the URL of lib/mappings.wasm by calli
  ng SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... })
   before using SourceMapConsumer

  - read-wasm.js:8 readWasm
    [admin]/[gatsby]/[source-map]/lib/read-wasm.js:8:13

  - wasm.js:25 wasm
    [admin]/[gatsby]/[source-map]/lib/wasm.js:25:16

  - source-map-consumer.js:264
    [admin]/[gatsby]/[source-map]/lib/source-map-consumer.js:26
    4:14

  - task_queues:95 processTicksAndRejections
    node:internal/process/task_queues:95:5

  - stack-trace-utils.ts:122 findOriginalSourcePositionAndConte
    nt
    [admin]/[gatsby]/src/utils/stack-trace-utils.ts:122:10

  - start-server.ts:457
    [admin]/[gatsby]/src/utils/start-server.ts:457:20

@han-tyumi This is identical to the issue initially described in the issue here. The error is shown because you are not authorized yet. Should be resolved by signing in to admin. Will close fow now, but reopen in case your issue persist 👍


Email Notifier: no such file to load -- active_support/inflector

Must include activesupport for email notificaiton or else mail gem via pony raises exception.
This is likely a pony or mail issue, but the mail gem appears to properly prevent this from occurring...
Adding activesupport when using pony email notifier to the Gemfile resolves this issue for me.
no such file to load -- active_support/inflector
/var/www/integrity/shared/bundle/ruby/1.9.1/gems/mail-2.4.1/lib/mail.rb	38

https://github.com/mikel/mail/blob/master/lib/mail.rb#L36
Did you have activesupport installed when you originally encountered this issue? If so what version?

I was using rvm and a gemset specifically for integrity so any versions installed shouldn't have been loaded.  I was also using bundle exec rackup also so to start the server so that also should have prevented it from being loaded.  I had found that line in Mail also when debugging which confused me since it appears this shouldn't be an issue.


[doc] Setup FPGA guide with openocd is incorrect

Description
On https://opentitan.org/guides/getting_started/setup_fpga.html, the guide says to run
./bazelisk.sh run //third_party/openocd -- \
    -f "bazel-opentitan/$(./bazelisk.sh outquery //third_party/openocd:jtag_adapter_cfg)" \
    -c "adapter speed 500; transport select jtag; reset_config trst_only" \
    -f util/openocd/target/lowrisc-earlgrey.cfg

but jtag_adapter_cfg does not exists.

This appears to be only an issue on https://opentitan.org/guides/getting_started/setup_fpga.html and not on the equivalent https://opentitan.org/book/doc/getting_started/setup_fpga.html page.
After further investigation it looks like these guides are very out of date - they are not in use and are not being updated, but remain available because the relevant bucket is not cleaned and so these outdated files stick around, mostly accessed via search engines. I don't have access to that so @jwnrt is looking at that instead.
I'm curious how you found this? Was it just via a search engine or do you have an active use case for opentitan.org/guides?

Also for reference the reason for this error (which is not present in the up to date opentitan.org/book/... documentation) is because of the renaming of :jtag_adapter_cfg to :jtag_olimex_cfg in https://github.com/lowRISC/opentitan/commit/6dc58eff36932c51d3b48dad01a064cedd5091cf to allow for multiple JTAG adapters.

I've deleted https://opentitan.org/guides from the bucket. Maybe we should be wiping and rebuilding the bucket when content changes?

As the guides have been removed now this issue no longer exists. For future reference up to date versions of these guides can be found under the relevant sections in https://opentitan.org/book/doc e.g. here.


Multi-threaded fuzzing

Does redb have multi-threaded fuzzing? I think some kind of parallel fuzzing would have uncovered #370. It would be pretty simple to simulate redb's MVCC model manually.

Nope, but ya that'd be great to have

Nice! Did the multi-threaded fuzzer find the bug you fixed in https://github.com/cberner/redb/pull/388/commits/9dc9cb0b92d8fd3f6301dcae5996987b1a63ed90?

yep, it sure did! :)


Recipes

Description

Create recipe model
Add user reference to recipes

Everything looks good Roy! keep it up this way!


DCGAN overriding training step- Keras 3 Migration (Only Tensorflow Backend)

DCGAN overriding training step- Keras 3 Migration (Only Tensorflow Backend)  fix it - KerasCV-Fixit

Retrained and generated the required files, Thanks!


Separate instantiation and building.

Separate out the instantiation from the building step to make testing the instrumentation easier, in particular when running the tests inside a nix-build.
This is a step on the path to fixing #58.

We went down a route refactoring how the logged evaluation worked, with regards to the logged evaluation's trace_attribute code. However, we misunderstood what exactly it was doing and need to step back and give it another go. This has to do with tracing where build-0 came from. @Profpatsch can fill in more details :)


Create venv relative to workspace directory

This PR modifies the behavior of build_env.py so that it always creates a virtual environment relative to the workspace root. The previous behavior was to create the venv relative to the directory you run bazel run ... in. This change makes it so that it doesn't matter what subdirectory you're in when running bazel. Here's a link to the bazel docs where I found the new environment variable to use.

I would accept this if it were optional. As in, add a create_under_workspace_root boolean flag or something that would enable this behavior.

@jvolkman sorry for the delay on this. I added a venv_location argument that allows the user to define where they want their venv to be generated relative to the workspace root.

Thanks @ArmaanT!


Add support for going backwards through paths

Can't remember if this is something that should get added to path profiling or if it can be tacked on later

Ideally, paths can include negative wheel velocities. At this point, OkapiLib is committed to supporting the following of paths in a reversed fashion, but I want to avoid having users to this if at all possible. It's always more intuitive to generate a path that has the robot go backwards than reversing a path.
We must also consider paths that include both positive and negative wheel velocities, like paths that include tight turns. I would like to see support for these paths as well.

That makes sense, it had been a minute since I looked at how Okapilib handles reversing paths. I can work on supporting reversed paths.
As for supporting both positive and negative wheel velocities, that's currently supported when going forward at least :smile:

I can work on supporting reversed paths.

OkapiLib works by negating the target wheel velocities after the motion profile is generated, so no support is required from the motion profile generator.


Detecting more than 2 digits

Hi, I was wondering if this code can detect more than 2 digits per picture. I am training it with pictures with 4 digits, and it has only been detecting 2.

I don't think training has been done properly. Can you show the detected image?

The solution I have found for that so far is to divide the image in two parts each with 2 digits since 2 are detected easily.

Do you know happen to remember what file I could use to print the digits that have been detected ?

I didn't understand the question.

I just want to save the detected digits to a database, but I am not sure in what file I should be adding the code for that. It's probably obvious, but I haven't worked with CNN before.

It creates various bounding boxes instead of 2 for 2 digit number . Is this happening for everyone?

Hi,
I have this problem, please !!
RuntimeError: The layer has never been called and thus has no defined output shape.
It happens in feature.py  !!!!!!!
RuntimeError                              Traceback (most recent call last)
~\AppData\Local\Temp/ipykernel_1144/3722384473.py in
2
3 # 1. create yolo instance
----> 4 yolo_detector = create_yolo("ResNet50", ["0", "1", "2", "3", "4", "5", "6", "7", "8", "9"], 416)
~\Documents\Pythons\test_yolo\Penny4860\Yolo-digit-detector\yolo\frontend.py in create_yolo(architecture, labels, input_size, anchors, coord_scale, class_scale, object_scale, no_object_scale)
33     n_classes = len(labels)
34     n_boxes = int(len(anchors)/2)
---> 35     yolo_network = create_yolo_network(architecture, input_size, n_classes, n_boxes)
36     yolo_loss = YoloLoss(yolo_network.get_grid_size(),
37                          n_classes,
~\Documents\Pythons\test_yolo\Penny4860\Yolo-digit-detector\yolo\backend\network.py in create_yolo_network(architecture, input_size, nb_classes, nb_box)
14                         nb_box):
15     feature_extractor = create_feature_extractor(architecture, input_size)
---> 16     yolo_net = YoloNetwork(feature_extractor,
17                            input_size,
18                            nb_classes,
~\Documents\Pythons\test_yolo\Penny4860\Yolo-digit-detector\yolo\backend\network.py in init(self, feature_extractor, input_size, nb_classes, nb_box)
30
31         # 1. create full network
---> 32         grid_size = feature_extractor.get_output_size()
33
34         # make the object detection layer
~\Documents\Pythons\test_yolo\Penny4860\Yolo-digit-detector\yolo\backend\utils\feature.py in get_output_size(self)
57
58     def get_output_size(self):
---> 59         output_shape = self.feature_extractor.get_output_shape_at(-1)
60         assert output_shape[1] == output_shape[2]
61         return output_shape[1]
~\AppData\Roaming\Python\Python38\site-packages\keras\engine\base_layer.py in get_output_shape_at(self, node_index)
1962       RuntimeError: If called in Eager mode.
1963     """
-> 1964     return self._get_node_attribute_at_index(node_index, 'output_shapes',
1965                                              'output shape')
1966
~\AppData\Roaming\Python\Python38\site-packages\keras\engine\base_layer.py in _get_node_attribute_at_index(self, node_index, attr, attr_name)
2558     """
2559     if not self._inbound_nodes:
-> 2560       raise RuntimeError('The layer has never been called '
2561                          'and thus has no defined ' + attr_name + '.')
2562     if not len(self._inbound_nodes) > node_index:
RuntimeError: The layer has never been called and thus has no defined output shape.


Attachment Improvements

Improves attachment support in Modmail-Viewer with a lightbox, better formatting, and a more discord like display for non media files.

No longer targeted to v1.
Attachments will be broken soon anyways and I don't have enough time to do anything beyond potentially somewhat fixing them.


Add assign to README documentation

fixes #23
I'm not sure if this is the best way to describe assign but my attempt is also a thanks for running the Elixirconf2015 workshop. :beers:

Thank you!


ConvertLambdaExpressionToMethodGroupAnalyzer null exception

#Bug
Is there anyway to get more info from the build process? From the error msg cannot find out what is the cause.
3>CSC : warning AD0001: Analyzer 'CodeCracker.CSharp.Style.ConvertLambdaExpressionToMethodGroupAnalyzer' threw an exception of type 'System.NullReferenceException' with message 'Object reference not set to an instance of an object.'.
Version: 1.0.3

@sharethl You can catch InnerExceptions and StackTrace.

If you can find the specific method that threw the error we can try to repro. I am closing the issue until we can get code that we can verify, feel free to reopen with the example.


Add missing debezium-postgres connector in distribution

Motivation

debezium-postgres connector is missing in distribution (build)

Modifications

assemby updated

run cpp tests
run java8 tests

run Integration Tests


Encrypt data with value is zero number

!0 always return true, so can not encrypt value = 0

Coverage remained the same at 85.932% when pulling b2f9b667eee6faf0b0600f40deb1fcd8f547f93d on hansanwok:patch-1 into 30668de1135f5ebb8185038c4c1bfdfa8f26d2df on softvar:master.


Document examples without link for examples

Document examples without link for examples

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

ID: d133f522-5f70-76a1-22b3-dbf90606ce7e
Version Independent ID: d809f541-abdf-5989-aac7-a38aa407d471
Content: Import document format guidelines - QnA Maker - Azure Cognitive Services
Content Source: articles/cognitive-services/QnAMaker/reference-document-format-guidelines.md
Service: cognitive-services
Sub-service: qna-maker
GitHub Login: @diberry
Microsoft Alias: diberry

@vglu Could you please provide more details of the examples your are looking for? There are two links to documents that can be used as examples to create a Kb.
Product Manuals
Brochures

@RohitMungi-MSFT Last line on this document "Document examples" not linked with anything.
If this button - why I cant click it, if this table - why this table from one single element, if this header - where description ....

@vglu Apologies for missing that earlier and thanks for pointing this out.
@diberry Are we missing any content here?

@RohitMungi-MSFT np, have a good day

Thank you for reporting it. Will have a fix published today. #please-close


[CGP-70] Add crowdfunding use case

Import existing code
Add refund txn
Remove "fundsAtAddress" from contribution script, use txn-specific information instead

Oh yes, you also need to add this to default.nix. You can find the line for plutus-prototype and then more-or-less copy that.

@michaelpj

Generally looks good. You need to use stylish-haskell on your code - see the open PR with some CONTRIBUTING.md docs.

Actually, maybe this should live under docs/. I see no point in enforcing style guidelines for production code for (mock) examples.

I see no point in enforcing style guidelines for production code for (mock) examples.

I think it's ok to enforce them for mock examples too. It makes the code easier to read for people familiar with the project, and the examples can be built during CI without having to add exceptions to the rules. And besides, I've already edited the commits anyway :)

Actually, maybe this should live under docs/. I see no point in enforcing style guidelines for production code for (mock) examples.

I think all our code should be up to scratch. Apart from anything else, part of the point of having code guidelines is to make it easy for others to collaborate on the code, and I expect other people will touch this code at some point. It's also possible that this will graduate to "real" code if we start running it as a test on our mock blockchain, in which case it should be production quality IMO.

btw I suggest using a label instead of changing the title to include WIP (I made "Do not merge") for this reason.

What's the status of this? Ready for a re-review, or still pending me fixing some bugs?

What's the status of this? Ready for a re-review, or still pending me fixing some bugs?

The crowdfunding validator script compiles now, I'm going to add a unit test to show what the output looks like. Then it can be merged.

Great work!

@michaelpj ready to review now

crowdfunding.plc.golden is 91.9 kB in size (5.16 kB when compressed). That seems quite large to me (especially considering that it contains a lot of errors instead of library functions)

crowdfunding.plc.golden is 91.9 kB in size (5.16 kB when compressed). That seems quite large to me (especially considering that it contains a lot of errors instead of library functions)

:man_shrugging: these programs just are going to be quite bulky. Note that joining all the lines reduces it to 27K unzipped (probably where a lot of that compression win is coming from!).
On reflection I don't think checking this program in as a golden test is that helpful - it would be more helpful to evaluate it on some expected input and check that it does what we expect.

Also see the new section in CONTRIBUTING.md about adding a package, in particular this should probably go in release.nix too.

You should be able to tell if things are going okay by running nix build -f default.nix plutus-use-cases in the root.

You should be able to tell if things are going okay by running nix build -f default.nix plutus-use-cases in the root.

I made some changes recently which messed up my nix setup. Currently trying to fix that!

Okay, I'm going to merge now, if @mchakravarty wants to add comment we can address them later.


sct_propseg add option to propagate a elliptical tube (adapted for cervical regions)

Currently we can only specify the radius.
Problem, on T1 images of cervical regions it nearly never works because:
(i) too elliptical
(ii) not enough contrast to deform

Also enable better CONTRAST of the viewer

It would be easy to compress the initial mesh in one direction, to make it look like an elliptical tube.  The command parameter would be -radius x,y where x is the radius in the anterior-posterior direction and y is the radius in the left-right direction. If the user provides one radius with -radius x, both AP and LR radii are the same. Values of radii are in millimeters.

Closing because:

isolated case
sct_deepseg_sc is replacing propseg


[SPARK-23698][Python] Avoid 'undefined name' by defining version

What changes were proposed in this pull request?
Prevent linters from raising undefined name '__version__' by initializing the variable before setting it via a call to exec().  This is the last remaining issue related to the work done in #20838
How was this patch tested?

$ python2 -m flake8 . --count --select=E9,F82 --show-source --statistics
$ python3 -m flake8 . --count --select=E9,F82 --show-source --statistics

Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Jenkins, ok to test.
LGTM pending Jenkins.
We should add a follow up to add these linter rules to ./dev/lint-python

It should have been better fixed together rather then 3 PRs to fix the same instances.

ok to test

Test build #95243 has started for PR 22214 at commit a077542.

Test build #95243 has finished for PR 22214 at commit a077542.

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

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

Merged build finished. Test PASSed.


Navbar

Created a navbar that allows users to navigate between sections of the website.

Thanks @kchinna for contributing to this project.
I like the idea of having a navbar but something more minimal that goes with the simplistic design of this template.
Also your solution doesn't account for mobile screens.
Please don't change directly in the main.css(minified) file, rather use the .scss files.


nethost  Hosting Sample- Invoking simple method via load_assembly_and_get_function_pointer

Apologies if this is the incorrect place for this question but I think I'm missing something in how load_assembly_and_get_function_pointer from the hosting example works.
In the hosting example it uses load_assembly_and_get_function_pointer to get a pointer to the C# method: public static int Hello(IntPtr arg, int argLength) which works fine.
In my tests though, I want to just invoke a more simple method: public static void HelloSimple() but I'm unable to get this to work, load_assembly_and_get_function_pointer  will return error code (-2147024809 / 0x80070057) - I'm not 100% sure what these error codes relate to. I couldn't find them on https://github.com/dotnet/runtime/blob/main/docs/design/features/host-error-codes.md
I can easily get my methods to invoke if I ensure a parameter is passed and a value is returned. Is this some kind of requirement when invoking C# or perhaps I'm missing some additional code required to allow me to invoke more simple methods?

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

ID: 83da7030-b5f1-72ad-71f6-424ff45b8b7f
Version Independent ID: a98926cc-64ab-2911-e4b8-1eaf4573dfe4
Content: Write a custom .NET runtime host - .NET
Content Source: docs/core/tutorials/netcore-hosting.md
Product: dotnet-fundamentals
GitHub Login: @mjrousos
Microsoft Alias: tdykstra

@mjrousos Can you help with this question?

ping @mjrousos

Hi @comeradealexi, load_assembly_and_get_function_pointer takes a parameter that specifies the delegate type name. If no delegate type is specified, then it defaults to expecting int (IntPtr args, int sizeBytes). If you want to call methods with different signatures, you should be able to just specify the delegate type to use that matches the method's signature. Additional details are available here.


ls: cannot access '/tmp/sphinx-err*': No such file or directory

https://github.com/flywire/tute/actions/runs/4624379652/jobs/8179156788#step:2:258
Wrong path, main folder is repeated.

There are some errors in your workflow, but pages print an unrelated error message (it wants to print the detailed log but can not
find the correct folder of the error log).
The real error is:
 Running Sphinx builder
  Running Sphinx v6.1.3

  Configuration error:
  config directory doesn't contain a conf.py file (/home/runner/work/tute/tute/docs)

pages@bugfix/disable-errlog-dumping disable the detailed log output, you can have a try if necssary.

There are some errors in your workflow

Yes, but I'm not sure what. It would be good if there was a Minimal Working Example.


restrict SAML service lookups to matching entityIDs

Following the addition of SamlIdPServicesManagerRegisteredServiceLocator, unidentified service IDs are evaluated as possible SAML entityIDs against known SAML services, in addition to regular service ID matching as performed by DefaultServicesManagerRegisteredServiceLocator. This introduces an interesting failure case.
First, we need a SAML registered service that retrieves its metadata over MDQ, but it has not yet been retrieved, or the cached copy has expired. Now, we fire a request bearing a service ID not related to the SAML service; let's say it's not an entityID at all but a regular CAS service ID. What will happen is that, at some point, a call to locate() on SamlIdPServicesManagerRegisteredServiceLocator will fire in AbstractServicesManager, providing a predicate entry -> entry.matches(serviceId). Before that predicate is evaluated, the candidates will be filtered by the BiPredicate on the extending class, which will dispatch a call to SamlRegisteredServiceServiceProviderMetadataFacade.get. After a series of attempted lookups, this will throw as no metadata is found - performing an MDQ lookup with the provided service ID is useless as it is not a SAML service. This will be logged as a failure to locate metadata for the candidate service, not the service ID being queried.
This also extends into misconfigured SAML services - if one uses filesystem metadata, for example, that does not exist, it will fail every service (other than SAML services with higher precedence, I believe), which is not ideal.
There are a couple of ways to deal with this. The code I've changed here performs a check with matches() before actually doing any attempt to resolve the metadata. Another option would be to change the filter order on DefaultServicesManagerRegisteredServiceLocator to evaluate the provided Predicate first, but I feel this is making implicit in the usage pattern something that should be explicit: the server ought not to perform a costly metadata lookup if the entityID of the registered service does not even match the provided service ID.
I believe this could be tested for by using Mockito in SamlIdPServiceManagerRegisteredServiceLocatorTests to ensure that get is not called on the metadataFacade, but haven't gotten that far yet.

Addressed the relevant issues (I think, though running the tests locally is still not working on my box)

Ok, so static mocks don't work without mockito-inline, which isn't that surprising, but I obviously shy away from wholesale changing over the mockito dependency for the entire project.
Unfortunately, mocking a resolver will not work, as the resolver must be passed to the locator as an argument, and the mocked resolver does not have the correct type.


Mobius (Bulkrax): handle bs_isCollection and bs_isCommunity fields

Story
Ref:

#27

In mobius' CSVs, the bs_isCollection and bs_isCommunity columns represent whether the record should be a Collection or not.
Acceptance Criteria

[ ] When importing into the Mobius tenant with a CSV that has a column named bs_isCollection with the value of TRUE, the data in that row should be used to create a Collection instead of a work
[ ] When importing into the Mobius tenant with a CSV that has a column named bs_isCommunity with the value of TRUE, the data in that row should be used to create a Collection instead of a work
[ ] Ensure that parent-child relationships still work as expected

[ ] Child work, parent collection
[ ] Child collection, parent collection

Testing Instructions and Sample Files
The provided sample files don't include an example of this data. A CSV will need to be created by hand to test

Notes
This was clarified in an email chain with the client. Jill has access if needed.

Note: All collections currently are created as private (because the spreadsheet doesn't specify permissions). What is the desired behavior?

SoftServ QA ✅
Importer


Publish the spec and javadoc

We should put the (rendered) spec and javadoc online somewhere because ATM it's impossible to link to them.
Is there any formal placement for those @kenfinnigan ?

Not sure if anything is done at the platform level.
@kwsutter?

When going through the release candidate process, it had me attach the spec (which I did as pdf and html form) to the git release,
https://github.com/eclipse/microprofile-context-propagation/releases/tag/1.0-RC2
However, even the html doc here seems to function as a download rather than displaying in a browser, and this doesn't address the JavaDoc at all.
When browsing through the spec doc, I noticed several broken links from the release notes section,
http://download.eclipse.org/microprofile/microprofile-context-propagation-1.0/microprofile-context-propagation.pdf
http://download.eclipse.org/microprofile/microprofile-context-propagation-1.0/microprofile-context-propagation.html
http://download.eclipse.org/microprofile/microprofile-context-propagation-1.0/apidocs/
I suspect these links are broken because they are anticipating the location for the final released version of the spec, and we are still in release candidate.
That said, backing up from this location, I found the following for 1.0 RC 2,
https://download.eclipse.org/microprofile/microprofile-context-propagation-1.0-RC2
which has both the JavaDoc and the spec (both as html and pdf) which is directly viewable in a browser rather than as a download like the git releases.

@FroMage We have our javadoc automatically rendered here: https://javadoc.io/doc/org.eclipse.microprofile.context-propagation/microprofile-context-propagation-api/1.0-RC2
If you go to the top of the README for this repo, there is a green "[javadoc | 1.0-RC2]" badge at the top, next to the other badges.

Also, it would be nice if the microprofile.io website could have links to all the javadoc/spec docs for all of the various components, so users don't need to go fishing around in github repos or other sites.

Also, it would be nice if the microprofile.io website could have links to all the javadoc/spec docs for all of the various components, so users don't need to go fishing around in github repos or other sites.

Given that, does this issue need to be raised against a different repository?


Double : inserted during completion

What happened?

If I type aws:s3 then the following sequence :, BACKSPACE : , I should get only one : but I get two.

Steps to reproduce
name: provider
runtime: yaml
description: A YAML program which uses a provider
resources:
  test:
    type: aws:s3$

Type : at the cursor ($).
Expected Behavior
Expect a : to appear and the next completion to show up.
Actual Behavior
Two :s appear.
Output of pulumi about
On release 0.1.6-pre
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Note: completion must be active for this effect to occur.


The server does not launch.

I checked out the code and ran all the necessary build and installs on a linux (ubuntu 19.04) machine.
Ran the following command to launch the server.
docker-langserver --socket=3000

The moment I run the above command, the server just exits on its own.
> tsc --version
Version 3.9.5
> node --version
v12.16.3

@cotigao Did you open up port 3000 so that it is listening for connections?

@rcjsuen oops! Guess I got the understanding wrong. I thought the LSP server would be listening on 3000 and the client (IDE) would connect to it.  So turns out the client (IDE) needs to start a server that's listening, which means the LSP server (that acts like a client )connects to the client (IDE, which is a server listening on port 300). Please correct me if I have got it wrong, if you feel

So turns out the client (IDE) needs to start a server that's listening, which means the LSP server (that acts like a client )connects to the client (IDE, which is a server listening on port 300).

@cotigao That is correct.

@rcjsuen If I may ask, is there a specific reason to have it that way?

@cotigao See https://github.com/microsoft/vscode-languageserver-node/issues/245#issuecomment-336054699.

@rcjsuen Thanks! That seems a bit counter-intuitive. But then I guess it is fine because LSP does not mandate on what medium is to be used for the server and client to establish the connection and  to exchange messages.
We can close this issue. Thanks for the prompt respone.

We can close this issue. Thanks for the prompt respone.

No problem. Happy to help.


PS2 freezes at Checking game region

I use an SCPH-39001 with modbo 4.0 chip. I can use the burned tonyhax disc but when I swapped the CD, it stopped at Checking game region step and never goes on.

Which version have you used?

Which version have you used?

I'm using v1.4.2

Okay thanks for the report. This issue has been apparently introduced while attempting to fix issue #95 (pinging @DarthMotzkus which was the reporter of the issue).
That English translation uses a terrible hack - it essentially expects the sectors read from the CD to be at a predefined address, and they assumed (and I believed that) it was fixed through all PS1 and PS2 consoles.
However it is not - all PS1 consoles I've seen use 0xA000B070, but PS2 consoles use 0xA000A8D0 instead. Hence their approach is totally flawed, and attempting to make tonyhax compatible with it is what caused this breakage.
I will thus be rolling back this change and leaving it as it was before, and releasing a new v1.4.3 in a couple minutes with the old behaviour.

Version v1.4.3 has been released, rolling back to the old behaviour and fixing this issue. Thanks for the report!

Hi @socram8888, it breaks anything else than ps2 support? Can you send me the 1.4.2 final to save here. I will not use it on ps2. Still using the beta and i need mizzurna working... Thanks!

@DarthMotzkus You should be able to use the v1.4.2 beta I sent you - there's no difference between that version and the final v1.4.2 I published other than a different version number: https://github.com/socram8888/tonyhax/issues/95#issuecomment-873667071


restrict TE in Flex

I tried restricting TE from the FLEX by using optimizer.set_players_with_same_position({'TE: 1}).  It does not seem to work,
I am loading a custom csv and creating list of players.  I have attached the csv as excel file.
NFL_op_input_20191215.xlsx

I'm facing the same issue.  Would it be possible to get FLEX % distribution by position (i.e. TE - 20%, WR - 30%, RB - 50%)?  Thanks for all that you do!

I would also like to say that selection Flex positions would be useful.  I
was trying to get that to work yesterday.
As simple as Flex, use WR, use RB, use TE.  Each is on or off.  I am not
sure a percentage is needed as that would be calculated from the optimizer
but I guess it wouldn't hurt to also have exposure.
On Tue, Sep 15, 2020 at 10:55 AM hunterjohn22<EMAIL_ADDRESS>wrote:

I'm facing the same issue. Would it be possible to get FLEX % distribution
by position (i.e. TE - 20%, WR - 30%, RB - 50%)? Thanks for all that you do!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DimaKudosh/pydfs-lineup-optimizer/issues/193#issuecomment-692770579,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQKFFZW5TVCY6JHGLMNCY3SF555VANCNFSM4RAOTMPA
.

I'm also interested in this feature, right now I'm often having to turn one position type completely on or off as well. I think the ability to set a relative percentage for each position would be great, even if the optimizer only roughly followed the pattern.

you can remove the available positions from the settings file, run how many lineups you want then change it to WR or what ever and run more lineups since i havent figured out how to do it with coding yet

I would start with a simple question - why are you projecting TE (or some other position) to have scores that would allow them to land in your optimal lineup in the first place? If you are trying to build tournament lineups, the first approach would be to alter your projections to reflect the intuition that TE doesn't score enough points to win a large-field tournament. The easiest way to do this is to generate your lineups through multiple runs of the optimizer and apply a greater amount of jitter to positions like WR and RB than TE. I've posted some examples previously that show how to do this. Basically, you create a new pool of Player objects by randomly altering the existing Player objects according to your own criteria and then load them into the optimizer, generate lineups, then repeat the process again.
You can also do this as a post-optimization step. You have a couple of possible approaches:
(1) Keep generating lineups until you hit the desired number that meet your criteria (in essence, throw out some "optimals")
(2) Generate a large number of lineups and then use some genetic algorithm-like techniques to modify them
So, for option number 1, it would look like:
n_lineups_wanted = 150
lineups = []

# this is a generator so you can use a very large number without worry
for lineup in optimizer.optimize(10000):
    # apply test criteria here
    if test_criteria_met:
        lineups.append(lineup)
    if len(lineups) >= n_lineups_wanted:
        break

Now you might say "I don't want to throw out optimal lineups" but you've already decided to throw out what the algorithm says is optimal with your exclusion criteria.
Option number 2 would look like the following
def mutate(lineups, players):
    """Make various changes to lineups"""
    # mutation code here
    return mutated_lineups

n_lineups_wanted = 150
lineups = list(optimizer.optimize(n_lineups_wanted))
mutated_lineups = mutate(lineups)

you can remove the available positions from the settings file, run how many lineups you want then change it to WR or what ever and run more lineups since i havent figured out how to do it with coding yet

I tried this by adjusting the uptake csv removing "/FLEX" from "TE/FLEX", but still got TEs in the FLEX albeit at a lesser exposure rate than normal.  Is this the approach you meant?

Change
@SitesRegistry.register_settings
class DraftKingsFootballSettings(DraftKingsSettings):
    sport = Sport.FOOTBALL
    min_games = 2
    positions = [
        LineupPosition('QB', ('QB',)),
        LineupPosition('RB', ('RB',)),
        LineupPosition('RB', ('RB',)),
        LineupPosition('WR', ('WR',)),
        LineupPosition('WR', ('WR',)),
        LineupPosition('WR', ('WR',)),
        LineupPosition('TE', ('TE',)),
        LineupPosition('FLEX', ('WR', 'RB', 'TE')),
        LineupPosition('DST', ('DST',))
    ]

to
@SitesRegistry.register_settings
class DraftKingsFootballSettings(DraftKingsSettings):
    sport = Sport.FOOTBALL
    min_games = 2
    positions = [
        LineupPosition('QB', ('QB',)),
        LineupPosition('RB', ('RB',)),
        LineupPosition('RB', ('RB',)),
        LineupPosition('WR', ('WR',)),
        LineupPosition('WR', ('WR',)),
        LineupPosition('WR', ('WR',)),
        LineupPosition('TE', ('TE',)),
        LineupPosition('FLEX', ('WR', 'RB')),
        LineupPosition('DST', ('DST',))
    ]

or you can create new settings instead and use them when you call get_optimizer
@SitesRegistry.register_settings
class DraftKingsFootballNoTESettings(DraftKingsSettings):
    sport = Sport.FOOTBALL
    min_games = 2
    positions = [
        LineupPosition('QB', ('QB',)),
        LineupPosition('RB', ('RB',)),
        LineupPosition('RB', ('RB',)),
        LineupPosition('WR', ('WR',)),
        LineupPosition('WR', ('WR',)),
        LineupPosition('WR', ('WR',)),
        LineupPosition('TE', ('TE',)),
        LineupPosition('FLEX', ('WR', 'RB')),
        LineupPosition('DST', ('DST',))
    ]


CappedCrowdsale.sol missing parent constructor

Shouldn't the parent constructor be called?
currently:
  function CappedCrowdsale(uint256 _cap) {     require(_cap > 0);     cap = _cap;   }
proposed:
  function CappedCrowdsale(uint256 _cap, uint256 _startTime, uint256 _endTime, uint256 _rate, address _wallet) Crowdsale(_startTime, _endTime, _rate, _wallet) {     require(_cap > 0);     cap = _cap;   }

I use this CappedCrowdsale as a base contract. Then I call both base constructors:
contract MyCrowdSale is CappedCrowdsale {
    function MyCrowdSale(uint256 _cap, uint256 _startTime, uint256 _endTime, uint256 _rate, address _wallet) CappedCrowdsale(_cap) Crowdsale(_startTime, _endTime, _rate, _wallet) {
}

This approach seems a bit cleaner than passing constructor arguments through to the base constructor.

This notation seems very confusing to me. I think it would make more sense if CappedCrowdsale called super(_startTime, _endTime, _rate, _wallet) and required its parent's constructor arguments.

Thanks for bringing this up! This is not a bug but a feature of Solidity we decided to use. Let me clarify.
Since the contracts are designed to use multiple inheritance, they need to be defined like this because otherwise the base constructor can be called different times with different arguments. There is no warning when this happens, as seen in this example. In this case, contract B is making an assumption on the value of a, which holds if B itself is instantiated, but which doesn't necessarily hold for child contracts.
This feature prevents such a bug from happening because the child contract cannot assume the constructor parameters that were used for the parent constructor.


oc-installer does not understand semver, can't install 3.11.375-1

Version
redhat-actions/oc-installer@v1
Describe the bug
oc-installer does not understand oc_version such as 3.11.375-1 (it will strip anything after the bugfix number, in this case, it will change the input to 3.11.375)   - works great with 3.11.374 though.
Steps to reproduce, workflow links, screenshots
With such configuration:
      - name: Install oc
        uses: redhat-actions/oc-installer@v1
        with:
          oc_version: '3.11.375-1'

oc-installer will fail to install oc :
Run redhat-actions/oc-installer@v1
  with:
    oc_version: 3.11.375-1

Installing oc version 3.11.375
Found oc version 3.11.375 at https://mirror.openshift.com/pub/openshift-v3/clients/3.11.375/linux/oc.tar.gz
Downloading oc from https://mirror.openshift.com/pub/openshift-v3/clients/3.11.375/linux/oc.tar.gz ...
Error: Error: Unexpected HTTP response: 404

Although 3.11.375-1 exists: https://mirror.openshift.com/pub/openshift-v3/clients/3.11.375-1/linux/

is using the url input type an acceptable workaround? the code seems to be rather rigid in this.
      - name: Install oc
        uses: redhat-actions/oc-installer@v1
        with:
          oc_version: 'https://mirror.openshift.com/pub/openshift-v3/clients/3.11.375-1/linux/oc.tar.gz'

this would also be satisfied by https://github.com/redhat-actions/openshift-tools-installer/issues/1

hey there @tetchel
Sorry for the long delay to answer you.
We're currently only using the oc-login action (and it's perfect the way it is! thanks!); I have installed the oc and helm CLIs on the runners (we're using GHES with self hosted runners) since we don't require specific versions of those CLIs - so I don't think we'll be using the oc-installer nor the openshift-tools-installer actions.
Not being able to leverage cache with such actions (https://github.com/redhat-actions/openshift-tools-installer/issues/17#issuecomment-833987400) is also a deal breaker IMO.

I think your usage makes sense. I wouldn't be using 'installer' actions if I was using SH runners, either, but rather build them into the runner image.
are you using our self-hosted runner images or your own?

hello @tetchel !
Actually, no I'm not using the redhat-actions runner images; I wasn't aware of them, just had a look and they seem to be images definitions for runners running as pods in k8s.
At my organization (unfortunately behind a private git repo), we're using Terraform to provision a launch configuration + AutoScalingGroup; that allows us to provision our runners directly in AWS as EC2 instances; drawback is the lack of dynamicity in the deployment - we're living with it for now.
When we start running runners in k8s, I'll be sure to check your solution out; I had already identified:

Another k8s based solution
a popular AWS based solution

OK, cool.
Well, to wrap this issue up I am going to close it in favour of https://github.com/redhat-actions/openshift-tools-installer/issues/1 as linked above.


Prometheus error

Home Assistant release with the issue:
0.75.2

Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
Prometheus
Description of problem:
Error
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
prometheus:

Traceback (if applicable):
Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/components/prometheus.py", line 87, in handle_event
    getattr(self, handler)(state)
  File "/usr/src/app/homeassistant/components/prometheus.py", line 186, in _handle_climate
    if unit == TEMP_FAHRENHEIT:
UnboundLocalError: local variable 'unit' referenced before assignment

Additional information:
Looks like this started in the last release or two.

caused by #15232
cc @stenius

Thanks, it's working in 0.81.1


Missing gamestate modifiers

The Savegame system will happily add gamestate modifiers to the save and publish them for execution but not all are handled yet:
Handling new modifiers

[x] GSModDisableAttackTrigger
[x] GSModRemoveItem
[x] GSModChangeNPCState - only triggered by instruction which fully handles it
[x] GSModDisableTrigger
[x] GSModRemoveModel  - 76578bf
[x] GSModSetTrigger
[x] GSModSetNPCModifier

Handling old modifiers

[x] GSModDisableAttackTrigger
[x] GSModRemoveItem
[x] GSModChangeNPCState
[x] GSModDisableTrigger
[x] GSModRemoveModel
[x] GSModSetTrigger
[x] GSModSetNPCModifier

Closed by 7641f19


chore: fix eslint ignore patterns for vite

Closes: #9068

[ ] Docs
[ ] Tests

Testing Strategy:

@brophdawg11 here's the fixes we talked about earlier today 😄


Installation failed (The system requirements are not satisfied.)

Hi there,
I have problem with installing HAXM in my windows 10 OS.
Details please see below logs:
Version: 7.6.5
Output folder: C:\Program Files\Intel\HAXM
Extract: checktool.exe... 100%
Execute: C:\Program Files\Intel\HAXM\checktool.exe --verbose
CPU vendor          *  GenuineIntel
Intel64 supported   *  Yes
VMX supported       -  No
VMX enabled         -  No
EPT supported       -  No
NX supported        *  Yes
NX enabled          *  Yes
Hyper-V disabled    -  No
OS version          *  Windows 10.0.19041
OS architecture     *  x86_64
Guest unoccupied    *  Yes. 0 guest(s)
The system requirements are not satisfied.
I have also tried v7.7.0, the same error and I have checked the System Requirements
Thanks.

Hi @gerryge ,seems you did not enable VT in Bios and did not disable Hyper-V on your platform. Please enable VT in BIOS ,then type 'bcdedit /set hypervisorlaunchtype off' in cmd terminal with admin, then reboot you PC for a try again.

FYI, I had the same problem (VMX support enabled in bios but showing disabled in the checker, Hyper-V disabled but showing not disabled in checker, windows saying another hypervisor is running in msinfo32).
The thing I had to do to fix this is disabling the Virtualbox Network Adapter in the network cards and reboot. Hope this helps !

Hi @wayne-ma, Thanks for you reply.
Actually, I have enabled the VT and disabled the Hyper-V.

@orion78fr  Thank you very much.
Your approach worked！👍
One thing I need to add is don't forget to restart after disable all the  "*Network Adapter"


import latest default consul.hcl

let's try this again 🙈  - molecule was running fine on my machine, but I couldn't get the workflows running locally with act to work:
[Ansible Molecule/lint  ] 🚀  Start image=ghcr.io/catthehacker/ubuntu:act-20.04
[Ansible Molecule/lint  ]   🐳  docker pull image=ghcr.io/catthehacker/ubuntu:act-20.04 platform=linux/amd64 username= forcePull=false
[Ansible Molecule/lint  ]   🐳  docker create image=ghcr.io/catthehacker/ubuntu:act-20.04 platform=linux/amd64 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Ansible Molecule/lint  ]   🐳  docker run image=ghcr.io/catthehacker/ubuntu:act-20.04 platform=linux/amd64 entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Ansible Molecule/lint  ]   🐳  docker exec cmd=[mkdir -m 0777 -p /var/run/act] user=root workdir=
[Ansible Molecule/lint  ]   🐳  docker cp src=/Users/bene/src/remerge/ansible-role-consul/. dst=/Users/bene/src/remerge/ansible-role-consul/${{ github.repository }}
[Ansible Molecule/lint  ]   🐳  docker exec cmd=[mkdir -p /Users/bene/src/remerge/ansible-role-consul/${{ github.repository }}] user= workdir=
[Ansible Molecule/lint  ] ⭐  Run checkout
[Ansible Molecule/lint  ]   ✅  Success - checkout
[Ansible Molecule/lint  ] ⭐  Run molecule
INFO[0006]   ☁  git clone 'https://github.com/robertdebock/molecule-action' # ref=4.0.7
[Ansible Molecule/lint  ]   🐳  docker pull image=robertdebock/github-action-molecule:4.0.6 platform=linux/amd64 username= forcePull=false
[Ansible Molecule/lint  ]   🐳  docker create image=robertdebock/github-action-molecule:4.0.6 platform=linux/amd64 entrypoint=[] cmd=[]
[Ansible Molecule/lint  ]   🐳  docker run image=robertdebock/github-action-molecule:4.0.6 platform=linux/amd64 entrypoint=[] cmd=[]
| ACTION: Welcome to the molecule action.
| /cmd.sh: line 20: cd: remerge/ansible-role-consul: No such file or directory
| ACTION: running (retry) molecule.
| CRITICAL 'molecule/default/molecule.yml' glob failed.  Exiting.
| ACTION: retry attempt 1.
| CRITICAL 'molecule/default/molecule.yml' glob failed.  Exiting.
| ACTION: retry attempt 2.
| CRITICAL 'molecule/default/molecule.yml' glob failed.  Exiting.
| ACTION: retry attempt 3.
| ACTION: Thanks for using this action, good luck troubleshooting.
[Ansible Molecule/lint  ]   ❌  Failure - molecule
Error: exit with `FAILURE`: 1

Not sure why it doesn't expand ${{ github.repository }} properly

Cool, learned about act today. I'll likely try it in the future!
I'll wait for CI here. You may continue to commit to this branch and PR if the build fails.

Included in version 2.0.0, thanks!


Linking to an expanded workshop archive

Changes

add ID to all accordions, so that adding quarter-year-eventName to the archive url will take you to the relevant accordion
add a button that will copy the link to the accordion
when linked to the accordion, the accordion will load as expanded

Type of change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)

Related Issues
Fixes #167

to do:

[ ] ensure that clicking the link icon doesn't open the accordion
[ ] if the url is to a valid accordion, set isExpanded to true and render it expanded.


Error: @php directive does not work as expected in an assumed scenario

Here is a quick example to describe the error:
@extends ('layout/main')

@php
  // This is php code
  $from = 10;
  $to = $from + 10;
@endphp

@section('body')
  {{ $to }}
@endsection

It is assumed to prepare the variable $to to be usable in the current viewfile, but it returns this error: Deprecated: htmlentities(): Passing null to parameter #1 ($string) of type string is deprecated in C:\xampp\htdocs\crow\vendor\corviz\crow\src\Crow.php(138) : eval()'d code on line 1

Okay I tried to move the @php block to inside the @section block and it works. I prefer to introduce a way to share all codes from @php block through all that view file for a better code logic organizing.


Expose implements and mixins of DeclareClass AST

Closes #5463
Closes #6096
Updates estree_translator.ml to expose those two fields of DeclareClass as we need those for Prettier. I fixed esprima compatibility tests that broke, but I'm not sure if/how I should add regression tests when the declaration includes an interface or mixin.
I'm not familiar with this codebase, let me know if I should do anything differently.
Thanks!
cc @mroch

cc @mroch

thanks!


NVM not able to uninstall installed node

Operating system and version:
nvm debug output:

nvm ls output:

How did you install nvm?
By downloading nvm-setup.exe from https://github.com/coreybutler/nvm-windows/releases
What steps did you perform?
What happened?
Not able to uninstall node 16..15.1
What did you expect to happen?
Want to uninstall node 16..15.1
Is there anything in any of your profile files that modifies the PATH?

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

This is nvm-windows, which is a different project - real nvm (this one) doesn't differentiate 64bit vs 32bit.

From where I should download real nvm

From this repo's readme. On windows, it requires cygwin, git bash, or WSL.


Document enabling OAuth for bot in non-public azure

Describe the bug
For a bot to use OAuthPrompt in non-public azure clouds (like gov ), the following code must be added for a c# bot, in the startup.cs file:
string uri = "https://api.botframework.azure.us";
MicrosoftAppCredentials.TrustServiceUrl(uri);
OAuthClientConfig.OAuthEndpoint = uri;

Expected behavior
Update the article Add authentication to a bot  to describe the required steps.
Additional context
See issue https://github.com/microsoft/botbuilder-dotnet/issues/4924.

Related  PR https://github.com/MicrosoftDocs/bot-docs-pr/pull/2585 ready to be merged.


[feature] cupy: repeat method

I need this method to implement forward_gpu for https://github.com/pfnet/chainer/pull/599.

It would make the implementation of Contrastive Loss simpler.
Related to #553.


fails crunchyroll

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.03.10. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.03.10

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'http://www.crunchyroll.com/akame-ga-kill/episode-17-kill-the-curse-662265', '-o', 'E:\\000\\0-Descargados/%(series)s/%(title)s.%(ext)s', '--download-archive', 'E:\\000\\0-Descargados/listado.txt', '--cookies', 'cookies.txt', '-f', 'best[height=1080]', '--write-sub', '-k', '--sub-format', 'ass', '--sub-lang', 'esLA', '--recode-video', 'mp4', '--ffmpeg-location', '.\\bin\\']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2018.03.10
[debug] Python version 3.4.4 (CPython) - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg N-81592-g2793ebd, ffprobe N-81592-g2793ebd, rtmpdump 2.3
[debug] Proxy map: {}
[Crunchyroll] 662265: Downloading webpage
ERROR: Unable to download webpage: [WinError 10054] Se ha forzado la interrupción de una conexión existente por el host remoto (caused by ConnectionResetError(10054, 'Se ha forzado la interrupción de una conexión existente por el host remoto', None, 10054, None)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpzznjsz2q\build\youtube_dl\extractor\common.py", line 519, in _request_webpage
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpzznjsz2q\build\youtube_dl\YoutubeDL.py", line 2199, in urlopen
  File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpzznjsz2q\build\youtube_dl\utils.py", line 989, in http_response
  File "C:\Python\Python34\lib\http\client.py", line 543, in read
  File "C:\Python\Python34\lib\http\client.py", line 629, in _readall_chunked
  File "C:\Python\Python34\lib\http\client.py", line 699, in _safe_read
  File "C:\Python\Python34\lib\socket.py", line 378, in readinto

Description of your issue, suggested solution and other information
fails crunchyroll.
It worked fine until 2 weeks ago

Network issue on your side.

Sorry
but n I have problems to see from browser
and my connection is stable and works well.
Can it be some other problem?


Simplify message handling

This makes message handling more symetric.   Before:
// sending
MyMessage msg = new MyMessage();
connection.send(MsgId, msg);

...
// receiving
public void MsgHandler(NetworkMessage netMsg) {
    MyMessage msg= netMsg.ReadMessage<MyMessage>();
    ...
}

connection.RegisterHandler(MsgId, MsgHandler);

notice how asymmetric this API is,  you send a MyMessage object,  but you receive a NetworkMessage object.
With this pull request, now you can do this:
// sending
MyMessage msg = new MyMessage();
connection.send(MsgId, msg);

...
// receiving
public void MsgHandler(MyMessage msg) {
    ...
}

connection.RegisterHandler<MyMessage>(MsgId, MsgHandler);

Now the API is fully symmetric.   Note that the previous mechanism still works to maintain compatibility.

can't we get rid of the previous mechanism then?
or is this needed for something important?

It would break the code for everyone else.
The new mechanism simply creates a delegate and passes to the old mechanism,  so there is no code redundancy.

Makes sense to keep it in place in the interim. Perhaps deprecate it in the future and remove altogether as a part of a clean up effort.
Either way, thanks for the new solution!

I like the depreciation route. Would give people some time to migrate over.

This PR is good to go,  it can be merged,  but I have an even better idea,  please take a look at #418

@paulpach I like this change a lot.
should we add an obsolete warning to networkmessage in this PR too?


feat: Creates variable to customize time_sleep due VPC-SC  propagation time

This PR adds variable to customize the time_sleep to wait VPC-SC propagation. Default is 3 minutes.

/gcbrun


readthedocs haven't rebuilt in over a year

https://ipycytoscape.readthedocs.io/en/latest/ is still on version 1.0.3 and looking at https://readthedocs.org/projects/ipycytoscape/ it seems it was last built 1 year and 3 months ago

@marimeireles can you either have a go at fixing this and/or add me as a maintainer to the docs so I can try?
I suspect changing the repo source might help, and also possibly what triggers doc builds.

Hey @ianhi.
I don't know what broke the badge. The docs are passing, 2 days ago when you opened this I rebuilt them.
I'll look into to how to add you.
The problem with the docs is that they don't have a hook with PRs? Or they're not working, I don't remember anymore.

They're building and passing fine but the animated examples you added aren't working anymore because the API is not backwards compatible. So we have to fix that! :)

To me it looks like https://ipycytoscape.readthedocs.io/en/latest/ has not been updated in a while but https://ipycytoscape.readthedocs.io/en/master/ seens to be up to date.


Sort items alphanumerically

Hello,
Been trying to add the following items in the list: 50, 100, 200, but they get sorted like so: 100, 200, 50. Adding a "0" in front of the 50 appears to be the only option though very unpreferable.
This does not only apply to numbers but also other numerical items such as IP addresses.
Can we make a directive like this: "Sort": "alpha", with options such as alpha (alpha numeric), natural, string length (or even random...)?
Alternatively an option to disable auto-sort, so items appear in the exact order as they are placed in the json config file.
Thanks!

@PetaByet Hello, I'm going to close this issue and refer you to #117 where there is a discussion regarding this topic.


Add Test Cases for all existing Event Commands

Added test cases for all existing event commands as we were lacking test cases.

Codecov Report

Merging #156 into master will increase coverage by 4.50%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##             master     #156      +/-   ##
============================================
+ Coverage     63.90%   68.41%   +4.50%
- Complexity      689      750      +61
============================================
  Files           114      114
  Lines          2391     2390       -1
  Branches        252      251       -1
============================================
+ Hits           1528     1635     +107
+ Misses          743      644      -99
+ Partials        120      111       -9

Impacted Files
Coverage Δ
Complexity Δ

...seedu/address/logic/commands/FindEventCommand.java
61.53% <0.00%> (+11.53%)
6.00 <0.00> (+3.00)

...rc/main/java/seedu/address/model/ModelManager.java
84.61% <ø> (+15.05%)
38.00 <0.00> (+6.00)

src/main/java/seedu/address/model/event/Event.java
79.16% <100.00%> (+47.16%)
10.00 <0.00> (+6.00)

src/main/java/seedu/address/model/event/Time.java
66.66% <0.00%> (+6.66%)
6.00% <0.00%> (+1.00%)

...in/java/seedu/address/model/event/Description.java
70.00% <0.00%> (+20.00%)
6.00% <0.00%> (+3.00%)

...ava/seedu/address/model/event/UniqueEventList.java
53.65% <0.00%> (+31.70%)
12.00% <0.00%> (+8.00%)

src/main/java/seedu/address/model/Calendar.java
87.50% <0.00%> (+41.66%)
11.00% <0.00%> (+6.00%)

... and 6 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 e5a67c1...5cb10fb. Read the comment docs.


too much softmax for CTC validation?

Hi @ku21fan,
In test.validation() you're doing log_softmax() in CTC scope:
https://github.com/clovaai/deep-text-recognition-benchmark/blob/master/test.py#L90
and then softmax() in common scope:
https://github.com/clovaai/deep-text-recognition-benchmark/blob/master/demo.py#L73
Seems like to much? :) It may affect confidence_score
Regards,

Hello,
Yes, it was too much.
Thank you for the report!
I just delete & moved to log_softmax(2) in recent version. 8920de93e8f85e9ddcdf117d256b28ccf8ab4d09
However, it would not affect confidence_score.
Try without/with log_softmax(2) in CTC scope.
It would be same :)
Best


IPFS in Brave Announcement

🛑   DO NOT MERGE  🛑

[ ] Add header img (awaiting design shop issue 467)
[ ] Add screenshots
[ ] Add “Download Brave now“ button img
[ ] ? Add gifs of IPFS in action ?
[ ] Embargo lifted by Brave/IPFS campaign team

Hey @alg621! Let me know how this looks to you. Still working on adding in imgs. Thanks!

Hey @alg621! Let me know how this looks to you. Still working on adding in imgs. Thanks!


Add runID to queryDirectlyThroughMatchingRequest

Coverage increased (+0.04%) to 66.955% when pulling f53fe097b799ffe3f053157a20929bc0acb4b91a on andrewjdawson2016:AddRunID into 351b3fd06da515b3ed36bbabdd3efacad2810a92 on uber:master.


Fix transversal NGINX issues

Fix transversal NGINX issues

!testme

For some reason adding the slashes breaks the librephotos UI (images don't load).


VMAlertmanager permission problems with persistent storage configuration

Describe the bug
In the Operator way when creating a VMAlertmanager CRD Object it is possible to define a spec.storage.volumeClaimTemplate for persistent storage of logs and silence rules from Alertmanager.
Unfortunately the user with witch the directory is mounted is the root user and the pod runs as nobody with such a configuration the alertmanager is not able to persist the data.
I know this is only applicable when not using multiple replicas of Alertmanager .
I was able to use an initContainer to chown the mounted directory before. Maybe this could be added in the Documentation?
To Reproduce
apiVersion: operator.victoriametrics.com/v1beta1
kind: VMAlertmanager
metadata:
  name: example-alertmanager
spec:
  replicaCount: 1
  selectAllByDefault: true
  storage:
    volumeClaimTemplate:
      spec:
        accessModes:
          - ReadWriteOnce
        resources:
          requests:
            storage: 100Mi
        storageClassName: ceph-rbd-sc
  extraArgs:
    data.maintenance-interval: 5m
  initContainers:
    - name: volume-mount-hack
      image: busybox
      command: ['sh', '-c', 'chown -R 65534:65534 /alertmanager']
      volumeMounts:
        - name: vmalertmanager-example-alertmanager-db
          mountPath: /alertmanager

Version
victoria-metrics-operator-0.27.0 chart with version 0.38.0
Logs
No response
Screenshots
No response
Used command-line flags
No response
Additional information
No response

VMAlertmanager is actually using alertmanager image from prom/alertmanager which using nobody as default user long time ago [maybe vm images should follow the pattern].
So all the time with spec.storage.volumeClaimTemplate, user will encounter the error and can fix it in three ways:

add initContainers like @Munsio did
enable VM_ENABLESTRICTSECURITY in operator
specify securityContext under pod or container

Prometheus operator doesn't handle or doc this and the charts use user 2000  across prometheus stack.
So we can probably doc this or add to the code, implementing the needed securityContext if extra volumeClaimTemplate is using. I prefer the second option for better experience, but it might mess up some users previous vmalertmanager if they already give root permission to the volume.
WDYT @f41gh7 @Amper

We can probably document this or add some code to implement the needed securityContext if extra volumeClaimTemplate is using. I preferred the second option for better user experience, but it might mess up some users previous vmalertmanager if they already give root permission to the volume.
So I will just add some notes for the field, do you guys have other opinion on this? @f41gh7 @Amper

I think, it'd be great to provide spec.strictSecurity: true per resource configuration. It solves current issue with alertmanger without affecting other components.
It allows to perform migration for insecure components by granular changes.
E.g. you can start for new components adding strict security. Migrate old ones one-by-one into new model and enforce global param at operator env, when migration finished.

Hello @Munsio
operator added UseStrictSecurity for all components including vmalertmanager since v0.39.0.
You can solve this by enable UseStrictSecurity under vmalertmanger.
Close this as completed, free feel to reopen if there is problem.


Add dhannnn's file

Created a branch, created a file and made a commit, and opened a pull request.

Created a branch, created a file and made a commit, and opened a pull request


Fixed last allergen is duplicated

Description
Revert #1877. Last allergen in Ingredients list is duplicated:

Please take a look at my comment at #1877.

Travis tests have failed
Hey @brandenfung,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

Thanks @brandenfung!


Add junit output for kubectl apply for CI pipelines

What would you like to be added: A new output format for kubectl apply logs in the form of JUnit XMLs.
Why is this needed: When managing a cluster with GitOps I would also like to test the validity of the yamls in my CI pipeline before deploying, kubectl apply --dry-run=server seems to be the best option when you have network access to a cluster in your CI pipe, JUnit is a popular output format for testing tools that is supported by multiple related tools (for example, gitlab knows how to visualize the JUnit output of testing tools in merge requests).
I think this is a worthwhile feature to add as more and more people will begin to manage their clusters/apps in git, here's a little python script I made for myself while developing my own GitOps CI pipeline for reference https://github.com/galshi/validate-kubernetes-manifests/blob/main/validate_kubernetes-manifests/main.py.

We don't expect adding XML output, I'd suggest creating your own transformer based on yaml/json output.
/close

@soltysh I don't have access to a k8s cluster, I work with openshift, but oc apply --dry-run=server -o json/yaml seems to just output the jsons/yamls to apply (while the normal output displays whatever applying an object succeeded or any resulting errors).
I assume the same is true for kubectl but can't check it, if that's the case I think some form of structured output for the results of kubectl apply is necessary.

Hi @soltysh, I think you've misunderstood the issue and that it's still relevant, please look at my previous comment.


Basic Gates Workbook Tasks 1.9, 1.10  V2

Basic Gates Workbook Tasks 1.9, 1.10  V2

Failed to validate Task 10


Percent sign spacing

Feedback was received that a space should be present before percent sign in some languages (eg Czech).
As per https://en.wikipedia.org/wiki/Percent_sign#Spacing, the rules around this are somewhat complicated and contextual.  If this is to be implemented, there should be consideration put into exactly how best to do this, and if there is existing localisation support in Python.

There appears to be support for this in Babel:
https://babel.pocoo.org/en/latest/api/units.html
For example,
from babel import units
units.format_unit(12,'percent',locale='en',length='short')
units.format_unit(12,'percent',locale='cs_CZ',length='short')

yields
'12%'
'12 %'

So in principle, we should be able to implement this using software we are already using, and locale variables for city and language we have already setup.