convenience tmap function

I find myself writin a lot of code like:
    generator = Base.Generator(zip(models, input_splits) do (model, inputs)
        predict(model, inputs; kwargs...)
    end
    tcollect(generator; basesize = 1)

Which I coild also write in direct generator from but I find that a bit too long:
tcollect((predict(model, inputs; kwargs...) for (model, inputs) in zip(models, input_splits); basesize = 1)

What I would like to write is:
tmap(zip(models, input_splits); basesize = 1) do (model, inputs)
        predict(model, inputs; kwargs...)
end

Code I ended up writing for this was:
"""
    tmap(f, xs...; basesize=1)

Multithreaded version of `map`(@ref).
`basesize` controls how the minimum number of items `xs` to process per thread.
If the function is slow (>1ms), then `basesize=1` is good.
If the function is faster then `basesize` should be set high enough that proccessing that
many items takes some time (~1ms). This is to counter the overhead of how long it takes
to dispatch work to a thread (~1μs).
"""
function tmap(f, xs...; basesize=1)
    # We collect the zip to make sure can split it up. Its not always required
    # TODO: workout how to avoid collect when not required.
    inputs = collect(zip(xs...))
    return tcollect(MapSplat(f), inputs; basesize = basesize)
end

Supporting zip-of-arrays should be easy.  I guess tmap could be a nice API but I'm not 100% sure.
Regarding the first snippet, you can just write
generator = Base.Generator(models, input_splits) do model, inputs
    predict(model, inputs; kwargs...)
end

without zip. (Also, you'll be able to use Iterators.map after https://github.com/JuliaLang/julia/pull/34352)
If we add a curried version of tcollect it would look like
predictions = Iterators.map(models, input_splits) do model, inputs
    predict(model, inputs; kwargs...)
end |> tcollect(basesize = 1)

which takes the same number of lines as
predictions = tmap(models, input_splits; basesize = 1) do model, inputs
    predict(model, inputs; kwargs...)
end

Arguably, the curried version of tcollect composes well with other components; e.g., you can insert |> withprogress to get the progress bar
predictions = Iterators.map(models, input_splits) do model, inputs
    predict(model, inputs; kwargs...)
end |> withprogress |> tcollect(basesize = 1)

or to produce a DataFrame
Iterators.map(...) do ...
    ...
end |> withprogress |> tcopy(DataFrame, basesize = 1)

Note: |> in above examples are the usual x |> f = f(x).

Your curried tcollect has no interest to me as
I will not use regular |> in my codebase.
It puts things in the wrong order when the rest of the codebase always has return value  controlling function on the left.
Your examples there are nice and I once would have really liked them. But I no longer write any code that work in that way.
gen = Iterators.map(models, input_splits) do model, inputs
    predict(model, inputs; kwargs...)
end
tcollect(withprogress(gen); basesize = 1)

is almost as nice and return type control remains always on the left.
But anyway, this is not a thread for discussing |>

But for discussing something that exists only to match existing API from Base.
I guess main argument against it is it would allow people to use Transducers.jl very shallowly, without delving into what a Transducer is or how to compose them.
This is also the main argument in favor of it.

As I said, I half-agree that tmap would be a nice addition. I'm just brainstorming if there can be a nice API.

I guess main argument against it is it would allow people to use Transducers.jl very shallowly, without delving into what a Transducer is or how to compose them.
This is also the main argument in favor of it.

Yes, this is a good summary of my struggle.

zip is supported by #203.

I thought about tmap but I think it's best to implement it outside Transducers.jl.  This is because:

tcollect and alike do not propagate size information, at least at the moment.  This is for using the same implementation for transducers that may break the shape (e.g., filtering).  But, arguably, it is better for tmap(f, ::Matrix) to return a Matrix.
tmap(f, xs::AbstractArray) can use extra assumptions that are not available in general reduce:

For example, the shape of output is known.  So, it can implement (slightly?) more efficient mechanism than tcollect by using the approach like Base.collect_to! (setindex!-based) instead Base.grow_to! (push!-based).
You can use return_type as an optimization and then minimize the allocation when the output type of f is inferred to be a concrete type.
You can schedule the tasks more dynamically in tmap since each work is "independent."  This would let you squash O(log N) "clean up" work into O(1). https://github.com/tkf/Transducers.jl/issues/136#issuecomment-573583512

(OTOH, I think implementing tmap based on Transducers.jl for the moment is a good choice because all the tmap implementations out there rely on return_type AFAIK.)
Maybe it makes sense to create a package (say) ThreadExtras with tmap that just wraps tcollect for the moment.  It can do post-hoc reshape to satisfy the first point.  It can gradually drop Transducers.jl once it has its own implementation.  Threads.foreach(f, ::Channel) from https://github.com/JuliaLang/julia/pull/34543 can be a good addition, too.  Although I don't need this personally so not really motivated to do this... Maybe I'll create ThreadExtras when I need more efficient tmap at some point.  But I'm closing this issue for now.

Just FYI, other libraries with "tmap":

https://github.com/tro3/ThreadPools.jl
https://github.com/mohamed82008/KissThreading.jl
https://github.com/baggepinnen/ThreadTools.jl
https://github.com/Jutho/Strided.jl


Lotus Statue + Necklace of Skulls - Make that combo work.

As it is, both relics compete for the same resource, the grid. I need a way to let both (and any similar others in the future) know that there are other classes that want to use the resources they are trying to get.

Or... not. Main thing here is that Lotus Statue is removing the cards ONE at a time and that makes a mess together with Necklace. Better to just or find a way to enable an "ok" to the removal choice OR let the player set before a "how many cards do you want to remove" choice with created choice cards.
By the way, I prefer the "how many cards do you want to remove". That makes the Lotus Statue not compete with Necklace.
Yeah, should do that.

 Let's go with an half-hardcoded solution.

No, just made the problem worse. -_-

Fixed.


Split up the main module

The Test.Predicates module contains over 50 names, which makes it hard to browse.  It would be nice to split these up into smaller submodules containing clusters of related combinators: for example, "container-related predicates" or "regular expression predicates" or "text predicates".  The lines might sometimes be blurry between the groups, but we can just make a choice.  The goal is to make it easier to find the predicate you're looking for from the haddock.
The Test.Predicates module should still re-export everything, but the generated haddock will refer to the re-exported submodules, rather than containing the complete list, and the module documentation for these submodules creates a great place to compare them and explain how to choose which you're looking for, and things like that.  See https://hackage.haskell.org/package/HMock-<IP_ADDRESS>/docs/Test-HMock.html for an example of a module that re-exports submodules in this way.

Not planning to do this.


Option to configure http proxy settings doesn't work at installation

Environmental Info:
K3s Version: v1.22.1+k3s-699ea165

Node(s) CPU architecture, OS, and Version: amd64, Ubuntu 2104

Cluster Configuration:

1 master, 1 node
Describe the bug:

As mentionned in #2026 and #3552, a new feature has been added to configure HTTP proxy settings, for Containerd.
However, these settings are not taken into account in the installation script, as only the "_proxy" environment variables are written in the service environment file.
Steps To Reproduce:

Install K3s master node with INSTALL_K3S_COMMIT=699ea165231cf6d665425c50ff5c75e1831f4afb and variables prefixed with "CONTAINERD"
On the master node, check the content of the /etc/systemd/system/k3s.service.env

Expected behavior:

the /etc/systemd/system/k3s.service.env should contains all environment variables prefixed with CONTAINERD
Actual behavior:

the /etc/systemd/system/k3s.service.env doesn't contain the environment variables prefixed with CONTAINERD
Additional context / logs:

@rancher-max you've tested the fact that the environment variables are used when the k3s service starts after you manually modify the service definition, could you test with my PR that it works correctly from the install script ?
Backporting

[ ] Needs backporting to older releases

Validated on the PR itself that this is working as expected. See comments there. Thank you again for the contribution!


info text on share popup on what sharing means in modal

This will allow you to share this chart string with anyone.  It will not be tied to your account, team, or folder.

done


Specify version in pack command to eliminate need for nuspec rewrite

The "pack" task of the build currently rewrites all of the nuspecs in order to include the generated version number. We can avoid the need to rewrite the nuspecs by specifying the version as an argument to the NuGet pack command instead.

CI failure is the Xunit race condition we have seen before. Is there a way for me to retrigger the build without rebasing the branch?

@eatdrinksleepcode unfortunately this won't work. The reason for nuspec rewrite is that the version number of the dependencies needs to be specified as well. E.g. Bau.Exec depends on Bau, and if we are building version 0.1.0, then Bau.Exec needs to depend on Bau 0.1.0. You'll notice that, without the rewrite, Bau.Exec ends up depending on Bau 0.0.0.
There are a few other projects which do something very similar in their build scripts, e.g. https://github.com/NancyFx/Nancy/blob/a8841e0c33d5ef9169f874da0eba7bcea4d7f1ca/rakefile.rb#L116-L148
Incidentally, one of the ideas I have for Bau.NuGet is to wrap up all this re-writing in a custom task.

Ah, yeah I missed that. I was wondering why the MSBuild and NuGet projects were both specifying Version with the command line switch and core wasn't :)
It's unfortunate that all of this nuspec rewriting is the only way to achieve these linked version numbers. It makes the build script very messy. Wrapping it into a task will help, but I still can't help feeling that there should be a better way.

There should definitely be a better way. A very simple way to achieve it is to use the version passed in with -Version to replace all occurrences of $version$ in the nuspec. However, this is not how replacement tokens work in nuget.exe (at least the last time I checked).


[README.md] Clarify docs re: --exec command (closes #19087)

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Clarify docs re: --exec command. As bug says, docs say --exec runs after file download, when actually it runs after download and processing (e.g. merging formats).

README is autogenerated.


Add normalisation tips

Code for max, min-max and z-shapes normalisations

These are actually scaling tips :-)


Un-fix the footer

The fixed footer takes a huge part of the page. Here's a small change to make it visible at the end of the page only.

Perfect! Thanks for the fix.


pull

pull just pull

Please don't make random pull requests

@8972legand The settingsRename.php is called like that, because if you cloned from git, you don't want your productive settings file checked into the repository. Hence it's listed in the .gitignore file and you have to do the the renaming process. :)


NDRS-535: add more fields to DeployProcessed server sent event

The output of a DeployProcessed event in the event stream is now equivalent to the following:
{
   "DeployProcessed": {
      "deploy_hash": "871f50ca3cc5627947e4310850b03e0a105a2ae4d028a2a85a9258455da30114",
      "account": "010c801c47ed20a9ec40a899ddc7b51a15db2a6c55041313eb0201ae04ee9bf932",
      "timestamp": "2020-10-27T01:55:17.276Z",
      "ttl": "1day",
      "dependencies": [],
      "block_hash": "d233ce4865db29eea5c54bb2074ea11b51d736ba46082d62f299323e10f36601",
      "execution_result": {
          ...
      }
   }
}

bors r+


how to get result from executed action

My action in contract creates a record in persistent storage and creates new id of a product.
How to get id (any other data) of this product using eosjs after action executed ?

> eos.getTableRows()
USAGE
getTableRows - Fetch smart contract data from an account.

PARAMETERS
{
  "json": {
    "type": "bool",
    "default": false
  },
  "code": "name",
  "scope": "name",
  "table": "name",
  "table_key": "string",
  "lower_bound": {
    "type": "string",
    "default": "0"
  },
  "upper_bound": {
    "type": "string",
    "default": "-1"
  },
  "limit": {
    "type": "uint32",
    "default": "10"
  }
}

RETURNS
{
  "rows": {
    "type": "vector",
    "doc": "one row per item, either encoded as hex String or JSON object"
  },
  "more": {
    "type": "bool",
    "doc": "true if last element"
  }
}

@jcalfee thx!

you need to enable --contracts-console on nodeosd

Hi, i am posting here to avoid duplicating issues as mine is very similar.
I am trying to execute an action on a contract, this action store data with a primary key value. I would like to get this primary key value as i need to use it to store other data with other actions that refer to that original set of data (via the primary key value). My understanding is to use the transaction id to read the result of the transaction/action and get the primary key from there somehow, but how do i get it from the result of the action ?
Second question is where could i read the documentation in how the action, the action result and the contract are structured (type, methods and properties, etc). I found the documentation to be unclear.
const signatureProvider = new JsSignatureProvider([privateKey]);
const rpc = new JsonRpc('http://<IP_ADDRESS>:8000', { fetch });
const api = new Api({ rpc, signatureProvider, textDecoder: new TextDecoder(), textEncoder: new TextEncoder() });

  try {
    var item = req.body;
    api.getContract('contractname').then((contract) => {
     //What is / How is formed "contract" ?
      contract.additem (JSON.stringify(item )).then(result => {
       //What is / How is formed "additem" ?
       //What is / How is formed "result" ?
          console.log("contract.additem 's result is : " + result);
      });
    });


backend check to ensure stock does not go negative

updated medication quantity field from integer to positive integer field
added check in patch request

lgtm, will merge soon


tool action does not find new script location

With the scripts having been moved, this now occurs:
k2cli tool kubectl --config ~/.kraken/jj-r53.yaml get nodes
Using K2 config file: /home/jjulian/.kraken/jj-r53.yaml
Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "exec: \"./computed_kubectl.sh\": stat ./computed_kubectl.sh: no such file or directory"
panic: Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "exec: \"./computed_kubectl.sh\": stat ./computed_kubectl.sh: no such file or directory"

This issue was moved to samsung-cnct/k2cli#133


how can I run my .ipynb files code by c++ kernel

Issue Type: Feature Request
I have installed python extension, so I can open .ipy now.
But, I have some troubles when run cells. Because they were written by c++ kernel. And I can not choose my installed c++ kernel. Is that not allowed?
VS Code version: Code 1.49.3 (2af051012b66169dde0c4dfae3f5ef48f787ff69, 2020-10-02T17:56:11.027Z)
OS version: Linux x64 5.4.0-49-generic snap

/extPython


fix runtime error toast

fix https://github.com/microsoft/pxt-arcade/issues/2211
Add back in toast when we get a runtime error. This got dropped when adding support for runtime errors to error list (here); this adds it in as the default behavior for the method that gets overwritten to propagate to the error list.

I thought this behavior was intentional. Error are propagated to error panel.


Mouse back button support in install package/themes

Using the mouse back button in the install package/themes page should be included as a feature. Makes browsing packages or themes much nicer. If there is a package that does this that would be nice but I couldn't find one.

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/settings-view/issues/912. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.

ah thanks


Short URLs

What do you think about using rel-shortlink for twitter-syndication?

sounds like @singpolyma would like this too (#422).
@singpolyma, out of curiosity, what's your use case for short urls? i'm always curious since twitter now t.co-wraps all links, so their length no longer matters, and no other supported silos limit chars.
btw, you can currently get bridgy to use a short link when publishing if you put the short link into the interactive UI instead of the full link, or use it as the source param if you're webmentioning. https://www.brid.gy/about#short-link

It's about visual noise.  If I post "it sure is hot outside" then a Facebook post like:
it sure is hot outside

(Original Link: https://singpolyma.net/2015/06/it-sure-is-hot-outside)

Just looks excessive...
Also, on twitter, I use algorithmic shorturls that I would prefer be displayed rather than t.co links (though of course it will be wrapped in t.co underneath in official clients)

I think this is a good idea, it may not be too easy to send the shortlink in the webmention in your system.

note to myself: i think i can find the shortlink(s) in a page with just:
soup.find_all('link', rel='shortlink') +
  soup.find_all('a', rel='shortlink') +
  soup.find_all('a', class='shortlink')

quick survey! rel-shortlink, which @pfefferle mentioned, is evidently the standard (or close enough).
looking at recent posts from the three people who requested this:
@pfefferle has:

<link rel="shortlink"> in head
<input class="shortlink" value="[URL]"> in body

@singpolyma has:

<link rel="shorter short_url"> in head

@dissolve has:

<a rel="shortlink" class="shortlink u-shortlink"> in body

looks like shortlink is the winner. sorry @singpolyma! you'll want to update your markup if you still want to use this feature.

class="shortlink" is hAtom/mf1, and we should probably add it to
backcompat parsing of mf2py instead of to Bridgy.
On Thu, Sep 17, 2015, at 08:54 AM, Ryan Barrett wrote:

quick survey! rel-shortlink[1], which @pfefferle[2] mentioned, is
evidently the standard (or close enough).

looking at recent posts from the three people who requested this:

@pfefferle[3] has:

 in head

 in body @singpolyma[4] has:

 in head @dissolve[5] has:

 in body looks
like shortlink is the winner. sorry @singpolyma[6]! you'll want to
update your markup if you still want to use this feature.

— Reply to this email directly or view it on GitHub[7].

Links:

http://microformats.org/wiki/rel-shortlink
https://github.com/pfefferle
https://github.com/pfefferle
https://github.com/singpolyma
https://github.com/dissolve
https://github.com/singpolyma
https://github.com/snarfed/bridgy/issues/173#issuecomment-141130389

evidently the way to get a feature into bridgy is to have three different people ask for it. :P


Added Device Pixel Ratio

Without the pixel ratio, shadows and other render objects depending on a pixel ratio will appear different from the original widget during flipping

Thanks


fileprovider issue

Change : android.support.v4.content.FileProvider
To: androidx.core.content.FileProvider
You have missed migration for file provider, it crashes app

Thanks, I have fixed it. e989433

Thanks, I have fixed it. e989433


This plugin only works for :web role

Hi,
Is there a specific reason why it should only work on :web role? I have RESTful API servers which I want to use this plugin for and I just learned that nginx:setup task only works on :web role.
Thanks,

You can assign your servers multiple roles. By making it possible to
separate the web and app role, this gem gives you the flexibility to setup
your cluster in the way you want.
On 20 July 2016 at 10:38, Dano Lee<EMAIL_ADDRESS>wrote:

Hi,
Is there specific reason why it should only work on :web role? I have an
API server which I want to use this plug in for and I just learned that
nginx:setup only works on :web role.
Thanks,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/capistrano-plugins/capistrano-unicorn-nginx/issues/86,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABobTJJ8aDGNstTyF08psic-8HZPkbm5ks5qXd58gaJpZM4JQjLp
.

Hi @rhomeister,
I do understand that. We are running a system composed of API servers, web servers for dashboard, workers, etc. I use :web role for our web servers for dashboard only and :app role for API servers to manage efficiently. For example, API servers do not need to precompile assets. In order to use this plugin I have to break this policy. Is there a better way to do this? I will appreciate your advice.
Thanks,

Hi @nextofsearch,
That's a tricky situation. I'm sure it can be solved somehow, but I can't give you any concrete pointers without digging deeper. By the way, if asset precompilation is the problem, maybe you can turn this off for the app role in the gem that you use for assets?
Cheers

Hi, @rhomeister,
I guess turning if off is the only solution for now. It would be nice if this plugin supports a custom role.
Thanks,


interpolate.ndgriddata.griddata causes Python to crash rather than raise QhullError

Hi,
Just wanted to let you know that since I've updated scipy to v0.18 (at work) and v0.19 (at home) on my windows computer it causes python to crash completly when using interpolate.ndgriddata.griddata.
Whilst using the same script previously, but with scipy v0.17 it raised a QHullError which I could catch. Since the upgrade however, python just crashes completely.

Please provide a self-contained script (e.g. runnably by "python
myscript.py") that causes such a crash.

griddata_issue.zip
Hi, please find attached. The data is included in the zip file. Sorry it is a bit large, but when I tried to use the first and second half of the input points separately, the problem did not occur.

Thanks, can confirm that that indeed crashes, so this is possible to investigate.

This is a Qhull bug. zcat bad-points.txt.gz | qdelaunay Qz also segfaults.
bad-points.txt.gz

Forwarded issue to qhull devs

Was fixed in Qhull 2019.1, so fixed by upgrading (#10413)


Not loading css

Hi  to all contributors and developers.
I recently made an installation and after getting it to work, i noticed it can't load the css files which exist in the folders. Might that have something to do to the way you are using to load assets in the templates ?
I am using a virtual host. Maybe the assets should be in the web folder.
Greetings.
Here is an screen shot

Hello!
Did you run the assets dump command?
php bin/console assetic:dump --env=prod

Thank you @ParisLiakos. I did not. I run php bin/console assets:install instead, but after your quick answer, i fallowed your suggestion and it worked smoothly.


feature/add-sphinx-docs

This PR includes a new directory containing sphinx documentation

@paranoya we can now upload the docs to reathedocs.


Omnichannel for Customer Service - not in Applications list

If you are not seeing Omnichannel for Customer Service listed in the Applications for configuration, then check out the directions from The CRM Ninja, Installing Omnichannel for Dynamics 365

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

ID: ccb94189-d65e-a39d-5280-8dddd77afbcf
Version Independent ID: f55521f2-5c80-04c2-85b1-b6612d91cfda
Content: Provision Omnichannel for Customer Service
Content Source: ce/omnichannel/administrator/omnichannel-provision-license.md
Service: dynamics-365-customerservice
GitHub Login: @lalexms
Microsoft Alias: laalexan

Hello @barrcode,
The provisioning experience of Omnichannel for Customer Service has been updated and the content has been updated to reflect the process. Therefore, I understand that this issue is no longer applicable and can be closed.
Best regards,
Neeraja


Simplify get_initial_state

I think the current way is there because of CNTK compatibility. I tried the simpler version first when I was refactoring the RNNs...
CC @souptc

Closing, we can revisit applying this refactor when CNTK supports it.


Transform test suite to RSpec

We noticed we weren't getting correct test coverage results on this repo. Digging into it, this test  suite was still on Test::Unit, and simplecov appears to not work properly with that anymore.
I've converted the suite to RSpec, which brings it more in line with our other projects. Locally running SimpleCov also shows that it appears to fix the inaccurate coverage results as well.
This conversion was done mostly with a bunch of local sed scripting & manually fixing cases I couldn't handle automatically, so there's probably still some messy bits. I personally don't think we need to get this perfect in every little bit of the test suite. Tests pass with no warnings, so I think it's pretty good.

cc @codeclimate/review

We noticed we weren't getting correct test coverage results on this repo. Digging into it, this test suite was still on Test::Unit, and simplecov appears to not work properly with that anymore.

wonder if it's worth digging into that and possibly printing a warning from our test reporter and/r refusing to send payloads if we detect they're using Test::Unit
(looking at the content of the conversion now)

wonder if it's worth digging into that and possibly printing a warning from our test reporter and/r refusing to send payloads if we detect they're using Test::Unit

Not sure it's worth it. Test::Unit hasn't been the default way to write Ruby tests for several years.

This LGTM -- now my other PR will have more accurate coverage
Nice:


Cluster creation fails with spec.clusterNetwork.cniConfig.cilium.policyEnforcementMode: "always"

What happened:
We would like to enable "default deny" for Cilium. So, following the documentation we added spec.clusterNetwork.cniConfig.cilium.policyEnforcementMode: "always" to the cluster config for a new PoC cluster.
Then, we tried to create the cluster which failed with the following error message after Installing networking on workload cluster:
Error: applying Cilium manifest for install: executing apply: Error from server (Invalid): error when creating "STDIN": Namespace "<no value>" is invalid: [metadata.name: Invalid value: "<no value>": a lowercase RFC 1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?'), metadata.labels: Invalid value: "<no value>": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue',  or 'my_value',  or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?')]
Error from server (NotFound): error when creating "STDIN": namespaces "<no value>" not found

If we remove the policyEnforcementMode: "always", then the cluster gets installed without any issues.
What you expected to happen:
We expect that the cluster can be installed with policyEnforcementMode: "always"
How to reproduce it (as minimally and precisely as possible):
We use the following cluster config with 4 nodes (1 CP and 3 worker) for out PoC cluster:
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: Cluster
metadata:
  name: eks-a-bm-poc
spec:
  clusterNetwork:
    cniConfig:
      cilium:
        policyEnforcementMode: "always"
    pods:
      cidrBlocks:
      - <IP_ADDRESS>/16
    services:
      cidrBlocks:
      - <IP_ADDRESS>/16
  controlPlaneConfiguration:
    count: 1
    endpoint:
      host: "<IP_ADDRESS>"
    machineGroupRef:
      kind: TinkerbellMachineConfig
      name: eks-a-bm-poc-cp
  datacenterRef:
    kind: TinkerbellDatacenterConfig
    name: eks-a-bm-poc
  kubernetesVersion: "1.24"
  managementCluster:
    name: eks-a-bm-poc
  workerNodeGroupConfigurations:
  - count: 3
    machineGroupRef:
      kind: TinkerbellMachineConfig
      name: eks-a-bm-worker01
    name: worker01
  identityProviderRefs:
  - kind: OIDCConfig
    name: eks-anywhere-azuread
  gitOpsRef:
    name: kubernetes-infra-addons
    kind: FluxConfig

---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellDatacenterConfig
metadata:
  name: eks-a-bm-poc
spec:
  tinkerbellIP: "<IP_ADDRESS>"
  osImageURL: "http://mysource.example.com/ubuntu_v1_24.gz"

---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellMachineConfig
metadata:
  name: eks-a-bm-poc-cp
spec:
  hardwareSelector:
    type: cp
  osFamily: ubuntu
  templateRef: {}
  users:
  - name: ec2-user
    sshAuthorizedKeys:
    - ssh-rsa AAAAB3Nza...

---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellMachineConfig
metadata:
  name: eks-a-bm-worker01
spec:
  hardwareSelector:
    type: worker01
  osFamily: ubuntu
  templateRef: {}
  users:
  - name: ec2-user
    sshAuthorizedKeys:
    - ssh-rsa AAAAB3NzaC1yc2EA......

---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: OIDCConfig
metadata:
  name: eks-anywhere-azuread
spec:
  clientId: "removed"
  groupsClaim: "groups"
  groupsPrefix: "aad:"
  issuerUrl: "removed"
  usernameClaim: "sub"
  usernamePrefix: "aad:"

---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: FluxConfig
metadata:
  name: kubernetes-infra-addons
spec:
  systemNamespace: "flux-system"
  clusterConfigPath: "clusters/eks-a-bm-poc-03"
  branch: "fluxv2"
  git:
    repositoryUrl<EMAIL_ADDRESS>    sshKeyAlgorithm: ed25519

Then we call:
eksctl anywhere create cluster --hardware-csv hw.csv -f eks-a-bm-poc.yaml -v10

Environment:

EKS Anywhere Release: v0.13.1
EKS Distro Release: 1.24

I have not been able to reproduce on the Docker provider. We're looking into reproducing on baremetal and I'll try VSphere today.

@Cajga thanks for creating a github issue. From your clusterconfig file it looks like you are enabling Flux gitOps too for your Baremetal cluster creation. However, we do not support GitOps for Baremetal for Baremetal cluster fully yet.
I would recommend you to remove fluxConfig as of now from your cluster config file and try again by enabling policyEnforcementMode: "always" in your cniConfig.
Let me know if you have any other question.

@panktishah26 wow, good to know, thanks for the heads-up... we have been using GitOps for our PoC baremetal cluster for about 2 months without any issues (except this one of course). I also brought this up in a conversation with our AWS contact but seems they also overlooked the lack of support... :/
I can confirm that if we remove the fluxConfig then the cluster gets installed without running into this issue. (actually, we run into another issue, which seems to be related to the fact that the eksa-packages namespace does not receive an allow-all network policy and as such, the controller container in the eks-anywhere-packages pod cannot reach the API and fails with a "unable to start manager: Get \"https://<IP_ADDRESS>:443/api?timeout=32s\": dial tcp <IP_ADDRESS>:443: i/o timeout" error message... But I will open another case for that).
Well, our whole cluster management and application deployment is done using GitOps/flux. I guess we can just bootstrap fluxcd manually after we had installed a cluster without fluxConfig enabled (and with policyEnforcementMode: "always"). Of course this solution is not very elegant and "too manual" knowing the GitOps integration of EKS Anywhere :)
Any public ETA when will you support GitOps for Baremetal?

That explains why I wasn't able to reproduce this issue on VSphere and Docker. Closing this, BM+GitOps support is already planned.


fix: Swap toArray() with attributesToArray()

Hello @danharrin, we have some problem with this fix. I try to explain.
Consider Resource file (for example UserResource) and suppose to implement getEloquentQuery() using eager loading
User::with('post')
Before the fix, when overriding method mutateFormDataBeforeFill(array $data), $data variable contains also eager loaded data (post relationship).
After the fix my variable $data doesn't have eager loaded data anymore, only user datas are present.
Is this the correct behaviour?
Thank you

Yes, that is the correct behaviour. Relationship data has always been accessible from $this->record, and I have always recommended that approach to others before this change was made. I wasnt even aware that the relationships were loaded before this was fixed 😂

Ok great, thank you for this clarification.


Adding Matt Nichols to list of community contributors

Signed-off-by: Tihomir Surdilovic<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please specify parts this PR updates:

[ ] Specification
[ ] Schema
[ ] Examples
[ ] Usecases
[ ] Extensions
[ ] Roadmap
[ ] Use Cases
[ x] Community
[ ] TCK
[ ] Other

What this PR does / why we need it:
Special notes for reviewers:
Additional information (if needed):

@transientvariable please let me know if this is ok to add you. Thanks for your contribution! (https://github.com/serverlessworkflow/specification/commit/45817cdfc8b01948598a5fa8019226d761119d95)

@transientvariable please let me know if this is ok to add you. Thanks for your contribution! (45817cd)

👍🏽


Create a screen to modify the Reminder

Is your feature request related to a problem? Please describe.
NA
Describe the solution you'd like

Create a screen using Jetpack Compose allowing users to modify reminders with new details or delete them.
Have the required code for ViewModel and Repository.

Describe alternatives you've considered
NA
Additional context
NA

Assigned to @geetgobindsingh team as Siddu left the team.


build_bridge x86 MSBUILD : error MSB1009: Project file does not exist.

name: Bug report
about: Create a report to help us improve
title: build_bridge x86 MSBUILD : error MSB1009: Project file does not exist.
labels: ''
assignees: ''

Describe the bug

vs solution are not builded for x86 MSBUILD : error MSB1009: Project file does not exist.
with dxvk-remix all is ok, environment is same

Environment

commit 1a05374b393cfa1a0c2afdb4226c6ac230b2a870 (HEAD -> main, origin/main, origin/HEAD)
win 11 pro 22H2 22621.1702
visual studio comunity 2022 17.6.2 (msvc 142 and 143 for x86, x64)

Attach logs!

build_log.log
meson-log.txt

To Reproduce
Steps to reproduce the behavior:

follow the instruction https://github.com/NVIDIAGameWorks/bridge-remix#how-to-build
run any build_bridge

Expected behavior
Solution will generated for x64 and x86

Reproduce on win 10
Modify build_common.ps1
Push-Location $CurrentDir
	$mesonArgs = "setup --buildtype `"$BuildFlavour`" --backend vs `"$BuildSubDir`" --debug"
	meson $mesonArgs
Pop-Location

build_common_cmd.log
bridge-remix_compDebug_x86\meson-logs[meson-log.txt](https://github.com/NVIDIAGameWorks/bridge-remix/files/11592330/meson-log.txt)

I have solved it with chatgpt helping

@SSertel u should highlight this in the readme


Commonjs modules / Browserify

This was mostly motivated by my need to avoid including the Runner code into my codebase (to avoid window being referenced in node). Using commonjs modules and browserify allows me to require individual files (and automatically include their dependencies) from my project.
https://github.com/hfaulds/matter-js works fine and uses browserify to build the final code. The diff is a bit of a nightmare at the moment because there's no need to wrap everything in closures in each file (browserify does that for you) which changes the indentation in every src file.
I also removed trailing whitespace during this process.
I'm willing to work towards making a reviewable PR if there is any chance it would get merged (I notice there has been a few PRs open for a long time).

Awesome, this has definitely been on my todo list (which is quite long) so I'll check this out soon!
I've recently been working on a rather large feature which is due to be merged soon, but if I decided to use this then I'd have to merge this first I think or it could get tricky.

Ok, here's some steps this could be split into to make the PR more reviewable.
Step 1 should be easy but be a big diff.
Step 2 is slightly more involved but will be a short diff.
Step 3 is easy but another large diff.
If possible it would probably be easier to do this once there are no PRs to merge. My fork serves my purposes for now so I'm in no rush.

[ ] Strip trailing whitespace (and make part of the jshint tests).

One could use a sed or something like https://www.npmjs.com/package/js-beautify. The latter might help people in my situation whose editors are set up for 2-space-tabs (and automatically convert tabs to spaces) as we can just run the beautify command after making changes, it may also help in step 3.

[ ] add requires, module.export and browserify grunt task
The existing closures can be left at this point. If any-one else does attempt this then be warned that Engine and Runner are both defined in terms of each other (Runner uses Engine repeatedly and Engine.run is an alias of Runner.run). I pushed this up into main.js but I think it could be avoided by defining Engine.run = function() { require('Runner').run() }.

I've been trying to work out how react's (https://github.com/facebook/react) build works. I believe they move all their src files to a temporary lib directory before running browserify which means the requires become require(Foo) even if Foo is in a different folder (this seems preferable to the long requires in my fork). It also exposes the src files as react/lib/* when requiring as a third party (https://github.com/Izzimach/react-pixi/blob/master/src/ReactPIXI.js#L26-L35 is a good example). I'll continue to try and piece together their build to imitate this behaviour.

[ ] remove unnecessary closures and re-indent (if we used js-beautify or an equivalent then this can be automated with minimal diff)

Hey! Thought I'd drop a few thoughts in here.

Why not add a babel transpilation step in here so we can use es6 module syntax? This step would also allow us to take advantage of any other new spec features. Obviously you want to be careful of performance here but babel is super efficient and simple features such as default parameter values would help clean up the codebase in many places. Babel would also make the npm publishing super simple. In answer to "how to react do it" and how do many other libraries do it - it's basically just this line - feel free to checkout the other scripts on that repo such as release which could help!
Use eslint for linting. It's much more extensible and basically the new goto linter with as much 3rd party supper as jshint or any others.
I agree you should wait until a release candidate of matter v1.0 is ready and then do this nasty convert all the module syntax business for that.
No strong feelings towards jsbeautifier step - I think it should maybe just be ran one time when v1.0 is packaged up and then have an .editorconfig which will basically remove any  other inconcistencies when people are contributing (doubt many people use an ide which doesn't support this now)
Use webpack for packaging would be my recommendation over browserify - for the basic stuff I think there's no telling the difference between the two (they have very similar basic api's) but webpack (i've used both quite extensively) has reduced headache so much more.

@hfaulds
I've now merged my latest changes in to master, so I'm looking at implementing this soon.
I think it's best as you are suggesting: I can merge this in two stages, build file, require calls and exports (these are mostly just additions so they won't conflict).
Then following that I will do a cleanup commit to remove the closures and extra indentation. This way the changes will be separated to make things clear.
As for the circular dependencies caused by aliases, it makes sense just to move them to main since there shouldn't be many.
@Chrisui

Why not add a babel transpilation step in here so we can use es6 module syntax?

Yeah I've toyed with the idea of babel and es6 too. But I think this may possibly cause problems for some users who need support for IE < 10 if we start using certain features. It might also be quite tricky to debug at times even with source maps.

Babel would also make the npm publishing super simple.

Hmm could you explain? Matter.js is already on npm, if we get browserify set up then it should work in node just fine?

In answer to "how to react do it" and how do many other libraries do it - it's basically just this line

Hmm so what's in the react build that we need here? I don't think I'm up to speed on this yet!

Use eslint for linting

Sure I'll look into this.

I agree you should wait until a release candidate of matter v1.0 is ready and then do this nasty convert all the module syntax business for that.

Actually I think I want to do this before then, since I'm considering splitting some of the functionality into plugins before 1.0 and proper dependencies are needed to do it. Going forward this way I can keep the core tight, but also build more extensions that people keep asking for without feeling so much feature creep guilt.

No strong feelings towards jsbeautifier step

I may use it to help during the merge, but probably not as part of the build script. I find that beautifiers often mess up some intentional formatting styles that I like to use, even if I configure them.

Use webpack for packaging would be my recommendation over browserify - for the basic stuff I think there's no telling the difference between the two (they have very similar basic api's) but webpack (i've used both quite extensively) has reduced headache so much more.

I need to look into webpack, but browserify's output looks just fine to me. Personally I just want as little overhead as possible and to maintain the exact same namespacing as before.
What sort of headaches could we run into here? How does webpack solve them?
Thanks for the input guys.

So far I've managed to implement browserify using @hfaulds fork!
It's not complete yet though, for some reason the Composite Manipulation fails because of a bad dependency Body.translate is not a function because Body is an empty object but other modules are using it just fine. So I'm not sure why this happens yet.
You can try this out in the browserify branch.

@liabru I ran into that when modules were loading in an infinite loop. If module A requires B requires A then you end up with undefined. Is it plausible something similar is happening here?

Possibly, but my guess is if that were the reason then there'd be far more cases of this issue than just this one. Either way, I was expecting that browserify would easily be able to handle circular module references since this all happens at runtime...

Just checked in on this branch, seems to be working fine now?

Nope try all the demos, there should still be one that exhibits the issue. I've not had chance to revisit this yet but I'm expecting to merge this when its fixed.

I've resolved the issue, I had to move all of the require statements to below the module.exports.
Before I merge, are there any objections to merging the browserify branch into master?

The browserify branch has merged into master.
I'm also using the standalone build option which outputs a UMD module so it should work everywhere and I've updated the main field in package.json so that it points to the latest edge build. This means installing via npm should also work correctly now.
Thanks @hfaulds and @Chrisui for your help.
Please update the thread if you run into any issues!


Fixed toolbar buttons z-index

The toolbar buttons were not clickable because they were appearing behind the layer of the code. Now they are clickable.

What browser is this with? There should be nothing on top of the toolbar (apart from the popup).
https://github.com/mrdoob/htmleditor/blob/master/index.html#L170-L173

It was on Firefox Developer Edition, the latest version
El sept. 24, 2015 6:42 PM, "Mr.doob"<EMAIL_ADDRESS>escribió:

What browser is this with? There should be nothing on top of the toolbar
(apart from the popup).
https://github.com/mrdoob/htmleditor/blob/master/index.html#L170-L173
—
Reply to this email directly or view it on GitHub
https://github.com/mrdoob/htmleditor/pull/13#issuecomment-143080937.

Hmm... Indeed, it's an issue in Firefox.
Seems like CodeMirror is adding z-index: 2 to .CodeMirror pre and Firefox gives priority to z-index rather than dom elements order.
I wonder if this follows the spec or if it's a bug in Firefox...?

El 27/09/2015, a las 9:50 a.m., Mr.doob<EMAIL_ADDRESS>escribió:
Hmm... Indeed, it's an issue in Firefox.
Seems like CodeMirror is adding z-index: 2 to .CodeMirror pre and Firefox gives priority to z-index rather than dom elements order.
I wonder if this follows the spec or if it's a bug in Firefox...?
—
Reply to this email directly or view it on GitHub https://github.com/mrdoob/htmleditor/pull/13#issuecomment-143563864.

Well, maybe it is a bug in Firefox, but, it is better to have support for all browsers right?

Well, maybe it is a bug in Firefox, but, it is better to have support for all browsers right?

I want to know if it's a bug in Firefox before adding workarounds.

El 27/09/2015, a las 10:01 a.m., Mr.doob<EMAIL_ADDRESS>escribió:
Well, maybe it is a bug in Firefox, but, it is better to have support for all browsers right?
I want to know if it's a bug in Firefox before adding workarounds.
—
Reply to this email directly or view it on GitHub https://github.com/mrdoob/htmleditor/pull/13#issuecomment-143564994.

Hmm, How may I help you?

This should be fixed now.


[Bug Fix] Support threads_per_head < 64 for wavefront size of 64

When launching apply_rotary_pos_half kernel, only threads_per_head of 64 is supported for wavefront size of 64.
This change adds support for threads_per_head < 64 such as 4, 8, 16.
Fixes the issue introduced in https://github.com/microsoft/DeepSpeed/pull/5402

ping @jithunnair-amd @jeffdaily @loadams

@loadams any comments on this PR?

LGTM, but let's add a unit test to ensure this functionality can be tested on ROCm (and CUDA)

@jagadish-amd - thoughts on adding unit tests for this?

LGTM, but let's add a unit test to ensure this functionality can be tested on ROCm (and CUDA)

@jagadish-amd - thoughts on adding unit tests for this?

I will add the unit tests. Thanks

LGTM, but let's add a unit test to ensure this functionality can be tested on ROCm (and CUDA)

@jagadish-amd - thoughts on adding unit tests for this?

I will add the unit tests. Thanks

@loadams I have added the test case to test the threads_per_head ,warp size alignment issue.
Unfortunately, I lost access to the AI model / node for which the "Assertion `false' failed" error had triggered on warp_size 64 node. Hence the values in the test cases are assumed here, but it still tests the intended fix. I will add the exact values in the future.
I noticed that the files in unit/ops/transformer/inference were refactored. I have used the InferenceBuilder().load() way to test the function apply_rotary_pos_emb. If this is not right, plz let me know, we can merge the PR without the newly added test. (and later folks can add the test cases, this change affects only warp_size 64 case / AMD Instinct device).
These are the results.
On warp_size = 32, test cases pass regardless of the changes in apply_rotary_pos_emb.cu
==================================== 4 passed, 2 warnings in 25.24s ====================================
On warp_size =64, with the fix.
==================================== 4 passed, 2 warnings in 5.58s =====================================
On warp_size =64, without the fix.
python: /opt/conda/envs/py_3.10/lib/python3.10/site-packages/deepspeed/ops/csrc/transformer/inference/csrc/apply_rotary_pos_emb.hip:169: void launch_apply_rotary_pos_emb(T *, T *, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, float, hipStream_t, int) [T = float]: Assertion `false' failed.
Fatal Python error: Aborted
The test run is aborted (as expected) due to the error in kernel. Not sure if there is better way to handle this?

LGTM, but let's add a unit test to ensure this functionality can be tested on ROCm (and CUDA)

@jagadish-amd - thoughts on adding unit tests for this?

I will add the unit tests. Thanks

@loadams I have added the test case to test the threads_per_head ,warp size alignment issue. Unfortunately, I lost access to the AI model / node for which the "Assertion `false' failed" error had triggered on warp_size 64 node. Hence the values in the test cases are assumed here, but it still tests the intended fix. I will add the exact values in the future. I noticed that the files in unit/ops/transformer/inference were refactored. I have used the InferenceBuilder().load() way to test the function apply_rotary_pos_emb. If this is not right, plz let me know, we can merge the PR without the newly added test. (and later folks can add the test cases, this change affects only warp_size 64 case / AMD Instinct device).
These are the results. On warp_size = 32, test cases pass regardless of the changes in apply_rotary_pos_emb.cu ==================================== 4 passed, 2 warnings in 25.24s ==================================== On warp_size =64, with the fix. ==================================== 4 passed, 2 warnings in 5.58s ===================================== On warp_size =64, without the fix. python: /opt/conda/envs/py_3.10/lib/python3.10/site-packages/deepspeed/ops/csrc/transformer/inference/csrc/apply_rotary_pos_emb.hip:169: void launch_apply_rotary_pos_emb(T *, T *, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, float, hipStream_t, int) [T = float]: Assertion `false' failed. Fatal Python error: Aborted
The test run is aborted (as expected) due to the error in kernel. Not sure if there is better way to handle this?

@jagadish-amd - this should be fine for now.  I believe the only remaining thing for this PR is the CLA agreement, you should just need to reply to it with accept and company as AMD.

@jagadish-amd please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="AMD"


fix: documentation of snippet cannot be shown when description is list

When formating documentation of snippets, we treat the description field of a snippet item as string by default but it could a list of string sometimes(see snippets for shell in friendly-snippets ) which might cause a concatenation failure.
So here is a tiny fix by joining the description list if it is a list when loading snippets, so now it could be shown and looks like this:

Closes https://github.com/Saghen/blink.cmp/issues/91

Thanks!


Update CSV email to say when link expires

What
Told users that link expires after 7 days
Why
So they know it will stop working and they should use it before then

Review Checklist

[x] Changes in scope.
[ ] Added/updated unit tests.
[ ] Added/updated feature tests.
[ ] Added/updated relevant documentation.
[ ] Added to Trello card.

 (2) CSV downloading page and email content tweaks


Large Random Intercepts + Slopes Model Fitting Results in MethodError for SparseMatrixCSC Multiplication

I have been having trouble fitting a very simple model with random intercepts and slopes when the number of grouping factors is large.  From what I can tell, this is because there are missing definitions for some of the linear algebra functions for sparse matrices.  A simple example is:
using MixedModels
using DataFrames

function breakme(n::Int, ng::Int)
    df = DataFrame(Y = randn(n), X = rand(n), G = rand(1:ng, n), H = rand(1:ng, n))
    f = @formula(Y ~ (1 + X|H) + (1|G)) # simple model with random slopes and intercepts
    m = LinearMixedModel(f, df)
    updateL!(m) # fit!(m) fails as well
end

# this works fine:
breakme(10000, 50)
# this does not:
breakme(10000, 600)

The resulting error is:
ERROR: MethodError: no method matching A_mul_Λ!(::SparseMatrixCSC{Float64,Int32}, ::MixedModels.VectorFactorReTerm{Float64,Int64,UInt16,2})
Closest candidates are:
  A_mul_Λ!(::Any, ::MixedModels.MatrixTerm) at MixedModels\src\linalg\lambdaprods.jl:15
  A_mul_Λ!(::Any, ::MixedModels.ScalarFactorReTerm) at MixedModels\src\linalg\lambdaprods.jl:16
  A_mul_Λ!(::MixedModels.BlockedSparse{T,Ti} where Ti, ::MixedModels.VectorFactorReTerm{T,V,R,S} where S where R where V) where T at MixedModels\src\linalg\lambdaprods.jl:18
  ...

When I attempted to define my own A_mul_Λ! with a first argument of type SparseMatrixCSC{T,Ti}, simply copying and pasting the definition at linalg\lambdaprods.jl:18, this fails with an even deeper missing multiplication function:
function MixedModels.A_mul_Λ!(A::SparseMatrixCSC{T,Int32}, B::VectorFactorReTerm{T,V,R,S}) where {T,V,R,S}
    λ = B.Λ
    m, n = size(A)
    q, r = divrem(n, S)
    iszero(r) || throw(DimensionMismatch("size(A, 2) = $n is not a multiple of S = $S"))
    A3 = reshape(A, (m, S, q))
    for k in 1:q
        A_mul_B!(view(A3, :, :, k), λ)
    end
    A
end

The error when using this version of A_mul_Λ! is:
ERROR: MethodError: no method matching A_mul_B!(::SubArray{Float64,2,Base.ReshapedArray{Float64,3,SparseMatrixCSC{Float64,Int32},Tuple{Base.MultiplictiveInverses.SignedMultiplicativeInverse{Int64}}},Tuple{Base.Slice{Base.OneTo{Int64}},Base.Slice{Base.OneTo{Int64}},Int64},false}, ::LowerTriangular{Float64,Array{Float64,2}})
Closest candidates are:
  A_mul_B!(::AbstractArray{T,2} where T, ::Base.LinAlg.AbstractTriangular, ::Tridiagonal) at linalg\triangular.jl:444
  A_mul_B!(::AbstractArray{T,2} where T, ::Base.LinAlg.AbstractTriangular, ::Union{Bidiagonal, SymTridiagonal, Tridiagonal}) at linalg\bidiag.jl:356
  A_mul_B!(::AbstractArray{T,2} where T, ::Base.LinAlg.AbstractTriangular, ::Union{AbstractArray{T,1}, AbstractArray{T,2}} where T) at linalg\triangular.jl:447
  ...

So the missing functions appears to go deeper than MixedModels.  Any suggestions on how to deal with this?

@reallyasi9 did you ever figure out a solution to this? having a similar issue

No solution yet.  Lack of support for sparse matrices has forced us, for the time being, to abandon the attempted fit with the entire dataset.

Sadly I haven't addressed the issue earlier and it is now quite old. Things have changed with the release of
julia> using BlockArrays, DataFrames, InteractiveUtils, LinearAlgebra, MixedModels, Random

julia> versioninfo()
Julia Version 1.0.0
Commit 5d4eaca0c9 (2018-08-08 20:58 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.0 (ORCJIT, ivybridge)

and the most recent MixedModels release (v1.1.0 is the latest as I write this).
A function to generate an example showing the problem is given in the issue but it uses simulated data without setting the random number seed.
I modified this function to take an AbstractRNG as the first argument, as is common now in simulation functions.
julia> function simulatemodel(rng::AbstractRNG, n::Int, ng::Int)
    df = DataFrame(Y = randn(rng, n), X = rand(rng, n), G = rand(rng, 1:ng, n), H = rand(rng, 1:ng, n))
    f = @formula(Y ~ 1 + X + (1 + X|H) + (1|G)) # simple model with random slopes and intercepts
    m = LinearMixedModel(f, df)
end
simulatemodel (generic function with 1 method)

Internal representation of a LinearMixedModel
A couple of things about the internal representation of the model in the LinearMixedModel type.
The trms field is a vector of matrix-like objects constructed from the terms in the model formula.
The random-effects terms are first, ordered by the number of random effects.
These are followed by the model matrix for the fixed-effects and the response, represented as a matrix with only 1 column.
julia> m1 = simulatemodel(MersenneTwister(1234321), 10_000, 100);

julia> show(typeof.(m1.trms))
DataType[VectorFactorReTerm{Float64,UInt8,2}, ScalarFactorReTerm{Float64,UInt8}, MatrixTerm{Float64,Array{Float64,2}}, MatrixTerm{Float64,Array{Float64,2}}]
julia> show(size.(m1.trms))
Tuple{Int64,Int64}[(10000, 200), (10000, 100), (10000, 2), (10000, 1)]

The A and Λ fields
The A field in the LinearMixedModel type is a blocked matrix corresponding to M'M, where M is the horizonal concatenation of these terms.
The size of M would be (10000,303) so A is of size (303,303) but divided into blocks corresponding to the terms.
julia> nblocks(m1.A)
(4, 4)

julia> blocksizes(m1.A)
[200, 100, 2, 1] × [200, 100, 2, 1]

A is symmetric and sparse.  Only the lower triangle is stored explicitly.
julia> Symmetric(m1.A, :L)
303×303 Symmetric{Float64,BlockArray{Float64,2,AbstractArray{Float64,2}}}:
 91.0      45.621       0.0     …     91.0       45.621      -6.78475
 45.621    28.8729      0.0           45.621     28.8729     -5.31706
  0.0       0.0        97.0           97.0       50.3144    -22.2702
  0.0       0.0        50.3144        50.3144    33.9297     -8.69875
  0.0       0.0         0.0          119.0       58.4556     15.3649
  0.0       0.0         0.0     …     58.4556    38.9647      6.06072
  0.0       0.0         0.0           91.0       43.3323     -4.42541
  0.0       0.0         0.0           43.3323    28.2741     -1.9568
  0.0       0.0         0.0           94.0       51.178       2.9719
  0.0       0.0         0.0           51.178     35.8487      1.5817
  ⋮                             ⋱      ⋮
  2.0       0.901234    0.0          116.0       57.5162     14.2066
  0.0       0.0         0.0     …     92.0       45.1858     10.4995
  1.0       0.632598    1.0          102.0       52.1247    -16.441
  1.0       0.541671    0.0           91.0       49.4059      2.46062
  1.0       0.985525    0.0           75.0       36.7601     -4.03442
  0.0       0.0         1.0
 ─────────────────────────────       108.0       53.339      17.3341
 ──────────────────────────────────
 91.0      45.621      97.0     …  10000.0     4935.93      -41.4178
 45.621    28.8729     50.3144
 ─────────────────────────────      4935.93    3268.94       14.4503
 ──────────────────────────────────
 -6.78475  -5.31706   -22.2702       -41.4178    14.4503  10086.1

There is another matrix, Λ, stored implicitly in the random-effects terms and depending on the parameter vector θ.
It is block-diagonal with the same block sizes as A.
All the off-diagonal blocks are zero.
The rightmost two diagonal blocks, corresponding to the fixed-effects and the response, are always the identity.
The diagonal blocks for the random-effects terms are either a multiple of the identity, for a scalar random-effects term like (1|G), or repetitions of small, lower-triangular matrix, λ, for vector-valued random-effects terms like (1+X | H).
The size of λ for a vector-valued random effects term is the dimension of the random effects for each level of the grouping factor.
In this case (1+X | H) generates a two-dimensional random effect for each of the 100 levels of H.
julia> show(m1.θ)
[1.0, 0.0, 1.0, 1.0]
julia> m1.λ[1]
2×2 LowerTriangular{Float64,Array{Float64,2}}:
 1.0   ⋅
 0.0  1.0

julia> m1.λ[2]
1.0

Optimization of the log-likelihood is with respect to the θ parameters, as can be seen in the verbose output.
julia> fit!(m1, true)
f_1: 29297.56487 [1.0, 0.0, 1.0, 1.0]
f_2: 29404.28073 [1.75, 0.0, 1.0, 1.0]
f_3: 29321.95421 [1.0, 1.0, 1.0, 1.0]
f_4: 29394.85725 [1.0, 0.0, 1.75, 1.0]
f_5: 29407.65216 [1.0, 0.0, 1.0, 1.75]
f_6: 29098.0851 [0.25, 0.0, 1.0, 1.0]
f_7: 29283.94126 [1.0, -1.0, 1.0, 1.0]
f_8: 29171.02982 [1.0, 0.0, 0.25, 1.0]
f_9: 29050.57235 [1.0, 0.0, 1.0, 0.25]
f_10: 28722.17068 [0.380883, -0.0616603, 0.66154, 0.0]
f_11: 28817.84599 [0.0, -1.78331, 0.0, 0.0]
f_12: 28607.42985 [0.0, 0.538509, 0.19806, 0.0]
f_13: 28709.87765 [0.0, 1.01832, 0.0, 0.0]
f_14: 28465.42793 [0.0, 0.0537491, 0.106181, 0.0]
f_15: 28505.33794 [0.0, -0.267398, 0.0, 0.0]
f_16: 28571.22305 [0.15251, 0.0455518, 0.128115, 0.15251]
f_17: 28544.21428 [0.0, 0.0790617, 0.363651, 0.051349]
f_18: 28519.39796 [0.0724224, 0.122279, 0.170913, 0.0724224]
f_19: 28470.53906 [0.0, 0.149737, 0.0, 0.0]
f_20: 28482.37885 [0.0420735, 0.0410006, 0.167528, 0.0]
f_21: 28466.63088 [0.0, 0.0976609, 0.0822434, 0.0]
f_22: 28463.46937 [0.0, 0.00445662, 0.0998947, 0.0]
f_23: 28467.86658 [0.0, -0.0529322, 0.124643, 0.0]
f_24: 28463.35591 [0.026153, -0.000514467, 0.0924469, 0.0]
f_25: 28462.0944 [0.00276354, 0.000927617, 0.0631551, 0.0]
f_26: 28462.2705 [0.0, -0.0154481, 0.074781, 0.0]
f_27: 28462.09616 [0.0141236, 0.0043129, 0.0680831, 0.0115698]
f_28: 28462.01276 [0.0193709, -0.00215849, 0.0596224, 0.0]
f_29: 28462.08556 [0.013576, 0.00333237, 0.0655305, 0.0]
f_30: 28462.02695 [0.0204882, -0.0109196, 0.0630613, 0.0]
f_31: 28462.01796 [0.0162498, -0.00447113, 0.0574031, 0.00621087]
f_32: 28462.00769 [0.0182536, 0.00660258, 0.0561835, 0.0]
f_33: 28461.98869 [0.0247955, 0.00525252, 0.0526579, 0.0]
f_34: 28462.01959 [0.0313683, 0.000446716, 0.0524214, 0.0]
f_35: 28461.95809 [0.0271396, -0.00348377, 0.0498609, 0.0]
f_36: 28461.95644 [0.0289345, 0.00217096, 0.0439413, 0.0]
f_37: 28461.9646 [0.0232163, 0.00852971, 0.0448402, 0.0]
f_38: 28461.9525 [0.0297636, -0.00250281, 0.0449843, 0.0]
f_39: 28461.95352 [0.033378, -0.0078737, 0.0444686, 0.0]
f_40: 28461.96998 [0.0281169, -0.0041808, 0.041859, 0.0]
f_41: 28461.95201 [0.0305204, -0.00414571, 0.0449815, 0.0]
f_42: 28461.95185 [0.0304347, -0.00428173, 0.045028, 0.000736605]
f_43: 28461.95244 [0.029942, -0.00484637, 0.0453968, 0.000670081]
f_44: 28461.95282 [0.0302709, -0.00508646, 0.0446542, 0.00055868]
f_45: 28461.95195 [0.0299707, -0.00357253, 0.0450071, 0.00098923]
f_46: 28461.95209 [0.0299851, -0.0034838, 0.0450163, 0.000690728]
f_47: 28461.95187 [0.0309345, -0.00473109, 0.0452489, 0.000348914]
f_48: 28461.95216 [0.0305192, -0.00385372, 0.0456972, 0.00066993]
f_49: 28461.95182 [0.0305089, -0.00417241, 0.0451253, 0.000741614]
f_50: 28461.95193 [0.0306668, -0.00420189, 0.0450726, 0.000499274]
f_51: 28461.95187 [0.0304233, -0.00417271, 0.0450083, 0.000715054]
f_52: 28461.95175 [0.0304693, -0.00422961, 0.0451836, 0.000863732]
f_53: 28461.95159 [0.0303703, -0.00427784, 0.0452607, 0.00112809]
f_54: 28461.95122 [0.0301618, -0.00424205, 0.0453486, 0.00167188]
f_55: 28461.94991 [0.0298823, -0.00409695, 0.0454508, 0.00280777]
f_56: 28461.94628 [0.0290626, -0.00336981, 0.045344, 0.00494828]
f_57: 28461.9321 [0.028488, -0.00423519, 0.0466264, 0.00940406]
f_58: 28461.91959 [0.0262657, -0.00379686, 0.0474332, 0.0185311]
f_59: 28461.94718 [0.0229668, 0.00186479, 0.0548887, 0.0206531]
f_60: 28461.92191 [0.026927, -0.00493181, 0.0459387, 0.0181057]
f_61: 28461.91639 [0.0281262, -0.00830126, 0.0499371, 0.0195828]
f_62: 28461.93203 [0.0265175, -0.00986049, 0.0497844, 0.0194291]
f_63: 28461.91027 [0.0297688, -0.010125, 0.0507765, 0.0190452]
f_64: 28461.90729 [0.031154, -0.0117474, 0.0517831, 0.017973]
f_65: 28461.90831 [0.0319205, -0.0140903, 0.0517205, 0.0193454]
f_66: 28461.90887 [0.0312285, -0.0121713, 0.0521754, 0.019036]
f_67: 28461.90629 [0.0317874, -0.0123743, 0.0514651, 0.0171561]
f_68: 28461.9068 [0.0318525, -0.0136669, 0.0517226, 0.0165394]
f_69: 28461.9067 [0.0313049, -0.0126278, 0.0511845, 0.0171583]
f_70: 28461.9058 [0.0318339, -0.0124157, 0.0508806, 0.0171027]
f_71: 28461.90567 [0.0322725, -0.013588, 0.0502819, 0.0168444]
f_72: 28461.90562 [0.0318521, -0.0122336, 0.0501791, 0.0169523]
f_73: 28461.90561 [0.0319299, -0.0125033, 0.050252, 0.0169446]
f_74: 28461.90562 [0.0319058, -0.0124202, 0.0502307, 0.0169463]
f_75: 28461.90567 [0.0319228, -0.0124949, 0.050272, 0.0168729]
f_76: 28461.90556 [0.0319359, -0.0125147, 0.0502405, 0.017018]
f_77: 28461.90549 [0.0319425, -0.0125358, 0.0502117, 0.0171641]
f_78: 28461.90544 [0.0319321, -0.012525, 0.0500779, 0.0174324]
f_79: 28461.90539 [0.0319285, -0.0124348, 0.0502989, 0.0175599]
f_80: 28461.90537 [0.0321018, -0.0130143, 0.0505331, 0.0174886]
f_81: 28461.9053 [0.032494, -0.0141913, 0.0509413, 0.0173642]
f_82: 28461.90542 [0.0332753, -0.0165952, 0.0516524, 0.017057]
f_83: 28461.90508 [0.0327646, -0.0139522, 0.0508174, 0.0170901]
f_84: 28461.90528 [0.0332827, -0.0149222, 0.051298, 0.0167959]
f_85: 28461.90515 [0.032849, -0.0139384, 0.0507271, 0.0168646]
f_86: 28461.905 [0.0327021, -0.0133509, 0.0506607, 0.0173069]
f_87: 28461.90506 [0.0324106, -0.0121376, 0.0502283, 0.0174302]
f_88: 28461.90491 [0.0328032, -0.0134588, 0.0505718, 0.0173235]
f_89: 28461.90468 [0.0330338, -0.0138574, 0.0503159, 0.0175897]
f_90: 28461.90463 [0.0335375, -0.01504, 0.0502862, 0.0178615]
f_91: 28461.9046 [0.0333953, -0.0144736, 0.0501916, 0.0178319]
f_92: 28461.90462 [0.0333479, -0.0142853, 0.0500981, 0.0178916]
f_93: 28461.90459 [0.0335724, -0.0144162, 0.0501701, 0.0178603]
f_94: 28461.90459 [0.0335597, -0.0145921, 0.0502904, 0.0178107]
f_95: 28461.90454 [0.0336153, -0.014691, 0.0501672, 0.017707]
f_96: 28461.90451 [0.0338367, -0.0149899, 0.0500174, 0.0175792]
f_97: 28461.90451 [0.0338955, -0.0151939, 0.0500909, 0.0175499]
f_98: 28461.90452 [0.0336971, -0.0148648, 0.050041, 0.0175137]
f_99: 28461.90451 [0.0339001, -0.0149596, 0.0500209, 0.0175464]
f_100: 28461.90451 [0.0338626, -0.0149931, 0.0499574, 0.0176159]
f_101: 28461.90451 [0.0338439, -0.0149962, 0.0500288, 0.0175677]
f_102: 28461.90451 [0.0338362, -0.0149766, 0.05003, 0.0175764]
f_103: 28461.90451 [0.0338273, -0.014961, 0.0500376, 0.017582]
Linear mixed model fit by maximum likelihood
 Formula: Y ~ 1 + X + ((1 + X) | H) + (1 | G)
     logLik        -2 logLik          AIC             BIC
 -1.42309523×10⁴  2.84619045×10⁴  2.84759045×10⁴  2.85263769×10⁴

Variance components:
              Column     Variance     Std.Dev.    Corr.
 H        (Intercept)  0.0011518184 0.033938451
          X            0.0027455508 0.052398004 -0.29
 G        (Intercept)  0.0003111605 0.017639741
 Residual              1.0065826656 1.003285934
 Number of obs: 10000; levels of grouping factors: 100, 100

  Fixed-effects parameters:
               Estimate Std.Error  z value P(>|z|)
(Intercept)  -0.0247419 0.0202585 -1.22131  0.2220
X             0.0419747 0.0351973  1.19255  0.2330

julia> show(m1.θ)
[0.0338273, -0.014961, 0.0500376, 0.017582]
julia> m1.λ[1]
2×2 LowerTriangular{Float64,Array{Float64,2}}:
  0.0338273   ⋅
 -0.014961   0.0500376

julia> m1.λ[2]
0.01758196823172704

The L field
The L field in a LinearMixedModel is the lower-triangular Cholesky factor of
\begin{equation}
\begin{bmatrix}
\Lambda^\prime\mathbf{Z}^\prime\mathbf{Z}\Lambda + \mathbf{I} & \Lambda^\prime\mathbf{Z}^\prime\mathbf{X} & \Lambda^\prime\mathbf{Z}^\prime\mathbf{y} \
\mathbf{X}^\prime\mathbf{Z}\Lambda  & \mathbf{X}^\prime\mathbf{X} & \mathbf{X}^\prime\mathbf{y} \
\mathbf{y}^\prime\mathbf{Z}\Lambda  & \mathbf{y}^\prime\mathbf{X} & \mathbf{y}^\prime\mathbf{y}
\end{bmatrix}
\end{equation}
in the same block pattern as A.
julia> m1.L
303×303 LowerTriangular{Float64,BlockArray{Float64,2,AbstractArray{Float64,2}}}:
  1.03171        ⋅             ⋅           …    ⋅          ⋅          ⋅
  0.0538965     1.03411        ⋅                ⋅          ⋅          ⋅
  0.0           0.0           1.03328           ⋅          ⋅          ⋅
  0.0           0.0           0.0578391         ⋅          ⋅          ⋅
  0.0           0.0           0.0               ⋅          ⋅          ⋅
  0.0           0.0           0.0          …    ⋅          ⋅          ⋅
  0.0           0.0           0.0               ⋅          ⋅          ⋅
  0.0           0.0           0.0               ⋅          ⋅          ⋅
  0.0           0.0           0.0               ⋅          ⋅          ⋅
  0.0           0.0           0.0               ⋅          ⋅          ⋅
  ⋮                                        ⋱   ⋮
  0.000923168   0.000718602   0.0               ⋅          ⋅          ⋅
  0.0           0.0           0.0          …    ⋅          ⋅          ⋅
  0.000415186   0.000516538   0.000401743       ⋅          ⋅          ⋅
  0.000438369   0.000437974   0.0               ⋅          ⋅          ⋅
  0.000325204   0.000821476   0.0               ⋅          ⋅          ⋅
  0.0           0.0           0.00045361
 ────────────────────────────────────────       ⋅          ⋅          ⋅
 ────────────────────────────
  2.32212       2.08644       2.44706      …  92.7263      ⋅          ⋅
  1.07712       1.34094       1.15591
 ────────────────────────────────────────     45.1208    28.5046      ⋅
 ────────────────────────────
 -0.145353     -0.249701     -0.603127        -0.400292   1.19647  100.329

An inelegant but fast summary of the block sizes and types of the A and L fields is available as
julia> describeblocks(m1)
1,1: UniformBlockDiagonal{Float64} (200, 200) UniformBlockDiagonal{Float64}
2,1: Array{Float64,2} (100, 200) Array{Float64,2}
2,2: Diagonal{Float64,Array{Float64,1}} (100, 100) Array{Float64,2}
3,1: Array{Float64,2} (2, 200) Array{Float64,2}
3,2: Array{Float64,2} (2, 100) Array{Float64,2}
3,3: Array{Float64,2} (2, 2) Array{Float64,2}
4,1: Array{Float64,2} (1, 200) Array{Float64,2}
4,2: Array{Float64,2} (1, 100) Array{Float64,2}
4,3: Array{Float64,2} (1, 2) Array{Float64,2}
4,4: Array{Float64,2} (1, 1) Array{Float64,2}

For each of the blocks in the lower triangle, the type and size of the block in A is listed followed by the type of the L block.
The (1,1) block is always the biggest block and hence the most important in preserving sparsity.
It will be Diagonal if the term with the most random effects is a scalar random-effects term.
For a vector-valued random-effects term, as in this example, it is UniformBlockDiagonal which means that it is block diagonal with $k$ diagonal blocks of size $\ell\times\ell$ where $k$ is the number of levels of the grouping factor and $\ell$ is the dimension of the random effects associated with each level.
In this example $k=100$ and $\ell=2$.
Although the (1,1) block of L always has the same structure as that of A, the (2,2) block can be subject to "fill-in".
Here the (2,2) block of A is Diagonal but the (2,2) block of L has non-zero off-diagonal elements and is stored as a full, dense matrix.
Furthermore, the (2,1) block is created as a sparse matrix but may not have a high proportion of zeros, in which case it is converted to a dense matrix as has been done here.
The "break-even" point where the complexity of sparse matrix operations is offset by storing and computing with only the non-zeros, as opposed to all the elements of a dense matrix even when most of them as zero, is surprisingly high, especially when using multi-threaded accelerated BLAS (Basic Linear Algebra Subroutines) such as MKL.
Updating L.
Once the model representation has been created, evaluation of the profiled log-likelihood requires only installation of a new value of θ and updating of L.
The updateL! function is now defined (in src/pls.jl) as

function updateL!(m::LinearMixedModel{T}) where T
    trms = m.trms
    A = m.A
    Ldat = m.L.data
    nblk = nblocks(A, 2)
    for j in 1:nblk
        Ljj = scaleInflate!(Ldat[Block(j, j)], A[Block(j, j)], trms[j])
        LjjH = isa(Ljj, Diagonal) ? Ljj : Hermitian(Ljj, :L)
        for jj in 1:(j - 1)
            rankUpdate!(-one(T), Ldat[Block(j, jj)], LjjH)
        end
        cholUnblocked!(Ljj, Val{:L})
        for i in (j + 1):nblk
            Lij = Λc_mul_B!(trms[i], A_mul_Λ!(copyto!(Ldat[Block(i, j)], A[Block(i, j)]), trms[j]))
            for jj in 1:(j - 1)
                αβA_mul_Bc!(-one(T), Ldat[Block(i, jj)], Ldat[Block(j, jj)], one(T), Lij)
            end
            rdiv!(Lij, isa(Ljj, Diagonal) ? Ljj : LowerTriangular(Ljj)')
        end
    end
    m
end

It relies on having appropriate methods for scaleInflate!, rankUpdate!, cholUnblocked!, Λc_mul_B!, A_mul_Λ!, αβA_mul_Bc! and rdiv!.
All of the methods act in-place, as indicated by the ! at the end of the name.
Making sure that all of the available methods are available is a bit tricky.
I keep accumulating examples but I don't have an exhaustive collection by any means so there may be situations that I have missed.
I appreciate it when users bring attention to a (reproducible, if possible) example that fails because then I know what I need to add.

Updating the original example a bit (including a reproducible RNG), we see that the new Terms specification doesn't tolerate non-categorical blocking variables.
using MixedModels, DataFrames, Random

gendata(n::Int, ng::Int) = gendata(MersenneTwister(42), n, ng)

function gendata(rng::AbstractRNG, n::Int, ng::Int)
    df = DataFrame(Y = randn(rng, n),
                   X = rand(rng, n),
                   G = rand(rng, 1:ng, n),
                   H = rand(rng, 1:ng, n))
    df
end

f = @formula(Y ~ (1 + X|H) + (1|G)) # simple model with random slopes and intercepts

df = gendata(10000, 50)
# fails
m = LinearMixedModel(f, df)

# make sure blocking variables are categorical
df = categorical!(df, [:G, :H])
# succeeds
m50 = LinearMixedModel(f, df)

df = gendata(10000, 500)
df = categorical!(df, [:G, :H])
# succeeds
m500 = LinearMixedModel(f, df)

I like the idea of forcing users to mark their blocking variables as categorical (because it highlights one surprisingly common misunderstanding about random effects v. nuisance parameters), but it might be nice to catch that error (ERROR: type ContinuousTerm has no field contrasts) and replace it with a clearer one.
There's also another type ambiguity / missing method that the example brings out:
julia> fit!(m50)
Linear mixed model fit by maximum likelihood
 Y ~ 1 + (1 + X | H) + (1 | G)
     logLik        -2 logLik          AIC             BIC
 -1.42875199×10⁴  2.85750398×10⁴  2.85870398×10⁴  2.86303019×10⁴

Variance components:
              Column           Variance              Std.Dev.       Corr.
 H        (Intercept)  0.0000000000000000000000 0.000000000000000
          X            0.0000000000000021658204 0.000000046538375   NaN
 G        (Intercept)  0.0000000000000000000000 0.000000000000000
 Residual              1.0198207911025178873388 1.009861768314118
 Number of obs: 10000; levels of grouping factors: 50, 50

  Fixed-effects parameters:
───────────────────────────────────────────────────────
                Estimate  Std.Error    z value  P(>|z|)
───────────────────────────────────────────────────────
(Intercept)  -0.00198834  0.0100986  -0.196892   0.8439
───────────────────────────────────────────────────────

julia> fit!(m500)
ERROR: MethodError: lmulΛ!(::LinearAlgebra.Adjoint{Float64,ReMat{Float64,1}}, ::BlockedSparse{Float64,1,2}) is ambiguous. Candidates:
  lmulΛ!(adjA::LinearAlgebra.Adjoint{T,#s32} where #s32<:ReMat{T,S}, B::BlockedSparse{T,S,P} where P where S) where {T, S} in MixedModels at /home/XXX/MixedModels.jl/src/remat.jl:125
  lmulΛ!(adjA::LinearAlgebra.Adjoint{T,ReMat{T,1}}, B::M) where {T, M<:AbstractArray{T,2}} in MixedModels at /home/XXX/MixedModels.jl/src/remat.jl:116
Possible fix, define
  lmulΛ!(::LinearAlgebra.Adjoint{T,ReMat{T,1}}, ::M<:(BlockedSparse{T,S,P} where P where S))
Stacktrace:
 [1] updateL!(::LinearMixedModel{Float64}) at /home/XXX/MixedModels.jl/src/linearmixedmodel.jl:625
 [2] #fit!#14(::Bool, ::Bool, ::typeof(fit!), ::LinearMixedModel{Float64}) at /home/XXX/MixedModels.jl/src/linearmixedmodel.jl:231
 [3] fit!(::LinearMixedModel{Float64}) at /home/XXX/MixedModels.jl/src/linearmixedmodel.jl:202
 [4] top-level scope at none:0

I suspect that the blocking structure is somewhat degenerate in that example though because when I increase the number of observations, everything works:
julia> df = gendata(100000, 500);
julia> df = categorical!(df, [:G, :H]);
julia> m500v2 = LinearMixedModel(f, df);
julia> fit!(m500v2)
Linear mixed model fit by maximum likelihood
 Y ~ 1 + (1 + X | H) + (1 | G)
     logLik       -2 logLik         AIC            BIC
 -1.4233557×10⁵  2.8467114×10⁵  2.8468314×10⁵ 2.84740217×10⁵

Variance components:
              Column      Variance     Std.Dev.    Corr.
 H        (Intercept)  0.00089677656 0.029946228
          X            0.00206739849 0.045468654 -1.00
 G        (Intercept)  0.00000000000 0.000000000
 Residual              1.00865535254 1.004318352
 Number of obs: 100000; levels of grouping factors: 500, 500

  Fixed-effects parameters:
──────────────────────────────────────────────────────
               Estimate   Std.Error   z value  P(>|z|)
──────────────────────────────────────────────────────
(Intercept)  0.00307589  0.00319195  0.963638   0.3352
──────────────────────────────────────────────────────

Getting at the missing multiplication method, there seems to be a problem in block creation where an extra singleton dimension is created in some circumstances:
julia> describeblocks(m500)
1,1: UniformBlockDiagonal{Float64} (1000, 1000) UniformBlockDiagonal{Float64}
2,1: SparseMatrixCSC{Float64,Int32} (500, 1000) BlockedSparse{Float64,1,2} # why does this have an extra dimension?
2,2: Diagonal{Float64,Array{Float64,1}} (500, 500) Array{Float64,2}
3,1: Array{Float64,2} (1, 1000) Array{Float64,2}
3,2: Array{Float64,2} (1, 500) Array{Float64,2}
3,3: Array{Float64,2} (1, 1) Array{Float64,2}
4,1: Array{Float64,2} (1, 1000) Array{Float64,2}
4,2: Array{Float64,2} (1, 500) Array{Float64,2}
4,3: Array{Float64,2} (1, 1) Array{Float64,2}
4,4: Array{Float64,2} (1, 1) Array{Float64,2}

julia> describeblocks(m500v2)
1,1: UniformBlockDiagonal{Float64} (1000, 1000) UniformBlockDiagonal{Float64}
2,1: Array{Float64,2} (500, 1000) Array{Float64,2}
2,2: Diagonal{Float64,Array{Float64,1}} (500, 500) Array{Float64,2}
3,1: Array{Float64,2} (1, 1000) Array{Float64,2}
3,2: Array{Float64,2} (1, 500) Array{Float64,2}
3,3: Array{Float64,2} (1, 1) Array{Float64,2}
4,1: Array{Float64,2} (1, 1000) Array{Float64,2}
4,2: Array{Float64,2} (1, 500) Array{Float64,2}
4,3: Array{Float64,2} (1, 1) Array{Float64,2}
4,4: Array{Float64,2} (1, 1) Array{Float64,2}


[Feature Request] Update Title on content change?

I'm trying to use chrome-tab-modifier to display the current track on plug.dj.  It works, but when the song changes the tab title does not update.  This would be a great feature for many sites I believe.

This will break down your browser performance. Pray for your CPU and memory.
Re-execute the code everytime the page change is not an elegant solution.
Tab Modifier can't add missing features for each website.
Best

You're already using a MutationObserver.  What is this for?
    // Set up a new observer
    observer_title = new window.WebKitMutationObserver(function (mutations) {
        if (title_changed_by_me === true) {
            title_changed_by_me = false;
        } else {
            mutations.forEach(function () {
                if (rule.tab.title !== null) {
                    document.title = processTitle(location.href, document.title);
                }

                title_changed_by_me = true;
            });
        }
    });

    // Observe when the website has changed the title
    if (document.querySelector('head > title') !== null) {
        observer_title.observe(document.querySelector('head > title'), {
            subtree: true,
            characterresponse: true,
            childList: true
        });
    }

Sure I already use an observer to detect when the website is changing the title like GMail, Twitter, etc.
I could observe the whole document but trust me it's bad design. This will slow Chrome.
Best


check if minion is up first before run_salt()

Hello,
I have added a check before passing returning any commands from run_salt() so if minion is down using test.ping it will raise an error, i have tested it already but i will test it again soon to be sure enough.
Thanks

Can one of the admins verify this patch?

We can run a test.ping if cmd() returns an empty dict.
If test.ping returns "Minion not connected", raise an error "Minion not connected", otherwise raise an error "Unkown error".
Also if cmd() returns a dict like {"host": "Minion not connected"}, raise an error.

Fixed in 6df82a96b4279de64c7d903590cb575a50579116
Just add "Minion not connected ?"  in the error message.
Thanks !


Wrong AF value on the second bar of a trend

On the first bar of a trend value of AF is inherited from the previous trend.
I.e. it should be updated on the the next bar of trend, becuase EP. But it'll be taken as initial AF (0.02 insted of 0.04). It breaks the calculation.

I plan to set up a unit test for this case. If you ave any suggestions on how to best set up unit tests for Pine, please let me know. Thank you very much for your PR on this!

Short of finding a way of doing a unit test, an example of the issue in a specific chart would be helpful for verifying this issue Thanks again, Ilya

It just struck me that the title of this issue could be misconstrued as being particularly vehement :)


Can't register in curator app

My simple-supply is running fine with docer-compose up. but when I am trying to register It shows error
screenshots are:

Same problem Here!

Fix is PR #37 Fix Genesis Block Creation


Fixing comments

Please don't merge this PR until all fixes are done.

Marked as on hold as requested


host: remove bootstrap double prints

Closes #2164

Not sure this is the best way. Very curious on how you would implement this.

LGTM, thanks!


Misc fixes

Changes proposed in this pull request:
Fix some minor issues I encountered while developing.

Can one of the admins verify this patch?

add to whitelist


Split up CSS file into multiple files

You could consider splitting these up into css files for each file.
For example, the countdown-specific css could go in countdown.css.
This would make the CSS more easy to understand.
But it's not really beneficial in the long run,
unless the CSS is being heavily edited
(eg in a redesign)

closing as won't-fix to keep our issues clean. As noted, it's not really a big deal unless we redesign, in which case we'll notice whether it's a big deal or not. But for now, it's not a big deal by default.


Timeout error returns incorrect message

When code execution times out the following is returned:
{"code":"ERR_SCRIPT_EXECUTION_TIMEOUT"}
It should return
{messages:[{code: "1629", message: "ERR_SCRIPT_EXECUTION_TIMEOUT"}]}
I couldn't immediately see how the timeout was being generated but I assume we can intercept it.

Seems to be fixed


require: 'mysql2' is NOT working in bundler

Receiving the following error in my files when executing or running tests:
cannot load such file -- mysql2/mysql2.

Why was this closed?


Recipe App: Initial Realease

Recipe app in Rails
The Recipe app keeps track of all your recipes, ingredients, and inventory. It will allow you to save ingredients, keep track of what you have, create recipes, and generate a shopping list based on what you have and what you are missing from a recipe. Also, since sharing recipes is an important part of cooking the app should allow you to make them public so anyone can access them.

Just go through each of them, I have even included pictures in some for clarity, incase you disagree with my observation you can send me a message on slack for further clarification

I really don't appreciate this review . it is the most petty review i had ever seen .The project it self is hectic and someone is requiring unecessary changes .This is patethic

I really don't appreciate this review . it is the most petty review i had ever seen .The project it self is hectic and someone is requiring unecessary changes .This is patethic

sorry to hear that, in case you find it unfair kindly as for second opinion.

I really don't appreciate this review . it is the most petty review i had ever seen .The project it self is hectic and someone is requiring unecessary changes .This is patethic

sorry to hear that, in case you find it unfair kindly as for second opinion.

@danmainah sorry bro ..am really stressed with project .lost my temper there . am going to work on the changes...otherwise am sorry

changes made

Fix layouts
Fix Destroy methods
About The Tests they are all working the previouse reviewer inferred and never observed.


Better checking of system.IndexInfo when rebuiling indexes

See CASSANDRA-10601

Looks good, and passes locally for me on all versions we test in CI. Thanks a lot, merging.


[FIXED] mesheryctl system stop bug for adapter containers removal

Notes for Reviewers
This PR fixes #8818
Signed commits

[X] Yes, I signed my commits.

@leecalcote #8788 must be merged first, this PR depends on it.

@zakisk were you able to test these changes you made locally

Yes

@leecalcote #8789 must be merged first, this PR depends on it.

@Philip-21 you need to merge #8789 PR first then merge this PR

@leecalcote #8789 must be merged first, this PR depends on it.

Thank you for pointing this out, @zakisk

Syncing this PR with head...

Syncing again...

Syncing again...

@leecalcote Did it work?

Let's discuss this on the Meshery dev call tomorrow,
Please add this as your agenda item in Docs: https://docs.google.com/document/d/1Dg4Uz9rGTuGHmYZwIt47z1j5x3LmnpxD1M1SgypAkQ0/edit

@leecalcote @Philip-21 check this again


Updated config example

Fixes RAI-13503

Should config.spec file be updated as well? Or eliminated if it is easy to overlook?


Given a list of github IDs, check whether each one has a W15-lab04  repo

For each one, write to a file Yes or No whether the repo exists. If it does exist, write the URL of the repo.
points:200

looks good

Make the searched repository name (e.g. "W15-lab05") configurable so that this can be used for any quarter or project.

F16 OK (200 pts)


failed to run sealer apply

What happened:
an error was encountered when i run sealer apply, it seems like excute kubeadm init failed . more details as below:

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

sealer version (use sealer version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

#138   fix it .

I have a similar problem, different places are shown in the following figure.

The problem of using CLI flag or Clusterfile is the same
os:ubuntu 20.04
sealer:0.1.4

/invite

This is CLOUD mode or BAREMETAL?

CLOUD mode

How can I reproduce it?


FINERACT-1541: Pentaho accounting reports converted to table format

This is the rebased version of :  https://github.com/apache/fineract/pull/2176
Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

I guess #2347 is the updated version of this. I'm closing it but let me know if that's not true and we need both.


Simple Undo/Redo support

Adds simple undo/redo support for object level changes, and the ability to step back nodes during polygonal drawing.

This PR will be up for review until it makes it into the StoreBound review stage, and once that is given the OK as far as acceptable functional review without bugs, this will be merged into 1.2.0 branch for the remaining features to be added before release.


Sidebar: Browser back/forward don't cause sidebar refresh

Sidebar needs to be refreshed based on the browser back/fwd action

merged to Develop


Add client configuration from dictionary

I've added this change that we implement in our own code, as it may be more broadly useful. As we don't store our service account JSON in plaintext, we can't use the from_service_account_json convenience method.
This PR separates out some of the logic from from_service_account_json into a separate from_dict convenience method.

split _ClientFactoryMixin.from_service_account_json

add from_dict to offer users a hook in without needing to load from plaintext JSON

add new test for completeness, though test coverage would be unaffected

Hi @mdhausman, I super appreciate you doing this, but I don't want to touch anything in core until https://github.com/GoogleCloudPlatform/google-cloud-python/issues/4267 is done. As part of #4267 we want to eliminate this class altogether, but I'll be sure to consider including similar functionality when we do that.


github workflow: update action

Avoid CI warning that node.js 16 is deprecated.
See https://github.com/riscv/riscv-cheri/actions/runs/7714759013: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Can we instead just sync with riscv/docs-spec-template again, which does include this fix among a bunch of other changes, rather than repeating the same fixes ourselves as the template?

Sure, makes sense. I'm not an expert on the processes here. This PR just came along with the same changes on a few other repos to get rid of the warning.

In my latest PR I did not merge with the templates repo since all of its history was squashed into the first commit of this repo. I could do a merge with --allow-unrelated-histories, so that future updates are simpler. @jrtc27 what do you think is the right approach? Should we continue diffing the files to the template and pulling over patches or do the merge?

In my latest PR I did not merge with the templates repo since all of its history was squashed into the first commit of this repo.

Thanks GitHub...

I could do a merge with --allow-unrelated-histories, so that future updates are simpler. @jrtc27 what do you think is the right approach? Should we continue diffing the files to the template and pulling over patches or do the merge?

Merging seems like the best approach going forwards, other than GitHub PRs not handling merge commits...

In my latest PR I did not merge with the templates repo since all of its history was squashed into the first commit of this repo.

Thanks GitHub...

I could do a merge with --allow-unrelated-histories, so that future updates are simpler. @jrtc27 what do you think is the right approach? Should we continue diffing the files to the template and pulling over patches or do the merge?

Merging seems like the best approach going forwards, other than GitHub PRs not handling merge commits... although given people seem to be using "Create a merge commit" for PRs I guess it might actually work ok?

Sounds good, I'll give this a try now.

Closing this PR, because #79 will handle this.


Change Global WorkQueue to create WQE for requests in "staged" status

As part of the MS Transferor design, global workqueue will have to create work for workflows sitting in the staged status, instead of the current assigned one.

Fixed by https://github.com/dmwm/WMCore/pull/9209


ADD labels on the MAIN PAGE

Description
missing labels "Hacktoberfest" and "GSSOC" on the main page
Screenshots

Any additional information?
For the repo to participate in gssoc ext 24, labels must be added
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

@YadavAkhileshh i cant perform this task, only you being the author would be able to add labels.Please kindly add labels for the repo to participate in Hacktoberfest and GSSOC


PLAT-72723: Update ui/VirtualList lifecycle method

Checklist

[X] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[X] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
UNSAFE_componentWillMount(), UNSAFE_componentWillReceiveProps(), and UNSAFE_componentWillUpdate() will be deprecated.
Resolution

Move the code in UNSAFE_componentWillMount() to constructor.
But updateStatesAndBounds was renamed as getStatesAndUpdateBounds to get a new state instead of calling setState in the updateStatesAndBounds.

Move the code in UNSAFE_componentWillReceiveProps() to componentDidUpdate.
But we still need the this.hasDataSizeChanged variable used in moonstone/VirtualList.
In addition, this.cc = [] for RTL was removed.

Move the code in UNSAFE_componentWillUpdate() and the part of the positionItems in render phase to getDerivedStateFromProps so that the previous first index and the previous childProps are only referenced in the getDerivedStateFromProps.

Links
PLAT-72723

LGTM

Hi @viodragon2
There are lots of bad practices in VirtualList. But to enhance the launch time performance and the scroll performance, we manipulate the DOM elements and the states manually in the VirtualList. As I mentioned the comments in PLAT-37236, the impact of calling the render function once more in VirtualList seems to be pretty large.
IMHO, if possible, we need to reduce calling the render function in VirtualList. To do that, we could not avoid updating states directly and referring the previous props from states in render phase.
But it is true that it is the right time to remove all the bad practices. Then we can do improve performance from another perspective for several months.
Please let me know your thought.

I tried a few things here and there with minimal changes in this branch. Here's a diff you can look at https://github.com/enactjs/enact/compare/feature/PLAT-72723-simple...feature/PLAT-72723-stephen
I'm still struggling how we can handle prevFirstIndex and childProps before componentDidUpdate but hopefully you get a generic idea on how we can move a lot of things in componentDidUpdate

https://github.com/enactjs/enact/pull/2108#discussion_r256657816

Is this.cc required to be reset when rtl prop changes? Doesn't index and key stay the same in RTL layout? Or am I missing something?

As I mentioned in https://github.com/enactjs/enact/pull/2108#discussion_r257102041, let's remove this code to reset this.cc.

Hi @viodragon2
I updated the code and the description in the PR. Could you review the PR again?
As you recommended, I moved the code in the deprecated lifecycle methods not to render but to constructor, getDerivedStateFromProps, and componentDidUpdate.
But I'm not sure whether it would be better to move the code in componentDidUpdate to getDerivedStateFromProps. Could you check my comment https://github.com/enactjs/enact/pull/2108#discussion_r257106546 above?
Please let me know your thought.
Thank you so much.


Convert videos on the same folder they are downloaded

Hello
I'm enjoying straw-viewer a lot! Using the gtk frontend to watch videos and using the -d command with --convert-to=mp4 to convert them. I only wish the program would save the converted videos on the same folder I have set to download them instead of defaulting to my home folder, I could not find any configuration instructions on doing so.

Fixed in https://github.com/trizen/straw-viewer/commit/7620cc345421cd067dcec880b36e6cc41ac98cad. Thanks for reporting.
Notice that there is also --prefer-mp4, which will prefer MP4 (AVC) streams over WEBM (VP9), if available.


Bug: Invalid descendant team link

As shown in the screenshot, the url contains "undefined".

Will be fixed by #627


feature(setState) New statement to set a specific state variable #143

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>Issue #143
Supports new syntax to set a specific state variable.

Coverage remained the same at 99.024% when pulling 73851b8ed9c6caa490a9e78de2f93ef07f256705 on jeromesimeon:js-feature-set-state into 698f7392e30ab6bba4c7fe54c7a30003acbc1068 on accordproject:js-release-0.20.