Any support for Remix/Hydrogen?

I'm looking to add preview functionality between Strapi and my Hydrogen app. Before I go too far is this possible to produce?

Hi @Olys6 I've never personally worked with Hydrogen, but the only thing this plugin does is build a URL according to your configuration and give you a button to open that URL. If you need to query data outside of Strapi when the preview URL is built, then you may have complications because the plugin does not currently support that, but it will in the future.
Let me know if that answers your question or if you are still confused about anything 🙂


docs: add example of parsing SDP using any source multicast

This is a proposed solution to #93

This is a good solution, thanks. We must add a test to the IS-05 suite to ensure this behaviour.

Please let's also merge this to v1.0.x as well.


Make computation expression keyword descriptions consistent

Changes keyword descriptions of let-bang and related keywords to be consistent by referring only to computation expressions, not asynchronous workflows, as per #5343.
Also, I've changed the grammar a touch; I think it is a little more readable now, but if those changes aren't good then I can revert them

(PR is broken; stuff is being included that shouldnt be)

This PR is now managed by this one:  https://github.com/Microsoft/visualfsharp/pull/5611


Define products.json format

There is not a clear definition of what the values are in the products.json for the exchanges.
"asset": "VIA",  --Con
"currency": "BTC", --Market
"min_size": "0.52410901", --Minimum  coin purchase purchase?
"min_total": "0.52410901", --Minimum coin purchase purchase?
"max_size": "1000000", --Maximum amount of coin you can buy at once.
"increment": "0.52410901", --Increment size (this I'm really unsure of)
"label": "BTC/VIA" -- label given to the coin/market pair.

Dear issue reporter,
We have slightly changed our github issue policy and would now kindly request folks that have questions that they ask them in our zenbot subreddit.
You can find it here: https://reddit.com/r/zenbot
This issue will be closed, but if you disagree with your ticket being marked as a question feel free to leave a comment defending your case.
Thanks for contributing time and effort!
Greetings,
🤖


Organ branch

Updated ToCanonical for liver_spleen_pancreas

Merge of the organ_branch with aortic calcifications added (no visualizations, only printing)


Code workflow

Title:

    Configure Azure Pipelines

Description:

    This pipeline configuration builds the application and produces a build for the Release configuration.

Test


(chemical)-[affects_expression_of]->(gene) hangs

{'message': {'query_graph': {'nodes': {'a': {'category': 'biolink:ChemicalSubstance', 'id': 'CHEBI:28119'}, 'b': {'category': 'biolink:Gene'}}, 'edges': {'ab': {'subject': 'a', 'object': 'b', 'predicate': 'biolink:affects_expression_of'}}}}}

Seems to run muuuuch longer than I would expect.  I gave up after 15 minutes or so; I think it actually ran much longer...

This does take a long time. It seems to complete, though. Less than 15 minutes for me. It's big, most or all from automat/ctd.

It's possible that other nasty things are happening here because there are so many results. For example, we may be DoS-ing the node normalizer?

Could be - I think we should leave it open to investigate

This runs in about 30 seconds now and seems to produce good results. Let me know if there are any other issues with this query and we can reopen.


[ENHANCEMENT] based on alpine docker image, much smaller.

Please don't add any time zone setting in dockerfile. We need to keep UI suitable for the global.
Also, after we moved this, the docker file may be not needed at all. Because it can't be released independently.

Please don't add any time zone setting in dockerfile. We need to keep UI suitable for the global.
Also, after we moved this, the docker file may be not needed at all. Because it can't be released independently.

Got it, two options:
1、we use the default time zone in dockerfile temporarily.
2、delete all dockerfile in this repo, in order to transfer it to apache-skywalking-rocketbot repo.
@wu-sheng I prefer 2ed. How about @TinyAllen ?

LGTM, I'll close this PR.

LGTM, I'll close this PR.

You can reopen it and delete the Dockerfile😄

Okay😂

UI in SkyWalking is binding release with webapp, also docker file released as UI too. So no need to add more, we just need to change the main repo submodule config.

UI in SkyWalking is binding release with webapp, also docker file released as UI too. So no need to add more, we just need to change the main repo submodule config.

I knew, but we think this repo can startup alone with nginx. So, we hope to provide some helpful dockerfile somewhere or not.

Docker file could be hosted in here, but we can't release them, and also need to highlight the purpose of dockerfile is just for developer review.

UI in SkyWalking is binding release with webapp, also docker file released as UI too. So no need to add more, we just need to change the main repo submodule config.

I knew, but we think this repo can startup alone with nginx. So, we hope to provide some helpful dockerfile somewhere or not.

Okay, we decide to hold those dockerfile in this repo.  But we need to remove time zone settings and adding some description in README.md to highlight the dockerfile just for developer review  or helpful suggestions. @Doublemine  Could you reopen this pr and fix it? Thanks~


fix(config-map): update examples in documentation (#1334)

Backport
This will backport the following commits from k8s-25/main to k8s-23/main:

fix(config-map): update examples in documentation (#1334)

Questions ?
Please refer to the Backport tool documentation

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1338

Questions ?
Please refer to the Backport tool documentation


Ensure that Windows builds get built and tested on a ZGC supported version of the O/S

TODO:  Actually this needs to be Windows 10 that this is tested on. So holding off as I'm not sure we can build and test on that OS just yet.


Complete chore/add-co-authoring-guide

Closes #58
While issue was originally to include links, including the details makes it more accessible and likely for contributors to read/follow. If we want to just include links for this (e.g. external or move this content to another markdown file) then that's also simple.
I've included details for GitHub Desktop/Git CLI as they'll likely be the two main options contributors use for source control.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add NFC Scanning capability

Add NFC Tag Scanning/Reading capability for specially coded NFC Tags to enable easy POS transactions
Description
App will be able to read valid NFC Tags to pre-populate the details required on the Transaction Send screen.
On supported devices, tapping a tag (from the home screen) can also launch the Verge app as well.
Motivation and Context
Functionality improvement - easier way to transfer
How Has This Been Tested?
Multiple send transactions of various types on multiple iOS devices.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Awesome 👏
There's still issues with the manual input of an amount but I'll fix it in the main repo. Gonna do a refactor, cause it's a hot mess 🥴


@conda-forge-admin,please add bot automerge

As per title.

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/genespeak-feedstock#6.


cie-middleware-linux: <IP_ADDRESS> -> 1.5.0

Description of changes
Minor updates, fixes several graphical issues
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[x] Tested compilation of all packages that depend on this change (none)
[ ] Tested PKCS#11, digital signature.
[x] Tested basic functionality of all binary files (cieid)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

@ofborg eval


Fix build issue (error obtaining VCS status)

I want to build this webterminal-proxy to test the Janus webtermina-plugin but couldn't build it on OpenShift nor my machine when running:
I got this error when running go build -o . or docker build ..
And, I got the same issue when building on an OpenShift cluster:
 => ERROR [builder 3/3] RUN go build -o .                                                                                0.4s
------
 > [builder 3/3] RUN go build -o .:
0.202 go: downloading github.com/gorilla/websocket v1.5.0
0.402 error obtaining VCS status: exit status 128
0.402 	Use -buildvcs=false to disable VCS stamping.
------
Dockerfile:3
--------------------
   1 |     FROM registry.access.redhat.com/ubi9/go-toolset:latest AS builder
   2 |     COPY . .
   3 | >>> RUN go build -o .
   4 |
   5 |     FROM registry.access.redhat.com/ubi9-micro:latest
--------------------
ERROR: failed to solve: process "/bin/sh -c go build -o ." did not complete successfully: exit code: 1

My go version is: go1.21.5 linux/amd64
The docker image uses currently: go version go1.20.10 linux/amd64
I added -buildvcs=false to solve that bug. See https://github.com/golang/go/issues/49004
To be honest, I'm unsure why this is now required. Wdyt?

Not sure why is it failing locally, when I try it on fresh clone of the repo with same version of go it works. The issue with the docker/podman is present tho and from what I saw it might be also fixable by adding .dockerignore where we specify .git (I think it is not necessary there anyway is it?). Once .git is ignored building image should work. I guess both options should be fine so I will let you decide. :)

I tried the .dockerignore solution first, but it didn't help me. Looks like the docker build cache was to optimistic for the COPY . . step.
With docker build --progress=plain --no-cache . I can confirm as well that it's working fine. So we can go just with that additional file and I will revert the change in the Dockerfile.
Thanks for your fast review. :)

ping @mimotej :smile:

Sorry for late review on this, I was off for a while. I think this solution sounds good so LGTM from my side.

@tumido can you approve/merge this?


Weave with recursive functions

Hey all - loving the library.
Question about using Weave for recursive function calling. See the toy example below:
@weave.op()
def recursive_function(n: int) -> int:
    if n == 0:
        return 0
    return recursive_function(n-1)

recursive_function(6)

The first trace sent to Weave looks to contain all the recursive function calls:

However it also generates 5 other traces. Is this expected behaviour? Or am I not thinking about this in the right way?
The use case for this recursive behaviour in the context of LLMs is multi-turn function calling (executing the function params and sending back to LLM for the next function given the last result).
Thanks

Hey @stantonius , that is expected because you're specifically filtering for the recursive_function op.  Here's fib with the same view showing all the times we called fib (including recursive calls):

If you remove the filter, you will see just the root call:

I can see why this might be confusing though.  Did you land on this page from the 🍩 link?  Were you expecting to see just 1 call because there's just 1 🍩 link?

Thanks for the reply.
Yes that is exactly how I got there, by opening the 🍩 link.
You're right - I am confused about what is being reported when I click that link vs when I view all ops, but in terms of the recursive functions tracking issue, Weave does work.
Thanks

I will close this ticket since the system is behaving as designed, but we do appreciate your feedback that the call link behavior is confusing.


langcheck.augment.synonym doesn't work because of some missing nltk package

>>> langcheck.augment.synonym('aaaa')

LookupError:
**********************************************************************
  Resource averaged_perceptron_tagger_eng not found.
  Please use the NLTK Downloader to obtain the resource:

  >>> import nltk
  >>> nltk.download('averaged_perceptron_tagger_eng')

  For more information see: https://www.nltk.org/data.html

  Attempted to load taggers/averaged_perceptron_tagger_eng/

Ref:
https://github.com/citadel-ai/langcheck/blob/7f5b4be37126f8958483028f472c645121bf630c/src/langcheck/stats.py#L33


Add validator

Link
https://github.com/Nicolab/crystal-validator
Checklist

[ ] - Shard is at least 30 days old.
[ ] - Shard has CI implemented.
[ ] - Shard has daily/weekly periodic builds (ideally with Crystal latest and nightly).

Thanks, but make another PR when it meets the first requirement.

In 25 days it'll be exactly the same module, but okay if I don't forget...


Install Daemonset by controller and sdk bundle update

As soon as the controller is deployed before executing anything else, the controller installs daemonsets and waits for the daemonsets to be ready. With this architecture, only the controller need to be deployed and the daemonset installation is taken care of by the controller.

/hold
until we have tests

Just curious, do we need to target multiarch for this operator? I saw the arm reference tag in this PR.

Should the hold be taken off of this PR?

/hold cancel

/lgtm

/override konflux

/override "Red Hat Konflux / dynamicacceleratorslicer-enterprise-contract / instaslice-operator-bundle"
/override "Red Hat Konflux / dynamicacceleratorslicer-enterprise-contract / instaslice-operator-controller"
/override "Red Hat Konflux / dynamicacceleratorslicer-enterprise-contract / instaslice-operator-daemonset"
/override "Red Hat Konflux / dynamicacceleratorslicer-enterprise-contract / pr group daemonset-installed-by-controller"


fix to report the correct row count

row count is reported as 0 currently. As the number of rows is logged at
info level, this can be misleading. This fix passes the CountingIterator
to the batch builder.

+1


FFMPEG  recorder not working at all.

Can someone please verify if they have used FFMPEG recorder recently? Tests are running properly but not able to see any videos 😢
Please help

Can see logs
INFO  com.automation.remarks.video.recorder.ffmpeg.FFMpegRecorder  - Trying to execute the following command: [ffmpeg, -y, -video_size, 1440x900, -f, avfoundation, -i, 1, -an, -framerate, 30, -pix_fmt, yuv420p, /Users/huzaifaahmed/Downloads/Work/video/temporary_recording_2022_31_10_19_56_11.mp4, -vsync, 2]
If I run this command in terminal I can verify the fffmepg starts properly and starts recording. But not sure what happens with Java

@SergeyPirogov Please if you can help

@huzaifaAhmedTestlio I experience the same problem.
But I think Sergei cannot fix this issue soon because he is sitting somewhere in Kyiv under bombing with constant electricity  outages.
You would better fix this issue and submit a pull request.
It's open source, your contribution is welcome! ;)

@huzaifaAhmedTestlio My problem was a bit silly...
but maybe this will help.
My problem was that when I run tests in TFS  there were videos but we see only a black screen.
The problem was that the lock screen was active.
Check if the lock screen is enabled on your computers...


add compatibility info option

Resolves #521

ee8jsmrbc5bm206k836c@bh2b070bfacvcc95n4tt:~/ytsaurus/yt/yt/server/all$ ./ytserver-all ytserver-master --compatibility-info
{
    "current_reign" = 2618;
}

Please capitalize commit message

Shipped!


Implement .format(moment.ISO_8601) to be an alias for .toISOString()

Fixes #3019

Are we sure we want this to always print UTC? That's not the way it works as a format constant, so it seems unbalanced.

Isn't that what was decided at the end of #3019, that its a toISOString() problem, that should be addressed separately?

Actually, if you go to the issue for changing .toISOString you'll see someone saying that we shouldn't change it at this point because too much code relies on it.
Basically, we can't agree on anything and we can't win :-).
Honestly, if you want to merge this, it's probably as good as any solution, even if it isn't the one I would pick.

Sorry I didn't see this sooner.  I'll go comment on the issue, but I'm not ok with it in this form.


[Chore] Configure CircleCI workflows and CodeClimate test coverage reporting

Coverage remained the same at 94.708% when pulling 0f255e7bdfdc72b0d60ce5feabf30b0263c3e0bc on ch-circleci-workflows into 871f792697d0da4f009b8a610e157571b3d48f94 on develop.


Rework addons (use rpc)

Migrate addons to https://github.com/hashicorp/go-plugin.
Closes https://github.com/woodpecker-ci/woodpecker/discussions/3214
This will likely take a lot of time to complete, please don't review yet.

One thing I noticed when thinking about the config api again ist that we should probably decided how we allow admins & maybe users to use plugins. For forges I think this approach makes sense. The previous building seemed to be already causing some issues, but using pure http seems a bit off for sth deeply intergreated as forges are currently.
For sth like config, secrets & registries it would be nice to allow repo admins to use their own plugins. We could allow grpc for that as well, but I actually think the http approach similar to the config-api as I started it months ago in #915 could be better suited and would be easier for developers to implement?


Refactored code

Removed Redundant codes
Improved documentation

I always think that this project is done; there is nothing to improve. But every time I find something to improve.
"You'll never reach perfection because there's always room for improvement" says all

Will test run and merge asap


Refresh combined FutureProvider

Assuming I have a FutureProvider combining two other FutureProviders.
Both futureProvider1 and futureProvider2 might throw an exception.
final futureProvider = FutureProvider<int>((ref) async {
  final future1 = await ref.watch(futureProvider1.future);
  final future2 = await ref.watch(futureProvider2.future);

  return future1 + future2;
});

Is there a convenient way to refresh the provider which causes the error?
context.refresh(futureProvider) would – of course – just refresh the combined FutureProvider, but not its dependencies.
The UI that uses the futureProvider does not know of futureProvider1 and futureProvider2, so it would be a bit awkward to having to refresh one of those.

A pattern for this would be to have all the providers you'd want to be refreshed to "watch" a common provider:
final myGroup = Provider<void>((ref) {});

final futureProvider1= FutureProvider((ref) {
  ref.watch(myGroup);
  ...
});
final futureProvider2= FutureProvider((ref) {
  ref.watch(myGroup);
  ...
});

...

ref.refresh(myGroup) // will refresh futureProvider1 and futureProvider2

That's an interesting approach. Thank you for your input :)

How about adding a onRefresh event, so a provider could itself call refresh on its dependencies? I think It's weird when the user of a provider has to call refresh on a different provider? 🤔

I think that's a fairly minor issue.

I have another use case where something like a onRefresh might be useful (imho) - I am using flutter_cache_manager to cache network requests, it would be nice that when it is called with ref.refresh(myProvider); the provider can clear the network cache, so next time a new network request is sent.. other approaches would be to either add a parameter to the onDispose whether it's disposed due to a refresh..  or add a property to the ref which is passed into the provider initialisation whether it a "refresh" or a "normal" create.. would you accept a PR for any of those variants? 😅
i'm pretty sure I don't want the call side of my providers to know which http requests have to be cleared for ref.refresh().

Feel free to make a PR

I came up with idea to use AsyncNotifier for refreshable combined FutureProviders.
I extended AsyncNotifier with async refresh method:
abstract class RefreshableAsyncNotifier<T> extends AsyncNotifier<T> {
  RefreshableAsyncNotifier();

  Future<void> refresh();
}

Example:
class CombinedFuturesNotifier
    extends RefreshableAsyncNotifier<FinanceOverview> {
  @override
  FutureOr<FinanceOverview> build() async {
    final result1 = await ref.watch(future1Provider.future);
    final result2 = await ref.watch(future2Provider.future);

    return FinanceOverview(
      result1: plafond,
      result2: _shouldShowResult2(result1) ? result2 : null,
    );
  }

  @override
  Future<void> refresh() async {
    await ref.refresh(future1Provider.future);
    await ref.refresh(future2Provider.future);
  }
}

To trigger refresh, eg. using RefreshIndicator:
   final result = ref.watch(financeOverviewProvider);

    return RefreshIndicator(
      onRefresh: () => ref.read(financeOverviewProvider.notifier).refresh(),
      child: result.when(
        skipLoadingOnReload: true,
// ... rest of the widget

AsyncNotifier solves this.
It's a FutureProvider where you can add custom methods. You can therefore do:
final futureProvider = AsyncNotifierProvider<MyNotifier, int>(MyNotifier.new);

class MyNotifier extends AsyncNotifier<int> {
  @override
  Future<int> build() async {
    final future1 = await ref.watch(futureProvider1.future);
    final future2 = await ref.watch(futureProvider2.future);

    return future1 + future2;
  }

  Future<int> refresh() {
    ref.invalidate(futureProvider1);
    ref.invalidate(futureProvider2);
    return future;
  }
}

Used as ref.read(futureProvider.notifier).refresh()


The F6 key is broken

Issue Type: Bug
Open vscode and try to press F6. Previously it cycled between various part of the interface. Now it is stuck.
 This works for me with latest insiders.
Can you reproduce using Visual Studio Code Insiders https://code.visualstudio.com/insiders/

Hello,
I am using the latest insiders updated today and I still think it
doesn't work like before.
Try to open an empty vscode, also close the untitled-1 document that
opens automatically. Then try F6 and Shift+F6. It works for a very first
time, but is stuck after.
Dňa 3. 2. 2021 o 10:33 Isidor Nikolic napísal(a):

Thanks for filling this issue. This works for me with latest insiders.
Can you reproduce using Visual Studio Code Insiders
https://code.visualstudio.com/insiders/
https://code.visualstudio.com/insiders/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/115677#issuecomment-772367821,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATNYX5PDOCT5JBDISU4Y43S5EJ5FANCNFSM4XANWIVQ.

Okey, I can only reproduce if no editors are open. Looks like a valid bug.

Thanks again for filling this issue!
The fix should be in vscode insiders from Friday, so try it out and let us know how it goes.


Update OpenStack docs for Terraform

Terraform looks great, thank you for adding it.
I've tested deployment in CiscoCloud and thought that we could extend our docs a little bit to make the deployments clearer for end users.

In particular You can find them in openstack/ in the main project directory looks to be outdated. Is it supposed to be in playbooks/?
From the user point of view, should we add a link to our docs of how to install Terraform? It's not provided from basic repositories yet.
To perform the terraform get or terraform plan commands, we need to:

cp terraform/openstack.sample.tf openstack.tf

and fill in all the variables.
Maybe it's a good idea to post some hints where to look for those variables. For example:
glance image-list for image_name
keystone tenant-list for tenant_id and tenant_name
nova flavor-list for control_flavor_name and resource_flavor_name
or the appropriate openstack commands such as openstack project list
security_groups probably should not be default to not mess up things.
The last one is that public_key should not be an ssh key itself but rather a path to the file.
Thank you.

I support, I had to make some effort to understand all the things. We must highlight more details in the documentation.

@loshkovskyi @altvnk thanks for the raising the issue. We're working on it now.

@loshkovskyi @altvnk I've pushed the docs at f07556c, would you review? I'm not sure what you mean by your public key comment, it uses a path now.

Thanks guys, now it looks more obvious how to start using terraform.


Update CustomOp doc with changes for GPU support

Description
Improve the custom operator example doc by adding how to write GPU custom operator.
This is a continuation of the CustomOp tutorial doc #17241
This PR is not

Updating docs on the MXNet website on extending MXNet
Consolidating operator related docs on the website

Those will be addressed in the coming PRs
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@samskalicky the fix is in #17516 and you can review it now

@aaronmarkham it looks fine to me here:
https://github.com/apache/incubator-mxnet/blob/9b93000c4a8f8da05e51547312bd605ec3798b3f/example/extensions/lib_custom_op/README.md
Looks like its just weird GitHub source-diff showing odd italics.

Hi, @rondogency I am trying to use the dynamic operator and have some questions.
How can we use mxnet::NDArray or mshadow_op used in xxx-inl.h of mxnet-backend operator? And I want to know how to use the mutateInputs function like in BatchNorm-like operators.
Thank you very much.

Hi, @rondogency I am trying to use the dynamic operator and have some questions.
How can we use mxnet::NDArray or mshadow_op used in xxx-inl.h of mxnet-backend operator? And I want to know how to use the mutateInputs function like in BatchNorm-like operators.
Thank you very much.

Hi @a550461053, MXNet custom operators have been designed not to integrate with any MXNet backend classes (mxnet::NDArray) to simplify building. We've designed MXTensor to be equivalent. Is there some other functionality you were wanting from NDArray thats not in MXTensor?
The mutateInputs API allows you to do the same as the backend APIs, so you can specify the index of the input that you want to be mutable to make a BatchNorm-like operator.

Hi, @rondogency I am trying to use the dynamic operator and have some questions.
How can we use mxnet::NDArray or mshadow_op used in xxx-inl.h of mxnet-backend operator? And I want to know how to use the mutateInputs function like in BatchNorm-like operators.
Thank you very much.

Hi @a550461053, MXNet custom operators have been designed not to integrate with any MXNet backend classes (mxnet::NDArray) to simplify building. We've designed MXTensor to be equivalent. Is there some other functionality you were wanting from NDArray thats not in MXTensor?
The mutateInputs API allows you to do the same as the backend APIs, so you can specify the index of the input that you want to be mutable to make a BatchNorm-like operator.

Ok, thank you. I want to create a custom operator calling another operator which input NDArray. Both operator is async pushed to engine, I think this way is possible. Also, I am not clear on using mutateInputs API, how and when to use it? If you can provide a example of the mutateInputs API, I will be grateful to you~

Ok, thank you. I want to create a custom operator calling another operator which input NDArray. Both operator is async pushed to engine, I think this way is possible. Also, I am not clear on using mutateInputs API, how and when to use it? If you can provide a example of the mutateInputs API, I will be grateful to you~

Hi @a550461053 currently the custom operator design focused on separating the custom operator from the MXNet backend source code complexity. This means that your custom operator can (must) be entirely separated from MXNet. So you cannot call a regular built-in MXNet operator from your custom operator. We have an item here #17006 for adding support in the future to be able to do this, but it is not implemented yet.
As for how to use mutateInputs, it works exactly as the doc describes:

This function allows you to mark some inputs to be mutable inputs. It is useful when using aux parameters for BatchNorm-like operators.

So lets say you have an operator with 5 inputs, you can mark the indices of the inputs that you want to be mutable like this (for example mark the last two inputs as mutable):
MXReturnValue batchNorm_mutateInputs(std::map<std::string, std::string> attrs,
                                     std::vector<int> &input_indices) {
  // mark mutable inputs
  input_indices.push_back(3);
  input_indices.push_back(4);
  return MX_SUCCESS;
}

@a550461053 Thanks for the questions. Currently you cannot call MXNet built-in operator from MXNet. We are making a plan for adding this support, but it cannot be easily implemented and may be a separate project. Also I added a snippet of how to use mutable input, hope it would help.

Ok, thank you. I want to create a custom operator calling another operator which input NDArray. Both operator is async pushed to engine, I think this way is possible. Also, I am not clear on using mutateInputs API, how and when to use it? If you can provide a example of the mutateInputs API, I will be grateful to you~

Hi @a550461053 currently the custom operator design focused on separating the custom operator from the MXNet backend source code complexity. This means that your custom operator can (must) be entirely separated from MXNet. So you cannot call a regular built-in MXNet operator from your custom operator. We have an item here #17006 for adding support in the future to be able to do this, but it is not implemented yet.
As for how to use mutateInputs, it works exactly as the doc describes:

This function allows you to mark some inputs to be mutable inputs. It is useful when using aux parameters for BatchNorm-like operators.

So lets say you have an operator with 5 inputs, you can mark the indices of the inputs that you want to be mutable like this (for example mark the last two inputs as mutable):
MXReturnValue batchNorm_mutateInputs(std::map<std::string, std::string> attrs,
                                     std::vector<int> &input_indices) {
  // mark mutable inputs
  input_indices.push_back(3);
  input_indices.push_back(4);
  return MX_SUCCESS;
}

Thank you and @rondogency . I am clear on use of mutateInputs API.
But now I can only build mxnet to create c++ customOp and I have a problem on compiling into python wheel at #17577

But now I can only build mxnet to create c++ customOp and I have a problem on compiling into python wheel at #17577
@a550461053 just to clarify, you do not need to recompile MXNet from source to use a custom operator, you can dynamically load your library into MXNet at runtime using one of the nightly builds from here: https://repo.mxnet.io/dist/index.html

@aaronmarkham or @wkcn can we merge this please?

Thanks for your contribution!


First attempt at improved toString for wideint.

Here's my attempt at improving toString. It supports the %s, %d (both decimal) and %x (hex) output formats.
We use a non-allocating overload for toString that spools its data via a caller-provided delegate, so that we don't have to allocate an output string.
The decimal formatting code also uses an on-stack buffer for storing the output digits so that we don't have to allocate. The buffer size is designed to be just a slight overestimate of the longest possible decimal representation of an n-bit number (see in-code comments), and digits are written in reverse order of extraction, so that we don't have to depend on ugly things like std.algorithm.reverse, which is actually throwing (because of stupid autodecoding).
Despite all of this, however, because of a silly limitation in current versions of Phobos we cannot actually mark toString as pure nothrow @nogc. Basically, the scope void delegate argument is, by default, assumed to be impure, throwing, and allocating, even if you pass in something that's pure, nothrow, and @nogc. We can't mark the argument with these qualifiers because it might break callers who need to, e.g., write to stdout (e.g., writeln).  The latest compiler does give us a way out, by templatizing toString into:
void toString(T : void delegate(const(char)[]))(scope T sink, FormatSpec!char fmt)

This overload, being a template, will trigger attribute inference and the compiler will correctly infer pure, nothrow, @nogc, etc., where appropriate.
However, the sad thing is, the current version of std.format does not recognize this overload of toString, so format() won't actually call toString, which defeats the entire purpose of this exercise. So unfortunately, we have to leave toString without pure nothrow @nogc for now.
I also tried to eliminate the dependency on std.format, but couldn't because although the docs on dlang.org claim that toString can take a string argument for format specifier instead of FormatSpec, I couldn't get std.format to actually recognize any such overload. So there's no way to get rid of the std.format import line, which may cause binary bloat in some cases. Hopefully this is not a show-stopper.

How do I reset the Travis CI tester? It seems to have failed on an unrelated intermittent server failure when trying to download Derelict.

However, the sad thing is, the current version of std.format does not recognize this overload of toString, so format() won't actually call toString, which defeats the entire purpose of this exercise. So unfortunately, we have to leave toString without pure nothrow @nogc for now.

It's clunky but it works with the right incantations; see for example the new Tuple.toString. Did you remember to mark it const?

Thanks for the tip, it actually works now!!!!  Hooray! (Now hoping it won't break on older versions of dmd in the Travis CI tester...)

Good.


Fix issue #615.

What changes were proposed in this pull request?
When batches can be skipped, extra checkEndOfRowGroup call can be also skipped.
Signed-off-by: Wang, Yue A<EMAIL_ADDRESS>How was this patch tested?
mvn passed.

@LuciferYang , it may not an elegant fix as it may not fully compatible with the batch reading framework design. Please help to review. Thanks!

As #615 I said, this pr is not root cause, although there will no error but result will not right,  IndexedVectorizedOapRecordReader should use indexedFooter call super.initialize, it my mistake, I'll give a pr to fix it. after complete #610 worker , the batch size will user-defined and I'll add more test case to ensure VectorizedOapRecordReader & IndexedVectorizedOapRecordReader robustness.

@yueawang I this #618 can fix #615 and result correct, please help to review~


chore: publish to GitHub Packages

Publish to GitHub Packages in addition to NPM, so that we can publish private packages in GitHub Packages and use them alongside palmetto-components.
Context:

https://github.community/t/github-package-registry-with-private-packages-proxying-scope-to-npm/2782
https://sevic.dev/npm-publish-github-actions/

What type of change is this?

[x] Updating deployment/build pipeline.

Thanks for getting this done @waissbluth


There is currently no documentation/example on how to run just 1 version of a model with multiple versions

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
https://docs.getdbt.com/docs/collaborate/govern/model-versions
What part(s) of the page would you like to see updated?
I have searched across the docs and couldn't find the info I am after. It might be there somewhere, but if it is, it should be added to https://docs.getdbt.com/docs/collaborate/govern/model-versions as well.
If a model has multiple versions, I am quite sure that we can run:

all versions, with dbt run -s my_model
but also specific versions, with dbt run -s my_model.v2 for example

This syntax with .v2 doesn't seem to be anywhere in the docs.
Additional information
No response

confirming syntax in slack


Method params types suggestion

Hi!
Just a suggestion:
Most of the FlowRouter methods have optional params.
interface Router {
    // ....
    url: (path: string, params?: Param, qs?: QueryParam) => string;
    path: (path: string, params?: Param, qs?: QueryParam) => string;
    // ....
 }

With these types, one needs to pass undefined or an empty placeholder value.
const path = FlowRouter.path('a-path', undefined, {q: "a query"});

In my opinion, undefined represents values that are not yet set in the runtime, whereas if you explicitly need to set a value to a non-value, null should be used. With that said, I think it may make sense to use union types with null instead of the question mark so devs call the methods like this:
const path = FlowRouter.path('a-path', null, {q: "a query"});

If you agree, I could submit a PR at some point.
Thanks for your time and work on this project!

Hello @harveysanders,
Pardon me for answering almost a year later, I agree, and love to add support for null along with void 0/undefined feel free so send a PR

@dr-dimitru no worries! I just submitted #106 for your consideration

Published as v3.10.1
@harveysanders thank you for contribution 🙏


Change  includes to  when using standard exceptions

Standard exceptions like std::out_of_range are defined in <stdexcept>, not in <exception>.
This fixes compilation issues i had with MSVC if I didn't include <stdexcept> before including some immer headers.
Thanks for this library btw !

Excellent! Thank you!

Codecov Report

Merging #179 (60f52a2) into master (39f8690) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #179   +/-   ##
=======================================
  Coverage   90.91%   90.91%
=======================================
  Files         104      104
  Lines        9131     9131
=======================================
  Hits         8301     8301
  Misses        830      830

Impacted Files
Coverage Δ

immer/detail/arrays/no_capacity.hpp
89.39% <ø> (ø)

immer/detail/arrays/with_capacity.hpp
87.21% <ø> (ø)

immer/detail/rbts/rbtree.hpp
96.47% <ø> (ø)

immer/detail/rbts/rrbtree.hpp
88.54% <ø> (ø)

immer/map.hpp
97.82% <ø> (ø)

Continue to review full report at Codecov.

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


Brick Dimension Size Classes Issue on iPad pro device

This is similar to the issue we closed last week. (https://github.com/wayfair/brickkit-ios/issues/6) However, it's more weird than previous one. When app is run on iPad pro simulator it shows correct number of horizontal bricks. However, when app is run on the real iPad pro device, the issue is same as mentioned in the link above.

@thevwu Can you take a look at it if that is fine?


Openengsb 2156/properties

cleaned up properties in parents/shared/pom.xml
http://issues.openengsb.org/jira/browse/OPENENGSB-2156

Is my assumption correct that the pre-push script runs through without errors with your modifications? :-)

yes, I ran the script and there were no errors.

great :-). merged. Thank you :-)


Unable to rescan

I created a new subfolder into my music folder. My music folder is added to the musikcube indexed paths from before. The new subfolder appeared in directory view. Then I added one track to this subnew folder, but musickube didn't find the track.
It seems since last I updated (some releases ago) the console has gone away, so I cannot issue a rescan myself anymore. The track only appeared after restarting musikcube.
Is there still any option to issue the rescan manually?
I am running <IP_ADDRESS>

Yep! Pressing CTRL+r will pop up a menu that allows you to "scan for changes" (only add new files or update files that seem to have changed) or "rebuild library" (forces a refresh of all music).
Closing this issue -- please re-open if you're still having problems.

Fantastic, thank you 👍


spec: allow empty App.Exec in image manifest.

As ACE can override and replace the App.Exec section, we should allow
empty App.Exec. This also allows some docker images that have empty
CMD/Entrypoint to be transformed to ACIs.

Seems reasonable to me, why not allow acis without an exec in the spec?
lgtm

fixes #504

lgtm

Rebase please

Rebased.

LGTM


How to force bot to to finish autoplay and go to queue?

Please tick all applicable boxes.

[x] I am using Python 3.5.3 or higher (run python --version on the command line)
[x] I have followed the official guides to install the bot for my system
[x] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[x] The latest master version (release-260419)
[ ] The latest review version

What type of issue are you creating?

[ ] Bug
[ ] Feature request
[x] Question

Description of issue
I can't understand how to force bot to stop playing autoplaylist.
I want it to play autoplaylist after summon, but I can't find any command to force bot to play queue.
Steps to reproduce

Setup bot.
!play anything
It's in queue, but it will be played only after autplaylist and that is sad ;'(

musicbot.log

!skip


text view shouldn't be editable to prevent selection with TAB on hardware keyboard

If you have a hardware keyboard pressing TAB will select a UITextView inside STTweetLabel. It can be then edited which etc. This commit fixes it

Hi!
I just wanted to tell how  much you  and your help meen to me,  so please  read  my whole message here http://wish.themark712.com/e4mvxnk
Rushing, vinner_2112


Investigating fallback option to use goodhosts on Windows

Like in the macOS start, we might want to investigate and use goodhosts to set entries in the hosts file for: oauth, api entries. This might also help those with VirtualBox [Ref: #751] without impacting us (as this does not affect the Hyper-V setup).

We do this on macos to workaround the fact that oc is not built natively and is not using /etc/resolver/. For this limited use case, oauth and api entries are enough.
Adding entries to /etc/hosts on Windows would be fairly limited as only a very small set of domains would be accessible.

See #756, as although people 'expect' us to automate this, just documenting this might be the alternative approach. Maintaining consistency and adding entries for apps is hard to realise.

With recent decisions we do not work on this.


Retrieve latest docs version from the branch while deploying

@arvi3411301

If this means what I think this means its not relevant. Moved latest docs version as hardcoded ENV in Dockerfile


NPOI - New Feature - custom color

Hello,
Can you please add a new API that allows adding custom color to "mappingIndex" in the “IndexedColors” class?
Thank in advance
Guy Katz

Hi @Maz4Life,
may I know the purpose of having this API?
As the class IndexedColors is more like a query dictionary for color name and index, and has limited index to support (56 at most)
And, not like color palette which belong to the workbook, this indexedColors is not related to excel workbook
Even we do a change on the dictionary of indexed Colors, we're not able to read back from excel file


Querying large tables without holding the whole result set in memory

Currently, most libSQL client will read the whole result set into memory because they're using a version of the remote protocol that only supports that. Let's work towards enabling cursor-based queries of Hrana 3 in the drivers.

It's the aim of #798 PR.


Client-side Structure

Luis and I have been discussing the atomic design structure for our client-side:
http://bradfrost.com/blog/post/atomic-web-design/
This has a great potential of creating a strict component-based structure where everything is split into levels. Each level is used by the level above it until you reach the page where the content is shown. However, I am not sure if this can be done with our current code.
An alternative to that approach is to use the suggested article for large scale vuex applications.
https://medium.com/3yourmind/large-scale-vuex-application-structures-651e44863e2f
With this approach, we have come up with the following structure. The naming conventions are still off, but we can talk about those.

I am all for this.  Would like to explicitly express my vote for YES.
As far as what your screenshot shows, this structure makes sense.  My only question is, and its not at all a major concern, more of just out of curiosity, what would go in Main/_api if all individual features could have their own _api spaces?
Would also like to implement this sooner than later to see if we can make this work with what we have up right now.

The problem is, we would copy files if we need re-usability. The atomic file structure approach remedies that problem.
Let me know what you guys think.

I think this might be the best solution for re-usability and for associating appropriate items together. (The guy's article probably did this, but he didn't display his whole structure.)


Error: No matching export in "xxx" for import "default"

Using the plugin results in the following error when trying to build.
A similar error happens when I try to use typeorm in my project. The error that occurs if I use typeorm is with "uuid" not having a default import.)
✘ [ERROR] No matching export in "node_modules/acorn-loose/dist/acorn-loose.mjs" for import "default"

    node_modules/@mikro-orm/core/utils/Utils.js:1:251:
      1 │ ...ort __import_os from "os";import __import_url from "url";import __import_fsExtra from "fs-extra";import __import_crypto from "crypto";import __import_acornLoose from "acorn-loose";import __import_acornWalk from "acorn-walk";import __import___clone from "./clone";import __import____enums from "../enu...

This is the error I get if I try using typeorm:
✘ [ERROR] No matching export in "node_modules/uuid/dist/esm-node/index.js" for import "default"

    node_modules/typeorm/query-builder/InsertQueryBuilder.js:1:7:
      1 │ import __import_uuid from "uuid";import __import____driver_DriverUtils from "../driver/DriverUtils";import __import____error from "../error";import __import____error_InsertValuesMissingError from "../error/InsertValuesMissingError";import __import____error_ReturningStatementNotSupportedError from "../e...
        ╵        ~~~~~~~~~~~~~

This is because some library (like uuid or acorn-loose) has exported both CommonJS and ES module files, where importing them needs different style of codes:
// original code
require("uuid")

// possible replacement in esm context
import __import_uuid from "uuid"

// another possible replacement
import * as __import_uuid from "uuid"

The 2 replacement above has different semantics depending on how the uuid module look like. Even when the uuid is a cjs module the behavior will differ when esbuild detects Node.js ESM context (i.e. file has '.mjs' extension or there be "type": "module" in package.json).
So it is not always safe to choose which style to convert. This plugin assumes a common situation where you're bundling a CommonJS module into ESM format, and the dependencies of that module are also in CommonJS, like how react-dom depends on react.
-->: depends on

Your esm code --> react-dom (cjs) --> react (cjs) ✅

Your esm code --> typeorm (cjs) --> uuid (esm) ❌

So maybe I should add an option to let you opt-in the style of importing external modules, like requireReturnsDefault
requireReturnsDefault: (mod) => !['uuid'].includes(mod)

Just published<EMAIL_ADDRESS>with the new option requireReturnsDefault, maybe you can give it a try.

Little nitpick: The type declarations seem to be faulty.
declare function commonjs({ filter, transform, transformConfig, }?: CommonJSOptions): Plugin;
should be
declare function commonjs({ filter, transform, transformConfig, requireReturnsDefault, ignore, }?: CommonJSOptions): Plugin;
shouldn't it?

Anyway .. using
commonjs({ requireReturnsDefault: (mod) => !["uuid", "glob"].includes(mod) })
I can now build everything. Sadly it still doesn't work when I try to run my code but that's another issue I guess.
In case you are interested:
[00:17:50][Error] ReferenceError: __dirname is not defined in ES module scope
platform for esbuild is node and format esm.
I need my code to be bundled to a ESModule to work properly in the environment I run the code.
But as I said that is probably a different issue so thank you so far. :)

The type declarations seem to be faulty.

My mistake, just fixed that on v0.2.4.

ReferenceError: __dirname is not defined in ES module scope

There's no global variable __dirname in ES modules context, instead they are replaced by import.meta.url. See https://nodejs.org/docs/latest/api/esm.html#differences-between-es-modules-and-commonjs.
Code depending on the location of itself is often not working well with bundlers, for example:
fs.readFileSync(path.join(__dirname, '../asset.txt'))

The above example code assumes it can find asset.txt at runtime right in its parent directory. However bundlers won't know this infomation. Some old versions of webpack may execute a crazy logic that it simulates the whole filesystem once matching code patterns like that.
In this case, you'd better just not bundle the dependency and leave it as-is.


Add links to  Tutorial: Deploy an ASP.NET Core and Azure SQL Database app to Azure App Service

Add links to https://docs.microsoft.com/en-us/azure/app-service/tutorial-dotnetcore-sqldb-app to the end of all on boarding tutorials.

@Rick-Anderson ,
By "onboarding tutorials" do you mean just:
Razor
MVC
Blazor
Or did you intend this link to be added to more than that such as:
Minimal Web API    (Not sure if this is the new intended starting point or not for web API)
SignalR

Yes, all of those are introduction tutorials.


Macros

Hi Eugene,
I have been trying to record a macro to allow me to have a two numbered television channel selected.  However, to date I have been unsuccessful.
item file setting
Switch Broadlink_Samsung_10  {mqtt=">[broker:broadlink/channel_10:macros:*:auto]"}
Are you able to assist me?
Thanks

Please use "macro" not "macros" message


[Linked Account] Hide backup and linked account option in profile tab

The feature already add in extension dev version 2.1.8


Pvb/discover code actions

Script side to enable codeaction for error codes,  needs Dev15 changes

:+1:

👍

I'd like to try this out, is there any way to get a fix to appear outside of the test suite, or manual interactions with the language service protocol? Maybe a branch of VSCode that knows to ask TS lang services for fixes?

@alexeagle Not yet unfortunately, VS Code is next on my list after I'm done with the VS integration.

Thanks, I just wrote a small program using the LanguageService to try it
out, along with diff/colors for displaying the delta after applying.
On Mon, Jul 18, 2016 at 9:52 AM Paul van Brenk<EMAIL_ADDRESS>wrote:

@alexeagle https://github.com/alexeagle Not yet unfortunately, VS Code
is next on my list after I'm done with the VS integration.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/TypeScript/pull/9304#issuecomment-233388459,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC5Iw_X4DwDbUB0cuPUsuMbx6X2fBTpks5qW69jgaJpZM4I7ObZ
.

Closing this in favor of more smaller PRs #10185


Why include generated schema.json in the app?

Hi there,
I generally like the structure and works of GraphQL but I don't see the purpose of generating a json and then including it. It sort of defeats one of the main strengths of GraphQL, which is that it's less prone to cause errors due to changes server-side (since we are querying specific things).
Now I have to generate a new JSON file every time the server decides to do an update? Feels odd.

@digitalbuddha
We want to use apollo-android in our new project, but our backend developer told us that the schema for our graphql api could be changed at any time.
Given such restriction, Is that possible we still able to use apollo-android in our project someshow ?


Removal of dead links to tutorials in examples

After this PR, the word 'tutorial' no longer appears in any of the examples/ notebooks. A lot of links to the old tutorials were fixed and replaced to the corresponding user guide links.

Note that this PR will address #1793 once the website is built and re-uploaded to S3.

Ready to merge?

I think so.


add update profile and auto generate api key

this fix https://github.com/healthsites/healthsites/issues/1193
This is how profile show
We have 2 button

When we don't have any key, looks like this

When update profile

When submitted

Coverage decreased (-0.08%) to 39.571% when pulling cb69c0abde26be11b6c6e475fb19f303fb296f84 on meomancer:develop into cc8195a6e2a5000cd7d0eb93e80e2921932f0ee7 on healthsites:develop.


Barcode type must be set error since update

Hello,
I'm using the PHP generic card sample.
Since I updated my dependencies:

Upgrading google/auth (v1.30.0 => v1.34.0)
Upgrading google/apiclient-services (v0.317.0 => v0.332.0)
Upgrading google/apiclient (v2.15.1 => v2.15.3)

I got this error from Google API:
{ "error": { "code": 400, "message": "Barcode type must be set.", "errors": [ { "message": "Barcode type must be set.", "domain": "walletobjects", "reason": "invalidResource" } ] } }
Did you experience something like this recently ?
Thanks

I had run into this issue as well and reached out to the Google Wallet API support team (thank you team!!). You can set the barcode to null to hide. I was trying to use "UNSPECIFIED" like in their demo but that doesn't seem to work anymore. Maybe this'll help someone who was googling this issue like I was.


Overscroll stretch animation makes SliverAppBar stretch when pinned is true

When using a SliverAppBar with the property pinned set to true, the overscroll stretch animation stretches the SliverAppBar instead of just the other content of the screen.
When not using a SliverAppBar inside a CustomScrollView (aka the most popular way: a scaffold with an appbar and a body), it behaves differently: Only the body stretches.
Current behavior (SliverAppBar inside a CustomScrollView):
https://user-images.githubusercontent.com/26173202/193195619-e0a19db0-977c-4a92-a09b-5c593fdf497a.mp4
Expected behavior (Scaffold with the app bar and body properties set):
https://user-images.githubusercontent.com/26173202/193195736-938d7536-b37a-4597-b352-3dff90c0cbe0.mp4
I thought a bit before posting this issue: "Is that really an issue or just intended?" but I came to a conclusion: If the user specifically wrote that it wants the appbar to be pinned, I think it expects it to behave as a regular app bar would (like me did 😁). So... It's your choices to decide if it is an issue or not!

[√] Flutter (Channel stable, 3.3.3, on Microsoft Windows [versÆo 10.0.22000.856], locale pt-BR)
[!] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    X cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    X Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.
[√] Chrome - develop for the web
[X] Visual Studio - develop for Windows
    X Visual Studio not installed; this is necessary for Windows development.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2021.2)
[√] VS Code (version 1.70.2)
[√] Connected device (4 available)
    ! Device RQ8N5001GPD is not authorized.
      You might need to check your device for an authorization dialog.
[√] HTTP Host Availability

! Doctor found issues in 2 categories.

Hi @Joaaofiilho,
Thanks for the report! This is a known issue being tracked at #104437 (the OP is using SliverAppBar.medium/ SliverAppBar.large which has pinned = true by default).
Closing this issue as a duplicate, so please follow up on it for further updates.


Throw an exception if someone tries to delegate to someone who is already delegating

Hi folks is this issue still up for grabs?


1.1.0_crab version of Don't sort list each iteration in FileBased splitting

Master PR here https://github.com/dmwm/WMCore/pull/7694
Could we also have a new tag created for our branch (1.1.0.crab3) after the merge? Thanks!

Thanks Emil for the fix. 1.1.0.crab3 tag is created.


JAVA17 and JAKARTA

Are there changes are needed to get ready for JAVA17 and JAKARTA?

Not that I am aware of. Is there a specific reason for your question?


WIP: feat: vuln attest support

Signed-off-by: Batuhan Apaydın<EMAIL_ADDRESS>Co-authored-by: Furkan Türkal<EMAIL_ADDRESS>
Summary

Users might upload vulnerability scan results in form of attestation within the OCI registry
Ticket Link

Fixes #442
Release Note

feat: vuln attest support

Looks good, the lint errors should be easy!

hey @dlorenc, I know spec documentation is not perfect but we tried to do our best, can you please review it, thanks in advance 🤝

kindly ping @dlorenc

kindly ping @dlorenc

Sorry missed this because of the WIP in the title. Is it ready for a merge?

I think yes, but it'd be nice if you can review it one more time I guess.

LGTM!


Did you ever create a NuGet package?

You talked at one point about creating a generic package. Is that still in the works?

I briefly considered it, but given how many ways people could possibly want to configure their apps to customise and tweak things (and the need to keep in step for every new release of ASP.NET Core and maybe need to make breaking changes), I decided against it.


Add documentation on how to migrate from 5.9.0 to 6.0.0 - password breaking change

Is your request related to a problem? Please describe.
I want to upgrade from 5.9.0 to 6.0.0. However, it's unclear from the gecko how to deal with the removal of the password generation. I don't want to change the password because that will generate application downtime.

Describe the solution you'd like.
Have some clear documentation on how to achieve this, such that not everyone needs to figure this out on their own.

Describe alternatives you've considered.
I'm considering moving away from the module and importing the created resources as individual resource blocks. Bing AI/ChatGPT is pretty good in such mappings.
An alternative would be to add the db id fix to version 5.10, such that it is not coupled with the breaking change.

Additional context
I just moved to 5.9.0 just to find out it broke other stuff because of the bug concerning the db id. Which is fixed in 6.0.0, only to find out that it is coupled with a breaking change with no clear solution.

My current solution is:
While on 5.9.0, create a random_password resource block
resource "random_password" "rds_master_password" {
  length  = 16
  special = false
}

Move the password from the module to the new resource block by running
terraform state mv 'module.db.random_password.master_password[0]' random_password.rds_master_password

Change these parts in the module
version                                = "~> 5.9.0"
create_random_password = true
random_password_length = 16

to
version     = "~> 6.0.0"
password = random_password.rds_master_password.result

Run
terraform init -upgrade
terraform plan
terraform apply

While your current solutions seems sound, I would recommend you revisit the manner in which the master password is used. It should be treated similar to the AWS root user's password - where its there when you need it for only a small select set of actions, but by in large, you should create additional users with the appropriately scoped permissions for their respective tasks. This is what allows you to enable the auto rotation of the master user password as well


Use 3rd party query builder

It would be awesome to be able to use custom QueryBuilder like https://knexjs.org/. It has a lot of cool features, migration support, seeding, etc.

I was thinking about that some time ago. In the end you could use it just to generate the query and execute it via driver.execute() right now:
const query = knex.select('*').from('users')
  .where(knex.raw('id = ?', [1]))
  .toSQL();

const driver = orm.em.getDriver<MySqlDriver>();
const res = await driver.execute(query.sql, query.bindings);

But this way one would have to use real field/table names. Another option is to extend/reimplement the query builder. Not sure how the integration should work, WDYT?
Btw I am planning to add support for migrations via https://github.com/sequelize/umzug some time in the future.

I think there are 2 options:

implement your SqlQueryBuilder based on knex
add thin abstraction over QueryBuilder so any QueryBuilder library can be connected

If you integrate knex, you will get migrations and seeds for  free :) Also community of your lib potentially will grow because those who knows and uses knex will feel comfortable when using your ORM (I guess).
The good think about knex is that it abstracts query building very well. Sometimes you need to exec some crazy query (e.g., recursive query) but at the same you want to have a good level of portability between database vendors. And knex allows this. Not sure about implementation details but I like their interface :)
The example you showed with mapping is quite cool actually! Maybe if you could export this as some utility function or base method in Repository, so other can use this, it would be awesome.

What I still do not understand fully is the way you would like the result to be let's say better for user. If I change the implementation of QueryBuilder, there will be pretty much zero difference for user, as its public API will remain the same. If the desired result is to use knex as a query builder instead of what currently sits inside ORM as QueryBuilder class, then my example above is the way to go. Sure I can wrap that code somewhere so its easier to use, I just need to understand what should be the result.
So if the result should be easy way to use knex instead of internal QueryBuilder, then it might be just the mapping code from above hidden under something like EntityManager.runKnexQuery() method (not very nice name, lol):
const query = knex.select('*').from('users').where(knex.raw('id = ?', [1]));
const entities = await orm.em.runKnexQuery(User, query); // root entity is needed

I could imagine KnexQueryBuilder class that would extend/wrap knex and be able to do this (as I definitely do not want to pollute EM API with this). It would have same API as knex with execute method that would handle the mapping. This thing could live inside the repository as part of utils folder.
const qb = new KnexQueryBuilder(orm.em, User); // one would have to pass the root entity probably
qb.select('*').from('users').where(knex.raw('id = ?', [1])); // same API as knex
const entities = await qb.execute(query, { mapEntities: true });
// `mapEntities` flag is something I am planning to add anyway to ease the usage of QB, it will do the `orm.em.merge()` part automatically then

Also, how will I get migrations and seeding for free? One can always add knex to the project for such thing, it can live next to the ORM without any problem I believe, sure with the obstacle of having different field names than entity property names. Again, can you propose some way of how the API could look like?

My initial intention to create this issue was the desire to use knex for advanced cases (recursive queries). Knex allows to do powerful things and keep queries at least semi-abstract relatively to database vendor.
I guess that it's enough to have EntityRepository.map(userProps) (I guess you call this  API to fulfill this issue requirement, so then it's possible to use knex at repository level:
class UserRepository extends EntityRepository {
  async findById(id) {
     const results = await knex.select('*')
       .from('users') // here I can use for example `.from(this.tableName)` or something similar
       .where(knex.raw('id = ?', [id]));
     return results.map(user => this.map(user))
  }
}

But if you support such behavior, then I don't know whether it make sense to have own QueryBuilder abstraction. I don't know.
About migrations and field names, frankly speaking I don't think it's a big issue to use different names in migrations and in models (at least currently this is how I do in my app :)).
I don't think that it make sense to add additional level of ORM abstractions on top of migrations because then it will be hard to do low level configuration of the database

It definitely makes sense to keep current QueryBuilder, as its pretty smart in terms of joining (see implicit joining here: https://b4nan.github.io/mikro-orm/query-builder/). It uses entity metadata under the hood. knex is just a 'native sql query builder', you have to instruct it about everything like what are join columns and pivot table names, etc.
Will think about this later, having some deadlines now, but adding support to repositories probably makes the most sense. Currently there is only this.em and this.entityName but adding some helper method for table name is not a problem (in the end one can always get the entity metadata from static storage helper class as in my previous comments).

FYI started to play with knex as a base layer for SQL drivers. Not really because of your concerns, but because of other features I would like to cover in near future - schema diffs and pooling mainly. Also I could easily get support for more SQL dialects to cover more databases. It might end up with some BC breaks (but save a lot of code), so v3 might be ahead of us :]

I will close this one with #61, integrating knex will take more time and work, will create new issue for that once I am sure how to proceed. I was surprised that knex is not really 100% ready as few workarounds I did are not present there and had to be done via knex.raw (like cascading truncate in postgre). Also the knex.raw does not behave the same as executing on raw driver level, although they say so (e.g. in sqlite it does not return inserted id although the underlying driver does return it), but it works consistently when using knex.insert()... (which means I will need to rewrite the QueryBuilder to use knex under the hood).
At this time I won't provide metadata at repository level, but you can access the global storage manually if you want to get the table name and property field names based on your entity metadata (const meta = MetadataStorage.getMetadata(Book.name);). You can create your own base repository with those helpers and register it in MikroORM.init({ entityRepository: MyBaseRepository }) so all repositories will use it.


new tools: split vcf

from @davemcg's post:
split a vcf into n pieces:
hts-nim-tools vcf-split -n 10 --prefix split $vcf

will create split.1.vcf .. split.10.vcf.

Going to have to update my post when this is finished!


Update guidance on cross-taregting

Could you fix https://github.com/aspnet/EntityFramework.Docs/issues/581 as well by linking to this from https://docs.microsoft.com/en-us/ef/core/get-started/uwp/getting-started instead of cross-targeting

@AndriySvyryd This is a little more work than I want to do right now because I think we also need to actually add the steps for creating the console application, and it would be good if the steps are actually tested.


[CT-1854] [Bug] Incrementally materialized tables do not obey hours_to_expiration config

Is this a new bug in dbt-bigquery?

[X] I believe this is a new bug in dbt-bigquery
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
After we moved some tables to incremental materialization, subsequent dbt runs did not set the expiration date to the current timestamp plus hours_to_expiration hours, causing our tables to expire. I took a look at the code and found that incremental materializations did not actually update the table options; the table options were only set on table or view creation.

Expected Behavior
We would expect that the expiration date of the incrementally materialized table would be updated on each subsequent dbt run - not just on initial table creation. The docs [1] do not explicitly specify that this behavior is expected, but if it is, a note about this behavior would be helpful.
[1] https://docs.getdbt.com/reference/resource-configs/bigquery-configs#controlling-table-expiration
Steps To Reproduce
In any environment, create an incrementally materialized table and set an hours_to_expiration config. dbt run, and note the expiration date is set properly. dbt run again; the expiration date is no longer updated
Relevant log output
No response
Environment
- OS: dbt Cloud, reproed on MacOS 12.3.9
- Python: unsure what version dbt Cloud uses, reproed on 3.9.15
- dbt-core: 1.3.2 on cloud, 1.3.1 locally
- dbt-bigquery: unknown on cloud, 1.3.0 locally

Additional Context
No response

Thanks for noticing this and reaching out @illiriks !
Docs update
Agreed that a note about this behavior in the docs would be helpful. I opened up this PR to update the docs: https://github.com/dbt-labs/docs.getdbt.com/pull/2837
Adding this as a new feature
I can totally see how this was unexpected from an end-user perspective. Since the original implementation is behaving as designed, I'd consider this a feature request rather than a bug though.
We don't have the capacity to prioritize implementing this, but we'd review a PR from a motivated community member that wanted to add the following type of logic during incremental runs:
ALTER TABLE mydataset.mytable
  SET OPTIONS (
    -- Sets table expiration to timestamp 2025-02-03 12:34:56
    expiration_timestamp = TIMESTAMP '2025-02-03 12:34:56');

Here's an example of getting this setting from the config:

https://github.com/dbt-labs/dbt-bigquery/blob/3ce88d75ac78b9aac1dcaa184c94e235f661a6f0/dbt/adapters/bigquery/impl.py#L754-L755


Type-Checking Static Members of a Class

This is something that was non-obvious to me at first glance.  I figured writing down a simple example for others would not hurt.

@microsoft-github-policy-service agree

I'm thinking about moving this down to the next section, "Static blocks in classes", as an illustrative example which fits better there.
interface VehicleType {
  manufacturer: string
}

interface VehicleTypeStatic {
  readonly wheelCount: number;
}

class Vehicle implements VehicleType
{
  static {
    const temp: VehicleTypeStatic = Vehicle;
    void(temp);
  }

  readonly manufacturer: string;

  constructor(maker: string) {
    this.manufacturer = maker;
  }

  static readonly wheelCount = 4;
}

I'm wondering what people think of this alternative.

I may not be able to respond in a timely manner.  I have a new job which takes up a lot more of my time than I've been used to.  If anyone wants to close this pull request, I have no objection.


fix(website): header docs in tablet view

Signed-off-by: Bogdan Bogdanov<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[x] clarity.design website / infrastructure changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

@hippee-lee  I thought that the do/dont component was bringing the issue but I found out that the angular component demos are written manually so this is what is needed for the headers to look okay on a tablet.

@hippee-lee  I thought that the do/dont component was bringing the issue but I found out that the angular component demos are written manually so this is what is needed for the headers to look okay on a tablet.


Replace the memory and CPU input fields with sliders

*Note the emptyStubForJSLinter.js file is for jest, which doesn't
expect to import CSS files.
PR #73 is now a bridge to get to the sliders -- it brings in the unit-test framework, among other things,
but this PR drops a lot of code from that PR, like much of the validation code.

Going to create a new PR against main, should be simpler.

Going to create a new PR against main, should be simpler.


Building sample OS fails

Describe the bug
I run the quick start sample os build and it fails.
cos-toolkit version:
master of the cos-toolkit-sample-repo(cc67643266c80f246e2cbc119170c6b8366a6fa8)
CPU architecture, OS, and Version:
# docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)

Server:
 Containers: 5
  Running: 1
  Paused: 0
  Stopped: 4
 Images: 99
 Server Version: 20.10.6
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc version: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.4.0-1048-aws
 Operating System: Ubuntu 20.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 3.786GiB
 Name: ip-172-31-15-143
 ID: IA5G:4Y63:4BCK:56BU:SUL4:GWDU:E2OT:LQAF:IDZW:NDI5:ZZHY:FWGD
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

WARNING: No swap limit support

To Reproduce

Provision an ubuntu20.04 EC2 instance
Install docker
Run the quick start build.

$ git clone https://github.com/rancher-sandbox/cos-toolkit-sample-repo
$ cd cos-toolkit-sample-repo
$ source .envrc
$ cos-build

Expected behavior
Build succeeds.
Logs
Step 12/13 : RUN checkmodule -M -m -o cOS.mod cOS.te && semodule_package -o cOS.pp -m cOS.mod
  ---> Using cache
 ---> 1be520969ead
Step 13/13 : RUN semodule -i cOS.pp
  ---> Running in c5bfa5ae92e2
 libsemanage.semanage_commit_sandbox: Error while renaming /var/lib/selinux/targeted/active to /var/lib/selinux/targeted/previous. (Invalid cross-device link).
semodule:  Failed!
 The command '/bin/sh -c semodule -i cOS.pp' returned a non-zero code: 1
 Error: while resolving join images: failed building join image: Failed compiling system/selinux-policies-0.0.6+3: failed building package image: Could not push image: raccos/sampleos:ffc8618ecbfbffc11cc3bca301cc49867eb7dccb623f951dd92caa10ced29b68 selinux-policies-system-0.0.6+3.dockerfile: Could not build image: raccos/sampleos:ffc8618ecbfbffc11cc3bca301cc49867eb7dccb623f951dd92caa10ced29b68 selinux-policies-system-0.0.6+3.dockerfile: Failed running command: : exit status 1
 Bailing out
make: *** [Makefile:45: build] Error 1

Additional context
Possibly related to https://github.com/docker/for-linux/issues/480 but the workaround there does not help.
The metacopy parameter is disabled.
$ cat /sys/module/overlay/parameters/metacopy
N

As the workaround, I change the docker storage driver from overlay2 to devicemapper then the build succeeds.

Another failure but this one seems to be occasional. A retry succeeds. Print the log here for reference.
 🐋  Building image raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d done
 📦  8/8 system/cos-0.5.3+1 ⤑ 🔨  build system/selinux-policies-0.0.6+3 ✅  Done
 🚀  All dependencies are satisfied, building package requested by the user system/cos-0.5.3+1
 📦  system/cos-0.5.3+1  Using image:  raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d
 📦  system/cos-0.5.3+1 🐋  Generating 'builder' image from raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d as raccos/sampleos:builder-8533d659df2505a518860bd010b7a8ed with prelude steps
🚧  warning Failed to download 'raccos/sampleos:builder-8533d659df2505a518860bd010b7a8ed'. Will keep going and build the image unless you use --fatal
🚧  warning Failed pulling image: Error response from daemon: manifest for raccos/sampleos:builder-8533d659df2505a518860bd010b7a8ed not found: manifest unknown: manifest unknown
: exit status 1
 🐋  Building image raccos/sampleos:builder-8533d659df2505a518860bd010b7a8ed
 Sending build context to Docker daemon  9.728kB
 Step 1/10 : FROM raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d
  ---> f1122e79b17e
Step 2/10 : COPY . /luetbuild
  ---> 4ff3e202951b
 Step 3/10 : WORKDIR /luetbuild
  ---> Running in 7ec571b96c6f
 Removing intermediate container 7ec571b96c6f
  ---> 9e05366f830a
Step 4/10 : ENV PACKAGE_NAME=cos
  ---> Running in 30297dbd21a3
 Removing intermediate container 30297dbd21a3
  ---> 4c4838b629f4
 Step 5/10 : ENV PACKAGE_VERSION=0.5.3+1
  ---> Running in 36361b617252
 Removing intermediate container 36361b617252
  ---> 6ac0d3a2ff9a
Step 6/10 : ENV PACKAGE_CATEGORY=system
  ---> Running in f20c2cf3cf34
 Removing intermediate container f20c2cf3cf34
  ---> a902ff95d273
 Step 7/10 : COPY --from=quay.io/costoolkit/build-cache:f3a333095d9915dc17d7f0f5629a638a7571a01dcf84886b48c7b2e5289a668a /usr/bin/yip /usr/bin/yip
  ---> 42fa00d9c990
 Step 8/10 : COPY --from=quay.io/costoolkit/build-cache:e3bbe48c6d57b93599e592c5540ee4ca7916158461773916ce71ef72f30abdd1 /usr/bin/luet /usr/bin/luet
 e3bbe48c6d57b93599e592c5540ee4ca7916158461773916ce71ef72f30abdd1: Pulling from costoolkit/build-cache
 3599716b36e7:  Already exists
 24a39c0e5d06: Already exists
 4f4fb700ef54: Already exists
 4f4fb700ef54: Already exists
 4f4fb700ef54: Already exists
 378615c429f5: Already exists
 c28da22d3dfd:  Already exists
 ddb4dd5c81b0: Already exists
 92db41c0c9ab: Already exists
 4f4fb700ef54: Already exists
 6e0ca71a6514: Already exists
 47debb886c7d: Already exists
 4f4fb700ef54: Already exists
 4f4fb700ef54: Already exists
 4f4fb700ef54: Already exists
 d0c9d0f8ddb6: Already exists
 e5a48f1f72ad:  Pulling fs layer
 4f4fb700ef54:  Pulling fs layer
 7d603b2e4a37:  Pulling fs layer
 64c4d787e344:  Pulling fs layer
 f8835d2e60d1:  Pulling fs layer
 64c4d787e344:  Waiting
 f8835d2e60d1:  Waiting
 e5a48f1f72ad:  Download complete
 e5a48f1f72ad:  Pull complete
 4f4fb700ef54:  Verifying Checksum
 4f4fb700ef54:  Download complete
 4f4fb700ef54:  Pull complete
 7d603b2e4a37: Verifying Checksum
7d603b2e4a37: Download complete
 64c4d787e344: Verifying Checksum
64c4d787e344: Download complete
 7d603b2e4a37: Pull complete
 64c4d787e344: Pull complete
 f8835d2e60d1:  Verifying Checksum
 f8835d2e60d1:  Download complete
 f8835d2e60d1: Pull complete
 Digest: sha256:9b58bed47ff53f2d6cc517a21449cae686db387d171099a4a3145c8a47e6a1e0
 Status: Downloaded newer image for quay.io/costoolkit/build-cache:e3bbe48c6d57b93599e592c5540ee4ca7916158461773916ce71ef72f30abdd1
 failed to export image: failed to create image: failed to get layer sha256:118537d8997a08750ab1ac3d8e8575e40fe60e8337e02633b0d8a1287117fe78: layer does not exist
 Error: while resolving join images: failed building join image: failed building package image: Could not push image: raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d cos-system-0.5.3+1-builder.dockerfile: Could not build image: raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d cos-system-0.5.3+1-builder.dockerfile: Failed running command: : exit status 1
 Bailing out
make: *** [Makefile:45: build] Error 1

Describe the bug
I run the quick start sample os build and it fails.
cos-toolkit version:
master of the cos-toolkit-sample-repo(cc67643266c80f246e2cbc119170c6b8366a6fa8)
CPU architecture, OS, and Version:
# docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)

Server:
 Containers: 5
  Running: 1
  Paused: 0
  Stopped: 4
 Images: 99
 Server Version: 20.10.6
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc version: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.4.0-1048-aws
 Operating System: Ubuntu 20.04.2 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 3.786GiB
 Name: ip-172-31-15-143
 ID: IA5G:4Y63:4BCK:56BU:SUL4:GWDU:E2OT:LQAF:IDZW:NDI5:ZZHY:FWGD
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

WARNING: No swap limit support

To Reproduce
1. Provision an ubuntu20.04 EC2 instance

2. Install docker

3. Run the quick start build.

$ git clone https://github.com/rancher-sandbox/cos-toolkit-sample-repo
$ cd cos-toolkit-sample-repo
$ source .envrc
$ cos-build

Expected behavior
Build succeeds.
Logs
Step 12/13 : RUN checkmodule -M -m -o cOS.mod cOS.te && semodule_package -o cOS.pp -m cOS.mod
  ---> Using cache
 ---> 1be520969ead
Step 13/13 : RUN semodule -i cOS.pp
  ---> Running in c5bfa5ae92e2
 libsemanage.semanage_commit_sandbox: Error while renaming /var/lib/selinux/targeted/active to /var/lib/selinux/targeted/previous. (Invalid cross-device link).
semodule:  Failed!
 The command '/bin/sh -c semodule -i cOS.pp' returned a non-zero code: 1
 Error: while resolving join images: failed building join image: Failed compiling system/selinux-policies-0.0.6+3: failed building package image: Could not push image: raccos/sampleos:ffc8618ecbfbffc11cc3bca301cc49867eb7dccb623f951dd92caa10ced29b68 selinux-policies-system-0.0.6+3.dockerfile: Could not build image: raccos/sampleos:ffc8618ecbfbffc11cc3bca301cc49867eb7dccb623f951dd92caa10ced29b68 selinux-policies-system-0.0.6+3.dockerfile: Failed running command: : exit status 1
 Bailing out
make: *** [Makefile:45: build] Error 1

Additional context
Possibly related to docker/for-linux#480 but the workaround there does not help.
The metacopy parameter is disabled.
$ cat /sys/module/overlay/parameters/metacopy
N

As the workaround, I change the docker storage driver from overlay2 to devicemapper then the build succeeds.

Looks like indeed an issue with the underlying storage driver, I think we should at least document the workaround in our docs in a proper section, like "Known issues" and alikes

Another failure but this one seems to be occasional. A retry succeeds. Print the log here for reference.
 🐋  Building image raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d done
 📦  8/8 system/cos-0.5.3+1 ⤑ 🔨  build system/selinux-policies-0.0.6+3 ✅  Done
 🚀  All dependencies are satisfied, building package requested by the user system/cos-0.5.3+1
 📦  system/cos-0.5.3+1  Using image:  raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d
 📦  system/cos-0.5.3+1 🐋  Generating 'builder' image from raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d as raccos/sampleos:builder-8533d659df2505a518860bd010b7a8ed with prelude steps
🚧  warning Failed to download 'raccos/sampleos:builder-8533d659df2505a518860bd010b7a8ed'. Will keep going and build the image unless you use --fatal
🚧  warning Failed pulling image: Error response from daemon: manifest for raccos/sampleos:builder-8533d659df2505a518860bd010b7a8ed not found: manifest unknown: manifest unknown
: exit status 1
 🐋  Building image raccos/sampleos:builder-8533d659df2505a518860bd010b7a8ed
 Sending build context to Docker daemon  9.728kB
 Step 1/10 : FROM raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d
  ---> f1122e79b17e
Step 2/10 : COPY . /luetbuild
  ---> 4ff3e202951b
 Step 3/10 : WORKDIR /luetbuild
  ---> Running in 7ec571b96c6f
 Removing intermediate container 7ec571b96c6f
  ---> 9e05366f830a
Step 4/10 : ENV PACKAGE_NAME=cos
  ---> Running in 30297dbd21a3
 Removing intermediate container 30297dbd21a3
  ---> 4c4838b629f4
 Step 5/10 : ENV PACKAGE_VERSION=0.5.3+1
  ---> Running in 36361b617252
 Removing intermediate container 36361b617252
  ---> 6ac0d3a2ff9a
Step 6/10 : ENV PACKAGE_CATEGORY=system
  ---> Running in f20c2cf3cf34
 Removing intermediate container f20c2cf3cf34
  ---> a902ff95d273
 Step 7/10 : COPY --from=quay.io/costoolkit/build-cache:f3a333095d9915dc17d7f0f5629a638a7571a01dcf84886b48c7b2e5289a668a /usr/bin/yip /usr/bin/yip
  ---> 42fa00d9c990
 Step 8/10 : COPY --from=quay.io/costoolkit/build-cache:e3bbe48c6d57b93599e592c5540ee4ca7916158461773916ce71ef72f30abdd1 /usr/bin/luet /usr/bin/luet
 e3bbe48c6d57b93599e592c5540ee4ca7916158461773916ce71ef72f30abdd1: Pulling from costoolkit/build-cache
 3599716b36e7:  Already exists
 24a39c0e5d06: Already exists
 4f4fb700ef54: Already exists
 4f4fb700ef54: Already exists
 4f4fb700ef54: Already exists
 378615c429f5: Already exists
 c28da22d3dfd:  Already exists
 ddb4dd5c81b0: Already exists
 92db41c0c9ab: Already exists
 4f4fb700ef54: Already exists
 6e0ca71a6514: Already exists
 47debb886c7d: Already exists
 4f4fb700ef54: Already exists
 4f4fb700ef54: Already exists
 4f4fb700ef54: Already exists
 d0c9d0f8ddb6: Already exists
 e5a48f1f72ad:  Pulling fs layer
 4f4fb700ef54:  Pulling fs layer
 7d603b2e4a37:  Pulling fs layer
 64c4d787e344:  Pulling fs layer
 f8835d2e60d1:  Pulling fs layer
 64c4d787e344:  Waiting
 f8835d2e60d1:  Waiting
 e5a48f1f72ad:  Download complete
 e5a48f1f72ad:  Pull complete
 4f4fb700ef54:  Verifying Checksum
 4f4fb700ef54:  Download complete
 4f4fb700ef54:  Pull complete
 7d603b2e4a37: Verifying Checksum
7d603b2e4a37: Download complete
 64c4d787e344: Verifying Checksum
64c4d787e344: Download complete
 7d603b2e4a37: Pull complete
 64c4d787e344: Pull complete
 f8835d2e60d1:  Verifying Checksum
 f8835d2e60d1:  Download complete
 f8835d2e60d1: Pull complete
 Digest: sha256:9b58bed47ff53f2d6cc517a21449cae686db387d171099a4a3145c8a47e6a1e0
 Status: Downloaded newer image for quay.io/costoolkit/build-cache:e3bbe48c6d57b93599e592c5540ee4ca7916158461773916ce71ef72f30abdd1
 failed to export image: failed to create image: failed to get layer sha256:118537d8997a08750ab1ac3d8e8575e40fe60e8337e02633b0d8a1287117fe78: layer does not exist
 Error: while resolving join images: failed building join image: failed building package image: Could not push image: raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d cos-system-0.5.3+1-builder.dockerfile: Could not build image: raccos/sampleos:cc0aee4ff6c194f920a945c45ebcb487c3e22c5ab40e2634ea70c064dfab206d cos-system-0.5.3+1-builder.dockerfile: Failed running command: : exit status 1
 Bailing out
make: *** [Makefile:45: build] Error 1

This seems another issue, can you try by enabling docker buildkit with DOCKER_BUILDKIT=1?


[Doc] Document use of CloudInit CRD

The finer details here may change, at least until the corresponding HEP for this enhancement is merged (TODO: add link to HEP PR when it exists)
Is your doc request related to a problem? Please describe or add related issue ID. https://github.com/harvester/harvester/issues/3902
Describe the solution you'd like
Perhaps as sub-headings under the "Host Management" page.

Creating CloudInit objects via the Harvester dashboard (GitHub issue TBD) and via kubectl
Using the CloudInit match selector to customize which nodes receive the CloudInit
Expected behavior for updating match selectors which causes nodes to no longer match
Expected behavior for deleting CloudInit objects

There's a possibility that it would be worthwhile to highlight to the User/Operator/Admin/Org that plans to use the CloudInit CRD functionality things like:

the importance for the user/admin/operator/org to understand how Elemental Toolkit / Elemental Cloud-Init Executor works, as in - understanding how Elemental Toolkit Cloud-Init Executor will parse the data you feed into the creation of your Harvester CloudInit CRD
how to "map" Harvester configuration properties to their appropriate:

Elemental Toolkit Stage
Elemental Toolkit's properties / objects / lists / items, etc.

@connorkuehl please work with @jillian-maroket on this


0.1.4 Module variable assignment now DeepCopy

Codecov Report

Merging #322 into master will decrease coverage by 0.05%.
The diff coverage is 78.57%.

@@            Coverage Diff             @@
##           master     #322      +/-   ##
==========================================
- Coverage   87.25%   87.19%   -0.06%
==========================================
  Files          15       15
  Lines        2604     2616      +12
==========================================
+ Hits         2272     2281       +9
- Misses        214      216       +2
- Partials      118      119       +1

Impacted Files
Coverage Δ

anko.go
68.47% <ø> (ø)
:arrow_up:

vm/vmStmt.go
96.28% <100%> (+0.04%)
:arrow_up:

vm/vmLetExpr.go
85.77% <50%> (-0.9%)
:arrow_down:

Continue to review full report at Codecov.

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

Thank you.

@mattn Can you add release 0.1.3 & 0.1.4?

Tagged now.

Thanks! :)


Multiedit does not show tags with indicators

When limiting marc output to certain tags it seems not possible to show tags that use indicators, but only marc tags with blank indicators. Also % wildcards seem not to apply. Example:
<datafield tag="024" ind1="7" ind2=" ">
    <subfield code="a">10.1103/PhysRevB.91.045136</subfield>
    <subfield code="2">doi</subfield>
</datafield>
<datafield tag="024" ind1="7" ind2=" ">
    <subfield code="a">0163-1829</subfield>
    <subfield code="2">ISSN</subfield>
</datafield>

Define as output field:
Output tags: 0247_

No tags get displayed.
Same for:
Output tags: 024
Output tags: 024%%
Output tags: 0247%

IMHO specifying correct indicators should show the proper indicators should work. Probably, wildcarding would be nice.

Testing on the latest maint-1.2, I can well ask in the Multi-Record Editor to output tags with indicators, for example 65017.
However it is still true that I cannot ask for wildcard.  @jmartinm Do you have any improvements here maybe?


Performance issue, one array item update triggers all children components re-render

Describe the bug
when use query result with v-for, any item in the list get updated will trigger all children components rerender.
Steps to reproduce the bug

Define models
Create data
Retrieve data
Bind data to component as computed property
Loop items with v-for, pass items to child component
update one of the item
all the children components get updated/re-rendered

Expected behaviour
Only the component with the updated item should be re-rendered.
Versions

Vuex ORM: 0.36.3
Vue: 2.6.11

Link to minimal reproduction
CodeSandbox https://codesandbox.io/s/broken-https-l8mk8?file=/src/App.vue
Additional context
I tested with normal usage of vuex, has no this kind of issue. please check out the example in the code sandbox above.

it also exists in the next version
https://codesandbox.io/s/sharp-lichterman-5hwnq?file=/src/App.vue

This is currently expected behavior. Your Vuex example is not equal to what Vuex ORM is doing.
The thing is, Vuex ORM returns new records from the store. Try changing your list computed property to this.
const list = computed(() => {
  return store.state.list.map((item) => ({ ...item }));
});

Then you can see 2 update log is called. Vuex ORM must return a new object instead of returning the store state as is because we must "mutate" the state before returning it when we have relationships.
To resolve this issue, I think we need to implement a caching system in Vuex ORM.


fix: use --no-goma in flutter-engine to prevent build error

While building the upstream code, I encountered an error that required me to remove the goma component from the bitbake recipe build of flutter-engine.bb. Interestingly, I observed that the meta-flutter/meta-flutter project followed a similar approach. You can find an example here: GitHub Link. Given this, I believe it would be prudent for us to adopt the same strategy. This could help us address the issue effectively.

Thank you for sending the PR. Could you update AUTHORS too? See also CONTRIBUTING.md

Please sign a Developer Certificate of Origin (DCO) in git comment?

@HidenoriMatsubayashi, I edit my commit to add the signed DCO.
Thank you,