Texture and texture creator

Hello, First of all I am sorry for the newbee question.
I have some trouble to understand how I can manage the Texture and the Texture creator.
I am stuck with the lifetime of the texture. So for the moment I do something like the code bellow to get a texture, but I have to do it at each iteration of my game loop. I have the feeling that is not the way it have to be used.
/// Example of how I create a texture
let map_loader = sdl2::rwops::RWops::from_file(Path::new("assets/Overworld.png"), "r").unwrap();
let surface: Surface = map_loader.load_png().unwrap();
let texture = self.creator.create_texture_from_surface(&surface).unwrap();

So basically I wanted to have a structure that own some information (such as the texture for example) the GameScene:
pub struct GameScene<'a> {
    creator: sdl2::render::TextureCreator<sdl2::video::WindowContext>,
    /// I would create a texture once and store it.
    texture: sdl2::render::Texture<'a>,
   /** Other objects **/
}

So here it is, the code bellow does not compile because the creator outlives the texture.
I have no clue of how to do such a things, I did some attempts:
struct TextureHolder<'a> {
    creator: &'a sdl2::render::TextureCreator<sdl2::video::WindowContext>,
    texture: sdl2::render::Texture<'a>
}

pub struct GameScene<'a> {
    creator: sdl2::render::TextureCreator<sdl2::video::WindowContext>,
    texture: TextureHolder<'a>
}

The code above would allows me to have a texture and its creator bounded to the same lifetime
But when I am creating a GameScene with the following code

let creator = canvas.texture_creator();
let textureHolder = TextureHolder {
    creator: &creator,
    texture: creator.create_texture_from_surface(&surface).unwrap()
};

GameScene{
    /// I have to find someone to own my creator.
    creator: creator,
    grid: grid,
    map: map,
    /// So this
    textureHolder : textureHolder
}

I've got the error :
error: `creator` does not live long enough
   --> src\scene.rs:95:23
    |
95  |             creator: &creator,
    |                       ^^^^^^^ does not live long enough
...
105 |     }
    |     - borrowed value only lives until here
    |
note: borrowed value must be valid for the lifetime 'a as defined on the body at 62:81...

I understand that the texture is bound to the creator, but I have no clue how to achieve this. I hope someone could point me to the right direction.
By the time I'll read some documentations about the lifetime :) .
I'm sorry for the inconvenience,
Thank you very much.

I'll take a look into in a few hours, but in the meantime you can try getting help from the #rust, #rust-beginners and #rust-gamedev IRC channels on mozilla's IRC, I'm sure they will be willing to help!
On Jun 2, 2017, 16:19, at 16:19, Adrien FAURE<EMAIL_ADDRESS>wrote:

Hello, First of all sorry for the newbee question.
I have some trouble to understand how I can manage the Texture and the
Texture creator.
I am stuck with the lifetime of the texture. So for the moment I do
something like the code bellow to get a texture, but I have to do it at
each iteration of my game loop. I have the feeling that is not the way
it have to be used.
/// Example of how I create a texture
let map_loader =
sdl2::rwops::RWops::from_file(Path::new("assets/Overworld.png"),
"r").unwrap();
let surface: Surface = map_loader.load_png().unwrap();
let texture =
self.creator.create_texture_from_surface(&surface).unwrap();

So basically I wanted to have a structure that own some information
(such as the texture for example) the GameScene:
pub struct GameScene<'a> {
   creator: sdl2::render::TextureCreator<sdl2::video::WindowContext>,
   /// I would create a texture once and store it.
   texture: sdl2::render::Texture<'a>,
  /** Other objects **/
}

So here it is, the code bellow does not compile because the creator
outlives the texture.
I have no clue of how to do such a things, I did some attempts:
struct TextureHolder<'a> {
creator: &'a sdl2::render::TextureCreator<sdl2::video::WindowContext>,
   texture: sdl2::render::Texture<'a>
}

pub struct GameScene<'a> {
   creator: sdl2::render::TextureCreator<sdl2::video::WindowContext>,
   texture: TextureHolder<'a>
}

The code above would allows me to have a texture and its creator
bounded to the same lifetime
But when I am creating a GameScene with the following code

let creator = canvas.texture_creator();
let textureHolder = TextureHolder {
   creator: &creator,
   texture: creator.create_texture_from_surface(&surface).unwrap()
};

GameScene{
   /// I have to find someone to own my creator.
   creator: creator,
   grid: grid,
   map: map,
   /// So this
   textureHolder : textureHolder
}

I've got the error :
error: `creator` does not live long enough
  --> src\scene.rs:95:23
   |
95  |             creator: &creator,
   |                       ^^^^^^^ does not live long enough
...
105 |     }
   |     - borrowed value only lives until here
   |
note: borrowed value must be valid for the lifetime 'a as defined on
the body at 62:81...

I understand that the texture is bound to the creator, but I have no
clue how to achieve this. I hope someone could point me to the right
direction.
By the time I'll read some documentations about the lifetime :) .
I'm sorry for the inconvenience,
Thank you very much.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/AngryLawyer/rust-sdl2/issues/667

Hello,
Thank you very much ! There is no rush :)
I this time to sleep for me !
I will go on IRC tomorrow,  and I will keep this thread up to date.

This might be helpful: https://stackoverflow.com/questions/32300132/why-cant-i-store-a-value-and-a-reference-to-that-value-in-the-same-struct

Hi, so I went on IRC to ask my question.
The conclusion, is that it is impossible to achieve what I want to do; or I use the API the wrong way.
I wonder what is the recommended way to obtain/store a texture before rendering it ? And what is the cost of creating a new texture: with creator.create_texture_from_surface for example.
Thank you.
By the way, very interesting stackoverflow thread, thank you;

We have several examples using Texture in the examples folder, for this repo, you might be interested in running cargo run --example resource-manager and cargo run --example game-of-life and examine the source code to see how it is used!

Hi thank you for your answer, but still I am not convinced of the resource manager.
For my case it only add a lot of complexity.
For me the API works well as long as the code stays in one file. But I try to split my code into submodules,
I have huge issues with lifetime.

I have had similar issues and my recommendation is to for your main to handle the lifetimes of the dependencies that are meant to last your whole program. What I mean by this is, create the texture creator (and renderer) in your main and pass a reference to the texture creator onto your game struct. This way we guarantee that the texture creator outlives any texture that is created within your game (your game goes out of scope before the texture creator) which solves all the lifetime issues you are having. I hope this helps (:

I wonder if it would be possible to remove the need to have an explicit lifetime on the Texture struct, though. That would make the whole lifetime management a lot easier.

I would love to find a solution that simplifies the lifetime management of textures. I am unsure how it coule be done given the constraints of sdl2 while keeping the code safe. Safety for me means
no undefined behaviors that could lead to a segfault.

The other immediate solution would be to wrap a reference to Renderer/ TextureCreator on every texture, and destroy the Renderer only when all the textures are dropped as well, but the overhead would be non-negligible, plus you may not want to allocate on the heap unnecessarily . Since Window cannot be destroyed before renderer as well, that would mean that a memory leak would potentially lead to a forever-opened window as well, and I'm not sure that's what we want...
I feel like the current way it is implemented is the "Rust" way of doing it, but if you don't agree with that, the SDL2_sys bindings are open and you can totally create your own wrapper that manages Textures differently!

The issue with the explicit lifetime on Texture is that as soon as you have some complex structure that needs to access the Texture, you start propagating explicit lifetimes all over your code.
You can see an example at my repo here: https://github.com/tanis2000/minigame-rust
Just look at https://github.com/tanis2000/minigame-rust/blob/master/src/renderstate.rs or https://github.com/tanis2000/minigame-rust/blob/master/src/spritebatcher.rs
Those structs just need to be able to access the Texture while rendering so that I am carrying around a reference to the Texture of the sprite batch item that I computed. This is still manageable, but then I started adding my own implementation of an entity-component-system on top of that and components that carry around an image, like a sprite, now need to reference their texture as well. So I have to propagate the explicit lifetime over there, too. And the main object that is instantiating the TextureCreator is having issues as I need to keep a reference to TextureCreator somewhere but also pass it over to my texture manager (sort of a resource manager for textures).
I know there must be a solution but things have started getting tricky. It's not really a rust-sdl2 issue per se; it's more like an issue with the need to refactor lifetimes as you build more systems into your own engine. That's why I started wondering if there could be a solution to avoid the explicit lifetime on the Texture itself, but I understand it's probably not possible because Rust is actually forcing you to behave the way you should.

What we could do is add a feature that would totally remove the lifetimes by removing the fact that Texture are destroyed on Drop. We could let them live indefinitely or manually (via a unsafe fn destroy(self) or something) and SDL_Renderer's drop actually drop the structure behind Texture. It would be technically safe as long as only one Canvas is used, because Texture cannot be used other than with a Canvas. destroywould be unsafe because it would be possible to destroy a Texture after its Canvas, and that would be undefined behavior; therefore the user must be careful to not destroy Textures after their Canvas.
This alternative is a little bit unsafe and requires more end-user control, but it will get rid of the lifetime and be easier to manage in things such as ECS as well.
I'm going to try something with that in mind soon, and if you don't mind @tanis2000 I'd like you to test that upcoming feature to tell me how it sounds. If that goes well, it's going to be in the v0.31.

Sure thing! I'm up to test it out and see how it fits.
So, if I understand it correctly, the Canvas is holding all the Textures. Would it be possible to let the Canvas lend the Texture through Rc.clone() to avoid having to use unsafe code?

The problem I have with Texture holding an Rc of Canvas is that Canvas cannot be dropped unless all Textures have been dropped as well. Since the Canvas can't be dropped, that means that potentially the Window that is linked to the Canvas can't be dropped. The thing is that Window's drop is literally "stop displaying this Window" from the Operating System perspective, meaning that if you have a memory leak with a Texture, you would have your window left opened until that memory leak goes away... Which is at worst at the program's completion.
The program's completion doesn't sound too bad in a single game, but if your application is made of multiple parts and multiple windows, you don't want to see one of the window still opened with no interaction possible whatsoever (you wouldn't even be able to close it since your event loop for this Window would not be active anymore). I agree that having memory leaks is something programmer-related, but it's trickier to debug than lifetimes.
The tricky part is that memory leaks are 100% safe and can happen a lot of the time, especially when dealing with Rcs
That's why I would prefer something slightly unsafe (but you don't even have to use it, you can let Canvas' Drop drop all the textures without worries) if someone needs fine tuning, than something safe but potentially doing something that the programmer doesn't want at all.

I don't know how possible this is, and I wish I had the time to test it out, but in my head I had envisioned the possibility of having the rust version of the sdl2 renderer mimic the c version of sdl2 a little closer, and how that might help. By this I mean, in the c version of sdl2, we have this renderer that owns the textures, and it only is in charge of mananging them. The reason why the textures cannot outlive ther renderer, is because the renderer will destroy them all when the renderer is destroyed. I wonder how possible and beneficial it would be to do such a thing within the rust version.
If we mimic'd this in the rust version, I envision we would have some shared data map that is owned (through some internall unsafe code) by the TextureCreator +Canvas + any Texture created. The TextureCreator is in charge of creating the Texture, adding them to the data map, and returning, not the SDL_Texture, but an identifier to it. The Renderer is in charge of, given a texture identifier, being able to locate it in the map, get the SDL_Texture out, and render it. This texture identifier, will have to be able to delete itself from the data map when it goes out of scope, somehow. When the Canvas goes out of scope, it deletes all of the entries from the data map.
This would solve the lifetime issues because now the TextureCreator doesn't care if the texture identifier outlives the Renderer. If the texture identifier outlives the Renderer, well too bad, no one can render it anyway and the real SDL_Texture was destroyed already. If the Renderer is passed an incorrect identifier, then we return an error, since all of those methods already return Result<> I believe.
I am unsure how doable this is, but I think by "enforcing" the C behavior in the Rust wrapper, we might be able to pull something that feels more idiomatic and ergonomic. Some kinks that would need to be worked out is how would this affect current methods on the Texture (e.g., do the texture query)
I am unsure if this added anything to the discussion since it seems you all already have an idea, I just wanted to share a thought I had but have not had the time to implement yet.

@Cobrand actually I mean that the Canvas should own a map of Rc<SDL_Texture> so that it can lend the texture to whatever function is in need of a reference through a clone(). It might make things less "unsafe", but then again I'm no expert with Rc so I might be completely off with this.
While I like @nrxus proposal, it would actually make it a little more difficult the management of textures for those not using the SDL2 rendering stuff. As an example, I am just using SDL2 to manage the window and the textures, while all the rendering is done with my own renderer that is using OpenGL ES 2 with no SDL2 involved at that stage except for retrieving the handle to the actual texture.
On the other hand, just like you envisioned the SDL2 renderer being able to pull out the SDL_Texture and use it, if such a mechanic would be directly available from within the Renderer, that would be fine as well. I'd just skip the rendering part and use the Renderer as a texture storage of sorts.

This crate stills aims to have minimum impact on performance while being the closest to the source, and in the source the Renderer doesn't own the Textures, it's merely linked. If the Renderer dies, all of the Textures die automatically, and that's it. A HashMap is still pa performance overhead; having to implement that in the default sdl2 crate means that everyone that don't want to use a HashMap won't be able to do it with sdl2 only, they'd have to use sdl2-sys instead.
Having a HashMap<Id, Texture> would be the role of another crate in this case.

It depends how you view "owning". From my perspective, if the Renderer is in charge of creating and destroying the textures, I would view it as owning the Textures.
I agree with the performance overhead, though. It might be a hit that we might not want people to incur as the default.

Fixed by #683, feel free to re-open if that's not enough.

That's super! I'm going to switch my master to use this feature as tests worked fine


Improve title annotations

This PR improves some titles by

Removing leading "The "
Aligning capitalization (sentence case)
Removing " settings" where it's not needed

Also adds a description to make one property less ambiguous.

Assuming that team Clippy is fine with annotation modifications.


Quests does not show saved quests

Where else have you looked for answers to this question?
I have looked on Reddit, Github, Spigot, citizens NPC and any Google articles I can find.
Share your question with as much detail as possible?
How can I make the saved quests be able to be used in game again?

I do not have any quests errors in my console

Once you save the quest, run /questadmin reload or restart the server. If the quest does not appear in-game, check your server's console for errors. If there are none, submit a new issue as a Bug Report.


using Winston fails julia  0.3.0 x86_64-linux-gnu (Xubuntu 14.04 LTS)

See below.  I tried installing the libglib2.0-dev package but it didn't help.  Any sugestions?
julia> Pkg.update()
INFO: Updating METADATA...
INFO: Updating cache of REPLCompletions...
INFO: Updating cache of IJulia...
INFO: Computing changes...
INFO: Upgrading Color: v0.3.3 => v0.3.4
INFO: Upgrading IJulia: v0.1.13 => v0.1.14
INFO: Upgrading Winston: v0.11.2 => v0.11.4
INFO: Building Nettle
INFO: Building ZMQ
INFO: Building IJulia
Found IPython version 1.2.1 ... ok.
Creating julia profile in IPython...
(Existing KernelManager.kernel_cmd setting in ipython_config.py is untouched.)
(Existing IPythonWidget.execute_on_complete_input setting in ipython_qtconsole_config.py is untouched.)
(Existing FrontendWidget.lexer_class setting in ipython_qtconsole_config.py is untouched.)
(Existing NotebookApp.port setting in ipython_notebook_config.py is untouched.)
(Existing ipynblogo.png file untouched.)
(Existing ipynblogo.svg file untouched.)
(Existing favicon.ico file untouched.)
(Existing custom.js file untouched.)
(Existing julia.js file untouched.)
INFO: Building Cairo
Installing dependency libglib2.0-0 via sudo apt-get install libglib2.0-0:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libglib2.0-0 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
INFO: Building Tk
julia> using Winston
ERROR: _jl_libgobject not defined
in init at /home/bharris/.julia/v0.3/Tk/src/tkwidget.jl:36
in include at ./boot.jl:245
in include_from_node1 at ./loading.jl:128
in include at ./boot.jl:245
in include_from_node1 at ./loading.jl:128
in reload_path at loading.jl:152
in _require at loading.jl:67
in require at loading.jl:54
in include at ./boot.jl:245
in include_from_node1 at ./loading.jl:128
in include at ./boot.jl:245
in include_from_node1 at ./loading.jl:128
in reload_path at loading.jl:152
in _require at loading.jl:67
in require at loading.jl:51
while loading /home/bharris/.julia/v0.3/Tk/src/tkwidget.jl, in expression stng on line 452
while loading /home/bharris/.julia/v0.3/Tk/src/Tk.jl, in expression startingline 25
while loading /home/bharris/.julia/v0.3/Winston/src/tk.jl, in expression stag on line 1
while loading /home/bharris/.julia/v0.3/Winston/src/Winston.jl, in expressioarting on line 2699
julia> quit()

Closing as this package no longer supports Julia 0.3.


Fix BUNDLE_PATH_RELATIVE_TO_CWD env variable name

What was the end-user problem that led to this PR?
The problem was that an environment variable in the docs does not work.
What was your diagnosis of the problem?
My diagnosis was that its name is incorrect.
What is your fix for the problem, implemented in this PR?
My fix is to fix the typo.
Why did you choose this fix out of the possible options?
I chose this fix because it's the only non absurd fix.

It sounds like Github needs a break :)

GitHub isn't sending webhooks, so we won't be able to use bundlerbot for the moment.

Yeah, I guess everyone has noticed by now :sweat_smile:. It's amazing how tightly we depend on certain services :open_mouth:.

@bundlerbot r=greysteil


I just pushed to master

I was trying to get my local and remote branches updated to the latest version of HoloToolkit-Unity, but now I see one of them points to our master. Can someone revert may latest commit or let me know how to do it?

You should be able to revert fairly easy.
Which git client are you using?

I'm actually really confused because some of the changes it says you made are things that already got merged into main...
Any chance to revert your commit?

Visual Studio

fixed

Thanks,


username-anarchy: init at 0.5

Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@D3vil0p3r if you have time for a review ?

@D3vil0p3r if you have time for a review ?

https://discourse.nixos.org/t/can-i-add-a-package-without-a-license-to-nixpkgs/33844

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4232

The license was added upstream, it is MIT, will update the pkg.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4248


PLANNER-1125: Various bug fixes

jenkins retest this

jenkins retest this

@Christopher-Chianelli Is this meant to fix all of the bugs described in https://issues.jboss.org/browse/PLANNER-1125? The "add foo spot, add shift for foo, then delete it -> error popup" use case is still broken.
Otherwise looks good.

@yurloc Yes; I have tested "add foo spot, add shift for foo, then delete (the shift for foo)"; no error popup (it is handled by the new moveAddedGridObjectToIdMap method in Lane). "add foo spot, add shift for foo, then delete (the spot foo)" is suppose to be an ErrorPopup for now; that issue is https://issues.jboss.org/browse/PLANNER-1095


scan_interval not working (and some other stuff)

Using scan_interval makes the "Senast uppdaterad" update at least every minute. Always -1 or 0 min since last updated. The time shown is always the current time +- 1 min. Bug? Calling the api every minute or display error? I used scan_interval: 7. Should it be in min or sec?
Btw, always show time, was that removed?
The card does not look like the other cards? No box? (note the update time, 0 min)

The card does not look like the other cards? No box?

I can confirm. There is a problem with paper-card-background-color

scan_interval is a time so that should be for instance like below. If you just specify a intervall with a integer that seems to be translated into seconds and that would then be 420.
scan_interval:
      hours: 0
      minutes: 7
      seconds: 0

The other part of the problem would be perhaps around the card. I cannot reproduce that error. I do have a frame as it looks in the readme, I'm using the below. Would that not give a frame in your end?
adjust_times: true
departures: true
deviations: true
entities:
  - sensor.molnvik_departures
language: sv-SE
name: Mölnvik
timeleft: true
type: 'custom:hasl-dep-card'
updated: true

The other part of the problem would be perhaps around the card.

const card = document.createElement('ha-card');
This fixes a bug with the card in line 4 hasl-comb-card.js

This have been updated/reverted in dev #22


CSS Isolation topic addresses Razor components, but what about Pages?

CSS Isolation topic addresses Razor Components, but what about Pages?
I have a page with unique styles that I'd like to have separate from the rest of the app. Can I use this mechanism for pages in addition to components?

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

ID: 2703a48e-8b35-53fc-ac36-cfb395833077
Version Independent ID: 39d464d9-aca6-34fa-7e52-5fde2e393ba7
Content: ASP.NET Core Blazor CSS isolation
Content Source: aspnetcore/blazor/components/css-isolation.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @daveabrock
Microsoft Alias: riande

Hello @Paul-Dempsey ... Product feature requests should go to the PU ("product unit"), as just handle docs here. Open an issue to discuss it with them at ...
https://github.com/dotnet/aspnetcore/issues

At the very least, the page can document that this is only for components, and not pages. That would be satisfactory.
From: Luke Latham @.>
Sent: Thursday, April 29, 2021 9:35 AM
To: dotnet/AspNetCore.Docs @.>
Cc: Paul Dempsey @.>; Mention @.>
Subject: Re: [dotnet/AspNetCore.Docs] CSS Isolation topic addresses Razor components, but what about Pages? (#22165)
Hello @Paul-Dempseyhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPaul-Dempsey&data=04|01|Paul.Dempsey%40microsoft.com|6323d1b071154d28d03808d90b2cae64|72f988bf86f141af91ab2d7cd011db47|1|0|637553108797867401|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=iIj8BmHhco8JTjlaKHVCHZTpV0JF9PCMvi5B%2FJVlQ2c%3D&reserved=0 ... Product feature requests should go to the PU ("product unit"), as we just handle docs here. Open an issue to discuss it with them at ...
https://github.com/dotnet/aspnetcore/issueshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Faspnetcore%2Fissues&data=04|01|Paul.Dempsey%40microsoft.com|6323d1b071154d28d03808d90b2cae64|72f988bf86f141af91ab2d7cd011db47|1|0|637553108797867401|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=4W8MBOaEEXr1FL90gxs%2B0yohLgICczeb9N5PlT0GyV4%3D&reserved=0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2FAspNetCore.Docs%2Fissues%2F22165%23issuecomment-829402039&data=04|01|Paul.Dempsey%40microsoft.com|6323d1b071154d28d03808d90b2cae64|72f988bf86f141af91ab2d7cd011db47|1|0|637553108797877394|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=yoO89UqSWi2fHRUVhxCh%2BKVIlgA4s7VENlZSGGM4JUQ%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF7S4CSAVYEFQEQBRWRTCN3TLGDB5ANCNFSM432HDLZA&data=04|01|Paul.Dempsey%40microsoft.com|6323d1b071154d28d03808d90b2cae64|72f988bf86f141af91ab2d7cd011db47|1|0|637553108797887388|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=KmA5PaoTcKoftBIql0lxdHKHWA%2BAwITf%2Bf1AbjtdHm4%3D&reserved=0.

It does indirectly, which is the standard docs organizational practice ... e.g., emphasis added ...

Title: "ASP.NET Core Blazor CSS isolation"
Location: It's in the Blazor node of the ToC.
Opening line: "CSS isolation simplifies an app's CSS footprint by preventing dependencies on global styles and helps to avoid styling conflicts among components and libraries."
Various examples: "To define component-specific styles ...", "Blazor rewrites CSS selectors to match markup rendered by the component.", etc.

... and it doesn't cross-link to any corollary in RP/MVC because such a thing doesn't exist to cross-link.
We don't want to go down this road of covering things that other frameworks do/don't do. This is the Blazor node, and we keep the content fairly focused on Blazor. The only overlap that we keep IIRC is for scaffolding and Razor syntax, where there is so much overlap that we keep the content in a combined topic. Those topics do need to say 'this is for RC' and 'this is for RP/views'. Where Blazor Server uses ordinary ASP.NET Core bits, we try to not cover the features at all in the Blazor node but defer to the main ASP.NET Core doc set for coverage.
Like I said, there's a Razor Pages ToC node. If you don't see a feature there ... which is revealed very quickly by searching the docs ... it isn't a Razor Pages scenario. The entire doc set is based on this principle.
Thanks again tho for the feedback. At least for the time being, I'd prefer to stick with not drifting into "this is only for Razor components" lingo here ... such language would have to go all over the place in this node.

I am talking about Blazor Pages. (My app is server-side Blazor).
There isn’t even a node for Pages under Blazor, which seems like an omission. Perhaps I’m just confused and in fact Blazor pages are 100% identical to Razor pages, but that isn’t obvious or explicit anywhere.
I haven’t really noticed a ton of distinctions between components/vs pages in most Blazor functionality.
Anyway, it looks like a simple inline

"Blazor Pages" ❓
That's not a thing. You just made that up. - David Fowler, 2015
:smile: ... seriously tho ... I think I understand that you mean a Blazor Server app can host Razor Pages framework pages (or MVC views for that matter). The framework/technology descriptions in their introductory docs of their respective nodes try to cover it, and we'll keep working on those docs as we go. They get revised from time-to-time, and I'll go over them again on these points on the next cycle of updates.
Razor Pages is a different framework from Blazor (Razor components). The Razor Pages node is here ...
https://docs.microsoft.com/aspnet/core/razor-pages/
... and common content follows that node in the Web apps area (same folder level as the other types of web apps), including in the Advanced node.
WRT ...

I haven’t really noticed a ton of distinctions between components/vs pages in most Blazor functionality.

There are many distinctions between Razor components and Razor pages (and MVC views) outside of the shared Razor syntax. [There are no distinctions for Razor Pages (pages) and MVC controllers/views tho.] It's true that we don't have a kind of 'compare and contrast' presentation of the differences between components and pages/views, but the basics of components are covered in the Components node starting with ...
https://docs.microsoft.com/aspnet/core/blazor/components/
... and going right down to class libs ... which btw was one other area of decent overlap. We call out the Blazor-specific bits and use Blazor examples in the Blazor RCL topic to distinguish things from the doc in the main content at ...
https://docs.microsoft.com/aspnet/core/razor-pages/ui-class
In any case, this feature ... Blazor CSS isolation ... is a Blazor-only/Razor components-only scenario. You could pitch it to the PU as a possible cool thing for Razor Pages (pages)/MVC views, but that's an issue for the PU repo. Here, I'd like to avoid "this feature is only for Razor components" ... there are many places where such a remark would go. The reverse would be true as well: We don't want to litter the RP/MVC docs with "this feature is only for Razor Pages/MVC." That also would also need to appear all over the place. We focus content by ToC node, and I think we'll probably end up (mostly) sticking with our current approach. If devs do get confused and I see several issues coming in on something like this ... i.e., a point of confusion over pages/views and components ... then yeah ... I'd do something in the docs about it. I'll keep an :ear: open as we go forward.
btw - I think that management should consider a 'compare and contrast' type of topic. I've cross-linked this issue to my UE ("user experience") tracking issue for discussion at #19286. I'll chat with Dan and Artak about it later. We're so busy with UE passes (overhauls of topics) ... and soon 6.0 work ... that it won't be addressed until the end of this year. I'll make sure to raise it with them.
btw :smile: ... We're aware of the overload in what to call a hybrid app. It's really a hybrid ...
services.AddRazorPages();
services.AddServerSideBlazor();

Is it an Razor Pages/MVC app with Razor components?
Is it an Blazor Server app with Razor Pages/MVC?

Such apps use both frameworks, but they remain distinct and process requests separately with a little bit of gymnastics to move context data across the barrier.

Absolutely – I appreciate the time and thoughts.
Now if only I had the leisure time to read the docs top to bottom (after already having to read 172 pages of CSEO, Azure security compliance, internal wiki pages, one-notes, stack overflow and sharepoint pages just to check enough boxes Service Tree registration, and approvals and configuration just right simply to get a simple site to run inside Microsoft :-).
From: Luke Latham @.>
Sent: Thursday, April 29, 2021 12:24 PM
To: dotnet/AspNetCore.Docs @.>
Cc: Paul Dempsey @.>; Mention @.>
Subject: Re: [dotnet/AspNetCore.Docs] CSS Isolation topic addresses Razor components, but what about Pages? (#22165)
One more thing @Paul-Dempseyhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPaul-Dempsey&data=04|01|Paul.Dempsey%40microsoft.com|279b1328e5b043f4343508d90b4453ef|72f988bf86f141af91ab2d7cd011db47|1|0|637553210357970169|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=7CjxOODA%2B5ctCczUVB2NdmMYOj9g381wBAhn46M%2FQPk%3D&reserved=0. I was just reviewing our intro content on these concerns. We do have a section pertaining to these concepts at ...
https://docs.microsoft.com/aspnet/core/blazor/hosting-models#comparison-to-server-rendered-uihttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Faspnet%2Fcore%2Fblazor%2Fhosting-models%23comparison-to-server-rendered-ui&data=04|01|Paul.Dempsey%40microsoft.com|279b1328e5b043f4343508d90b4453ef|72f988bf86f141af91ab2d7cd011db47|1|0|637553210357970169|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=iLadmB4ezSrSvECCECPClxs3PAYzkBUouaPxvjtzb5I%3D&reserved=0
... and in the next few sections, which further describe particular aspects of Blazor Server apps. Take a look and see if that clears some things up.
Those sections could use another look later for improvements. I've made a note on the tracking issue so that it doesn't get lost.
Thanks again for chatting with me about it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2FAspNetCore.Docs%2Fissues%2F22165%23issuecomment-829524343&data=04|01|Paul.Dempsey%40microsoft.com|279b1328e5b043f4343508d90b4453ef|72f988bf86f141af91ab2d7cd011db47|1|0|637553210357980160|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=OPoP6zgzo2%2FrBIY6kzE3dcWPKIUDUly%2BNZnTNm3NmS0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAF7S4CUCQVVS5JWM2LQTERTTLGW4VANCNFSM432HDLZA&data=04|01|Paul.Dempsey%40microsoft.com|279b1328e5b043f4343508d90b4453ef|72f988bf86f141af91ab2d7cd011db47|1|0|637553210357990155|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3zV%2F0HK3RI7iTZd9%2FP9qpy3Oux%2FQYbUPEr91Hep99cw%3D&reserved=0.

@Paul-Dempsey ... I was just reviewing some of the new features that we'll be documenting for 6.0 and came across ...
https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-2/#css-isolation-for-mvc-views-and-razor-pages
... so that will lead to a cross-link in this topic to the new content, which will appear somewhere in the Razor Pages/MVC node(s). I don't tend to look too early in a release cycle at preview features because they change so much. By the time we get a few months out, many of the features will go into preview documentation. That process is getting underway now (https://github.com/dotnet/AspNetCore.Docs/issues/22045).


colcon sometimes doesn't exit after Ctrl+C on Windows

Ctrl+C on Windows does interrupt the build of the package being built but then the tool hangs and doesn't exit. Only option is to close the terminal.

Only option is to close the terminal.

Ctrl+Break should stop the running process and keep your terminal around.

Since even with the referenced merged PRs the invocation still sometimes doesn't exit I will keep this ticket open.

Assuming #30 and colcon/colcon-parallel-executor#6 have resolved this issue I am going ahead and close the ticket. Please feel free to comment on the closed issue if this is still a problem for you.


Implement core expires checking.

Working on adding more tests.

don't forget to breath @mattcollier =)

@dlongley I propose getting this merged into validate-allowed-action and then we can take a look at refactoring.


Add landscape.yaml validation workflow

This workflow validates that the landscape.yml file is valid on every pull request. It'd be great if you could update the repository's settings so that PRs cannot be merged unless this check passes. This way you'll ensure that the landscape.yml stays valid and the landscape build doesn't break.

@wrathwolf don't worry about the check not passing at the moment. This was expected because the landscape.yml file contains some errors at the moment. @cynthia-sg will submit a PR shortly to address them and this validation will help you keeping it valid going forward. As soon as Cynthia's PR is merged please mark this check as required 🙂


Fix/correct locale

Overview:
Currently all code is run in "default" locale, not the locale you load the console in. e.g you load the console for en_GB, but the code is executed in the "default" locale. This is not expected behaviour.
Reviewer:
BEFORE:

AFTER:

TEXT
Checklist:

I have tested each of the following, and they work as expected: ( required )

[x] Meets Contributing Guide Requirements
[x] Pulled in the Latest Code from the develop branch
[x] Works on a Desktop / Laptop Device
[x] Works on a Mobile Device
[x] npm test Does Not Generate Errors

@taurgis thanks for this, you are amazing 🥇

@taurgis thanks for this, you are amazing 🥇


update_checkout: fix scheme_map not reloaded

A one line follow-up fix for #62004. We re-read the config, but didn't check out correct branches after that, because scheme_map dictionary was loaded from the old config.

@swift-ci please smoke test


chore: update more deps, relax versions

this is just a follow-up on updating deps based on hints from renovate


Support for react-native > 0.60

#Feature Request
I would love to see this updated and supported for react 0.60 >
#Why it is needed
I have an older app who uses this library, and always thought it was great, but can't use it anymore when upgrading react.

There is now a PR for this with 2 small import changes

can you please guide me to fix this issue,
error: bundling failed: Error: Unable to resolve module NativeModules
RN Version : 0.61.5


Encode non UTF-8 before send

I have an problem with my project that is encoded in ISO-8859-1 if the exception message or the code snippet contains non UTF-8 the request fails as json_encode returns false on the data.
In this commit https://github.com/bugsnag/bugsnag-php/commit/23a34e1fadfe66bd2578deddb3553531e6c550d5 there was implmented a fix for this (same as mine) but it was rewritten in this commit https://github.com/bugsnag/bugsnag-php/commit/49e5d600014990255d1951fb4c14592d32b70b97 to only affect the metaData array.
What do you think?

Fixed in other PR


Trigger the action only on merged PR on main

I was thinking to execute the Publish workflow only when a push is done on the main branch, and a build workflow on the other branches/pull requests to check whether the container image builds or not. Let me add some code to your pull request, I will merge it and and also add the other workflow.


Fixed problem with Bubbles legend when a new analysis is applied

Related: https://github.com/CartoDB/cartodb/issues/11666.
Already described the problem in the ticket ^^^. In order to check it, just follow the steps described there.

Found an issue.
STR:

Create points map
Style size by value, and then color by value
Add subsample analysis, and apply
Style size by value, and then color by value
Remove analysis

The style is reset to the default yellow instead of persisting the state (layer style node cache stuff).
Another one:
STR:

Create points map
Style size by value, and then color by value
Refresh the map

The bubble legend will be yellow (it should be the primary color of the color ramp).
Finally, I managed to create a ghost node while playing with analysis editions. But I haven't been able to reproduce, and I tried several times. 😕 Maybe you guys have some clue? My approximate steps were:
STR:

Create points map
Style size by value, and then color by value
Add subsample analysis, and apply
Refresh
Apply some styles
Edit the analysis
Delete the analysis

As I said, not sure how it happened, so feel free to ignore. I just point this out in case you can think of something that might be missing in this process with the new code.

About case 1 and 3, this is not related with styles cache stuff or other problems, so we should not stop this release. About 2, taking a look....

@xavijam go home!
1, Happens in this PR but not production, so I think it can be related.
3, I thought it might be relates because it's ghost nodes, but cannot reproduce, so let's forget it.

Look at the code, it is near impossible that the code is related with the cache stuff @javitonino (it only touches bubble legend).
I've found a bug trying to replicate the second problem. Fixing it.

I feel problems have been fixed :crossed_fingers: .

Yeah, I know. I tried to replicate again today and I cannot, although it happened to me 3 or 4 times yesterday. There probably was something wrong somewhere else.

Btw, in Firefox I'm getting the following errors when adding an analysis on top of a layer with bubble legends:

It does not seem to be a problem, though. I don't know why it says XML 😕

Weird @javitonino, but in any case, if you have the chance, try with the last changes please 💋 .

Sure! Will do!

Please, @nobuti, take a look when you have a minute. In short:

Removed bindings from legend-bubble-definition-model, because now layer-manager takes care of that 💃 .
Changed tests.
That's all.

Ok, looking 🍏. Could not break it with several combinations of adding analysis, widgets and playing with legends. Rock solid!
I'll deploy after all tests pass.

Yay!, thanks both! 💋


Link Validation: Microsoft Docs links must not be localized

Updates the link validation to also prohibit pinning of Microsoft Docs links to localized versions

@greenie-msft @willtsai

Merge this after #1906

This PR is working as intended. Please don't merge yet! #1906 must be merged first.

This works now:

Thanks for this contribution @berndverst!


testing/api: Add test for filter values and 'filter_list' query

Add testsuite/filters that verifies that the filter shapes are correct and don't change if we make future changes to the filter code.
Along the way, add a new global getattribute query 'filter_list', that returns a semicolon-separated list of all the 2D filters it knows about.

No comments or objections for a week + only affects tests and can't break existing code = merge


Adjusting the scroll container listener to be the page content

ℹ This is the same fix as for release 1.8: https://github.com/dcos/dcos-ui/pull/1688

Before:

After:

retest this please


[Feature] README.md file update

Problem
README.md
Description
README.md file does not contain the steps required to setup the project locally on a personal work environment
Alternatives
This will help new contributors to be able to setup their environment with ease... This is especially for those who are new to open source
Additional context
Links to various sites that could help the contributor during setup phase
Implementation

[ x] I would be interested in implementing this feature.

Already raised #45, and i am working on this, you can look up to other issues.

@Biki-das okay thanks for the heads up


not an issue but a question

I'd like to have multiple containers I'd like to add a "search bar with jump to matches" to - what would be the best way to do that?

Please have a look into the examples on the website.


feat!: move API to typescript code generation

This will be a breaking change because some helper function name of resources get changed. But no change for the real APIs.
This library will be published as @google-cloud/dialogflow.

Thanks for the review @bcoe , @JustinBeckwith !
we changed the logic for resources pathTemplate, so only the name of the resources get changed, not the API names, such as for the Sesssion resource, now it calls projectSessionPathTemplate
      projectSessionPathTemplate: new gaxModule.PathTemplate(
        'projects/{project}/agent/sessions/{session}'
      ),

but in js session_client, it's called
     sessionPathTemplate: new gaxModule.PathTemplate(
        'projects/{project}/agent/sessions/{session}'
      ),

but your point totally makes sense, I will list all the resource names that being changed, to give users a better understanding. And at the same time, we list all the resources that defined by google.api.resource even if it's not referenced, that's why some clients have more resources, should I include these extra resources as breaking change as well?

Talked to Alex, so the resource only affects the helper function we generated like projectPath and users rarely use that, the real API is not changed at all. So I probably may not list all the helper function names [it's huge] but give a better explanation for the PR description, sorry for the confusion @bcoe

Added warning message for dialogflow of the name change: https://github.com/googleapis/nodejs-dialogflow/pull/526


add support for 12.2.0 and drop 9.x and 10.x

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi @isuruf @beckermr, what is the status of this PR (sorry conda newbie here), anything I can do to push it forward?
I'm failing to build scipy (as part of the build process of https://github.com/sagemath/sage from source via conda) on OSX ventura (v 13.1.0)
Here at some step of the build I see an error

@conda-forge-admin, rerender

That was fixed in https://github.com/conda-forge/gfortran_impl_osx-64-feedstock/pull/61
Please open a new issue with the details in the issue template.

That was fixed in #61 Please open a new issue with the details in the issue template.

Well I guess its a different issue to #61 if the changes from that PR are live on conda-forge and I still have the issue?
I hesitated to open a new issue as I figured it was essentially a duplicate of this PR, but here is #63 if thats what you prefer

@isuruf Where did the mega-arm-patch come from?

Ah, found it https://raw.githubusercontent.com/Homebrew/formula-patches/1d184289/gcc/gcc-12.2.0-arm.diff


Adding translation for gear up for success challenge

closes #4541
Not sure how you folks are translating "full stack". I left it in English so you can comment on that and then I can make the correction.

Thanks for the translation, I made minor suggestions that cold be applied after this PR is accepted.  Hope @bugron or @Itegram could merge it.

Closing this PR, I've merged in #5013. Thanks all for your excellent work.


Add grounding for major entity types using EXTRACT 2.0 API

This pull request implements grounding / entity linking for the major entity classes (Chemicals/Drugs, Disease/Disorder, Species/Living beings, and Proteins/Genes) using the EXTRACT 2.0 API. This is used in place of the grounding system we had previously, which only worked for protein/gene entities.
I tried to model the output format used by REACH as close as possible. Grounding adds a new field to each item in ents (xrefs) in the output JSON returned by Saber.annotate(). E.g.,
Without grounding
{
  "text": "The phosphorylation of Hdm2 by MK2 promotes the ubiquitination of p53.",
  "ents": [
    {
      "start": 23,
      "end": 27,
      "text": "Hdm2",
      "label": "PRGE"
    },
    {
      "start": 31,
      "end": 34,
      "text": "MK2",
      "label": "PRGE"
    },
    {
      "start": 66,
      "end": 69,
      "text": "p53",
      "label": "PRGE"
    }
  ]
}

With grounding
{
  "text": "The phosphorylation of Hdm2 by MK2 promotes the ubiquitination of p53.",
  "ents": [
    {
      "start": 23,
      "end": 27,
      "text": "Hdm2",
      "label": "PRGE",
      "xrefs": [
        {
          "namespace": "TODO",
          "id": "ENSP00000258149",
          "organism-id": "9606"
        },
        {
          "namespace": "TODO",
          "id": "ENSP00000410769",
          "organism-id": "9606"
        }
      ]
    },
    {
      "start": 31,
      "end": 34,
      "text": "MK2",
      "label": "PRGE",
      "xrefs": [
        {
          "namespace": "TODO",
          "id": "ENSP00000356070",
          "organism-id": "9606"
        },
        {
          "namespace": "TODO",
          "id": "ENSP00000433109",
          "organism-id": "9606"
        }
      ]
    },
    {
      "start": 66,
      "end": 69,
      "text": "p53",
      "label": "PRGE",
      "xrefs": [
        {
          "namespace": "TODO",
          "id": "ENSP00000269305",
          "organism-id": "9606"
        }
      ]
    }
  ]
}

Where namespace is the external resource the entity is grounded to andid is the unique identifier in that external resource. organism-id is unique to PRGE entities. Currently, this will default to reporting 9606. The EXTRACT API docs state that a feature is currently being developed that will allow for the automatic detection of organism-id for each protein/gene mention.

TODO

[ ] Figure out namespace field.
[ ] Lint the code.
[ ] Sanity check that I didn't break any existing features. Write more unit tests.

Pull Request Test Coverage Report for Build 311

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 299:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


Mosquitto mqtt broker on Rasberry Pi 2 connection issue

I just finish installing esp8266 tool-chain and try to get familiar with your esp_mqtt. so this is my very first program I compile and flash to the esp-07 module. the flashing was a success  but i having an issue connecting to my mosquitto mqtt broker running on rasberry pi 2. the following message constantly display in serial terminal. could you help take a look on my issue ?. BTW. i just install mosquitto on my ubantu with the same procedure as the one installed on rasberry pi. there is no issue at all to connect so I'm not sure what causing this.
TCP: Connect to ip  <IP_ADDRESS>:1880
TCP: Reconnect to: <IP_ADDRESS>:1880
MQTT: Connected to broker <IP_ADDRESS>:1880
MQTT: Sending, type: 1, id: 0000
TCP: Sent
TCP: data received 4 bytes
MQTT: Connected to <IP_ADDRESS>:1880
MQTT: Connected
MQTT: queue subscribe, topic"/mqtt/topic/0", id: 21
MQTT: queue subscribe, topic"/mqtt/topic/1", id: 22
MQTT: queue subscribe, topic"/mqtt/topic/2", id: 23
MQTT: queuing publish, length: 23, queue size(646/2048)
MQTT: queuing publish, length: 25, queue size(671/2048)
MQTT: queuing publish, length: 25, queue size(698/2048)
TCP: Disconnected callback
MQTT: Disconnected
Free memory

I did enable debug log in rpi and found that mosquitto was refusing connection from esp_mqtt. it sening connack with return code 5. then i guess it close the socket immediately after that. but i can connect to the rpi with mqtt spy with the same user and password. please advice how i can resolve this issue.
thanks in advance.

I have identify some differences between my mosquitto installation.
the one that install in my virtual machine under ubantu was mosquitto 1.4
on my rpi 2 installation install using standard apt-get install was mosquitto 1.35
so I try again to identify whether the issue still remain there or not by install a pi snappy ubuntu image and perform installation of mosquitto using snappy but I can not configure my mosquitto to be the same as my ubantu installation. so I take another route by downloading necessary liblary and deb package for mosquitto from whizzy debien repo then install it with dpkg -i then i can configure it but the problem still the same. i guress i need mosquitto 1.4 for testing but there is no rasberry pi 2 binary exis in any repo yet so I may need to go deeper again to do cross compiling mosquitto on my existing unbuntu. BTW. if you have any work around or solution on esp8266 end please update or post the solution here I'd very greatfull.

maybe you need to change
#define PROTOCOL_NAMEv31	/*MQTT version 3.1 compatible with Mosquitto v0.15*/

from user_config.h

I got it working now Thanks, for the PROTOCOL_NAME setting I did not change anything yet, just clone your git repo them make and flash to the module so I'm not sure what is the actual problem.
here is my solution.
I Download Rasbian Debian Wheezy fresh from  https://www.raspberrypi.org/downloads/ then create a boot sd for my raspberry pi 2 then.

update the pi to latest software
$ sudo su
apt-get update && apt-get upgrade

Install Development Environment on Pi 2
apt-get install build-essential

Download mosquitto 1.4 source tar file from http://www.eclipse.org/downloads/download.php?file=/mosquitto/source/mosquitto-1.4.1.tar.gz (iput it on  pi's home directory)
extract tar -xvzf   it should create a directory mosquitto-1.4.1
cd mosquitto-1.4.1
make

I got error during make cause by missing uuid.h  if you got error like me you need to install uuid-dev
apt-get install uuid-dev

make install

after that config mosquitto as it should be also if you have a script to start mosquitto pit it in /etc/init.d
That conclude my problem


Error: The package 'Microsoft.VisualStudio.Component.AzureDevOps.OfficeIntegration' was not recognized.

Hi team,
I'm moving this from here: https://github.com/MicrosoftDocs/visualstudio-docs.de-de/issues/64
The user reports an error in the documentation and module availability
@aisbergde commented 3 days ago — with docs.microsoft.com
When trying to install some components regarding to this list I get an error:
vs_community__818795694.1537480254.exe --layout D:\SQLServer_Setup_diverse\vslayout --add Microsoft.VisualStudio.Component.CoreEditor --add Microsoft.VisualStudio.Workload.Data --add Microsoft.VisualStudio.Workload.DataScience --add Microsoft.VisualStudio.Workload.Python --add Component.GitHub.VisualStudio --add Microsoft.Component.HelpViewer --add Microsoft.VisualStudio.Component.AzureDevOps.OfficeIntegration --add Microsoft.VisualStudio.Component.Git --includeRecommended --lang en-US
Great error message:
Visual Studio Setup Command Line Utility, version 1.18.1049.33485
Copyright (C) Microsoft Corporation. All rights reserved.
Download of 'https://aka.ms/vs/15/release/channel' succeeded using engine 'WebClient'
Download of 'https://download.visualstudio.microsoft.com/download/pr/82e3dcda-e8a0-44e4-8860-eb93a12d4e80/61c5d0ed852e311c8fd6a62627fcb326da6aa79028b40ae25ee062da3c33791b/VisualStudio.vsman' succeeded using engine 'WebClient'
Catalog load operation correlation: {"id":"e3e60385-1915-4031-8ea6-a6e1717ea8dc"}
Layout operation correlation: {"id":"d59730ed-a56e-4cb6-abf9-3ba824cd7af5"}
Planning 'Layout' operation
Error: The package 'Microsoft.VisualStudio.Component.AzureDevOps.OfficeIntegration' was not recognized.
Error: Failed to plan for layout.
Error: Setup completed with errors.
Error: The package 'Microsoft.VisualStudio.Component.AzureDevOps.OfficeIntegration' was not recognized.
Press any key to continue ...

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

ID: 4891ebc9-fdea-c376-94f6-17295ca275d7
Version Independent ID: ccc61918-cc18-a7ff-cc6c-8659d6c9c78a
Content: Visual Studio Community workload and component IDs
Content Source: docs/install/workload-component-id-vs-community.md
Product: visual-studio-windows
Technology: vs-installation
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@CeciAc I took a look at this yesterday and I believe the problem is that the customer tried to run a Visual Studio Community 2017 bootstrapper (vs_community.exe) against a Visual Studio Community 2019 manifest. The giveaway here is when they report using "https://aka.ms/vs/15/release/channel". The version "15" is associated with Visual Studio 2017, where the version "16" is associated with the Visual Studio 2019 version.
If you check both the en-us copy and the de-de copy of the Workload and Component IDs page for Visual Studio Community 2017, you see that the "Microsoft.VisualStudio.Component.AzureDevOps.OfficeIntegration" component is not listed on either of them.
Please if you would, advise the customer of this?

I used the bootstrapper from the link in the instruction: vs_community__818795694.1537480254.exe
And finally I prepared a VS 2019 installation.
If this is a bootstrapper for VS 2017 how a user should know? And if this is the wrong bootstrapper: why this link is included in the instruction but not a link to the right version? Then you should correct the link in the instruction. But I think it was the VS 2019 bootstrapper.
I went step by step through the instructions and got an error which I reported. It should be easy possible to reproduce the error following the instructions.

@aisbergde Our concern via this venue is that our documentation is correct. I've verified that the download links on our en-us pages point to the right versions. However, I will make some adjustments to the direct download links for Visual Studio 2017 so that there are visual cues as to what version is being downloaded, which should prevent the possibility of someone accidentally downloading a bootstrapper for the previous version of Visual Studio.
As for the error you've run up against: I'll check with the engineering team as to verify that the Microsoft.VisualStudio.Component.AzureDevOps.OfficeIntegration component is still viable for Visual Studio 2019.
And, if you are looking to have your scenario tested and possibly repro'd, the best place to do that is by using the Report a Problem tool. When you do so, your report becomes part of the work items that are listed in the in the Visual Studio Developer Community, which allows you to engage directly with the engineering team while they address and fix the problem. (As well, you can provide the engineering team with the diagnostic information they need to do so.)

@aisbergde The engineering team looked at this issue and here is their feedback:

The Microsoft.VisualStudio.Component.AzureDevOps.OfficeIntegration component is still viable for Visual Studio 2019, so no updates need to be made to the Visual Studio Community component directory page.

The setup bootstrapper that generated the error message is indeed for Visual Studio 2017. Our engineer identified the "1.18" in the following line of the message as belonging specifically to the Visual Studio 2017 version 15.9 installer.
Visual Studio Setup Command Line Utility, version 1.18.1049.33485

Because I am not sure where you downloaded your copy of the setup bootstrapper, and because I've verified that all our download links are correct in the en-us set of installation content, I'd suggest deleting any vs_community__818795694.1537480254.exe file that you have and then downloading it again from this page: https://visualstudio.microsoft.com/downloads/. (Also, to make certain that you don't accidentally pick up a copy of the bootstrapper from a previous download, you might consider trimming __818795694.1537480254 from the file name so that it reads simply as vs_community.exe and then revising your command-line script accordingly.)
Hope this helps,
~ Terry


Error while installing 'Flutter' extension. Please check the log for more details.

Type: Bug
So I enabled experimental settings profiles feature and now I am trying to install flutter extension in new profile but it gives this error. Also one more extension is giving similar error! It says in logs something like this:
Unable to resolve nonexistent file 'c:\Users\Administrator.vscode\extensions\johnpapa.winteriscoming-1.4.4'
Winteriscoming was a theme but it is not even installed in current profile!
I am not sure why I am unable to install certain extensions from marketplace. I don't want to do manually!
P.S I get the same error in my default profile too! I am not sure if it is related to settings profile or not! But I have never encountered this before!
Here are the logs:
`
[2022-10-25 14:09:58.041] [renderer1] [error] ["Error: Unable to resolve nonexistent file 'c:\Users\Administrator\.vscode\extensions\johnpapa.winteriscoming-1.4.4'","    at a.resolve (vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:36:18746)","    at async J.toLocalExtension (vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:189254)","    at async Promise.all (index 205)","    at async G.doRun (vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:193221)"]
[2022-10-25 14:09:58.093] [renderer1] [error] Unable to resolve nonexistent file 'c:\Users\Administrator.vscode\extensions\johnpapa.winteriscoming-1.4.4': Error: Unable to resolve nonexistent file 'c:\Users\Administrator.vscode\extensions\johnpapa.winteriscoming-1.4.4'
at a.resolve (vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:36:18746)
at async J.toLocalExtension (vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:189254)
at async Promise.all (index 205)
at async G.doRun (vscode-file://vscode-app/c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:193221)
`
VS Code version: Code 1.72.2 (d045a5eda657f4d7b676dedbfa7aab8207f8a075, 2022-10-12T22:15:18.074Z)
OS version: Windows_NT x64 10.0.19043
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz (4 x 2594)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
11.85GB (3.39GB free)

Process Argv
--crash-reporter-id a0fbb6bd-fff4-43a7-8ec6-e229505b6ad2 --crash-reporter-id a0fbb6bd-fff4-43a7-8ec6-e229505b6ad2

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

flutter-snippets
ale
3.0.0

flutter-stylizer
gml
0.1.16

vscode-flutter-files
gor
4.4.2

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
vsccc:30566497
pyindex848:30577860
nodejswelcome1cf:30587006
fc301958:30595537

Can you please share the Shared Process Log - F1 > Open View... > Log (Shared) while you reproduce this issue?

It is working now Thanks!


IgnoreAndPopulate and DataContract.IsRequired mismatch between serialization and deserialization

Source/destination types
    [DataContract]
    class Person
    {
        [DataMember(Order = 1, IsRequired = true)]
        public int  Id {  get; set; }

        [DataMember(Order = 2)]
        public string FirstName {  get; set; }

        [DataMember(Order = 3)]
        public string LastName { get; set; }
    }

Serialized JSON
When serializing a Person created with default constructor, and since I use DefaultValueHandling.IgnoreAndPopulate, all properties are ignored:
 { }

Expected behavior
I expect that since Id is required, it will also be populated and the serialized JSON should be:
{
   "id" : 0
}

and than, when deserializing, no error will be produced
Actual behavior
When deserializing, an exception is thrown: Required property 'Id' not found in JSON. Path '', line 1, position 2.
Steps to reproduce
 var serializer = new JsonSerializer();
 serializer.DefaultValueHandling = DefaultValueHandling.IgnoreAndPopulate;

 using var writer = new StringWriter();
 using var jwriter = new JsonTextWriter(writer);
 serializer.Serialize(jwriter, new Person());
 string text = writer.ToString();

 using var reader = new StringReader(text);
 using var jreader = new JsonTextReader(reader);
 var person = serializer.Deserialize<Person>(jreader);

Any update on this? I am also running into this issue, though somehow only for .net standard (am using net6.0) and not in .net FW


PEP8 states that package names should be one word all lower case

https://www.python.org/dev/peps/pep-0008/#package-and-module-names
ECS_demo should probably be ecsdemo

wow @dacb you would raise an issue that forces me to recursively grep through the whole package and rename everything and hope it all still works at the end of the day!

whoops tagged the commit with wrong issue number but #1 is done, did, fixed! Thanks @dacb !

What? @nealde says that never happens.

It only breaks everything like 90% of the time...

Then fixes, so OK, right?
With ag installed, I did this in bash, and yes, I used perl to fix all references:
function agr { ag -0 -l "$1" | xargs -0 perl -pi.bak -e "s/$1/$2/g"; }
agr EISfit eisfit


Error 0xc0000039 Object Path Component was not a directory object

I'm getting this error when trying to run System Informer elevated.

Note that while it is an "Unable to load kernel driver" error, it is not the typical "not yet supported" error.
I found here:
https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55
that error 0xC0000039, STATUS_OBJECT_PATH_INVALID, "The object path component was not a directory object." is an NTSTATUS value. But that does not really help my non-developer mind. A search turns up a few results with this error but most seem to be bluetooth device related.
Can anybody shed a little light on this for me?

@kiumut thanks for reaching out. This could be a number of things. I'd like to have you send me a trace log of the issue reproducing. Could you do the following:

open an elevated command prompt
execute: logman create trace ksi -p {F64B58A2-8214-4037-8C7D-B96CE6098F3D} 0xffffffff 0xff -bs 64 -nb 16 128 -o "kph.etl" -v mmddhhmm -ow
execute: logman start ksi
reproduce the issue
execute: logman stop ksi
execute: logman delete -n ksi
collect the kph_nnnnnnnn.etl from disk
attach the .etl file here or email it to me

With this trace log I should be able to tell where in the driver it is failing or if it's not getting that far that rules out a number of possibilities.

Thanks for the quick reply.
I did not get a chance to make an .etl file as I managed to eliminate the error.
I am running SI as the default Task Manager and am launching it via right-click in a blank taskbar area (with ExplorerPatcher). Not sure if any of that is related, but I also got the error when launching SI normally from the Start menu.
I re-downloaded a fresh copy of the latest canary portable (systeminformer-3.1.24244-canary-bin) and ran it. I enabled the kernel mode driver in the options and elevated SI. I received no error. Then I closed that instance of it and opened my regular one, clicked the reset button in the options window and enabled only these settings

and that worked too.
Unfortunately, I did not make note of which options I had set previously so I cannot say which of these might be changed or which might be the same. I also had about 12 excluded device notifications in my old configuration. So it seems that the error might be as simple as a particular setting or a combination of customizations I had made. I will pay attention to any future changes I might make to SI settings in case that error pops up again. But for now it's working properly with the "++ (Administrator)" indication.

Likely one of the Ksi... settings caused the conflict. Resetting them likely resolved it.


enhancement: optimize GroupExpressionMatching

Proposed changes
Issue Number: close #xxx

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

run buildall

run buildall

run buildall


Can we control the Playback Speed in AVPlayer?

I amusing AVPlayer to play videos in my app. Is it possible to implement the playback speed for a video. For example: 1x, 2x, 3x etc... as a speed limit for video playback?

No idea because I never tried to implement fast speed, but here is the stack overflow link that may be useful for you: http://stackoverflow.com/questions/2350657/avaudioplayer-how-to-change-the-playback-speed-of-audio

Thanks!! I will try using that!


issues in ibm.com react support for dir="rtl" in header and footer

https://chiefdataoffice.slack.com/archives/C2PLX8GQ6/p1600278573123800
Please see the conversation in slack channel

testing URL:  (https://proxy1.marketplace-test.ibmcloud.com/profile/dataprivacypreferences/welcome/ae-ar)

Jeff has replicated the bug on the NextJS test environment.  The live Search page does not have the same problem in the Masthead.
https://www.ibm.com/search?lang=ar&cc=sa

@jeffchew Wrote documentation on how to properly configure RTL ( #4157 ). When RTL is active after following the configuration guide, this bug does not occur -- the search bar is properly aligned to the left.

This is a dup of issue (#4026).  Consolidating the comments and priority discussed in the Oct 13 Adopter issue review meeting here.
Oct 6, 2020 comments:  There are 2 privacy teams.  This bug was opened by the Privacy Preferences team.
This page created by the Privacy Portal team appears to be working.  https://www.ibm.com/privacy/portal/ae-ar
Tool that that RTL language sites need to use.  https://rtlcss.com/
Jeff will create an RTL NextJS environment to try to replicate the reported issue.
NextJS environment with RTL enabled:  http://ibmdotcom-nextjs-rtl.mybluemix.net/
Jeff also created documentation to guide adopters on the proper implementation steps.
https://ibmdotcom-react-canary.mybluemix.net/?path=/docs/overview-enable-right-to-left-rtl--page
Jeff will create additional documentation for kitchen sink implementation
Oct 13, 2020 comment:  Next step to provide an RTL version of the styles kitchen sink and provide support for the RTL styles in the CCS artifact.

@IgnacioBecerra The duplicate issue (#4026) was discussed in our adopter issues review meeting.  See the October 13, 2020 comment above.  There is some development work to be done to support the RTL version of the styles kitchen sink.


Fix memory allocation in Python and improve the documentation

Related to https://github.com/stack-of-tasks/eigenpy/issues/156

I did not handle all the doc yet. This will be done in future work.


global: URL key as path

Changes the 'key' argument type in URL pattern to path.

Signed-off-by: Krzysztof Nowak<EMAIL_ADDRESS>

Coverage remained the same at 90.361% when pulling 4bd76d526118fac9f725e44cfce61141f5338c9e on krzysztof:master into 286cda7b198f1423831ddff43510a9c8607e47e6 on inveniosoftware:master.


How to support dbeaver for a new db? Tibero

Hey guys, I've been using DBeaver for a while and I really like it, the community is amazing and the developments it has had are fantastic.
I use it for everything, oracle, mysql, sql server ... but recently the company I work with decided to get a new db to replace oracle, this db is called Tibero I have used dbeaver with odbc to connect to this database.
I wonder how it would work so that dbeaver could support this Tibero.
Thank you so much for your attention.

If there is a JDBC driver for Tibero then you could try to add it by this instruction: https://github.com/dbeaver/dbeaver/wiki/Database-drivers

If there is a JDBC driver for Tibero then you could try to add it by this instruction: https://github.com/dbeaver/dbeaver/wiki/Database-drivers

Yes tibero has JDBC drive and works using the "Generic driver", but this generic has no sequences and some other features that you have when using the correct drive in dbeaver such as oracle.
As I said the way I've been using it is generic as if it were an ODBC driver

I see. Well, for extra functions (like sequences) we need to create a new extension.
Unfortunately I'm not familiar with Tibero and we don't have any test Tibero server to validate our code.
You could try to contribute the extension (it is quite trivial for simple improvements like sequences, view/procedure source, etc). You can check how other similar extensions were implemented (e.g. H2).
Otherwise I can't say when we'll implement this. In any case we'll need more requests and assistance with Tibero installation.

Also interested in this topic. In case you need a Tibero Server on the Cloud, I can provide you one. Thanks!

I've managed to create separate driver for Tibero and establish a connection but found some nuances.
There is a table with column A detected NUMBER by dbeaver. In Query column A/3 is returned as NUMBER(38,0) which does inproper round of returned value. Can this behavior be tuned in driver properties?

As for assistance for installing tibero - tmaxsoft (Tibero DB) does provide free trial vm with Tibero Database https://www.tmaxsoft.com/tibero-vm-download/. Hope that can move adoption Dbeaver for Tibero easier.


Add support for container tools package

We should support using https://docs.microsoft.com/en-us/visualstudio/containers/container-msbuild-properties?view=vs-2019 to build containers for deployment and local run

Related to #240 (we may be able to close that one)

Not sure if related or not, but I'd like to see a tye deploy --containers-only or similar, where the project container images are built, tagged & pushed to the current container registry, but not deployed to k8s.

Not related but good idea 👍

we do have tye build which will do the building and tagging. I'd be open to adding tye push  or tye build --push

oh, I did not see that, but also decided that I need the feature now, so I'll write it today :)

@davidfowl @jkotalik - quick discussion on naming for command?
I kinda prefer tye push to tye build --push. I know we don't have to have a ridiculous amount of commands, but I also think we'd hit the natural limit for build/deploy with generate, build, push, deploy.

For anyone watching this, we've added tye push as a top level command. Keep this issue around because that wasn't the original purpose.


doc: release-notes-3.6: Add note on GRLIB SPIMCTRL driver

The GRLIB SPIMCTRL SPI device driver was added in commit e13d4a14df18a9e40b50cfbbde66dec38e6ac844.

@tbr-tt I regret to inform that this entry didn't make it into the v3.6.0 release notes as the review comment wasn't addressed in time of the release.


Add Plutus Crowdfunding E2E Example

Issue Number
ADP-1233

I am currently unable to build against plutus-ledger-api and plutus-contract.
nix-build -A checks:
Error:
    The following packages are broken because other packages they depend on are missing. These broken packages must be rebuilt before they can be used.
installed package ghc-8.10.7 is broken due to missing package directory-<IP_ADDRESS>, process-<IP_ADDRESS>, terminfo-<IP_ADDRESS>, time-1.9.3, unix-<IP_ADDRESS>
installed package ghc-boot-8.10.7 is broken due to missing package directory-<IP_ADDRESS>installed package ghci-8.10.7 is broken due to missing package unix-<IP_ADDRESS>
installed package hpc-<IP_ADDRESS> is broken due to missing package directory-<IP_ADDRESS>, time-1.9.3

builder for '/nix/store/gxzlm3s0mgbwklb25j4n4i56kr3fa2b3-plutus-tx-plugin-lib-plutus-tx-plugin-<IP_ADDRESS>.drv' failed with exit code 1
cannot build derivation '/nix/store/z5kzb2w5fnaadxmhphpx2zkpykib383v-plutus-contract-lib-plutus-contract-<IP_ADDRESS>-config.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/qwd149s947v6c6dbsk56rasv6l2r9sdr-plutus-contract-lib-plutus-contract-<IP_ADDRESS>.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/lkdm0lnmz1ly98s1bw115x9c5c2lglw4-cardano-wallet-core-integration-lib-cardano-wallet-core-integration-2021.12.15-config.drv': 1 dependencies couldn't be built

So the plutus-tx-plugin fails to build, triggering the rest to fail.

So for some reproduction information...
I can build all plutus-apps projects with a nix-build. But when I enter a nix-shell I can't find any of the plutus-apps libraries.
Here is a table I made:

package
relies on sublib?
nix-build?
available in shell?

freer-extras
no
✅
✅

playground-common
plutus-ledger -> cardano-api:gen
✅
❌

plutus-chain-index
plutus-ledger -> cardano-api:gen
✅
❌

plutus-chain-index-core
plutus-ledger -> cardano-api:gen
✅
❌

plutus-contract
plutus-ledger -> cardano-api:gen
✅
❌

plutus-ledger
cardano-api:gen
✅
❌

plutus-ledger-constraints
plutus-ledger -> cardano-api:gen
✅
❌

plutus-pab
plutus-ledger -> cardano-api:gen
✅
❌

plutus-playground-server
plutus-ledger -> cardano-api:gen
✅
❌

plutus-use-cases
plutus-ledger -> cardano-api:gen
✅
❌

The nix-build command used for testing is:
nix-build -A private.project.hsPkgs.plutus-use-cases

The commands used to determine availability in a shell are:
nix-shell
ghc-pkg list | grep plutus-use-cases


Add auto_updates to adobe-photoshop-lightroom, crashplan, yourkit-java-profiler

These casks that were reported as outdated despite being automatically kept up-to-date with built-in updaters.

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Additionally, if adding a new cask:

[ ] Named the cask according to the token reference.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no open pull requests for the same cask.
[ ] Checked the cask was not already refused in closed issues.
[ ] Checked the cask is submitted to the correct repo.

Thank you. In the future, please submit separate pull requests for each cask, as more often than not this type of pull request brings problems with one or more of them, and it halts the inclusion of the other ones. These are fairly simple, so they’re fine in a single PR, but they should still be separate commits.

Thank you for the contribution. It was merged directly as 55b6f2b46400a8dc52dd552b68ccc08bd7716f98. Your contribution is still credited to you.


security: run the crash collector as ceph user

The crash collector does not have the command line arguments to run as ceph user id 167, so we set the security context to run as the ceph user in the main crash collector container.
Signed-off-by: Travis Nielsen<EMAIL_ADDRESS>(cherry picked from commit df6d7af355440eab3fae7eea970f9196b5de125f)

Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide).
[ ] Skip Tests for Docs: If this is only a documentation change, add the label skip-ci on the PR.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] Pending release notes updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

cc @travisn @agarwal-mudit

Linters/pylint ci error is fixed in upstream versions

Linters/pylint ci error is fixed in upstream versions

Please also cherry-pick the fix into this PR for rook#11606 so we can get a clean linter.

done

@travisn ready to go in?

What BZ is this for? We need Bug *: in the PR title

What BZ is this for? We need Bug *: in the PR title

sorry, Travis I missed the ping.

/approve
/lgtm


Calendar block manual refresh inconsistency

Description of the bug
When you have a calendar block with a manual refresh and the records are shown on the calendar when they are created (created_at), and you have couple records and when you delete one of the records and you refresh the calendar block, the record is still shown. The record will go away just if you reload the whole page.
Reproduction steps

Create a calendar block with manual refresh that has records enabled in the event source
Create couple records and notice that they are shown on the record on the date that they were created (if that is the configuration in the event source)
Delete one of the records
Press on the manual refresh on the calendar block and notice that even though the record is deleted, it is still shown on the calendar block
Check the video for more context.

Expected behavior
The calendar block should also refresh when triggered a manual refresh as in other page blocks.
Video
https://user-images.githubusercontent.com/53232926/214026358-af714752-f91c-4d8c-a933-cb9a7d1652db.webm
Version branch
Branch: 2023.3.x

Retested this and confirming that this now works as expected. The only thing now left is the CL entry.

Changelog Entry
Fixed
What was fixed
Calendar block manual refresh was not updating events.


Could not find com.google.android.exoplayer:extension-rtmp:2.12.1.

When I add video_360: ^0.0.3, and run the App, i have the next Issues:
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not find com.google.android.exoplayer:extension-rtmp:2.12.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/google/android/exoplayer/extension-rtmp/2.12.1/extension-rtmp-2.12.1.pom
- https://repo.maven.apache.org/maven2/com/google/android/exoplayer/extension-rtmp/2.12.1/extension-rtmp-2.12.1.pom
- https://storage.googleapis.com/download.flutter.io/com/google/android/exoplayer/extension-rtmp/2.12.1/extension-rtmp-2.12.1.pom
Required by:
project :app > project :video_360
Could not find com.google.android.exoplayer:extension-mediasession:2.12.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/google/android/exoplayer/extension-mediasession/2.12.1/extension-mediasession-2.12.1.pom
- https://repo.maven.apache.org/maven2/com/google/android/exoplayer/extension-mediasession/2.12.1/extension-mediasession-2.12.1.pom
- https://storage.googleapis.com/download.flutter.io/com/google/android/exoplayer/extension-mediasession/2.12.1/extension-mediasession-2.12.1.pom
Required by:
project :app > project :video_360

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 6s
Exception: Gradle task assembleDebug failed with exit code 1

I experienced the same problem this morning:
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:mergeDebugAssets'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not find com.google.android.exoplayer:exoplayer:2.12.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/google/android/exoplayer/exoplayer/2.12.1/exoplayer-2.12.1.pom
- https://repo.maven.apache.org/maven2/com/google/android/exoplayer/exoplayer/2.12.1/exoplayer-2.12.1.pom
- https://storage.googleapis.com/download.flutter.io/com/google/android/exoplayer/exoplayer/2.12.1/exoplayer-2.12.1.pom
Required by:
project :app > project :video_360
Could not find com.google.android.exoplayer:extension-rtmp:2.12.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/google/android/exoplayer/extension-rtmp/2.12.1/extension-rtmp-2.12.1.pom
- https://repo.maven.apache.org/maven2/com/google/android/exoplayer/extension-rtmp/2.12.1/extension-rtmp-2.12.1.pom
- https://storage.googleapis.com/download.flutter.io/com/google/android/exoplayer/extension-rtmp/2.12.1/extension-rtmp-2.12.1.pom
Required by:
project :app > project :video_360
Could not find com.google.android.exoplayer:extension-mediasession:2.12.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/google/android/exoplayer/extension-mediasession/2.12.1/extension-mediasession-2.12.1.pom
- https://repo.maven.apache.org/maven2/com/google/android/exoplayer/extension-mediasession/2.12.1/extension-mediasession-2.12.1.pom
- https://storage.googleapis.com/download.flutter.io/com/google/android/exoplayer/extension-mediasession/2.12.1/extension-mediasession-2.12.1.pom
Required by:
project :app > project :video_360

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 40s
Exception: Gradle task assembleDebug failed with exit code 1


Issue with depNotify.sh

Hello,
I created a launchagent to kick off the depNotify.sh on login and it does launch it, the problem is, whether the test flag is true or false, it runs through and doesn't actually trigger the policies. Can you review my script and advise on what I did wrong? I barely modified anything.
I have the shell script saved on a web server and i have it downloaded to the computer via a curl command script in a policy so it can be modified on the fly without the need to constantly recreate a package. I am chmoding it 777. Any advice would really help as it worked once and then stopped working on all the machines ive tested on. Machines are running OEM 10.13.6.
depNotify.sh.zip

👋 @Hugonauts! I took a look at your script and you are right not many changes. I would expect the script not to run the policies in TESTING_MODE as that is the expected behavior. depNotify.sh script looks good and I tested the policy names with special characters so that shouldn't be a problem.
On the computer you having issues on. Can you try the following command and post the behavior?
sudo /usr/local/bin/jamf policy -event audacity
If you get a warning or error about not finding the Jamf verb check to make sure that the jamf binary is in /usr/local/bin/jamf. If it is not there, then you will need to edit line 116 where it says   JAMF_BINARY="/usr/local/bin/jamf" or upgrade Jamf Pro to a newer version.

Thank you, i will check first thing tomorrow once i'm back in the office. we're on jamf pro version 10.8. Now I haven't chowned it root:wheel, I'm also going to test that, is that something that might cause a problem (if it's not chowned root:wheel?)

@Hugonauts also try the 1.2.0 version that was released today. I moved from calling the binary within the app to just calling the app. Some folks in Slack said that the older method had some issues.
Jamf Pro 10.8 should have the binary in the proper place for the script using macOS 10.13. I believe, when SIP was added, that we had to move the binary and made some changes there.

Also, Trying it on Mojave now. No Dice. Experiencing the same thing..

So I ended up putting into a script in my jamf server and it is working now =/
Thank you for your help haha~!

@Hugonauts if you keep trying things with LaunchD, check out https://yearofthegeek.net/2018/05/updating-our-depnotify-process/ @jmahlman did a session at JNUC about how he uses that method.

how to fix Recalculating Spines. Just before weeks, it was working fine and showing the enrollment process but now getting Recalculating Spines


fix(docs): update zeit now deployment process considering v2

Now is currently on version 2, and it use that version by default when someone want to make a deploy, then it let us two choices:

A) Maintain current docs about v1 deployment but set version on example JSON.
B) Update docs considering the the advent of v2 (11/2018)

I choose option B, then i made the changes and just commit it.
Before

After

Reasons to try to contribute

Docs need to be always updated :)

Refs
ZEIT - Now about Vue.js deployment (v2)
Sorry my english, only a Brazilian servant.

Possible duplicate with #3560

Possible duplicate with #3560

To work right must exists a "now-build" script on package.json #3560 don't have this warn/instruction.

I think you are right to use the option B as I see no reason not to get the advantage of now 2 with a vue project

Now CLI has just reached version 14.2.0 and the aliasing commands has changed
now build and give a default alias
now --target production build and give alias from the config
more information at https://zeit.co/blog/automatic-aliasing

Thank you for working on this! Unfortunately, need to close the PR in favor of https://github.com/vuejs/vue-cli/pull/4232


Research Plan

We're done with the assignment

Done
https://docs.google.com/document/d/1moGijtKNxIfqM5Dhmeg0A0Wz6FrocRtin1Ipr3qVhCs/edit?usp=drivesdk

Thank you Abukunolu


x5t query parameter description misleading

I believe there is an extra "thumbprint" in the following statement that describes the x5t query parameter:
"Base64-encoded SHA-1 thumbprint of the X.509 certificate thumbprint".
It is more clear as:
"Base64-encoded SHA-1 thumbprint of the X.509 certificate."
As making a thumbprint of a thumbprint is not what it is happening.

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

ID: 7e44b783-3ca5-6b6a-1f33-d7a107b8f8e0
Version Independent ID: aa2bb5fd-bd0d-830c-84c7-0525657b6d4f
Content: Microsoft identity platform certificate credentials - Microsoft Entra
Content Source: articles/active-directory/develop/active-directory-certificate-credentials.md
Service: active-directory
Sub-service: develop
GitHub Login: @nickludwig
Microsoft Alias: ludwignick

@brcolow
Thanks for your feedback! We will investigate and update as appropriate.

@brcolow
Thank you for pointing this out! I've created a PR to update the documentation and it's currently waiting for the author to review and sign off.

I will now close out this issue. Please allow some time for the author to review and the changes to reflect.
Thank you for your time and patience!


Update jsoniter-scala-core, ... to 2.13.14

Updates

com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core
com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros

from 2.13.12 to 2.13.14.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.plokhotnyuk.jsoniter-scala" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequest = { frequency = "@monthly" },
  dependency = { groupId = "com.github.plokhotnyuk.jsoniter-scala" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #277.


Close execute anonymous immediately after executing piped command

Is your feature request related to a problem? Please describe.
I find it quite useful to use these quick apex snippets to clear out database between tests, but don't want to create apex files for them.
echo "delete [select id from lead limit 2000];" | sfdx force:apex:execute

If Apex executes in about 5 seconds, the actual shell command takes another ~55 seconds to complete (I think apex times out). Perhaps there can be a flag added that terminates command immediately?

This has been fixed at some point


[Bug]: Liked models not showing correctly when on the liked models page

What happened?
The liked models collection page not showing the models correctly, instead it shows a bunch of other models that are not liked by me.

Steps to reproduce the problem

Click the profile icon
Choose "Liked Models"

What should have happened?
It should shows the correct liked models instead
What platforms do you use to access the site?
No response
What browsers do you use to access the site?
No response
Additional information, context and logs
No response

Actually still happening, taking a deeper look

@linjunshi Fix is live, sorry for the inconvenience


Side menu no longer highlights selected page

The side menu no longer highlights and shows the selected page. It used to do this, imo this feature is critical.
Is there a new way to enable it or is it just gone or broken?
Examples:

Docs.page

FlexColorScheme

Looks like it's broken on domain based docs, will fix tomorrow 👍

Fixed this, there's just one small issue left with "index" pages not showing - will investigate!

Yes was about to say the same, works again, except for the index page.


Config file in deployment and upload

https://kubernetes.io/docs/tasks/manage-kubernetes-objects/declarative-config/

0.9.1