Push minimum supported version of Rust to 1.9.0

This PR is not fully prepared yet. I first want to see what breaks in the CI, if we do this. Once everything works, I will add a CHANGELOG.md entry.
This is done to allow #431 to go forward.

The release of gcc-rs 0.3.39 results in 1.7 builds breaking again. Since, I am a bit lost here, could you, @posborne, point me towards where I should be looking for the build failures that happen here. To me, it looks like 'infrastructure' problems (wrong files for old versions being requested). Given that you are more involved in the odd Platforms, you might have some insights, whose typing out does not require to much time.

At present, Rust 1.7.0 is baked into the docker images we use for doing builds for other targets.  Some notes on how our current system works as well as a few others here: https://github.com/rust-embedded/rfcs/issues/16.  I would  like to move to being based on https://github.com/japaric/trust by @japaric.
I'm not 100% sure on the best way to reuse those contents are present (copying, git submodule, something else).  I've also been pretty busy lately with the day job, so my FOSS time has been decreased.

More and more dependencies don't run on older versions, so we have to update the minimal version. Since you do not have the time at the moment and I do not want to spend the time to get into working with these platforms, I propose that we drop support for those platforms for now.
I propose to support only beta, stable, stable-1 and stable-2 (and work toward nightly support) on Linux/ MacOSX (x86/x86_64).

I propose that we drop support for those platforms for now.

We definitely should support these platforms, but in order to fix the build, I am fine with moving these targets to the ignored failures in travis.

I'll close this for now, since I won't be working on it.


📝 Fix version number for Workflow Executions started after the change.

What was changed

Replace workflow.DefaultVersion to 1 in Part D, 2.
Why?

It's a mistake in README, the version must be equal to 1. See https://github.com/temporalio/edu-102-go-code/blob/37032994b3ea52d42452e9c4a33a943d3ec0b1a7/exercises/version-workflow/solution/workflow.go#L53
Checklist

Closes

How was this tested:

Any docs updates needed?

Thanks for catching this, Guillaume, and for submitting the correction!


simple_repwhile

Fixed in: https://github.com/SymbiFlow/yosys-symbiflow-plugins/pull/168

Fix for missing stmt when while contains block: https://github.com/SymbiFlow/yosys-symbiflow-plugins/pull/202

Issue fixed.


bug: Not showing diagnostics in Python file unless a line is deleted

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.9.0
Operating system/version
Windows 11 and MacOS
Describe the bug
I have a base lazyvim config with the Python extras. No other changes. Whenever I write a line of code in a Python file that should produce an error, I do not get error diagnostics. I only get error diagnostics after deleting a line.
This video should help illustrate the issue. I write sleep(), which should be an error since I didn't import it. However, I do not get any visual diagnostics until after I add a line and delete it.
https://github.com/LazyVim/LazyVim/assets/33569440/50bc9388-ebd4-4cb6-9dfc-607cabfef325
Steps To Reproduce

Open a new Python file
write sleep() or any line that would result in diagnostic that should be shown
exit insert and save

Expected Behavior
I would expect the red squiggles and ghost text to tell me I have an error.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Can't reproduce this with the python extra.

@folke I've reproduced this on 3 different machines, and swapped to my own personal config with the same tools installed and not found the issue. I'm not suggesting you're incorrect, but since you're so experienced I was hoping you might be able to point me in the right direction to solve this problem :D

no idea. I don't use python myself

no idea. I don't use python myself

I’ve also reproduced this in the docker container suggested on your website after installing pyenv and using nvm to install pyright. May I ask how you tried to reproduce? Did you use a docker container? Trying to narrow down differences to discover a cause.

same issue here

must be a pyright issue then. Either way, this is not a LazyVim issue.

must be a pyright issue then. Either way, this is not a LazyVim issue.

Can't be a pyright issue, cannot reproduce in my own config that uses same verisons.
@puppyapple will you let me know if you discover a cause or a fix?

@folke
I've tried the following experiments under the same  original configs only with { import = "lazyvim.plugins.extras.lang.python" } added to lazy.nvim.

Macbook air M1: pyright diagnostic infomation show well
Ubuntu 22.04: no pyright infomation displays
Ubuntu 22.04 with other pluging that support pyright lsp(Coc.nvim with coc-pyright): pyright diagnostic infomation show well

BTW, I used Lunarvim before and want to move to LazyVim. And Lunarvim also uses nvim-lspconfig to manage pyright lsp for python, the diagnostic works well in my Ubuntu.
So if it is possible there are some compatibility issue in the python config on Linux? @folke

must be a pyright issue then. Either way, this is not a LazyVim issue.

Can't be a pyright issue, cannot reproduce in my own config that uses same verisons.
@puppyapple will you let me know if you discover a cause or a fix?

@roberte777 Unfortunately, no progress for now...

I found my situation is a little bit different @roberte777

pyright seems to report some of the diagnostic like not defined but does not do any type checking or memberaccess check.  But it give all error when using in cmdline. So maybe it is not a  pyright issue? @folke

look, this is definitely not a LazyVim issue. It's either going to be a bug in Neovim diagnostics, Neovim's lsp, lspconfig or pyright.
There's also some work on Neovim done to support pull diagnostcis, so maybe that's somehow causing issues.
LazyVim does nothing special for diagnostics for pyright.
When I tested it, I didnt see this issue. Maybe different pyright version? No idea.

local pyright_opts = {
  root_dir = function(fname)
    local util = require("lspconfig.util")
    local root_files = {
      "pyproject.toml",
      "setup.py",
      "setup.cfg",
      "requirements.txt",
      "Pipfile",
      "manage.py",
      "pyrightconfig.json",
    }
    return util.root_pattern(unpack(root_files))(fname) or util.root_pattern(".git")(fname) or util.path.dirname(fname)
  end,
  settings = {
    pyright = {
      disableLanguageServices = false,
      disableOrganizeImports = false,
    },
    python = {
      analysis = {
        autoSearchPaths = true,
        diagnosticMode = "workspace",
        useLibraryCodeForTypes = true,
        reportGeneralTypeIssues = true,
      },
    },
  },
  single_file_support = true,
}
return {
  "neovim/nvim-lspconfig",
  init = function()
    local keys = require("lazyvim.plugins.lsp.keymaps").get()
    keys[#keys + 1] = { "<leader>ca", false }
    -- change a keymap
    keys[#keys + 1] = { "<leader>cA", false }
    keys[#keys + 1] = { "gr", false }
    keys[#keys + 1] = { "gd", false }
    keys[#keys + 1] = { "<leader>cd", false }
    keys[#keys + 1] = { "<leader>cf", false }
    keys[#keys + 1] = { "<leader>cl", false }
    keys[#keys + 1] = { "<leader>cr", false }
    keys[#keys + 1] = {
      "<leader>la",
      vim.lsp.buf.code_action,
      desc = "Code Action",
      mode = { "n", "v" },
      has = "codeAction",
    }
    keys[#keys + 1] = { "<leader>lr", vim.lsp.buf.rename, desc = "Rename", has = "rename" }
  end,
  opts = {
    servers = {
      pyright = pyright_opts,
      ruff_lsp = {},
    },
    setup = {
    },
  },
  config = function(_, opts)
    require('lspconfig')["pyright"].setup({ pyright_opts })
  end
}

New Progress:
I add config with function that mannually setup pyright with my own opts like showed above(So I think the default config https://www.lazyvim.org/plugins/lsp here for nvim-lspconfig is overrided if I understand well). Then I got all the diagnostics from pyright. @folke

does your project have a .vscode folder with settings?

No. For testing I created a brand  new and clean project.发自我的 iPhone在 2023年7月26日，18:41，Folke Lemaitre @.***> 写道：
does your project have a .vscode folder with settings?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Thanks for your continued work on this @puppyapple! I admit I stopped looking because I didn’t want to make Folke mad when he’s done great things with LazyVim. However, he is correct in the sense this still seems like it’s not a LazyVim issue, should I open an issue in neoconf instead?

@puppyapple I am seeing the same issue with python but also typescript files in lunarvim. They use nlsp settings but not neoconf. I wonder if there's some similarity between those two plugins that is causing the issue?

@puppyapple I am seeing the same issue with python but also typescript files in lunarvim. They use nlsp settings but not neoconf. I wonder if there's some similarity between those two plugins that is causing the issue?

I'm not an expert of nvim plugins so I could not say what really happened here. Mayby leave this to the experts. (BTW, I used to work well with Lunarvim without issue above.)
The other thing is that I think your issue in the video is a little different from mine. Have you tried to disable the neoconf.nvim to see what will happen?

I was having an inexplicable issue around lsp's using default python extra as well as various custom configs
I deleted the .vscode directory, and suddenly everything works fine
Not sure why that worked but posting here just in case. Thanks for the work on LazyVim, top notch, hope to save others from this gotcha.

I was having an inexplicable issue around lsp's using default python extra as well as various custom configs
I deleted the .vscode directory, and suddenly everything works fine
Not sure why that worked but posting here just in case. Thanks for the work on LazyVim, top notch, hope to save others from this gotcha.

Thanks for the tips, I'm sure this will help someone out in the future. However, I don't have a vscode folder.

I'm facing the same issue in C# file.
Actually the whole diagnostics today has been faulty. Not sure if there has been breaking changes or something...
Any updates on this?
To reproduce, clone the lazy vim starter template and test the UI Diagnostics.

I'm facing the same issue in C# file.
Actually the whole diagnostics today has been faulty. Not sure if there has been breaking changes or something...
Any updates on this?
To reproduce, clone the lazy vim starter template and test the UI Diagnostics.

No updates from me, I've just been living with it D: I'm not really sure where to start looking for the solution to this issue. I'm not even unwilling, I've been trying for a month, I just don't have the background

@roberte777,
I switched to "AstroVim" and it's working without issues so far.


Can't create or modify hyper::client::connect::Destination

I'm trying to write a connector that takes a destination, modifies it and passes it to the next connector. It seems this is currently not possible because there's no way to get a mutable reference to the internal state and only hyper can create new Destination objects.
My usecase is having a custom dns resolver as a Connector that resolves the domain before passing it to the final HttpConnector that creates the connection.

I definitely get the use case! I'd like to find a way to support it, but I'd also like to list why the constructor was so far private:

The Destination type may gain more fields, such as in #1485 to support ALPN.
I worried that if a Destination gained more fields in new release, and a connector didn't know that and could create their own, then it could be possible for some intent on the connect action could be silently lost.

What if, without adding a constructor, you could just mutate the internal URI of the Destination?

that would work for me as well

This would be nice for me as well. In hyper 0.11, I had a "stack" of composed connectors: HttpsConnector<ProxyConnector<HttpConnector>>. The ProxyConnector handled CONNECT tunneling for HTTPS proxies, and so needs to tell the underlying connector to point to the proxy address. In 0.12, that isn't currently possible so I ended up using a non-connector type under the ProxyConnector that just took a host/port.


fix misspell #84

Some syntactic corrections

Misspell now reports 100%.
Good job, thank you.
misspell100%
Misspell Finds commonly misspelled English words
No problems detected. Good job!


clean the temp file after the run

I have ended up with lots of folders. the temp files remain in place after the tool finishes running.

What temp files, and where are they left?

This one:
51 # this will create a directory with a random name, e.g. /tmp/mergin-work-packages-w7tbsyd7
52 tmp_dir = tempfile.mkdtemp(prefix="mergin-work-packages-")


Map String a <-> Object

Following the discussion here https://github.com/purescript-contrib/purescript-argonaut-codecs/issues/101
Could an EncodeJson / DecodeJson for Map String a be provided that convert from/to a javascript object instead of an array?
I think that this is the desired behavior in nearly all situations and when it isn't people can manually write their codec.

The proposed instance overlaps with the existing Map instance, so it's not really an option unfortunately.
If you want that encoding for with the least amount of work possible, maybe use an Object rather than a Map - it has much the same interface as Map but is restricted to String keys and will encode the way you're looking for.


finished semantic well-formedness of equality type

c.f. #181

ok I will pause here and do another PR for the last lemma.


Change Text Color statusbar

Can you change the color of text from statusbar?

I've added StatusBar::theme. To be analogous with the Qt Quick Controls 2 Material style, a light theme means dark text on light background, and a dark theme means light text on dark background.
The values of StatusBar.Theme and Material.Theme enum values are equal, so you can use either StatusBar.Light, StatusBar.Dark, Material.Light, or Material.Dark as you wish:
StatusBar {
    theme: StatusBar.Light // DARK TEXT (assumes LIGHT application theme/background)
}

vs.
StatusBar {
    theme: StatusBar.Dark // LIGHT TEXT (assumes DARK application theme/background)
}

Perfect
Thanks


Single-card training configuration error

Dear author, your work is very good! I have a problem when I am learning the single card, so I come to ask for help. The error is as follows:

Thank you for your answer.

Error supplement：

Hi, there is no problem with the changes you made to single-card training in train.sh. This problem may come from an incorrect version of a package in the environment, or from incorrect settings in the dataloader.


Should build products be documented and how?

This is essentially an open invitation for comment on the issue of build products. Below I've laid out some points to potentially address and think about.

Where is the best place for products to be documented?
Currently it seems like every vendor platform except QuickLogic does this in it's docstring for the platform. This is already rendered in the vendor section of the rendered documentation pages and this is likely a useful place for it to exist in some form. The question is if this adhoc method of documenting the available output products is really ideal given the importance of the information.
Should there be a programmatic way to query the available output products?
This is likely not particularly necessary, while initially I thought this might be desirable in enabling users to copy all products from a remote machine or into a specific location, this can likely be done just as well or better by just allowing the folder itself to be copied in some form.
Should there be any standardized interface to the products?
Obviously each platform's output is fairly unique, but there are some similarities, of these I think the most common likely products to exist are "bitstream/input to programmer software" type files, log files from the build, and any potential timing/DRC reports. It might be nice to have these extracted out so that at least some level of generic interface can be built on top. This also might result in a fragile mess that's not worth maintaining.
Should we document any changes to the products that a Platform will produce?
I think we should, but we should think about how we want to handle this given that vendor toolchains especially can change the outputs they can provide or their format essentially at a whim.

I think I've covered most of my thoughts here. Perhaps in a bit too much detail, but hopefully it gets us thinking about the options we can have.

Just so we lay our thoughts out on these issues also:

We think the current format of documenting them in the docstring is reasonable enough, but we might want to think about ways to format it a bit nicer or separate it out on the rendered documentation.
Probably not. I can't honestly see anything particularly good coming of this and it results in a list that must be kept in sync with the docstring above and the scripts that generate output, enabling a point of failure for little gain.
In general I think this isn't a terrible idea, but I think it would be something where we got to see an actual usecase before thinking about adding. It's likely to not be useful to the vast majority of users and of limited benefit for those that can use it.
As I said above, I think it's clear that we should mention if products change, add, remove, rename or change format in some obvious way unless it becomes a problem to keep up.

It seems like there's nothing actionable here.


Player: Be able to decline geolocation recording

When scanning a code, make geolocation recording optional

Done, geolocation can be tracked and declined using a checkbox.
The way that it's implemented, it will always attempt to always get user location on activity onCreate.
The user can click the location checkbox as many time as they want and nothing will happen.
Only when they hit Save, do we see if the checkbox is enabled or not.
If checked, do nothing, location is always stored
If unchecked, set the location tonull


🌱 cache: replicate all APIExports and APIResourceSchemas

Summary
Since we don't anticipate a huge number of APIExports and APIResourceSchemas we have decided to replicate all instances of those resources by default.
Previously only objects with internal.sharding.kcp.dev/replicate: "true" were replicated.
Related issue(s)
part of https://github.com/kcp-dev/kcp/issues/342
Closes #https://github.com/kcp-dev/kcp/pull/2087
Closes #https://github.com/kcp-dev/kcp/pull/2116

/lgtm
/approve


Slugify filenames when metadata found on Spotify too

Fixes #239.
We already run slugify on tracks when metadata is not found on Spotify (possible when not using Spotify track URI to download some song). I did not realize that is possible for tracks on Spotify to have special characters as well.
This PR fixes this issue.
P.S. Since, I am not close to a Windows for a few upcoming days. I'd be happy if someone can test these changes on a Windows machine to speed up things a bit.
Try downloading this track with debug mode enabled:
https://open.spotify.com/track/0MsrWnxQZxPAcov7c74sSo
and let me have the output. :smile:

OK, there we go!


transform classes with jar merging for debug

when i cloned you project into android studio a few days ago,it can't run normally for follow exception

You are probably including the library twice


Update Help class name selector.

updated the closed class on the widget to the new bb-help-closed class name

Codecov Report

Merging #314 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #314   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          59     59
  Lines        1370   1370
  Branches      208    208
=====================================
  Hits         1370   1370

Flag
Coverage Δ

#builder
100% <ø> (ø)
:arrow_up:

#runtime
100% <ø> (ø)
:arrow_up:

#srcapp
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[Event Request] Codeunit 12 - "Gen. Jnl.-Post Line" - OnBeforePostCust

Dear ALAppExtensions team,
through this issue we would like to request adding a new event publisher OnBeforePostCust in Codeunit 12 "Gen. Jnl.-Post Line" with the following signature:
[IntegrationEvent(false,false)]
local procedure OnBeforePostCust(var GenJnlLine: Record "Gen. Journal Line"; var IsHandled: Boolean)
begin
end;

which would be called as follows in PostCust:
local procedure PostCust(var GenJnlLine: Record "Gen. Journal Line"; Balancing: Boolean)
var
    LineFeeNoteOnReportHist: Record "Line Fee Note on Report Hist.";
    Cust: Record Customer;
    CustPostingGr: Record "Customer Posting Group";
    CustLedgEntry: Record "Cust. Ledger Entry";
    CVLedgEntryBuf: Record "CV Ledger Entry Buffer";
    TempDtldCVLedgEntryBuf: Record "Detailed CV Ledg. Entry Buffer" temporary;
    DtldCustLedgEntry: Record "Detailed Cust. Ledg. Entry";
    SalesSetup: Record "Sales & Receivables Setup";
    ReceivablesAccount: Code[20];
    DtldLedgEntryInserted: Boolean;
    ShouldCheckDocNo: Boolean;
    // >>>> New >>>>>>>>>>>>>>>>
    IsHandled: Boolean;
    // <<<< New <<<<<<<<<<<<<<<<
begin
    // >>>> New >>>>>>>>>>>>>>>>
    IsHandled := false;
    OnBeforePostCust(GenJnlLine,IsHandled);
    if IsHandled then
        exit;

    // <<<< New <<<<<<<<<<<<<<<<
    SalesSetup.Get();
...
end;

Thanks in advance!

Please explain why do you need replacement for one of the major procedures in Gen. Jnl.-Post Line?

Hi @AlexanderYakunin and @tkr95
Could you please reopen this case?
We have a user request wherein the user desires a custom modification to enable the entry of multiple payment methods on the invoice. Additionally, they would like each payment method to generate a separate entry in both the Customer Ledger Entry and Detailed Customer Ledger Entry tables.
I can see that events exists in other procedures in this codeunit:
PostVend:
IsHandled := false;
OnBeforePostVend(GenJournalLine, IsHandled);
if IsHandled then
exit;
PostBankAcc:
IsHandled := false;
OnBeforePostBankAcc(GenJnlLine, IsHandled);
if IsHandled then
exit;
PostICPartner:
IsHandled := false;
OnBeforePostICPartner(GenJnlLine, IsHandled);
if IsHandled then
exit;


Possibly missing info

I followed your tutorial, and I had error memprocfs couldn't initialize vmm.
Changing value of rw[21] to 1, just under following line

rw[20]      <= 1;                       //       CFGSPACE_STATUS_REGISTER_AUTO_CLEAR [master abort flag]

fixed my issue. Not sure what the issue is, but leaving it here as it may help someone else.
To give credit, following page suggested changing that value (in the video at the end of tutorial, before comments)
https://blog.rabu.me/dma-create-custom-firmware/

Interesting to see.
I built mine just fine while leaving rw[21] as the default and it ran fine with no issues. If I have the time, I will look into rw[21] and see what that controls. Glad you found a solution.
That link seems to be a pretty solid tutorial too! Doesn't go into too much depth, but it covers some things I perhaps did not such as flashing.


logpresso identifies CVE-2021-4104

I downloaded reload4j <IP_ADDRESS> from Maven Central and executed logpresso [1] on it via
log4j2-scan --scan-log4j1 reload4j-<IP_ADDRESS>.jar

I get the following output:
[?] Found CVE-2021-4104  (log4j 1.2) vulnerability in C:\Users\xxx\Downloads\reload4j\reload4j-<IP_ADDRESS>.jar, log4j N/A

Scanned 0 directories and 1 files
Found 0 vulnerable files
Found 1 potentially vulnerable files
Found 0 mitigated files
Completed in 0.01 seconds

I don't know how logpresso actually works to identify the issue. But as the intention of reload4j is to fix CVE-2021-4104, there seems to be some inconsistency. Not sure if the ticket is placed correctly here or if it should be opened in the logpresso repository. Any insights would be helpful to get a consistent view on the fix provided via reload4j to avoid confusions.
[1] https://github.com/logpresso/CVE-2021-44228-Scanner

@fipro78 CVE-2021-4104 has been fixed by hardening JMSAppender and not by removal. Is log4j2-scan checking for the removal of JMSAppender?

To be honest, I have no idea as I am just a user. But I have now also opened a ticket in logpresso. Maybe this way a communication can be established to solve the issue together.
https://github.com/logpresso/CVE-2021-44228-Scanner/issues/271

I think logpresso currently only checks if the JMSAppender class exists in the codebase and shows that output without checking it further.
See
https://github.com/logpresso/CVE-2021-44228-Scanner/blob/main/src/main/java/com/logpresso/scanner/Detector.java#L280
and
https://github.com/logpresso/CVE-2021-44228-Scanner/blob/main/src/main/java/com/logpresso/scanner/Detector.java#L352-L353

logpresso added a special handling for reload4j, so this issue can be closed.


Delay function can't access current state where it is referenced

Description
There is option to specify delay in state after section as function. In my use case it makes sense to use one function that calculates delay based on current state and optionally context variable value. It looks like currently delay function is called first, even before interpreter changes state.value and is calling onTransition listener.
Probably most general solution would be adding additional parameter (state or meta object that includes state like in actionFunction(context, event, actionMeta)) to delay function, which currently has (context, event) as parameters.
Less preferable solutions:

using service (interpreter).state, which would be updated before (now - after) delay function is called.
onTransition listener is called before (now - after) delay function is called. Then I set current state as variable to use in delay function

P.S. In reproduction I have added also changing context variable value, which happens after state is transitioned, just to understand better xstate inside. I guess it would be wrong idea to call delay function after entry actions are executed.
Expected Result
See reproduction. service.state is 'process' (state where delay function resides)
Actual Result
See reproduction. service.state is 'start' (previous state)
Reproduction
Simplest reproduction - https://codesandbox.io/s/xstate-example-template-vanilla-forked-wdzg3
Additional context
XState version 4.22.00

@ilmarmors Could you fill in a bit more detail on your use case? What is it that you're trying to achieve? Are you trying to have one delay length while in one state, and another delay length while in another?
We might be able to model this more idiomatically using current tools.

I have set of exercises user is going through one by one. All the exercises have the same flow - start, intro, position check, feedback and more. So basically all the exercises go through the same states and I'm using the same state machine. But there are differences among exercises for the same states - different duration, different parameters etc, which are stored in json configuration file
For example, I have state
body_orientation_instructions: {
  entry: [
    'showTextMessage'
  ],
  after: {
    // messageDuration: { target: 'body_orientation_wait' } // doesn't work as I wanted
    bodyOrientationInstructionsDuration: { target: 'body_orientation_wait' }
  },
  meta: {
    // wanted to avoid referencing machine interpreter in showTextMessage
    // when looking up message for current exercise, so I can use lookup id
    // which I choose to be the same as state id in this case
    state: 'body_orientation_instructions'
  }
}

and in machineOptions I have functions:
actions: {
  showTextMessage: function(context, event, actionMeta) {
    console.log('showTextMessage for '+ actionMeta.state.value);
    context.text_message = exercise.messages[actionMeta.state.value].text;
    // context.text_message is used in web app to display to user
  }
}

But delay function doesn't work like action - no access to current state meta data (3rd parameter exists but it is some kind of internal stuff), and interpreter.state has previous state, not current state. I wanted to be able to use one fuction
delays: {
  messageDuration: function(context, event) {
    return exercise.durations[delayMeta.state.value]; // can't work, no third parameter like in action
    return exercise.durations[machineService.state.value]; // don't work, contains previous state
  }
}

Workaround - use seprate state specific function for every delay, so no need to access current state
delays: {
  bodyOrientationInstructionsDuration: function(context, event) {
    return exercise.durations.body_orientation_instructions;
  }
}

It seems fairly reasonable that since we have meta for actions, we should do something similar for delay calculation. @Andarist, @davidkpiano thoughts?

Note that actionMeta.state might not always be what you think it is. For assign actions it's the "source state" (the state before transition) and for custom actions (functions) it's the state in which the machine lands after resolving all microsteps (after resolving all raised and null events) in a transition. This is not necessarily how it should work but it is how it currently works. We plan to refactor this for it to be more predictable.
Since the value of meta.state will always be somewhat misleading due to how our internal algorithm works... I would like to explore removing meta.state entirely. For that, I need to understand how people are using it because we should provide a better way to achieve the goals which have been enabled by it.
In this instance - you seem to want to provide per state (or rather maybe - per delay) configuration for a particular "executable content" (the delay "resolver" in this case). Would allowing the pattern presented below solve your problems?
// in the machine config
after: [{ type: 'calculateDelay', extraProp: 100 }]

// in the implementations object
calculateDelay: (ctx, event, { delay }) => {
  // do smth with `delay.extraProp`
}

Is there any info in documentation, which describes what is the sequence of microsteps during state transition? Or it is too implementation specific so it shouldn't be specified and people wouldn't rely on that information? Although I would say that clear logical sequence is good thing to be described.
For my case possibility to pass additional function argument (object that can contain many properties) is fine. That would be something like you wrote (and could be applicable not only to delay but also to actions, guards and any other function):
body_orientation_instructions: {
  entry: [
    'showTextMessage': { messageId: 'body_orientation_instructions' }
  ],
  after: {
    messageDuration: { target: 'body_orientation_wait', { stateId: 'body_orientation_instructions' } }
  }
}

and
actions: {
  showTextMessage: function(context, event, params) {
    context.text_message = exercise.messages[params.messageId].text;
    // context.text_message is used in web app to display to user
    // this example is simplified as probably the same effect can be achieved with assign
    // but you might want to do more complex calculations to calculate context var value
  }
},
delays: {
  messageDuration: function(context, event, params) {
    return exercise.durations[params.stateId];
  }
}

Regarding state and actionMeta. I see that there is good reason to know the state from which function is called, and no real reason not to provide that. You can call it somehow different than state, for example,callState so its value is clearly defined and won't depend on microstep sequence of state change

That would be something like you wrote (and could be applicable not only to delay but also to actions, guards and any other function):

Yes, this is already supported for some things (mainly for actions) - we should look into supporting this pattern for all the implementation "types" (guards, services, etc)

Regarding state and actionMeta. I see that there is good reason to know the state from which function is called, and no real reason not to provide that. You can call it somehow different than state, for example,callState so its value is clearly defined and won't depend on microstep sequence of state change

Right - I think what usually people want here is some kind of representation of the state node from which the thing is called (exactly like you have described it). The current meta.state doesn't deliver that (it is sometimes that - depending on the taken transitions, but that's mostly coincidental).

Is there any info in documentation, which describes what is the sequence of microsteps during state transition? Or it is too implementation specific so it shouldn't be specified and people wouldn't rely on that information? Although I would say that clear logical sequence is good thing to be described.

Quite good documentation on this can be found in the SCXML spec here. There are some subtle differences between their implementation and ours but conceptually we aim to follow that closely (while reserving the right to diverge from it where it makes sense to us, for a variety of reasons). We might want to document our exact algorithm in the future but that's probably something that we should revisit after releasing the next major version - v5.

All arguments can be destructured from the arguments object that we call your functions with in v5. state (or anything like it) is not part of this object though.
I firmly believe that people, usually, don't want the current state there. I'd love to hear more about your use case to suggest an alternative. We are also constantly reevaluating this decision - so who knows, maybe something like it will get added there in the future.

I'm very new to xstate and I'm only trying to design machine to have better control over app navigation than what typical router (e.g. Angular) offers. I find xstate very powerful and flexible, probably offering much more than I actually need so still not sure whether this may be an overkill in my case.
In particular let's say an app has reading feature, comprehension quiz, jigsaw puzzle. These are sll states and there is also start state in which first some particular kind of puzzle is presented and after that there is some guide message presented - as action - the guides are presented in many places of the app - via events - and often ideally I'd just use SHOW_GUIDE event and the action could know what message to present based on the state in the first place. Repeating the state when sending/raising the event adds extra verbosity to the already quite verbose machine config.

Made a pull request to add .stateNode for this and many other use-cases @ciekawy: https://github.com/statelyai/xstate/pull/4211


nixos/virtualisation/proxmox-image: fix SIGABRT during image generation

generation of proxmox image bugfix
Error log with actual version:

       > vma: ../util/error.c:59: error_setv: Assertion `*errp == NULL' failed.
       > /nix/store/3i2l6psna71r2jacfhm0b3yyki5905f8-vm-run: line 61:  1402 Aborted                 (core dumped) /nix/store/p1653ija0fjqfl6

bugfix description

vma create "vzdump-qemu-nixos-VERSION.dirty.vma" -c /nix/store/HASH-qemu-server.conf/qemu-server.conf drive-virtio0=$diskImage

Change  create to $out directory  ($out/vzdump-qemu-nixos-VERSION.dirty.vma) fixes the error.
Things done

Built on platform(s)

[x ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ x] Fits CONTRIBUTING.md.

Thank you for this change, please can you use the CONTRIBUTING guide to rename your commits accordingly (the new PR title is a suggestion) and squash them?
It seems like there are debugging leftovers in the change, I will put in draft in the meantime.

@RaitoBezarius squashed.

The best what I have achieved is reset to starting commit, then making commit which contains fix and add option.
Let me explain diskSize usage option with example:
flake.nix

{
  inputs = {
    nixpkgs.url = "nixpkgs/nixos-unstable";

    nixos-generators = {
      url = "github:nix-community/nixos-generators";
      inputs.nixpkgs.follows = "nixpkgs";
    };
  };
  outputs = { self, nixpkgs, nixos-generators, ... }: {

    packages.x86_64-linux = {

      proxmox = nixos-generators.nixosGenerate {
        system = "x86_64-linux";

        modules = [
          # nixos configuration:
          ./proxmox.nix
        ];
        format = "proxmox";
      };
    };
  };
}

proxmox.nix

{ config, lib, pkgs, ... }:
{
  services.sshd.enable = true;
  services.nginx.enable = false;
  networking.firewall.allowedTCPPorts = [ 22 ];
  users.users.root.password = "nixos";
  services.openssh.permitRootLogin = lib.mkDefault "yes";
  services.getty.autologinUser = lib.mkDefault "root";
  system.stateVersion = "22.11";
  environment.systemPackages = with pkgs; [
      htop
  ];

  proxmox = {
      diskSize = 40960;
      #Additional options appended to qemu-server.conf
      qemuExtraConf = {
          cpu = "host";
          onboot = 1;
        };
       qemuConf = {
          cores = 2;
          memory = 2048;
          bios = "seabios";
          name = "nixos-${config.system.nixos.label}";
          #virtio0 = "ceph:vm-123-disk-0";
       };
  };
}

Usage
Creating proxmox image 2 cpu, 2GB RAM, 40GB size

nix build .#proxmox

@ofborg test proxmox-image

I also get the *errp assert on non-NixOS (and not on NIxOS), but this patch does not fix it for me.
It seems to me to be a memory initialization-issue in the vma tool itself -- which may be sensitive on the output path.
I'm currently trying to enable debug symbols, and using rr and valgrind.
This may also have been fixed in newer QEMU versions:
https://lists.gnu.org/archive/html/qemu-devel/2021-06/msg02495.html
Moving to qemu 7.2 and newer patch from proxmox may also fix it.

Ignore my previous reply, it is wrong.
It turns out to be vma-writer.c uses O_DIRECT which is incompatible with tmpfs.
<EMAIL_ADDRESS>Also, going to qemu 7.2.0 didn't fix it.
(FYI, proxmox's patch does not apply to qemu 7.2.1)

@hernad Thanks for the diskSize! I'd like to see that go in :+1: .
But I do think writing to $out does not solve the SIGABRT in the general case.

Fixed in another PR.


MY Profile Enabed makes entire website not load.

For some odd reason when my profile is enabled the entire website will not load if logged out. This is with the newest edition.

Hey, I'm unable to reproduce that, could you please give me a link to your website? Or maybe some other plugins might be breaking it?

NVM i believe it was another plugin causing the issue due to the order they where installed in. anyways thank you.


Update-DSAsset -LargeImageKey "icon" not working

Update-DSAsset -SmallImageKey works but when I try it with -LargeImageKey it doesn't.

Updated LargeImageKey through manually adding it in Start-DSClient.ps1 + Added some text with it -> shows everytime now when I launch it.

Thank you for submitting an issue! It's been so long since I've worked with this project, i forget most of the details and won't have time for a while. any chance you can submit a pull request?


'Password changed' email received when you create an account

When you receive an account invite for the Register Management Tool, you need to set a password to create a new account. Once the account had been created, the user receives another email notifying them that their password has been changed. This is not as expected.
URL:
https://managing-registers-staging.cloudapps.digital/users/invitation/accept
Steps to recreate:

Receive email invite
Click on link
Create a password
Confirm a password
Click 'Set my password' button
Check inbox

Expected result:
No email.
Actual result:

required before this release


ndb window needs to be closed manually

Steps to reproduce

with webpack-dev-server started
DEBUG=true ndb jest -c jest.config.integration.js
All tests pass but debugger stays open

Tell us about your environment:

ndb version: `"ndb": "^1.0.26"
Platform / OS version: OSX 10.13.2
Node.js version: v8.12.0

What is the expected result?
ndb debugger window closes
What happens instead?
ndb debugger window stays open
Thanks! :)

I can confirm, debugger window stays opened for me as well.

Do you need ndb in this use case only in case when something goes wrong?
I believe that you can try following approach instead:

install ndb as dev dependency to your project or add global node_modules to NODE_PATH,
run NODE_OPTIONS=-r=ndb/inspect DEBUG=true jest -c jest.config.integration.js instead of your command.
later when you would like to debug your tests, just open ndb and it will automatically detects jest.


File saving not working

Once I change a file, and save it then new changes are not working it's still rendering the previous one.

/needsMoreInfo including coding language, platform, version, and what you mean by "not rendering".


Update to MongoClientURI javadoc

URI can contain collection name which is not mentioned in javadoc. Fixed.

Is this dropped later by accident in current MongoClientURI or collection will be dropped eventually from it?


Create composer.json

@suin great lib! Thanks!

Note: I thought about rewriting to psr-4, but the way it already works very well.

I look forward to the release package :D

Thanks you!!


Can't build with the latest DMD (2.067.1)

Subj. "dub build" spits this:
source/star/entity/entity.d(70): Error: undefined identifier 'conv'

It seems that std.conv isn't imported for some reason. Adding
import std.conv : to;

at the beginning of entity.d seems to solve the issue, hovewer I'm not sure that this is an optimal way, so I don't make a PR for now.

This should be closed, since it was fixed in 2d3ec4c.


Installation request for laravel/scout == <IP_ADDRESS> -> satisfiable by laravel/scout[v6.0.0].

Problem 1
- Installation request for laravel/scout == <IP_ADDRESS> -> satisfiable by laravel/scout[v6.0.0].
- asolopovas/scout-elasticsearch v3.0.0 requires laravel/scout ^3.0 -> satisfiable by laravel/scout[3.0.x-dev].
- asolopovas/scout-elasticsearch v3.0.1 requires laravel/scout ^3.0 -> satisfiable by laravel/scout[3.0.x-dev].
- Conclusion: don't install laravel/scout 3.0.x-dev
- Installation request for asolopovas/scout-elasticsearch ^3.0 -> satisfiable by asolopovas/scout-elasticsearch[v3.0.0, v3.0.1].

This project is cool but need to be upgraded to scout v6.

Added Scout v6 support in v3.9.0. Please, update the package in your projects.


Bug: Shipping details are cleared/erased when auth route is queried at checkout

I have consistently been able to reproduce this bug, it appears that the checkout provider is recreated when the user auth session is queried (see video below)

Clear cookies/session data
Add an item to bag
go to checkout page
begin filling out form
when auth is queried, the form is erased

I am guessing that when the checkout provider is recreated, the entire <CheckoutForm> component is remounted, causing the data loss.
No workaround at the moment
https://github.com/medusajs/nextjs-starter-medusa/assets/3488482/37282339-bd00-458a-bbf1-70343a72538b

Same here

while trying to diagnose the issue I have found that there is a difference in the cart object returned from useCheckout() on the 2nd load of the checkout component. It appears that the property payment_sessions is an empty array on first load, and later populated with the active session from stripe.
Still unsure why the Checkout component does not hold the values between renders

I am guessing that the payment session causes the entire component tree to be mounted again when the data changes, looking at CheckoutProvider:

I have implemented a workaround for now:
change CheckoutForm to call useCheckout instead of useCart
const CheckoutForm = () => {
    const { cart } = useCheckout();
   ...
}

also render a spinner where <Addresses /> was until the payment_session prop has a value to prevent customer frustration

    {!cart?.payment_session &&
        <StepContainer index={1} title="Shipping" closedState={

                <Spinner />

        } />
    }
    {cart?.payment_session && <Addresses />}

If someone from the medusa team has any insights, I am still uncertain as to why the component is unstable. I read through the payment docs but it did not shed any light on why the this storefront implementation behaves this way. The system is still very new to my knowledge to be clear.
Customers are unhappy with their carts being cleared after ~1 sec of typing, as one might expect

Would be great to have some more eyes on this issue.
Can confirm the we are experiencing it as well.
Removing this code from the <Payment /> component in the checkout "fixes" the problem, but then we don't get the intended fallback:
`const Payment = () => {
const {
cart,
setPaymentSession,
initPayment,
sameAsBilling: { state: isSame },
} = useCheckout()
/**

Fallback if the payment session are not loaded properly we
retry to load them after a 5 second delay.
/
/ useEffect(() => {
let timeout: NodeJS.Timeout | null = null
if (cart?.shipping_address && cart?.payment_sessions) {
timeout = setTimeout(() => {
initPayment()
}, 5000)
}

return () => {
  if (timeout) {
    clearTimeout(timeout)
  }
}
// eslint-disable-next-line react-hooks/exhaustive-deps

}, [cart]) */
return (.....`
Anyone else have a good fix for this bug?


[BUG]

Hi, this bug happened to me, before this happened, I could delete messages from dms etc but, I got this bug.
I went on discord google, pressed f12 to get access to the console, pasted the code, got the "menu" then did the usual steps, pressed get authorization, author, guild and channel.
I pressed start and this happened:
Started at 14/06/2020 à 04:31:17
authorId="REDACTED" guildId="REDACTED" channelId="REDACTED" afterMessageId="REDACTED" beforeMessageId="REDACTED" hasLink=false hasFile=false
Error searching messages, API responded with status 404!
{"message":"404: Not Found","code":0}
Here's a screenshot https://prnt.sc/szbpmw
Thanks if you fix the problem.

Same

I have the same problem. It's very annoying. Doesn't work on Chrome or any other browsers. Please fix it if you can soon thank you very much.

It's a discord issue, see here https://status.discord.com/incidents/zthbs4tmjt70

It's a discord issue, see here https://status.discord.com/incidents/zthbs4tmjt70

It says the issue is resolved yet the script is not working, what is the reason?

4.0 is out lmk if it is working for you


Update for node 12

Thanks @sebakerckhof!
I'll merge and publish. It'll have to be a major version bump since this is backwards incompatible with all Meteor versions older than 1.8.2.


CI tests fail because of undefined migrations

Some PRs fail CI tests, because their tests attempt to run on undefined database tables and relations.

Resolved by #43


setAnimData still broken

When a SingletonGeoAnimatable is registered, the class name used by registerSyncedAnimatable is com.class.name.Here.
However, when getSyncedAnimatable is called, the string passed to it is instead class com.class.name.Here, resulting in this message:
Attempting to retrieve unregistered synced animatable! (class com.class.name.Here)

lol. sigh.


Env file missing after build extension by "vsce package"

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Zip plugin does not handle inner file name contain glob character

e.g. if you create a zip file that contains a file with name [a].txt then the unzip command will look like
unzip -p -- a.zip \[a\].txt

to which unzip command will see its argument as [a].txt and perform another level of glob matching, resulting in no match.
In my version, it suffices to escape the characters \[?*. Escaping ] appears to be unnecessary but I see no harm either.
--- a/runtime/autoload/zip.vim
+++ b/runtime/autoload/zip.vim
@@ -234,7 +234,7 @@ fun! zip#Read(fname,mode)
   " but allows zipfile://... entries in quickfix lists
   let temp = tempname()
   let fn   = expand('%:p')
-  exe "sil! !".g:zip_unzipcmd." -p -- ".s:Escape(zipfile,1)." ".s:Escape(fname,1).' > '.temp
+  exe "sil! !".g:zip_unzipcmd." -p -- ".s:Escape(zipfile,1)." ".s:Escape(escape(fname, '\?*[]'),1).' > '.temp
   sil exe 'keepalt file '.temp
   sil keepj e!
   sil exe 'keepalt file '.fnameescape(fn)

Not sure if it works on Windows/other platforms/implementations of unzip.
A small Python script for testing  a.zip

Please follow the bug report template and test with the latest commit.


[BUG] Invalid receipts error with rest function call

When rest functions are called, invalid receipts errors are triggered:
https://github.com/ainblockchain/ain-blockchain/blob/master/consensus/index.js#L708

Resolved.


BUG: if sealos pull/push failed, error logs will be printed twice.

Sealos Version
v4.1.4
How to reproduce the bug?
run cmd

sealos pull hub.sealos.cn/labring/affine:latest

What is the expected behavior?
error logs should be printed only once.
What do you see instead?
error logs is printed twice.
Operating environment
- Sealos version:
- Docker version:
- Kubernetes version:
- Operating system:
- Runtime environment:
- Cluster size:
- Additional information:

Additional information
eg:
# sealos pull hub.sealos.cn/labring/affine:latest                                                                                [2:52:01]
Trying to pull hub.sealos.cn/labring/affine:latest...
Error: initializing source docker://hub.sealos.cn/labring/affine:latest: reading manifest latest in hub.sealos.cn/labring/affine: errors:
denied: requested access to the resource is denied
unauthorized: authentication required

initializing source docker://hub.sealos.cn/labring/affine:latest: reading manifest latest in hub.sealos.cn/labring/affine: errors:
denied: requested access to the resource is denied
unauthorized: authentication required

Is this a bug?

Yes

here is my solution: https://github.com/labring/sealos/pull/2519

pkg/buildah/buildah.go
set buildah cmd.SilenceErrors = true


chore(polar_area_chart): add data-testid attribute

Build succeeded (check pipeline).

Build succeeded (check pipeline).

Build succeeded (check pipeline).

Build succeeded (check pipeline).

LGTM

Sonar scan result
More detail, see in https://sonarqube-gate.intgdc.com/dashboard?id=gooddata-dashboard-plugins-gate-PR71
To scan for vulnerabilities in dependencies and run unit tests (to get coverage report in sonar) please comment your PR with 'extended check sonar'.

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-dashboard-plugins-sonarqube-scan-zuul-gate/64/ : SUCCESS in 1m 02s
https://checklist.intgdc.com/job/compliance/job/gooddata-dashboard-plugins-fossa-scanning-zuul/41/ : SUCCESS in 1m 24s (non-voting)
https://checklist.intgdc.com/job/compliance/job/gooddata-dashboard-plugins-merge-compliance-check/65/ : SUCCESS in 6s


Only upload a block if it doesn't already exist

Fixes #524.  Also fixes an issue I'm seeing in production where we are exceeding the per-object rate limit for GCS by overwriting the same block over and over again.

Should look into the CI failures before you merge obviously. Could just be the same types of intermittent failures we've been seeing.


Front end layout complete #55

Front end Nav and Chat layout with ng-view.
Also, re-route landing page directly to app to bypass login for now since the login is not functional.

Need to add functionality but seems like a good general layout, we'll develop on it!

#55


Resolve using BigUint or BigInt [LOW PRIO]

https://github.com/summa-dev/summa-solvency/blob/482f2790191be9a72ecae21cfb5b8a85757e1834/zk_prover/src/chips/overflow/utils.rs#L4C1-L8C1
It seems like we have a duplicate of the same API here
https://github.com/summa-dev/summa-solvency/blob/482f2790191be9a72ecae21cfb5b8a85757e1834/zk_prover/src/merkle_sum_tree/utils/operation_helpers.rs#L9
Should we use BigUint or BigInt?

Should we use BigUint or BigInt?

In the context of the zk_prover within the circuit, I believe using BigUint would be a slightly better option.
This could help us avoid accidentally storing a negative number at some point in the future.

Sounds good to me. Can you modify it such that we use a unique converter function?

Sure I will make it.


Fixes 294: Save button on edit modal

This adds a small fix to the Save button to ensure that it won't be accessible between validation calls.

https://issues.redhat.com/browse/HMSCONTENT-294


Add docs reference info

Add docs sample reference info will allow it to show up in samples, which only has 1 thing in it today :( https://docs.microsoft.com/en-us/samples/browse/?expanded=dotnet&products=blazor
See: https://github.com/dotnet/EntityFramework.Docs/blob/main/samples/end2end/PlanetaryDocs/README.md
for example:
---
page_type: sample
description: "This repository is intended to showcase a full application that supports Create, Read, Update, and Delete operations (CRUD) using Blazor (Server), Entity Framework Core and Azure Cosmos DB."
languages:
- csharp
products:
- dotnet-core
- ef-core
- blazor
- azure-cosmos-db
---

Thanks @jamesmontemagno ... Sorry for the delay! I just found these issues over here. These samples are all linked into the Blazor doc set of the dotnet/AspNetCore.Docs repo, and that's where we normally work and receive pings on issues. I'll see if I can address this today (6/16).

😕 ... I'll research further because I already have the following in the README.md file without this repo appearing in the search results as you say ...
---
page_type: sample
languages:
  - csharp
  - razor
products:
  - aspnet-core
  - blazor
name: Blazor sample applications
urlFragment: blazor-samples
description: "Samples to accompany the official Microsoft Blazor documentation."
---

I wonder if that indentation is hosing it. I'll remove the indentation (at least).

Hummmmm ...
https://docs.microsoft.com/en-us/samples/browse/?expanded=dotnet&products=blazor
There might be a delay given that I just added the dotnet-core entry. Or, there might be a management gesture required. I've pinged Rick and Wade offline for assistance.

UPDATE: Looks like the repo isn't picked up automatically. It will need to be tagged internally somehow. We're working on it internally.

Will ping @jongalloway  who can help here

There's also a form that needs to be submitted once per repo, once that's done the repo is scanned for docs with frontmatter as part of the process. I submitted for this repo.

Showing up in review now: https://review.docs.microsoft.com/en-us/samples/browse/?branch=main&expanded=dotnet&products=blazor


Refactor useCientos to new state context provider

Description
Adapt cientos package to https://github.com/Tresjs/tres/issues/331 changes
Abstractions

[x] Environment
[x] MouseParallax
[ ] Stars
[x] Smoke
[x] Levioso
[x] Contact Shadows
[ ] Precipitation

Controls

[x] OrbitControls @alvarosabu
[x] TransformControls
[x] PointerLockControls
[ ] KeyboardControls
[x] MapControls
[x] ScrollControls

Materials

[ ] WobbleMaterial

Staging

[x] Backdrop

Misc

[x] useTweakpane

Suggested solution

[x] Refactor watchers
[x] Remove deconstruct props if needed
[x] Merge to 'next'

Alternative
No response
Additional context
No response
Validations

[X] I agree to follow this project's Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

@alvarosabu I don't see changes related to the new state in stars and precipitation.
Can we mark them as ready?

What do you mean @JaimeTorrealba I had not worked on them yet, have you?

@alvarosabu they don't use useCientos or any context related


Unable to setup multiple blogs

I’m having issues setting up a second blog to an existing website.
activate :blog do |blog|
  blog.layout = "article_layout"
  blog.permalink = ":title.html"
end

activate :blog do |blog|
  blog.name = 'jobs'
  blog.prefix = "jobs"
  blog.permalink = "jobs/{title}.html"
  blog.sources = "/jobs/:year-:month-:day-:title.html"
end

There seems to be a problem using blog.name, when I try to start middleman I’m getting the following error:
/config.rb:2:in `block in initialize': undefined method `name=' for #<Middleman::Blog::Options:0x007f8527069038> (NoMethodError)

Hmm, what if you set a name on both?
Can you post your Gemfile.lock and the full error message?

I'm doing some issue-gardening 🌿🌷🌾 and came across this issue.
Sorry that this has lingered for quite a while! I'd suggest either closing this issue or submitting a PR with an implementation as a starting point for discussion around this.


source-git + create-srpm = :heavy_check_mark:

This PR enables create-srpm for source-git repos when the spec file is in a dedicated folder.
It also fetches the upstream tarball for source-git projects instead of creating it.

and I also need this one!


chore(deps): :arrow_up: update dependency @types/node to v20.10.6

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@types/node (source)
20.10.5 -> 20.10.6

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@angular/animations
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-01-02T00_36_53_633Z-eresolve-report.txt

npm ERR!


language not working

its seems its not working on python for me
ive tried a few others and it works just fine

are you sure that python is assigned to "python" in the language selection ( what matters is the language identifier, inside the () )


Added commands to list vpx contents and script.

./vpxtools ls  list the files inside an vpx without extracting.

and looks like rust fmt was not applied

Updated commands to println in main.rs


AMBARI-24006. Enhance ERROR returned in case of incorrect Mpack Version passed during Mpack Advisor call.

What changes were proposed in this pull request?
For instance during Mpack Advisor's Recommendation call, in case wrong Mpack Version is passed, the error returned as part of API response is following:
POST http://[AmbariServer]:8080/api/v1/mpacks/recommendations
Error parsing services.json file content: null
One possible reason is if wrong/non-existing Mpack version is passed-in in the REQUEST body.
{
	"hosts": [
		"host1.openstacklocal",
		"host2.openstacklocal"
	],
	"recommend": "configurations",
	"recommendations": {
		"blueprint": {
                              "mpack_instances": [{
				"name": "HDPCORE",
				"type": "HDPCORE",
				"version": "1.0.0-b121",   ---- > if WRONG_VERSION_NUMBER
                                 .........

Fix: Return information on passed-in Mpack Name and Version, and suggested checking for the Name, version and its existence.
Error retuned after fix:
Error parsing created services object for Mpack Advisor Python Code. Attempt to read services information for passed-in Mpack : "HDPCORE" and version : "1.0.0-b4121" is NULL. Check passed-in Mpack Name, Version and corresponding stack's existence in cluster.
How was this patch tested?
Tested on cluster.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2555/
Test FAILed.
Test FAILured.

As we discussed the API call to stacks endpoint should have returned 404 instead of 200 OK. Looks like we need to investigate why the API call is not reporting this error.

I agree that we should abandon this change - it's very stale and doesn't address the root problem.


ISPN-5314 Increase worker thread pool in SocketTimeoutException tests

https://issues.jboss.org/browse/ISPN-5314

Increasing worker thread pool size avoids propagating SocketTEs into operations executed after the SocketTimeoutException has been thrown back to the client.

There are SocketTimeout failures in the PR

Hmmmm, looking...

Updated fix, HotRodTestingUtil was hardcoding workerThreads to 2!!

Integrated, thanks @galderz


Update PoC instructions to use 2 Cassandra instances in separate namespaces

Also merged latest master. Actual changes of this PR are in commit https://github.com/mesosphere/kudo-cassandra-operator/commit/7125f67636763e439904ff38149434287ea0eb4b.

I shouldn't have merge master here. This is making things more complicated. Let me merge master into node-replace-pod then rebase this PR. Otherwise "Squash and merge" will cause trouble.


Interpretation of the immediate value for the vnclipu.vi , ,  instruction is not clear

The interpretation of the immediate value for the vnclipu.vi <vd>, <vs>, <imm> instruction is not clear from the specification 0.7
Does the immediate specify a single unsigned value range 0-31, or two unsigned value ranges 0-15 and 0xfff...fff0-0xfff...ffff?

Jim Wilson of SiFive says this should be the same as the scaled shift
instructions immediately above (in the spec), hence it is unsigned 0 to 31.  This is
an issue with the spec that it should be clarified.


Incorrect resolving paths (Angular)

Version: 1.3.51
import { TestBed } from '@angular/core/testing';

Actual<EMAIL_ADDRESS>Expected<EMAIL_ADDRESS>Because contents of<EMAIL_ADDRESS>{"main": "../bundles/core-testing.umd.js"}

Hm.. so you are saying that any folder can contain a package.json that should be treated as well?

I suppose yes.
https://github.com/substack/node-resolve/blob/master/lib/sync.js#L54

Fair enough, will be fixed

That's a big issue... I must admit, requires a lot of thinking there. =(

Maybe create some kind of Remap plugin as stop gap solution?
{
 '@angular/platform-browser/testing': <EMAIL_ADDRESS>}

Can you point me to the right direction where to start, if it is possible?

You want to try to fix it?
I actually have a branch there issue88, where i solved the issue at bundle time. But the front end still does not understand that instead of pointing to index.js it has to point to a different file. That's the problem. We have this stuff
I was thinking of making it in the config as well like you suggested, but the loader is still a problem.
In order for you to proceed, you can just point to the actual file in that package.json.
Let's think about it... I am working on different approaches still.

https://github.com/fuse-box/fuse-box/issues/324

this is solved now, please reopen otherwise :)


integrations: added honeybadger webhook

Testing Plan:
Tested it manually using the dev env and integration tool

Kindly review.
All the specified changes has been taken into account.

@punchagan
Made the changes as suggested.

@timabbott
Could you review the changes?
I have integrated the suggestions.

@timabbott
Any more changes?

Can you work on improving these templates?  I feel like after reading the tests, they don't seem like a very nice way to present the information contained in the payloads.
For example, I think a lot of your links could be in markdown, and given that very long messages are possible, it seems like those should often be in a paragraph by themself.

@timabbott
I have added Linking and Emphasis in the templates. Regarding the large messages, a large message only arrives in the case when a comment is made. I have handled that case differently and put the message bode in a different paragraph.

@timabbott Any more issues?


[PreCheck] Filter out macro declarations from result set

Move logic from ConstraintGenerator::visitOverloadedDeclRefExpr
to pre-check to avoid including macro declarations referenced without
#. This means that pre-checking would synthesize TypeExpr in
situations when there is a type reference that is shadowed by a stdlib
macro.
Resolves: https://github.com/apple/swift/issues/67815
Resolves: rdar://114796811

@swift-ci please test

@swift-ci please build toolchain macOS


update codec bg and border

Description & motivation 💭
Add background and border color to data encoder
Found a tooltip issue here, making a jira ticket to get it fixed.
Screenshots (if applicable) 📸
Before :

After :
dark:

light:

Design Considerations 🎨
Testing 🧪
How was this tested 👻

[x] Manual testing
[ ] E2E tests added
[ ] Unit tests added

Issue(s) closed
DT-1993

We'll also want to update /components/data-encoder-status.svelte and account for various states ⬇

I was going to do this in a separate PR, but can totally add it to this one <3 Thanks for catching this Laura, I appreciate you!


Shipyard not found host conainers after power outage

After power outage and reboot shipyard not any more find containers. In Shipyard web GUI gives followed error.
Error...
{"data":"No elected primary cluster manager\n","status":500,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"url":"/containers/json?all=1","headers":{"Accept":"application/json, text/plain, /","X-Access-Token":"admin:XXXXXX"}},"statusText":"Internal Server Error"}
Enviroment is running top of latest stabile coreOS version (Stable
766.4.0 with Docker 1.7.1)

vi /etc/selinux/config
settings SELINUX=disabled
Remember to restart the server.

This seems to be a duplicate of #636 and etcd electing a master.  Thanks for reporting.  We will track this issue there.


impl_969

Will there be a release version for this?
(I need to request to pull this in via corporate channels).

I'm working for that. I guess that the new release will be on this weekend. Please wait a moment :)

https://github.com/redboltz/mqtt_cpp/releases/tag/v13.2.0 has been released.


Remove the requirement for bucket details when deploying the enterprise server

In the hackathon when deploying the enterprise server to GKE we noticed it was impossible not to supply a bucket name, even though the enterprise server doesn't use a GCS bucket. This PR re-orders the arguments so GCS/ABS/S3 are the last arguments and can be skipped if the enterprise server flag is set.
/cc @nadegepepin - this will be relevant for the enterprise server docs, but we also need to update all the deploy docs since the arguments change order.

NB: the golden manifest tests are currently disabled - I ran them locally and these changes are fine, but our manifests have drifted in production quite a bit. We should re-enable them prior to 2.0.


Storing Application Insights' Instrumentation Key in AzureAppConfig

Environment details:
ASP.NET Core application (discovered in 2.2, reproduced in 3.0 before filing issue), Not sure if this is a caveat/bug for ApplicationInsights or AzureAppConfiguration, but I wanted to bring it up.
I believe I may have found a compatibility issue when using the default setup with Application Insights and Azure App Configuration? It seems like something in the AzureAppConfiguration is triggering the TeletryClient (and consequently the TelemetryConfiguration) to be instantiated when there's no key defined yet (since it's stored in the Azure App Config), and because they are only created once it never uses the key it will obtain from AzureAppConfiguration.
Reproduce:
Have an AzureAppConfig setup with at least one key/value pair of ApplicationInsights:InstrumentationKey and a valid instrumentation key for its value, (empty label)
New ASP.NET Core application
*I went for 3.0 with MVC pattern, but I don't it matters in this instance
Add reference to Microsoft.ApplicationInsights.AspNetCore
Add reference to Microsoft.Extensions.Configuration.AzureAppConfiguration
My CreateHostBuilder inside of Program.cs is as follows
public static IHostBuilder CreateHostBuilder(string[] args) =>
    Host.CreateDefaultBuilder(args)
        .ConfigureAppConfiguration((context, config) => {
            var appConfigName = "..."; //Name of the AzureAppConfig

            config.AddAzureAppConfiguration(options => {
                options.ConnectWithManagedIdentity($"https://{appConfigName}.azconfig.io")
                    .Use("*", labelFilter: LabelFilter.Null);
            });
        })
        .ConfigureWebHostDefaults(webBuilder =>
        {
            webBuilder.UseStartup<Startup>();
        });

Within one of the cshtml files (I just put this in _Layout)
@using Microsoft.ApplicationInsights.Extensibility
@using Microsoft.Extensions.Configuration
@inject TelemetryConfiguration telemetryConfiguration
@inject IConfiguration config

@config["ApplicationInsights:InstrumentationKey"]

<div<EMAIL_ADDRESS>
The InstrumentationKey pulled from the config will have the value from the AzureAppConfig, but the telemtry client will not.
If you put the instrumentation key in any of the local appconfig.json files (appconfig.json, appconfig.development.json, or even the secrets.json file) then both statements will have the correct instrumentation key.

Same for me : this  does not work
services.AddApplicationInsightsTelemetry();
While this works :
var key = Configuration["ApplicationInsights:InstrumentationKey"];
services.AddApplicationInsightsTelemetry(key);

The current implementation of IServiceCollection.AddApplicationInsightsTelemetry extension method with no arguments uses the default options that only use configuration from certain locations specified in the following code.
var configBuilder = new ConfigurationBuilder()
    .SetBasePath(this.hostingEnvironment.ContentRootPath ?? Directory.GetCurrentDirectory())
    .AddJsonFile("appsettings.json", true)
    .AddJsonFile(string.Format(CultureInfo.InvariantCulture, "appsettings.{0}.json", this.hostingEnvironment.EnvironmentName), true)
    .AddEnvironmentVariables();

ApplicationInsightsExtensions.AddTelemetryConfiguration(configBuilder.Build(), options);

It is possible to update the implementation of the following method in Application Insights to retrieve configuration from IConfiguration injected within the service collection.
public static IServiceCollection AddApplicationInsightsTelemetry(this IServiceCollection services);

However, this approach is not guaranteed to work, since IConfiguration registered in the service collection may not be instantiated at the time of initialization of TelemetryClient. An explicit instantiation of IConfiguration in the Application Insights code would cause an additional unintended load of data from all configuration providers. Therefore, this is not a good idea.
In order to enable the settings within App Configuration to be used, I would suggest using the following overload of AddApplicationInsightsTelemetry that takes an IConfiguration instance as an additional parameter. This will ensure that the settings within this instance would be used for initialization of TelemetryClient.
public static IServiceCollection AddApplicationInsightsTelemetry(this IServiceCollection services, IConfiguration configuration);

Working Code for Startup.cs
public IConfiguration Configuration { get; }

public Startup(IConfiguration configuration)
{
    Configuration = configuration;
}

public void ConfigureServices(IServiceCollection services)
{
    services.AddControllersWithViews();
    services.AddApplicationInsightsTelemetry(Configuration);
}

We will add this usage sample to our documentation to make it easier for other users to avoid this issue.


Cleanup license headers from snippets and samples

The snippets and samples sporadically define the apache license header. We probably add it because Idea automatically pastes it in every new source files. It is not required though and makes the snippets/samples database inconsistent.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.


Citation numbers appear in square bracket instead of as numeric superscripts

When using this citation style, I am getting numerical references but they are of this fashion:
Fisher [1] instead of Fisher1
My preamble
\usepackage[backend=biber,style=nature,articletitle=true,intitle=true,natbib=true]{biblatex}
Citation command
This is a citation \citep{Fisher1930}.

You are using the wrong citation command: you want \supercite or \autocite. See the core biblatex docs on this.


Not working on Windows 10 - Chrome 81.0.4044.138

While the tool does outputs some cookies, this aren't really the cookies of the user.
Chrome dev tools opens the page in some kind of container, without the user's cookies.
The cookies it outputs are just the cookies that google sets automatically, without the user being logged in.
If you delete de --headeless parameter in the source code, run the tool and when chrome opens you go to http://localhsot:9222/json/new?https://some_page_you_are_logged_in.com you will see you are not going to be logged in this URL, that's why the tool can't retrieve the real cookies.
At least that is what I understood. Only tested in Windows 10, on the latest Chrome.

BTW, i used the pull requests update that is not yet on the main branch to make it work.

Please you can see my repo works all version browser
https://github.com/hakanonymos/steal-chrome-password-all-version

Well, It did work! very interesting work @hakanonymos , I will take a closer look!


AssistantClient.CreateMessage() doesn't support using the Assistant role

This capability was added to the spec just a few months ago: https://github.com/openai/openai-openapi/commit/9fcd900b58005549ab77d3e8af20f58473ce4d07
The implementation currently hard-codes the User role (which made sense prior to the above) and needs to support creating an Assistant message.

Fixed by: #81


Refactor AddProjectFromGithub to run separate queries for orgs+repos

Rationale: https://www.loom.com/share/38dee712127349b39f835da740849cbc
Currently this feature fetches all the data needed in 1 API call
We should separate fetching the list of organizations, then when an organization is selected we fetch the repos for only that selected organization

@mecoccaro


Ensure RLMSupport.swift's SequenceType additions iterate over an RLMResults snapshot

A user reported that using Realm Objective-C from Swift doesn't iterate over a frozen TableView when SequenceType-enumerating an RLMResults:
let realm = RLMRealm.defaultRealm()
let allItems = uncheckedItemsNoUpdate()

try! realm.transactionWithBlock({
  for itemObj in allItems {
    if let item = itemObj as? GroceryListItem {
      item.deleted = true
      item.syncStatus = SyncStatusNeedsUpdate
    }
  }
})

We should investigate if this is truly what's happening here, and if so mark this as a bug and fix this.
I was under the impression that NSFastGenerator on a collection with a custom enumerator would use the custom enumerator (where the TableView copy is done), but that wouldn't appear to be the case based on this report.

Just to jump in, I was the user JP is referring to. Let me know if I can help or provide more information about my particular situation. Thanks!

Closing this as it's already supported by RLMSupport.swift https://github.com/realm/realm-swift/blob/master/Realm/Swift/RLMSupport.swift, which extends RLMResults and makes it conform to Sequence which allows iteration over a RLMResults.
This test passes.
class TestObjectRLM: RLMObject {
    @objc dynamic var stringCol = ""
    @objc dynamic var boolCol = false
}

func testRLMResultsIterationFromSwift() throws {
        let realm = RLMRealm.default()
        realm.beginWriteTransaction()
        realm.createObject("TestObjectRLM", withValue: ["string A"])
        realm.createObject("TestObjectRLM", withValue: ["string B"])
        try realm.commitWriteTransaction()

        let allItems = realm.objects("TestObjectRLM", with: NSPredicate(format: "TRUEPREDICATE"))
        XCTAssertEqual(allItems.count, 2)

        try realm.transaction {
            for itemObj in allItems {
                if let item = itemObj as? TestObjectRLM {
                    item.boolCol = true
                    XCTAssertEqual(item.boolCol, true)
                }
            }
        }
}


Removed unused var from DockJsonManipulator.

+1

The failed CI check seems to be due to me merging it too quickly or something.


avoid stubs maintance

Closes #64
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed
[ ] Branch name follows type/descript (e.g. feature/add-llm-agents)
[ ] Ready for code review

ℹ Additional Information

follow the settings in vllm.
Link mypy with config-file: https://github.com/vllm-project/vllm/blob/main/.github/workflows/mypy.yaml
Ignore import checking: https://github.com/vllm-project/vllm/blob/main/pyproject.toml

@ProKil I change and fix a few potential bugs that appears after changing to non-strict mode without stubs.

I think stub files have their role in mypy check.

But the stubs is only related to third-party packages, right?
If type errors happen when using stubs, it should raise error from the third-party and it looks like is the common case to avoid adding stubs for mypy?
vllm avoid this:
https://github.com/vllm-project/vllm/blob/main/pyproject.toml
[tool.mypy]
python_version = "3.8"
ignore_missing_imports = true
check_untyped_defs = true

after switching from strict mode and stubs files to loose model of mypy, I actually came across a few additional type error that I found that is indeed potential bugs. Therefore, it looks like strict mode testing of mypy does not strictly indicate more strict checking.

I have to ponder a bit more on this. I think one of way is to remove most of the dependencies we currently have, including LangChain.

sure

Based on our discussion offline. We can work on cut the dependencies instead of removing stubs all together.


fix: black hole z= replacements

Standard vim and vanilla neovim both blackhole z= replaced words
This makes the behaviour more like a vanilla z= as you don't end up with the misspelt word in your register

Thanks!


Wiki is not updated

Information on the wiki is not up to date. The sftp server IP need to be changed.
cc: @treddington @theryecatcher

Updated the wiki and removed the publicly accessible IP address.


Heart rate and calories on watch stuck at 0

Don't think this is an issue with the server, it's most probably with the app on the watch. It might not have access to the data it needs or something. See attached screenshot.

Also getting this when running the app. Seems like the websocket connection can't be established (not sure if this is related):
node ./public/app.js
Listening at port 8080
(node:16564) UnhandledPromiseRejectionWarning: Error: Could not connect
at Socket.onerror (C:\Users\diete\Downloads\Health-Data-Server-Overlay-3.0\Health-Data-Server-Overlay-3.0\node_modules\discord-rpc\src\transports\ipc.js:32:16)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
(node:16564) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:16564) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Client connected
This is what gets served:

Please assist, and let me know where I can help.
Thanks
Dieter

If anyone faces this same issue, it's permissions related. Go to your iPhone Settings > Health >Data > Health Data Server and switch on read and write permissions from there.

The server app spits out that error when it can't connect to a local Discord instance. I should probably consume that error somewhere so the user doesn't see it.


Minor additions and improvements: purge aliases, new rep triggers, etc

Added purge aliases: clean, clear
Added new rep_triggers: thnx, tnx, tysm, tyvm, thanx
Added commands.guild_only() for the following commands (even though it's not really needed for purge and cleanup, just for code consistency hehe):
• Purge (cogs/moderation/Line406)
• Cleanup (cogs/moderation/L393)
• Giverep (cogs/reputation/L83)

Also, a side note: the ?col command has stopped working, and it doesn't show collecting pokemon of any user. I believe it has something to do with this commit fdeb1629b9c4b9ad9badd66974e4805d0e8826d9 (not sure tho)

Thanks!


bump github.com/DataDog/nikos to v1.12.5

What does this PR do?
This PR bumps the nikos dependency to v1.12.5 (release notes). The main drive behind this bump is to remove the forced dependency on zstd coming from nikos, and replace it by something that can work in non-cgo mode.
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


update to remove dependency on perl for 'list' feature

The install relies on perl for a single-line rexex when scraping the
Bintray website for a list of REX-Ray versions available for install.
This tiny update removes the need for the installing operating system to
have Perl installed, mostly because RHEL does not have Perl installed by
default. One other option would have been to trap the error and echo
some sort of message calling for the user to install Perl, but that
seems drastic, considering the same page scrape can be executed just
fine using the bash built-in command 'cut'.
This update should not affect any other versions, as 'cut' hasn't really
changed its syntax in decades.

Coverage remained the same at 100.0% when pulling ff2571eb5c7609c86516a9e2496007df4ba4d43c on installer-remove-perl into d668199a001a5539547539b73cc4f72c148fb124 on master.

[Current coverage][cc-pull] is 100%

Merging [#439][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master   #439   diff @@
====================================
  Files           1      1
  Lines          93     93
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits           93     93
  Misses          0      0
  Partials        0      0

[][cc-pull]

Powered by Codecov. Last updated by [d668199...ff2571e][cc-compare]
[cc-base-branch]: https://codecov.io/gh/emccode/rexray/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/emccode/rexray/compare/d668199a001a5539547539b73cc4f72c148fb124...ff2571eb5c7609c86516a9e2496007df4ba4d43c
[cc-pull]: https://codecov.io/gh/emccode/rexray/pull/439?src=pr

Hi @mux23,
Seriously? RHEL doesn't have Perl by default? This was tested on CentOS, which is based on RHEL. Thanks for doing this BTW. I just don't know the current script was ever validated if the above failed.

Hi @mux23,
This is being closed as your commit will be merged as part of #474.


Enable magic for .tab file extension

I noticed in a comment that .tsv files get some defaults changed automatically.
Can you enable this for .tab files too, a common alternative TSV extension?
Or honour a XSV_TSV_EXTENSIONS=tab,tsv env var?
Much like the much desired XSV_DEFAULT_DELIMITER etc

I don't think I've ever heard of the tab extension, but the Wikipedia article does list it along with tsv. A PR would be welcome.


Write documentation

Currently, opstooling-js has a lot of utility methods that, unless you jump to read the code, are invisible. So it usually ends up with @mutantcornholio commenting in the code reviews that there is already a method for that.
Let's write a clear and concise documentation showing a bit of each method and linking it to the file if necessary (or adding an example on how to use it). This would improve visibility and usability.
We can also use a doc generation tool using the documented methods.

We can also use a doc generation tool using the documented methods.

Let's do this.


feat support star exclude modifier

When we query many fields in a wide-table,
but ignore one field or two fields,
we need to write out fields we need one by one.
Therefore, try to use select * exclude (excluded_item1, excluded_item2, ...),
the sql will be simplified.
Checklist(Required)

Does it affect the original behavior: (No)
Has unit tests been added: (No)
Has document been added or modified: (Yes)
Does it need to update dependencies: (No)
Are there any changes that cannot be rolled back: (No)

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

I found discussion here: https://stackoverflow.com/questions/729197/exclude-a-column-using-select-except-columna-from-tablea

It is best to be consistent with the sql of the data warehouse that supports this kind of syntax.

It is best to be consistent with the sql of the data warehouse that supports this kind of syntax.

I try to make it similar to BigQuery, using except dialect.


Add a license file to Cargo.toml

This is a legal requirement for distributing software in Fedora.
Fixes #90

Thanks for the PR !


Query: Convert SetOperator.Source2 from EntityQueryable to QueryModel…

… when applicable.
This causes issue when translating EntityQueryable to SelectExpression as there is no query source.
resolves #7279

Updated.


2.0.0rc4: Interactive learning still exports nlu-data and stories as markdown

Rasa version: 2.0.0rc4
Python version: 3.8
Operating system (windows, osx, ...): Windows 10 1909
Issue:
Stories (and also NLU training data) generated with interactive learning are still exported in the old markdown format.

thanks! duplicate of https://github.com/RasaHQ/rasa/issues/6935 I think. Already fixed and the release is imminent! :)


Skip recompiling when running tests

/azp run java - cosmos - tests

/check-enforcer override

Overrode check-enforcer as live tests were able to run properly and that was the only check needed from them