Does Stylet.Start scaffold package supports .net 5?

I don't prefer to use command line for creating project in windows visual studio.

Stylet.Start only supports .NET Framework, not .NET Core (and .NET 5 is just reskinned .NET Core, although I should make that clearer in the docs).
I'm not sure whether Stylet works on .NET 5 (need to test), but you will need to use Stylet.Templates. As of recent VS 16.2 Preview 8, there's an option to make the CLI templates show up in the New Project window.

OK, thanks.


Add a CLI argument that gets all song names for artist

Adding the CLI argument -ls or --listsongs should print all song names for the randomly selected artist instead of printing/tweeting lyrics.
If the user sets a predefined artist with -a/--artist then print all song names for that specific artist

Hi there! I would like to give it a try to this issue!

Good luck with the task! 😄 And don't forget to handle the case with -a/--artist

Just a quick question, is it possible to use this package https://pypi.org/project/azlyrics/ ? Or you prefer to interact with azlyrics programmatically?

This project started as a challenge to try and imitate packages like this 😅 so you'll have to interact with azlyrics programmatically.
Your approach makes more sense but it's not the purpose of this project.

Understood completely! I regretted it as soon as I posted the question, that's why I deleted the question. Just trying to type the less possible :stuck_out_tongue_closed_eyes:
Anyway, it is almost ready, and currently testing.
Thanks!

Sorry again.. I have tried to push my new branch to your repo but I keep getting an error message:
ERROR: Permission to MohamedYasser97/lyricurator.git denied to jbarbaran.
I have double checked that my SSH account is correct, and it seems it is ok. Do you have to add me as a contributor? or is it automatically done?
Thanks!

Happens to the best 😆


Rename the board's layer

It was using an incorrect name.
Changelog-Entry: rename the board's layer

@floion  @acostach seems that I missed this when we renamed things and we did not noticed it later on :-/


Add Mayhem

Added a Dockerfile for fuzz testing
Added Mayhemfile(s) for fuzz testing
Added a mayhem.yml file for automatically running fuzz tests with Mayhem using the mcode action

@nottirb This action is failing:
https://github.com/mayhemheroes/risingwave/runs/7532414112?check_suite_focus=true
According to the output, I believe the simple fix is to make sure that the package stage of the Dockerfile installs openssl and pkg-config. Could you please open another PR resolving this? I'll get it reviewed once I see it.

@nottirb This action is failing: https://github.com/mayhemheroes/risingwave/runs/7532414112?check_suite_focus=true
According to the output, I believe the simple fix is to make sure that the package stage of the Dockerfile installs openssl and pkg-config. Could you please open another PR resolving this? I'll get it reviewed once I see it.

I'll look into this, and open another PR when I get it fixed. Thanks for bringing it to my attention!


install: implement --backup (and -b)

GNU man pages says:
       --backup[=CONTROL]
              make a backup of each existing destination file

As ride along, it is possible to implement -b
-b     like --backup but does not accept an argument
Note that src/uu/mv/src/mv.rs has backup support and
we should not duplicate the code.
Instead, we should use src/uucore/src/lib/features

is someone working on this? i’m looking for a first bug to tackle and ran into this myself, seems like it should be reasonably straightforward and i agree it feels worthwhile to try and reuse this functionality if possible.

Hi Alan,
I wanted to work on it but got sidetracked by other projects. Feel free to tackle it, I'll gladly do code review if you want.
Regards,
Lukas

On 7. Apr 2021, at 07:27, Justin Alan Ryan @.***> wrote:

is someone working on this? i’m looking for a first bug to tackle and ran into this myself, seems like it should be reasonably straightforward and i agree it feels worthwhile to try and reuse this functionality if possible.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

@bitmonk Are you working on it?

Hello,
I don't mean to be rude but I have attempted to implement the --backup option here in case anyone is interested. Unfortunately I started coding before I actually read the discussion to this issue...
Are you still working on this, @bitmonk?

I have a stale attempt at this, I got stuck trying to genericize this behavior, then as I mentioned above, decided it was probably not worth it with only two commands having a --backup functionality.
Yours looks great at a glance, would love to chat about what it might take to address this deviation from the manual: master...Funky185540:install-implement-backup?expand=1#diff-f64dac8ba1

I have a stale attempt at this, I got stuck trying to genericize this behavior, then as I mentioned above, decided it was probably not worth it with only two commands having a --backup functionality.

Well in fact there are at least 4 commands in the coreutils that use the --backup option: mv, cp ln and install. And they all use pretty much exactly the same code and options for it, too.

Yours looks great at a glance, would love to chat about what it might take to address this deviation from the manual:

Thanks, appreciate it! I already have an idea for a "fix" to this deviation. I wanted to open another PR and refactor the "backup_control" a little. If you feel like it you can have a go, too, then we can compare and maybe fuse our codes together... ?
See how it fares against the critics here... :)
IMO the interface to determine_backup_mode needs to be rewritten such that it accepts the "long" and "short" backup options (the bool returned from 'is_present' or what it's called) separately, as these have a different behavior according to the GNU docs. Then, if '--backup' is supplied, we:

Check if it has an argument supplied. If so:

Match (this calls for a regex) against the values that the GNU manual allows for the backup type
If there's a match: Take that. If the match is ambiguous: Reject it, print error. If there's no match: Error as well

If there's no argument, check if the env var mentioned in the manual exists
If neither exists, use the default

If there's no long option but only the short one, default to "existing" type. If both the long and short option are supplied (!), the long option always takes precedence.
Then I'd also like to add a new function (maybe call it backup_file) that then performs the actual backup. This is (as far as I could determine today) needed for all utilities that offer the '--backup' option. That way we would have the backup process streamlined, because if you look at what "mv" does, you'll see it has it's own wrapper around fs::rename that contains failsafes and falls back to "copying and deleting" the files to make backups in case fs::rename fails. Now I don't know why fs::rename may fail but "copying and deleting" wouldn't, but it's interesting to see. It also seems to consider and react to some other corner cases...
The backup-implementation for ln on the other hand (that also has '--backup') really only calls fs::rename, without failsafes or other strings attached.
This could be streamlined I think, as the process of "backing up a file" is always the same.
Well those are just some thoughts. Like I said, I'll make a PR for this in the next few days and see how these changes integrate with the CLI programs I mentioned above. Of course, you're more than welcome to make a different implementation, add to this and throw in some arguments yourself. I'd be curious to hear what you think about it, as you have already worked with the code, too!
I'm still very new to rust, and I find this so very exciting... :-)

Happy to see the interest!

See how it fares against the critics here... :)

We critics look forward to your submission(s). 😄

Then I'd also like to add a new function (maybe call it backup_file) that then performs the actual backup. This is (as far as I could determine today) needed for all utilities that offer the '--backup' option. That way we would have the backup process streamlined, because if you look at what "mv" does, you'll see it has it's own wrapper around fs::rename that contains failsafes and falls back to "copying and deleting" the files to make backups in case fs::rename fails. Now I don't know why fs::rename may fail but "copying and deleting" wouldn't, but it's interesting to see. It also seems to consider and react to some other corner cases...

On various platforms, file renames across file system boundaries will usually fail. Most times, it's not easy (or possible) to determine if the source and destinations are on the same file system. Hence, copy and delete is used as a fallback strategy.

This could be streamlined I think, as the process of "backing up a file" is always the same.

If it's common across utilities, we could add backup_file(...) as feature-gated functionality to uucore.

@bitmonk have you had a shot at the --backup behavior yet?

@Funky185540 - just catching up, here, it sounds like you are way deeper into this than I've gotten and I'd love to contribute to your WIP. Don't forget you can open PRs against branches, so you can leave your current PR intact if it's working, and create a refactor PR against it. I do this sometimes based on my experience of completely destroying WIP. :)

Cool trick, thanks! ;)

I think @rivy's feedback here is really useful, and I'd love to peek at your next PR. It seems like you're moving at a faster pace than I am, so I don't want to gum up the works.

I've opened the PR for the improved 'backup option handling' just yesterday: https://github.com/uutils/coreutils/pull/2467
I'm currently trying to add proper tests to it, but that doesnät work for reasons I don't understand yet...

Same! Part of why my WIP here got stale is I decided to work through some of, "Practical Systems Programming in Rust", so that I'd have better reflexes working through this larger, real-world codebase.
Looks like you're doing great! I'm happy to help however I can!

I totally understand that. I've been wanting to contribute to some FOSS project for a long time, so I decided I'd do it to learn how to code rust. But we all learn differently, right? And that's fine.
So as I see this there are 2 more points to get the backups 'right'.
Improve the backup suffix determination
This is slightly off-topic for this particular issue, but I'll leave it here anyways
This should be a simple one as it only parses either a CLI argument or and env variable. I noticed that there is something odd in the current implementation, because what happens e.g. if you add a path separator into the suffix? So you could give it a suffix of "~/~", which would imply to move the file to backup to a whole different subfolder.
I haven't checked the C implementation, but I did some quick tests with e.g. cp or mv and their -S option. Here's an MWE to give you and idea of what I mean (using the default C utilities):
$ mkdir /tmp/playground && cd /tmp/playground
$ mkdir dest
# So backup works immediately
$ touch a dest/a
# Sanity check, creates "dest/a~"
$ cp -b a dest/a
$ ls dest
a  a~
$ rm dest/a~
# Invalid!
$ cp -b -S "foo/bar~" a dest/a
$ ls dest
a  a~
# Valid
$ cp -b -S "suffix~" a dest/a
$ ls dest
a  a~  asuffix~

Interestingly the erroneous suffix doesn't cause an error, it just silently falls back to the default suffix '~'. It might be worth checking the GNU implementation to see if they handle any other special cases that I haven't thought of yet.
Perform backups
Like @rivy said, it would be cool to have a backup_file function that does the backing up for us. I have started working on this here: https://github.com/Funky185540/coreutils/tree/backup_control_perform_backups
I thought that as it handles files, directories and symlinks, I'd call it perform_backup instead, but that's more of a detail than a feature. The code is mostly taken from what mv has already implemented. It still needs tests, and it'd be cool to have some file I/O expert look over it to tell us whether we forgot some OS-specific corner cases.
Apart from that I'd say that the backup functionality is good to go. Once these changes are in we can refactor the utilities using it to use the same code, instead of their own implementations.
If you want to pick either of these, or both, feel free to do it! I think that once this is done I'll have a stab at the SELinux context options (-Z and --context), because as far as I can tell these aren't implemented in most (all?) of the utlities.

I think the issue can be closed as it has been implemented with #2457.


Fix close process

#343 after more, close #206
maybe some #269 #123

It'll be cool to test that we're not regressing on Mac.

It looks like these commits related to "close process" have caused some issue on OS X. See #467.


save the RTT with the session ticket, for non-0-RTT tickets

For 0-RTT session tickets, we save the RTT in the session ticket: https://github.com/quic-go/quic-go/blob/cb3453db2508eedf4ea3ce49f86bbe029de5c1c9/internal/handshake/crypto_setup.go#L483-L489
We could do that as well for non-0-RTT tickets, allowing for a faster session resumption. This makes sense to implement once we have the new crypto/tls API (#2727).

Blocked on the new 0-RTT API (mostly to avoid merge conflicts). Once we have this, this would be a good first issue.

Hi @marten-seemann, is there anyone working on this?

Not that I'm aware of. Want to submit a PR? Happy to review :)

Thanks for the fast reply! I'll have a try this week.

Hi @marten-seemann , I have made it work for go 1.21 but I find it is hard to implement for go 1.20 due to the current api provided by qtls-go1-20. Should I submit a PR to the qtls-go1-20 package for this?

No need to. We don't need to optimize for old versions. Of course, we need to make sure that both are still interoperable though.


CUE documentation should talk about whether terser diffs are selling point

You know, like what git-diff would say about an item added to a list. How many lines does the underlying diff engine think has changed.

This issue has been migrated to https://github.com/cue-lang/cue/issues/96.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


@http directive

This will be helpful to connect to remote endpoints, or even the custom endpoints the user creates on his side, through GraphQL.

Skipping HTTP for now.


nDRandom_ideas

Idea for documentation

It can generates a random coordinates in n-th dimensions employing a single random numbers.


include-files.lua fails with relative path if not executed from the main document directory

All relative paths are processed relatively to the working directory.
Relative path in a document (main source file) are obviously relative to the directory of this document.
So the filter works only if the working directory (from which the pandoc command is run) is the directory where the main document is stored.
This should be easily fixed if we could access to the sourcefile variable set by Pandoc (see Pandoc's manual).
I was not able to figure out how it can be accessed from a lua filter.
NB1. I suspect the same restriction applies to include-code-files.lua
NB2. With this restriction we can not even build clean test cases with all files stored in a test subdirectory

Absolute paths are fine, but the line 86 local fh = io.open(line) of the lua filter does not support non-Latin paths.

I found a solution.
I modifyed the code a bit but didnt came to the moment to create a PR:
My modification looks as followed:
    local path = pandoc.path.directory(PANDOC_STATE.input_files[1]) .. "\\" .. cb.attributes.include
    local fh = io.open(path)
    if not fh then
      io.stderr:write("Cannot open file " .. path .. " | Skipping includes\n")
    else
      ...

When i am done with my exams I will do a PR

I have solved it with the help of ChatGPT.

-- block-auto.lua
function RawBlock(raw)
  -- 根据嵌入的格式匹配相应的过滤器
  local filters = {
    markdown = pandoc.read(raw.text, 'markdown').blocks,
    html = pandoc.read(raw.text, 'html').blocks,
    latex = pandoc.read(raw.text, 'latex').blocks
  }
  -- 返回匹配到的过滤器的结果，如果没有匹配到，返回原始块
  return filters[raw.format] or raw
end

function CodeBlock (cb)
  -- 根据嵌入的格式匹配相应的过滤器
  local filters = {
    ["insert-markdown"] = function (path)
      local blocks = pandoc.pipe("pandoc", {"-f", "markdown", "-t", "markdown", path}, "")
      local doc = pandoc.read(blocks, "markdown")
      return doc.blocks
    end,
    ["insert-html"] = function (path)
      local blocks = pandoc.pipe("pandoc", {"-f", "html", "-t", "json", path}, "")
      local doc = pandoc.read(blocks, "json")
      return doc.blocks
    end,
    ["insert-latex"] = function (path)
      local blocks = pandoc.pipe("pandoc", {"-f", "latex", "-t", "json", path}, "")
      local doc = pandoc.read(blocks, "json")
      return doc.blocks
    end,
    ["insert-docx"] = function (path)
      local blocks = pandoc.pipe("pandoc", {"-f", "docx", "-t", "json", path}, "")
      local doc = pandoc.read(blocks, "json")
      return doc.blocks
    end
  }
  -- 创建一个空的结果列表
  local result = {}
  -- 遍历代码块中的每一行
  for line in cb.text:gmatch("[^\n]+") do
    -- 假设每一行都是一个文件路径，尝试匹配相应的过滤器
    local matched = false
    for class, filter in pairs(filters) do
      if cb.classes:includes(class) then
        -- 如果有匹配到的过滤器，调用它并将结果添加到结果列表中
        local blocks = filter(line)
        for _, block in ipairs(blocks) do
          table.insert(result, block)
        end
        matched = true
        break
      end
    end
    -- 如果没有匹配到任何过滤器，就保留原始内容，并将其作为一个段落添加到结果列表中
    if not matched then
      table.insert(result, pandoc.Para({pandoc.Str(line)}))
    end
  end
  -- 返回结果列表作为新的代码块内容
  return result
end

Instructions:

```{.insert-html}
D:\Research\R\Project\output\report.html
```

```{.insert-markdown}
D:\Research\R\Project\output\report.md
```

```{.insert-latex}
D:\Research\R\Project\output\report.tex
```

```{.insert-docx}
D:\Research\R\Project\output\report.docx
```


Implement support in Java for shared memory buffers

I started implementing a SharedMemory class in Appose Java, which is a direct translation of Python's handy multiprocessing.shared_memory.SharedMemory class. It leans on JNA for the low-level system calls. But it is not yet fully working. This needs to be finished, so that we can share memory easily between processes!
I'm hoping the JNA-based approach will work directly. But other options include:

Add support for shared memory buffers to the LArray library—work already started by @mkitti on a branch
Write our own small C library and ship it in the Appose Java JAR

HEllo Curtis,
I just finished implementing shared memory IPC communication on the JDLL side:
https://github.com/bioimage-io/JDLL/blob/python-appose/src/main/java/io/bioimage/modelrunner/tensor/SharedMemoryArray.java
I have used jna-platform which contains a ready to use JNA for kernel32 and posix methods (what cpython uses for multiprocessing.shared_memory).
I had the urgency to implement it because when I tried to send relatively big images through the pipes it would take too much time. Changing to shm works great and has a huge performance improvement as the information sent by the pipes is way smaller now.
I did not change anything on the appose implementatio, I just carefully desigined the inputs that I sent to appose from JDLL and the outputs of the Python worker.
JDLL creates a script that is able to recreate the imglib2 array of the Java side:
# Create the shared memory object pointint to the shm block of interest with the wanted size
input_06112023_151243_shm_a9b8d59c_0087_4394_a9dd_fb54e23235e6 = shared_memory.SharedMemory(name='b024e140-5780-4ec6-a45d-f51cfa2ce3e7', size=20545536)

# Recreate the data array with the data from the shm block
input_06112023_151243 = xr.DataArray(np.ndarray(5136384, dtype='float32', buffer=input_06112023_151243_shm_a9b8d59c_0087_4394_a9dd_fb54e23235e6.buf).reshape([1, 304, 512, 33]), dims=["b", "y", "x", "c"], name="output")

All the code above is then fed to the Python worker to be executed, as you can see the memory location, size and shape is hardcoded on the JAva side (done here)
Then once the result is obtained, on the Python side, the shm block is created and the info to access that memory block is sent to java together with the data type, shape and whether is fortran order or not.
On the Python side:
shm_out_list = []
def convertNpIntoDic(np_arr):
  shm = shared_memory.SharedMemory(create=True, size=np_arr.nbytes)
  aux_np_arr = np.ndarray((np_arr.size), dtype=np_arr.dtype, buffer=shm.buf)
  aux_np_arr[:] = np_arr.flatten()
  shm_out_list.append(shm)
  shm.unlink()
  return {"data": shm.name, "shape": np_arr.shape, "appose_data_type__06112023_151246": "np_arr", "is_fortran": np.isfortran(np_arr), "dtype": str(np_arr.dtype)}

def convertXrIntoDic(xr_arr):
  shm = shared_memory.SharedMemory(create=True, size=xr_arr.values.nbytes)
  aux_np_arr = np.ndarray((xr_arr.values.size), dtype=xr_arr.values.dtype, buffer=shm.buf)
  aux_np_arr[:] = xr_arr.values.flatten()
  shm_out_list.append(shm)
  shm.unlink()
  return {"data": shm.name, "shape": xr_arr.shape, "axes": "".join(xr_arr.dims),"name": xr_arr.name, "appose_data_type__06112023_151246": "tensor", "is_fortran": np.isfortran(xr_arr.values), "dtype": str(xr_arr.values.dtype)}

The dictionary returned is then used by the following Java method to recreate a JDLL tensor or ImgLib array:
https://github.com/bioimage-io/JDLL/blob/cdf5469f0405be6aabc30d7380ba0f4c1baf2a11/src/main/java/io/bioimage/modelrunner/tensor/SharedMemoryArray.java#L422
Performance is improved greatly (at least on my old laptop) because the stdout does not need to flush millions of numbers and the result looks like the following:
https://twitter.com/carlosg91018370/status/1721526937686868443
A similar logic dould be implemented in Appose to support sending more high level objects such as numpy arrays or imglib2 images.
Regards,
Carlos

This issue has been addressed by apposed/appose-java#5. Big thanks to @tpietzsch and @carlosuc3m for their efforts. :beers:

And for the record, the Python implementation maintains feature parity with Java thanks to apposed/appose-python#1.


feat: Added Nginx config and Dockerfile

Added updated Nginx config and Dockefile to build custom Nginx image.
For what:

For better app logging

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5948

Relevant Lines:
6787

💛  - Coveralls

Thanks @AliakseiMalyshau
How can we test or run the service with the same environment as aws codebuild? same question for all the other services


Optimised trajectories

In addition to my pull request #16 for brute force computation of optimal trajectories, I've also implemented a combinatorial optimisation feature using the python API for Gurobi, a commercially available optimisation package.
This is significantly more powerful, but adds a dependency to the library.
Is there any appetite for including this within the feature set?

The gurobi combinatorial option was added in #51.  The open-source option remains an open challenge...


Adds additional sample deployment

Description

Requested by Andy R

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 5e69cf4532207cb070538d21f5b91d6b33140016
https://deploy-preview-2350--calico.netlify.com

Deploy preview for calico ready!
Built with commit 5e69cf4532207cb070538d21f5b91d6b33140016
https://deploy-preview-2350--calico.netlify.com


[RAC] Calendar: cells who are unavailable get aria-disabled, but not data-disabled

Provide a general summary of the issue here
CalendarCells that are filtered by isDateUnavailable only get aria-disabled, but not data-disabled.
🤔 Expected Behavior?
data-disabled should also be true.
😯 Current Behavior
states.isDisabled from useCalendarCell is false
💁 Possible Solution
  isDisabled = isDisabled || state.isCellDisabled(date);
this line seems to be the culprit from useCalendarCell
🔦 Context
No response
🖥 Steps to Reproduce

Visit Calendar/RangeCalendar
Go to Unavailable dates section and inspect unavailable dates cell

Note:
Somehow the unavailable weekend dates in calendar get data-disabled.
The unavailable dates in the weekday do not
Version
1.1.1
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
MacOS
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Unavailable and disabled are distinct states, so they use different data attributes (data-unavailable and data-disabled). Aria-disabled is an implementation detail for screen readers and shouldn't be used for styling.


Ports

Can the ports be added to this article? I only see ports on technet, not docs.microsoft.com
https://social.technet.microsoft.com/wiki/contents/articles/34407.sharepoint-2016-step-by-step-installation-of-workflow-manager.aspx

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

ID: eb30d62f-9a48-d8c2-a755-161611c2399f
Version Independent ID: c7f7e286-1d24-6e60-91e2-503cd53b8c36
Content: Deploy Office Online Server
Content Source: OfficeOnlineServer/deploy-office-online-server.md
Product: office-online-server
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

This is documented at:
https://docs.microsoft.com/en-us/officeonlineserver/plan-office-online-server

Created a Pull Request with cross link. Thanks. https://github.com/MicrosoftDocs/OfficeDocs-OfficeOnlineServer/pull/9


Backup Naming

I like the changes you made to allow including the version. I would suggest one change to use "version" instead of "latest_version"
theversion=$(ha core info --raw-json | jq -r .data.version_latest)
I noticed when I did a manual backup "before" updating to 0.111.0. The backup of 0.110.6 was labelled as 0.111.0
Thanks for your efforts

Fixed in v2.1


⚠ Bofrost.de has degraded performance

In 0fcb83e, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1388 ms

Resolved: Bofrost.de performance has improved in bdbc8ed after 34 minutes.


Update to 280 Characters

Not an issue. But i love this Chrome extension so much since 2010. I have been using this at my office and home whenever i am working on my laptop. Please update the extension to show the entire 280 characters. As of now it gives an extended link which opens on twitter.com . Clicking the link pretty much defeats the purpose if i have to use twitter web client

Try using it in detached mode:
chrome-extension://cggngiphndchpmlighpenhejheolmeod/popup.html?detached
I would love to see those tweets without line break, which consumes lots more of screen realstate thou.

Try such patch on local copy of extension:
280.patch.txt

I am sorry, i am not so technical. How do i do that ?
On Wed, Nov 8, 2017 at 3:25 PM, Arkadiusz Miśkiewicz <
<EMAIL_ADDRESS>wrote:

Try such patch on local copy of extension:
280.patch.txt
https://github.com/cezarsa/silver_bird/files/1455303/280.patch.txt
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cezarsa/silver_bird/issues/437#issuecomment-342948103,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVYIoWpJ4uFRfTn4wVRXwqanME-g12d_ks5s0g4sgaJpZM4QW66l
.

I mostly have this fixed I think in a fork of this.
I don't think it works on DMs or Favorites, but it seems to pull in tweets ok. I don't use it to send out tweets so no idea if that works with the extended limit.
Changes are what is in @arekm s txt file though it was not quite the same as apparently that is a different version.
working fork more or less:
https://github.com/rdyar/silver_bird
install directions - start at step 6:
https://stackoverflow.com/questions/16680682/how-to-modify-an-extension-from-the-chrome-web-store


Problem when embedding: Legend not fully visible with the tooltip

We are currently looking at how the graphics appear on the website. We found the following problem :
In the line charts, the legend via the tooltip is always aligned centrally above the current year. This means that the legend is cutted to the left or right if years are selected at the beginning or end of the axis.
With the bar chart, on the other hand, the legend is automatically placed correctly.

How it looks like in AEM :

Ok by Bar chart

Hi @ortnever, we recently changed the way we position tooltips in case of segmentation being active. This problem should no longer exist – please feel free to re-open the issue if that's not the case.


[Umbrella][Sort] Sortstandalone support switch metadata acquire mode

Describe the proposal
Enable sortstandalone switch metadata acquire mode by configurationto
Task list

[x] #10526
[x] #10527
[x] #10528
[x] #10529
[x] #10540
[x] #10555

InLong Component
InLong Sort
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

All tasks have been completed.


Fix SynologyDSM sensor TypeError if network_sensors value is None

Breaking Change:
None
Description:
Fix this log :
2020-01-12 12:24:56 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/Users/XXX/dev/home-assistant/homeassistant/helpers/entity.py", line 284, in async_update_ha_state
    self._async_write_ha_state()
  File "/Users/XXX/dev/home-assistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
    state = self.state
  File "/Users/XXX/dev/home-assistant/homeassistant/components/synologydsm/sensor.py", line 237, in state
    if self.var_id in network_sensors:
TypeError: unsupported operand type(s) for /: 'NoneType' and 'float'

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

Actually fix #30048


How does this gem differs from Rails strict_loading?

Thanks for the great work on this gem.
Can we compare more in depth why would this gem be useful given that Rails strict_loading exists? (and maybe we can add it to the Readme)
For me, I understand that strict_loading prevents all kinds of lazy loading, which includes n+1 issues but also includes other things, it is very hard for me to pinpoint how those 2 cases diverge
In other words: what are lazy loading cases that will throw exception in strict_loading but are NOT N+1 issues?
Plus, any other points you think are handled better in Prosopite
Thanks

If you are like me, and weren't familiar with strict_loading, it was added in Rails 6.1

https://github.com/rails/rails/pull/37400
Rails has added strict loading mode to prevent lazy loading | Saeloun Blog

Thanks, I know about strict_loading and many resources cover it well, but I hope the author of the gem (or someone) can explain how Prosopite is different than Rails strict_loading and what are the benefits of using it instead.

Interested in hearing more about the differences as well

@aelkoussy I came across this https://github.com/learningtapestry/lcms-engine/issues/151#issuecomment-765330664 , hope it helps

I just learned about strict_loading today. What do I gain from using prosopite vs strict_loading? You can enable strict_loading globally and every n+1 will be detected right? Or does prosopite do something else?


Image License

https://github.com/denoland/deno_website2/blob/master/public/v1.png
I've been asked for permission to use this illustration for blog posts etc.
I think it would be a good idea to license this illustration to MIT. What do you think? @ry

Yes that's good.


Improve Connection header for WebSocket reverse proxy

Type of Change

Tool Source: Config generator (general.conf.js, proxy.conf.js)

What issue does this relate to?
Reverse Proxy always sends Connection: upgrade header.
What should this PR do?

add nginx map to general.conf
use map variable in proxy.conf

With this change nginx will only forward Connection: upgrade when the client sets Upgrade.
As far as I am aware this is a cleaner way of forwarding the Connection and Upgrade headers.
Reference: https://nginx.org/en/docs/http/websocket.html
What are the acceptance criteria?

[ ] Double check if my understanding of the upgrade mechanism is correct.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism
https://tools.ietf.org/html/rfc7230#section-6.1

[x] The highlight feature also highlights the line above the added config. Not sure why.

Hey, @m1ckey - Thanks a ton for this sweet PR! 😄
Would you please shoot me an email when you get a chance?
mcowley at digitalocean dot com 🎉

Would you please shoot me an email when you get a chance?

I sent you a email, however, I am not sure if it got through.
If it's still relevant, you can find my email address in my profile ^^


Deploy chart with more than one replica fail webhooks

Bug description
When I deploy the chart with more than one replica, the webhooks only start listenting in the leader. This causes that when requests are started and reach the replica, it returns a 500 error connection refused because the webhooks have not been deployed.
The reason is because the chart deployment create an empty secrets (ca-secret and tls-secret) and the manager container that has been set leader, in first init, detect the empty secrets, creates certificates and fill secrets with them. After this process, the manager container will be restarted automatically but the replicas not, that causes the webhooks never start in replicas until deployment/pod restart and detect secrets with certificates filled.
I tested fill the secrets in chart before install it and it works fine because all replicas start with the secrets filled.
How to reproduce
Steps to reproduce the behavior:
Set default chart values and change replicaCount: to more than one replica.
Expected behavior
The webhooks will be start in all replicas for answer the requests in HA.
Logs
Logs of manager container that has been elected leader in first execution:
[bash]$ k logs --previous capsule-controller-manager-946d5bb5f-4xfbn -c manager -n capsule-system
{"level":"info","ts":"2021-08-27T10:34:12.422Z","logger":"setup","msg":"Capsule Version  "}
{"level":"info","ts":"2021-08-27T10:34:12.422Z","logger":"setup","msg":"Build from: "}
{"level":"info","ts":"2021-08-27T10:34:12.422Z","logger":"setup","msg":"Build date: "}
{"level":"info","ts":"2021-08-27T10:34:12.422Z","logger":"setup","msg":"Go Version: go1.15.11"}
{"level":"info","ts":"2021-08-27T10:34:12.422Z","logger":"setup","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":"2021-08-27T10:34:13.077Z","logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":"<IP_ADDRESS>:8080"}
{"level":"info","ts":"2021-08-27T10:34:13.081Z","logger":"setup","msg":"starting with following options:","metricsAddr":"<IP_ADDRESS>:8080","enableLeaderElection":true,"forceTenantPrefix":true}
{"level":"info","ts":"2021-08-27T10:34:13.082Z","logger":"setup","msg":"starting manager"}
I0827 10:34:13.082581       1 leaderelection.go:243] attempting to acquire leader lease  capsule-system/42c733ea.clastix.capsule.io...
{"level":"info","ts":"2021-08-27T10:34:13.082Z","logger":"controller-runtime.manager","msg":"starting metrics server","path":"/metrics"}
W0827 10:34:13.088242       1 warnings.go:67] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0827 10:34:13.089615       1 warnings.go:67] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0827 10:34:13.092510       1 warnings.go:67] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0827 10:34:13.092677       1 warnings.go:67] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
I0827 10:34:13.115634       1 leaderelection.go:253] successfully acquired lease capsule-system/42c733ea.clastix.capsule.io
{"level":"debug","ts":"2021-08-27T10:34:13.115Z","logger":"controller-runtime.manager.events","msg":"Normal","object":{"kind":"ConfigMap","namespace":"capsule-system","name":"42c733ea.clastix.capsule.io","uid":"022df253-0d34-480b-b38d-a2e8f310dea4","apiVersion":"v1","resourceVersion":"1636"},"reason":"LeaderElection","message":"capsule-controller-manager-946d5bb5f-4xfbn_602c0cfc-24a5-410e-b202-3d844c800814 became leader"}
{"level":"debug","ts":"2021-08-27T10:34:13.115Z","logger":"controller-runtime.manager.events","msg":"Normal","object":{"kind":"Lease","namespace":"capsule-system","name":"42c733ea.clastix.capsule.io","uid":"5844e58d-9854-4f0b-88a5-3b8cf38e3201","apiVersion":"coordination.k8s.io/v1","resourceVersion":"1637"},"reason":"LeaderElection","message":"capsule-controller-manager-946d5bb5f-4xfbn_602c0cfc-24a5-410e-b202-3d844c800814 became leader"}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controllers.Rbac","msg":"setting up ClusterRoles","ClusterRole":"capsule-namespace-provisioner"}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.service","msg":"Starting EventSource","reconcilerGroup":"","reconcilerKind":"Service","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.tenant","msg":"Starting EventSource","reconcilerGroup":"capsule.clastix.io","reconcilerKind":"Tenant","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.secret","msg":"Starting EventSource","reconcilerGroup":"","reconcilerKind":"Secret","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.endpoints","msg":"Starting EventSource","reconcilerGroup":"","reconcilerKind":"Endpoints","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.secret","msg":"Starting EventSource","reconcilerGroup":"","reconcilerKind":"Secret","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.clusterrole","msg":"Starting EventSource","reconcilerGroup":"rbac.authorization.k8s.io","reconcilerKind":"ClusterRole","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.clusterrolebinding","msg":"Starting EventSource","reconcilerGroup":"rbac.authorization.k8s.io","reconcilerKind":"ClusterRoleBinding","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.endpointslice","msg":"Starting EventSource","reconcilerGroup":"discovery.k8s.io","reconcilerKind":"EndpointSlice","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.tenant","msg":"Starting EventSource","reconcilerGroup":"capsule.clastix.io","reconcilerKind":"Tenant","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.183Z","logger":"controller.tenant","msg":"Starting EventSource","reconcilerGroup":"capsule.clastix.io","reconcilerKind":"Tenant","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.283Z","logger":"controller.endpointslice","msg":"Starting Controller","reconcilerGroup":"discovery.k8s.io","reconcilerKind":"EndpointSlice"}
{"level":"info","ts":"2021-08-27T10:34:13.283Z","logger":"controller.endpointslice","msg":"Starting workers","reconcilerGroup":"discovery.k8s.io","reconcilerKind":"EndpointSlice","worker count":1}
{"level":"info","ts":"2021-08-27T10:34:13.283Z","logger":"controller.tenant","msg":"Starting EventSource","reconcilerGroup":"capsule.clastix.io","reconcilerKind":"Tenant","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.284Z","logger":"controller.clusterrole","msg":"Starting Controller","reconcilerGroup":"rbac.authorization.k8s.io","reconcilerKind":"ClusterRole"}
{"level":"info","ts":"2021-08-27T10:34:13.284Z","logger":"controller.endpoints","msg":"Starting Controller","reconcilerGroup":"","reconcilerKind":"Endpoints"}
{"level":"info","ts":"2021-08-27T10:34:13.284Z","logger":"controller.secret","msg":"Starting Controller","reconcilerGroup":"","reconcilerKind":"Secret"}
{"level":"info","ts":"2021-08-27T10:34:13.284Z","logger":"controller.service","msg":"Starting Controller","reconcilerGroup":"","reconcilerKind":"Service"}
{"level":"info","ts":"2021-08-27T10:34:13.284Z","logger":"controller.clusterrolebinding","msg":"Starting Controller","reconcilerGroup":"rbac.authorization.k8s.io","reconcilerKind":"ClusterRoleBinding"}
{"level":"info","ts":"2021-08-27T10:34:13.284Z","logger":"controller.secret","msg":"Starting Controller","reconcilerGroup":"","reconcilerKind":"Secret"}
{"level":"info","ts":"2021-08-27T10:34:13.290Z","logger":"controllers.Rbac","msg":"setting up ClusterRoles","ClusterRole":"capsule-namespace-deleter"}
{"level":"info","ts":"2021-08-27T10:34:13.294Z","logger":"controllers.Rbac","msg":"setting up ClusterRoleBindings","ClusterRoleBinding":"capsule-namespace-provisioner"}
{"level":"info","ts":"2021-08-27T10:34:13.384Z","logger":"controller.tenant","msg":"Starting EventSource","reconcilerGroup":"capsule.clastix.io","reconcilerKind":"Tenant","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.384Z","logger":"controller.endpoints","msg":"Starting workers","reconcilerGroup":"","reconcilerKind":"Endpoints","worker count":1}
{"level":"info","ts":"2021-08-27T10:34:13.384Z","logger":"controller.secret","msg":"Starting workers","reconcilerGroup":"","reconcilerKind":"Secret","worker count":1}
{"level":"info","ts":"2021-08-27T10:34:13.384Z","logger":"controller.service","msg":"Starting workers","reconcilerGroup":"","reconcilerKind":"Service","worker count":1}
{"level":"info","ts":"2021-08-27T10:34:13.384Z","logger":"controller.clusterrole","msg":"Starting workers","reconcilerGroup":"rbac.authorization.k8s.io","reconcilerKind":"ClusterRole","worker count":1}
{"level":"info","ts":"2021-08-27T10:34:13.384Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:13.384Z","logger":"controller.clusterrolebinding","msg":"Starting workers","reconcilerGroup":"rbac.authorization.k8s.io","reconcilerKind":"ClusterRoleBinding","worker count":1}
{"level":"info","ts":"2021-08-27T10:34:13.384Z","logger":"controller.secret","msg":"Starting workers","reconcilerGroup":"","reconcilerKind":"Secret","worker count":1}
{"level":"info","ts":"2021-08-27T10:34:13.385Z","logger":"controllers.CA","msg":"Reconciling CA Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-ca"}
{"level":"info","ts":"2021-08-27T10:34:13.390Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:13.415Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:13.435Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:13.476Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:13.485Z","logger":"controller.tenant","msg":"Starting EventSource","reconcilerGroup":"capsule.clastix.io","reconcilerKind":"Tenant","source":"kind source: /, Kind="}
{"level":"info","ts":"2021-08-27T10:34:13.557Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:13.615Z","logger":"controller.tenant","msg":"Starting Controller","reconcilerGroup":"capsule.clastix.io","reconcilerKind":"Tenant"}
{"level":"info","ts":"2021-08-27T10:34:13.615Z","logger":"controller.tenant","msg":"Starting workers","reconcilerGroup":"capsule.clastix.io","reconcilerKind":"Tenant","worker count":1}
{"level":"info","ts":"2021-08-27T10:34:13.718Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:14.039Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:14.693Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:15.995Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:18.556Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:23.715Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:33.028Z","logger":"controllers.CA","msg":"Handling CA Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-ca"}
{"level":"info","ts":"2021-08-27T10:34:33.028Z","logger":"controllers.CA","msg":"Updating CA secret with new PEM and RSA","Request.Namespace":"capsule-system","Request.Name":"capsule-ca"}
{"level":"info","ts":"2021-08-27T10:34:33.346Z","logger":"controllers.CA","msg":"Capsule CA has been updated, we need to trigger TLS update too","Request.Namespace":"capsule-system","Request.Name":"capsule-ca"}
{"level":"info","ts":"2021-08-27T10:34:33.347Z","logger":"controllers.CA","msg":"Reconciliation completed, processing back in 87647h59m40s","Request.Namespace":"capsule-system","Request.Name":"capsule-ca"}
{"level":"info","ts":"2021-08-27T10:34:33.347Z","logger":"controllers.CA","msg":"Reconciling CA Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-ca"}
{"level":"info","ts":"2021-08-27T10:34:33.347Z","logger":"controllers.CA","msg":"Handling CA Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-ca"}
{"level":"info","ts":"2021-08-27T10:34:33.347Z","logger":"controllers.CA","msg":"Updating CA secret with new PEM and RSA","Request.Namespace":"capsule-system","Request.Name":"capsule-ca"}
{"level":"info","ts":"2021-08-27T10:34:33.549Z","logger":"controllers.CA","msg":"Reconciliation completed, processing back in 87647h59m40s","Request.Namespace":"capsule-system","Request.Name":"capsule-ca"}
{"level":"info","ts":"2021-08-27T10:34:33.956Z","logger":"controllers.Tls","msg":"Reconciling TLS Secret","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:33.956Z","logger":"controllers.Tls","msg":"Missing Capsule TLS certificate","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controllers.Tls","msg":"Capsule TLS certificates has been updated, we need to restart the Controller","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controllers.Tls","msg":"Reconciliation completed, processing back in 4320h0m0s","Request.Namespace":"capsule-system","Request.Name":"capsule-tls"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controller.tenant","msg":"Stopping workers","reconcilerGroup":"capsule.clastix.io","reconcilerKind":"Tenant"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controller.secret","msg":"Stopping workers","reconcilerGroup":"","reconcilerKind":"Secret"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controller.secret","msg":"Stopping workers","reconcilerGroup":"","reconcilerKind":"Secret"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controller.endpoints","msg":"Stopping workers","reconcilerGroup":"","reconcilerKind":"Endpoints"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controller.clusterrolebinding","msg":"Stopping workers","reconcilerGroup":"rbac.authorization.k8s.io","reconcilerKind":"ClusterRoleBinding"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controller.clusterrole","msg":"Stopping workers","reconcilerGroup":"rbac.authorization.k8s.io","reconcilerKind":"ClusterRole"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controller.service","msg":"Stopping workers","reconcilerGroup":"","reconcilerKind":"Service"}
{"level":"info","ts":"2021-08-27T10:34:50.335Z","logger":"controller.endpointslice","msg":"Stopping workers","reconcilerGroup":"discovery.k8s.io","reconcilerKind":"EndpointSlice"}

As you can see, fill the secrets and reboot.
Logs of manager container after auto reboot:
[bash]# k logs capsule-controller-manager-946d5bb5f-4xfbn -c manager -n capsule-system
{"level":"info","ts":"2021-08-27T10:34:50.727Z","logger":"setup","msg":"Capsule Version  "}
{"level":"info","ts":"2021-08-27T10:34:50.727Z","logger":"setup","msg":"Build from: "}
{"level":"info","ts":"2021-08-27T10:34:50.727Z","logger":"setup","msg":"Build date: "}
{"level":"info","ts":"2021-08-27T10:34:50.727Z","logger":"setup","msg":"Go Version: go1.15.11"}
{"level":"info","ts":"2021-08-27T10:34:50.727Z","logger":"setup","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":"2021-08-27T10:34:51.394Z","logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":"<IP_ADDRESS>:8080"}
{"level":"info","ts":"2021-08-27T10:34:51.421Z","logger":"setup","msg":"starting with following options:","metricsAddr":"<IP_ADDRESS>:8080","enableLeaderElection":true,"forceTenantPrefix":true}
{"level":"info","ts":"2021-08-27T10:34:51.421Z","logger":"controller-runtime.webhook","msg":"registering webhook","path":"/validating-ingress"}
{"level":"info","ts":"2021-08-27T10:34:51.422Z","logger":"controller-runtime.webhook","msg":"registering webhook","path":"/validating-v1-pvc"}
{"level":"info","ts":"2021-08-27T10:34:51.422Z","logger":"controller-runtime.webhook","msg":"registering webhook","path":"/validating-v1-registry"}
{"level":"info","ts":"2021-08-27T10:34:51.422Z","logger":"controller-runtime.webhook","msg":"registering webhook","path":"/validating-external-service-ips"}
{"level":"info","ts":"2021-08-27T10:34:51.422Z","logger":"controller-runtime.webhook","msg":"registering webhook","path":"/mutate-v1-namespace-owner-reference"}
{"level":"info","ts":"2021-08-27T10:34:51.422Z","logger":"controller-runtime.webhook","msg":"registering webhook","path":"/validate-v1-namespace-quota"}
{"level":"info","ts":"2021-08-27T10:34:51.422Z","logger":"controller-runtime.webhook","msg":"registering webhook","path":"/validating-v1-network-policy"}
{"level":"info","ts":"2021-08-27T10:34:51.423Z","logger":"controller-runtime.webhook","msg":"registering webhook","path":"/validating-v1-namespace-tenant-prefix"}
{"level":"info","ts":"2021-08-27T10:34:51.423Z","logger":"controller-runtime.webhook","msg":"registering webhook","path":"/validating-v1-tenant"}
{"level":"info","ts":"2021-08-27T10:34:51.424Z","logger":"setup","msg":"starting manager"}

After rebooting, you can see how the webhooks start because it has detected the full secrets.
Logs of manager container that is replica:
[bash]# k logs capsule-controller-manager-946d5bb5f-rpskn -c manager -n capsule-system
{"level":"info","ts":"2021-08-27T10:34:12.421Z","logger":"setup","msg":"Capsule Version  "}
{"level":"info","ts":"2021-08-27T10:34:12.422Z","logger":"setup","msg":"Build from: "}
{"level":"info","ts":"2021-08-27T10:34:12.422Z","logger":"setup","msg":"Build date: "}
{"level":"info","ts":"2021-08-27T10:34:12.422Z","logger":"setup","msg":"Go Version: go1.15.11"}
{"level":"info","ts":"2021-08-27T10:34:12.422Z","logger":"setup","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":"2021-08-27T10:34:13.076Z","logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":"<IP_ADDRESS>:8080"}
{"level":"info","ts":"2021-08-27T10:34:13.078Z","logger":"setup","msg":"starting with following options:","metricsAddr":"<IP_ADDRESS>:8080","enableLeaderElection":true,"forceTenantPrefix":true}
{"level":"info","ts":"2021-08-27T10:34:13.078Z","logger":"setup","msg":"starting manager"}

As you can see, the webhooks not start at any time, even if secrets have been filled out. It also needs to be restarted in order to start the webhooks
Additional context

Capsule version: 0.0.18
Helm Chart version: 0.0.4
Kubernetes version: 1.20.7

Hi @prometherion, thanks you for quick response.
I think that the best option that you propose is the first one, as you well indicate, it can be confusing to deploy the chart with one replica and then scale.
Cheers!


fix: upgrade actions checkout to v4

Try out this version of the Leather — download extension builds.

Testing this to fix actions/checkout@v3 issue:  https://github.com/actions/checkout/issues/1448
*Not sure if this should be merged or not?

This upgrade requires node 20.

seems it worked

Closing bc appears to be fixed.


Websocket non-standard port not appended to hostname

Websocket async example (possibly others as well) don't append port to hostname when a non-standard port is used, e.g. 9001.

@djarek I'm struggling to see in the example where the port might be appended. Would you be able to clarify?


Rename DemoDataGenerator classes

JIRA

Referenced pull requests

When we sync the quarkus-school-timetabling example with the one in quarkus-quickstarts, we need to adjust the quarkus docs, because those say "DemoDataGenerator".
@emmurphy1 This might affect your docs too.

When we sync the quarkus-school-timetabling example with the one in quarkus-quickstarts, we need to adjust the quarkus docs, because those say "DemoDataGenerator". Note that those quarkus docs are coming back into our docs too (and we'll just duplicat them there).

This is exactly why it makes little sense to rename things just to rename things.
The fix is worse than the original problem - not only do you have to change references in many places (and potentially miss some), you also destroy what people already remember. The hypothetical benefits from consistency in this case are, in my opinion, miniscule - especially since the quickstarts were already consistent, you just didn't like the name.
I implore you - stop doing this, @ge0ffrey . It helps no one.

@triceo Some renames are worth their fallout. Some restructures are worth their fallout. Like splitting off optaplanner-quickstart (which was your proposal IIRC). So I won't just stop polishing such things, especially in quickstarts/examples which need to be crystal clear for the getting started experience. This one is arguable, I don't feel strongly about it - happy to drop this request. We didn't realize the impact all the way into the quarkus docs when we noticed the downside of having so many classes with the same name.
@rsynek Wdyt? is this rename still worth the effort? Or shall we drop it? your call.

It's true that we might impact some blog posts (although in our blog posts we don't mention this class) and as nobody feels strongly about merging this PR, I am closing it.
If we want to keep every potential blog post compatible, shall we only fix bugs after any quickstart makes it into the stable branch?

We don't want to keep blog posts compatible. That is a non-goal.
We want to keep the docs compatible, including those in quarkus.io, which's master needs to be moved to optaplanner-docs anyway.


log level for appenders

Hi,  is there any way to specify different log level by appenders at the root level?

Yep - you can add threshold filters to your appenders - take a look at the example here for reference: https://docs.rs/log4rs/0.8.0/log4rs/file/index.html

Thank you!!


AdaptiveSparseGrid different between python 2 and 3

Issue Description
What did you expect to see happen?
Consistent behavior
What did you see instead?
Do you have a suggested fix for the development team?
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.
framework/Samplers/SparseGrid.AdaptiveOnVariance

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

This change is almost entirely internal, so no notifications need be made. Checklists passed, approve to close via #848.


Configure Automatic Release Process to the npm Registry

Should also add change log

changeset is a great package for that 👍

#26

You are the only one who can do that as you only own this repo.
Please fill there values
https://github.com/Yedidyar/remult-cli/pull/78/commits/7d7a0f4377acc85ae4927c7ccaa7c3a1034a794a
Something like:


[quick_actions] Add DartDoc and test coverage

Description
Also adds a lint to prevent undocumented DartDocs from being added in
the future.
Some of the APIs were public when they really should have been
@visibleForTesting or even private. Added some @visibleForTesting
annotations as well.
Related Issues
Fixes flutter/flutter#44399.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[x] Yes, this is a [potentially] breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[ ] No, this is not a breaking change.

@collinjackson good call, updated to use your wording.


Add Evaluator::Transformer::Name

Useful to "place named marks" in the evaluation tree. A printer walking this tree can then associate these names with the given input and params passed to evaluators "below" the named marks. Such information can be used to construct customized human readable error messages from failing predicate evaluators inside an evaluation tree.

Closing this as redundant with #27


helperColor property on TextField and TextView

This introduces a way to change the color of the helper text on the TextField or TextView components.
Usage
<MDTextField
    ...
    helper="help me!"
    helperColor="red"
    ...
></MDTextField>

or
MDTextField {
    helper-color: red;
}

Examples
iOS

Android

Awesome PR really! Thanks for the way you did it!

@farfromrefug Thanks so much! Want me to put some documentation in for it?

You can. I am really bad with docs :(

Sounds good! I just didn't want to flood you with too many PRs.

Hi really grateful for your contribution, it would be nice feature if you add helper click event listeners as well! I don't know if this feature exists, ping me if you know how to achieve it. Thanks beforehand!

Hi really grateful for your contribution, it would be nice feature if you add helper click event listeners as well! I don't know if this feature exists, ping me if you know how to achieve it. Thanks beforehand!


Problem with the new claim plugin for Vanha

This bug happened in the other plugin aswell but now is even worse, it happens that you can break armor stands with a bow. If the players find this they can take advantage of it and steal the armors in the adventure map.
I know it happened with the other plugin and tried to see if it was fixed but now is even worse since before you could put the armor stand back if you broke it by accident but now you can't.
I tested it and, yes it happens with item frames aswell, and since there are medals in the gyms, players can take them and that could be a major problem.
PD: I retrieved the armor and the medal I got to a mod, who put them back in it's place.

Confirmed as of the current version.

Confirmed still happens post reset.

Should be fixed with the next code update

Closing since Roku says it is fixed.


Add lint rule flags to the rule detail page

Description
Not an issue, more of a documentation feature request.
In the lint rules listing, every rule has flags about stability and if fixable or not (https://biomejs.dev/linter/rules/), example:

but the rule detail page is missing the information, example:

Expectations
We have strong control over every configuration in the project so when new Biome version is released, we go through the changelog and evaluate every new rule. Right now, we have to find every rule in the listing to see those flags. It would be great to have those icons in the rule detail page too 🙂
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Is it needed though? Every rule page has a diagnostic example, and from there you can understand if the rule has a code action and if it's safe or unsafe

We're always open to suggestions, I was trying to understand why the current information isn't informative enough.
Would you like to come up with something? Or even contribute?

I don't see anything wrong in "repeating" the work, it's just generating the HTML in a different way


Geo partitioning tutorial

Add geo-partitioning tutorial to accompany new video demo. Also create new Tutorials section for such stand-alone demonstrations/tutorials, and move contents of Guides > Explore Capabilities as well. If not in this PR, then soon after, I'd like to find a way to clarify Guides vs. Tutorials, perhaps via a simple tooltip in the sidenav.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d52a14ad6d79f722cb34b1c87198816706e6f919/
Edited pages:

v19.1/demo-geo-partitioning.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/324c88881307b03f1a209f4907c45af08353e84a/
Edited pages:

v19.1/demo-geo-partitioning.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ef1d9ea809197c81144c0a30986470789d6e1025/
Edited pages:

v19.1/demo-geo-partitioning.md

Barring some minor grammatical nits, :lgtm:! Most of my suggestions can probably wait until after Wednesday if there is a time crunch. The only one I would definitely recommend changing is adding locality flags to the gen haproxy commands.

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/6b7a3920fe8f56c0023c5acb7c2a2d9a26369a55/
Edited pages:

v19.1/demo-geo-partitioning.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5c0abb933fa4c6601581ba834ceba6304bf916ba/
Edited pages:

v19.1/demo-geo-partitioning.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9a6a9e3b96ed6d82d30a925a9db25bbd72ede980/
Edited pages:

v19.1/demo-geo-partitioning.md


[WIP] FromIPLD.lean tests

Writing some tests to check that the typechecker expressions/constants from the compiler match those from FromIPLD.lean (and if not, see which side is broken). I think it will be a good sanity check right before we get into #120 since we've already somewhat verified the correctness of our IPLD expressions/constants and we're separately constructing the typechecker versions in two different places.

FromIpld is definitely broken since it's not converting the free variables generated in the inductive constants with the actual values they should take

Okay, I'll try to get the infrastructure for the tests up anyways so we can work on this later via TDD.


fix: MD003/heading-style/header-style

Escape C# caught as closed_atx
Underscoded block marked as heading

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

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


As of the recent update, Elite Observatory does not produce audio

I'd appreciate any help, the application does not announce events in audio form anymore as of the latest update (v1.0.3 Bugfix 3).
Neither the Herald plug-in nor the native voice output seem to produce any audio, at least not on any audio device I can locate. It doesn't show up in the windows volume mixer either, under any output device. I've restarted both the application and my PC. There's very little additional information I can glean I'm afraid, I'm not well versed with this type of audio issue.

I also found this issue.  I solved it by deleting Observatory and using a previous version and reloading all the plugins again

This should hopefully now be resolved, there was an issue where loading the selected audio device could fail. Feel free to comment here and re-open if this is not the case.


Aws fresh spawn of CoreOS - etcd2 single node does not start.

Hi.
 I am using ami-7e72c70d for Ireland and UserData:
#cloud-config
coreos:
etcd2:
discovery: "https://discovery.etcd.io/aa..."
advertise-client-urls: "http://$private_ipv4:2379"
initial-advertise-peer-urls: "http://$private_ipv4:2380"
listen-client-urls: "http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:4001"
listen-peer-urls: "http://$private_ipv4:2380,http://$private_ipv4:7001"
units:
- name: etcd2.service
command: start
- name: fleet.service
command: start
ssh_authorized_keys:

"ssh-rsa ..."

I generated the token for "discovery" using https://discovery.etcd.io/new?size=1 url.
When I start etcd2 using systemctl start etcd2 I get in journalctl:
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal systemd[1]: Starting etcd2...
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: recognized and used environment variable ETCD_ADVERTISE_CLIENT_URLS=http://<IP_ADDRESS>:2379
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: recognized and used environment variable ETCD_DATA_DIR=/var/lib/etcd2
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: recognized and used environment variable ETCD_DISCOVERY=https://discovery.etcd.io/aa..
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: recognized and used environment variable ETCD_ELECTION_TIMEOUT=1200
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: recognized and used environment variable ETCD_INITIAL_ADVERTISE_PEER_URLS=http://<IP_ADDRESS>:2380
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: recognized and used environment variable ETCD_LISTEN_CLIENT_URLS=http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:4001
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: recognized and used environment variable ETCD_LISTEN_PEER_URLS=http://<IP_ADDRESS>:2380,http://<IP_ADDRESS>:7001
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: recognized and used environment variable ETCD_NAME=xxx
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: etcd Version: 2.2.0
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: Git SHA: e4561dd
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: Go Version: go1.4.2
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: Go OS/Arch: linux/amd64
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: setting maximum number of CPUs to 1, total number of available CPUs is 2
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: the server is already initialized as member before, starting as etcd member...
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: listening for peers on http://<IP_ADDRESS>:2380
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: listening for peers on http://<IP_ADDRESS>:7001
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: listening for client requests on http://<IP_ADDRESS>:2379
Jan 26 15:44:21 ip-10-0-0-82.eu-west-1.compute.internal etcd2[949]: listening for client requests on http://<IP_ADDRESS>:4001
Jan 26 15:44:26 ip-10-0-0-82.eu-west-1.compute.internal unknown[949]: stopping listening for client requests on http://<IP_ADDRESS>:4001
Jan 26 15:44:26 ip-10-0-0-82.eu-west-1.compute.internal unknown[949]: stopping listening for client requests on http://<IP_ADDRESS>:2379
Jan 26 15:44:26 ip-10-0-0-82.eu-west-1.compute.internal unknown[949]: stopping listening for peers on http://<IP_ADDRESS>:7001
Jan 26 15:44:26 ip-10-0-0-82.eu-west-1.compute.internal unknown[949]: stopping listening for peers on http://<IP_ADDRESS>:2380
Jan 26 15:44:26 ip-10-0-0-82.eu-west-1.compute.internal unknown[949]: context deadline exceeded
Jan 26 15:44:26 ip-10-0-0-82.eu-west-1.compute.internal systemd[1]: etcd2.service: Main process exited, code=exited, status=1/FAILURE
Jan 26 15:44:26 ip-10-0-0-82.eu-west-1.compute.internal systemd[1]: Failed to start etcd2.
Jan 26 15:44:26 ip-10-0-0-82.eu-west-1.compute.internal systemd[1]: etcd2.service: Unit entered failed state.
Jan 26 15:44:26 ip-10-0-0-82.eu-west-1.compute.internal systemd[1]: etcd2.service: Failed with result 'exit-code'.
So I do not see a clean source of the problem.
$ cat /usr/lib64/systemd/system/etcd2.service
[Unit]
Description=etcd2
Conflicts=etcd.service
[Service]
User=etcd
Type=notify
Environment=ETCD_DATA_DIR=/var/lib/etcd2
Environment=ETCD_NAME=%m
ExecStart=/usr/bin/etcd2
Restart=always
RestartSec=10s
LimitNOFILE=40000
TimeoutStartSec=0
[Install]
WantedBy=multi-user.target
$ cat /run/systemd/system/etcd2.service.d/20-cloudinit.conf
[Service]
Environment="ETCD_ADVERTISE_CLIENT_URLS=http://<IP_ADDRESS>:2379"
Environment="ETCD_DISCOVERY=https://discovery.etcd.io/aa.."
Environment="ETCD_INITIAL_ADVERTISE_PEER_URLS=http://<IP_ADDRESS>:2380"
Environment="ETCD_LISTEN_CLIENT_URLS=http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:4001"
Environment="ETCD_LISTEN_PEER_URLS=http://<IP_ADDRESS>:2380,http://<IP_ADDRESS>:7001"
Can someone help?
BR,
Rafal.

This is already fixed in a later version of etcd. (>2.2.1)

I changed CoreOS version to beta to get etcd in version 2.2.3:
$ cat /etc/os-release
NAME=CoreOS
ID=coreos
VERSION=899.5.0
VERSION_ID=899.5.0
BUILD_ID=2016-01-22-1100
PRETTY_NAME="CoreOS 899.5.0"
ANSI_COLOR="1;32"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"
$ etcd2 --version
etcd Version: 2.2.3
Git SHA: 05b564a
Go Version: go1.4.3
Go OS/Arch: linux/amd64
User Data:
#cloud-config
coreos:
etcd2:
discovery: "https://discovery.etcd.io/aa..."
advertise-client-urls: "http://$private_ipv4:2379"
initial-advertise-peer-urls: "http://$private_ipv4:2380"
listen-client-urls: "http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:4001"
listen-peer-urls: "http://$private_ipv4:2380,http://$private_ipv4:7001"
units:
- name: etcd2.service
command: start
- name: fleet.service
command: start
ssh_authorized_keys:

"ssh-rsa AAAA..."

I got https://discovery.etcd.io/aa... after invoking discovery.etcd.io/new?size=1 and am starting only one node.
When I try to start etcd2 I get in journalctl:
-- Logs begin at Wed 2016-01-27 13:30:17 UTC. --
Jan 27 13:31:59 ip-10-0-0-64.eu-west-1.compute.internal systemd[1]: Starting Garbage Collection for rkt...
Jan 27 13:31:59 ip-10-0-0-64.eu-west-1.compute.internal systemd[1]: Started Garbage Collection for rkt.
Jan 27 13:32:08 ip-10-0-0-64.eu-west-1.compute.internal systemd-timesyncd[607]: Timed out waiting for reply from <IP_ADDRESS>:123 (3.coreos.pool.ntp.org).
Jan 27 13:32:14 ip-10-0-0-64.eu-west-1.compute.internal systemd[1]: Started OpenSSH per-connection server daemon (<IP_ADDRESS>:50455).
Jan 27 13:32:14 ip-10-0-0-64.eu-west-1.compute.internal sshd[871]: Accepted publickey for core from <IP_ADDRESS> port 50455 ssh2: RSA SHA256:xo0LdLyurs/Srf551ozDDbkZv6fWrSprHfKdRqHJ8ds
Jan 27 13:32:16 ip-10-0-0-64.eu-west-1.compute.internal locksmithd[646]: [etcd.service etcd2.service] are inactive
Jan 27 13:32:16 ip-10-0-0-64.eu-west-1.compute.internal locksmithd[646]: Unlocking old locks failed: [etcd.service etcd2.service] are inactive. Retrying in 1m20s.
Jan 27 13:32:18 ip-10-0-0-64.eu-west-1.compute.internal sudo[880]:     core : TTY=pts/1 ; PWD=/home/core ; USER=root ; COMMAND=/bin/su -
Jan 27 13:32:18 ip-10-0-0-64.eu-west-1.compute.internal su[880]: Successful su for root by root
Jan 27 13:32:18 ip-10-0-0-64.eu-west-1.compute.internal su[880]: + /dev/pts/1 root:root
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal polkitd[662]: Registered Authentication Agent for unix-process:888:14758 (system bus name :1.31 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal systemd[1]: Starting etcd2...
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: recognized and used environment variable ETCD_ADVERTISE_CLIENT_URLS=http://<IP_ADDRESS>:2379
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: recognized and used environment variable ETCD_DATA_DIR=/var/lib/etcd2
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: recognized and used environment variable ETCD_DISCOVERY=https://discovery.etcd.io/aa...
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: recognized and used environment variable ETCD_ELECTION_TIMEOUT=1200
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: recognized and used environment variable ETCD_INITIAL_ADVERTISE_PEER_URLS=http://<IP_ADDRESS>:2380
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: recognized and used environment variable ETCD_LISTEN_CLIENT_URLS=http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:4001
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: recognized and used environment variable ETCD_LISTEN_PEER_URLS=http://<IP_ADDRESS>:2380,http://<IP_ADDRESS>:7001
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: recognized and used environment variable ETCD_NAME=87f09ea6b18f4077982b09dcfbbacdec
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: etcd Version: 2.2.3
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: Git SHA: 05b564a
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: Go Version: go1.4.3
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: Go OS/Arch: linux/amd64
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: setting maximum number of CPUs to 1, total number of available CPUs is 2
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: listening for peers on http://<IP_ADDRESS>:2380
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: listening for peers on http://<IP_ADDRESS>:7001
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: listening for client requests on http://<IP_ADDRESS>:2379
Jan 27 13:32:43 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: listening for client requests on http://<IP_ADDRESS>:4001
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: stopping listening for client requests on http://<IP_ADDRESS>:4001
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal polkitd[662]: Unregistered Authentication Agent for unix-process:888:14758 (system bus name :1.31, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: stopping listening for client requests on http://<IP_ADDRESS>:2379
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: stopping listening for peers on http://<IP_ADDRESS>:7001
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: stopping listening for peers on http://<IP_ADDRESS>:2380
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: failed to join discovery cluster (context deadline exceeded)
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: discovery token https://discovery.etcd.io/aa... was used, but failed to bootstrap the cluster.
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal etcd2[893]: please generate a new discovery token and try to bootstrap again.
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal systemd[1]: etcd2.service: Main process exited, code=exited, status=1/FAILURE
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal systemd[1]: Failed to start etcd2.
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal systemd[1]: etcd2.service: Unit entered failed state.
Jan 27 13:32:48 ip-10-0-0-64.eu-west-1.compute.internal systemd[1]: etcd2.service: Failed with result 'exit-code'.
Jan 27 13:32:51 ip-10-0-0-64.eu-west-1.compute.internal systemd-timesyncd[607]: Timed out waiting for reply from <IP_ADDRESS>:123 (0.coreos.pool.ntp.org).
So overall etcd2 does not start correctly also in this case. Can someone tell what should be done?

@rradecki Does your machine have access to discovery.etcd.io?


1.2.7

New feature: Export PDF.
New feature: Export images without background. Reference #56
New feature: Undo & Redo via multi-touch gestures.
New feature: iCloud data sync toggle within the app.
Apple Pencil support. Reference #59

Also support drawing with the Apple Pencil and directly dragging the canvas with your finger.

Fix issue where Sidebar was not clickable. Fixes #53
Accessibility improvements for offline usage on iOS.
Fix issue with File History not working properly on iPad.
Sync with the latest Excalidraw core code.
Add Korean font support. Fixes #60

Thanks for the update. Huge thanks for making this software available!
Finally we can export as PDF now. But its not really the PDF export we expected is it? :) It would be really nice if we could export the documents as PDF but in vector. I think this is the only feature that prevents it from being perfect.
Thanks again!

Hello, @tensarflow. That’s a great suggestion! I hadn’t noticed this requirement before. You can submit it as an issue, and I’ll include this feature in a future update.


Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it)
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.

Looks good apart from my comment on wording in the specs.

Good comment @jonas054 thanks - I did know that, I think the existing spec that used the wrong wording threw me. I've updated the PR

:+1:

Has to be rebased.

@bbatsov: done


Any idea if this works on/with Linux?

I use Ubuntu 20.04 Desktop servers with XRDP and can connect to them using RDP.
Noticed your code was python so was wondering if it is designed only for Windows in mind.

It is designed to work on linux,windows,mac but for now it just supports windows.
In future support for linux and mac can be added.


Need a better module hierarchy

Now the boba and boba-visualizer modules depend on each other ...
The reason that boba depends on boba-visualizer is because we would like a single pip command to install all boba submodules.
The reason that boba-visualizer depends on boba is because the server needs to invoke boba run.
If we separate boba-dsl from boba, and make boba only a dummy module that imports everything else, we can get rid of circular dependency.
Also, I am not sure where to put the sampling code. Maybe we need another module like boba-stats.

boba no longer depends on boba-visualizer: https://github.com/uwdata/boba/commit/88aebd98f773ee863816106db38e5723d3cccabb
Users now need to install these two packages separately via two commands, but it might be ok for now ...


mysql placeholder should be '?'

comment examples to reflect what should be used for mysql

Pull Request Test Coverage Report for Build 245

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

Totals

Change from base Build 244:
0.0%

Covered Lines:
1223

Relevant Lines:
1649

💛  - Coveralls


feature: Chart.font

A chart has an XML element where a default font can be specified:
c:chartSpace/c:txPr/a:p/a:pPr/a:defRPr
Setting certain font attributes such as size and color at the chart level can greatly reduce the piece-wise changes required when the default 18pt Text1 font is not suitable.

Added in release v0.6.13 out later today.


Multiple disease prediction web app

Project Request
Disease prediction app using various machine learning algorithm where we can find if a person is suffering from disease or not

Field
Description

About
Disease prediction web app

Github
Shubhamkumar-op

Email
singhshubhamkumar778<EMAIL_ADDRESS>

Label
Project Request

https://github.com/Shubhamkumar-op

Define You

[ * ] GSSOC Participant
[ * ] Contributor

Project Name
Multiple disease prediction app
Description

I will make a disease prediction web app that will tell you the if you have that disease or not
In this we will use multiple ML algorithm
This web app predict  disease like heart disease, diabetes, parkinnson's

Scope
After using machine learning algorithm like logistic regression , SVM  we will improve the model performance
Them we will use stream lit cloud to deploy our app from where user fill the required values and app will tell whether it  suffering from that disease or not
Timeline
Start time: Time of Assignment
End time: July 25th.

Hey I have been working on something similar please assign this project to me


Change deprecated intel::ii to intel::initiation_interval in two files in FPGA mvdr_beamforming sample

Signed-off-by: mtucker<EMAIL_ADDRESS>Description
Removed intel::ii which is deprecated as of 2021.3.  These files were missed in PR #482.
Add -Werror so that warnings can not slip in to this sample undetected in the future.
External Dependencies
None
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Compiled fpga_emu target with latest 21.3 SYCL resource, no warnings generated.

Failed CI tests are expected once -Werror is added, since the CI runs with 2021.2 and the intel::initiation_interval attribute is not added until 2021.3.


Basic storybook - No audio

Storybooks are books that have a picture on each page and text that goes with it. In the more complex versions that will be covered in other issues, it can have audio playing, automatic page advancement, and Ken Burns type of motion on the images.  For the initial simplest case, PWA needs to support picture books without audio or motion.    Each page has a text and a picture defined.  The view changes depending upon whether the app is being viewed in landscape mode or portrait mode.  In portrait mode, the picture is displayed at the top of the screen and the text is viewed in the bottom of the screen.  In landscape mode, it only displays the picture as a full screen image.
Portrait mode:

Landscape mode:

As with the scripture books, double tapping the screen changes it to full screen mode (and back)

Advance from page to page as you would with the scripture paging.  Text for the first page of this book (which is displayed above)
\id 005
\toc2 No Audio

\page 1
\img image1.jpeg
\m One day, Peter asked Jesus, “Master, how many times should I forgive my brother when he sins against me?  Up to seven times?”
\m Jesus said, “Not seven times, but seventy times seven!”
\m By this, Jesus meant that we should always forgive. Then Jesus told this story.

Besides the \img and \m markers, for img url and paragraph, the following entries may also be present:
\video followed by the video file name
\b blank line paragraph
\pc - centered paragraph
\pr - right justified paragraph
\s1 Heading 1
\s2 Heading 2
\s3 Heading 3
Configuration for a non audio storybook:
        <book id="005" type="story">
            <n>No Audio</n>
            <v>NA</v>
            <ct c="9" />
            <cn value="1-9" />
            <font-choice type="book-collection" />
            <f>UnfaithfulServant2.usfm</f>
            <audio-story-book mode="single-file" />
            <page num="1">
                <image-filename>UnfaithfulServant2-image1.jpeg</image-filename>
            </page>
            <page num="2">
                <image-filename>UnfaithfulServant2-image2.jpeg</image-filename>
            </page>
            <page num="3">
                <image-filename>UnfaithfulServant2-image3.jpeg</image-filename>
            </page>
            <page num="4">
                <image-filename>UnfaithfulServant2-image4.jpeg</image-filename>
            </page>
            <page num="5">
                <image-filename>UnfaithfulServant2-image5.jpeg</image-filename>
            </page>
            <page num="6">
                <image-filename>UnfaithfulServant2-image6.jpeg</image-filename>
            </page>
            <page num="7">
                <image-filename>UnfaithfulServant2-image7.jpeg</image-filename>
            </page>
            <page num="8">
                <image-filename>UnfaithfulServant2-image8.jpeg</image-filename>
            </page>
            <page num="9">
                <image-filename>UnfaithfulServant2-image9.jpeg</image-filename>
            </page>
            <features type="book">
                <e name="show-chapter-numbers" value="no" />
                <e name="lock-orientation" value="none" />
                <e name="show-border" value="inherit" />
                <e name="story-image-max-height" value="45" />
                <e name="show-in-book-selector" value="inherit" />
                <e name="show-verse-numbers" value="inherit" />
            </features>
            <images type="illustration">
                <image width="410" height="230">image1.jpeg</image>
                <image width="410" height="230">image6.jpeg</image>
                <image width="410" height="230">image7.jpeg</image>
                <image width="410" height="230">image8.jpeg</image>
                <image width="410" height="230">image4.jpeg</image>
                <image width="410" height="230">image5.jpeg</image>
                <image width="410" height="230">image9.jpeg</image>
                <image width="410" height="230">image2.jpeg</image>
                <image width="410" height="230">image3.jpeg</image>
            </images>
        </book>

Note that the size of the illustration may need to be adjusted by the "Resize the image files to reduct the app size" in Media/illustrations in SAB.  (features resize-illustrations-width if resize-illustrations is true).  This may also be overridden at the book level

The text area is a scrollable view.  The text may exceed the area that's visible.  If it does, the user can scroll through the text.  The picture remains on the screen as it is with only the text scrolling.

I was going to make a separate about borders, but it seems to small.  If borders are defined and active for this book, then the border is displayed around the text window in portrait view.  It does not appear in landscape view at all:

Besides the codes mentioned above, ordered and unordered lists are also supported.  An example screen would be as follows (even though it makes no sense in context)

The source text for that screen would be:
\img image2.jpeg

\s1 The Story
\s2 Unmerciful Servant
\m Jesus said, “The kingdom of God is like a king who wanted to settle accounts with his servants. One of his servants owed a huge debt worth 200,000 years' wages.”
\zuli1 One
\zuli1 Two
\zuli1 Three
\b
\zon1 1
\zoli1 One
\zoli1 Two
\zoli1 Three
\b
\zon1 7
\zoli1 Test
\zoli1 Test 2
\b

The html for that screen in the app would be:


feat(segment): disabled prop

feat(segment): disabled prop
BREAKING CHANGES mitigation:
Segment's boxShadowColor variable was replaced by boxShadow => in order to set box shadow color you need to replace:
<Segment variables={{ boxShadowColor: COLOR }} />

with
<Segment variables={{ boxShadow: `1px 1px 1px 1px ${COLOR}` }} />

Description
For Segment component:

adds missing disabled prop
improves variables:

boxShadowColor variable was replaced by boxShadow
added colorDisabled, backgroundColorDisabled, borderColorDisabled, borderStyle, borderWidth

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Update zeroc-ice wheel table

Add link for m1

Since https://www.glencoesoftware.com/blog/2023/12/08/ice-binaries-for-omero.html was updated on 21st July

https://github.com/ome/omero-documentation/pull/2448


Replacing IPFS wallet service lib with bch-consumer

:tada: This PR is included in version 3.7.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


MM-14038 Access recent reactions from the long press menu

Summary
This PR Adds a quick reaction element to the post options long press menu
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/14038
Checklist

[x] Added or updated unit tests (required for all new features)
[x] Has UI changes

Device Information
This PR was tested on:

iPhone 11 Simulator
Google Pixel 3L Simulator

Screenshots
Android:

iOS:

@avasconcelos114 tests failing

@avasconcelos114  you're awesome!

Ah my bad, had forgotten to update snapshots after the latest batch of changes

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/4461
https://circleci.com/gh/mattermost/mattermost-mobile/4460

Artifact links:
https://4461-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.apk
https://4460-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.ipa

@esethna I'm working with Andre over Mattermost on some of the spacing, sizing and the icon. All good! @avasconcelos114 I'll keep an eye out for an update.

Alrighty I just did another round of improvements that should fix the styling.
The one thing left to do is patch this to avoid the unnecessary re-renders

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/4726
https://circleci.com/gh/mattermost/mattermost-mobile/4725

Artifact links:
https://4726-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.ipa
https://4725-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.apk

Okay I swear I'm done with changes now! 🙏
I just decided to create a reaction button component and keep the isSelected state local to that component to avoid any re-renders of every single button just so highlight a single one of them
Also just decided to use the already existing method to get the deviceWidth instead of importing Dimensions

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/4779
https://circleci.com/gh/mattermost/mattermost-mobile/4778

Artifact links:
https://4779-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.ipa
https://4778-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.apk

@matthewbirtch can you comment on @josephbaylon observation?

@josephbaylon @enahum this was updated in design and I guess we neglected to update the ticket description. I'll update that now


feat(lsp): add incoming call handler

This PR implements the incoming_call handler for the lsp provider..

Ty!
https://github.com/ibhagwan/fzf-lua/commit/5060b677e02ba7ce408e7827c8187140e3dd910d - merged manually as I also added a ref for the new functoin in init.lua:lsp_incoming_calls (so it can be found in the builtin provider:
https://github.com/ibhagwan/fzf-lua/blob/5060b677e02ba7ce408e7827c8187140e3dd910d/lua/fzf-lua/init.lua#L142
Out of curiouslty what langauge servers support this functionality?

Thank you! Sorry I missed that part.
Out of curiosity, how did you change the commit while keeping the author of the commit?

Out of curiosity, how did you change the commit while keeping the author of the commit?

Great question :-)
# create a local branch of the PR
git fetch origin pull/387/head:pr_387
# switch to our local branch
git switch pr_387
# make addittional changes
git commit
# squash to one commit (not a must)
git rebase -i <commit before PR>
git switch main
git merge pr_387
git push

Learn git from awesome maintainers, not from those dumb books :)


ClipBoard menu?

A menu for ClipBoard history (images, files and text)

Should work over OneDrive or Googls Drive

Add "My computer name", "My ip" and so on, to the clipboard menu


fix: pnpm api.update for build success

What is it?

[ ] Feature / enhancement
[X] Bug
[ ] Docs / tests

Description
can't build success, so exec pnpm api.update
Use cases and why

One use case

Another use case

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Hi @cunzaizhuyi 👋
Just tested locally on latest main and i don't get a diff on the api 🤷 where do you see this diff? and is it still the case after pulling latest main?

re-clone qwik, it's ok now.


console tab with dark background?

I know this is super picky, but would it be possible for the console tab to have a dark background? In my experience, most hackers use a light-on-dark terminal setup.

The output on my Safari 7.0.3 is dark grey on black


Can we add VTK9 and QT6 to /usr/workspace/visit/visit/thirdparty_shared

The title says it all. It would be nice if those versions of VTK and QT could be built on the RZ (and CZ for that matter). We would have to update the config site files as well if we wanted them to use the new versions of the libraries.

They are available in /usr/workspace/visit/visit/thirdparty_shared/3.4.0/toss4. (on CZ)
VTK 9 is also in blueos, but not sure about qt version as I don't have read permissions for that subdir.

Good to know. I should have checked the CZ first. There is no /usr/workspace/visit/visit/thirdparty_shared/3.4.0 directory on the RZ; I think one should be added.

I'm doing this now.

Are you sure the config-site is looking for VTK-9.2.6?
Does the config-site entry for VISIT_XDMF_LIBDEP look something like this (from poodle18.cmake):
VISIT_OPTION_DEFAULT(VISIT_XDMF_LIBDEP HDF5_LIBRARY_DIR hdf5  ${VISITHOME}/vtk/${VTK_VERSION}/${VISITARCH}/lib64 vtklibxml2-${VTK_MAJOR_VERSION}.${VTK_MINOR_VERSION} TYPE STRING)

Does the vtklibxml2-9.2 library exist in the VTK-9.2.6 install?


netperf: Support confidence intervals, increase test length, report stddev

Increases default netperf test length to 60 seconds (from 10).
Adds support to run each netperf test for a user-specified amount of time (--netperf_test_length).
Adds support for multiple test iterations, which will also generate confidence estimates (--netperf_max_iter).
Adds standard deviation for RR tests to the output.

test this please.

LGTM