Explain use case

Hey, nice project!
I am new to the Golang profiling world.
I was unsure what was the difference between standard pprof and autopprof.
After trying your example I think I understand the advantages of your project:

autopprof allows you to manually start the profiling at any arbitrary moment and for any specified duration.
As opposed to pprof which starts at the beginning of the program and can only be stopped manually (i.e. SIGINT) or when the program ends.

Did I get that right?
Your tool is very useful for newcomers, I think adding an explanation of the advantages of autopprof in the README would be helpful.

Closed via https://github.com/rakyll/autopprof/commit/31be2b066678643f362f953314a50f86f6d2b90f.


board full of water exceeds 100% cpu

as of writing, having nothing but water on the board (and block surrounding the board, to keep it from draining out) causes cpu to sit around 191%
this doesn't seem to be strictly linear; it remains around 99% cpu if all but one row are full of water, and then instantly shoots up by almost 100%. it might not be necessary to explain why this happens, but at the very least we should try to save some per-atom cycles if we can manage it. since the settings screen is inaccessible as long as the game is running over 100%, it's vitally important to get sub-100% some way or another
nothing else is as expensive as water, so if water can be made less expensive at the expense of something else then that could work

inlining the logic that was in bump, per 849a36843e5c85bca7ce1e9228b3abb93194faf3, seems to have brought it back within acceptable range

reopening because i goofed it up again

the culprit is 166f9b5b0f007e09e6f61f0e7cca707fd1a72771

specifically it's here. despite the fact that water and oil were "handled" earlier in the block, they both only succeed in conjunction with something, so if that conjunction misses, then they both get to be asked three times in a row if they're a type of fire. this makes both water and oil exceed 100% cpu

resolving #10 successfully brought performance back under control


showTodayButton with maxDate today date doesn't work

I have used moment() for maxDate but showTodayButton doesn't work
https://jsfiddle.net/Lodecesa/6nps786f/5/
You can try to use moment("today_string_format") in this code
https://jsfiddle.net/Lodecesa/6nps786f/6/
but the showTodayButton still doesn't work

Take a look at my issue: I think it's the same problem
https://github.com/Eonasdan/bootstrap-datetimepicker/issues/995

It's possible.
Thanks.

https://github.com/Eonasdan/bootstrap-datetimepicker/issues/995#issuecomment-108388511

closing in favor of #995


Hyprland/workspaces improvements and further development

I'm creating this issue so we can keep track of further development for the newly implemented hyprland/workspaces module (by @Anakael in https://github.com/Alexays/Waybar/pull/2264)
Here are some features I would personally like to see:

[ ] Urgent class
[x] Focused class
[ ] Option to only show active workspaces
[x] Persistent workspaces (+persistent css class)
[x] Multi-monitor: option to disable showing all workspaces on every output
[x] on-click action
[x] on-scroll action

Active (focused) class is already implemented.

Wiki is updated:
https://github.com/Alexays/Waybar/wiki/Module:-Hyprland
(Also fixed wrong class name in https://github.com/Alexays/Waybar/wiki/Module:-Workspaces)

Hi,
It seems the icons for the workspaces specified in the configuration only work if they’re specified for a workspace ID, not its name.

For me, multi-monitor displaying does not work. All the workspaces are shown on both bars in my dual monitor setup. Names also do not work, with Waybar claiming that the argument {name} does not exist.
I can open up a separate issue for this, if it sounds interesting.

That’s not me for the unseen ^^
I changed my configuration to use IDs instead of names, it works fine now. I think.

@zjeffer I tried many different configurations and the one you presented is one of those I tried. None of the options seem to do anything, except format.
    "hyprland/workspaces": {
        "format": "{id}",
        "all-outputs": false,
        "persistent_workspaces": {
                "*": 5
            }
    },

The error in question is this, if you set "format": "{name}":
[2023-08-11 08:54:32.006] [error] hyprland/workspaces: argument not found
[2023-08-11 08:54:32.121] [error] hyprland/workspaces: argument not found

It is definitely that element, because if I set "format": "{id}" or "format": "{}" then it does not show that error. No other errors are present either.

What do you mean by "unseen workspace"?

I should have said "not visible" instead. If we have three workspaces 1, 2, and 3:

1 is visible on left monitor
2 is visible on right monitor
3 is not visible, whether assigned to left or right monitor
If I switch between 1 and 2 in Hyprland, then the active workspace in Waybar is always shown as being either 1 or 2, regardless of which workspace is actually active in Hyprland.
If I switch to 3 in Hyprland, then the active workspace will correctly switch to 3 in Waybar, as expected.

Hope that was clear enough.

That's so strange, I don't have any of those issues.
Here's a video of me moving my mouse between two of my monitors:
https://github.com/Alexays/Waybar/assets/4633209/36a3b3a4-8dbd-4988-bd9b-7c3bae78e13c
It was kind of difficult to record so I only managed to record the workspace regions of my left and middle monitors. I move the mouse and the active workspace changes. Active means a white line appears at the bottom. Non-empty workspaces are a slightly whiter color. At the end of the video, I moved to my third monitor, which makes the other monitors not have an active workspace.
This seems to work perfectly fine on my system. Can you double-check you are running the latest version?

According to waybar --version, I am indeed running the latest version 0.9.20.

Is that the release version or the latest git commit? Because the 0.9.20 release was published a month ago, while my PR with the changes necessary for persistent workspaces was merged two weeks ago (https://github.com/Alexays/Waybar/commit/600653538b778cf9528bb7a230428418b5b9220b)
I use v0.9.20-64-gb084bf72 from the AUR, which is the latest git version.

I believe it is the release version. I use Waybar as distributed in the Fedora 38 repositories.

Alright, so you'll have to compile Waybar yourself or wait until the next version releases.
@VincentBerthier Can you check your version as well?

0.9.20 too, so… Hmm… Well, I guess this explains that.

I don't know if this is how the module is intended to work but it is not working as expected for me.
It arbitrarily numbers persistent workspaces from left to right not respecting which workspace I've bound to each monitor via hyprland configs.
I don't know if  it is feasible but we should be able to pick which individual workspace to show as persistent instead of specifying the amount of persistent workspaces or automatically show all workspaces bound to the monitor.

I don't know if this is how the module is intended to work

I use it together with my fork of Duckonaut's split-monitor-workspaces plugin. This plugin automatically binds workspaces to monitors, and sets up keybinds so that you can for example do this:

Automatically bind 5 workspaces to each monitor, based on the formula:

workspace_id = monitor_id * nr_of_workspaces_per_monitor + 1
So, the first workspace on the second monitor (= monitor ID 1) will have workspace_id = 1*5+1 = 6

Assign keybinds like Super+4, to go to the 4th workspace on the currently focused monitor.

The good thing about this approach is that I can use the exact same formula in Waybar, so that the binds the plugin makes correspond to the same workspaces that are shown on each monitor's bar. The plugin assigns workspace 6 to the second monitor, and Waybar also assigns workspace 6 to that monitor. Keybinds work perfectly and without configuration.
If I connect a monitor it has never seen before, it will automatically create 5 persistent workspaces in Waybar and the plugin. All without ever touching Hyprland's config file: no need to set binds. I just tell Waybar and the plugin settings to both add 5 workspaces per monitor, and that's it.

The problem with this approach is exactly as you describe: if you manually set your own binds in your hyprland config, the IDs you set in your Hyprland config won't necessarily match Waybar's formula.
The solution to this is manually setting the persistent_workspaces just like you would in wlr/workspaces (https://github.com/Alexays/Waybar/wiki/Module:-Workspaces#persistent-workspaces). The good news: I also implemented this in hyprland/workspaces :)
Instead of using "*": 5, you can manually set which monitors should show which workspaces:
"persistent_workspaces": {
        "1": ["DP-1"], // workspace ID : [array of monitors to show this workspace on, ...]
        "2": ["DP-1"],
        "3": ["DP-1"]
        // and so on, up to 5...
        "6": ["DP-2"],
        // up to 10...
        "11": ["DP-3"],
        // up to 15
}

I dislike this approach which is why I implemented the "*": 5 automatic approach, but I understand if you want to do it manually like above, to have more control over the workspace names.
Let me know if this works for you @proudhon

Thank you so much for the explanation, I couldn't find the manual setup in the wiki and therefore I ended up being confused.
I will try both the approaches and I will give you a feedback asap.

Manual setup works flawlessly, thank you so much.
I will try your own approach asap as it looks more flexible (especially because my docking station tends to mess with  my monitor names very often).

@mischw That is not yet implemented, I'll see if I can implement that today.

@mischw I just looked at the Hyprland wiki and the description of those settings implied it should work with the current implementation, so I tested it on my system and it already seems to work fine.
Are you using the latest release?

@zjeffer Oh sorry, I didn't see that there was just a new release. I will try that. Can't get it to compile right now but will try again tomorrow.

Fantastic work, thank you very much for implementing!
Is there a way to style workspaces that are currently visible on a monitor differently than those that are not shown on any monitor?

Is there a way to style workspaces that are currently visible on a monitor differently than those that are not shown on any monitor?

@jr64 Not yet, I'm thinking of implementing that soon, though

Just curious if we need to go down this road or request something more similar to the approach we're taking in nixpkgs in discussion https://github.com/NixOS/nixpkgs/pull/251115 about just enabling the experimental flag and using wlr/workspaces as-is. It looks like it functions fine so I'm not sure whether its worth investing effort into this module anymore. @zjeffer  opinions/context?

@khaneliman Some things that come to mind why I dislike that approach:

The persistent workspaces implementation is quite limited in wlr/workspaces.
With wlr/workspaces, you have to specify "<workspace>": [<array of monitors to show workspace on>]. This is quite cumbersome and doesn't automatically work with keybinds. With my changes in hyprland/workspaces, you can simply specify "*": 5 to show 5 workspaces on each monitor.
Persistent workspaces are named automatically based on hyprland monitor IDs, to make sure the names match between waybar and plugins like split-monitor-workspaces.
This would need to be ported to wlr/workspaces but it uses hyprland specific stuff (monitor IDs) to accomplish the automatic workspace naming. I actually tried to implement this before hyprland/workspaces existed, see here: https://github.com/Alexays/Waybar/pull/2251.
See this issue for more info about why I implemented it this way.

@khaneliman Some things that come to mind why I dislike that approach:
* The persistent workspaces implementation is quite limited in wlr/workspaces.

* With wlr/workspaces, you have to specify `"<workspace>": [<array of monitors to show workspace on>]`. This is quite cumbersome and doesn't automatically work with keybinds. With my changes in hyprland/workspaces, you can simply specify `"*": 5` to show 5 workspaces on each monitor.

* Persistent workspaces are named automatically based on hyprland monitor IDs, to make sure the names match between waybar and plugins like [split-monitor-workspaces](https://github.com/zjeffer/split-monitor-workspaces).

* This would need to be ported to wlr/workspaces but it uses hyprland specific stuff (monitor IDs) to accomplish the automatic workspace naming. I actually tried to implement this before hyprland/workspaces existed, see here: [[wlr/workspaces] Improve persistent_workspaces by allowing fixed nr of workspaces per monitor #2251](https://github.com/Alexays/Waybar/pull/2251).

* See [this issue](https://github.com/Alexays/Waybar/issues/2243) for more info about why I implemented it this way.

The interesting thing is that the wlr implementation supports my use case better of wanting to show specific workspaces on a monitor, albeit in poor experience of declaring it in configuration. I use specific icons/names per monitor and can't seem to get that functioning with hyprland persistent workspaces.
wlr/workspaces

hyprland/workspaces

The video workspace is assigned to a different monitor but the perisistent workspace implementation in hyprland shows it on my other monitor.

The interesting thing is that the wlr implementation supports my use case better of wanting to show specific workspaces on a monitor, albeit in poor experience of declaring it in configuration. I use specific icons/names per monitor and can't seem to get that functioning with hyprland persistent workspaces.

Your wlr persistent workspace configuration should be able to work the same on both modules, unless I made a mistake while programming it ;)

The video workspace is assigned to a different monitor but the perisistent workspace implementation in hyprland shows it on my other monitor.

That sounds more like a bug than an intended feature. Can you create a separate issue for this, with a minimal reproducible example?

The interesting thing is that the wlr implementation supports my use case better of wanting to show specific workspaces on a monitor, albeit in poor experience of declaring it in configuration. I use specific icons/names per monitor and can't seem to get that functioning with hyprland persistent workspaces.

Your wlr persistent workspace configuration should be able to work the same on both modules, unless I made a mistake while programming it ;)

The video workspace is assigned to a different monitor but the perisistent workspace implementation in hyprland shows it on my other monitor.

That sounds more like a bug than an intended feature. Can you create a separate issue for this, with a minimal reproducible example?

My understanding from the wiki was that I had to just specify a number of workspaces for a monitor and then it just loops through and assigns that many.
{
  "hyprland/workspaces": {
    "all-outputs": false,
    "active-only": "false",
    "format": "{icon}",
    "format-icons": {
      "1": "",
      "2": "",
      "3": "",
      "4": "",
      "5": "",
      "6": "",
      "7": "",
      "8": "󰢹",
      "urgent": "",
      "default": "",
      "persistent": "persistent",
      "empty": "empty"
    },
    "persistent_workspaces": {
      "*": 8,
      "DP-3": 1
    }
  },

vs
  "wlr/workspaces": {
    "all-outputs": false,
    "active-only": "false",
    "on-click": "activate",
    "format": "{icon}",
    "format-icons": {
      "1": "",
      "2": "",
      "3": "",
      "4": "",
      "5": "",
      "6": "",
      "7": "",
      "8": "󰢹",
      "urgent": "",
      "default": ""
    },
    "persistent_workspaces": {
      "1": [
        "DP-3"
      ],
      "2": [
        "DP-1"
      ],
      "3": [
        "DP-1"
      ],
      "4": [
        "DP-1"
      ],
      "5": [
        "DP-1"
      ],
      "6": [
        "DP-1"
      ],
      "7": [
        "DP-1"
      ],
      "8": [
        "DP-1"
      ]
    }
  }

Yeah the wiki should be updated with that info and more examples but I've been kind of busy with other stuff lately and didn't feel like it :)

@khaneliman

hyprland/workspaces ideal but probably hard to support

That actually looks pretty easy to implement, I'll do it if I find some time.

@khaneliman

hyprland/workspaces ideal but probably hard to support

That actually looks pretty easy to implement, I'll do it if I find some time.

I guess just check if it's an array within it instead of a single number to process differently.

I guess just check if it's an array within it instead of a single number to process differently

Indeed.

special workspaces can now opened empty in hyprland
so persistent special workpsaces can exist and behaviour should be tested

so persistent special workspaces can exist and behavior should be tested

Current behaviour with this config:
"hyprland/workspaces": {
    "format": "{icon}",
    "format-icons": {
      "urgent": "",
      "active": "",
      "default": "",
      "persistent": "",
      "special": "s"
    },
    "on-scroll-up": "hyprctl dispatch workspace r-1",
    "on-scroll-down": "hyprctl dispatch workspace r+1",
    "all-outputs": false,
    "show-special": true,
    "persistent_workspaces": {
      "*": 5,
      "special": [
        "eDP-1",
        "DP-2",
        "HDMI-A-1"
      ]
    }
  },

seems to show the workspace persistently on all my monitors, and has the correct css class both when empty and not empty.
There seems to be no active class when the special workspace is toggled. I would assume the user wants visual feedback when the special workspace is active, right? Should the currently active workspace keep its active class or should it become non-active. I think it should keep the active class.
There's also some weird behaviour with named special workspaces, I'll have to investigate further.

there isn't a IPC event for when a special workspace is opened
you can find out by calling hyprcctl monitors
feel free to create a feature request, but for now the best you can do is start preparing the code for when it gets implemented
maybe add a format for special-active

There's also some weird behaviour with named special workspaces, I'll have to investigate further.
?

Hi,
Do I miss something? I can't get working https://github.com/hyprland-community/hyprland-autoname-workspaces with this new module. What is the way to keepthe same format and behavior aswlr/workspaces` ?

And also, wlr/workspaces didn't work anymore, but I can't find error, nothing but no workspaces anymore at all with this legacy module.
I would like to be able to still use hyprland-autoname-workspaces to control the content of my workspaces in waybar.

Thanks

And also, wlr/workspaces didn't work anymore for me, but I can't find relevant error, nothing but no workspaces anymore at all with this legacy(?) module.

The protocol that supported wlr/workspaces module in Hyprland was removed from Hyprland recently.

* I would like to be able to still use hyprland-autoname-workspaces to control the content of my workspaces in waybar.

I've never used that program before, but I can try and take a look at what the workspaces module needs to make it work.

* I would like to be able to still use hyprland-autoname-workspaces to control the content of my workspaces in waybar.

I've never used that program before, but I can try and take a look at what the workspaces module needs to make it work.

I would be happy if you can do this please 👍🏻

And also, wlr/workspaces didn't work anymore for me, but I can't find relevant error, nothing but no workspaces anymore at all with this legacy(?) module.

The protocol that supported wlr/workspaces module in Hyprland was removed from Hyprland recently.

https://github.com/hyprwm/Hyprland/commit/bb0933437f4602080a66cc877fee36dce8dcb3ff OMG i'm so sad.

new PR for "activespecial" IPC event is up so special workspace integration should be fully doable now

new PR for "activespecial" IPC event is up so special workspace integration should be fully doable now

Alright, I'll probably do this next weekend because I'll be too tired after work during the week... Unless someone else wants to implement it? ;)

for me the persistent workspace icon is shown every where i wanted to modify the workspaces somehow so that occupied have different icons then non occupied workspace.
it was possible int wlr/workspace as then occupied used to have only the default: icons and all unoccupied used to have persistent: icon but in hyprland/workspace persistent icons override the default one's

@niksingh710 If I understand your request correctly, you should be able to get the behaviour you want by using the "empty" icon class.
Occupied persistent workspaces will have the persistent icon, while non-occopied persistent workspaces will have the empty icon. If you don't define the empty icon in your config, it will fall back to the persistent icon. Hope this helps.

Is it possible to add a visible workspaces class?

Occupied persistent workspaces will have the persistent icon, while non-occopied persistent workspaces will have the empty icon. If you don't define the empty icon in your config, it will fall back to the persistent icon. Hope this helps.

Exactly what I wanted.
I guess it wasn't on the wiki earlier.

* I would like to be able to still use hyprland-autoname-workspaces to control the content of my workspaces in waybar.

I've never used that program before, but I can try and take a look at what the workspaces module needs to make it work.

I understand we maybe need a "mode" in this module, that will "just" fetch for example every second, or on events a fetch of workspaces name. Maybe react on the same events as hyprland-autoname-workspaces to be sure in this mode.

The renameworkspace was added https://github.com/hyprwm/Hyprland/commit/2d100bf57e0c0184d307bd4173b1a8d9fc7130e1#diff-3c089c6c6b23a85ab5b4cffb002e8880ad069c8a8b3462f7aafa9e5345c0333d

#workspaces button.urgent
isn't working anymore!

#workspaces button.urgent
isn't working anymore!

In what way? I daily drive the last commit and it works for me.

#workspaces button.urgent
isn't working anymore!

In what way? I daily drive the last commit and it works for me. My example of styling in other issue: #2469 (comment)

It works with "wlr/workspaces" module in hyprland 28
I tired with "hyprland/workspaces" module in hyparland 28 but it doesn't work.
I'm using hyprland 29.1 now and "hyprland/workspaces" module.
It doesn't work for me.

@tumon-art But which version of waybar are you using? The urgent class was only added pretty recently.

@tumon-art But which version of waybar are you using? The urgent class was only added pretty recently.

0.9.22

@tumon-art But which version of waybar are you using? The urgent class was only added pretty recently.

0.9.22

Urgent isn't in that release.

There seems to be an issue with active-only after https://github.com/Alexays/Waybar/pull/2408 has been implemented - you will see all active workspaces for the fraction of a second while switching from an active workspace to an empty one.
CC @zjeffer

Sorry to necro the split-monitor discussion, but is there an efficient way to rename split-workspaces to their relative number?
For example: There are 5 workspaces per monitor. Thus, workspace id "6" corresponds to workspace 1 on the second monitor. Instead of showing this as "6" in the second monitor's waybar, I would like an option to have it shown as "1".
In short, the ability to set a number n such that the displayed workspace names cycle every n workspaces.

Does format-icon not work? Just map 6-10 as 1-5 again for display.

Not sure if this the place to ask, but what would it take to incorporate something like wlr-taskbar into hyprland-workspaces?
If not feasible (I haven't checked for complexity) then would it be possible to either have a tooltip & tooltip-format added,
that way I could run a script to get info from hyprland on a hover event.
I suppose on-click might also work.
Anyway, just asking, and thanks to all doing the work to make waybar/* possible

A feature which I really need would be the option to have a different format-icon for "ocupied" workspaces.
There are currently format-icons available for default, active and urgent workspaces. Is there any way this could be implemented ?

  "hyprland/workspaces": {
    "format": "{icon}",
    "on-click": "activate",
    "persistent_workspaces": {
      "1": [],
      "2": [],
      "3": [],
      "4": [],
      "5": [],
      "6": [],
      "7": [],
      "8": [],
      "9": [],
      "10": []
    },
    "format-icons": {
      "active": " 󰮯 ",
      "default": " ",
      "empty": "󰧵 ",
    }
  }```

This is my config.
earlier it used to display all workspaces (1 to 10) with correct icons
now this same config does not work as expected.
it only shows the occupied workspaces.

Hyprland has native support for persistent workspaces now (see https://github.com/hyprwm/Hyprland/pull/3530)
This is not needed anymore.

Hyprland has native support for persistent workspaces now (see hyprwm/Hyprland#3530) This is not needed anymore.

Thanks for mentioning mate seems like have to wait for a while to get it in release.

I'm using the git version until the next releases comes out. I think you can do the same :shrug:
Worth noting that waybar behaves weirdly when moving workspaces around across monitors, reloading configuration solves the issue: killall -SIGUSR2 waybar

Hyprland has native support for persistent workspaces now (see hyprwm/Hyprland#3530) This is not needed anymore.

Great! Once this branch is merged, we should be able to query for persistent workspaces and we can then dynamically fill the module with the persistent workspaces, without having to manually specify them in the config :tada:

@hariseldon78 This would definitely be very useful for us!

Ok great to hear that! I'll get to it asap.

https://github.com/hyprwm/Hyprland/pull/3630 it's merged guys, let me know if you need any help using the feature

Hyprland has native support for persistent workspaces now (see hyprwm/Hyprland#3530) This is not needed anymore.

This is my hyprland workspaces
[{
    "workspaceString": "1",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "2",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "3",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "4",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "5",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "6",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "7",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "8",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "9",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "10",
    "monitor": "eDP-1",
    "default": true,
    "persistent": true
}]

This is my waybar Config
  "hyprland/workspaces": {
    "format": "{icon}",
    "on-click": "activate",
    "all-outputs": false,
    "format-icons": {
      "active": " 󰮯 ",
      "default": " ",
      "empty": "󰧵 ",
      "persistent": "󰧵 ",
    }
  },

only occupied workspaces are shown.

one thing i observed is if i switch my focus to an empty workspace then it is getting shown in waybar but then also it is not using empty icon defined in config.
and if i logout login back again i need to focus each workspace once then only it shows up.

Hyprland has native support for persistent workspaces now (see hyprwm/Hyprland#3530) This is not needed anymore.

This is my hyprland workspaces
[{
    "workspaceString": "1",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "2",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "3",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "4",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "5",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "6",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "7",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "8",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "9",
    "monitor": "DP-1",
    "default": true,
    "persistent": true
},{
    "workspaceString": "10",
    "monitor": "eDP-1",
    "default": true,
    "persistent": true
}]

This is my waybar Config
  "hyprland/workspaces": {
    "format": "{icon}",
    "on-click": "activate",
    "all-outputs": false,
    "format-icons": {
      "active": " 󰮯 ",
      "default": " ",
      "empty": "󰧵 ",
      "persistent": "󰧵 ",
    }
  },

only occupied workspaces are shown.

Looks like you didn’t set up persistent workspaces in waybar.

@niksingh710  maybe you are already doing it, but those shown are just the workspace rules, they act on the workspaces when they are present, so you always need 2 commands, one to set the workspacerule and one to create the workspace.
That said, i also found some inconsistencies with how waybar react when i create a new persistent workspace, sometimes it is shown many times, sometimes it is shown with the wrong css style (occupied instead of empty or viceversa). My workaround for now is to restart the waybar in the same script, and it works. Here is my script, it creates a workspace asking the name and then it sorts them alphabetically:
hyperland-create-workspace.py

Here is my script maintaining 10 workspaces on multiple monitors.

@niksingh710 FYI: Hyprland's new persistent workspace rule (implemented in Hyprland by @hariseldon78) is not yet supported in Waybar. I'm working on it in this PR: https://github.com/Alexays/Waybar/pull/2603, but I haven't had much time to work on it lately. For now, you should specify your persistent workspaces in your waybar config, see the wiki for an example.

@niksingh710 FYI: Hyprland's new persistent workspace rule (implemented in Hyprland by @hariseldon78) is not yet supported in Waybar. I'm working on it in this PR: #2603, but I haven't had much time to work on it lately. For now, you should specify your persistent workspaces in your waybar config, see the wiki for an example.

Added persistent workspace.
I think hyprland persistent workspace making them identify as non-empty as now e+1 and r+1 behave in same manner.
I have asked that in the pr discussion https://github.com/hyprwm/Hyprland/pull/3530

after the rename event gets registered and handled i tried to use renaming more and more. But currently after renaming the order of workspaces stays the same although i configured 'sort-by': 'name'.
Is there any chance i can trigger the sort from outside or this behaviour gets added?

Looks like we're already listening to workspace rename events, maybe we should add a call to sort_workspaces() at the end of this function: https://github.com/Alexays/Waybar/blob/0a747ddafc10ace2a2d8588ba673b9c2015d8446/src/modules/hyprland/workspaces.cpp#L329-L342

Hi all, I finally found time to finish my PR to use Hyprland's persistent workspace rules instead of Waybar's "persistent-workspaces" object, it's ready to test and review: https://github.com/Alexays/Waybar/pull/2603
Remember to update Hyprland to be able to listen to the configreloaded event.

Currently module cycles with scroll through workspaces back to beginning when the last one is reached. Could you add an option to configure/avoid this? Something like disable-scroll-wraparound option in Sway/workspaces module.

@pkreuzt I added this to my "hyprland/workspaces" object in my waybar config:
"on-scroll-up": "hyprctl dispatch workspace r-1",
"on-scroll-down": "hyprctl dispatch workspace r+1"

That does something not very desirable for me. Could work as a temporary workaround, but the issue is still there.
El 12 de octubre de 2024 11:44:11 CEST, Tuur Vanhoutte @.***> escribió:

@pkreuzt I added this to my "hyprland/workspaces" object in my waybar config:
"on-scroll-up": "hyprctl dispatch workspace r-1",
"on-scroll-down": "hyprctl dispatch workspace r+1"

--
Reply to this email directly or view it on GitHub:
https://github.com/Alexays/Waybar/issues/2271#issuecomment-2408479056
You are receiving this because you were mentioned.
Message ID: @.***>

@pkreuzt Can you explain what you mean by 'something not very desirable'?
What behavior do you want to see instead? Do you want the scroll to not do anything at all when you reach the start/end?

Previous config goes on creating new workspaces beyond existing ones. Or should I say, makes empty workspaces visible on scrolling when I have chosen to show only occupied ones. Some people would maybe like this, but not everyone.
There should be a way to scroll only through busy workspaces (or fixed ones) but without looping. For example, if I have 3 workspaces visible on module,  scrolling over it from 1 should move to 2 and 3 at most, and stay there without looping back to 1.
El 14 de octubre de 2024 10:19:03 CEST, Tuur Vanhoutte @.***> escribió:

@pkreuzt Can you explain what you mean by 'something not very desirable'?
What behavior do you want to see instead? Do you want the scroll to not do anything at all when you reach the start/end?
--
Reply to this email directly or view it on GitHub:
https://github.com/Alexays/Waybar/issues/2271#issuecomment-2410400531
You are receiving this because you were mentioned.
Message ID: @.***>

I see. You said: Currently module cycles with scroll through workspaces back to beginning when the last one is reached. Can you share your config that causes this? I can't reproduce that with a minimal config (scrolling doesn't do anything)

Module config is like this:
	"hyprland/workspaces": {
                 "on-scroll-up": "hyprctl dispatch workspace m-1",
                 "on-scroll-down": "hyprctl dispatch workspace m+1",
		 "active-only": false,
		 "all-outputs": false,
	    },

Got it. Can you create a separate GitHub issue with the explanation of your feature request? As far as I know it's not yet possible to do what you want.


Multi Modal Question

in multi modal example, i see fake prompt id is different for every embedding token:
https://github.com/NVIDIA/TensorRT-LLM/blob/main/examples/multimodal/run.py#L271-L275
is this by design in TRT-LLM? my custom tokenizer tokenize into same id for embedding and i could workaround it to fit what trt-llm is looking for but i am wondering if this is something by design or there are someways to achieve with a combination of prompt tuning params?

fake_prompt_id can contain same id multiple times and in any order.  If id is in [0, vocab_size) range, it indexes into text embedding table. If id is in [vocab_size, vocab_size + max_prompt_embedding_table_size),  it indexes into prompt table.
In multimodal example, we provide image features as input to model in addition to text prompt. So, fake_prompt_id is initialized to [vocab_size, vocab_size + 1, vocab_size + 2, ..,]. These ids index into prompt table which contains image features.

sounds good. thanks for the explanation


When use footerValueBuilder, popup bubble don't show the same text.

When I change the bottom text with footerValueBuilder should update the popup bubble text.

It's only for the footer, but you are right, we will need a builder for the bubble.

Yes, or be able to disable indicator in the bubbler. Because, if change the footer, sometimes bubbler indicator do not make sense. (They look not related).

Just more one thing, can I fix a popup bubble or something that show the value?

You could fork the project do your changes and send a Pull request (without
breaking the current behaviour).
On Thu, Aug 1, 2019, 7:22 PM Eliseu Codinhoto<EMAIL_ADDRESS>wrote:

Just more one thing, can I fix a popup bubble or something that show the
value?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aeyrium/bezier-chart/issues/30?email_source=notifications&email_token=ABFL3UA7IPW2XVCHGXJKQCLQCN45NA5CNFSM4IIXAF62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3MHMSA#issuecomment-517502536,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABFL3UDFZSDSRZRERDMZ5WDQCN45NANCNFSM4IIXAF6Q
.

So, currently there is not way to "always show" popup bubble, right?

What do you mean?
On Thu, Aug 1, 2019, 7:58 PM Eliseu Codinhoto<EMAIL_ADDRESS>wrote:

So, currently there is not way to "always show" popup bubble, right?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aeyrium/bezier-chart/issues/30?email_source=notifications&email_token=ABFL3UGOQVINUSM663Z2LWTQCOBDBA5CNFSM4IIXAF62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3MIYHY#issuecomment-517508127,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABFL3UB4Y76ZFVN7SE5PPHTQCOBDBANCNFSM4IIXAF6Q
.

I want something like this:

This package supports multiline graph, so what do we do in that case?

If multiline, it should show values on tap (select) line.

Ok, I will leave this issue open in case anyone want to implement it
without breaking the current behavior.
On Fri, Aug 2, 2019 at 11:44 AM Eliseu Codinhoto<EMAIL_ADDRESS>wrote:

If multiline, it should show values on tap (select) line.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aeyrium/bezier-chart/issues/30?email_source=notifications&email_token=ABFL3UAULB2EV3IGGZRTMEDQCRP5RA5CNFSM4IIXAF62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3OIQJA#issuecomment-517769252,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABFL3UDE3CMDLZSNE56PN2LQCRP5RANCNFSM4IIXAF6Q
.

there are new changes about custom labels inside bubble indicator:  https://github.com/aeyrium/bezier-chart/pull/40


Reorder Campaigns, vert centre only child breadcrumb

Fixes https://github.com/silverstripe/silverstripe-framework/issues/5508
Was:

After:

Couldn't figure out how to move Campaigns further down but I think this position or after Files would be better than being in first position.
Maybe it was just caching but couldn't find the magic number.


Circleci project setup

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@141e161). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main        #2   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         5
  Lines           ?        33
  Branches        ?         7
========================================
  Hits            ?        33
  Misses          ?         0
  Partials        ?         0

Continue to review full report at Codecov.

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


misa WLRL field

"The misa CSR is a WARL read-write register" seems not entirely true since it contains a WLRL field.
Also, the definition of WLRL says that such fields must only be written with legal values (a software requirement) and that the reset value of WLRL fields must be legal (a hardware requirement).  The software requirement can be complied with by always doing read-modify-write.  But the hardware requirement can only be complied with if legal values are specified.  Unlike the other WLRL fields in the privileged spec, there is no description of what values are legal for this misa field.  We can infer that zero is one of the legal values since the whole register is allowed to be zero, but that doesn't rule out other legal values.
Is this field implementation-specific and UNSPECIFIED?  Must it be zero (as was the case when the field was WIRI two years ago)?  Something else?

It is true that forward-compatible software shouldn't try to write fields it doesn't know about to nonzero values, because newer versions of the spec could assign meaning to such fields.  But I don't think it means the unused bits are actually WLRL.  Writing them to a nonzero value on future hardware could cause behavior that software doesn't expect, because it could enable some extension that software doesn't know about.  But that's different from causing UNSPECIFIED behavior.
The unused misa bits are analogous to pmpcfg bits 6:5, which are currently always 0, but which might take on new meaning in the future.  We label those pmpcfg bits as "0 (WARL)".  I think we should be doing the same thing for the unused misa bits.

Is there a reason that bits MXLEN-3...26 aren't WARL (0)? or WPRI ?
IF they're being reserved for future standard features, WPRI makes sense.
The architecture defines WARL, WLRL, and WPRI, and describes how each
behaves - but doesn't describe the use cases.
CSRs with WLRL that are written with illegal values are allowed to trap,
but ordinarily we've said that we don't have data dependent traps on CSRs.
That can still occur if the CSRRxI immediate forms are used, but otherwise
not. It seems strange that writing the same value to the same CSR will trap
if the immediate form is used, but not if the register version is used.
The only CSRs that have WLRL fields are MISA, the exception code in the
various versions of the xcause CSRs, and VGEIN in the hypervisor status
CSR. I'm wondering what makes those fields so special that they couldn't
use WARL or WPRI.
On Fri, Jul 10, 2020 at 1:57 PM Andrew Waterman<EMAIL_ADDRESS>wrote:

It is true that forward-compatible software shouldn't try to write fields
it doesn't know about to nonzero values, because newer versions of the spec
could assign meaning to such fields. But I don't think it means the unused
bits are actually WLRL. Writing them to a nonzero value on future hardware
could cause behavior that software doesn't expect, because it could enable
some extension that software doesn't know about. But that's different from
causing UNSPECIFIED behavior.
The unused misa bits are analogous to pmpcfg bits 6:5, which are currently
always 0, but which might take on new meaning in the future. We label those
pmpcfg bits as "0 (WARL)". I think we should be doing the same thing for
the unused misa bits.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-isa-manual/issues/537#issuecomment-656886866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJRNTBZQPV4M2TRJYATR256CDANCNFSM4OW5MHMQ
.

@allenjbaum I guess I'm saying I think this is an editing oversight, and they should indeed be marked WARL (0).

And the next step is: can we eliminate the other two cases and simplify the
architecture so there are only 2 types of fields?
The description that says that fields should be written with the same
value read: that is a SW requirement - I'm not sure that "requirement" is
even the right word here.
I don't think it makes sense to define HW field behavior based on some
software rule, as opposed to having a note about the expected SW behavior
where the field is defined, and the possible consequences if you don't
follow the rule
If we can have WARL fields where you have no idea what happens if you
write an illegal value (well, you know its legal, but not which legal and
therefore with unknown side effects and putting the hart into an unknown
state) - how is that any worse than telling implementors that only the
value that is legal is the one that is read, so they shouldn't change it or
bad things may happen?
On Fri, Jul 10, 2020 at 10:30 PM Andrew Waterman<EMAIL_ADDRESS>wrote:

@allenjbaum https://github.com/allenjbaum I guess I'm saying I think
this is an editing oversight, and they should indeed be marked WARL (0).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-isa-manual/issues/537#issuecomment-656993839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJTJUY3RZHDNU2E3BMDR272GNANCNFSM4OW5MHMQ
.


[BUG] Typo in betterteams messages.yml EN

What is the bug?
While I was translating betterteams I have noticed a typo:
Found: You team home could not be found
Correct: You're team home could not be found
Expected Behaviour
To fix this typo its not really that big of an issue.
How to Reproduce

Enter the files

Search specific messages.yml

Line 120: "home.world"

Fix the typo

commit and push

(OPTIONAL): Could search for any other near typo's

Error message
Language bug
Output of /teama version
Language bug / Just the most recent one.
Additional Information
No response

This bug has been fixed and the patch will be included in the next update. Thank you for reporting.


"Fântânele" is listed in the drop-down menu

Description:
"Fântânele" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Fântânele" in the search bar.

Expected results
The location is listed in the drop-down menu as "Fântânele, Alba (Ceru-Băcăinți)".


Minor updates for governance references.

Removed the link to issue proposing the governance WG and replaced it with the governance README and called it our Charter, similar to what Contributor Growth has done.
Added our meeting time to the governance page.

Approved at Gov WG meeting


docs: This patch updates syntax for yarn

It's a very tiny change, but the syntax of yarn has shifted to
no longer require to use of "install", it's inferred now.

Woops. Meant to base that on develop.


Feature/mockoon/mockoon#469

Closes mockoon/mockoon#469
Makes the server instance honor the passed in hostname restriction.

Thanks for starting to add some tests for the server :)


Remove Crittercism from Standalone application's dependencies

This will allow any user to build with Crittercism cordova plugin. (Cannot currently because the library is already there, but user cannot configure it.)

+1

+1
On Thursday, February 12, 2015, Brian DeBoer<EMAIL_ADDRESS>wrote:

+1
—
Reply to this email directly or view it on GitHub
https://github.com/AppGyver/steroids/issues/573#issuecomment-74207069.

--
Alex Gaber
+1.415.225.2581

bump

+100

+9000

We're pushing out a new iOS release in a few weeks, and this will be included!

great! Can't wait to get my hands on this. Thanks!

+1

when is the iOS update being released?


Command xxx is not found in team XXX?

I am using flask-slack and I did a test with your example(just echo your text).
My Slash Command is /stats
here is my code in server:
from flask_slack import Slack
from flask import Flask
app = Flask(__name__)

slack = Slack(app)
app.add_url_rule('/', view_func=slack.dispatch)

@slack.command('/stats', token='xxxxxxxxxxxxxxxxxxxx',
               team_id='T0BR3AK3T', methods=['POST'])
def echo_method(**kwargs):
    text = kwargs.get('text')
    return slack.response(text)

if __name__ == "__main__":
    app.run(host='<IP_ADDRESS>')

The URL I put is:(is it okay?)
http://server:5000/

But when I triggered the Slash Command,result
Command xxx is not found in team XXX

Can you give a  more detailed example?

Solved.
@slack.command('/stats', token='xxxxxxxxxxxxxxxxxxxx',
               team_id='T0BR3AK3T', methods=['POST'])

should be
@slack.command('stats', token='xxxxxxxxxxxxxxxxxxxx',
               team_id='T0BR3AK3T', methods=['POST'])

:smile:

:clap: glad you solved it

im running into the same thing running pretty much the same code on pythonanywhere
# A very simple Flask Hello World app for you to get started with...
from flask import Flask
from flask_slack import Slack

app = Flask(__name__)
slack = Slack(app)
app.add_url_rule('/', view_func=slack.dispatch)
@slack.command('flaskyou',token=' xxxxxxx',team_id='xxxxxx',methods=['GET'])
def your_method(**kwargs):
    text = kwargs.get('robo says hi from flask on pythonAnywhere 12-8-2015')
    return slack.response(text)```

@RoboDonut
Maybe your methods should be 'POST'.
@slack.command('flaskyou',token=' xxxxxxx',team_id='xxxxxx',methods=['GET'])

to:
@slack.command('flaskyou',token=' xxxxxxx',team_id='xxxxxx',methods=['POST'])

@RoboDonut Could you paste the error message here?

its funny i'm not getting any errors, just the "Command None is not found in team None"
im running my flask app on pythonanywhere.com (you can check out the response here http://robodonut.pythonanywhere.com/ ).
get -> post doesn't seem to help. when i inspect the command while running the slack client in the browser it seems that the method is always post..
as a note i just updated flask-slack too with out resolution.
im gonna get flask up on a box with outside access and see if the issue is with pythonanywhere. Whats strange is this was working on Sunday night then Monday no worky

got this up and running on my server. when i initiate the command this is the response from the server and nothing pops up in slack at all:
`<IP_ADDRESS> - - [09/Dec/2015 13:59:35] "GET /?token=XXXXXXXX&te
am_id=XXXXXX&team_domain=thespatialones&channel_id=C0A612AS0&channel_name=gen
eral&user_id=U0ACDK98R&user_name=robodonut&command=%2Fflaskyou&text=&response_ur
l=https%3A%2F%2Fhooks.slack.com%2Fcommands%2FT0A61BW1G%2F16318587378%2FbVNknWEso
9ga4MLYthnW5tSQ HTTP/1.1" 200 -

I tried to access http://robodonut.pythonanywhere.com/?token=XXXXXXXX&team_id=XXXXXX&team_domain=thespatialones&channel_id=C0A612AS0&channel_name=general&user_id=U0ACDK98R&user_name=robodonut&command=%2Fflaskyou&text= and got Command flaskyou is not found in team XXXXXX. The request data is not missing.
A possible reason could be the command and team_id your registered is different from the parameters in GET request.

its strange. If i dump in like basic "hello world" code with the return i get "hello world" back. triple checked team ID and command and token and such. I;m going to be working on this tonight and will document everything and post again


$transition$.params() includes a "#" key

I'm trying to transition from $stateParams to $transition$.params() in an Angular.js (current at 1.4) app. Things are mostly working except that I'm seeing an extra key in all my params.
Here's a relevant snippet from my router:
// app/admin/admin-router.js (lines 2-25)
$uiViewScrollProvider.useAnchorScroll();
$urlMatcherFactoryProvider.strictMode(false);

$urlRouterProvider.otherwise('member');

// Base admin area
$stateProvider.state('admin', {
  url: '/',
  templateUrl: 'admin/index.html',
  controller: 'AdminController'
});

// Member search etc.
$stateProvider.state('admin.member', {
  url: 'member',
  templateUrl: 'admin/member/search.html',
  controller: 'MemberSearchController'
})
.state('admin.member.results', {
  url: '/results?subId&email&slug&phone&firstname&lastname&partialEmail&role',
  templateUrl: 'admin/member/search-results.html',
  controller: 'MemberSearchResultsController'
})

In the MemberSearchResultsController, the parameters are populated by a search form. If I fill one field in and log params inside the controller I get this:
{
  #: null,
  subId: 'banana',
  email: undefined,
  phone: undefined,
  firstname: undefined,
  lastname: undefined,
  partialEmail: undefined,
  role: undefined
}

which is a problem because I'm currently blindly serializing that to send to a remote API and null is not dropped the way undefined is, so I end up with something like http://mydomain.com/myroute?%23=null&subId=banana. Obviously, I can work around this case, but everywhere I've checked params, they always include this extraneous "#" key. Why is that? Is this something legacy about my app or an issue with ui-router? FWIW, if I log $transition$.targetState().params() the # key is not present.
I'm also setting
  $locationProvider.html5Mode(false);
  $locationProvider.hashPrefix('!');

in a different config block in case that's relevant (and I suspect that it is).
This is a (check one box):

[x] Bug Report
[ ] Feature Request
[ ] General Query

My version of UI-Router is: (type version)
1.0.17
Bug Report
Current Behavior:
I get an extra key in my params: "#"
Expected Behavior:
I get only the params I specify in my routing config.

That doesn't seem related to the issue I posted.

You are right that it is not directly related to your reported issue.
However, I am convinced that the issues we are reporting are indirectly related due to the AngularJS version used.
I also noticed the $stateParams["#"] value in the $stateParams injected into the Angular Controller as you reported depending on the AngularJS version used.
I posted my code because it is easier for the ui-router maintainers to test.


Task: Fix Form Issues

Thanks to Mikhail for pointing out these issues:

TextInput now has a decoration prop where you can pass underlined and it will have that dotted underline that we used everywhere

Updated the OutcomeSelection to have a hideBars prop to disable the actual outcome probability bars on scalar markets

I didn’t change the slider, I think it looks better this way, the previous version was more inconsistent across the screens, the light version of the scalar is supposed to look like this imo, otherwise let's change this in the design overhaul

buuuut why did the tests fail?


chore: update *.mbti

Pull Request Test Coverage Report for Build 51
Details

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 73.071%

Totals

Change from base Build 50:
0.0%

Covered Lines:
1335

Relevant Lines:
1827

💛  - Coveralls


Feat module reference reorganization

@jamie-pate adding the entryPoint to each function solves the problem. much simpler. no need to slipt chunks now. thanks for pointing out the entryPoint method.


Optimising workspace selector

Is this expected? Looks super tight to logo?

Yes that was the idea.
Can add "1" if you're shocked though!

Maybe... but makes the Workspace Conversations even weirder I think that's what shocked me


Fix log initialization timing

Support the lazy initialization log
Move the log configuration timing for xml config

Fixes gh-1272
@harawata
Please review this.
Main Changes:

I added the LazyReference class. It is the container class to delay the creation of an object using a Supplier.
I added the getLazyInitializationLog method on LogFactory using on LazyReference and JDK Proxy.
I changed as call the LogFactory#getLazyInitializationLog instead of LogFactory#getLog on some classes (Only class in which problem will occurs)
I changed as perform logging configuration as possible as faster at the XML config.

Note:
Problems may occur depending on the setting order at other classes, but I will cover it with documentation.

Thank you, @kazuki43zoo .
I'm not opposed to the change, but would like to consider other options if there is any.
For example, does using LOG4J2 or SLF4J (as the abstraction layer) solve the problem?

So, this can be fixed by the nested holder class technique as well, is that correct?
  WARNING {
    @Override
    public void doAction(MappedStatement mappedStatement, String columnName, String property, Class<?> propertyType) {
      getLog().warn(buildMessage(mappedStatement, columnName, property, propertyType));
    }
  },

  // ...

  private static class LogHolder {
    static Log log = LogFactory.getLog(AutoMappingUnknownColumnBehavior.class);
  }

  protected static Log getLog() {
    return LogHolder.log;
  }

Can't say it's definitely better than your solution, but it's simpler and less intrusive (which is my preference :)).
What do you think?

@harawata I think your suggestion is good because it is very simple !!
I have a one question. The getLog method is required?
Is following code problem? If no problem, I feel it is more simple.
  WARNING {
    @Override
    public void doAction(MappedStatement mappedStatement, String columnName, String property, Class<?> propertyType) {
      LogHolder.log.warn(buildMessage(mappedStatement, columnName, property, propertyType));
    }
  },

  // ...

  private static class LogHolder {
    private static final Log log = LogFactory.getLog(AutoMappingUnknownColumnBehavior.class);
  }


docker-compose per each public environment

Overview
Currently we have docker-compose-watcher.yml that can be spun up and connect to *.ropsten.v1.omg.network, we need the same for other public environments that connect to ropsten/mainnet/etc. so each engineer can easily spin up an instance and debug locally.

just need two: 1) ropsten testnet 2) mainnet

Closing until there's more request for it


Allow kafka to be used for EmsEvents

This adds the option for kafka to be used as the backend mechanism for publishing and consuming ems_events instead of MiqQueue.
https://github.com/ManageIQ/manageiq/issues/20027

@agrare What are your thoughts on moving forward - do you want to move forward, at least tactically in this PR, with these changes piggybacking on syndication, or did you want to go the other way with multiple streams?

@Fryguy I was thinking of going with multiple streams unless there's a huge rush to get this in (though I don't think it'll take that long).  Just haven't gotten there yet

Okay @Fryguy this is functional, ready for review


:memo:  update demo docs

Description
Update demo doc:

keep config in demo homepage align with doc settings
simplify customDirective example for group-by demo

Checklist

[x] My changes follow the contributing guidelines of this project.
[x] I have performed a self-review of my code.
[x] I have made corresponding changes to the documentation.
[ ] ~I have added tests that prove my fix is effective or that my changes work.~
[ ] ~New and existing unit tests pass locally with my changes.~

Coverage: 94.863%. Remained the same when pulling 9a6fe00b08025172762324ef84487b2f09b69396 on doc/update-doc-demo into 0866cd3ca9abbffc0c7e27815d2ed94ef8408999 on main.


Upgrades: Upgrade Etcd

To keep the cluster at a consistent well defined state, etcd will also be upgraded when running kismatic upgrade for both online and offline commands.

[x] Publish new "transitional" etcd package, this is required to upgrade old networking etcd from v2.3.x to v3.0.x then to the final v3.1.x versions

This means the whole cluster must be upgraded to 3.0 first then again to 3.1

[x] Fix bug with etcd service not restarting correctly
[x] Will need to place an indicator on node that it has been upgraded to the transition etcd, without it rerunning the upgrade on a failure will fail due to the package conflict

No need to do this as we can rely on the kismatic-version file

[x]  Add new upgrade code for etcd as described in upgrade to 3.0 and upgrade to 3.1
[x] Verify an etcd node has been upgraded and is ready

cluster-health seems to do this fine

[x] Move cert copying to the certs play so it doesnt rerun on upgrades
[x] Test the overall state of the etcd clusters, maybe another step after node-upgrade?
[x] Figure out what happens for an online upgrade when an etcd node has multiple roles and those are ingress, storage - maybe these can be upgraded?

Will need to place an indicator on node that it has been upgraded to the transition etcd, without it rerunning the upgrade on a failure will fail due to the package conflict
Can we detect etcd version using etcdctl instead?

Closed via #331


Nuget package includes package.json and package-lock.json files

As the title suggests the nuget package contains these files as seen in the nusepc file:
    <contentFiles>
      <files include="any/net5.0/package-lock.json" buildAction="Content" />
      <files include="any/net5.0/package.json" buildAction="Content" />
    </contentFiles>

I think you have to explicitly set these files to not be packed into the nuget package similar to how you did it with the favico:
https://github.com/MyNihongo/MudBlazor.Markdown/blob/09d7c3a8127144eb8c3fcb91444f857fdd735e9b/src/MudBlazor.Markdown/MudBlazor.Markdown.csproj#L29-L34

@erri120 thank you for issue. Indeed there is no need to pack package.json and package-lock.json
Now it should be fixed by #14.


Session tracking

Track user session. Assign session id to events / spans
Needs to be elaborated:
Does session persist between page reloads? How?
Should we send a separate event for initializing session?
Anything else?

Let's keep it simple and NOT persist between page reloads. Reload = new session, multiple tabs = multiple sessions
Yes to session start event

Let's make session id easily accessible on the agent.
Q: how to set session id on otel if configured

fixed with https://github.com/grafana/grafana-javascript-agent/pull/52


improvesupport arrays_overlap with invertedIndex

support arrays_overlap with invertedIndex
Proposed changes
Issue Number: close #xxx

run buildall

run p0

run buildall


handling duplicate request names when postman collection import by appending an occurrence count.

Description
fixes https://github.com/usebruno/bruno/issues/1300
postman collection used for testing.json
Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[ ] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

@lohxt1 please review this.

Closed since this was addressed in #1300


added standard mobile navbar component

PR Title

The purpose of this Pull Request is to fix #161
Screenshots

Checklist

[ x] I have Made this contribution as per the CONTRIBUTING guide in this repo
[ x] I have tested in local Environment.
[ x] I have made the fix as per issue conversation
[ x] I have starred the repository ⭐

Look perfect @rakicodes as per requirement
Please also look for other open issues where you can contribute your designs


First commit for merge sort design

Signed-off-by: tyoungsc<EMAIL_ADDRESS>Description
Creating a new FPGA reference design: merge sort
External Dependencies
None
Type of change

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

How Has This Been Tested?

[X] Command Line
We currently don't have a regtest flow to grab from a fork. So I have tested this manually (all three flows) myself.

For some reason, I cannot add reviewers to my own fork, so mentioning you here:
@mdbtucker


Getting closer to shelves

Nowadays we're using the shelves' waypoints for robot's navigation. To execute the pick-up the robot needs to be closer to the shelf. To make robot closer to the shelf, in #116, I tried to change the waypoint x coordinate from 1.61 to 1.37, but with this new coordinate the robot is not able to navigate until this position.
I think this behaviour is due to the obstacles and robot inflation on the cost map, but I was not able to change that on turtlebot2i_navigation/config/costmap_common_params.yaml and make the robot closer to the shelf.

Nowadays we're using the shelves' waypoints for robot's navigation. To execute the pick-up the robot needs to be closer to the shelf. To make robot closer to the shelf, in #116, I tried to change the waypoint x coordinate from 1.61 to 1.37, but with this new coordinate the robot is not able to navigate until this position.
I think this behaviour is due to the obstacles and robot inflation on the cost map, but I was not able to change that on turtlebot2i_navigation/config/costmap_common_params.yaml and make the robot closer to the shelf.

Maybe it is a problem in the grid map. The existing map may not be so accurate as required and needs to be regenerated.

This issue is related to the Issue #122

@jramadeu I updated the map in the branch issue_122. In this map the shelves have a thinner border. Please, check if it works.

@albertohata, on issue #139 i've made some changes that partially solve this issue.
Please take a look there, and if it's possible update this changes on branch issue_112.

@albertohata, on issue #139 i've made some changes that partially solve this issue.
Please take a look there, and if it's possible update this changes on branch issue_112.

@jramadeu I will check that. By the way, you mean issue_122 right?

Sorry. Branch issue_122

Closing as wontfix; the project is finished and the repository is to be archived.


improved button customizer

fixes #40
@Bashamega I have improved the button-customizer
do have a look and merge it :)

Maybe make the button in the center and also make the black background take full width.

Okay sure will do


Change definition namespace scope

fix #918
modified definition related chart yamls,  modified controllers and webhooks for supporting namespace scope definition. The next pr will modify api-server related logic to support namespace definition

Is this a breaking change (not backward compatible)?

Is this a breaking change (not backward compatible)?
Because of the scope field is immutable, users should delete workload/trait definition first then recreate them with namespaced scope. So i supposed to be a workload/trait CR must belong to a namespace

ping @ryanzhang-oss please review again

Good Job, much better now


Missing information from Error Messages

Describe the bug
[05/11/22 16:10:57] [Failed]: Update of ExperienceBundle SDO_B2B_Commerce1: Error: We couldn't validate componentAttributes in SDO_B2B_Commerce1/views/productDetailFlexSpotter.json for component 62df3ca0-8a87-4137-b5da-b824bbf9bf85. Error: attribute [configId]: Invalid value [a0N4S0000000vNaUAI].
Check your file and try again.
Error: Could not process MDAPI response: Update of ExperienceBundle SDO_B2B_Commerce1: Error: We couldn't validate componentAttributes in SDO_B2B_Commerce1/views/productDetailFlexSpotter.json for component 62df3ca0-8a87-4137-b5da-b824bbf9bf85. Error: attribute : Invalid value . Check your file and try
again.
Run this command for more information about debugging errors: cci error --help
Reproduction steps
Have CCI run a deployment to an org, where an error is returned which contains details within square brackets []. The information is then lost when the error is repeated below the deployment. Often happens with Experience Cloud deployments.
Reviewing the bug description submitted. This is an example of what happens. As you can see the attribute has been called out and added within the square brackets [configId] although it doesnt show on the next line where the deploy task has ended.
Your CumulusCI and Python versions
CumulusCI version: 3.57.0 (/usr/local/Cellar/cumulusci/3.57.0/libexec/bin/cci)
Python version: 3.9.12<EMAIL_ADDRESS>Operating System
Mac OS
Windows environment
No response
CumulusCI installation method
brew
Error Gist
No response
Additional information
No response

@GeekStewie What produced the first line of output? Was this in cci's log? And the second line was the error output from the CLI?

Thank you for the report, @GeekStewie, this will be fixed in the next release.


Update docs with compatible config for new rollbar

I ran into this trying to set up ownership + rollbar, the payload was being updated but it wasn't changing which rollbar project my exception was being sent to until I made this change.

Great, thanks @katherinescherr!


Update test and dependencies.

Ï think it is better to use electron for testing when possible and I have also encountered an issue when running the package-lock.json in my system, can you please if this work for you as well?

@alan-wu thanks I will do a fresh install


Improvement: externalizing environment from Angular CLI build process

There is a great article: http://www.jvandemo.com/how-to-configure-your-angularjs-application-using-environment-variables/ about externalizing the environment file from the build. The deployment phase can be responsible for providing the app with the correct environment variables. "Build once - Deploy anywhere".
What I did in my own project to get this to work was to externalize my environment parameters the same way as the article had it. Then I imported those variables in the environment.dev.ts file like so:
export const environment = {
production: false,
environment: window['__env'].environment,
build: window['__env'].build,
siteName: window['__env'].siteName,
};
I also referred to my real environment file in index.html via a javascript import.
I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
No bug
Expected behavior
No bug
Minimal reproduction of the problem with instructions
Environment files are compiled with the app during build phase for Angular CLI. It should [ideally] be outside.
What is the motivation / use case for changing the behavior?
Build once - Deploy anywhere.

Angular version: 2.0.1

Language: [TypeScript 2.0.2]

using window = using dom = not cross platform solution. using Webpack define plugin may be a solution

Using window is not advisable for the reasons @antonybudianto put out.
While I agree there is room for improvement, I don't agree with this approach. It was one of the approaches we considered initially and decided to go with the current one.

Totally understand. That implementation gets the job done for me today. The current solution forces me to build per environment and when you get to more than 5 environments, that turns into a headache.
Looking forward to what you guys come up with! Good work!!

Has anything been decided or discussed for this?  It's very important for me as well to be able to inject configuration after AoT.  In any way, really.  Specific json files dropped into the /dist/ folder, environment variables, ng command line...anything is better than nothing.


Pandas missing from 2.5.1 after build

I was receiving a missing panda module after installing 2.5.1.
Pandas is in the requirements file.
I was able to resolve it by connecting into the docker container cli and running pip install pandas==1.5.2

Also, another issue I had was that I received an error when executing multiple sql statements at one time with the postgres operator. This worked in the previous version.


Production with mangle: true breaks components

In production mode, it's recommended to use mangle: true for UglifyJS. Unfortunately, when we add that option, the mappings of the react components to AEM components gets lost.
Is there a solution for this?

Hello, I made it work by keeping the function names, the file got bigger obviously. Although smaller that development setup.
Here is sample config
mangle: {
    keep_fnames: true
  },
  compress: {
    ...
    keep_fnames: true,
  }

Let me know if you have a better solution for this.

Can you tell me which function names are the problem here? Is it on the server or in the browser? On the server we actually need to keep function names intact, because java makes calls to the JS API (something like AemGlobal.renderComponents). That is probably the issue here. We can probably get around that by explicitly creating an object hash with that function.
AemGlobal = {renderReactComponents : ()=> {....}}

yes, this happens on the server. I haven't tested on the client side yet because it already breaks on the page/server load.
i'll take a look on how to create an object hash of functions.

I turned off uglify on the server but still had to keep the names from being mangled for the client. Anyway, I think this is good enough. 👍
Thanks!


Closing Zen Mode on Windows

Testing #15647
The command palette works super well to exit Zen mode - however for non-command palette users did we consider an action in the editor context to exit Zen Mode.  It's particularly difficult on Windows.
Something here perhaps based on the context.

I do observe that double escape works (eg. lose my selection and then press again) so this could be a non-issue unless we get feedback otherwise.

Closing as designed until users complain.
Also closing vscode and starting again will leave zen mode so I am not worried somebody gets stuck in zen mode forever

There should be an easy to identify graphical button to exit 'Zen Mode'

I was stuck in Zen mode until I found this thread via google - ctl-k z does not work to exit zen mode in the version I'm currently running (1.12.2). Double escape works, but is extremely non-obvious...

It would be better if ctrl+k z works to exit zen mode

THis needs to be addressed

ctrl+k z works to exit zen mode, I just tried it on windows with latest vscode insiders and it works perfectly for me
https://code.visualstudio.com/insiders

If you have vim plugin installed, neither Esc Esc, nor ctrl+k z works.
There should be menu/other way then keyboard.

@rdslw
This is the issue with full screen mode in general.
You should always be able to press F11 to exit full screen mode.


Reorganize the documentation and add plenty of info

@ddeboer  Do you know why this build is failing? https://travis-ci.org/php-translation/documentation/builds/184838341

Solved the build error by removing primary_domain = 'php'


Error: Provider produced inconsistent final plan

Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
0.12.29
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
terraform apply without any error
Actual Behavior
Error: Provider produced inconsistent final plan

When expanding the plan for
module.xyz-abcd.github_branch_protection.this[0] to
include new values learned so far during apply, provider
"registry.terraform.io/-/github" produced an invalid new value for .branch:
was cty.StringVal("master"), but now cty.StringVal("develop").

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Steps to Reproduce
Please list the steps required to reproduce the issue, for example:

terraform apply

Important Factoids
no
References

@kzw is this still happening for your use case? which release of the provider are you using?


template doc, update Java ARM SDK to 2.x

Update the link of Java SDK for template doc to latest track2, as SDK owner.
Alternatively, the link can be https://docs.microsoft.com/java/api/com.microsoft.azure.management.resources?view=azure-java-stable

@weidongxu-microsoft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@weidongxu-microsoft -thanks for this update.
#sign-off


Remove duplicate Visual Studio Code ignore file

Pull Request
Update

[X] Template - Update existing .gitignore template

Details
This PR removes the old and outdated Code.gitignore definitions in favor of the more updated VisualStudioCode.gitignore.
For compatibility's sake, I included a symlink Code.stack to replace the old definition file, to just link to VisualStudioCode.gitignore.
I also removed and moved the VisualStudioCode.patch contents to the main VisualStudioCode.gitignore file since github/gitignore doesn't have Vscode definitions.

Thanks for finding the dupe.  Can you also please undo the change to the VisualStudioCode.gitignore and VisualStudioCode.patch.  The reason for the .patch file is because the build system checks against @github/gitignore for the source of truth.  If our template doesn't match GitHub's the build will fail. .patch files allow gitignore.io to amend GitHub's templates.

Sure! I didn't notice it on Github's repo but it seems to be under /Global there. My bad.

Gotcha, I made the change yesterday and hopefully it's good now!

Ah yeah you are 100% correct.  Sorry I got confused :)


Tuple type does not exist

I tried using this type today and saw an error that said it doesn't exist. Sure enough, there is no variable named Tuple in the component.js. Might be a bug?

opss. sorry that was an experiment, I'll remove asap


How to Receive Bulk Messages from Azure Service bus

In my application all the events are getting stored in Azure service Bus queue, and another component reads that queue and process the events.We are using Azure-servicebus java sdk version 0.9.2.
After processing few thousand events we are getting below Service Bus error.
Caused by: com.microsoft.windowsazure.exception.ServiceException: WRAP server returned error acquiring access_token Response Body: ACS90055: The server has terminated the request (tenant exceeded rate limit). Please wait a few seconds and try again.
Alert me | Edit | Change type
Question
You cannot vote on your own post
0
In my application all the events are getting stored in Azure service Bus queue, and another component reads that queue and process the events.We are using Azure-servicebus java sdk version 0.9.2.
After processing few thousand events we are getting below Service Bus error.
Caused by: com.microsoft.windowsazure.exception.ServiceException: WRAP server returned error acquiring access_token
Response Body: ACS90055: The server has terminated the request (tenant exceeded rate limit). Please wait a few seconds and try again.
It slows down my application. Also I am loosing lot of events.
How to get pass this error ?
How to fetch messages in a batch, Instead of fetching individual call for single message ?
Do we have Batch Receive support for Azure service bus Java SDK ? If no what other way we should follow for Java Application using Azure Service bus.
How to increase the rate limit for my tenant ?
I am using below code to receive all the messages from Queue:
`   ServiceBusConfiguration.configureWithWrapAuthentication(
ServiceBusName,
ServiceBusAuthenticationName,
ServiceBusSharedSecret,
ServiceBusRootUri,
ServiceBusWrapRootUri);
ReceiveMessageOptions options = new ReceiveMessageOptions();
options.setReceiveAndDelete();
ServiceBusContract service = ServiceBusService.create(serviceBusConfig);

ReceiveQueueMessageResult message =
    service.receiveQueueMessage(queueName, options);

   while( message.getValue() != null){

//Process the message .
message =
service.receiveQueueMessage(queueName, options);
   }`

Hi,
You are hitting the WRAP server rate limit because there is a bug in token caching for DELETE message requests. I have created pull request which should fix the issue: https://github.com/Azure/azure-sdk-for-java/pull/666
It should also possible to mitigate this issue by using SAS authentication instead of WRAP authentication.
As for bulk receive requests; the REST API unfortunately only supports bulk send requests. I suggest looking into AMQP if you need higher throughput.

the service bus client library is not in this repo anymore, so if this is still an issue, it should go there:
https://github.com/azure/azure-service-bus-java


Add Panoply v4.2.1

Panoply netCDF, HDF and GRIB Data Viewer

Seeing as url doesn’t point to a specific version, this cask should use version :latest and sha256 :no_check. See an example.

I updated it. Thanks.


Move tool versions into versions.mk

Previously, versions were located at 1, but some were overlooked. This commit consolidates all versions into versions.mk.

By the way, the link in your PR comment is broken. Probably you wanted to link this PR?

By the way, the link in your PR comment is broken. Probably you wanted to link to https://github.com/topolvm/pvc-autoresizer/pull/221?

It seems to be a rendering issue. I fixed it.


Winform Support

Hi,
Thanks for the great package and easy to follow examples.
When I ran a mock model in console application - I get nicely callback output (verbose 1, epoch runs) in the console window. However, when I tried the same in a winform application, there is no output. It still compiles and runs but there is no output.
For eg:
public void PrepareData()
      {
          int batch_size = 32;
          TensorShape img_dim = (180, 180);
          //var data_dir = @"C:/Users/haipi/.keras/datasets/flower_photos";
          var data_dir = @"C:\flowers";
          var train_ds = keras.preprocessing.image_dataset_from_directory(data_dir,  validation_split: 0.2f,
              subset: "training",
              seed: 123,
              image_size: img_dim,
              batch_size: batch_size);

          var val_ds = keras.preprocessing.image_dataset_from_directory(data_dir,
              validation_split: 0.2f,
              subset: "validation",
              seed: 123,
              image_size: img_dim,
              batch_size: batch_size);

          train_ds = train_ds.cache().shuffle(100).prefetch(buffer_size: -1);
          val_ds = val_ds.cache().prefetch(buffer_size: -1);

          foreach (var (img, label) in train_ds)
          {
              print("batch images: " + img.TensorShape);
              print("labels: " + label);
              tbConsole.AppendText("batch images: " + img.TensorShape);
              tbConsole.AppendText(Environment.NewLine);
              tbConsole.AppendText("labels: " + label);
              tbConsole.AppendText(Environment.NewLine);
          }

          int num_classes = 5;
          // var normalization_layer = tf.keras.layers.Rescaling(1.0f / 255);
          var layers = keras.layers;
          var model = keras.Sequential(new List<ILayer>
          {
              layers.Rescaling(1.0f / 255, input_shape: (img_dim.dims[0], img_dim.dims[1], 3)),
              layers.Conv2D(16, 3, padding: "same", activation: keras.activations.Relu),
              layers.MaxPooling2D(),
              /*layers.Conv2D(32, 3, padding: "same", activation: "relu"),
              layers.MaxPooling2D(),
              layers.Conv2D(64, 3, padding: "same", activation: "relu"),
              layers.MaxPooling2D(),*/
              layers.Flatten(),
              layers.Dense(128, activation: keras.activations.Relu),
              layers.Dense(num_classes)
          });
          model.compile(loss: keras.losses.SparseCategoricalCrossentropy(from_logits: true),
          optimizer: keras.optimizers.Adam(), metrics: new[] { "accuracy" });

         model.summary();
         model.fit(train_ds, validation_data: val_ds, epochs: 2, verbose: 1);

      }

I would like to know if there is a way to get the console outputs in a winform application.
Thanks,
Veeru

I've created a PR #764 which could solve your problem.

Hi lsylusiyao,
Thank you for creating  pull request for solving the problem. I have a very stupid (newbie) question, how can I use your code change in my project - should I download the repository, compile and then import the dll into my project ?

I downloaded the repository and tried packing tensorflow.keras to generate TensorFlow.Keras.0.5.0.nupkg in the debug folder of the project but I was not able to install it on my project. I am sure I am missing something, new to this so it will take time. I appreciate your help. Thanks,

It seems that you've already finished compiling and created the useful nupkg. Then you can just search for how to install local nuget package in visual studio and you'll find the answer. :)


Training with Multiproject Importer gives UnicodeDecodeError in Rasa 2.0

Rasa version: 2.0
Python version: 3.7
Operating system (windows, osx, ...): Windows
Issue:
When using multiproject importer and there is any non-text file such as compressed tar.gz file under the directories in config.yml, it gives UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte .
It seems like compared to previous version, Rasa 2.0 does another file read process after ValueError exception under guess_format function while on the previous version it doesn't.
Error (including full traceback):
Traceback (most recent call last):
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\nlu\training_data\loading.py", line 134, in guess_format
    content = rasa.shared.utils.io.read_file(filename)
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\utils\io.py", line 118, in read_file
    return f.read()
  File "c:\users\anaconda3\lib\codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\users\anaconda3\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\anaconda3\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\anaconda3\Scripts\rasa.exe\__main__.py", line 7, in <module>
  File "c:\users\anaconda3\lib\site-packages\rasa\__main__.py", line 116, in main
    cmdline_arguments.func(cmdline_arguments)
  File "c:\users\anaconda3\lib\site-packages\rasa\cli\train.py", line 90, in train
    nlu_additional_arguments=extract_nlu_additional_arguments(args),
  File "c:\users\anaconda3\lib\site-packages\rasa\train.py", line 55, in train
    loop,
  File "c:\users\anaconda3\lib\site-packages\rasa\utils\common.py", line 308, in run_in_loop
    result = loop.run_until_complete(f)
  File "c:\users\anaconda3\lib\asyncio\base_events.py", line 583, in run_until_complete
    return future.result()
  File "c:\users\anaconda3\lib\site-packages\rasa\train.py", line 90, in train_async
    config, domain, training_files
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\importers\importer.py", line 86, in load_from_config
    config, config_path, domain_path, training_data_paths, training_type
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\importers\importer.py", line 146, in load_from_dict
    for importer in importers
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\importers\importer.py", line 146, in <listcomp>
    for importer in importers
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\importers\importer.py", line 190, in _importer_from_dict
    config_path, domain_path, training_data_paths, **constructor_arguments
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\importers\multi_project.py", line 38, in __init__
    self._init_from_dict(self.config, self._project_directory)
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\importers\multi_project.py", line 89, in _init_from_dict
    self._init_from_path(p)
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\importers\multi_project.py", line 59, in _init_from_path
    self._init_from_directory(path)
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\importers\multi_project.py", line 106, in _init_from_directory
    elif rasa.shared.data.is_nlu_file(full_path):
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\data.py", line 201, in is_nlu_file
    return nlu_loading.guess_format(file_path) != nlu_loading.UNK
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\nlu\training_data\loading.py", line 137, in guess_format
    if MarkdownReader.is_markdown_nlu_file(filename):
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\nlu\training_data\formats\markdown.py", line 177, in is_markdown_nlu_file
    content = rasa.shared.utils.io.read_file(filename)
  File "c:\users\anaconda3\lib\site-packages\rasa\shared\utils\io.py", line 118, in read_file
    return f.read()
  File "c:\users\anaconda3\lib\codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte

Command or request that led to error:
rasa train

Thanks for raising this issue, @tmbo will get back to you about it soon✨
Please also check out the docs and the forum in case your issue was raised there too 🤗


Support for customizing kube-apiserver kubelet-preferred-address-types

TenantControlPlane CRD supports extraArgs for kube-apiserver, but customization of --kubelet-preferred-address-types is not working since it is overridden in buildKubeAPIServerCommand function in internal/builders/controlplane/deployment.go.
It would be nice to have a way to customize this option since the default affects proper operation in our environment, where a value of InternalIP,ExternalIP,Hostname is required to make everything work.

Thanks @fchiacchiaretta, we just release a PR addressing this feature request!
Once the test suite is green it will be merged, in the meanwhile, feel free to join the conversation!


SSH keys for GitHub?

This article recommends using SSH keys instead of a credential manager for working with Azure DevOps. Does this recommendation also hold for using GitHub?

I should have seen this:
https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github


Warning when linting FirebaseDatabaseSwift

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.5
Firebase SDK version: 8.2.0
Installation method: CocoaPods
Firebase Component: DatabaseSwift

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
Trying to lint FirebaseDatabaseSwift has a warning:
    - WARN  | xcodebuild:  FirebaseDatabaseSwift/FirebaseDatabaseSwift/Sources/third_party/RTDBEncoder/RTDBEncoder.swift:933:33: warning: cast from 'Encodable' to unrelated type '[String : Encodable]' always fails

This should be investigated and remedied.

Just FYI,the same warning exists in JSONEncoder.swift from apple/swift

I believe that swift is misdiagnosing here.

I'm not able to reproduce. Is there something different in the command?

 $ pod spec lint --skip-tests  FirebaseDatabaseSwift.podspec --sources=git@github.com:firebase/SpecsStaging.git,https://cdn.cocoapods.org --no-clean

 -> FirebaseDatabaseSwift (8.2.0-beta)
    - NOTE  | xcodebuild:  note: Using new build system
    - NOTE  | xcodebuild:  note: Building targets in parallel
    - NOTE  | xcodebuild:  note: Using codesigning identity override: -
    - NOTE  | xcodebuild:  note: Build preparation complete
    - NOTE  | xcodebuild:  note: Planning build
    - NOTE  | xcodebuild:  note: Analyzing workspace
    - NOTE  | xcodebuild:  note: Constructing build description
    - NOTE  | xcodebuild:  warning: Capabilities for Signing & Capabilities may not function correctly because its entitlements use a placeholder team ID. To resolve this, select a development team in the App editor. (in target 'App' from project 'App')
    - NOTE  | xcodebuild:  warning: Skipping code signing because the target does not have an Info.plist file and one is not being generated automatically. (in target 'App' from project 'App')
    - NOTE  | [iOS] xcodebuild:  Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'leveldb-library' from project 'Pods')
    - NOTE  | xcodebuild:  note: Using codesigning identity override:
    - NOTE  | [OSX] xcodebuild:  Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.7, but the range of supported deployment target versions is 10.9 to 11.3.99. (in target 'leveldb-library' from project 'Pods')

Pods workspace available at `/var/folders/f8/780yxvcx2x91wmlsmvyv0bdr00bzqz/T/CocoaPods-Lint-20210617-10851-1a7j68x-FirebaseDatabaseSwift/App.xcworkspace` for inspection.

Analyzed 1 podspec.

FirebaseDatabaseSwift.podspec passed validation.

~/github/firebase-ios-sdk (master) $ xcodebuild -version
Xcode 12.5
Build version 12E262

This popped up in my pod repo push command yesterday when staging the pods.

I believe it's a compiler warning and not the linter. Could that be the case?

The linter should show compiler warnings. I also didn't repro in the Xcode 12.5 and 13 beta-0 UI's

This hasn't shown up in the M99 release process

Hmm, I'll close it for now until I can reproduce it locally. Thanks Paul for checking in on it.

Edited Xcode version in description to 12.2 which is required for the failure - and reopening.
Weird that the warning goes away with more recent Xcode versions?
@ryanwilson So is it an Xcode bug that we can disregard?

Sorry about the incorrect version. I think it's fine to close this and see if anyone complains about it, probably safe to disregard given it's not visible in the most recent (and more used) Xcode versions.


Roadmap and changelog

References #36.
Roadmap
See Wikipedia explanation.
Purpose of a roadmap is to set goals and expectations. Roadmap sets focus and drives excitement. Roadmap does not dictate every single change but rather lists known immediate upcoming changes and tries to define more distant changes - a wishlist in its simplest form. After a release roadmap should almost from word to word be in changelog.
Current state of docker-alpine project is that there is no roadmap. Releases are sporadic, which is fine and understandable considering this is a community project, but more problematic is the what is needed for a release to happen. While a release could happen, especially with automation, after every single change to set goals and expectations might be preferable. Having a roadmap should also alleviate pressure from release master as there are now more clear definition of when to release.
I propose GitHub milestones feature to be used. All issues are to be triaged and then moved to a milestone, comments requested or closed. This process should be as lightweight and quick as possible.
Changelog
Example that I like: https://github.com/hashicorp/consul/blob/master/CHANGELOG.md.
I propose a simple changelog based on roadmap (or more specifically milestones). If changes are issues and issues have meaningful context (so far they have) then I do not see a point to write again what was changed, why etc.
Note: docker-alpine project due to it's multiple release numbers (one per image) does pose a challenge. In order to simply versioning moving to one release number for all, even if no change is done, might be in order. Then in changelog we could just note
NO CHANGE LIST:
alpine-nginx-nodejs
alpine-nginx

I do acknowledge that doing a release with no changes is curious thing, but I believe it simplifying things outweights the negative.

@matthewvalimaki, I'm definitely down with the Roadmap. I think that would be a great idea.
It would be good to discuss releases (on Docker Hub) a little more. They're quite time consuming and manual at the moment. Docker Hub functionality is quite limited especially when it comes to automated repositories. It would be great to work out a way to streamline lines. I think I'll document a seperate issue to discuss this specifically.
Regarding the CHANGELOG: yeah, that's a tricky one too. Do you like the current versioning as it is explained here https://github.com/smebberson/docker-alpine#versioning? I'll admit that new people coming into the project could find it confusing. Take for example the Node.js containers, they update frequently. And once I go through and update the base images all node.js 4.x releases and node.js 5.x releases won't be on the same alpine-nodejs X.x path (if that makes any sense). Maybe the versioning needs to be rethought? Maybe we keep the version numbers as they are for each image, but move away from versioning for the entire repository. Eric Elliot explains it better than I can. More food for thought...

I've created #38 to discuss testing and automated releases.

@smebberson thank you for the thoughtful response. Clearly you've given this some thought. I'll think about this more and come back to it.

@matthewvalimaki, another idea here is to rename each VERSIONS.md file to CHANGELOG.md (that should have been the case in the version place). The CHANGELOG would list the version number of the image itself and what has changed, just like a traditional changelog. Then in the VERSIONS.md file we could create page that simplifies upgrade paths for people - like I was aiming to do with https://github.com/smebberson/docker-alpine/blob/master/alpine-consul-nodejs/NODEJS.md (so information is grouped by the primary software version number, i.e. Node.js or Nginx).


IDS camera driver with MM1.4

Lars,
I was able to use my IDS camera (U3-3140CP-M-GL) with your driver on MM 2.0. However, I have a different application that require MM 1.4, any change to the driver work on 1.4 version?
Humberto
Originally posted by @humberojoca in https://github.com/Lars-Kool/MM_IDS_Peak/issues/1#issuecomment-1994769993

Hi Humberto,
I've never worked with MM1.4, and I'm not sure which changes would need to be made to the driver to make it compatible with MM1.4. Sadly I'm not planning to make the driver work with MM1.4, as I don't have the time to do this.
I'm sorry for the inconvenience.
Best,
Lars


Fix the removal of Thunk and add/remove some features

This is a rustup. Should fix #18

Please bump version - then we'll merge


fix: pass healthchecks config to Utapi

fix #373

@ironman-machine

Hello @rahulreddy
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "fix/utapiHealthcheckConfig2", "DEFAULT_BRANCH": "rel/6.2.1"}
Please follow http://ci.ironmann.io/gh/scality/Integration/6428 for CI status.


Dotnet SDK path mismatch to VSCode suggested location

https://github.com/Azure-Samples/azure-sql-library-app-blazor/blob/20dcf6858a7ccbba15dbed17769df754823052b1/.devcontainer/devcontainer.json#L27
VSCode suggests that the path be: /usr/share/dotnet and not include the sdk folder, since there doesn't seem to be a dotnet.exe in the sdk folder.

This affect building the Blazor project

Thanks, this issue was fixed under commit: fb0b7530251e42da4a6455317bf8f1377fc1c31c

Hey @croblesm , this issue is opened up on the latest code you merged in this commit https://github.com/Azure-Samples/azure-sql-library-app-blazor/commit/20dcf6858a7ccbba15dbed17769df754823052b1.
The path doesn't align with suggestion by VSCode.

Can you reopen?

Hi @seantleonard,
Could you please try building / publishing the Database project using this configuration? I'm using this path in multiple dev containers and the build/publish works just fine whether I do it from command line or the UI.

Using command line

using UI

Build