Tutorial: nbdev-hello-world deploy to GitHub Pages action failing

I'm following along with the tutorial and on the initial commit I'm getting a failed action for deploying to GitHub Pages. Here is the log:
Unpacking quarto (1.0.38) ...
209
Setting up quarto (1.0.38) ...
210
Traceback (most recent call last):
211
File "/opt/hostedtoolcache/Python/3.10.6/x64/bin/nbdev_filter", line 8, in
212
sys.exit(nbdev_filter())
213
File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/fastcore/script.py", line 116, in _f
214
return tfunc(**merge(args, args_from_prog(func, xtra)))
215
File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/nbdev/cli.py", line 127, in nbdev_filter
216
with redirect_stdout(dn): filt.nb_proc(nb).process()
217
File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/nbdev/process.py", line 130, in process
218
for cell in self.nb.cells: self._process_cell(cell)
219
File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/nbdev/process.py", line 111, in _process_cell
220
cell = opt_set(cell, proc(cell))
221
File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/nbdev/processors.py", line 194, in add_links
222
nl = NbdevLookup()
223
File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/nbdev/doclinks.py", line 167, in init
224
self.entries = {o.name: o.load() for o in pkg_resources.iter_entry_points(group='nbdev')
225
File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/nbdev/doclinks.py", line 167, in
226
self.entries = {o.name: o.load() for o in pkg_resources.iter_entry_points(group='nbdev')
227
File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/pkg_resources/init.py", line 2471, in load
228
return self.resolve()
229
File "/opt/hostedtoolcache/Python/3.10.6/x64/lib/python3.10/site-packages/pkg_resources/init.py", line 2477, in resolve
230
module = import(self.module_name, fromlist=['name'], level=0)
231
ModuleNotFoundError: No module named 'nbdev_hello_world'
232
Error: Process completed with exit code 1.
The first time it was happening I had underscores in the name but deleted that repo and started over and am still gettin this same ModuleNotFoundError.

Yes, that did it. I figured there was something missing in the tutorial as it seemed simpler than the 90min Youtube tutorial you have. Thanks.


Closes #2546 Updating ABLFL to Null if not "Y" in derive_var_base()example

… example
Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Review the Cheat Sheet. Make any required updates to it by editing the file inst/cheatsheet/admiral_cheatsheet.pptx and re-upload a PDF and a PNG version of it to the same folder. (The PNG version can be created by taking a screenshot of the PDF version.)
[x] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md under the header # admiral (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers). A Developer Notes section is available in NEWS.md for tracking developer-facing issues.
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

Hi @sadchla-codes is this ready for review?

Can you check to see if other examples have ABLFL = N please

Question @bms63: Would you prefer ABLFL ="N" be replace with blank ("") or NA_character_?

Can you check to see if other examples have ABLFL = N please

Question @bms63: Would you prefer ABLFL ="N" be replace with blank ("") or NA_character_?

I think our convention is to use NA_character_.

@sadchla-codes can you please align the test data so easier for folks to read the data sets in the examples and test data?  tyty


Documentation Error: Animation API

On the react-native documentation site, the documentation for the Animation API doesn't look like it's generating correctly.

cc @sahrens this might be related to the AnimationExperimental rename.

Yeah, we removed the Animation API from react-native as it's not being used anywhere and not good right now. I need to remove it from the docs.

https://github.com/facebook/react-native/commit/6a970546966aa190e5d972bca17baa3d1c2a4786
--
Christopher "vjeux" Chedeau
Facebook Engineer
http://blog.vjeux.com/
On Mon, Apr 6, 2015 at 2:44 PM, James Ide<EMAIL_ADDRESS>wrote:

cc @sahrens https://github.com/sahrens this might be related to the
AnimationExperimental rename.
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/issues/709#issuecomment-90254670
.

Good to know, thanks!

@vjeux What are the plans on this?  Any recommendations for animation til then?

I've seen people use react-tweet-state successfully https://github.com/chenglou/react-tween-state

perfect, thx


Add a deprecation warning for the eventBusDispatchToDOM option/preference (PR 11631 follow-up)

Update the waitOnEventOrTimeout helper function to handle internal events consistently with the rest of the viewer components (PR 11631 follow-up)
I overlooked this in PR #11631; sorry about that!
Also, ensure that EventBus instances always track "external" events using a boolean regardless of the actual option value.

Move the dispatchDOMEvent functionality out from the EventBus and add a deprecation warning for the eventBusDispatchToDOM option/preference (PR 11631 follow-up)
It occured to me that similar to the getGlobalEventBus function, it's probably a good idea to also notify users of the fact that eventBusDispatchToDOM is now deprecated.
Rather than depending of the re-dispatching of internal events to the DOM, the default viewer can instead be used in e.g. the following way:
document.addEventListener("webviewerloaded", function() {
  PDFViewerApplication.initializedPromise.then(function() {
    // The viewer has now been initialized, and its properties can be accessed.

    PDFViewerApplication.eventBus.on("pagerendered", function(event) {
      console.log("Has rendered page number: " + event.pageNumber);
    });
  });
});

/botio unittest

/botio-linux preview

Yes, that's indeed a good idea. Thanks!


[code-infra] Fix release:publish:dry-run script

The --registry argument was available when lerna was used. pnpm does not support it, but it does have the same --[dry-run attribute](https://pnpm.io/cli/publish#--dry-run) as npm.
I noticed this when working on https://github.com/mui/mui-x/pull/11875.

I used it without issues. But it's fair to say that it wasn't really a dry run but publishing to a local registry. The pnpm's dry-run works differently - it just doesn't publish.

@michaldudak Thank you for confirming it. 👍
Double-checked that it works.
The suggested port is used by default by verdaccio.


Move under the sprint-guide subdirectory

We will ultimately hosting this at design.thoughtbot.com/sprint-guide.
This moves under that subdirectory, which also opens up a place for the
rest of design.thoughtbot.com to live.
We will eventually merge the repositories, either design-dot will come
in here or the other way around.
I've opten to keep data and styles up at the root so they can be shared
between everything, but I don't feel strongly about that and I'm open to
feedback.
This will be a pretty disruptive change to any in-progress work, so I'm
happy to wait to merge until there is a good time to do that, though I'd
prefer not to let this branch live for too long as then rebasing will
become difficult.

@cpytel I merged the other big PR we were waiting for so I think we're in a pretty good spot for the great rebasing to begin.


Confusing language describing the different lifespans

There seems to be an error in language regarding the lifespans, just above the section "Call services from main"...
The document states: "Scoped objects are the same for each request but different across each request."
I assume it's instead meant to be: ""Scoped objects are the same for each request but different across each session."? (or something similar to that nature)

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

ID: 0d78f540-81fd-1ba9-cb90-591e4ec27d9b
Version Independent ID: 2251f557-dd3a-ec35-2558-6243337db009
Content: Dependency injection in ASP.NET Core
Content Source: aspnetcore/fundamentals/dependency-injection.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

It's right but poorly worded.
See Scoped which is clear.

"Services of a given lifetime shouldn't use a database context with a lifetime that's shorter than the service's lifetime"
What? Time to refactor the docs
How about. "Do not use a database context with a lifetime shorter than the services'"

Fantastic. Do you want to PR this? IF you do, add the link I mentioned above.

No, I tried doing a PR earlier on this but it wasn't working for some reason. Need to get back to reading the docs for now :)

At the top right of the article, select the Edit pen icon:

Select the pen icon again. Save.

+1 for finding this confusing! I assumed it was intended to be "Scoped objects are the same for each request but different across different requests."


Update MessagePack article for .NET 6

Update this section for https://github.com/aspnet/Announcements/issues/454. The breaking change is doc'd here: https://docs.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/6.0/messagepack-library-change.

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

ID: e807e138-f84c-e63e-ab37-eec0d554d3bb
Version Independent ID: 3ac41883-3bc2-30ba-a47f-462196850c12
Content: Use MessagePack Hub Protocol in SignalR for ASP.NET Core
Content Source: aspnetcore/signalr/messagepackhubprotocol.md
Product: aspnet-core
Technology: aspnetcore-signalr
GitHub Login: @bradygaster
Microsoft Alias: bradyg

@fiyazbinhasan  have you used SignalR?

I have few ideas. I can take a look at this 🚀

@fiyazbinhasan I'm going to work on it and hopefully you can review it.

Sure. that would be great! I'll get to learn about message pack 😁


Audio gets muted completely under specific conditions

Godot version
4.2 rc2 / 4.1
System information
Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; <IP_ADDRESS>3) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)
Issue description
In my project I managed to meet some very specific conditions that break the audio system. This looks like engine bug, because it requires all of the specific steps and makes the audio die completely.
Here's the bug (I'm using debug teleport to move faster):
https://github.com/godotengine/godot/assets/2223172/eca766cb-e9cd-42c1-b072-c486d048a32f
Note how in 0:10 the video goes completely silent and then after the gate animation the sounds plays normally. During that silence,  and audio track is supposed to play.
Here's video with the intended effects:
https://github.com/godotengine/godot/assets/2223172/2fa21898-f89e-494a-9d1c-5960923a5361
Note that this is the exactly the same build! The silence is 100% reproducible and the correct sounds is also 100% reproducible. If you look closely, the only thing that changed is that in the second video I didn't touch the save point.
Now, this is the interesting part. In order to trigger the bug I need to:

start in the desert area. When I change areas, the music transition makes two music tracks play together and crossfade smoothly
touch the save point to play its opening and closing animation
when the gate closes, the music is silenced (I tween it to 0 volume)

If I skip any of these steps, the bug does not happen.
As for the bugged silence itself, it's not that the animation audio is not playing. All sound is completely disabled, I tried playing other sound affects at that moment and they are muted too.
EDIT:
After further investigation, silencing the music (Jukebox.silence() call) is the direct trigger of the bug, all other steps are just a setup. I tried silencing the music later and if I call the method mid-animation, the audio goes out immediately. Also it has something to do with 2 music players (see Jukebox.tscn). When I stop the unused one before calling silence() the bug does not happen.
Steps to reproduce
Start the MRP and repeat what I did in the first video. You can use F1 to teleport character to cursor.
Minimal reproduction project
Unfortunately, since the reproduction steps are extremely convoluted, I am not even sure how to extract it into a minimal project. I stripped down my game down to some essential files required to reproduce the bug. That's still 90MB though.
https://www.mediafire.com/file/pwz70vuxjtrqo86/repro_audio_oblivion.zip/file

4.3 dev 6

While the symptoms were fixed, I wonder if it's user error or I did something that triggered engine bug. I don't even know where the error comes from.

Don't use linear_to_db(0).

See https://github.com/godotengine/godot/pull/61935


Wgpu 0.15

Objective
Update Bevy to wgpu 0.15.
Changelog

Update to wgpu 0.15, wgpu-hal 0.15.1, and naga 0.11
Users can now use the DirectX Shader Compiler (DXC) on Windows with DX12 for faster shader compilation and ShaderModel 6.0+ support (requires dxcompiler.dll and dxil.dll, which are included in DXC downloads from here)

Migration Guide
WGSL Top-Level let is now const
All top level constants are now declared with const, catching up with the wgsl spec.
let is no longer allowed at the global scope, only within functions.
-let SOME_CONSTANT = 12.0;
+const SOME_CONSTANT = 12.0;

TextureDescriptor and SurfaceConfiguration now requires a view_formats field
The new view_formats field in the TextureDescriptor is used to specify a list of formats the texture can be re-interpreted to in a texture view. Currently only changing srgb-ness is allowed (ex. Rgba8Unorm <=> Rgba8UnormSrgb). You should set view_formats to &[] (empty) unless you have a specific reason not to.
The DirectX Shader Compiler (DXC) is now supported on DX12
DXC is now the default shader compiler when using the DX12 backend. DXC is Microsoft's replacement for their legacy FXC compiler, and is faster, less buggy, and allows for modern shader features to be used (ShaderModel 6.0+). DXC requires dxcompiler.dll and dxil.dll to be available, otherwise it will log a warning and fall back to FXC.
You can get dxcompiler.dll and dxil.dll by downloading the latest release from Microsoft's DirectXShaderCompiler github repo and copying them into your project's root directory. These must be included when you distribute your Bevy game/app/etc if you plan on supporting the DX12 backend and are using DXC.
WgpuSettings now has a dx12_shader_compiler field which can be used to choose between either FXC or DXC (if you pass None for the paths for DXC, it will check for the .dlls in the working directory).

I'd prefer to default to the DXC shader compiler for DX12 for this PR, as it's faster/supports modern features (FXC doesn't support Shadermodel 6.0+, while DXC does. Note that the techpowerup shadermodel support is inaccurate, as new drivers have upped the support on older GPUs), is actually maintained (unlike FXC, the current default), and is necessary for eg. FSR2 support for users using DX12.
The problem is that it requires the user to get dxcompiler.dll and dxil.dll (from the releases tab on https://github.com/microsoft/DirectXShaderCompiler) and ship them with their game if they plan on supporting DX12. There is an environment variable users can set so they don't have to keep copying the .dlls into every new project.
Currently WGPU logs a warning (sidenote, why are we filtering out WGPUs warning logs?) and falls back to FXC if either of the .dlls are missing.
WGPU wants to switch to DX12 by default for Windows in the near future (probably within the next 2 releases?), so testing this feature (including what docs improvements are needed, error message tweaks, possible bugs, unsupported drivers, etc) is imo pretty important before that happens to try and limit any future papercuts once that happens. (and for now, 99% of Bevy Windows users use Vulkan anyways, since it's the default)

...mention in the migration guide that you should use an empty view_formats (&[]) unless you have a specific reason not to.

Done

Not approving this yet, as when I was using a git branch of wgpu, I was getting errors about multisampled texture creation when MSAA was enabled.

MSAA works fine on my machine on DX12 , Vulkan and webGL in Firefox, but I think most MSAA issues are Linux+Intel+Vulkan or GL which I don't have to test against.

Ideally we'd try to use an sRGB texture_view on the surface if sRGB surface formats aren't supported (afaik only WebGPU doesn't support sRGB surface formats, so if someone somehow gets Bevy working with webgpu before next release, the colours will be wrong). However, I couldn't get it working on Vulkan without spewing thousands of validation errors per second, so I just made a TODO of it at SurfaceConfiguration creation.
Other than that, I think it's ready? Maybe the book should be updated to tell users to download DXC and drop the .dlls into their project if they want to use DX12?

CI failures should be fixed since https://github.com/bevyengine/bevy/pull/7370 and https://github.com/bevyengine/bevy/pull/7368 landed in main. I don't think I need to rebase on main for it to work this time.

I tested all the examples on MacOS/M1.
post_processing and shader_prepass are broken, but both seem unrelated to this PR.

I tested all the examples on MacOS/M1.
post_processing and shader_prepass are broken, but both seem unrelated to this PR.

Looks like the cascaded shadow maps (CSM) PR probably broke both of them, as I'm now getting failures when running those examples after rebasing on main with CSM.
https://github.com/bevyengine/bevy/pull/6997 is a bit of a bodge and needs to be updated for CSM, but should fix them. https://github.com/bevyengine/bevy/pull/5703 is probably the better fix, but might not land in time for the next bevy release?

bors try

This currently panics when Msaa is used on an unsupported format instead of silently falling back to no Msaa (due to wgpu changes). Afaik this is mainly an issue on Linux+Vulkan+Intel Mesa setups.
Ideally we'd have the Msaa on Windows PR lined up (along with 2x and 8x support, since they all require the same querying for supported msaa formats on the Surface's format), but I can probably add a check on surface creation to log an error and fall back to disabling Msaa, and a TODO to remove it once someone does https://github.com/bevyengine/bevy/issues/7194.

Does this also allow us to use const expressions?

Someone ran into an issue with custom paths for the DXC dlls (https://github.com/gfx-rs/wgpu/issues/3433), but there'll probably be a wgpu patch version released in a week or two (so before bevy releases) and I've made a PR to fix it that will most likely be included in the wgpu patch.

Does this also allow us to use const expressions?

I don't know, and I didn't see anything about it in the wgpu or naga changelog when I skimmed it.

@Elabajaba could you rebase? I’m going to give this another look over but I think it’s probably ready to merge.


Simple syntax for querying the model and posterior sample

In this issue, I propose the creation of a new macro @logprob to query Turing models as well as the sampled posterior. Let's take the following model as an example using the syntax of #965:
@model demo(x, y) = begin
    a ~ Normal()
    b ~ Gamma()
    y .~ Normal.(a .* x, b)
end
model = demo(rand(100), rand(100))
chain = sample(model, NUTS(10, 0.65), 10000)

I propose the following syntax:

@logprob a = 1.0, b = 2.0 | model = model -> returns log the prior
@logprob a = 1.0, b = 2.0, x = rand(100), y = rand(100) | model = model -> returns log the joint probability
@logprob 0.2 <= a <= 0.3, 1.0 <= b <= 1.1 | model = model, chain = chain -> returns log the ratio of the number of samples in chain with 0.2 <= a <= 0.3, 1.0 <= b <= 1.1. For discrete distributions, we can also use  a = 2 or a == 2 for example. Passing model here can be optional.
@logprob x = rand(10), y = rand(10) | model = model, chain = chain returns the log likelihood of x = rand(10), y = rand(10) for each sample in chain
@logprob x = rand(10), y = rand(10) | model = model, a = 1.0, b = 2.0 returns the log likelihood of x = rand(10), y = rand(10) using a = 1.0, b = 2.0.

Let me know if you have comments on the syntax or if I missed any use case.

I can also provide an @prob macro that returns the probability instead of log the probability.

I suggest we also allow = and == to be used interchangeably in the examples above.

I like it, I think it'd be a good tool to have. I have no helpful comments, so I guess you're welcome?

I am working on it.

@logprob a = 1.0, b = 2.0, x = rand(100), y = rand(100) | model = model -> returns log the joint probability

model is created by demo(rand(100), rand(100)) in which x and y are already provided. It's unclear to me what the log joint is supposed to return.

I agree, it feels a bit strange to me. I think it would be more natural to write
@logprob a = 1.0, b = 2.0 | model = demo

for the prior probabilities p(a = 1.0, b = 2.0) and
@logprob a = 1.0, b = 2.0, x = x, y = y | model = demo

for the joint probability p(a = 1.0, b = 2.0, x = x, y = y). I'm not even sure if it should be a macro, couldn't one just define a function logprob that allows to evaluate logprob(model, (a = 1.0, b = 2.0)) or logprob(model, (a = 1.0, b = 2.0, x = x, y = y)). Maybe for convenience one could even define model.logprob instead which allows to write model.logprob(a = 1.0, b = 2.0).

@xukai92 the log joint probability case will replace the data inside model and compute the log joint probability for the given data and parameters. If that's not intuitive enough, I can limit this macro to the likelihood and posterior only. Convenience functions can then be made to calculate the prior and joint probability for NamedTuple parameters as @devmotion suggested. In case of the joint probability, the data inside the model can be used.
Actually, for all of them I can just make a function under the hood that can be called instead of the macro. So I have a few  questions for you all:

Do you prefer a macro and a function API, a function only API or a macro only API?
Should I include the prior syntax in the macro?
Is conveniently calculating the log joint probability for new data and new parameters useful in practice or not?

I would actually prefer to have both. People who do a lot of automated model stuff would prefer a function API, whereas all the folks who are messing around with the REPL prefer the macro API. Might be that one ends up being better than the other, so we could deprecate one if it is just less useful.

Sounds good.

Re 1: I agree with Cameron that we do need both.
Re 2: I feel model = demo is more intuitive than model = model
Re 3: I think it's useful in general.

Will this allow this also allow to return the point logp of the each data point given a parameter set?

Yes

Is this available once the referenced PR is accepted?

Yup!

@logprob 0.2 <= a <= 0.3, 1.0 <= b <= 1.1 | model = model, chain = chain -> returns log the ratio of the number of samples in chain with 0.2 <= a <= 0.3, 1.0 <= b <= 1.1. For discrete distributions, we can also use a = 2 or a == 2 for example. Passing model here can be optional.

I am slightly confused by the above feature. It seems like this should be a filter-style function in the MCMCChains package. Also, what are the potential use cases?

Hypothesis testing, for one. If you wanted to have some measure of confidence about whether a parameter is negative and you wanted a quick check:
@logprob a >= 0 | model=model, chain=chain

I think it's a little nicer to work with than a Chains object, and it's very quick to write.

I am slightly confused by the above feature. It seems like this should be a filter-style function in the MCMCChains package.

Indeed IMO that feature seems more like one of the other convenient functionalities provided by MCMCChains. It is also not clear to me why specifying model = model would be useful in that example?
The nice thing about using a function instead of a macro would be that one could just dispatch on Chains (or AbstractChains) and implement the chain-based evaluations in MCMCChains. Since there seems to be an agreement that also a macro is needed, maybe one solution could be to provide a generic @logpdf macro in Turing that parses the input and forwards NamedTuples (or something else?) to the functional variant. The macro feels slightly more restricted, however, since it seems to require some protected parameter names (such as model or chain, e.g.).

I think it's a little nicer to work with than a Chains object, and it's very quick to write.

To me logprob(x -> x.a >= 0, chain) or
logprob(chain) do sample
    sample.a >= 0
end

feels doesn't feel too bad and actually more powerful and flexible than a macro.

To me logprob(x -> x.a >= 0, chain) or
logprob(chain) do sample
    sample.a >= 0
end

I like that! I think we could probably stick this on the MCMCChains side.

I agree that this doesn't belong here. I actually left it out from #997 .

You're referring only to the filtering functionality, I guess? As far as I can see, https://github.com/TuringLang/Turing.jl/pull/997 contains the chain-based feature

Query the likelihood given every sample in the chain using prob"y = rand(3) | chain = chain, model = demo"

@devmotion yes that feature is actually important, @trappmartin and @sethaxen have uses for it. Imo, I see this belongs to Turing (and in the future DynamicPPL) because the same VarNames we use in VarInfo are keys in the chain:Chain output by Turing.sample. I make use of that to feed chain[i] for example into the VarInfo before running the model in the LikelihoodContext. This may not be possible for any arbitrary chain coming from other packages, and going from chain to NamedTuple or another standard underlying representation is completely non-trivial for nested array types, e.g. when the parameter is an array of matrices. So model = demo, chain = chain makes sense for 2 reasons:

Both demo and chain are used to compute the likelihoods, and
chain was generated from demo  to begin with and the 2 are compatible, while other seemingly equivalent models may not work with chain and other seemingly equivalent chains may not work with demo.

chain was generated from demo to begin with and the 2 are compatible, while other seemingly equivalent models may not work with chain and other seemingly equivalent chains may not work with demo.

To me that sounds like the syntax should be just y = rand(3) | chain = chain (without model = demo) to avoid any incompatibilities between chain and model, and just use the model saved in chain.info which was used to generate chain.

This may not be possible for any arbitrary chain coming from other packages

Sure, but does this imply that this functionality can't be provided in, e.g., MCMCChains?

Hmm using the model in chain sounds good, I had missed the fact that we can store these in chain. The only catch is that the chain.info field optionally stores the model in Turing, but that's easily fixable. Thanks!

Sure, but does this imply that this functionality can't be provided in, e.g., MCMCChains?

Yes we need access to VarInfo which is not seen by MCMCChains, may be in a future PR we can consider moving things and interfacing.

So here is a nice middle ground, if model is defined in chain, we use that. Otherwise, we check if model was passed on the RHS. We do the same for varinfo. That way even if the user forgot to save model and VarInfo in chain, we can still save the day. Sounds good?

Hmm nevermind, that won't be necessary if chain always saves varinfo and model. Any reason not to do save them by default in my PR @cpfiffer?

Even if it is saved by default, I will leave the backup there.

No reason that I can think. You could probably just set the keyword save_state=true and everything should be good.

Cool, thanks!

Closed via #997.


Persist alternate file per window in session

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
Currently there seems to be no built-in way to persist the alternate file for a window in a session, even though all open buffers and windows are saved.
Describe the solution you'd like
When saving buffers and windows to a session, in addition to the current buffer for that window being saved, the alternate buffer/file should also be saved for that window.
Describe alternatives you've considered
I've looked online for what others have tried here, and it has amounted to either hacking their session file (which seems extremely fragile) or just using a terminal which saves terminal sessions entirely, avoiding the need for Vim sessions.
Additional context
I'd find this extremely useful, since I use the alternate file a lot, and expect it to be there pointing to a specific file for each window. Without this, it's quite tedious to have to open the file manually for all windows when I already had it in the previous session.

Wow really appreciate the really fast fix @brammool ! Love Vim a ton btw!


Missing Caching Support

Describe the solution you'd like
Missing caching support equivalent to the Python SDK or Gemini TS SDK
Describe alternatives you've considered
I can create & manage caches with raw requests to the API endpoint, but I cannot use them as the cached_content cannot be passed through the library to the request

Thanks! looking into this at the moment.

Hi @legraphista, :)
It looks like CacheContent support was added in v1.8.0. But I recommend using the latest version (v1.8.1 as of Sep 26).

Here's how you use it
Here's how you'd use Gemini's Context Caching via TypeScript, Google Cloud (Vertex AI), and @google-cloud/vertexai.
1. Evaluate pricing
First, make sure the pricing (of Gemini's Context Caching) and other benefits (e.g., lower latency) makes sense for your use case. For instance, if you're only making about 10 requests a day, it might not be worth the effort/price. There's also a minimum size for your cache (32,769 tokens as of Sep 30, 2024).
2. Create CachedContent
Create a CachedContent. It has a default life span of 1 hour, so update ttl (time-to-live) to your needs. When you create it, Google Cloud will give your CachedContent a unique name. You'll later (when you need to generate content using ) use that name to reference your CachedContent.
const LLM_NAME = `gemini-1.5-flash-002`; // Make sure your model choice is up-to-date and fits your use case

// Example googleCloudRegion value: "us-central1". More info: https://cloud.google.com/vertex-ai/generative-ai/docs/learn/locations
export async function createCachedContent(
  googleCloudProjectId: string, googleCloudRegion: string, initialPrompt: string,
): Promise<CachedContent | undefined> {
  const vertexAI = new VertexAI({ project: googleCloudProjectId, location: googleCloudRegion });
  // cachedContent.name is automatically generated at server side and cannot be specified by users
  const cachedContent: CachedContent = {
    displayName: 'My cached content',
    model: `projects/${googleCloudProjectId}/locations/${googleCloudRegion}/publishers/google/models/${LLM_NAME}`,
    systemInstruction: '',
    contents: [{ role: 'user', parts: [{ text: initialPrompt }] }],
    ttl: `${3600 * 3}s`,
  };
  const createdCachedContent = await vertexAI.preview.cachedContents.create(cachedContent);
  // createdCachedContent.name will look like projects/123456781249/locations/us-central1/cachedContents/12345678471874431234
  if (!createdCachedContent || !createdCachedContent.name) {
    console.error('Failed to create CachedContent.');
    return;
  }
  console.log({ createdCachedContent });
  return createdCachedContent;
}

3. Get CachedContent name
The name is the unique identifier of your CachedContent. The previous createCachedContent() function returns a CachedContent object containing the name. But if you weren't able to grab the name, you can list your CachedContent objects in your Google Cloud project:
export async function listCachedContent(
  googleCloudProjectId: string, googleCloudRegion: string,
): Promise<CachedContent[] | undefined> {
  const vertexAI = new VertexAI({ project: googleCloudProjectId, location: googleCloudRegion });
  const cachedContentsResponse = await vertexAI.preview.cachedContents.list();
  return cachedContentsResponse.cachedContents;
}

4. Reference the CachedContent when generating content
Generating content works the same as it would without context caching, except you now (to use your CachedContent) need to specify the name of your cachedContent in your request (GenerateContentRequest) object.
const LLM_NAME = `gemini-1.5-flash-002`; // Make sure your model choice is up-to-date and fits your use case

export async function generateContentUsingCachedContent(
  googleCloudProjectId: string, cachedContentName: string, prompt: string,
): Promise<void> {
  const vertexAI = new VertexAI({ project: googleCloudProjectId, location: `us-central1` });
  const request: GenerateContentRequest = {
    cachedContent: cachedContentName,
    contents: [{ role: 'user', parts: [{ text: prompt }] }],
    generationConfig,
    safetySettings,
  };
  console.log(`\n🤖 Sending message to Gemini:\n${prompt}`);

  const generativeModel = vertexAI.preview.getGenerativeModel({ model: LLM_NAME });
  const result = await generativeModel.generateContent(request);

  if (result && result.response && result.response.candidates && result.response.candidates[0]) {
    const resultCandidate = result.response.candidates[0];
    if (resultCandidate.content.parts[0].text) {
      console.log(`\n🤖 Gemini's response:\n${resultCandidate.content.parts[0].text}`);
      return;
    }
  } else {
    console.error("Unexpected response format:", result);
  }
}

Resources
Always refer to the official docs at cloud.google.com for Google Cloud related guidance:

Context caching overview
Create a context cache
Use a context cache
etc.

You might find more up-to-date, official Google Cloud samples in:

https://github.com/GoogleCloudPlatform/nodejs-docs-samples
https://github.com/GoogleCloudPlatform/generative-ai

Hey @NimJay , can you provide some guidance on how one could later append to the cached content? My use case is Q&A over an increasing set of audio recordings. Ideally I could incrementally append to the content cache with new audio snippets as the recording gets larger.

Hi @timconnorz,
Sorry, that's not a supported feature at the moment (source):

You can set a new ttl or expire_time for a cache. Changing anything else about the cache isn't supported.

(I'll reach out to the relevant teams internally.)


Development: Add future programming languages to ProgrammingLanguage enum

Motivation and Context

Currently, Test Server 2 is not able to load exercises. This is caused by some programming exercises in the database which use a language not defined in the ProgrammingLanguage enum.
These exercises entered the database during testing of #8802 and #8859 which have not been merged yet.
Until the change of the enum is merged into the develop branch all other branches will not be able to use TS2.
Description

This PR only adds the programming languages to be added in future to the ProgrammingLanguage enum.
This should prevent the current situation when more languages are added.
The current Spotless rules force these declaration to be on a few lines.
Review Progress

Code Review

[ ] Code Review 1
[ ] Code Review 2

Summary by CodeRabbit

New Features

Added support for new programming languages in various services, including JavaScript, C#, C++, SQL, R, TypeScript, Rust, Go, MATLAB, Bash, Ruby, PowerShell, Ada, Dart, PHP, C, VHDL, Assembler, OCAML.

Bug Fixes

Improved error handling for unsupported programming languages across different services.

Refactor

Simplified exception handling for unsupported languages in JenkinsBuildPlanService and TemplateUpgradePolicyService.

Is this realy necessary? This solve the TS2 problem but is not really a change we need to promote to production. Could an admin not just delete the exercises from the database, and future testers should be reminded to delete their exercises after testing.

We tried reminders but they weren't working. An admin could delete these exercises as a short term fix, but this would happen constantly.
We discussed this in our last developer meeting on Monday. This change was proposed by @krusche.

There is a startup-time check which is run on all enum members. We could fill the configuration with bogus values or remove this check altogether. I think that both cases would work against what this check had in mind.
The missing values shouldn't be an issue if no exercise can be created with them. But we might risk runtime crashes if a random null pops up.
Any opinions on how we should handle this?
    /**
     * Makes sure that for each programming language at least a default image is defined.
     * <p>
     * Aborts server startup by throwing an exception if some definitions are missing.
     *
     * @param buildImages The build images as defined in the configuration.
     */
    private void checkImageForAllProgrammingLanguagesDefined(final Map<ProgrammingLanguage, Map<ProjectType, String>> buildImages) {
        for (ProgrammingLanguage language : ProgrammingLanguage.values()) {
            if (!buildImages.containsKey(language)) {
                throw new IllegalArgumentException("For each programming language a CI build image must be defined. Missing: " + language);
            }

            final Map<ProjectType, String> languageImages = buildImages.get(language);
            if (!languageImages.containsKey(DEFAULT_PROJECT_TYPE)) {
                throw new IllegalArgumentException("For each programming language a default image must be defined. Missing: " + language);
            }
        }
    }

There seems more to it than expected. There are more places which iterate over all programming languages. There are also some tests which are parametrized on all languages via @EnumSource.
The best I could come up with was to define a set of enabled languages and replace all usages of ProgrammingLanguages.values() and the @EnumSources with this set.


make book-view collections and subcollections as markdown titles

By adding # character for each nested level and between the last # and the text. Example (see source since github is markdown compatible and styles it):
Collection
Subcollection lvl 1
Subcollection lvl 2
Subcollection lvl 3
...

Fixed


⚠ Turnos 24x7 has degraded performance

In eaccda9, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 3027 ms

Resolved: Turnos 24x7 performance has improved in f8fdbd6.


"(intermediate value)().with_tcp is not a function"

I'm getting the above error when trying to use the module as described in the README. with_websock() works without an issue, but sadly using it is not an option for me.
Code looks as follows:
import mqtt_client from 'u8-mqtt'

async function mqttConnect() {
    try {
      let client = mqtt_client().with_tcp(getServerString() + ':1883').with_autoreconnect(); //tcp://localhost:1883

      await client.connect();
      client.subscribe_topic(MQTT_TOPIC, mqttOnMessage);
    } catch (err) {
      console.log(err.message);
    }
  }

mqttConnect() gets triggered via a button press.
Package version is 0.5.3.
I apologize if I'm missing anything obvious, but I'm not really seeing it.

Try changing your import to:
import mqtt_client from 'u8-mqtt/esm/web/index.js'

I've tried accommodating different packagers, but they all seem to have different opinions. Fortunately, most of them support explicit pathing, too.

I'm afraid the issue persists. I also had a look at the file in question, and there's indeed no with_tcp() function in it. Nor in any of the other index.js files under /esm/. Instead there's about 50 empty lines, as if something that should be there is missing. All I have is with_stream() and with_websock().

I was thrown off by the mention of a button. The web version does not have direct TCP access, as the platform does not support that to my knowledge.
Did you use the NodeJS or Deno versions? Are you on a different platform? I ask because the TCP functionality depends on platform APIs.

Ah sorry, I am using NodeJS. And it appears the issue is with my local installation, because I've built a test project from scratch and that one worked fine. I'll do a bit more troubleshooting on my end, but it doesn't seem to be an issue with the module.


I'm studying your flake.nix file and am trying to replicate the way that you have separated your darwin configuration from your home-manager configuration.
I was wondering how you have home-manager in your path after installation? I can't seem to find anyone else with the problem, so I'm wondering if I've setup my flake wrong. I have a simliar mkDarwinConfiguration function in my flake but I'm adding my home-manager as a module in there.
Do you mind giving me some insight?
Edit: I should also note that I'm working on darwin right now.

 Let me try to explain how my setup differs from common configurations.
There are two main approaches to using home-manager with NixOS/nix-darwin:

The common approach: Including home-manager as a module within your NixOS/nix-darwin configuration
My approach: Keeping home-manager configuration completely separate

I chose the second approach because it gives me the flexibility to rebuild home-manager and system configurations independently. In my setup:

System configuration (NixOS/nix-darwin) manages system-level settings
Home-manager manages user-specific configurations

To see how this works, look at my home configuration files (example: https://github.com/AlexNabokikh/nix-config/blob/master/home/nabokikh/nabokikh-mac.nix#L8) where home-manager is enabled specifically for Mac machine.
The reason you don't have home-manager in your PATH is that it needs to be bootstrapped first. Here's how to set it up on a new machine:

First, get the required tools:

nix-shell -p git home-manager

Clone the configuration:

git clone https://github.com/AlexNabokikh/nix-config

Apply both configurations:

sudo nixos-rebuild switch --flake .#<computer_name> && home-manager switch --flake .#<user_name>@<computer_name>

After this initial setup, you can rebuild configurations separately and home-manager will be available without additional steps:

For system: sudo nixos-rebuild switch --flake .
For home-manager: home-manager switch --flake .

I hope it makes more sense now, but let me know if you need any clarification on specific parts of the setup.

Hey dude! Thanks for the great write up. I followed your instructions and it worked great! I also now understand that home-manager is its own thing which helps me understand how they can exist separately. I didn't realize that you can just add home-manager from nix-shell, which is pretty neat!
I hope you don't mind, but I've been using your config to learn some of the more interesting parts of the nix language, so thats been super helpful. Thanks a ton!


chore: adding plugin-fetch and example

Which problem is this PR solving?

Fixes #1041

Short description of the changes

Adds auto instrumentation for fetch in browser

@open-telemetry/javascript-approvers @open-telemetry/javascript-maintainers
^^

Added a few minor comments in the first pass.


feat: Updating base Terraform module

Description
Updates the base Terraform module for AUSF to the latest agreed form, in particular:

removes integrations from main.tf
models Juju integrations using output.tf
updates README to show how to use base module (README with information about how to deploy will come along with a higher level module)
moves module files under terraform/modules/terraform-juju-sdcore-ausf-k8s to accommodate module with dependencies in the future

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library

I think we need to get the team opinions' regarding with TF module directory movement to terraform/modules/terraform-juju-sdcore-ausf-k8s. Other than that LGTM.

I think we need to get the team opinions' regarding with TF module directory movement to terraform/modules/terraform-juju-sdcore-ausf-k8s. Other than that LGTM.

Yeah, I figured we'll need to move it anyway when we start working on the module with all the dependencies. We'll need to store it somewhere. I thought we could have it directly under terraform folder.


Manually rendering Razor precompiled views

My ASP.NET Core 2.0 site uses some .cshtml files as e-mail templates. I have a custom service that uses the IRazorViewEngine service to render views to a string. This works completely fine in Dev where the View files are sourced from the .cshtml files at runtime. However, in Production, the view engine can't find the template views and throws an error when the site tries to render an e-mail.
I am unsure if this is because the precompilation detects that the views are not used by any controllers and excludes them, or if IRazorViewEngine.FindView cannot load views that have been precompiled.
I can't include the .cshtml files in Production because the hosting server runs CentOS, and apparently runtime view compilation is not supported on Linux (it throws an error about not finding the Microsoft.Win32.Registry module).
Is there a way around this issue, or perhaps a better way of manually rendering a view? I considered just having a controller action that renders each template and having the e-mail service call the action, but I don't want users to have access to rendering the templates unless it's via an actual e-mail sent to them.

@briman0094 your issue might be a dup of https://github.com/aspnet/Mvc/issues/6672. The most likely solution in your case is to use IViewEngine.GetView which is meant for path-based lookups and pass in path rather than a name.
e.g.
IViewEngine.FindView("Foo/Bar") -> IViewEngine.GetView("/Views/Foo/Bar.cshtml")

Yes this does sound like a dup of https://github.com/aspnet/Mvc/issues/6672.


bugfix: fix prometheus fail to return seata metrics data when using Nacos

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
fix prometheus fail to return seata metrics data when using Nacos
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

LGTM.I have tested by some examples.


Get timetable from ecnu.edu.cn

https://github.com/flutterchina/dio/blob/master/README-ZH.md

https://pub.flutter-io.cn/packages/http

https://github.com/jonataslaw/getx/blob/master/README.md#getconnect

https://pub.dev/packages/flutter_spinkit

https://api.flutter.dev/flutter/material/CircularProgressIndicator-class.html

https://pub.dev/packages/sentry#:~:text=Tracking HTTP Requests

https://cloud.baidu.com/product/ocr_general

https://api.flutter.dev/flutter/material/Stepper-class.html


Fix TargetRubyVersion in FrozenStringLiteral description

I was about to fix this myself, but I forgot about it. :-)


Fact check bounty

Pitch
Ideally, when consuming news, we should fact check claims. However this is time-consuming. So often, you don't. Either, you assume they did their job, or you let someone else do it.
If you're letting someone else do it, is it possible to attach a bounty for fact checking? To verify the references in the news piece really supports its claims. Verify that the chain of references to the source? Produce other supporting or disputing claims of evidence, maybe even to a primary source?
Imagine a network where the participants are distributed among any bias, and the evaluation of evidence is the job of a randomly selected subset of these participants. Those offering evidence deemed valid, will receive a part of the bounty. The bounty could also be upped by others interested in verifying the same.
Maybe this could be read for inspiration
https://www.theatlantic.com/politics/archive/2016/12/what-journalists-can-learn-from-david-fahrentholds-trump-coverage/511277/
Team
This is currently just an idea. ETHBerlin could be an appropriate venue to try to make something tangible out of it.
I'm a self-taught binary enthusiast, lately working on development for Ethereum Swarm, specifically authoring the implementations of PSS (messaging layer) and the first iteration of Mutable Resource Updates.
Skills wanted

Solidity
Javascript
Someone who knows about the economics of such things

Communication
Since I don't use a smart phone (it's the most evil device in history, didn't you know?) I can be contacted on https://gitter.im/nolash or grab hold of me at the event; I'm either in a digit covered red shirt with white collar or an orange swarm hoodie.

I remember talking to people from Gnosis on EdCon about this - if I'm not mistaken they have a project in the works related to fact checking using prediction markets, and some partnerships ongoing as well.


failing in running kameris with mac

kameris classify hiv1-mlp hiv1-genomes
INFO     retrieving 'https://raw.githubusercontent.com/stephensolis/kameris-experiments/master/files.yml'
/Users/Lab/anaconda/lib/python2.7/site-packages/urllib3/util/ssl_.py:354: SNIMissingWarning: An HTTPS request has been made, but the SNI (Server Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  SNIMissingWarning
INFO     file 'https://raw.githubusercontent.com/stephensolis/kameris-experiments/master/models/hiv1-mlp-py2.mm-model' already downloaded, using cached version
INFO     started loading model
INFO     finished loading model in 0.01 seconds
INFO     started computing input CGRs
INFO     running command ""/Users/Lab/anaconda/lib/python2.7/site-packages/kameris/scripts/generation_cgr_mac_avx2" cgr "hiv1-genomes" "/var/folders/5p/mvgcw45d5rs13x2hr3k59nlw0000gn/T/tmpFkwgSm/cgrs.mm-repr" 6 16"
INFO     5 files, using 8 threads
INFO     20% [======>                            ] 1/5 ETA:0s
INFO     started frequency-normalizing CGRs
ERROR    an unexpected error occurred: TypeError: Struct() argument 1 must be string, not unicode
ERROR    ***if you believe this is a bug, please report it at https://github.com/stephensolis/kameris/issues and include ALL the following text:***
Traceback (most recent call last):
  File "/Users/Lab/anaconda/lib/python2.7/site-packages/kameris/__main__.py", line 41, in main
    run_module.run(args)
  File "/Users/Lab/anaconda/lib/python2.7/site-packages/kameris/subcommands/classify.py", line 48, in run
    backend.run_backend_kmers(options, {})
  File "/Users/Lab/anaconda/lib/python2.7/site-packages/kameris/job_steps/backend.py", line 45, in run_backend_kmers
    reader = kameris_formats.repr_reader(options['output_file'])
  File "/Users/Lab/anaconda/lib/python2.7/site-packages/kameris_formats/repr_reader.py", line 27, in __init__
    self.count, = struct.unpack('<Q', self.file.read(8))
TypeError: Struct() argument 1 must be string, not unicode
```

Should be fixed with https://github.com/stephensolis/kameris-formats/commit/24a120d0ba7ee3f146c72988f7c08ff94ccc4f06
Run pip install --upgrade kameris-formats and it should work.


Refactor to move github/data to vcs/data

This is mostly changes to prevent the PR with the actual logic to be obfuscated. I move the data structures from github/data to vcs/data. I also rename the GitHubRepoAlg to VCSRepoAlg.
With this PR, we are assuming the data structures (used to talk to GitHub) will work for any VCS be it BitBucket and GitLab. In reality, it's a bit of a stretch. I've made it work with a bunch of shortcut (as a prototype it ran on one of our internal repository and it opened a bunch of PR 👍 ). But we'll need to discuss what needs to change in those structures in order to accommodate other VCS when I open the PR with the actual logic.
The actual changes would look like:

a new package called org.scalasteward.core.gitlab (with a different Url class
custom encoder/decoders to go from Gitlab's JSON to the vcs data structures (if they're left as-is)
a VCSApiAlg that covers Github and Gitlab
a VCS Selector (if you will) to read the config and build the appropriate implementation of VCSApiAlg

Referencing #313

Ok, let's do this! I agree that reusing the same data structures for different repository mangers might be problematic. Especially the Out classes currently mirror GitHub's API and if we want to support different features for different repository mangers in the future we probably also need different Out classes.
Btw, thanks @daddykotex for splitting your changes into this "rename" PR and a later "logic" PR. This makes it easier for me to review them.

Wow amazing. Thanks to you for scala-steward.
If you want to make sure you are not breaking anything, we can work on a feature branch. I'll open the follow-up MR and explains the difference so we can all be on the same page about the differences between GitHub integration and Gitlab integration.

:+1: Sounds good to me. I've created the branch topic/gitlab for that.


gccgo: gcc testsuite failures due to regression in ppc64le

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.7.1 gccgo (GCC) 7.0.0 20161128 (experimental) linux/ppc64le
What operating system and processor architecture are you using (go env)?
Ubuntu 16.04 ppc64le
What did you do?
Looking at the test failures in gcc-testresults for gccgo from 7.0.0
What did you expect to see?
No failures (except the expected cplx.go)
What did you see instead?
Failures
In looking at the gcc-testresults output for ppc64le I found that the failures for stack.go and recover.go started happening in commit 241222, and passed in 241215.  The commit for 241222 looks suspicious since it affects functions and trampolines.  This change doesn't look to be specific to Go but caused regressions in gccgo.
gcc-testresults log shows this when it fails (cplx.go is a known error):
=== go tests ===

Running target unix
FAIL: go.test/test/ken/cplx2.go execution,  -O2 -g
FAIL: go.test/test/recover.go execution,  -O2 -g
FAIL: go.test/test/stack.go execution,  -O2 -g
Running the new test failures individually show this output:
./recover.x
panic: 13
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0xa]
goroutine 16 [running]:
__go_panic
/home/boger/gccgo.work/trunk/bld/../src/libgo/runtime/go-panic.c:110__go_panic
/home/boger/gccgo.work/trunk/bld/../src/libgo/runtime/go-panic.c:66main.test13reflect2
/home/boger/gccgo.work/trunk/src/gcc/testsuite/go.test/test/recover.go:456main.main
/home/boger/gccgo.work/trunk/src/gcc/testsuite/go.test/test/recover.go:58
goroutine 18 [finalizer wait]:
./stack.x
bad func 21 at level 8000
panic: fail
goroutine 16 []:
__go_panic
/home/boger/gccgo.work/trunk/bld/../src/libgo/runtime/go-panic.c:110main.recur
/home/boger/gccgo.work/trunk/src/gcc/testsuite/go.test/test/stack.go:87main.main
/home/boger/gccgo.work/trunk/src/gcc/testsuite/go.test/test/stack.go:99

/cc @ianlancetaylor

Mentioned externally at https://gcc.gnu.org/ml/gcc-patches/2016-12/msg00388.html.

libgo testcase crypto/tls also started failing with this commit.

The go testcases stack.go, recover.go and libgo testcase crypto/tls now pass according to the latest gcc-testresults for gccgo 7.0.0 on ppc64le.


Can you put a mod in a Multiverse core world?

Can you put a mod in a Multiverse core world?

Information

Server version:

Full output of /mv version -p:

Server log:

Help request
Problem

What I have tried

Screenshots

mv doesnt control that. Naturally, mv is a bukkit plugin that only installs on bukkit based servers like spigot and paper. So you only can install other plugins that support this platform.

Is it possible?

Nope, and out of scope of mv as well.

Oh
On Mon, Feb 22, 2021 at 10:28 PM Ben Woo<EMAIL_ADDRESS>wrote:

Nope, and out of scope of mv as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Multiverse/Multiverse-Core/issues/2571#issuecomment-783850560,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APLOUCKXY6KUZ4NPKG3IVRDTAMOFBANCNFSM4YA6Z7BA
.


USelect with placeholder display options with missleading color

Environment

Operating System: Windows_NT
Node Version:     v20.10.0
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Version
2.8
Reproduction
visible even on the docs page
Description
When there is no value set for select, the placeholder is displayed (if set).
In such case, when options are displayed their labels are "muted" - looks like disabled ones.

Once any option is picked, their color change to "proper" one.

Additional context
No response
Logs
No response

Yes, I can select it, and no, it's not like this on default selects, that's why I've spotted it.
It's caused by class text-gray-400 that is applied to "placeholder version", and is later changed to text-gray-900
So, it's styled by Nuxt UI.

@KonradDRAST can u open a reproduction?

@KonradDRAST can u open a reproduction?

As mentioned in my issue - this happens even on official docs page: https://ui.nuxt.com/components/select#placeholder

I am having the same issue, if I add a placeholder the enabled options become light gray and the disabled options are darker, once I select an option it sometimes fixes the colors. so to reproduce try to add a few disabled and enabled options.


Localization with custom key-value format

This is a follow-up PR/replacement for #3094 and aims to improve the handling of localization in Typst.
It relies on https://github.com/typst/typst-assets/pull/2 to be merged.
The main benefit of this PR is the separation between translation strings and code.
Previously, the localized strings of one language were spread across 7 files.
As discussed in #3094, this PR implements a simple, custom key-value format for translations.
This is less complex than using Fluent or other localization systems, which are overkill for our current needs.
If this changes, switching to Fluent is now easier than without this PR.
The format is the following, whitespace around key and value are ignored:
# this is a comment, only valid on its own line
key = value

Sorry I didn't reply until now, I was on vacation. I will try and implement your suggestions the coming days.

I agree with all your suggestion and this should now be ready.
The only thing I am a bit unsure about is the 31 calls of the translation macro.
The include_dir would probably shorten it, but I don't know if that's worth it.

I think it would be great if these values could be exposed to the user too. You can see how, in subpar#2 for example, it would be beneficial to have the user be able to read the values to replicate the builtin behavior faithfully.

It looks like Catalan translations (and possibly more?) got lost in this change.

You are right, sorry for that!
If my following thought process is correct, there shouldn't be any more missing languages:
There are 32 "Lang" constants in lang.rs. There are 2 regions, pt and tw (unfortunately, I don't know a central place to find all regions, other than the translation files).
That adds up to 34 translation files in total.
But since Croatian and Lower Sorbian don't have a translation file (and never had one, at least not when this PR was created), we are back to 32.
#4414 should already solve the issue, so I will not do a follow-up PR.

Alright, thanks for checking for other missing things!


Add compatibility for sort without ext labels

In https://github.com/thanos-io/thanos/pull/6299 we changed the comparison algorithm in the store proxy to ignore store-specific external labels. This causes problems during long rollouts because old stores and new stores will sort data differently, leading to incorrectly deduplicated results.
This commit adds a new flag to the store info message to indicate whether the store sorts data with or without external labels. The querier uses this flag to decide whether to resort the store response set before starting a merge.

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes

Resort response set data if stores do not support sorting without external labels.

Verification

This was tested in a staging environment by running a querier from the branch against stores with an old version.
Added a unit test for the sorting functionality.

We will try to solve this problem differently. It seems hard to fix it with compatibility flags.


test PR with Github API

Please pull this in!

Docs Build status updates of commit 954f97c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

sdp-test/index.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 15a9f02:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

sdp-test/index.md
:white_check_mark:Succeeded

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


Commits show up as "unverified" when using git spr update after amending commits.

compare:

with:

Would love any guidance on how to debug/assist/fix?

Closing stale issue


Update macOS MySQL version

The latest homebrew formula pulls 8.0.21 and it breaks our CI. This just updates the number to unblock other PRs but it'd be great if we could stop hard-coding it as a follow-up work.

As I'm not a MacOS user I'm not sure how to write the script otherwise, but if there is a possibility to change that I'm in favor of such a change.

but if there is a possibility to change that I'm in favor of such a change.

The problem here is formula has the latest v8.x MySQL only. I'll try to find a (hacky) workaround if I get some time.


Support multi-locale templates

The template specification must be extended to support locale-specific template grammar text.
At present, a template can have multiple sample.txt instances (one per locale) but the grammar generation doe not take a locale as input.

To fix #63 we need to be able to specify the locale for a template, with the default date/time format for the template based on the locale for the template.
This requires refactoring how we manage the template grammars within a template.
/grammar/template.tem <-- default template. This is for the en-US locale
/sample.txt <-- sample.txt for the en-US locale
/README.md <-- readme file for the en-US locale
/grammar/en-GB/template.tem <-- a locale specific template
/grammar/en-GB/sample.txt <-- sample.txt for the en-GB locale
/grammar/en-GB/README.md <-- readme file for the en-GB locale
Locales are specified using IETF BCP 47 language tags.
A template may contain any number of locale specific sub-folders.
Note that the name of the template and the description of the template specified in package.json are not localisable.

This should be updated to reflect the new template directory structure from #435


Is UMI compatible with React? Why do I always encounter errors when using React and UMI together?

If I want to use UMI in the frontend, which frontend framework is recommended?

experiencing almost the same problem when use nuxt as frontend, using umi always makes my nuxt stop working error
Cannot read properties of undefined (reading 'prototype')
at http://localhost:3000/_nuxt/node_modules/.cache/vite/client/deps/@metaplex-foundation_umi-bundle-defaults.js?v=eaf4a82e:2834:78

experiencing all sorts of issues with vite and react swc


Snap release updates

The issue
The current release on snap does not match the actual version.
Reproduce

install via "sudo snap install natls"
check version of nat with "natls --version"

Things I tried

update nat with "sudo snap refresh natls"

Idea for a fix
Snap should be integrated into a CI like GitHub Actions, Jenkins or similar to automatically update the binary. Or on each release someone should update the binary manually.

The snap is maintained by @tbille in https://github.com/tbille/natls-snap
Most likely Snap Store builds it automatically. It is possible to build directly from this repo instead, but then the snapcraft.yml should be committed here and @willdoescode need to register at the store and it add webhook to the repo.

I am working out getting natls updated on snap

Hey @willdoescode I am happy to make a pull request on your repo and handover the snap.

That would be great thank you

snapcraft should be on the latest version now! Now that I own the snap project I will push new builds before I add the build to github.

Awesome.
@tbille thanks for providing it in the first place.

yes thank you @tbille


Remove HIV messaging collection screen

As a result of the UET, we want to remove the HIV message screen.

@KaitCrawford Ready for review. Currently based off of feature/MOMUG-100-combine-hoh-name-screens to make reviewing easier, but I'll change the base once the previous pull request gets landed.

@rudigiesler :+1:


How to run end-to-end tests against local devenv?

I'm at NYU Libraries and we're implementing Primo NUI customizations, influenced greatly by your wonderful work on this repo. We've attempted end-to-end testing in a variety of frameworks but have been unsuccessful so far. I was able to run your e2e tests against your production primo, but I can't seem to run them against a local devenv, which it appears you all have done (due to the localhost in the config). When I attempt to run it against a local devenv, it doesn't load the page at all – it remains stuck on the loading symbol. That's true whether I use your customization views, ours, or none at all on my local devenv.
How were you able to run the Protractor e2e tests against a local devenv? Did you have to configure the devenv or tests in any special way? Any advice on this and automated testing of Primo NUI in general would be greatly appreciated.

Sorry for getting back so late. I am no longer working at Royal Danish Library, but I know that we ran them against our local environment too. If you still have the issue, could you check out the browser console and describe what you see? Otherwise, it would be great to know how you handled the issue.

Thanks for the reply @muratseyhan – The browser console isn't showing any errors when we run via Protractor, but Protractor is giving the error "Angular could not be found on the page … : angular never provided resumeBootstrap." I've read that this may be caused by BrowserSync, but I can't find a way to disable BrowserSync in the devenv and I've opened up an issue with them in that regard.
Is this an issue you encountered? Were you running the primo UI locally using the devenv or in some custom way?

Just to make sure, you are running the app locally while trying this, right?
We were using the devenv. IIRC, the only configuration we had on the devenv was the PROXY_SERVER in gulp/config.js. I will try to reproduce this when I will have the chance.

@muratseyhan Yes I was running the app locally (via the devenv). I also tried pointing to another proxy server over http and I got the same result. I can't point to a proxy server over https, however, because the devenv is running locally in http. Did you setup the devenv to run over https locally perhaps?

Hi @ericgriffis!
I finally had the chance to try this out. I was able to run the tests on a local server on Ubuntu 17.10. Some of the tests failed, but that's probably expected. They ran on protractor 5.3.0. I had to degrade to node v6.9.2 and install JDK to get protractor run.
Also, it seemed to work the same both with HTTP and HTTPS proxy URLs.
$ npm -v
3.10.9

$ node -v
v6.9.2

$ java -version
java version "1.8.0_162"
Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)

I did a quick search on the error you receive, and it seemed to me like the error you received might be specific to some versions of protractor. Could you give it another try with the versions I used?


Unable to extract tables from following the pdf

I have gone through the code and found that currently it doesn't support to extract text from table which are like hybrid between bordered tables and borderless tables PFA
Can please check this and let me know if you are able to extract tables from below pdf

ip-test.pdf

Hello,
In your file, the 6.2 and 6.4 tables are extracted properly.
For the 6.3 table, as it spans over 3 pages, the "bordered table" algorithm is not able to detect it.
When it comes to the "borderless table" algorithm, it requires by design a table with at least 3 columns in order to avoid detecting a lot of BS, that is why it also won't work.


Refactor TaskUpdate.debugPrintScala(SafetyLogger,SafetyConfiguration,Boolean,$Tuple,Seq)

I've selected TaskUpdate.debugPrintScala(SafetyLogger,SafetyConfiguration,Boolean,$Tuple,Seq) for refactoring, which is a unit of 32 lines of code. Addressing this will make our codebase more maintainable and improve Better Code Hub's Write Short Units of Code guideline rating! 👍
Here's the gist of this guideline:

Definition 📖
Limit the length of code units to 15 lines of code.
Why❓
Small units are easier to analyse, test and reuse.
How 🔧
When writing new units, don't let them grow above 15 lines of code. When a unit grows beyond this, split it in smaller units of no longer than 15 lines.

You can find more info about this guideline in Building Maintainable Software. 📖

ℹ To know how many other refactoring candidates need addressing to get a guideline compliant, select some by clicking on the 🔲  next to them. The risk profile below the candidates signals (✅) when it's enough! 🏁

Good luck and happy coding! :shipit: :sparkles: :100:

done


Updated Demo | Added requirements | Updated READMEs

Changes Made

Added a standard requirements.txt.

Added the requirements.txt for the ease of users. As they can install all the libraries required using a single command.
Added it using pip freeze. So, there should no doubt about any errors.
Also, I tested it in the venv.

Updated README.md

Updated the README file with new pip install -r requirements.txt command in place of installing all the libraries one by one.

Removed some errors from the Documents i.e Numbering spaces

Any response Maintainers??

Hello @SoniNow @ankiitsinghh07 @ashish8947 Please review this, it's been 21 days since I am waiting.

Why did yu mark it as ineligible

Its wrong. I was the first one to add all the Requirements.

I am seriously regretting to contribute to this Repo. And if you are thinking I am submitting due to Hacktober, than for your kind information I have already completed it. You merged the same changes made by a person 4 days ago. And just check when I created this repo.

Also I just saw the PR with merged changes, it consists only 5 packages, in requirements.txt.

Please improve your service guys.

@pranayjoshi
Thanks for contributing to the repo. We can surely improve as per your suggestions. But as per the HacktoberFest guideline, we will not be accepting minor text fixes & the same content PR again. Please suggest and improve some quantifiable changes in the pull request to make your PR eligible for HacktoberFest.


Race condition: couldn't copy path (the source path is not an existing file; [possible duplicate #751]

I tried compiling the Piston image example and I got an ICE on one of the dependencies. More specifically, it failed building gl_generator. I could not reproduce this again and searching for the error text yielded #751.
Here is a copy of the log for reference:
> ~/C/R/f/p/image ❯❯❯ cargo build
    Updating git repository `https://github.com/pistondevelopers/event`
    Updating git repository `https://github.com/pistondevelopers/sdl2_window`
    Updating git repository `https://github.com/pistondevelopers/opengl_graphics`
    Updating git repository `https://github.com/PistonDevelopers/event_loop`
    Updating git repository `https://github.com/PistonDevelopers/current`
    Updating git repository `https://github.com/PistonDevelopers/window`
    Updating git repository `https://github.com/PistonDevelopers/input`
    Updating git repository `https://github.com/rust-lang/time`
    Updating git repository `https://github.com/alexcrichton/gcc-rs`
    Updating git repository `https://github.com/pistondevelopers/shader_version`
    Updating git repository `https://github.com/AngryLawyer/rust-sdl2`
    Updating git repository `https://github.com/bjz/gl-rs`
    Updating git repository `https://github.com/netvl/rust-xml`
    Updating git repository `https://github.com/pistondevelopers/texture`
    Updating git repository `https://github.com/pistondevelopers/graphics`
    Updating git repository `https://github.com/pistondevelopers/image`
    Updating git repository `https://github.com/PistonDevelopers/freetype-rs.git`
    Updating git repository `https://github.com/PistonDevelopers/read_color`
    Updating git repository `https://github.com/PistonDevelopers/vecmath`
   Compiling current v0.0.0 (https://github.com/PistonDevelopers/current#ad63ba6a)
   Compiling gl_common v0.0.1 (https://github.com/bjz/gl-rs#d212190f)
   Compiling khronos_api v0.0.2 (https://github.com/bjz/gl-rs#d212190f)
   Compiling rust-xml v0.1.2-pre (https://github.com/netvl/rust-xml#2d9df326)
   Compiling read_color v0.0.1 (https://github.com/PistonDevelopers/read_color#c563f9f0)
   Compiling sdl2 v0.0.7 (https://github.com/AngryLawyer/rust-sdl2#81daa9f8)
   Compiling input v0.0.0 (https://github.com/PistonDevelopers/input#fb351501)
   Compiling texture v0.0.0 (https://github.com/pistondevelopers/texture#65e7bbd5)
   Compiling freetype-rs v0.0.0 (https://github.com/PistonDevelopers/freetype-rs.git#994de62b)
   Compiling shader_version v0.0.0 (https://github.com/pistondevelopers/shader_version#32364088)
   Compiling image v0.2.0-alpha.2 (https://github.com/pistondevelopers/image#cd87733f)
   Compiling gcc v0.1.0 (https://github.com/alexcrichton/gcc-rs#6b60df5c)
   Compiling vecmath v0.0.0 (https://github.com/PistonDevelopers/vecmath#e0efa852)
   Compiling graphics v0.0.0 (https://github.com/pistondevelopers/graphics#8a0f9b0c)
   Compiling time v0.1.0 (https://github.com/rust-lang/time#b8e219aa)
   Compiling event_loop v0.0.0 (https://github.com/PistonDevelopers/event_loop#b2a47dd1)
   Compiling window v0.0.0 (https://github.com/PistonDevelopers/window#888aeccd)
   Compiling gl_generator v0.0.1 (https://github.com/bjz/gl-rs#d212190f)
   Compiling event v0.0.0 (https://github.com/pistondevelopers/event#04fa0d83)
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: http://doc.rust-lang.org/complement-bugreport.html
note: run with `RUST_BACKTRACE=1` for a backtrace
task 'rustc' panicked at 'called `Result::unwrap()` on an `Err` value: couldn't copy path (the source path is not an existing file; from=/Users/salad/Code/Rust/forks/piston-examples/image/target/deps/gl_generator-14b70861eb330221.0.o; to=/Users/salad/Code/Rust/forks/piston-examples/image/target/deps/gl_generator-14b70861eb330221.o)', /Users/rustbuild/src/rust-buildbot/slave/nightly-mac/build/src/libcore/result.rs:743
>
>
> Could not compile `gl_generator`.

I think that this has since been fixed (I remember landing a fix or two related to this). Feel free to reopen if it still reproduces though!


Some fixes

use hasOwnProperty() to avoid problems with module ID 0 (zero)
include hashSize in the chunk hash to avoid problems when changing the hash size (like the recent change from default 28 bits to 53 bits)

Also added a README section explaining how to use hashDigestLength to get better chunk hash strings.

which kind of problems happens with module #0?

@x2es now that you ask, there probably isn't really a problem with module #0.
Still, it's usually better to use hasOwnProperty() to check if an object has a specific property/key.
Not a big deal, but always better to be on the safe side.. ;-)

The really important part of this PR is the one regarding chunkHash, anyway.
The old code (combined with long-term caching) caused failures in my application. It took me a while to locate the reason, which this PR fixes.

@zhenyong okay for you?

Thanks @zhenyong
Would you mind publishing a new release on npmjs.com? thanks!


App should move to run placed screen if there is an active run.

Check database for active run and redirect user to that screen.
This will account for the case where the user closed the app.

Hold off on this until all testing is done. @ZonalWings


Create maven.yml

setup
Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

no need setup maven yml


As a Developer I want to run the example in Kubernetes

We want to provide a simple example of how to run a service that uses JWT-OPA on a Kubernetes cluster as a Pod, via a Helm chart.

Hello, this is my first experience with open source contributions. Would really appreciate it if you explained exactly what is needed to be done.
I would love to work on this issue.
Thanks in advance! :)

Hi Anushka - I'm so glad you're willing to help out here :+1:
The general idea is that the webapp is an example Spring Boot server app, which demonstrates how to use jwt-opa for those who wish to adopt it: in this respect, I'd like to also provide a Helm chart to deploy it (for example) on a Kind cluster (for dev env) so that folks who are deploying to K8s (the vast majority these days) can test it out in their environment.
So, ideally, we would have a couple of options:

"bare" webapp - just the server container, with a service that fronts it; the user will deploy OPA and MongoDB (or whatever DB they chose to use) separately;
"batteries included" webapp - a fully-fledged Helm chart, that deploys (and configures) webapp, OPA, Mongo.

This may need some "glue" scripting to generate the "bundle" of Rego policies for OPA (but that part I already have the code for, no worries).
Does this make sense?
Thanks!

And this also made me realize that we should also have a Dockerfile (just created #52)


Pass dependencies from stuff like postcss-import to webpack

Using postcss-import and this loader, whenever something is @import'ed, making changes to the @import'ed file doesn't recompile the files depending on it.

What postcss-import do you use? The latest version supports dependency message and postcss-loader use this message for behavior that you want:
https://github.com/postcss/postcss-loader/blob/master/index.js#L125

:/ sorry I coulda sworn I had updated to latest of both of these things before filing...


KeyError for binarised features during makecldf.

Binarised features inherit their Clarifying Comment from their parent features.  However, the inheritance was implemented too late which means the features raised a KeyError when running makecldf.
This patch copies the parent values right when the features are loaded from disk.

I hope so, too. (<_<)"


Meteor 1.8.2: ReferenceError: meteorBabelHelpers is not defined

Getting:
lib.coffee:1131 Uncaught ReferenceError: meteorBabelHelpers is not defined
seems to be related to
https://github.com/peerlibrary/meteor-subscription-scope/pull/3/files
and
https://forums.meteor.com/t/meteor-1-8-2-beta-17-referenceerror-meteorbabelhelpers-is-not-defined/50097/6
I changed it to...
fields = Object.keys(Blaze.TemplateInstance.prototype)
blazeComponentMethods = Object.keys(BlazeComponent.prototype)
for i in [0...fields.length]
  methodName = fields[i]
  if methodName in blazeComponentMethods
    continue
  method = Blaze.TemplateInstance.prototype[methodName]
  do (methodName, method) ->
...

But it seems like there's some other uses of that loop in there... not sure if that will be enough for all cases...

I think you are not using the latest package. Please check which version of the package you are using. Please provide a small reproduction.

I'm using 0.23.0
I tried a reproduction using meteor create --bare; meteor remove static-html; meteor add peerlibrary:blaze-components
But it doesn't seem to happen. I checked and all the packages installed in versions in the repro are the same in my project. So I'm a little confused since the error is being reported as peerlibrary:blaze-components

From my experience I think you are not really using 0.23.0. Can you check in versions file?

<EMAIL_ADDRESS>

Hm, then I do not have an idea. Without reproduction I cannot really help much here. :-(
Maybe some other PeerLibrary dependency is not at the latest version.

OK I took the packages from from my large app and copied it into a new project. Seems to reproduce this issue but I'm not yet sure why...
https://github.com/hexsprite/meteor-blaze-components-156

Have you went through all peerlibrary packages in versions and made sure they are at the latest version?

Have you went through all peerlibrary packages in versions and made sure they are at the latest version?

Yup.

I am not sure when I will have time too look into this. I thought this has been resolved by re-publishing all packages.
You could try putting them temporary into packages/ inside your app, and see if that resolves it. And if does, then bisect to see which one has to be there. And then I can look if I maybe missed some to republish.

Thanks, I'm going to be busy with some other issues but I will return to this and let you know what I figure out... I suspect something is pulling in an old dependency...

I suspect something is pulling in an old dependency...

But you would see that in .versions file I believe.

I've been checking dependencies using meteor list --tree but I don't notice anything obvious.
As a workaround I forked the package and added meteorBabelHelpers = Package.modules.meteorBabelHelpers at the top of lib.coffee and that has fixed the problem for now.
I audited all the built packages and found that also peerlibrary:base-component was also missing the meteorBabelHelpers declaration.

I'm curious by which mechanism that Meteor decides that a given package requires the a particular dependency declaration to be added... seems like something is broken there...

They are using dependency resolver, computing the solution for all dependency constraints. So something is pushing an old version.
Have you tried cloning repositories into packages? From my experience that should be enough and no need to change the code in a forked repo?

Have you tried cloning repositories into packages? From my experience that should be enough and no need to change the code in a forked repo?

Yes. It did not help. I had to add the declaration in order to get it to work.

Bumping this as I also ran into the same or a very similar issue when building for cordova/electron (web version works just fine).
Uncaught ReferenceError: meteorBabelHelpers is not defined
    at lib.coffee:1131


[IDEA] netflix and/or airplay

Please read conditions below carefully, and don't delete this part. Invalid issues will be closed.

No apps related to piracy or intellectual property infringement is allowed.
We can't guarantee if the app will be developed by anyone.
We encourage you to develop the app by yourself. This would be a great contribution to webOS homebrew community.

[x] I understand conditions above
[ ] (Optional) I'd like to develop this app by myself

Issue content starts below this line

Hello,
recently I bought an LG PF610P projector and noticed that it does not has the Netflix app on it, but it does have Amazon Prime, Disney+ etc. The big brother HU810P got the app after an update.
Then there is the HU70LS, which has the app, but does not have AirPlay.
Now to the idea. I saw that there is an add free YouTube app.
Would it be possible to create something equal for the Netflix app? I mean, to download the app on devices, which don't support the app?
Maybe a bit harder, the idea to bring AirPlay to the devices, which don't have AirPlay?
If there is any way to achieve one of the goals quickly, with an tutorial or something like that, that would be enough for me :)

AirPlay would be something easier to start. First you have Moonlight to stream screen on your computer, and IHSplay (which is in early stage testing) to stream desktop via Steam.

For Netflix, it would be harder, sometimes it's as easy as copy the binary to run on your project, while sometimes it would be nearly impossible, as it requires proper DRM support to stream.

If it didn't come with Netflix, there was probably no idfile provisioned at the factory. Therefore, as far as I understand it, Netflix is never going to work.


Fixes for Turkish translation files.

Closing this as there was no more action on this and it seems that this adds little value and breaks translations as @piotrgradzinski mentioned.

Emmanuel Lamblin

Le vendredi 22 décembre 2017 à 02:16:58 UTC+1, Kerem Güneş<EMAIL_ADDRESS>a écrit :

@k-gun commented on this pull request.
In locale/tr/LC_MESSAGES/More/EAV/README.po:

@@ -17,7 +17,7 @@ msgstr "Entity-Attribute-Value (Varlık-Özellik-Değer)"

#: ../../More/EAV/README.rst:4
msgid "The Entity–attribute–value (EAV) pattern in order to implement EAV model with PHP."
-msgstr ""
+msgstr "-"
'Cos it does not add anything to translation. It sounds EAV is EAV.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


[WIP] Improve/extend reference manual

List of Changes

Add all modules to the reference manual.
Change class render template: class methods now don't get their own files any longer, their documentation is now located in their corresponding parent classes. (Also speeds up docbuild on RTD, from ~300sec to ~270sec.)
Fix all Sphinx warnings

TODO:

Add more documentation 🙃 (at least some more one-line module / class documentations...) -- help welcome!

Motivation
The reference manual should be as complete as possible, even if there is little to no documentation for the methods/objects.
Testing Status
See https://behackl-manim.readthedocs.io/en/improve-refman/reference.html for a deployed version.
Acknowledgement

[x] I have read the Contributing Guidelines

In a157c047, I tried adding summary docstrings for most submodules of mobject.
There are some modules where I am not sure what they are actually used for, and some where I did not really know what to write. The missing ones are:

mobject.changing
mobject.frame
mobject.mobject_update_utils
mobject.three_d_shading_utils
mobject.three_d_utils

Furthermore, when skimming through the modules, I felt that there are some inconsistencies (or at least weird choices), e.g., I feel that mobject.shape_matchers and mobject.brace could merge into mobject.annotation or so; mobject.value_tracker and mobject.mobject_update_utils seem compatible to some degree (if I understood their intended use correctly); mobject.three_d_utils and mobject.three_d_shading_utils seem compatible; and I also see some common ground for mobject.number_line and mobject.coordinate_systems. (I certainly don't propose changing all of this now and here, but I was curious in how far structural changes like these have been discussed before.)
See either the changed files here or https://behackl-manim.readthedocs.io/en/improve-refman/reference.html for a list of the others.
I suggest adding all of the remaining missing module summaries, and doing more detailed documentation in follow-up PRs (in order to not blow this out of proportion and keep it reviewable).

There are some modules where I am not sure what they are actually used for, and some where I did not really know what to write. The missing ones are:
Furthermore, when skimming through the modules, I felt that there are some inconsistencies (or at least weird choices), e.g., I feel that mobject.shape_matchers and mobject.brace could merge into mobject.annotation or so; mobject.value_tracker and mobject.mobject_update_utils seem compatible to some degree (if I understood their intended use correctly); mobject.three_d_utils and mobject.three_d_shading_utils seem compatible; and I also see some common ground for mobject.number_line and mobject.coordinate_systems. (I certainly don't propose changing all of this now and here, but I was curious in how far structural changes like these have been discussed before.)

There are numerous inconsistencies. I think what you've done is a big step forward, so I won't worry about those other modules just yet. Moreover, the fact that a dev is confused about them means that they're not ready for public documentation anyway.

I suggest adding all of the remaining missing module summaries, and doing more detailed documentation in follow-up PRs (in order to not blow this out of proportion and keep it reviewable).

Agreed.

Alright, then lets do it like that! 👍
Thanks for the suggested changes; I first thought of writing more than just the one-line summary---but then decided against it; its better to have well-documented classes (and maybe even an improved structure for the modules) first.

manim.scene.reconfigureable_scene only contains the class ReconfigureableScene, which mentions prominently in its documentation that "Note, this seems to no longer work as intended."
I won't add a module summary to it; it should probably be removed.

This is complete from my point of view. While the diff looks a bit scary at first glance, there are three files that actually needed a bit more attention: mobject/svg/code_mobject.py, mobject/svg/text_mobject.py and utils/tex.py. For these, having a look at the rendered documentation -- but unfortunately, something weird is happening over at RTD with this branch since I resolved the merge conflict such that it does not build the correct version; so building docs and looking at them has to be done locally.

All the open discussions should now be resolved with 356d1115. :-)


[PY] feat: task modules decorators

Linked issues
closes: #534
Details

Add decorators for task modules fetch / submit
Removes check of data property length because the property does not always only have 1 property
TODO: The submit functionality needs more discussion, seems it cannot be triggered based on current design in JS. I need more background for this functionality.

Change details

Describe your changes, with screenshots and code snippets as appropriate

code snippets:
screenshots:
Attestation Checklist

[x] My code follows the style guidelines of this project

I have checked for/fixed spelling, linting, and other errors

I have commented my code for clarity

I have made corresponding changes to the documentation (we use TypeDoc to document our code)

My changes generate no new warnings

I have added tests that validates my changes, and provides sufficient test coverage. I have tested with:

Local testing
E2E testing in Teams

New and existing unit tests pass locally with my changes

Additional information

Feel free to add other relevant information below

@blackchoey FYI for next time, you can delete the parts of the template that you don't use :)


Upgrade Authors Haven Django app from Django 1.10 to Django 2.1

What does this PR do?
This Pull Request upgrades the codebase from Django 1.10 to Django 2.1
Description of Task to be completed?
Currently, the codebase is running Django 1.10 which was released in August 2016, Django 2.1 is the latest release of Django with the full support of Python 3.x series.
How should this be manually tested?
pip install -r requirements.txt

pip freeze to see what version of Django
What are the relevant pivotal tracker stories?
#162163155

Nice work Eric, I can see Django and the Django Rest Framework has been fully updated./

@ekumamait this looks good! Yes, Django is updated to 2.1! Good work!


webhook fix

这个 PR 实现什么功能/修复什么问题:

fix(region): send webhook notification when delete dbinstance
fix(region): send webhook when the creation task is completely completed

是否需要 backport 到之前的 release 分支:

release/3.7
release/3.6
release/3.5

/area region
/cc @zexi

Codecov Report

Merging #11116 (f3e3a94) into master (a737ab7) will increase coverage by 5.35%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #11116       +/-   ##
===========================================
+ Coverage    5.81%   11.16%    +5.35%
===========================================
  Files         901      147      -754
  Lines      139117    16957   -122160
===========================================
- Hits         8088     1894     -6194
+ Misses     130322    14870   -115452
+ Partials      707      193      -514

Flag
Coverage Δ

aFlag
11.16% <ø> (+5.35%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/compute/models/storageresource.go

pkg/compute/regiondrivers/kvm.go

pkg/compute/models/routetable_routesets.go

pkg/multicloud/ecloud/create_time.go

pkg/hostman/system_service/telegraf.go

pkg/hostman/system_service/ovn_conroller.go

pkg/cloudcommon/db/enabledstatusinfrasresource.go

pkg/mcclient/options/k8s/fed_namespace.go

pkg/cloudcommon/db/query.go

pkg/util/gin/middleware/keystone_auth.go

... and 744 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 a737ab7...f3e3a94. Read the comment docs.


change base_url on file config

Please approve this PR, changes base_url on file config, thank you

Oke PR approved and already to merge


Where to fix pre-loading size

I deployed CVAT on a server and issue is when multiple annotators loading files, the speed will be very slow, so I want to fix pre-loading size.

I am not sure it is CVAT issue, usually downloading speed depends on the bandwidth of the server and user's host. What do you expect from CVAT side?

I will close the issue, because there is not a response from your side. Do not hesitate to reopen it if you still have questions


Integrate Public Domain Map

This PR pulls in my work incorporating Public Domain Map into the tasking manager. It also includes related work updating and rebranding the TM for OSMUS.
I'm drafting this work-in-progress PR to help with tracking and discussing the changes.

Screenshots! Notable features of this update:

New fonts, colors, and messaging related to OSMUS
Public Domain Map projects live alongside OpenStreetMap projects, distinguished by colors and labels
Only approved orgs can create Public Domain Map projects
The Public Domain Map editor only includes license-compatible data sources


AveragePool incorrect for asymmetric padding

MIGraphX used explicit padding when padding size is asymmetric. As a result, the padding elements are counted in the number of elements in the window, which cause incorrect output.
The solution could be tuning the number of elements in the window in the case of asymmetric padding.

AveragePool.pptx
avepool.zip
I create some slides that explains why averagepool with asymmetric padding is incorrect. The zip contains a very simple program that can reproduce the problem, an onnx file and the python script used to create the onnx file.

One solution could be tuning the output value by multiplying a tuning factor, which can be computed as (window_size / non_padding_element_num in the window).

PR# 553 is created for this issue.


Invisible email / password textbox and words in login page in Darkmode?

Hi everyone,
Is there anyone hitting a strange problem as below?
I tried it in Samsung phone. Android 10.
The email and password textboxes are invisible.
When I touch the screen, the boxes appear.
I can key in but the words are not displayed too.
However, I can still login.
Updated: This issue happened when I set my phone into Dark mode. Normal mode shows OK. Should fix anything for Darkmode?

Fixed in https://github.com/thingsboard/flutter_thingsboard_app/pull/7